Several questions have been asked on this topic but none solved my issue. System has been working fine for a long time. Shut it off for a few days and when I restarted it, I had several problems. The most obvious is that the settings function won't launch. Everything seems to more or less work ok although I no longer have audio. That's how I noticed that I could not launch settings. Any related command gives the below undefined symbol complaint. There was an identical question where the OP tried numerous things to fix this and none helped. No possible solutions were offered. I'd like to upgrade to 24.04.1 LTS but obviously don't want to do that until this is resolved.

Trying to launch settings from the GUI or CLI returns the following error:

symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2

I upgraded everything prior to posting this question.

This could well be a very easy fix. Hoping someone offers a solution.

gnome-control-center --verbose
gnome-control-center: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2

The following ran without error:

sudo apt install --reinstall gnome-control-center

locate gnome-control-center.desktop
/usr/share/applications/gnome-control-center.desktop

apt list -a libwebkit2gtk-4.0-37
Listing... Done
libwebkit2gtk-4.0-37/jammy-updates,jammy-security,now 2.44.3-0ubuntu0.22.04.1 amd64 [installed]
libwebkit2gtk-4.0-37/jammy 2.36.0-2ubuntu1 amd64

libwebkit2gtk-4.0-37/jammy-updates,jammy-security 2.44.3-0ubuntu0.22.04.1 i386
libwebkit2gtk-4.0-37/jammy 2.36.0-2ubuntu1 i386

One answer recommend the following which did not resolve my issue:

sudo add-apt-repository ppa:ubuntu-desktop/ppa

Gnome otherwise appears to be working fine.

Many related questions focus on the video driver as the culprit. This is the configuration I am running:

sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: /dev/fb0
       version: e7
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
       resources: irq:149 memory:c0000000-cfffffff memory:d0000000-d01fffff ioport:e000(size=256) memory:df500000-df53ffff memory:df540000-df55ffff
  *-display
       description: VGA compatible controller
       product: HD Graphics 530
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 06
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:148 memory:de000000-deffffff memory:b0000000-bfffffff ioport:f000(size=64) memory:c0000-dffff

I just upgraded my 22.04 LTS desktop to 24.04.1 LTS. The upgrade seemed to go fine. On the final reboot the desktop came up in console mode. The GUI never started. I saw no interesting errors in the syslog. To try to fix this I did a

sudo apt install gnome-shell

This caused the GUI to start on reboot but I totally hate this interface! The Wayland choice is no longer there. Just Ubuntu and Ubunti Xorg.

I don't know if this matters but the video is a RV730XT Radeon HD4670 PCI card

On further cursory inspection it appears that a LOT of apps are no longer there. Software & Updater and the legacy terminal shell to name just two. The printer queues all disappeared. Brasero won't run complaining about missing libraries. There is a LOT of software that was removed and not replaced!

I probably should have waited to do this upgrade but the release is now 24.04.1 indicating that it is a tested, shaken down, stable release. I received the popup asking if I wanted to upgrade to the latest LTS and I clicked upgrade.

This upgrade issued no errors yet has turned out to be a massive fail. The desktop is running but is completely unusable. I could really use some help here!

As observed in the comments, it seems that the update was massively incomplete. Uh, yeah...

So how do I fix this without having to do a clean install? I did try to repeat the upgrade but it responded that everything is up-to-date. What's needed, I think, is a method of re-installing this upgrade where all of the missing software will be installed. Is this possible?

Thanks in advance!

This question has been asked several times but no answers were posted.

Cannot turn on Bluetooth on Ubuntu 23.10 (Asus ROG ROG Flow X13 GV302XV) seemed like a great answer but didn't work in my case.

sudo dkms install btusb/4.1

failed at the end of the build. However, this answer was aimed at a problem with a USB BT connection. In my case, bluetooth is implemented on the mobo.

$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
     Active: active (running) since Fri 2024-02-16 21:38:23 PST; 1 day 21h ago
       Docs: man:bluetoothd(8)
   Main PID: 1905 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76903)
     Memory: 2.3M
        CPU: 172ms
     CGroup: /system.slice/bluetooth.service
             └─1905 /usr/lib/bluetooth/bluetoothd

Feb 18 17:30:50 Ubuntu bluetoothd[1905]: Endpoint unregistered: sender=:1.89 pa>
Feb 18 17:30:50 Ubuntu bluetoothd[1905]: Endpoint unregistered: sender=:1.89 pa>

Shows that the service is running ok. But.... there is no bluetooth icon in the top right status bar (as it is on my M8H machine using a BT dongle)

sudo lshw | grep blue -C 8 
configuration: driver=usbhid maxpower=500mA speed=12Mbit/s
              *-usb:1
                   description: Bluetooth wireless interface
                   product: Qualcomm Bluetooth 4.1
                   vendor: ASUSTek Computer, Inc.
                   physical id: 9
                   bus info: usb@1:9
                   version: 0.01
                   capabilities: bluetooth usb-2.01
                   configuration: driver=btusb maxpower=100mA speed=12Mbit/s
           *-usbhost:1
                product: xHCI Host Controller
                vendor: Linux 5.15.0-94-generic xhci-hcd
                physical id: 1
                bus info: usb@2
                logical name: usb2
                version: 5.15

Bluetooth has worked on this machine previously but that could have been when earlier versions of Ubuntu were installed.

The mobo specs are bt v4.0/3.0+HS on an Intel Z170 chipset.

The problem: In Ubuntu's BT settings, bluetooth is turned on and the devices search wheel is spinning but no devices are ever found. This is true even if I install a BT dongle. The desktop right beside it is an ASUS ROG M8H mobo with no integrated BT. With a dongle installed it immediately connects to selected BT devices. Both machines are running identical versions of Ubuntu.

ASUS has firmware for bt but only in Microsoft format. They are clear that they do not support *NIX but obviously there are many of us running Ubuntu on ROG machines without problems.

I'd like to be able to run just one speaker via BT on each desktop instead of having four speaker sets, one hardwired to each machine. Yes, I know I can only have the device paired to one PC at a time.

sudo dmesg|grep Blue
[165140.288091] Bluetooth: hci0: unexpected event for opcode 0x2005

bluetoothctl fires up but I don't understand enough about that tool to use it productively. Looks like it's working ok though. Just no devices are discovered (and yes, the wifi antenna is connected. The manual sort of implies that this is needed for BT)

$ hciconfig
hci0:   Type: Primary  Bus: USB
    BD Address: C8:FF:28:31:81:72  ACL MTU: 1024:8  SCO MTU: 50:8
    DOWN 
    RX bytes:13041 acl:0 sco:0 events:2012 errors:0
    TX bytes:17186 acl:0 sco:0 commands:1506 errors:0

As expected for an onboard BT capability

$ btmgmt info
Index list with 1 item
hci0:   Primary controller
    addr C8:FF:28:31:81:72 version 7 manufacturer 29 class 0x000000
    supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr hs le advertising secure-conn debug-keys privacy static-addr phy-configuration 
    current settings: ssp br/edr le secure-conn 
    name Ubuntu
    short name 

$ bluetoothctl list
Controller C8:FF:28:31:81:72 Ubuntu [default]

$ rfkill unblock all
frankie@Ubuntu:~$ hciconfig
hci0:   Type: Primary  Bus: USB
    BD Address: C8:FF:28:31:81:72  ACL MTU: 1024:8  SCO MTU: 50:8
    DOWN 
    RX bytes:13041 acl:0 sco:0 events:2012 errors:0
    TX bytes:17195 acl:0 sco:0 commands:1509 errors:0

frankie@Ubuntu:~$ bluetoothctl power on
Failed to set power on: org.bluez.Error.Busy
frankie@Ubuntu:~$ bluetoothctl scan on
Failed to start discovery: org.bluez.Error.NotReady

$ bluetoothctl
Agent registered
[CHG] Controller C8:FF:28:31:81:72 Pairable: yes

[bluetooth]# list
Controller C8:FF:28:31:81:72 Ubuntu [default]
[bluetooth]# show
Controller C8:FF:28:31:81:72 (public)
    Name: Ubuntu
    Alias: Ubuntu
    Class: 0x00000000
    Powered: no
    Discoverable: no
    DiscoverableTimeout: 0x00000000
    Pairable: yes
    UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
    UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
    UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
    UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
    UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
    UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
    UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
    UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
    UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
    UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
    UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
    UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
    UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
    UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
    UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
    UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
    Modalias: usb:v1D6Bp0246d0540
    Discovering: no
    Roles: central
    Roles: peripheral
Advertising Features:
    ActiveInstances: 0x00 (0)
    SupportedInstances: 0x05 (5)
    SupportedIncludes: tx-power
    SupportedIncludes: appearance
    SupportedIncludes: local-name
[bluetooth]# devices
[bluetooth]# power on
Failed to set power on: org.bluez.Error.Busy

Ideas?

Audio works fine. But any time I reboot the audio settings changes to select digital output (S/PDIF) built-in audio even though nothing is plugged in to that jack. So each time I reboot I have to go in to the settings to point to line out - Built-in-audio.

Not a huge problem but inconvenient. I did see similar questions and answers but those questions were quite old and not on point.

I haven't done testing to see if other settings are effected since the system is running perfectly otherwise.

Shouldn't the change in audio output settings be remembered automatically? I see no save button.

Thanks in advance.

I suspect this might be a Firefox bug except that all was working fine and seemed to all of a sudden break. This did not start happening immediately after any update or system change.

Obvious and easily repeatable symptoms are playing a youtube video on Firefox. Audio will be turned off. If you go into settings and move the firefox audio slider to full it will only stay there for a brief period. If you pause the video, skip forward or start viewing a new video the audio setting will revert back to zero. Incredibly annoying.

No other apps seem to exhibit this problem. I did go "under the hood" as recommended in relevant answers posted here and changed the media settings as recommended. This did not help.

Seems to only effect youtube video playbacks based on superficial testing. Rumble videos work as expected.

Wondering if I have to just wait for a FF update or if there is a way to patch in a fix.

I'm troubleshooting a problem of system hangs and want to know what's being logged just before the system freeze occurs. This effort is being hampered because my VPN provider (PIA) is logging gobs of information messages every minute. I'd like to have a lot less clutter on the shell window when things lock up.

I've tried adding something like various permutations of the following to rsyslog.conf

pia-daemon.info      /dev/null
pia*.info            /dev/null

I'd like to avoid creating additional conf files if possible. I do not want to suppress all info messages, just these. Ideas?

This is absolutely not a previously answered question! I have spent weeks (literally) reading these posts and documentation and for the most part the information and answers have been vague, misleading, downright incorrect or so convoluted that no normal person could ever follow them. Based on the number of comments by users who also had problems following these "answers" what's really needed is a clear, simple, flawless FAQ type procedure. It just shouldn't be this hard to resize a system when you install a larger SSD!

I'd prefer to do this via command lines but the several CLI answers I've seen posted have not worked. And one answer included the statement "say a prayer" after you enter this command. Like that's a procedure I want to follow.

The solution that looked the most promising involved kvpm but there is no information I can find that easily explains how to perform this simple task.

The procedure that came closest to success is posted at Encrypted drive cloning - resizing partitions problem

I'm very wearing reading poorly prepared documentation, answers that were obviously never tested before they were posted and trying various advice and commands that ultimately turn out to not work.

This is a VERY simple question:

I have a 100% running 18.04.2 Ubuntu installation that I've cloned onto a much larger 500 GB SDD. Everything works great but since I cloned it using dd the new SDD has a partition size of 32 GB (the size of the old SSD).

What we users need is a clear, correct, mistake-free, bullet-proof procedure for expanding the encrypted LVM partition (LUKS and ubuntu-vg) to use the available 485 gig of currently unallocated space. This ought not be rocket science and could probably be accomplished in a half dozen to a dozen commands, right?

Flames and downvotes are not going to be helpful here. An answer that works for everyone searching for a solution to this issue will help a lot of folks visiting here not just me.

Many thanks in advance.

I'm trying to clone my SSD to a larger device so I will have a bootable backup in anticipation of doing a system upgrade on several desktop clients. I also want to model a known-correct procedure to see if I can reliably clone my system drives to a larger HDD/SSD (so far all attempts to do this in the past have failed). Currently running 16.04 which was built using the fully encrypted disk option. The test system being used is running fine.

I followed several procedures I found on this site but none worked. I hit a dead end with each procedure, so to simplify things, I did the following:

sudo dd if=/dev/sda of=/dev/sdd  bs=64k

Opened GParted and deleted the old crypt-luks partition on /dev/sdd as instructed in the procedure posted at Cloning Encrypted SSD to larger SSD. This was a mistake and I was dead in the water from here on. I was unable to create a new crypt-luks partition.

So an answer that explains how to [re]create/resize the crypt-luks partition on the new target drive would be very helpful.

I repeated the dd and tried expanding the target filesystem with the following commands (using a live CD):

sudo cryptsetup luksOpen /dev/sda5 sda5_crypt
sudo cryptsetup resize sda5_crypt
sudo modprobe dm-crypt
sudo vgscan --mknodes
sudo vgchange -ay
sudo pvresize /dev/mapper/sda5_crypt
sudo lvresize -l +100%FREE /dev/ubuntu-vg/root

Returns: New size (7020 extents) matches existing size (7020 extents).

sudo pvchange -x n /dev/mapper/sda5_crypt

Returns:

Physical volume "/dev/mapper/sda5_crypt" is already unallocatable.
Physical volume /dev/mapper/sda5_crypt not changed
0 physical volumes changed / 1 physical volume not changed

sudo e2fsck -f /dev/mapper/ubuntu--vg-root

Returns:

Pass 5: Checking group summary information
/dev/mapper/ubuntu--vg-root: 296641/1798720 files (0.8% non-contiguous), 3525828/7188480 blocks

The source SSD was 32GB and the HDD I am trying to expand is 80 GB.

sudo resize2fs -f /dev/mapper/ubuntu--vg-root

Returns:

resize2fs 1.44.1 (24-Mar-2018)
The filesystem is already 7188480 (4k) blocks long.  Nothing to do!

So it appears that the procedure did not expand the partitions. This is verified by rebooting and running GParted which shows the same partitioning before and after:

I've been at this for many days doing research and trying to get this to work and I'm starting to get tunnel vision. I would very much appreciate someone posting a bullet-proof procedure that is known to work in cloning encrypted HDDs/SSDs to larger storage devices.

The target dd drive will indeed boot without expanding any partitions.

My primary question is really much more about expanding encrypted file systems than it is about cloning them. Although these two tasks are obviously very closely related. A bullet-proof, scalable, reliably repeatable procedure that explains how to do both would be extremely helpful. The procedure https://help.ubuntu.com/community/ResizeEncryptedPartitions is a bit too complex for me to follow although I believe I ran the procedure correctly. It's probably very close to what I need, but may be missing a step or two.

It seems to me that simply expanding the encrypted partitions on a properly cloned device ought not require more than several commands. Ideally this is something easily done using GParted.

I have several desktops running 16.04LTS. I have been anticipating upgrading them to 18.04LTS. I recently installed 18.04 on a crash dummy machine for testing and it mostly is working quite well. I downloaded the standard amd iso and installed Ubuntu without disk encryption (or LVM). This machine happens to have an AMD processor. All of my other machines use Intel CPUs.

I have quite a few folders that have been encrypted using Truecrypt. 7.1-14 I believe. The old version in any case.

I see that Truecrypt doesn't seem to be included in the standard distro so I installed it manually. However, it will not decrypt any of my existing encrypted folders. As a test, I created a container and then tried to mount it and that also failed. I won't bother with the various messages I got but suffice to say that Truecrypt is not working on my 18.04 LTS install.

I've read quite a few threads regarding this new distro and I'm wondering if it is a requirement to select full disk encryption when building the OS in order to have TC support. And either way, is there a method to install TC as a stand alone encryption tool?

There are several good answers here regarding how to fix problems caused by a full /boot partition. What I'd like to know is if there is any best practices for proactively managing this issue before it becomes a problem.

I routinely go many weeks and sometimes several months between reboots. The need to apply patches frequently is rarely an issue with Linux like it is with MS. If I didn't mind rebooting every few days I'd just run Windows.

I am running a small farm of Ubuntu 16.04 LTS machines. I added the following to one of them as a test:

sudo crontab -e

1 9 * * 2 apt -y autoremove --purge >> /dev/null

This runs a purge once a week which should be more than frequent enough. This does work although I did a manual purge before creating the cron job so there may be issues when there is actually something in there to purge. Like, will this command run to successful completion unattended in all situations? Any unforeseen unintended consequences of using this approach? Is there a better OOB management scheme? For supportability reasons I would prefer to avoid using custom scripts.

Many thanks in advance.

https://help.ubuntu.com/community/RemoveOldKernels specifically says that the following does NOT purge old kernels:

File: /etc/apt/apt.conf.d/50unattended-upgrades

Set: Unattended-Upgrade::Remove-Unused-Dependencies "true";

I am running Ubuntu on an ASUS Maximus VIII Formula mobo. All has been running fine for several months. Running Psensor 1.1.5

Problems with monitoring temps and fan speeds. The most obvious issue is that the Corsair H75 CPU cooler fans shows zero RPM. The cooler water pump isn't even listed.

Another major issue is that when I change the sensor settings in psensor they often change to some absurd value (e.g max CPU usage = 212%!).

I don't know if this is a factor but my home directory is encrypted.

frankie@Ubuntu:~$ sensors acpitz-virtual-0 Adapter: Virtual device temp1: +27.8°C (crit = +119.0°C) temp2: +29.8°C (crit = +119.0°C)

coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +34.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +18.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +17.0°C (high = +80.0°C, crit = +100.0°C) Core 2: +34.0°C (high = +80.0°C, crit = +100.0°C) Core 3: +19.0°C (high = +80.0°C, crit = +100.0°C)

asus-isa-0000 Adapter: ISA adapter cpu_fan: 0 RPM frankie@Ubuntu:~$ sudo pwmconfig

pwmconfig revision 6243 (2014-03-20)

This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed.

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

frankie@Ubuntu:~$ fancontrol Loading configuration from /etc/fancontrol ... Error: Can't read configuration file

frankie@Ubuntu:~$ ls -l /etc/fan* ls: cannot access '/etc/fan*': No such file or directory

Since posting this question I have tried to get psensor to recognize the sensors on numerous motherboards on multiple machines running a variety of Ubuntu distros. Recently built two Ubuntu 18.04 LTS machines, one using an ASUS ROG mobo and the other using an old Gigabyte mobo. Same problem. This seems to be a global problem with psensor. Is there a better app to display this information?