When I browse a folder in Files, I would like to open a photo or video, and then use the arrow keys to display/play the next photo or video file. Loupe (the default image viewer in 25.10) works perfectly for photos, but does not playback videos.

I've looked at Photo & video viewer similar to Android's Gallery app and similar Q&As, but they all basically say "open all your photos with an app like VLC or gThumb".

I do not want to "import" my media in a special folder/gallery. I have tens of thousands of photos across many folders and I like the way they are organized.

I tried:

• gThumb: almost does the job, but it creates a new window for each video, not allowing me to quickly breeze through photos/videos. That's not the user experience I'm after.

• Shotwell: does not playback videos, it just skips them, like Loupe.

• When I tried installing Gwenview, I was told by apt that I need to install 230 new packages, so I said "no thanks".

I'm surprised this doesn't just work in Ubuntu 25.10 desktop. It feels like a rather basic requirement.

How do people browse their video and photo folders?

I updated Linux kernel in Ubuntu on my old iMac 14.2 to 6.17.0-14 I think, but now it will only boot into 6.14.0-37 via Advanced Options. The screen produced by the usual boot shows this error message: Kernel Panic: VFS: Unable to mount root fs on unknown-block (0.0) What can I do?

$ uname -a
Linux ray-desktop 6.14.0-37-generic #37~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 20 10:25:38 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 24.4.

• I can login okay to my own (admin) account.
• Other users enter correct password (error message for wrong password) and it immediately goes back to the login screen to choose a user.

Following suggestions elsewhere I did:

$ sudo apt update ; sudo apt install --reinstall ubuntu-desktop gdm3

but there was no obvious difference.

I've also done:

sudo chown -R angie:angie /home/angie
sudo chmod -R o-w /home/angie
sudo chmod -R g-w /home/angie

These are the only user files that have changed since the last backup:

./.bash_history
./.config/dconf/user
./.config/evince/print-settings
./.config/ibus/bus/816f888a34bf4fb1bde1af3c3d97ad49-unix-2
./.config/ibus/bus/816f888a34bf4fb1bde1af3c3d97ad49-unix-wayland-0
./.config/libreoffice/4/user/config/javasettings_Linux_X86_64.xml
./.config/libreoffice/4/user/pack/config/javasettings_Linux_X86_64.pack
./.config/libreoffice/4/user/pack/registrymodifications.pack
./.config/libreoffice/4/user/registrymodifications.xcu
./.config/tiling-assistant/tiledSessionRestore.json
./.local/share/evolution/addressbook/system/contacts.db
./.local/share/gnome-shell/application_state
./.local/share/icc/edid-ad2ce0cfe20ce3cd48444ac28e86e056.icc
./.local/share/keyrings/login.keyring

The hardware is all Intel. (an NUC)

I'd try rebooting, but I'm concerned I'll end up locked out too.

Thanks for the interactive help in the comments. I'll give it a rest until tomorrow, and try again then.

how to check in the bash file dialog existence of the file "File Name", and if not. to open a new file "File Name" (in the w-r mode)?

Trying to format this drive to no partitions but get error:

unmounting/dev/sdb4(or 1,2,3) target busy(udisks-error-quark,14)

Screenshot:

How can I eliminate 3 of the partitions so I get an empty full 16gb drive to work with

I recently reset Ubuntu 22.04.05 LTS on my Dell Precision 5510. For context, I did not clear my Ubuntu partition myself and simply let the autosetup install, which I assumed would properly reset my Ubuntu with a fresh installation. Everything seems to be working fine (save for the audio and bluetooth that was an issue on my previous installation as well) except my computer shuts down instead of suspending. This happens if I hit the suspend button on Ubuntu, if I close the laptop lid (Tweaks is set to suspend on closing the lid), and systemctl suspend. In every case the computer shuts down instead of suspending.

To my further surprise, my Windows also shuts down instead of sleeping now, which makes me assume I have an issue with my hardware. However, I am unsure of where to start when it comes to debugging a hardware issue. I have examined my journalctl file, which gives very little detail.

Here is my journalctl after running journalctl -b -1 -e

Feb 04 20:05:24 kenan-Precision-5510 systemd[1]: Finished NVIDIA system suspend actions.
Feb 04 20:05:24 kenan-Precision-5510 systemd[1]: Starting System Suspend...
Feb 04 20:05:24 kenan-Precision-5510 systemd-sleep[11415]: Entering sleep state 'suspend'...
Feb 04 20:05:24 kenan-Precision-5510 kernel: PM: suspend entry (deep)

I would really appreciate any advice on where to begin debugging.

Additional context:

Specs:
make: dell-precision-5510
cpu: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
gpu: Quadro M1000M

Bios last updated July 7, 2022

Someone posted this question on the forum a week ago but they never followed up with clarifying information to the commenters. I am having the same issue as I am a new Linux/Ubuntu user also. My question includes the outputs asked for from the original question. The issue is the output at the end of step 3.

I am using Ubuntu 24.04.3 LTS noble.

I followed the steps listed "How to install the Proton VPN GUI app on Ubuntu" Here's the outputs that I'm getting:

Step 1

rom@NUC:~$ wget https://repo.protonvpn.com/debian/dists/stable/main/binary-all/protonvpn-stable-release_1.0.8_all.deb

--2026-02-05 12:32:28-- 
https://repo.protonvpn.com/debian/dists/stable/main/binary-all/protonvpn-stable-release_1.0.8_all.deb
Resolving repo.protonvpn.com (repo.protonvpn.com)... 
172.67.70.114, 104.26.4.35, 104.26.5.35, ... 
Connecting to repo.protonvpn.com (repo.protonvpn.com)|172.67.70.114|:443... connected. 
HTTP request sent, awaiting response... 
200 OK Length: 4852 (4.7K)
[application/octet-stream] Saving to:
‘protonvpn-stable-release_1.0.8_all.deb.8’
 
protonvpn-stable-re 100%[===================>] 4.74K --.-KB/s in 0s
 
2026-02-05 12:32:28 (15.0 MB/s) -
‘protonvpn-stable-release_1.0.8_all.deb.8’ saved [4852/4852]

Step 2

rom@NUC:~$ sudo dpkg -i ./protonvpn-stable-release_1.0.8_all.deb &&
sudo apt update 
[sudo] password for rom: 
(Reading database ... 213964 files and directories currently installed.) 
Preparing to unpack .../protonvpn-stable-release_1.0.8_all.deb ... Unpacking protonvpn-stable-release (1.0.8) over (1.0.8) ... 
Setting up protonvpn-stable-release (1.0.8) ... 
Hit:1 https://repo.nordvpn.com/deb/nordvpn/debian stable InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu noble InRelease 
Hit:3 http://security.ubuntu.com/ubuntu noble-security InRelease 
Hit:4 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease Hit:6 https://esm.ubuntu.com/apps/ubuntu noble-apps-security InRelease Hit:7 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates InRelease Hit:8 https://esm.ubuntu.com/infra/ubuntu noble-infra-security InRelease
Hit:9 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates InRelease 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
1 package can be upgraded. Run 'apt list --upgradable' to see it. 
W: https://repo.nordvpn.com/deb/nordvpn/debian/dists/stable/InRelease:
Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg),
see the DEPRECATION section in apt-key(8) for details.

Step 2.5

rom@NUC:~$ echo  "0b14e71586b22e498eb20926c48c7b434b751149b1f2af9902ef1cfe6b03e180  protonvpn-stable-release_1.0.8_all.deb" | sha256sum --check -

protonvpn-stable-release_1.0.8_all.deb: OK

Step 3

rom@NUC:~$ sudo apt install proton-vpn-gnome-desktop 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
**E: Unable to locate package proton-vpn-gnome-desktop**

Here's the result of the cat cmd

rom@NUC:~$ cat /etc/apt/sources.list.d/protonvpn-stable.sources 
cat: /etc/apt/sources.list.d/protonvpn-stable.sources: No such file or directory

Any help would be appreciated. I intentionally broke the links in step 2,by making them http due to not having enough reputation to post more than 8 links.

@steeldriver After uninstalling then re-installing, this is the output that I get.

rom@NUC:~$ sudo apt install proton-vpn-gnome-desktop 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Some packages could not be installed. 
This may mean that you have requested an impossible situation or 
if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. 
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:  
linux-headers-generic : Depends: linux-headers-6.8.0-100-generic 
but it is not installable
E: Unable to correct problems, you have held broken packages.

After updating to kernel 6.8.0-94 and having the dependency on Nvidia drivers, I get a kernel panic at boot. Kernel module builds fail due to missing drm/drm_legacy.h and switching to the hwe kernel (6.17.0-14) yields the same result, but likely due to the fact that the initrd is not mounting encrypted disks before it tries to mount the root partition.

Has anyone solved this yet?

I’m using Ubuntu 22.04 with the following NVIDIA configuration, which is the only setup where the driver loads correctly and nvidia-smi works:

System configuration

Kernel: 6.8.0-94.96~22.04.1

GPU: NVIDIA GeForce RTX 4050 Laptop GPU

Driver: nvidia-driver-580-open

Open kernel NVIDIA driver

CUDA: 13.0

Output of nvidia-smi:

Thu Feb 5 14:52:00 2026 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 580.126.09 Driver Version: 580.126.09 CUDA Version: 13.0 | +-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 4050 Laptop GPU | 00000000:01:00.0 Off | N/A | +-----------------------------------------------------------------------------------------+

With this configuration:

✅ NVIDIA driver loads correctly

✅ nvidia-smi works

✅ GPU compute and acceleration work

Issue

The second monitor does not work with this configuration.

Internal display works

External monitor is not detected or does not activate

This issue only occurs when using nvidia-driver-580-open

Question

Is there a better NVIDIA driver or kernel configuration for Ubuntu 22.04 that:

Keeps the NVIDIA driver working correctly

Preserves CUDA / GPU acceleration

Allows the second monitor to work

Any known working setups or suggestions are welcome.

I installed the latest upgrade to Ubuntu this morning (2026/02/05) and now my laptop keyboard is locked out. I can’t revert the upgrade because I can’t log in to do so. This is almost enough to make me go back to windows.

I'm having a weird problem trying unsuccessfully to update the kernel to 6.8.0-100 on a 24.04 computer. It's throwing apt errors (held back and/or no installation candidate).

The host popped up this morning as requiring a kernel update from 6.8.0-94 to 6.8.0-100. I have some scripting in place that would normally handle this, but today things are not going my way.

$ sudo apt -y upgrade
Hit:1 http://au.archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:2 http://au.archive.ubuntu.com/ubuntu noble InRelease                    
Hit:3 http://au.archive.ubuntu.com/ubuntu noble-backports InRelease          
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease             
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.

Then:

$ apt list --upgradable
Listing... Done
linux-generic/noble-updates 6.8.0-100.100 amd64 [upgradable from: 6.8.0-94.96]
linux-headers-generic/noble-updates 6.8.0-100.100 amd64 [upgradable from: 6.8.0-94.96]
linux-image-generic/noble-updates 6.8.0-100.100 amd64 [upgradable from: 6.8.0-94.96]

Next:

$ sudo apt -y upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libmagickcore-6.q16-7t64 libsvn1 imagemagick-6-common subversion
  libapache2-mod-security2 libmagickwand-6.q16-7t64
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

So I am trying to force the held packages:

$ sudo apt -y install linux-generic linux-headers-generic linux-image-generic
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-generic : Depends: linux-headers-6.8.0-100-generic but it is not installable
 linux-image-generic : Depends: linux-image-6.8.0-100-generic but it is not going to be installed
                       Depends: linux-modules-extra-6.8.0-100-generic but it is not installable
E: Unable to correct problems, you have held broken packages.

I'm trying to decide if this is:

• repo lag? - but I've tried various regional repositories with the same outcome

• 6.8.0-100 has been pulled?

• Something I've never encountered before

EDIT: "aptitude -f install" and "apt install -f" also refused to install the new kernel. "apt install -f" declared 6.8.0-100 "REMOVED" despite not being installed, and no longer appears as an upgrade option after "apt -y update".

I wouldn't post here if I didn't feel like I'm struggling with something basic that I'm missing.

I recently installed a new Ubuntu installation. It was originally installed as Ubuntu Server (25.10), due to the desire to install in RAID, and then Ubuntu desktop (apt install ubuntu-desktop) immediately installed via apt.

It has booted fine, but I've had problems with the hardware crashing. I got rid of an NVIDIA card and crashed went from daily to less than weekly, so I guess that's an improvement.

The problem is that I can't boot the system, but it looks like everything is going fine. It is booting without the splash screen, and everything has a green [ OK ], but then it just stops and gets stuck. This is before networking is working, no GUI and no terminals running on tty2,3,4,5. I can switch to those ttys, but there is just a blinking cursor. Without networking, of course, no SSH.

If I boot into recovery mode, networking works right away, and if I "continue boot" it goes into the desktop, and networking, ssh, etc. are working, but only at 1024x768 resolution and SSH won't connect to a terminal because it isn't "fully booted" and kicks me off.

I've run fsck on all of the filesystems and, although the array that gets mounted as /home has some issues with tree depth or something, they didn't seem like hard errors and correcting them didn't fix it.

For reference, this is where I end up stuck at a black screen with the following boot messages:

[  OK  ] Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Started dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Started fstrim.timer - Discard unused filesystem blocks once a week.
[  OK  ] Started fwupd-refresh.timer - Refresh fwupd metadata regularly.
[  OK  ] Started logrotate.timer - Daily rotation of log files.
[  OK  ] Started man-db.timer - Daily man-db regeneration.
[  OK  ] Started mdcheck_continue.timer - MD array scrubbing - continuation.
[  OK  ] Started mdcheck_start.timer - MD array scrubbing.
[  OK  ] Started mdmonitor-oneshot.timer - Reminder for degraded MD arrays.
[  OK  ] Started motd-news.timer - Message of the Day.
[  OK  ] Started sysstat-collect.timer - Run system activity accounting tool every 10 minutes.
[  OK  ] Started sysstat-rotate.timer - Rotate daily system activity data file at midnight.
[  OK  ] Started sysstat-summary.timer - Generate summary of yesterday's process accounting.
[  OK  ] Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Reached target boot-complete.target - Boot Completion Check.
[  OK  ] Reached target paths.target - Path Units.
[  OK  ] Listening on avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on cups.socket - CUPS Scheduler.
[  OK  ] Listening on dbus.socket - D-Bus System Message Bus Socket.
[  OK  ] Listening on iscsid.socket - Open-iSCSI iscsid Socket.
         Starting lxd-installer.socket - Helper to install lxd snap on demand...
         Starting snapd.socket - Socket activation for snappy daemon...
[  OK  ] Listening on ssh.socket - OpenBSD Secure Shell server socket.
[  OK  ] Listening on sshd-unix-local.socket - OpenSSH Server Socket (systemd-ssh-generator, AF_UNIX Local).
[  OK  ] Listening on systemd-hostnamed.socket - Hostname Service Socket.
[  OK  ] Listening on uuidd.socket - UUID daemon activation socket.
[  OK  ] Listening on lxd-installer.socket - Helper to install lxd snap on demand.
[  OK  ] Listening on snapd.socket - Socket activation for snappy daemon.
[  OK  ] Reached target sockets.target - Socket Units.
[  OK  ] Started systemd-networkd.service - Network Configuration.
         Starting systemd-networkd-persistent-storage.service - Enable Persistent Storage in systemd-networkd...
[  OK  ] Finished systemd-networkd-persistent-storage.service - Enable Persistent Storage in systemd-networkd.

The system responds to Ctrl-Alt-Del and reboots cleanly, as well as REISUB reboot. It just won't load the environment completely. It seems like it thinks it's done.

Logs don't seem to contain any issues. I've disabled the wait for network service, for now, since that seemed to be hanging, if that is a clue. Where should I be looking?

For some unknow reason it just disconnected. Now can't get it to reconnect.

Restarting NetworkManager and Network icon shows '?', and still no access. Journalctl shows;

journalctl -u NetworkManager

Feb 03 10:40:59 stephen-MS-7640 systemd[1]: Started NetworkManager.service - Network Manager.
Feb 03 10:40:59 stephen-MS-7640 NetworkManager[5349]: <info>  [1770136859.0196] modem-manager: ModemManager available
Feb 03 10:40:59 stephen-MS-7640 NetworkManager[5349]: <info>  [1770136859.0680] agent-manager: agent[7109e950d6c526d9,:1.56/org.kde.plasma.networkmanagement/1000]: agent registered
Feb 03 10:40:59 stephen-MS-7640 NetworkManager[5349]: <info>  [1770136859.0838] manager: NetworkManager state is now ASLEEP
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[5349]: <info>  [1770138255.7610] caught SIGTERM, shutting down normally.
Feb 03 11:04:15 stephen-MS-7640 systemd[1]: Stopping NetworkManager.service - Network Manager...
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[5349]: <info>  [1770138255.7626] device (virbr0): bridge port vnet0 was detached
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[5349]: <info>  [1770138255.7696] exiting (success)
Feb 03 11:04:15 stephen-MS-7640 systemd[1]: NetworkManager.service: Deactivated successfully.
Feb 03 11:04:15 stephen-MS-7640 systemd[1]: Stopped NetworkManager.service - Network Manager.
Feb 03 11:04:15 stephen-MS-7640 systemd[1]: Starting NetworkManager.service - Network Manager...
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.8165] NetworkManager (version 1.46.0) is starting... (after a restart, boot:00e599ea-31b2-400d-b5f5-23ee90cc41e5)
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.8165] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, no-mac-addr-change.conf) (r>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.8211] manager[0x55fdf67f3e80]: monitoring kernel firmware directory '/lib/firmware'.
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.8211] monitoring ifupdown state file '/run/network/ifstate'.
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9243] hostname: hostname: using hostnamed
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9243] hostname: static hostname changed from (none) to "stephen-MS-7640"
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9252] dns-mgr: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9261] manager[0x55fdf67f3e80]: rfkill: Wi-Fi hardware radio set enabled
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9262] manager[0x55fdf67f3e80]: rfkill: WWAN hardware radio set enabled
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9286] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wif>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9309] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-bl>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9314] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-adsl>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9320] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wwa>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9336] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-tea>
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9343] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9345] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9346] manager: Networking is disabled by state file
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9355] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-settings->
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9356] settings: Loaded settings plugin: keyfile (internal)
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9357] ifupdown: management mode: managed
Feb 03 11:04:15 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138255.9357] ifupdown: interfaces file /etc/network/interfaces doesn't exist
Feb 03 11:04:16 stephen-MS-7640 generate[6315]: Permissions for /etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration should NOT be accessible by others.
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8603] dhcp: init: Using DHCP client 'internal'
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8606] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8618] device (enp2s0): carrier: link connected
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8623] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8634] device (virbr0): carrier: link connected
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8637] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8651] manager: (vnet0): new Tun device (/org/freedesktop/NetworkManager/Devices/4)
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8658] failed to open /run/network/ifstate
Feb 03 11:04:16 stephen-MS-7640 systemd[1]: Started NetworkManager.service - Network Manager.
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8668] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8679] manager: startup complete
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.8732] modem-manager: ModemManager available
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.9177] agent-manager: agent[8463d41f70f28715,:1.56/org.kde.plasma.networkmanagement/1000]: agent registered
Feb 03 11:04:16 stephen-MS-7640 NetworkManager[6304]: <info>  [1770138256.9311] manager: NetworkManager state is now ASLEEP


Since State is reported as "asleep" ...

stephen@stephen-MS-7640:~$ cat /var/lib/NetworkManager.state
cat: /var/lib/NetworkManager.state: No such file or directory
stephen@stephen-MS-7640:~$ nmcli connection show
NAME                UUID                                  TYPE      DEVICE
lo                  7bb3f01a-acd5-4d32-8ae8-2aa9ff372bb6  ethernet  --
netplan-enp2s0      7ea6f90b-3495-3533-948a-ef0035687c34  ethernet  --
Wired connection 1  6983a9cc-d8b8-3e3b-980b-152774c4357f  ethernet  --

stephen@stephen-MS-7640:~$ lspci | grep -i ethernet
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 06)


stephen@stephen-MS-7640:~$ sudo systemctl restart NetworkManager
stephen@stephen-MS-7640:~$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 44:8a:5b:97:f6:c1 brd ff:ff:ff:ff:ff:ff
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:cb:4a:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
stephen@stephen-MS-7640:~$ sudo ip link set enp2s0 up
stephen@stephen-MS-7640:~$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 44:8a:5b:97:f6:c1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::468a:5bff:fe97:f6c1/64 scope link
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:cb:4a:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever

I keep going round and round on suggested fixes. Nothing seems to work ... any ideas? Need more info??? Thanks for any help!

I'm a newbie to Ubuntu who's enjoying the fact that no bloatware is forced upon me. I'm learning the command line, and making slow progress for an oldie at 60 years. I have been trying to use my favorite VPN Proton as I use Proton mail as well. I'm following the instructions, but I've come to a dead end in the terminal tab with this output:

~$ sudo apt install proton-vpn-gnome-desktop
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package proton-vpn-gnome-desktop

Where am I going wrong? So far I have had no other issues with my choice of apps. I'm using the latest LTS version of Ubuntu.

PRETTY_NAME="Ubuntu 24.04.3 LTS"
ID_LIKE=debian

After a recent Ubuntu update, Bluetooth audio on a Sony WH‑1000XM4 headset no longer works in High Fidelity (A2DP sink Codec SBC) mode, including SBC‑XQ and AAC. The headset connects successfully and appears to negotiate the A2DP profile, but audio playback fails immediately. Sound still works in HSP/HFP (Headset/Handset mode).

The failure occurs at the moment PipeWire/WirePlumber attempts to start the A2DP audio stream. The Bluetooth transport opens, then instantly closes with an error.

Notes

• I restarted pulse, bluetooth, and everything I could think of
• I restarted the machine after setting changes
• I added this to ~/.config/pipewire/media-session.d/bluez-monitor.conf

   properties = {
     bluez5.codecs = [ sbc sbc_xq ]
     bluez5.default.rate = 48000
     bluez5.default.channels = 2
     bluez5.sbc-xq.bitpool = 76
   }

No effect

At this point I am not sure what else to try . The headset was working fine for years before this problem

I'm using KDE as my main desktop. Since the upgrade to Ubuntu 25.10, I can no longer share my screen whatever the app I'm using, Firefox (the deb one), snap or flatpak for Slack or Teams.
The feature just do not work at all and I can't do it.
I know that now Wayland is the only way, but I would expect that this screen sharing issue was solved in a reliable fashion to enforce the switch.
How can I have any app doing screen sharing from Ubuntu 25.10?

I'm trying to install Ubuntu in a Hyper-V VM on a Dell Latitude 7455, which has a Snapdragon X Elite X1E-80-100. I've found an ARM64 version of Desktop Ubuntu 24.04 and 24.10 on cdimage.ubuntu.com, but could not get past the Try or Install Ubuntu screen.

Every time I attempt it I get a black screen with a cursor that blinks once and then freezes.

I have also attempted to use VirtualBox, but VirtualBox doesn't support ARM64 Windows.

Is it possible to get Ubuntu to work in this environment. If so how? If not, are there alternatives?

After updating my Ubuntu from 22.04 to Ubuntu 24.04, my GRUB disappeared. There's no way to find it. Have other Ubuntu users had this problem?

I am currently using Ubuntu 24.04. When I turn on my PC and log in using my password, it lands on a black screen with only the mouse cursor visible. I am unable to perform any actions, including turning off my PC.

I found that pressing Ctrl+Alt+F4 allows me to switch to a terminal where I can log in using my username and password. After logging in, I can reboot my PC using the command line, and it works fine temporarily. However, the issue persists after some time, and I have to repeat the same steps again.

I am looking for a permanent solution to this problem.

Thank you!

It is an old Dell laptop, 2014. Lubuntu is installed. Is it reasonable to install Xubuntu instead of Lubuntu? HDD is very slow.

System:
  Kernel: 5.15.0-56-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: LXQt 0.17.1 Distro: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
Machine:
  Type: Portable System: Dell product: Inspiron 5547 v: A04
    serial: <filter>
  Mobo: Dell model: 08KNCD v: A00 serial: <filter> UEFI-[Legacy]: Dell
    v: A04 date: 05/09/2014
Battery:
  ID-1: BAT1 charge: 39.9 Wh (100.0%) condition: 39.9/43.8 Wh (91.0%)
    volts: 12.4 min: 11.1 model: LGC DELL 1V2F6498 status: Full
Memory:
  RAM: total: 3.72 GiB used: 1.25 GiB (33.7%)
  Array-1: capacity: 16 GiB slots: 2 EC: None max-module-size: 8 GiB
  Device-1: JDIMM1 size: No Module Installed
  Device-2: JDIMM2 size: 4 GiB speed: 1600 MT/s type: DDR3
CPU:
  Info: dual core model: Intel Core i5-4210U bits: 64 type: MT MCP
    arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 798 high: 799 min/max: 800/2700 cores: 1: 798 2: 798
    3: 798 4: 799 bogomips: 19155
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell
    driver: i915 v: kernel bus-ID: 00:02.0
  Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445
    530/535 620/625 Mobile]
    vendor: Dell driver: amdgpu v: kernel bus-ID: 03:00.0
  Device-3: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-1.8:5
  Display: server: X.Org v: 1.21.1.3 driver: X:
    loaded: amdgpu,ati,modesetting unloaded: fbdev,vesa gpu: i915
    resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:03.0
  Device-2: Intel 8 Series HD Audio vendor: Dell driver: snd_hda_intel
    v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.15.0-56-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell
    driver: r8169 v: kernel port: 4000 bus-ID: 01:00.0
  IF: enp1s0 state: down mac: <filter>
  Device-2: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter
    vendor: Dell Vostro 3470 driver: ath9k v: kernel bus-ID: 02:00.0
  IF: wlp2s0 state: up mac: <filter>
Bluetooth:
  Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8
    bus-ID: 1-1.5:6
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 2.1 lmp-v: 4.1
Drives:
  Local Storage: total: 465.76 GiB used: 7.67 GiB (1.6%)
  ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142
    size: 465.76 GiB
Partition:
  ID-1: / size: 456.88 GiB used: 7.67 GiB (1.7%) fs: ext4 dev: /dev/sda3
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A gpu: amdgpu temp: 44.0 C
  Fan Speeds (RPM): cpu: 2800

On February 5, 2026 AntiX with kernel 6.1 is installed. Neither Xubuntu nor Lububtu doesn't work with video card.

Upon an attempted do-release-upgrade from Ubuntu Server 20.04.4 to 22.04, the installation ran, and now upon reboot, it is stopping with this error:

cloud-init: schema.py[WARNING]: Invalid cloud-config provided: Please run 'sudo cloud-init schema --system' to see the schema errors.

It drops to a root prompt.

Running cloud-init schema --system gives: Error: Cloud config schema errors: users.0: {'gecos': 'User', 'groups': ['adm', 'cdrom', 'dip', 'plugdev', 'lxd', 'sudo'], 'lock_passwd': False, 'name': 'user', 'passwd' '<some hash>', 'shell': '/bin/bash'} is not valid under any of the given schemas

(where User/user is the name of my user account)
At this point there seems to be no way to proceed, now even attempting to boot with the previous kernel gives an instant kernel panic.

I am not trying to do any sort of cloud configuration. This is a single standalone server, so I have no idea what cloud instance is is trying to initialise.

Is there a way to bypass this? Or am I supposed to be creating a cloud of one machine?

Ubuntu 18.04 past cmake version 3.10.2

After I have install cmake with sudo make ,sudo make install,and cmake --version

(base) lzw@resplendent-star:~/3d_lib/cmake-3.17.1$ cmake --version
CMake Error: Could not find CMAKE_ROOT !!!
CMake has most likely not been installed correctly.
Modules directory not found in
/usr/local/share/cmake-3.10
cmake version 3.10.2

I have already installed Oracle VirtualBox and during installing of Genymotion it detected a valid version of VirtualBox. Virtualisation is enabled in BIOS setting of laptop and I have done everything from downloading latest version of VirtualBox and Genymotion to switching to 'Host only netwrok' in network preferences of VirtualBox.

But nothing works for me. This is the error I get while strating Genymotion:

In order to work, Genymotion requires VirtualBox to be installed on your computer. You can download the latest version of VirtualBox from www.virtualbox.org/wiki/Downloads.

Genymotion log archive has been saved in /home/sourabh/genymotion-log.zip
Please contact Genymotion support for more help.

Virtualization engine not found. Plugin loading aborted.

Can anyone tell me what's possibly going wrong?

Edit:

Here is a link to the log file: https://www.mediafire.com/file/jdi51acm136vk0f/genymotion-log.zip

I've encountered a problem while I was trying to set an encrypted logical partition for personal data. All I did was formating some free space on the same hard disk I installed Kubuntu using the KDE Partition Manager. I read multiples guides online on how to decrypt and use the encrypted partition and pretty much everyone suggests to use the cryptsetup command, then mount the partition somewhere in / and it should be ready to use. The problem is that whenever I launch the cryptsetup command, I receive the following error:

Cannot use device /dev/sda5 which is in use (already mapped or mounted)

Here is the command I launched:

sudo cryptsetup open /dev/sda5 partition-enc --type=luks

A not really elegant workaround seemed to be "deactivate" the logical partition in the KDE Partition Manager to make the cryptsetup command execute without errors, however, even doing so, the mounting process will give a unknown filesystem type 'crypto_LUKS', which means the file system has not been decrypted successfully, I reckon.

Disclaimer: I already searched for similar questions and issues online of course, but no one seems to be solved. I don't know if I'm doing something wrong but no guides or discussion I found seems to take this problem into account.

I have a problem where if I turn on the computer I tried to boot to Kubuntu, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)

If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.

That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.

I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.

Kubuntu boots to a black screen with the following error messages.

[    0.528611] EDD information not available.
[    0.530345] PM: Hibernation image not present or could not be loaded.
[    0.532079] md: Waiting for all devices to be available before autodetect
[    0.533721] md: If you don't use raid, use raid=noautodetect
[    0.535830] md: Autodetecting RAID arrays.
[    0.537468] md: Scanned 0 and added 0 devices.
[    0.539110] md: autorun ...
[    0.540769] md: ... autorun DONE.
[    0.542435] VFS: Cannot open root device "mapper/kubuntu--vg-root" or unknown-block(0,0): error -6
[    0.544121] Please append a correct "root=" boot option; here are the available partitions:
[    0.545812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.547512] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-65-generic #86-Ubuntu
[    0.549222] Hardware name: LENOVO 80G0/Lancer 5A6, BIOS A7CN40WW 07/18/2014
[    0.550945]  0000000000000086 000000009b7de47d ffff88017a403de8 ffffffff813f8743
[    0.552706]  ffffffff81ca4618 ffff88017a403e80 ffff88017a403e70 ffffffff8118d367
[    0.554481]  ffff880100000010 ffff88017a403e80 ffff88017a403e18 000000009b7de47d
[    0.556229] Call Trace:
[    0.557931]  [<ffffffff813f8743>] dump_stack+0x63/0x90
[    0.559674]  [<ffffffff8118d367>] panic+0xd3/0x215
[    0.561400]  [<ffffffff81f5e576>] mount_block_root+0x201/0x294
[    0.563126]  [<ffffffff81f5e66e>] mount_root+0x65/0x68
[    0.564842]  [<ffffffff81f5e7ab>] prepare_namespace+0x13a/0x172
[    0.566557]  [<ffffffff81f5e21b>] kernel_init_freeable+0x1e9/0x212
[    0.568263]  [<ffffffff8182ff40>] ? rest_init+0x80/0x80
[    0.569959]  [<ffffffff8182ff4e>] kernel_init+0xe/0xe0
[    0.571625]  [<ffffffff8183ca0f>] ret_from_fork+0x3f/0x70
[    0.573263]  [<ffffffff8182ff40>] ? rest_init+0x80/0x80
[    0.574951] Kernel Offset: disabled
[    0.576541] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I am running the following command in my backup script:

rsync -ravv user@serverprod:/home/user/sites/main_site/backup/*.zip /space/backup/main_site/

Crontab:

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8
*       20      *       *       1-5     python /root/scripts/backup/backup.py -S -F main_site

I run into a issue every time rsync runs in crontab, but if I try to run it manually, I see no problem at all. I run as root in both cases.

Error:

rsync: mkstemp "/space/backup/main_site/.main_site_2016_01_29_132442250748_a82abb7e57f88c2afedb2e00c022f935c470b9e1_backup.zip.I3kVYl" failed: No such file or directory (2)

Now have in mind that main_site_2016_01_29_132442250748_a82abb7e57f88c2afedb2e00c022f935c470b9e1_backup is an expected file name. However, what comes before it, . and after .I3kVYl are not. I guess this must be temporary files the command creates in order to perform its operations. And the question is: why this error?

I am using Ubuntu server 14.04.4.

After running sudo apt-get -f install command at terminal and downloaded about 351 MB of fixes, I restarted Ubuntu 16.04 OS, but after selecting "Ubuntu" From Windows Boot Menu (Default OS: Windows 10) and then selecting Ubuntu from the GRUB boot menu, screen hanged at purple-orange wallpaper - one which is shown in GRUB menu, something like this image of the GRUB boot menu and the Caps lock key was blinking continuously.

I restarted by holding power key for 5 seconds and then again selected Ubuntu from Windows Boot Loader and selected Advanced Options from the GRUB menu and then Recovery mode (I don't know what's written after that) and after in DOS-like screen after all the commands were loaded automatically, this error was shown:

End Kernel Panic - not synced Requested init/sbin/upstart failed (error-2)

Specs:

Manufacturer:            HP
Model:                   G72-b66US Notebook
Processor:               Intel Core i3 CPU M 370 @ 2.40GHz 2.40 GHz
Installed memory (RAM):  4.00 GB (3.80 GB usable)
System type:             64-bit Operating System, x64-based processor
Pen and Touch:           No Pen or Touch Input is available for this Display

When I want to configure instants messaging, for some applications like Office365 lync and Telegram, I receive this error:

This IM Account cannot be created - 
a Telepathy Connection Manager named 'morse' is missing or 
it cannot handle protocol 'telegram'. 
Please try installing morse with your package manager.

Here are the specs for my desktop:

• Ubuntu 14.04 and Windows 7
• HP Pavilion p6000, AMD64

Here are the problem details:

• Kernel panic error (Ubuntu) and Blue Screen of Death (Windows)
• Computer doesn't start up at all sometimes (it powers on but does not boot).
• Standby sometimes doesn't awake.
• Keyboard and mouse freeze.
• I get a black screen at boot time with the following boot messages.

[   25.646903] task: ffff8800b6f96000 ti: ffff8800bdcca000 task.ti: ffff8800bdcca000
[   25.646910] RIP: 0010:[<ffffffff81185272>]  [<ffffffff81185272>] unlink_anon_vmas+0x52/0x1b0
[   25.646911] RSP: 0018:ffff8800bdccbd38  EFLAGS: 00010287
[   25.646911] RAX: 0000000000000000 RBX: ffff8800bbafbc00 RCX: 0000000000000000
[   25.646912] RDX: 00003461000236a2 RSI: ffff880012548230 RDI: ffff880012548200
[   25.646913] RBP: ffff8800bdccbd60 R08: 00007f5e32ec0000 R09: ffff8800b6b538a1
[   25.646913] R10: ffff880012548220 R11: ffffea00033ef7c0 R12: 00003461000236a2
[   25.646914] R13: ffff880012548230 R14: ffff8800125480e8 R15: 00174e0000000000
[   25.646915] FS:  00007f5e35635840(0000) GS:ffff88012f400000(0000) knlGS:0000000000000000
[   25.646916] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   25.646916] CR2: 00007f5e34464c20 CR3: 00000000b67e5000 CR4: 00000000000007e0
[   25.646918] Stack:
[   25.646923]  ffff8800b651cb00 ffff8800b651c338 ffff8800b651cc00 00007f5e32ec0000
[   25.646924]  0000000000000000 ffff8800bdccbe90 ffff8800b651cc00 000000000bdebc00
[   25.646925]  00007f5e31f25d50 0000000000000000 ffff8800bdccbd78 ffffffff81175418
[   25.646926] Call Trace:
[   25.646931]  [<ffffffff81175418>] free_pgtables+0xa8/0x120
[   25.646933]  [<ffffffff8118067b>] exit_mmap+0xcb/0x170
[   25.646935]  [<ffffffff8106482c>] mmput+0x5c/0x120
[   25.646936]  [<ffffffff81069c7c>] do_exit+0x2bc/0xa50
[   25.646938]  [<ffffffff8106a48f>] do_group_exit+0x3f/0xa0
[   25.646939]  [<ffffffff8106a504>] SyS_exit_group+0x14/0x20
[   25.646941]  [<ffffffff8172efad>] system_call_fastpath+0x1a/0x1f
[   25.646942] Code: 48 8d 4b 10 48 39 c1 48 8d 50 f0 4c 8d 66 f0 0f 84 21 01 00 00 45 31 ed eb 0c 66 0f 1f 44 00 00 4c 89 e2 49 89 d4 4c 8b 7b 08 <4d> 8b 37 4d 39 f5 74 15 4d 8
[   25.646957] RIP  [<ffffffff81185272>] unlink_anon_vmas+0x52/0x1b0
[   25.646958]  RSP <ffff8800bdccbd38>
[   25.646960] ---[ end trace 5fb86019f1cacbf7 ]---
[   25.646961] Fixing recursive fault but reboot is needed!
[   25.650357] BUG: Bad rss-counter state mm:ffff8800b67e5300 idx:1 val:2
[   25.958505] ------------[ cut here ]------------
[   25.958353] WARNING: CPU: 1 PID: 1480 at /build/buildd/linux-3.13.0/mm/mmap.c:2736 exit_mmap+0x16b/0x170()
[   25.958983] Modules linked in: hmep rfcomm bluetooth binfmt_misc snd_hda_codec_hdmi snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer ttm drm_kms_helper smi drm soundcore i2c_algo_bit mac_hid parport_pc ppdev lp parport hid_generic usbhid hid usb_storage psmouse ahci r8169 libahci mii
[   25.963875] CPU: 1 PID: 1480 Comm: apport Tainted: G      D      3.13.0-35-generic #63-Ubuntu
[   25.965265] Hardware name: Hewlett-Packard p6655nl/2A99, BIOS 6.10 05/07/2010
[   25.966660]  0000000000000000 ffff8800bdccbc60 ffffffff8171e569 0000000000000000
[   25.968064]  ffff8800bdccbc98 ffffffff8106733a ffff8800b651cc00 0000000000000000
[   25.969464]  ffff8800b651cc00 00007f5e32ec0000 ffff8800bdccbca8 ffffffff8106744c
[   25.970864] Call Trace:
[   25.972256]  [<ffffffff8171e569>] dump_stack+0x45/0x56
[   25.973667]  [<ffffffff8106733a>] warn_slowpath_common+0x7a/0xa0
[   25.975141]  [<ffffffff8106744c>] warn_slowpath_null+0x1c/0x20
[   25.976540]  [<ffffffff8118071b>] exit_mmap+0x16b/0x170
[   25.977941]  [<ffffffff8106482c>] mmput+0x5c/0x120
[   25.979343]  [<ffffffff811c3a6b>] flush_old_exec+0x41b/0x6b0
[   25.980752]  [<ffffffff81214618>] load_elf_binary+0x318/0x10b0
[   25.982161]  [<ffffffff811c3213>] km_get_action+0x23/0x30
[   25.983563]  [<ffffffff81341e12>] process_measurement+0x1a2/0x2c0
[   25.984966]  [<ffffffff811c35ff>] search_binary_handler+0xdf/0x2b0
[   25.986327]  [<ffffffff811c47a3>] do_execve_common.isra.22+0x5a7/0x7c0
[   25.987647]  [<ffffffff811c4c16>] SyS_execve+0x36/0x50
[   25.988919]  [<ffffffff8172f599>] stub_execve+0x69/0xa0
[   25.990164] ---[ end trace 5fb86019f1cacbf8 ]---

I have ASUS UL50Vt with nvidia optimus hybrid graphics (GeForce 210M). I recently installed ubuntu 12.04, and in Details app it was showing me, that I am on Intel video driver. So, I installed bumblebee and after reboot, Details showed "VESA: GT218 Board - 0698a740" As VESA differs from NVIDIA, I uninstalled bumblebee, but bug hasn't gone :(

Now my Xorg.0.log contains:

cat /var/log/Xorg.0.log | grep nvidia
[    12.616] (II) LoadModule: "nvidia"
[    12.634] (WW) Warning, couldn't open module nvidia
[    12.634] (II) UnloadModule: "nvidia"
[    12.634] (II) Unloading nvidia
[    12.634] (EE) Failed to load module "nvidia" (module does not exist, 0)
[    12.634] (==) Matched nvidia as autoconfigured driver 0
[    12.634] (II) LoadModule: "nvidia"
[    12.634] (WW) Warning, couldn't open module nvidia
[    12.634] (II) UnloadModule: "nvidia"
[    12.634] (II) Unloading nvidia
[    12.634] (EE) Failed to load module "nvidia" (module does not exist, 0)

Additional drivers says, that NVIDIA is activated but not currently in use:

jockey-text --list | grep nvidia
kmod:nvidia_current - nvidia_current (Proprietary, Disabled, Not in use)
kmod:nvidia_current_updates - nvidia_current_updates (Proprietary, Enabled, Not in     use)
kmod:nvidia_experimental_304 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use)
kmod:nvidia_experimental_310 - Experimental NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use)

NVIDIA X Server Settings writes on start:

You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run nvidia-xconfig as root), and restart the X server.

Suggested by https://askubuntu.com/a/121612/165811

sudo apt-get install linux-headers-`uname -r`
sudo dpkg-reconfigure nvidia-current
sudo nvidia-xconfig
sudo reboot

does not change anything. I'm still on fallback VESA driver. Resolution is 1280x768 instead of 1366x768.

How can I find out why nvidia-current fails to load nvidia module, which, I believe exists:

modprobe -l | grep nvidia
kernel/drivers/video/nvidia/nvidiafb.ko
kernel/drivers/net/ethernet/nvidia/forcedeth.ko
updates/dkms/nvidia_current.ko
updates/dkms/nvidia_current_updates.ko
updates/dkms/nvidia.ko

If it can help, here is my xorg.conf:

cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 304.88  (buildmeister@swio-display-x86-rhel47-06)  Wed Mar 27 15:32:58 PDT 2013


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Also, how can switch to my on-board Intel graphics, that served me well earlier?

UPDATE

lshw shows me, that my display is UNCLAIMED:

*-display UNCLAIMED
            description: VGA compatible controller
            product: GT218 [GeForce G210M]
            vendor: NVIDIA Corporation
            physical id: 0
            bus info: pci@0000:01:00.0
            version: a2
            width: 64 bits
            clock: 33MHz
            capabilities: pm msi pciexpress vga_controller bus_master cap_list
            configuration: latency=0
            resources: memory:fd000000-fdffffff memory:e0000000-efffffff memory:fa000000-fbffffff ioport:dc00(size=128) memory:f0000000-f007ffff

It looks like linux does not know about my integrated graphics at all:

lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce G210M] (rev a2)