I can not purge broken/old kernels:

sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-modules-nvidia-590-6.17.0-19-generic (6.17.0-19.19~24.04.2) ...
linux-image-nvidia-6.17.0-19-generic: constructing .ko files
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: warning: --package-metadata is empty, ignoring
/usr/bin/ld.bfd: cannot open linker script file /usr/src/linux-headers-6.17.0-19-generic/scripts/module.lds: No such file or directory
/usr/bin/ld.bfd: cannot open linker script file /usr/src/linux-headers-6.17.0-19-generic/scripts/module.lds: No such file or directory
/usr/bin/ld.bfd: cannot open linker script file /usr/src/linux-headers-6.17.0-19-generic/scripts/module.lds: No such file or directory
/usr/bin/ld.bfd: cannot open linker script file /usr/src/linux-headers-6.17.0-19-generic/scripts/module.lds: No such file or directory
/usr/bin/ld.bfd: cannot open linker script file /usr/src/linux-headers-6.17.0-19-generic/scripts/module.lds: No such file or directory
sha256sum: nvidia-drm.ko: No such file or directory
nvidia-drm.ko: FAILED open or read
sha256sum: nvidia-modeset.ko: No such file or directory
nvidia-modeset.ko: FAILED open or read
sha256sum: nvidia-peermem.ko: No such file or directory
nvidia-peermem.ko: FAILED open or read
sha256sum: nvidia-uvm.ko: No such file or directory
nvidia-uvm.ko: FAILED open or read
sha256sum: nvidia.ko: No such file or directory
nvidia.ko: FAILED open or read
sha256sum: WARNING: 5 listed files could not be read
dpkg: error processing package linux-modules-nvidia-590-6.17.0-19-generic (--configure):
 installed linux-modules-nvidia-590-6.17.0-19-generic package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-modules-nvidia-590-generic-hwe-24.04:
 linux-modules-nvidia-590-generic-hwe-24.04 depends on linux-modules-nvidia-590-6.17.0-19-generic (= 6.17.0-19.19~24.04.2); however:
  Package linux-modules-nvidia-590-6.17.0-19-generic is not configured yet.

dpkg: error processing package linux-modules-nvidia-590-generic-hwe-24.04 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 linux-modules-nvidia-590-6.17.0-19-generic
 linux-modules-nvidia-590-generic-hwe-24.04
E: Sub-process /usr/bin/dpkg returned an error code (1)

Any suggestions, please?

I am running

$ uname -r
6.14.0-37-generic

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:        24.04
Codename:       noble

Thanks in advance

Ubuntu Version:
Example: 22.04 LTS

Desktop Environment (if applicable):
Example: GNOME

Problem Description:

I cannot get write permissions on my Windows 11 share. I can access and read all files in Nautlilus, but when I try to copy a file TO the Windows 11 share, I get permission denied.

What I’ve Tried:

I have permissions open on the Win11 share and I can read and write on that share from another Windows machine, I just cannot write to that share from Linux. Not sure what config files in Linux I need to adjust to achieve writing permissions to this share. I am happy to post any config files I need to but am just not sure which ones need tweaking.

Appreciate any pointers on this subject. Thanks in advance.

I recently upgraded from Ubuntu 22.04 to 24.04. Cinnamon DE. Since the upgrade, reminders are overriding power management and keep the screen enabled well past the power management display inactivity timeout. I understand these reminders are generated by the Evolution service. I like the reminders, I just don't want it to override power management. This didn't happen in 22.04, power management worked fine. Is there a way to fix this or am I stuck with either getting rid of the reminders altogether or remembering to turn off the monitor, which I don't?

I am not sure if this is a software or hardware issue.

On my Ubuntu 24.04.4, my capslock button is showing as activated (led on), when it is inactive and vice versa. Could this be a software issue and if so, how would I fix it?

I'm running Ubuntu 24.04.4 LTS on my Dell XPS-13. As I have very limited knowledge on configuring firewalls, I've been using the Default Configuration of UFW (Deny all incoming traffic, Allow all outgoing traffic). However, I am running some closed-source programs which I do not trust not to call home. Therefore, I would appreciate the ability of OpenSnitch to monitor outgoing traffic on a per-App basis while retaining the security of a traditional Firewall.

However, I have read conflicting reports on whether or not OpenSnitch can adequately handle incoming traffic in the same way UFW does. Since, as mentioned, I am not well versed on configuring Firewalls, I would like to avoid creating more vulnerabilities than I am solving. So my question is: Is OpenSnitch a good solution for my use-case?

I am using Ubuntu Studio 24.04. When I try to open my DAW, about 50% of the time it starts to open, but then freezes. I have to use the System Monitor to quit the application. Then I start it again and it starts up OK.

I wonder if anyone knows why this might be happening. I sometimes have Firefox open while opening the DAW. I wonder if it might be a Pipewire thing. I have tried keeping Firefox closed before opening the DAW, but it still happens.

I have an old MacBook and I installed Ubuntu 22.04 LTS on it. The problem is the internal keyboard has some problems and some keys press by themselves. I have an external keyboard and mouse that are functioning well enough so I have no problem disabling the internal keyboard. How can I do this and make it persist through restarts?

I just installed Ubuntu 24.04 LTS succesfully on a PC, and it runs nice and smooth...

When finishing installation I chose encryption of the disk (LMV and encryption), and I agreed on a encryption password. I got the password notet, so no problem there.

But it's a PC...

When I'm prompted for the password (please unlock /disk dm_crypt-0) , it is under boot-up and therefore before my blootooth keyboard is activated. For this reason I would like to unlock the disk permanently without a password.

How and where in the setup can I do so, if possible?

Thank you very much in advance.

Regards, Ole

Option to boot from usb missing from bios.

Which ever way i get to bios settings, there is no usb visible.

My install of Ubuntu did not go well and i now have no way of using the live usb [or any usb] to reinstall.

I have an old imac that was running mint ok. The error came after i tried to update. The

usb function was working ok till then.

I am still trying to get my old head around linux so please be gentle with me.

Thanks for any help

I enable it, but I can't access it through ssh.

I know I need to install ssh/sshd via apt install because I'm know `ssh/sshd`.

The GUI does not prompt me anything, this is a so bad design for new user.

I'm unable to connect to my local router IP (192.168.1.1). I'm connected to the internet and I can reach external servers. I tried to connect my local network file storage, but it's not showing in Nautilus. I've just installed Ubuntu 24.04.4 after corrupted BIOS.

Here is the output for 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
2: enp14s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group 57841 qlen 1000
    link/ether 54:04:a6:44:00:67 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.139/24 brd 192.168.1.255 scope global noprefixroute enp14s0
       valid_lft forever preferred_lft forever
3: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group 57841 qlen 1000
    link/ether 88:88:88:88:87:88 brd ff:ff:ff:ff:ff:ff
    altname enp0s25
6: nordlynx: <POINTOPOINT,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none 
    inet 10.5.0.2/16 scope global nordlynx
       valid_lft forever preferred_lft forever

IP route:

default via 192.168.1.1 dev enp14s0 proto dhcp src 192.168.1.139 metric 20100 
10.5.0.0/16 dev nordlynx proto kernel scope link src 10.5.0.2 
192.168.1.0/24 dev enp14s0 proto kernel scope link src 192.168.1.139 metric 100 
nmap -sp 192.168.1.1
Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-03-15 08:43 GMT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.00 seconds

I am very new to Ubuntu and really don't understand much of how this all works, so I apologize if this is a stupid question. I used to be able to back up my files to my external hard drive, but then one day I plugged it in and it said I didn't have permission to modify the files. When I looked online, most solutions suggest this issue is something to do with connecting the hard drive to a windows laptop, which is not the case. The hard drive was used to back up a MacBook in the past, but not recently. The Ubuntu is the only system it has been connected to in months. I've seen some suggestions involving sudo mount but I don't what specifically to do with that and I don't want to screw things up further. I tried lsblk -f but I have no clue what the output means. Here it is in case it's helpful:

$ lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                    0   100% /snap/audacity/1212
loop1
     squash 4.0                                                    0   100% /snap/audacity/1208
loop2
     squash 4.0                                                    0   100% /snap/bare/5
loop3
     squash 4.0                                                    0   100% /snap/thunderbird/1017
loop4
     squash 4.0                                                    0   100% /snap/brave/603
loop5
     squash 4.0                                                    0   100% /snap/brave/604
loop6
     squash 4.0                                                    0   100% /snap/chromium/3369
loop7
     squash 4.0                                                    0   100% /snap/core/17247
loop8
     squash 4.0                                                    0   100% /snap/core/17272
loop9
     squash 4.0                                                    0   100% /snap/core18/2979
loop10
     squash 4.0                                                    0   100% /snap/core18/2999
loop11
     squash 4.0                                                    0   100% /snap/core20/2717
loop12
     squash 4.0                                                    0   100% /snap/core20/2686
loop13
     squash 4.0                                                    0   100% /snap/core22/2339
loop14
     squash 4.0                                                    0   100% /snap/chromium/3375
loop15
     squash 4.0                                                    0   100% /snap/core22/2292
loop16
     squash 4.0                                                    0   100% /snap/core24/1349
loop17
     squash 4.0                                                    0   100% /snap/cups/1142
loop18
     squash 4.0                                                    0   100% /snap/cups/1146
loop19
     squash 4.0                                                    0   100% /snap/digikam/100
loop20
     squash 4.0                                                    0   100% /snap/digikam/101
loop21
     squash 4.0                                                    0   100% /snap/enpass/12
loop22
     squash 4.0                                                    0   100% /snap/ffmpeg-2204/122
loop23
     squash 4.0                                                    0   100% /snap/ffmpeg-2204/126
loop24
     squash 4.0                                                    0   100% /snap/ffmpeg-2404/103
loop25
     squash 4.0                                                    0   100% /snap/ffmpeg-2404/108
loop26
     squash 4.0                                                    0   100% /snap/firefox/7836
loop27
     squash 4.0                                                    0   100% /snap/firefox/7869
loop28
     squash 4.0                                                    0   100% /snap/gimp/550
loop29
     squash 4.0                                                    0   100% /snap/gimp/552
loop30
     squash 4.0                                                    0   100% /snap/gnome-3-28-1804/198
loop31
     squash 4.0                                                    0   100% /snap/gnome-3-34-1804/90
loop32
     squash 4.0                                                    0   100% /snap/gnome-3-34-1804/93
loop35
     squash 4.0                                                    0   100% /snap/gnome-42-2204/226
loop36
     squash 4.0                                                    0   100% /snap/gnome-42-2204/247
loop37
     squash 4.0                                                    0   100% /snap/gnome-46-2404/145
loop38
     squash 4.0                                                    0   100% /snap/gnome-46-2404/153
loop39
     squash 4.0                                                    0   100% /snap/gtk2-common-themes/13
loop40
     squash 4.0                                                    0   100% /snap/gtk-common-themes/1535
loop41
     squash 4.0                                                    0   100% /snap/kf5-5-108-qt-5-15-10-core22/5
loop42
     squash 4.0                                                    0   100% /snap/hunspell-dictionaries/21
loop43
     squash 4.0                                                    0   100% /snap/kf6-core22/42
loop44
     squash 4.0                                                    0   100% /snap/kf6-core22/43
loop45
     squash 4.0                                                    0   100% /snap/kf6-core24/34
loop46
     squash 4.0                                                    0   100% /snap/kf6-core24/36
loop47
     squash 4.0                                                    0   100% /snap/mesa-2404/1165
loop48
     squash 4.0                                                    0   100% /snap/mesa-2404/912
loop49
     squash 4.0                                                    0   100% /snap/qt-common-themes/8
loop50
     squash 4.0                                                    0   100% /snap/qt-common-themes/10
loop51
     squash 4.0                                                    0   100% /snap/snap-store/1113
loop52
     squash 4.0                                                    0   100% /snap/snap-store/1216
loop53
     squash 4.0                                                    0   100% /snap/snapd/25577
loop54
     squash 4.0                                                    0   100% /snap/snapd/25935
loop55
     squash 4.0                                                    0   100% /snap/snapd-desktop-integration/315
loop56
     squash 4.0                                                    0   100% /snap/snapd-desktop-integration/343
loop57
     squash 4.0                                                    0   100% /snap/teams-for-linux/1392
loop58
     squash 4.0                                                    0   100% /snap/teams-for-linux/1499
loop59
     squash 4.0                                                    0   100% /snap/vlc/3777
loop60
     squash 4.0                                                    0   100% /snap/core24/1499
loop61
     squash 4.0                                                    0   100% /snap/firmware-updater/216
sda                                                                         
├─sda1
│    vfat   FAT32       3491-A7AE                             459.3M    10% /boot/efi
└─sda2
     ext4   1.0         7abab72c-e0df-4b5c-aead-f72af7cb0ff7   56.4G    70% /var/snap/firefox/common/host-hunspell

LaCie file permissions:

How do I begin to solve this issue?

EDIT: Here is the output to sudo fdisk -l && udisksctl status

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 611.95 MiB, 641679360 bytes, 1253280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 617.38 MiB, 647364608 bytes, 1264384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 180.89 MiB, 189681664 bytes, 370472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 197.32 MiB, 206905344 bytes, 404112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 180.98 MiB, 189771776 bytes, 370648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 104.23 MiB, 109289472 bytes, 213456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC  WDS250G2B0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D13A4908-1868-4D16-94EA-7FC7C69C0EA6

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624 488396799 487346176 232.4G Linux filesystem


Disk /dev/loop8: 104.98 MiB, 110080000 bytes, 215000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 55.49 MiB, 58187776 bytes, 113648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 55.49 MiB, 58183680 bytes, 113640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 63.77 MiB, 66871296 bytes, 130608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 63.77 MiB, 66871296 bytes, 130608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 73.95 MiB, 77545472 bytes, 151456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 73.96 MiB, 77549568 bytes, 151464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 66.85 MiB, 70098944 bytes, 136912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop16: 66.83 MiB, 70078464 bytes, 136872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop17: 48.82 MiB, 51187712 bytes, 99976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop18: 47.59 MiB, 49897472 bytes, 97456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop19: 226.74 MiB, 237752320 bytes, 464360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop20: 222.66 MiB, 233480192 bytes, 456016 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop21: 32.39 MiB, 33964032 bytes, 66336 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop22: 62.16 MiB, 65175552 bytes, 127296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop23: 62.16 MiB, 65175552 bytes, 127296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop24: 82.13 MiB, 86114304 bytes, 168192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop25: 96.42 MiB, 101101568 bytes, 197464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop26: 254.56 MiB, 266928128 bytes, 521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop27: 251.64 MiB, 263868416 bytes, 515368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop28: 16.45 MiB, 17244160 bytes, 33680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop30: 137.23 MiB, 143896576 bytes, 281048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop31: 164.82 MiB, 172830720 bytes, 337560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop32: 218.39 MiB, 228999168 bytes, 447264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop33: 218.39 MiB, 228999168 bytes, 447264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop34: 531.38 MiB, 557187072 bytes, 1088256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop35: 516.2 MiB, 541278208 bytes, 1057184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop36: 606.08 MiB, 635518976 bytes, 1241248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop37: 669.79 MiB, 702320640 bytes, 1371720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop38: 140 KiB, 143360 bytes, 280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop39: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop40: 450.15 MiB, 472018944 bytes, 921912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop41: 32.07 MiB, 33632256 bytes, 65688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop42: 2.03 GiB, 2182340608 bytes, 4262384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop43: 1.3 GiB, 1391226880 bytes, 2717240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop44: 2.02 GiB, 2166636544 bytes, 4231712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop45: 1.41 GiB, 1515048960 bytes, 2959080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop46: 394.98 MiB, 414167040 bytes, 808920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop47: 290.77 MiB, 304898048 bytes, 595504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop48: 188.02 MiB, 197152768 bytes, 385064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop49: 188.02 MiB, 197152768 bytes, 385064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop50: 12.93 MiB, 13553664 bytes, 26472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop51: 12.2 MiB, 12791808 bytes, 24984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop52: 50.93 MiB, 53399552 bytes, 104296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop53: 48.09 MiB, 50421760 bytes, 98480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop55: 576 KiB, 589824 bytes, 1152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop54: 139.91 MiB, 146702336 bytes, 286528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop56: 576 KiB, 589824 bytes, 1152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop57: 107.25 MiB, 112459776 bytes, 219648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop58: 227.47 MiB, 238518272 bytes, 465856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop59: 321.1 MiB, 336699392 bytes, 657616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop60: 107.28 MiB, 112488448 bytes, 219704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop61: 197.3 MiB, 206888960 bytes, 404080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
MODEL                     REVISION  SERIAL               DEVICE
--------------------------------------------------------------------------
WDC  WDS250G2B0A-00SM50   401000WD  19197F801218         sda 

I'm on Ubuntu 22.04. Only a few months ago, I had Webmin installed, but I had to remove to free up space. When I try to install now, I get an error message about an unmet dependency:

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:
 libauthen-pam-perl : Depends: perlapi-5.28.0
E: Unable to correct problems, you have held broken packages.

Trying to install perlapi-5.28.0 with APT told me that it couldn't be found or sometihing. I found this Launchpad page that says the package I can download from there provides perlapi-5.28.0. I downloaded it and tried intalling it manually. I got some errors, so I reinstalled perlapi-5.34.0 and now I'm getting this on trying to install Webmin:

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:
 libauthen-pam-perl : Depends: perlapi-5.28.0
E: Unable to correct problems, you have held broken packages.

Given that I had Webmin installed not too long, this should be working. How do I fix it?

Update: This is the output of apt policy libauthen-pam-perl:

libauthen-pam-perl:
  Installed: (none)
  Candidate: 0.16-3+b6
  Version table:
     0.16-3+b6 500
        500 http://archive.debian.org/debian buster/main amd64 Packages
     0.16-3build9 500
        500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

When I see a stable, well-accepted package like coreutils get removed, my initial reaction is something of shock. However, I know the danger of "speaking without knowledge" to use the biblical wording, and that the Ubuntu people know way more about this than I do, but:

Why did the Ubuntu team want to change from coreutils to uutils?

I know there's a big push for "safer" languages like rust right now, is simply that the reason? or is there a more complex reason? It seems like a mature project like coreutils would no longer have any memory leaks or similar errors that might make the Ubuntu team have second thoughts about using it. So, why?

Just a note for those who don't know, this is not in an LTS release yet, just in intern releases.

Windows have been moving underneath the dock (see attached photo).

I can consistently reproduce the effect by having a maximized window open, locking the screen, and then unlocking it.

Example of the dock overlapping with firefox after locking and unlocking my system

I am using Ubuntu 22.04.3 LTS and Gnome version 42.9. If any other information is helpful please let me know.

I understand this is a duplicate issue but the others have no solution and no steps to reproduce. Without reputation I can't comment steps to reproduce on these posts, so I'm making my own.

I am using Ubuntu 23.04 and found that the desktop dock will overlay on windows, see image below:

The dock bar is displayed on top of bash window! Note that:

1. I have switched OFF dock auto-hiding.
2. Whenever an application is launched, or I manually maximize its window, the behavior is always correct, i.e., the maximized window will be aligned to the right of the dock bar edge
3. If I switch over applications, sometime already maximized window will extend below the dock bar! I don't know when this happens, but it is very common, any maximized window will behave like this!

I think it is a bug, unless there is a hidden GNOME setting to control this behavior?

I know hard links can't cross filesystems, but trying to link files via bind mounts that physically live on the same filesystem fails as well. I detailed things below to visualize it better, but the TLDR of my question is why is ln treating the mounted directories as though they live separately?

Basically, copying files into a share folder would be best-served with hardlinks so I'm not duplicating space:

mymedia/
├─ share/
│  ├─ pics/
│  │  ├─ pic2.tif
│  ├─ vids/
│  │  ├─ vid1.mov
├─ homevid/
│  ├─ vid1.mov
│  ├─ vid2.mov
│  ├─ vid3.mov
├─ homepic/
│  ├─ pic1.tif
│  ├─ pic2.tif
├─ training/

mymedia/share is on one drive (Media1), whereas homepic is on Media2 and homevid on Media3. The two folders in share are mounted from Media2/Media3. This is from fstab:

/dev/disk/by-uuid/UUID_1 /mnt/Media1 auto 0 0  
/dev/disk/by-uuid/UUID_2 /mnt/Media2 auto 0 0  
/dev/disk/by-uuid/UUID_3 /mnt/Media3 auto 0 0  
/mnt/Media1 /mnt/mymedia none bind 
/mnt/Media2/homepic /mnt/mymedia/homepic none bind
/mnt/Media2/share /mnt/mymedia/share/pics none bind
/mnt/Media3/homevid /mnt/mymedia/homevid none bind
/mnt/Media3/share /mnt/mymedia/share/vids none bind

I can create the link while using the "real" path, like so: ln /mnt/Media2/homepic/pic2.tif /mnt/Media2/share/, and see the new file in both directories; stat confirms the inode is the same for the files, as well as same device:

Unfortunately, using the bind mounts would be way better for my workflow (this fails): ln /mnt/mymedia/homepic/pic1.tif /mnt/mymedia/share/pics/pic2.tif

What am I missing?

I run into a well-known problem that was actually already widely discussed on the web. However, I unfortunately could not solve the problem yet.

I recently replaced the Wifi network adapter into a new one, Intel(R) Wi-Fi 6 AX210 160MHz, in a Dell Rugged 5414 laptop, several years old.

I'm still fairly new to Linux/Ubuntu and appreciate any assistance.

root@laptop-02# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

The network adapter was correctly recognized by the system:

root@laptop-02# lspci -knn | grep Net -A3
01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz [8086:0024]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

However, the system shows the WLAN function as switched off. Wireless networks are not displayed. The function is greyed out in Ubuntu.

root@laptop-02# sudo iwconfig
lo        no wireless extensions.
enp0s31f6  no wireless extensions.
enx10050197f9a6  no wireless extensions.
wwan0     no wireless extensions.
wlp1s0    no wireless extensions.

The first errors are displayed here:

• reporting RF_KILL (radio disabled)
• Direct firmware load for iwlwifi-ty-a0-gf-a0-73.ucode failed with error -2

root@laptop-02:/usr/lib/firmware# dmesg | grep wifi
[    4.914540] Loading modules backported from iwlwifi
[    4.914541] iwlwifi-stack-public:master:9858:4c7cba27
[    4.997046] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    5.003663] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-73.ucode failed with error -2
[    5.003684] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2
[    5.009461] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[    5.009490] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[    5.010086] iwlwifi 0000:01:00.0: loaded firmware version 71.058653f6.0 ty-a0-gf-a0-71.ucode op_mode iwlmvm
[    5.109985] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[    5.116435] iwlwifi 0000:01:00.0: reporting RF_KILL (radio disabled)
[    5.288652] iwlwifi 0000:01:00.0: loaded PNVM version 05a8dfca
[    5.304238] iwlwifi 0000:01:00.0: Detected RF GF, rfid=0x10d000
[    5.377673] iwlwifi 0000:01:00.0: base HW address: 8c:f8:c5:3b:dc:c4
[    6.498280] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[ 3575.564341] Loading modules backported from iwlwifi
[ 3575.564343] iwlwifi-stack-public:master:9858:4c7cba27
[ 3575.610167] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-73.ucode failed with error -2
[ 3575.610195] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-72.ucode failed with error -2
[ 3575.610697] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[ 3575.610719] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[ 3575.611123] iwlwifi 0000:01:00.0: loaded firmware version 71.058653f6.0 ty-a0-gf-a0-71.ucode op_mode iwlmvm
[ 3575.656549] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 3575.663397] iwlwifi 0000:01:00.0: reporting RF_KILL (radio disabled)
[ 3575.811807] iwlwifi 0000:01:00.0: loaded PNVM version 05a8dfca
[ 3575.823466] iwlwifi 0000:01:00.0: Detected RF GF, rfid=0x10d000
[ 3575.894946] iwlwifi 0000:01:00.0: base HW address: 8c:f8:c5:3b:dc:c4
[ 3575.949398] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0

The driver seems to be ready, but it still need to get the firmware for the chip, that doesn't work:

root@laptop-02# sudo dkms install backport-iwlwifi/8400

Kernel preparation unnecessary for this kernel. Skipping...

Building module:
cleaning build area...
'make' -j4 KLIB=/lib/modules/5.15.0-46-generic...(bad exit status: 2)
ERROR (dkms apport): binary package for backport-iwlwifi: 8400 not found
Error! Bad return status for module build on kernel: 5.15.0-46-generic (x86_64)
Consult /var/lib/dkms/backport-iwlwifi/8400/build/make.log for more information.

I downloaded drivers from here: https://www.intel.de/content/www/de/de/support/articles/000005511/wireless.html

I mainly followed this post in the procedure (answer 3): Ubuntu 20.04 LTS driver Intel Wi-Fi 6E AX210 160MHz

Many thanks to everybody for any support. Please keep in mind, I'm still a beginner with Linux ;)

I just installed Ubuntu Budgie 22.04 on my new ASUS Vivobook OLED S15 S3502 (2022). The keyboard is not working while the touchpad is working. But the external keyboard is working fine.

My grub entry; GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX=""

How can I make it work fine?

I have Ubuntu 22.04 with

$ lspci | grep VG
08:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1)

Today the resolution of the display was forced to 1024x728 (refresh rate 76 Hz) with no options. I am getting the error xrandr: Failed to get size of gamma for output default, so I tried the solutions of these posts (1), (2), (3). But nothing has changed.

How can I force a resolution of 1920 x 1080? Or let the system recognize the display automatically as before?

Thank you

For the life of me I can't get that network icon back. I have restarted the X server, ran "nm-applet" and restarted NetworkManager. Any ideas? I can provide output for commands if needed.

i've just switched from XP to ubuntu, and i've made some partitions, like efi, /home, swap, and root. For me it is pretty good OS, but when i checked the partition, i noticed that the swap partition on the off condition, so i tried to activate it, and then this message showed up ; swapon failed : device or resource busy. So, what does it mean by that? hope can find help for this question

I was having problems answering a call in Skype, no answer button, and so I decided to reinstall Skype from scratch.

This is Xubuntu with lsb-release showing

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

Ran this morning

apt-get update
apt-get dist-upgrade
sudo apt-get autoremove --purge skypeforlinux

Get Skype from https://www.skype.com/en/get-skype/

Downloaded skypeforlinux-64.deb

sudo apt install ./skypeforlinux-64.deb

Started Skype from the menu.

Obtained the Skype window outline but no body, just what was showing under where the body should be. It just hangs there and I have to kill the pid to close it.

Gnome-boxes begins to start then crashes on my account. However, I created another account and boxes loaded fine. I tried to delete the files in ~/.config and ~/.share but no luck.

When I launch from the CL I get the following error:

(gnome-boxes:13410): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed
Segmentation fault (core dumped)\

Update: gnome-boxes --checks results in:

(gnome-boxes:2803): Boxes-WARNING **: util-app.vala:270: Failed to execute child process ?virsh? (No such file or directory)

(gnome-boxes:2803): Boxes-WARNING **: util-app.vala:250: Failed to execute child process ?restorecon? (No such file or directory)
• The CPU is capable of virtualization: yes
• The KVM module is loaded: yes
• Libvirt KVM guest available: no
• Boxes storage pool available: no
    Could not get “gnome-boxes” storage pool information from libvirt. Make sure “virsh -c qemu:///session pool-dumpxml gnome-boxes” is working.
• The SELinux context is default: no

Report bugs to <https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>.
Boxes home page: <https://wiki.gnome.org/Apps/Boxes>.`

Thanks in advance for any advice how to correct this problem.

I'm running Ubuntu 16.04 (the only OS on my machine), and I've recently run into some strange behaviour when booting. The GRUB menu comes up normally, but if I try to do a normal boot (either selecting the default option or letting it time out) I just get a black screen with a cursor in the upper left. If I type anything it appears on the screen, but I'm not getting a login prompt or a shell or anything like that.

If I use the GRUB menu to select "recovery mode", then just choose "resume" from the recovery menu, it works properly.

I don't reboot all that often, so it's hard to pinpoint exactly what update caused the problem. Obviously, it's just a minor nuisance, but I'd like to report it as a bug - but I have no idea if it's a kernel bug, a GRUB bug, or something else.

Can anybody help me understand what's going on here, and whom I should contact about it?

sudo chown proftpd /etc/proftpd/ftpd.passwd sudo chmod o-r /etc/proftpd/ftpd.passwd sudo service proftpd start

At this stage proFTPd is running but I am unable to log in,

sudo chmod o+r /etc/proftpd/ftpd.passwd

And now I can log in to FTP However if I change the permission on the ftpd.passwd to sudo chmod o+r /etc/proftpd/ftpd.passwd before I start the proFTPd , the proFTPd won't start and will give me the error:

mod_auth_file/1.0: unable to use world-readable AuthUserFile '/etc/proftpd/ftpd.passwd': Operation not permitted Fatal: AuthUserFile: unable to use /etc/proftpd/ftpd.passwd: Operation not permitted on line 36 of '/etc/proftpd/proftpd.conf'

What my suspicion is that proFTPd is not a member of a specific group, if I execute:

groups proftpd

proftpd : nogroup is the reply.

Any ideas?

What is the difference between:

sudo chown $USER:$USER

and

sudo chown $USER

Why is it 2 times? Is the one user wrong? When I look at permissions with namei -l, I often see things like root root or proxy proxy.

Why does the owner have to be defined and listed 2 times?

I'm using Ubuntu 12.04 and I've installed Viber and I'm struggling for days with this problem. My Viber icon is located at the top left corner, few milimeters to the right from the dash icon. I have tried to whitelist it on desktop enviroment variables, it wroked with Skype, but not with Viber. Please help.

I used to work for a long time with ubuntu 10.10 and I changed to a recent machine so I had to move to Ubuntu 13.04. One feature I'm now missing is the auto umount of usb drives. I've not been able to find easy info on internet.

I just installed Ubuntu 13.04 on my new Lenovo Ideapad using the live USB. My problem is that I cannot connect to my wireless network. My wireless adapter is recognized as Atheros Communications Inc AR9285 Wireless network adapter.