[Desktop-packages] [Bug 2085144] [NEW] the gjs application permanently consumes more than 100% of a processor
You have been subscribed to a public bug: Hello. I just upgraded from version 24.04.1 to version 24.10. Since I connected, I constantly hear the noise of the fan. Using the top command, I notice that the gjs application consumes more than 100% of a processor. This doesn't seem normal to me and I don't know what to look for to explain this behavior. If I kill the application, it automatically regenerates and has the same behavior. THANKS. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.10 Release:24.10 Codename: oracular a@p:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu oracular InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu oracular-updates InRelease Atteint :3 http://fr.archive.ubuntu.com/ubuntu oracular-backports InRelease Atteint :4 http://security.ubuntu.com/ubuntu oracular-security InRelease Tous les paquets sont à jour. Tâches: 320 total, 2 en cours, 318 en veille, 0 arrêté, 0 zombie %Cpu(s): 26,0 ut, 2,9 sy, 0,0 ni, 71,0 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 5815,2 total,175,8 libr, 2573,2 util, 3748,5 tamp/cache MiB Éch: 0,0 total, 0,0 libr, 0,0 util. 3242,0 dispo Mem PID UTIL. PR NIVIRTRESSHR S %CPU %MEMTEMPS+ COM. 4403 a 20 0 3203764 348396 43932 R 102,3 5,9 43:28.44 gjs 19664 a 20 0 1584276 167812 103900 S 8,6 2,8 0:18.41 gnome-text-edit 2732 a 20 0 4481976 325760 142840 S 4,0 5,5 2:03.18 gnome-shell 17 root 20 0 0 0 0 I 0,3 0,0 0:01.09 rcu_preempt 3764 a 20 0 561932 60444 44492 S 0,3 1,0 0:16.09 gnome-terminal- 18721 root 20 0 0 0 0 I 0,3 0,0 0:01.40 kworker/2:3-i915-unordered 19802 a 20 0 14828 5888 3712 R 0,3 0,1 0:00.09 top 1 root 20 0 25056 16544 10272 S 0,0 0,3 0:05.61 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.00 pool_workqueue_release 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_g 5 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_p 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-slub_ 7 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-netns 9 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:0H-events_highpri 12 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-mm_pe 13 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_kthread a@p:~$ ** Affects: gjs (Ubuntu) Importance: Undecided Status: New -- the gjs application permanently consumes more than 100% of a processor https://bugs.launchpad.net/bugs/2085144 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085404] Re: No display after booting
Are you suggesting the issue might come from the monitor? I used two monitors to reproduce the same issue, and both of them work on other machines. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085404 Title: No display after booting Status in xorg package in Ubuntu: New Bug description: [Impact] No display is shown after booting the machine. [Reproduce] 1. connect a monitor to the machine and boot it. 2. ssh into the machine and check the display using the following commands: $ export DISPLAY=":0.0" $ xrandr [Fail rate] 5/5 (100% failure rate) [Expected result] Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) [Actual result] Authorization required, but no authorization protocol specified Can't open display :0.0 [Additional information] https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202005-27944/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 23 14:10:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa] InstallationDate: Installed on 2024-05-31 (145 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd03/31/2020:br1.0:svnDellInc.:pnPrecision3440:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku09AA: dmi.product.family: Precision dmi.product.name: Precision 3440 dmi.product.sku: 09AA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2085404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085404] Re: No display after booting
Analysis from 201912_27623_journal_log.txt Early on during boot we see: kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is 61 kernel: [00] BAD 00 ff ff ff ff ff ff 00 04 69 c4 24 cc 83 03 00 kernel: [00] BAD 2c 18 01 03 80 35 1e 78 2a a0 a5 a6 56 52 9d 27 kernel: [00] BAD 0f 50 54 a0 00 00 00 00 00 00 00 07 ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff fe 00 00 00 00 00 00 00 kernel: [00] BAD 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff kernel: EDID has corrupt header kernel: i915 :00:02.0: [drm] Cannot find any crtc or sizes Then as GNOME Shell (Wayland) is starting up it suddenly terminates with SIGKILL. There's no clear indication of why, but just before we see "kernel: EDID has corrupt header" again. Oct 23 13:56:26 dell-precision-3440-c27623 kernel: EDID has corrupt header Oct 23 13:56:26 dell-precision-3440-c27623 systemd[1572]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL We are then kicked back to GDM which falls back to Xorg mode and keeps printing: kernel: EDID has corrupt header kernel: EDID block 0 (tag 0x00) checksum is invalid, remainder is ### kernel: workqueue: i915_hpd_poll_init_work [i915] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND (You now see `Authorization required, but no authorization protocol specified` because Xorg is running as the GDM user and you did not specify an XAUTHORITY file -- that is expected) There seems to be something wrong with the connection to the monitor, although that probably should not be killing GNOME Shell...? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085404 Title: No display after booting Status in linux package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Impact] No display is shown after booting the machine. [Reproduce] 1. connect a monitor to the machine and boot it. 2. ssh into the machine and check the display using the following commands: $ export DISPLAY=":0.0" $ xrandr [Fail rate] 5/5 (100% failure rate) [Expected result] Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) [Actual result] Authorization required, but no authorization protocol specified Can't open display :0.0 [Additional information] https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202005-27944/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 23 14:10:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa] InstallationDate: Installed on 2024-05-31 (145 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.
[Desktop-packages] [Bug 2083031] Re: cannot access hidraw devices
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2083031 Title: cannot access hidraw devices Status in chromium-browser package in Ubuntu: Fix Released Bug description: The snap version of chromium cannot access the /dev/hidraw* devices. My use case is to use an app like https://usevia.app/ or https://vial.rocks/ to configure my keyboard. Despite the filesystem permission chromium cannot open (in write mode) the hidraw devices: ``` $ snap run --shell chromium To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. dvd@tardis:/home/dvd$ ls -l /dev/hidraw* crw-rw+ 1 root plugdev 241, 0 Sep 27 13:52 /dev/hidraw0 crw-rw+ 1 root plugdev 241, 1 Sep 27 13:52 /dev/hidraw1 crw-rw-rw-+ 1 root plugdev 241, 10 Sep 27 13:59 /dev/hidraw10 crw-rw+ 1 root plugdev 241, 11 Sep 27 13:52 /dev/hidraw11 crw-rw+ 1 root plugdev 241, 2 Sep 27 13:52 /dev/hidraw2 crw-rw+ 1 root plugdev 241, 3 Sep 27 13:52 /dev/hidraw3 crw-rw+ 1 root plugdev 241, 4 Sep 27 13:52 /dev/hidraw4 crw-rw+ 1 root plugdev 241, 5 Sep 27 13:52 /dev/hidraw5 crw-rw+ 1 root plugdev 241, 6 Sep 27 13:52 /dev/hidraw6 crw-rw+ 1 root plugdev 241, 7 Sep 27 13:52 /dev/hidraw7 crw-rw+ 1 root plugdev 241, 8 Sep 27 13:52 /dev/hidraw8 crw-rw+ 1 root plugdev 241, 9 Sep 27 13:52 /dev/hidraw9 dvd@tardis:/home/dvd$ touch /dev/hidraw10 touch: setting times of '/dev/hidraw10': Operation not permitted dvd@tardis:/home/dvd$ ``` Maybe the fix is as simple as adding an hidraw plug? see https://snapcraft.io/docs/hidraw-interface? snap info chromium ``` name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 4 days ago, at 13:43 CEST channels: latest/stable:129.0.6668.58 2024-09-26 (2955) 181MB - latest/candidate: 129.0.6668.58 2024-09-26 (2955) 181MB - latest/beta: 130.0.6723.19 2024-09-26 (2958) 182MB - latest/edge: 131.0.6724.0 2024-09-25 (2954) 183MB - installed: 129.0.6668.58(2953) 177MB - ``` snap connections chroimium ``` Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record - bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support- camerachromium:camera :camera - content chromium:foo-install-cups - - content[gnome-42-2204]chromium:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes - content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups chromium:cups cups:cups - desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - hardware-observe chromium:hardware-observe :hardware-observe - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network
[Desktop-packages] [Bug 2085144] Re: the gjs application permanently consumes more than 100% of a processor
** Package changed: ubuntu-keyring (Ubuntu) => gjs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2085144 Title: the gjs application permanently consumes more than 100% of a processor Status in gjs package in Ubuntu: New Bug description: Hello. I just upgraded from version 24.04.1 to version 24.10. Since I connected, I constantly hear the noise of the fan. Using the top command, I notice that the gjs application consumes more than 100% of a processor. This doesn't seem normal to me and I don't know what to look for to explain this behavior. If I kill the application, it automatically regenerates and has the same behavior. THANKS. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.10 Release: 24.10 Codename: oracular a@p:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu oracular InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu oracular-updates InRelease Atteint :3 http://fr.archive.ubuntu.com/ubuntu oracular-backports InRelease Atteint :4 http://security.ubuntu.com/ubuntu oracular-security InRelease Tous les paquets sont à jour. Tâches: 320 total, 2 en cours, 318 en veille, 0 arrêté, 0 zombie %Cpu(s): 26,0 ut, 2,9 sy, 0,0 ni, 71,0 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 5815,2 total,175,8 libr, 2573,2 util, 3748,5 tamp/cache MiB Éch: 0,0 total, 0,0 libr, 0,0 util. 3242,0 dispo Mem PID UTIL. PR NIVIRTRESSHR S %CPU %MEMTEMPS+ COM. 4403 a 20 0 3203764 348396 43932 R 102,3 5,9 43:28.44 gjs 19664 a 20 0 1584276 167812 103900 S 8,6 2,8 0:18.41 gnome-text-edit 2732 a 20 0 4481976 325760 142840 S 4,0 5,5 2:03.18 gnome-shell 17 root 20 0 0 0 0 I 0,3 0,0 0:01.09 rcu_preempt 3764 a 20 0 561932 60444 44492 S 0,3 1,0 0:16.09 gnome-terminal- 18721 root 20 0 0 0 0 I 0,3 0,0 0:01.40 kworker/2:3-i915-unordered 19802 a 20 0 14828 5888 3712 R 0,3 0,1 0:00.09 top 1 root 20 0 25056 16544 10272 S 0,0 0,3 0:05.61 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.01 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.00 pool_workqueue_release 4 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_g 5 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-rcu_p 6 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-slub_ 7 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-netns 9 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/0:0H-events_highpri 12 root 0 -20 0 0 0 I 0,0 0,0 0:00.00 kworker/R-mm_pe 13 root 20 0 0 0 0 I 0,0 0,0 0:00.00 rcu_tasks_kthread a@p:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2085144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085375] Re: KUbuntu 24.04 can not acceass local files from Chromium and Brave
You did not mention Firefox, with comes pre-installed. Does the problem
not happen there or did you just not test it there?
Your home interface is connected. Do you have a non-conventional home
directory, or is it the usual /home/USER? The Apparmor log indicates the
latter, but I want to confirm it.
In /var/lib/snapd/apparmor/profiles/snap.chromium.chromium, do you have
such a section:
--->
# Allow read/write access to all files in @{HOME}, except snap application
# data in @{HOME}/snap and toplevel hidden directories in @{HOME}.
owner @{HOME}/[^s.]** rwklix,
owner @{HOME}/s[^n]** rwklix,
<---
Please also attach
dpkg -l|grep xdg-desktop-portal
systemctl list-units --user --type=service --state=running | grep xdg-desk
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
** No longer affects: ubuntu-personal-security (Ubuntu)
** No longer affects: ubuntu-core-security (Ubuntu)
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2085375
Title:
KUbuntu 24.04 can not acceass local files from Chromium and Brave
Status in chromium-browser package in Ubuntu:
Incomplete
Status in snapd package in Ubuntu:
Incomplete
Bug description:
KUbuntu 24.04 can not acceass local files from Chromium and Brave.
*How to reproduce*
1. Lets have Chromium or Brave installed from snap
2. Start app
3. Try to download file or load local file
*What happens*
Nothing. IUn download it says "Need permission to download"
*What is expected*
Download and upload files shall be not a problem for modern OS.
*Observation*
cat/var/log/syslog shows following relevant logs:
2024-10-22T19:43:11.774787+02:00 XXX kernel: audit: type=1400
audit(1729618991.773:244): apparmor="DENIED" operation="open"
class="file" profile="snap.chromium.chromium"
name="/home/user/Desktop/file.jpg" pid=3679 comm="ThreadPoolForeg"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
ProblemType: Bug
DistroRelease: Ubuntu 24.04
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Oct 22 19:45:58 2024
InstallationDate: Installed on 2024-05-11 (164 days ago)
InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64
(20240425.1)
Snap: chromium 129.0.6668.100 (latest/stable)
SnapChanges: no changes found
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2085375/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085340] Re: Plenty of amdgpu backtraces post resume
I enabled that debug option thingy. I'll try to have a go at a mainline kernel build at some point. Now the problem is I can't reproduce this so far. gnome-shell/xwayland randomly exits at some point without any explanation (you can see it just starts broken pipe at 12:31:54, no crash before, I need to find the cause for that and report another bug :(), and then it *might* trigger a suspend when switching to the gdm session. But like not every logout (forced or manual) triggers that. I think the hard part is that it suspends while it's VT switching to gdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2085340 Title: Plenty of amdgpu backtraces post resume Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: This is a very weird case: The GNOME session crashed 3 times today, the last time, it went to gdm, but then gdm did not recognize it was docked and suspended. I think the kernel needed two attempts to resume, it got suspended again after the first one; and it produced a whole bunch of back traces in dmesg. [ 3300.659129] WARNING: CPU: 1 PID: 65823 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 dal_gpio_service_open+0x1b6/0x270 [amdgpu] [ 3410.146130] WARNING: CPU: 4 PID: 73742 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 dmub_psr_enable+0x102/0x110 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-9-generic 6.11.0-9.9 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 22 12:45:20 2024 InstallationDate: Installed on 2022-11-26 (696 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.11.0-9-generic N/A linux-backports-modules-6.11.0-9-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033259] Re: netplan.script crashed with AttributeError in __getitem__(): /usr/bin/python3: undefined symbol: netplan_get_id_from_nm_filename
Recent version of Netplan (v1.1.1-1++) make use of dh-python and
${python3:Depends} substvars (LP: #2077011), so there's nothing to be
fixed there.
NetworkManager pulling in (old) Netplan on dist-upgrade happens only on
dist-upgrades to Noble, so there's nothing to be fixed in NM on Jammy.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: network-manager (Ubuntu Jammy)
Status: New => Invalid
** Summary changed:
- netplan.script crashed with AttributeError in __getitem__():
/usr/bin/python3: undefined symbol: netplan_get_id_from_nm_filename
+ [SRU] NetworkManager triggers a call from (old) Netplan Python CLI to into
(old) libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
** Summary changed:
- [SRU] NetworkManager triggers a call from (old) Netplan Python CLI to into
(old) libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
+ [SRU] NetworkManager triggers a call from (old) Netplan Python CLI into (old)
libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033259
Title:
[SRU] NetworkManager triggers a call from (old) Netplan Python CLI
into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-
upgrade
Status in netplan.io package in Ubuntu:
Won't Fix
Status in network-manager package in Ubuntu:
Fix Released
Status in netplan.io source package in Jammy:
New
Status in network-manager source package in Jammy:
Invalid
Status in netplan.io source package in Noble:
Won't Fix
Status in network-manager source package in Noble:
Confirmed
Status in netplan.io source package in Oracular:
Won't Fix
Status in network-manager source package in Oracular:
Fix Released
Bug description:
ubuntu desktop (mantic) live test on dell optiplex 780
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
exploring the /var/crash/ directory I noticed this report; nothing had
appeared on screen, so just filed it with `ubuntu-bug`.
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: netplan.io 0.106.1-8
Uname: Linux 6.3.0-7-generic x86_64
Architecture: amd64
Date: Mon Aug 28 08:12:32 2023
ExecutablePath: /usr/share/netplan/netplan.script
ExecutableTimestamp: 1684343476
InterpreterPath: /usr/bin/python3.11
ProcCmdline: /usr/bin/python3 /usr/sbin/netplan generate
ProcCwd: /
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
PythonArgs: ['/usr/sbin/netplan', 'generate']
SourcePackage: netplan.io
UserGroups: N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033259/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033259] Re: [SRU] NetworkManager triggers a call from (old) Netplan Python CLI into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
** Description changed:
+ [ Impact ]
+
+ * Context: Running a dist-upgrade from Jammy to Noble.
+ * Starting with Noble (Mantic actually), NetworkManager integrates with
Netplan as a backend and calls 'netplan generate' at different stages, e.g.
when migrating old /etc/NetworkManager/sytem-connections/ profiles to
/etc/netplan/ on package upgrade.
+ * NetworkManager depends on Netplan >= 0.106 only, but there was a major
SOVER/ABI bump of libnetplan, starting with Netplan v1.0. The new
build-dependency on libnetplan1 >= 1.0 is automatically picked up, but the
runtime dependency on the Netplan CLI (netplan.io binary) is not.
+ * Therefore, we can end up in a situation where the old netplan.io Python
CLI is still installed during dist-upgrade and tries to call into the new
libnetplan1, which is incompatible.
+ * Furthermore, python3-netplan ships a python3.10 specific
_netplan_cffi.cpython-310-x86_64-linux-gnu.so binary module, while
python3-netplan on Noble++ ships a universal _netplan_cffi.abi3.so binary
module. The old one can lead to issues when python3 is already upgraded.
+ * Incompatible versions of Netplan CLI, Netplan Python bindings and
libnetplan can lead to crashes of the Netplan CLI, like this: AttributeError:
/lib/x86_64-linux-gnu/libnetplan.so.1: undefined symbol:
netplan_get_id_from_nm_filename
+
+ * Such crash doesn't always happen, as it depends on the ordering of
+ package upgrades during dist-upgrade. It will recover itself after the
+ dist-upgrade is complete and all components are at their expected
+ versions again. So side-effects are rather small, but it can lead to
+ blocking of phased-updates for Netplan, which we'd like to avoid (LP:
+ #2058031).
+
+ * We want to make sure NetworkManager pulls in the latest libnetplan1,
+ netplan.io and python3-netplan packages on dist-upgrade, to avoid such
+ issues. Therefore declaring corresponding dependencies on the network-
+ manager binary package in debian/control. Such changes are not needed on
+ series after Noble, as recent Netplan is much more resilient against
+ such issues, using a python stable API binary module
+ (_netplan_cffi.abi3.so), using dh-python & ${python3:Depends} substvars,
+ and providing a stable libnetplan1 library.
+
+ [ Test Plan ]
+
+ $ lxc launch ubuntu-daily:jammy jj-nm-np
+ $ lxc shell jj-nm-np
+
+ # Verify old version of Netplan (< 1.0)
+ root@jj-nm-np:~# dpkg -l | grep netplan
+ ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
+ ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
+
+ root@jj-nm-np:~# sed -i 's/jammy/noble/g' /etc/apt/sources.list
+ root@jj-nm-np:~# apt update
+ root@jj-nm-np:~# apt install network-manager
+
+ => Make sure libnetplan1 >= 1.0, netplan.io >= 1.0 and python3-netplan
+ >= 1.0 are installed and the Netplan CLI does not crash, e.g.:
+
+ root@jj-nm-np:~# dpkg -l | grep netplan
+ ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
+ ii libnetplan1:amd64 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration runtime library
+ ii netplan-generator 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration systemd-generator
+ ii netplan.io 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration for various backends
+ ii python3-netplan 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration Python bindings
+ root@jj-nm-np:~# netplan generate
+
+ On a broken system, it looks like this:
+ root@jj-nm-np:~# dpkg -l | grep netplan.io
+ ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
+ root@jj-nm-np:~# dpkg -l | grep netplan
+ ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
+ ii libnetplan1:amd64 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration runtime library
+ ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
+ root@jj-nm-np:~# netplan generate
+ Traceback (most recent call last):
+ File "/usr/sbin/netplan", line 20, in
+ from netplan import Netplan
+ File "/usr/share/netplan/netplan/__init__.py", line 18, in
+ from netplan.cli.core import Netplan
+ File "/usr/share/netplan/netplan/cli/core.py", line 24, in
+ import netplan.cli.utils as utils
+ File "/usr/share/netplan/netplan/cli/utils.py", line 27, in
+ import ne
[Desktop-packages] [Bug 2085404] Re: No display after booting
After testing various monitors, I found that the first two monitors did not display any output, while the third monitor functioned correctly. I think the issue may be related to a connection problem like Alessandro suspect or compatibility with specific monitors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085404 Title: No display after booting Status in linux package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Impact] No display is shown after booting the machine. [Reproduce] 1. connect a monitor to the machine and boot it. 2. ssh into the machine and check the display using the following commands: $ export DISPLAY=":0.0" $ xrandr [Fail rate] 5/5 (100% failure rate) [Expected result] Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) [Actual result] Authorization required, but no authorization protocol specified Can't open display :0.0 [Additional information] https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202005-27944/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 23 14:10:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa] InstallationDate: Installed on 2024-05-31 (145 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd03/31/2020:br1.0:svnDellInc.:pnPrecision3440:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku09AA: dmi.product.family: Precision dmi.product.name: Precision 3440 dmi.product.sku: 09AA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085404] Re: No display after booting
[3.318004] EDID block 0 (tag 0x00) checksum is invalid, remainder is 61 [3.318009] [00] BAD 00 ff ff ff ff ff ff 00 04 69 c4 24 cc 83 03 00 [3.318010] [00] BAD 2c 18 01 03 80 35 1e 78 2a a0 a5 a6 56 52 9d 27 [3.318011] [00] BAD 0f 50 54 a0 00 00 00 00 00 00 00 07 ff ff ff ff [3.318011] [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [3.318012] [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [3.318012] [00] BAD ff ff ff ff ff ff ff ff fe 00 00 00 00 00 00 00 [3.318013] [00] BAD 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [3.318013] [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [5.537789] EDID has corrupt header [5.558591] i915 :00:02.0: [drm] Cannot find any crtc or sizes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085404 Title: No display after booting Status in xorg package in Ubuntu: New Bug description: [Impact] No display is shown after booting the machine. [Reproduce] 1. connect a monitor to the machine and boot it. 2. ssh into the machine and check the display using the following commands: $ export DISPLAY=":0.0" $ xrandr [Fail rate] 5/5 (100% failure rate) [Expected result] Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384 DP-1 disconnected primary (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) [Actual result] Authorization required, but no authorization protocol specified Can't open display :0.0 [Additional information] https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202005-27944/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) Date: Wed Oct 23 14:10:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 [VGA controller]) Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa] InstallationDate: Installed on 2024-05-31 (145 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Precision 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd03/31/2020:br1.0:svnDellInc.:pnPrecision3440:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku09AA: dmi.product.family: Precision dmi.product.name: Precision 3440 dmi.product.sku: 09AA dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2085404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.
[Desktop-packages] [Bug 2085420] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2085420/+attachment/5831052/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2085420 Title: gnome-shell/mutter crashes after suspend on 24.04 LTS Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2
[Desktop-packages] [Bug 2085420] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2085420/+attachment/5831049/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2085420 Title: gnome-shell/mutter crashes after suspend on 24.04 LTS Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24
[Desktop-packages] [Bug 2085420] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2085420/+attachment/5831050/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2085420 Title: gnome-shell/mutter crashes after suspend on 24.04 LTS Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu
[Desktop-packages] [Bug 2085420] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2085420/+attachment/5831048/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2085420 Title: gnome-shell/mutter crashes after suspend on 24.04 LTS Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2
[Desktop-packages] [Bug 2085420] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2085420/+attachment/5831051/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2085420 Title: gnome-shell/mutter crashes after suspend on 24.04 LTS Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2 Ta
[Desktop-packages] [Bug 2085420] [NEW] gnome-shell/mutter crashes after suspend on 24.04 LTS
Public bug reported: Unpacking the apport crash and running gdb with symbols, I get: #0 0x7336df3a216b in meta_thread_impl_get_instance_private ( self=) at ../src/backends/native/meta-thread-impl.c:84 #1 meta_thread_impl_is_in_impl (thread_impl=) at ../src/backends/native/meta-thread-impl.c:496 #2 meta_thread_is_in_impl_task (thread=0x73318768a70e) at ../src/backends/native/meta-thread.c:1258 #3 0x7336df3883d9 in meta_kms_in_impl_task (kms=) at ../src/backends/native/meta-kms.c:171 #4 meta_kms_impl_device_get_fd (impl_device=) at ../src/backends/native/meta-kms-impl-device.c:1064 #5 0x7336df38402b in meta_kms_mode_create_blob_id (error=0x7336cbdfebc0, mode=0x7336b40341f0) at ../src/backends/native/meta-kms-mode.c:51 #6 process_mode_set (error=0x7336cbdfebc0, user_data=0x0, update_entry=0x55b3b68353e0, blob_ids=, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=) at ../src/backends/native/meta-kms-impl-device-atomic.c:409 #7 process_entries (user_data=0x0, error=0x7336cbdfebc0, func=, entries=, blob_ids=0x7336c001aa40, req=0x7336b4034a90, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device-atomic.c:898 #8 meta_kms_impl_device_atomic_process_update (impl_device=0x7336b4003060, update=0x55b3b2be4b20, flags=) at ../src/backends/native/meta-kms-impl-device-atomic.c:1124 #9 0x7336df38c38b in do_process (impl_device=0x7336b4003060, latch_crtc=, update=0x55b3b2be4b20, flags=META_KMS_UPDATE_FLAG_MODE_SET) at ../src/backends/native/meta-kms-impl-device.c:1364 #10 0x7336df383027 in process_mode_set_update ( flags=META_KMS_UPDATE_FLAG_MODE_SET, update=0x55b3b2be4b20, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1736 #11 meta_kms_impl_device_process_update (flags=META_KMS_UPDATE_FLAG_MODE_SET, update=, impl_device=0x7336b4003060) at ../src/backends/native/meta-kms-impl-device.c:1770 #12 process_sync_update_in_impl (thread_impl=, user_data=, error=) at ../src/backends/native/meta-kms-device.c:304 #13 0x7336df3a16e7 in meta_thread_impl_dispatch ( thread_impl=thread_impl@entry=0x55b3af9be6c0) at ../src/backends/native/meta-thread-impl.c:542 #14 0x7336df3a180c in impl_source_dispatch ( source=source@entry=0x55b3af9be6f0, callback=, user_data=) at ../src/backends/native/meta-thread-impl.c:175 #15 0x7336df8b15b5 in g_main_dispatch (context=0x55b3afa46230) at ../../../glib/gmain.c:3344 #16 0x7336df910717 in g_main_context_dispatch_unlocked ( context=0x55b3afa46230) at ../../../glib/gmain.c:4152 #17 g_main_context_iterate_unlocked.isra.0 (context=0x55b3afa46230, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4217 #18 0x7336df8b1f77 in g_main_loop_run (loop=0x7336b4003100) at ../../../glib/gmain.c:4419 #19 0x7336df3a7426 in meta_thread_impl_run (flags=, thread_impl=) at ../src/backends/native/meta-thread-impl.c:582 #20 thread_impl_func (user_data=) at ../src/backends/native/meta-thread.c:428 #21 0x7336df8dfc82 in g_thread_proxy (data=0x55b3af9be1c0) at ../../../glib/gthread.c:835 #22 0x7336dee9ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #23 0x7336def29c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 This is on Lenovo Thinkpad T14s Gen 5 (Intel) with Core 135U CPU. Seems to be possible to reproduce quite reliably. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./.disk/casper-uuid-oem ./boot/grub/efi.img ./boot/grub/grub.cfg ./casper/initrd CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240409-800 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-23 (183 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240409-800 Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.2 Tags: noble wayland-session Uname: Linux 6.8.0-47-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-10-22 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected noble wayland-session ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected noble wayl
[Desktop-packages] [Bug 2084731] Re: Not report 6 GHz capability correctly
FTR: I've just uploaded a bundled SRU for network-manager 1.46.0-1ubuntu2.2, containing the changes from this bug report and additionally the changes from bug #2033259 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2084731 Title: Not report 6 GHz capability correctly Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Noble: Fix Committed Bug description: [Impact] network-manager not report 6GHz capability even hardware able to support 6GHz band [Test Plan] 1. nmcli -f wifi-properties.6ghz device show $DEV 2. should get correct result on 6GHz band enabled system "WIFI-PROPERTIES.6GHZ: yes" [Where problems could occur] If the parsing is incorrect, the status of WIFI-PROPERTIES.2GHZ, WIFI-PROPERTIES.5GHZ and WIFI-PROPERTIES.6GHZ may be incorrect. A codesearch query suggests those properties are only used by settings panels to reflect capabilities in the UI so if something went wrong the visible impact should be to have wrong information displayed. This SRU add attribute NL80211_ATTR_SPLIT_WIPHY_DUMP to split wiphy data across multiple messages, then parse the message one by one to get full supported frequencies. This attribute added after Linux 3.9. And there is not other function impact. The risk should be low [Other information] upstream merge proposal https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1899 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2084731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033259] Re: [SRU] NetworkManager triggers a call from (old) Netplan Python CLI into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
I've uploaded network-manager 1.46.0-1ubuntu2.2 into the Noble UNAPPROVED queue
for SRU review:
https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=network-manager
I'm bundling this with the pending SRU for 1.46.0-1ubuntu2.1 (LP:
#2084731)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033259
Title:
[SRU] NetworkManager triggers a call from (old) Netplan Python CLI
into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-
upgrade
Status in netplan.io package in Ubuntu:
Won't Fix
Status in network-manager package in Ubuntu:
Fix Released
Status in netplan.io source package in Jammy:
New
Status in network-manager source package in Jammy:
Invalid
Status in netplan.io source package in Noble:
Won't Fix
Status in network-manager source package in Noble:
In Progress
Status in netplan.io source package in Oracular:
Won't Fix
Status in network-manager source package in Oracular:
Fix Released
Bug description:
[ Impact ]
* Context: Running a dist-upgrade from Jammy to Noble.
* Starting with Noble (Mantic actually), NetworkManager integrates with
Netplan as a backend and calls 'netplan generate' at different stages, e.g.
when migrating old /etc/NetworkManager/sytem-connections/ profiles to
/etc/netplan/ on package upgrade.
* NetworkManager depends on Netplan >= 0.106 only, but there was a major
SOVER/ABI bump of libnetplan, starting with Netplan v1.0. The new
build-dependency on libnetplan1 >= 1.0 is automatically picked up, but the
runtime dependency on the Netplan CLI (netplan.io binary) is not.
* Therefore, we can end up in a situation where the old netplan.io Python
CLI is still installed during dist-upgrade and tries to call into the new
libnetplan1, which is incompatible.
* Furthermore, python3-netplan ships a python3.10 specific
_netplan_cffi.cpython-310-x86_64-linux-gnu.so binary module, while
python3-netplan on Noble++ ships a universal _netplan_cffi.abi3.so binary
module. The old one can lead to issues when python3 is already upgraded.
* Incompatible versions of Netplan CLI, Netplan Python bindings and
libnetplan can lead to crashes of the Netplan CLI, like this: AttributeError:
/lib/x86_64-linux-gnu/libnetplan.so.1: undefined symbol:
netplan_get_id_from_nm_filename
* Such crash doesn't always happen, as it depends on the ordering of
package upgrades during dist-upgrade. It will recover itself after the
dist-upgrade is complete and all components are at their expected
versions again. So side-effects are rather small, but it can lead to
blocking of phased-updates for Netplan, which we'd like to avoid (LP:
#2058031).
* We want to make sure NetworkManager pulls in the latest
libnetplan1, netplan.io and python3-netplan packages on dist-upgrade,
to avoid such issues. Therefore declaring corresponding dependencies
on the network-manager binary package in debian/control. Such changes
are not needed on series after Noble, as recent Netplan is much more
resilient against such issues, using a python stable API binary module
(_netplan_cffi.abi3.so), using dh-python & ${python3:Depends}
substvars, and providing a stable libnetplan1 library.
[ Test Plan ]
$ lxc launch ubuntu-daily:jammy jj-nm-np
$ lxc shell jj-nm-np
# Verify old version of Netplan (< 1.0)
root@jj-nm-np:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
root@jj-nm-np:~# sed -i 's/jammy/noble/g' /etc/apt/sources.list
root@jj-nm-np:~# apt update
root@jj-nm-np:~# apt install network-manager
=> Make sure libnetplan1 >= 1.0, netplan.io >= 1.0 and python3-netplan
>= 1.0 are installed and the Netplan CLI does not crash, e.g.:
root@jj-nm-np:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
ii libnetplan1:amd64 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration runtime library
ii netplan-generator 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration systemd-generator
ii netplan.io 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration for various backends
ii python3-netplan 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration Python bindings
root@jj-nm-np:~# netplan generate
root@jj-nm-np:~# echo $?
0
On a broken system, it looks like this:
root@jj-nm-np:~# dpkg -l | grep netplan.io
[Desktop-packages] [Bug 2085423] [NEW] "Privacy screen enabled" / "disabled" the wrong way on Ubuntu 24.04 LTS
Public bug reported: There is something wrong in the logic of Privacy screen enabled / disabled message, since it seems to be the wrong way around. Initially when logging in, there is a popup is shown about it being disabled. Then when one presses Fn+D for the first time, the privacy screen (Lenovo PrivacyGuard) is correctly enabled, but without a popup displayed. After that, it continues to show but the wrong way around - second Fn+D disables the privacy screen but the popup states it was enabled, and third Fn+D enables the privacy screen but the popup states it was disabled, and so on. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2085423 Title: "Privacy screen enabled" / "disabled" the wrong way on Ubuntu 24.04 LTS Status in mutter package in Ubuntu: New Bug description: There is something wrong in the logic of Privacy screen enabled / disabled message, since it seems to be the wrong way around. Initially when logging in, there is a popup is shown about it being disabled. Then when one presses Fn+D for the first time, the privacy screen (Lenovo PrivacyGuard) is correctly enabled, but without a popup displayed. After that, it continues to show but the wrong way around - second Fn+D disables the privacy screen but the popup states it was enabled, and third Fn+D enables the privacy screen but the popup states it was disabled, and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2085423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033259] Re: [SRU] NetworkManager triggers a call from (old) Netplan Python CLI into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-upgrade
** Changed in: network-manager (Ubuntu Noble)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2033259
Title:
[SRU] NetworkManager triggers a call from (old) Netplan Python CLI
into (old) libnetplan0 that got replaced by (new) libnetplan1 on dist-
upgrade
Status in netplan.io package in Ubuntu:
Won't Fix
Status in network-manager package in Ubuntu:
Fix Released
Status in netplan.io source package in Jammy:
New
Status in network-manager source package in Jammy:
Invalid
Status in netplan.io source package in Noble:
Won't Fix
Status in network-manager source package in Noble:
In Progress
Status in netplan.io source package in Oracular:
Won't Fix
Status in network-manager source package in Oracular:
Fix Released
Bug description:
[ Impact ]
* Context: Running a dist-upgrade from Jammy to Noble.
* Starting with Noble (Mantic actually), NetworkManager integrates with
Netplan as a backend and calls 'netplan generate' at different stages, e.g.
when migrating old /etc/NetworkManager/sytem-connections/ profiles to
/etc/netplan/ on package upgrade.
* NetworkManager depends on Netplan >= 0.106 only, but there was a major
SOVER/ABI bump of libnetplan, starting with Netplan v1.0. The new
build-dependency on libnetplan1 >= 1.0 is automatically picked up, but the
runtime dependency on the Netplan CLI (netplan.io binary) is not.
* Therefore, we can end up in a situation where the old netplan.io Python
CLI is still installed during dist-upgrade and tries to call into the new
libnetplan1, which is incompatible.
* Furthermore, python3-netplan ships a python3.10 specific
_netplan_cffi.cpython-310-x86_64-linux-gnu.so binary module, while
python3-netplan on Noble++ ships a universal _netplan_cffi.abi3.so binary
module. The old one can lead to issues when python3 is already upgraded.
* Incompatible versions of Netplan CLI, Netplan Python bindings and
libnetplan can lead to crashes of the Netplan CLI, like this: AttributeError:
/lib/x86_64-linux-gnu/libnetplan.so.1: undefined symbol:
netplan_get_id_from_nm_filename
* Such crash doesn't always happen, as it depends on the ordering of
package upgrades during dist-upgrade. It will recover itself after the
dist-upgrade is complete and all components are at their expected
versions again. So side-effects are rather small, but it can lead to
blocking of phased-updates for Netplan, which we'd like to avoid (LP:
#2058031).
* We want to make sure NetworkManager pulls in the latest
libnetplan1, netplan.io and python3-netplan packages on dist-upgrade,
to avoid such issues. Therefore declaring corresponding dependencies
on the network-manager binary package in debian/control. Such changes
are not needed on series after Noble, as recent Netplan is much more
resilient against such issues, using a python stable API binary module
(_netplan_cffi.abi3.so), using dh-python & ${python3:Depends}
substvars, and providing a stable libnetplan1 library.
[ Test Plan ]
$ lxc launch ubuntu-daily:jammy jj-nm-np
$ lxc shell jj-nm-np
# Verify old version of Netplan (< 1.0)
root@jj-nm-np:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
root@jj-nm-np:~# sed -i 's/jammy/noble/g' /etc/apt/sources.list
root@jj-nm-np:~# apt update
root@jj-nm-np:~# apt install network-manager
=> Make sure libnetplan1 >= 1.0, netplan.io >= 1.0 and python3-netplan
>= 1.0 are installed and the Netplan CLI does not crash, e.g.:
root@jj-nm-np:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction runtime library
ii libnetplan1:amd64 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration runtime library
ii netplan-generator 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration systemd-generator
ii netplan.io 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration for various backends
ii python3-netplan 1.0.1-1ubuntu2~24.04.1
amd64Declarative network configuration Python bindings
root@jj-nm-np:~# netplan generate
root@jj-nm-np:~# echo $?
0
On a broken system, it looks like this:
root@jj-nm-np:~# dpkg -l | grep netplan.io
ii netplan.io 0.106.1-7ubuntu0.22.04.4
amd64YAML network configuration abstraction for various backends
root@jj-nm-np:~# d
[Desktop-packages] [Bug 2085424] [NEW] libportal 0.8
Public bug reported: Hello, Please can we update libportal to 0.8 in Ubuntu 24.10 Oracular Oriole? The version currently available (libportal 0.7) is very old and stops programs like Deskflow, Input Leap, and Synergy from being able to support Wayland. https://packages.ubuntu.com/oracular/libportal1 https://packages.ubuntu.com/oracular/libportal-dev Thanks, Nick ** Affects: libportal (Ubuntu) Importance: Undecided Status: New ** Summary changed: - libportal + libportal 0.8 ** Description changed: Hello, Please can we update libportal to 0.8 in Ubuntu 24.10 Oracular Oriole? The version currently available (libportal 0.7) is very old and stops programs like Deskflow, Input Leap, and Synergy from being able to support Wayland. + https://packages.ubuntu.com/oracular/libportal1 + https://packages.ubuntu.com/oracular/libportal-dev + Thanks, Nick -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libportal in Ubuntu. https://bugs.launchpad.net/bugs/2085424 Title: libportal 0.8 Status in libportal package in Ubuntu: New Bug description: Hello, Please can we update libportal to 0.8 in Ubuntu 24.10 Oracular Oriole? The version currently available (libportal 0.7) is very old and stops programs like Deskflow, Input Leap, and Synergy from being able to support Wayland. https://packages.ubuntu.com/oracular/libportal1 https://packages.ubuntu.com/oracular/libportal-dev Thanks, Nick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libportal/+bug/2085424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
Change from HDMI to DisplayPort cable works for me. Ubuntu 24.10 Monitor Philips 276E Radeon 740M Graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in Mutter: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: [ Impact ] On some machines when the screen blanks, the LCD backlight stays on. [ Workarounds (reported to work by some people) ] * Configure the monitor (in its own menus) to not auto-switch inputs. * Change from HDMI to DisplayPort cables. * Disable HDMI audio output. [ Test Plan ] 0. Make sure you're using an LCD (not OLED) so you can see if the backlight is on. 1. In Settings -> Power -> Screen Blank, set the inactivity period to 1 minute. 2. Verify after 1 minute that the screen is blank and the backlight is also visibly off. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2084761] Re: gnome-shell crashes with SIGTRAP ("Settings schema 'org.gnome.desktop.interface' does not contain a key named 'accent-color'")
That's something may have happened, but it's weird that a restart could
lead to load a not-yet configured new gnome-shell (as its dependency has
not been configured yet).
So, that's definitely a quite weird problem. It seems more packaging
related, but g-s is correctly depending on the right version of desktop
schemas.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2084761
Title:
gnome-shell crashes with SIGTRAP ("Settings schema
'org.gnome.desktop.interface' does not contain a key named 'accent-
color'")
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
47.0-2ubuntu2, the problem page at
https://errors.ubuntu.com/problem/a244eec3c4a760a463be275e323b2717661e947e
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2084761/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085182] [NEW] package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit
You have been subscribed to a public bug: This occurred during the upgrade to 24.04. The snap changeover hung which hung the upgrade. I killed it from a shell session, the 143 error then popped up. ProblemType: Package DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 5.15.0-122.132-generic 5.15.163 Uname: Linux 5.15.0-122-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: susan 1534 F pulseaudio BuildID: 20240903191356 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Oct 22 10:19:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 143 ForcedLayersAccel: False InstallationDate: Installed on 2020-01-10 (1747 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp src 192.168.0.106 metric 600 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.106 metric 600 MachineType: HP HP Spectre x360 Convertible 13-aw0xxx NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 RunningIncompatibleAddons: False Snap: thunderbird 128.3.1esr-1 (stable) SnapChanges: ID Status Spawn Ready Summary 273 Done2024-10-22T10:15:27+10:30 2024-10-22T10:29:27+10:30 Install "thunderbird" snap Title: package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 143 UpgradeStatus: Upgraded to noble on 2024-10-22 (0 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 15.29 dmi.bios.vendor: AMI dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86F9 dmi.board.vendor: HP dmi.board.version: 87.74 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.74 dmi.modalias: dmi:bvnAMI:bvrF.29:bd08/20/2021:br15.29:efr87.74:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86F9:rvr87.74:cvnHP:ct31:cvrChassisVersion:sku8VZ58PA#ABG: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8VZ58PA#ABG dmi.sys.vendor: HP mtime.conffile..etc.init.d.apport: 2024-07-23T00:29:07 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 143. The process hung and I had to kill it. https://bugs.launchpad.net/bugs/2085182 You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085182] Re: package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit st
** Package changed: ubuntu => thunderbird (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2085182 Title: package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 143. The process hung and I had to kill it. Status in thunderbird package in Ubuntu: New Bug description: This occurred during the upgrade to 24.04. The snap changeover hung which hung the upgrade. I killed it from a shell session, the 143 error then popped up. ProblemType: Package DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 5.15.0-122.132-generic 5.15.163 Uname: Linux 5.15.0-122-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: susan 1534 F pulseaudio BuildID: 20240903191356 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Oct 22 10:19:42 2024 ErrorMessage: new thunderbird package pre-installation script subprocess returned error exit status 143 ForcedLayersAccel: False InstallationDate: Installed on 2020-01-10 (1747 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp src 192.168.0.106 metric 600 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.106 metric 600 MachineType: HP HP Spectre x360 Convertible 13-aw0xxx NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2 PythonDetails: /usr/bin/python3.12, Python 3.12.3, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6.1 apt 2.7.14build2 RunningIncompatibleAddons: False Snap: thunderbird 128.3.1esr-1 (stable) SnapChanges: ID Status Spawn Ready Summary 273 Done2024-10-22T10:15:27+10:30 2024-10-22T10:29:27+10:30 Install "thunderbird" snap Title: package thunderbird 1:115.15.0+build1-0ubuntu0.22.04.1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 143 UpgradeStatus: Upgraded to noble on 2024-10-22 (0 days ago) dmi.bios.date: 08/20/2021 dmi.bios.release: 15.29 dmi.bios.vendor: AMI dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86F9 dmi.board.vendor: HP dmi.board.version: 87.74 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 87.74 dmi.modalias: dmi:bvnAMI:bvrF.29:bd08/20/2021:br15.29:efr87.74:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86F9:rvr87.74:cvnHP:ct31:cvrChassisVersion:sku8VZ58PA#ABG: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx dmi.product.sku: 8VZ58PA#ABG dmi.sys.vendor: HP mtime.conffile..etc.init.d.apport: 2024-07-23T00:29:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2085182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2081728] Re: Startup crash (meta_seat_impl_run_input_task) with a wayland session and mouse keys
This bug was fixed in the package mutter - 47.0-1ubuntu5 --- mutter (47.0-1ubuntu5) plucky; urgency=medium * Add seat-impl-Initialize-the-impl-reverse-pointer-slightly-ea.patch to avoid crashing when mousekeys or keyboard a11y features are enabled (LP: #2081728) -- Daniel van Vugt Mon, 21 Oct 2024 15:07:57 +0800 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2081728 Title: Startup crash (meta_seat_impl_run_input_task) with a wayland session and mouse keys Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Invalid Status in mutter source package in Oracular: In Progress Bug description: [ Impact ] GNOME Shell Wayland sessions crash on startup if Mouse Keys (and other?) accessibility features are enabled. This seems to affect a large number of people: https://errors.ubuntu.com/problem/8a95f1902f49fc831d4bee942899ed1239896c64 [ Test Plan ] 1. Enable Mouse Keys: Settings > Accessibility > Pointing & Clicking > Mouse Keys = ON 2. Log out. 3. Log in (to a Wayland session). Expect: You can log in at all. When the bug is present you won't be able to log in without using 'Ubuntu on Xorg'. [ Where problems could occur ] During Wayland session startup, particularly relating to input support. Potentially other crashes could occur, or input devices malfunction. [ Other Info ] Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 meta_seat_impl_run_input_task (seat_impl=0x0, task=0x71bacc029130, dispatch_func=0x71bb2c9c2e10 ) at ../src/backends/native/meta-seat-impl.c:144 144 g_source_attach (source, seat_impl->input_context); [Current thread is 1 (Thread 0x71bb074006c0 (LWP 34862))] >>> bt #0 meta_seat_impl_run_input_task (seat_impl=0x0, task=0x71bacc029130 [GTask], dispatch_func=0x71bb2c9c2e10 ) at ../src/backends/native/meta-seat-impl.c:144 #1 0x71bb2c9c8278 in meta_virtual_input_device_native_constructed (object=0x71bacc0842e0 [MetaVirtualInputDeviceNative]) at ../src/backends/native/meta-virtual-input-device-native.c:1042 #2 0x71bb2d41801a in g_object_new_internal (class=0x71bacc030fd0, params=0x71bb073fe9a0, n_params=3) at ../../../gobject/gobject.c:2657 #3 0x71bb2d41a0fb in g_object_new_internal (class=0x71bacc030fd0, params=0x71bb073fe9a0, n_params=3) at ../../../gobject/gobject.c:2923 #4 g_object_new_valist (object_type=, first_property_name=first_property_name@entry=0x71bb2c9e3fc6 "seat", var_args=var_args@entry=0x71bb073fec70) at ../../../gobject/gobject.c:2945 #5 0x71bb2d41a47f in g_object_new (object_type=, first_property_name=first_property_name@entry=0x71bb2c9e3fc6 "seat") at ../../../gobject/gobject.c:2418 #6 0x71bb2c9b8218 in meta_seat_native_create_virtual_device (seat=0x5d75cfc73480 [MetaSeatNative], device_type=CLUTTER_POINTER_DEVICE) at ../src/backends/native/meta-virtual-input-device-native.c:101 #7 0x71bb2c99659b in enable_mousekeys (device_evdev=0x71bacc002580 [MetaInputDeviceNative]) at ../src/backends/native/meta-input-device-native.c:957 #8 meta_input_device_native_apply_kbd_a11y_settings_in_impl (device=0x71bacc002580 [MetaInputDeviceNative], settings=0x71bb073fedc0) at ../src/backends/native/meta-input-device-native.c:1308 #9 0x71bb2c9ba0b3 in meta_seat_impl_take_device (seat_impl=seat_impl@entry=0x5d75cfc74900 [MetaSeatImpl], device=device@entry=0x71bacc08e540 [MetaInputDeviceNative]) at ../src/backends/native/meta-seat-impl.c:1739 #10 0x71bb2c9be18e in process_base_event (seat_impl=0x5d75cfc74900 [MetaSeatImpl], event=0x71bacc07aa40) at ../src/backends/native/meta-seat-impl.c:1797 #11 process_event (seat_impl=0x5d75cfc74900 [MetaSeatImpl], event=0x71bacc07aa40) at ../src/backends/native/meta-seat-impl.c:2683 #12 process_events (seat_impl=seat_impl@entry=0x5d75cfc74900 [MetaSeatImpl]) at ../src/backends/native/meta-seat-impl.c:2699 #13 0x71bb2c9bfc21 in init_libinput (seat_impl=0x5d75cfc74900 [MetaSeatImpl], error=0x71bb073fef20) at ../src/backends/native/meta-seat-impl.c:2869 #14 input_thread (seat_impl=0x5d75cfc74900 [MetaSeatImpl]) at ../src/backends/native/meta-seat-impl.c:2968 #15 0x71bb2cd6ad02 in g_thread_proxy (data=0x5d75cfc629a0) at ../../../glib/gthread.c:892 #16 0x71bb2c4a1e2e in start_thread (arg=) at ./nptl/pthread_create.c:447 #17 0x71bb2c533a4c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 apt policy gnome-shell gnome-shell: Installed: 47.0-1ubuntu2 Candidate: 47.0-1ubuntu2 Version table: *** 47.0-1ubuntu2 1000 1000 http://fr.archive.ubuntu.com/ubuntu oracular/main amd64 Pa
[Desktop-packages] [Bug 2084662] Re: Hitting "send" does not do anything
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2084662 Title: Hitting "send" does not do anything Status in thunderbird package in Ubuntu: Confirmed Bug description: Somethings, when I hit "send", nothing happens. No error, nothing. Even if I run thunderbird in the terminal, I see no message or anything after pressing the "send" button. I have to save the draft, close thunderbird AND `pkill -f thunderbird`, then open thunderbird and the draft. Then, senting usually works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: thunderbird 2:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-550/nvidia-utils-550_550.67-0ubuntu3_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-550/nvidia-kernel-source-550_550.67-0ubuntu3_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Wed Oct 16 12:18:50 2024 InstallationDate: Installed on 2024-06-10 (128 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SnapChanges: ID Status Spawn Bereit Zusammenfassung 62 Done2024-10-16T11:47:35+02:00 2024-10-16T11:49:43+02:00 Entferne "thunderbird" Snap 63 Done2024-10-16T12:05:14+02:00 2024-10-16T12:05:36+02:00 Installiere "thunderbird" Snap 64 Done2024-10-16T12:06:04+02:00 2024-10-16T12:06:31+02:00 Restore of snapshot set #3 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2084662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032824] Re: Veth pairs fail activation on Jammy
The changes landed in upstream NetworkManager between 1.39.10-dev and 1.41.8-dev all of which is included in Noble. ** Changed in: network-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2032824 Title: Veth pairs fail activation on Jammy Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Triaged Bug description: Network Manager 1.36 has a bug that prevents it to activate veth pairs. The problem was found in the Netplan's CI with the new support for veths in Netplan (because we run the tests on Jammy). How to reproduce the problem: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were not activated, even though both interfaces were created in the system. Also, check the systemd journal and you should see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists Try the very same steps on Lunar and you'll see that the connections will be activated just fine. This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 I created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager If you run the same steps again on Jammy with this PPA you'll see it fixes this issue. In fact, Netplan's integration tests will work on Jammy using the PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028016] Re: Drop Channels feature?
Yeah, none of the online "Channels" work. When switching to the "Channels" tab and trying to click any of the pre- installed online channels, none of them works: - Clicking "Rai.tv" and opening on any of the categories causes Totem to crash on SIGSEGV. - Clicking "Apple Movie Trailers" causes lots of parser errors to be printed on stdout and Totem to hang. - Clicking "Euronews" displays an empty window. It would be the best to just remove them, sadly Totem has no active maintainer[1] and is on a basic "life support" now, and grilo-plugins also do not seem to be much active. Upstream tickets: https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/89 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/90 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/91 [1] https://www.hadess.net/2023/08/new-responsibilities.html ** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #89 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/89 ** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #90 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/90 ** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #91 https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/91 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2028016 Title: Drop Channels feature? Status in Totem: New Status in totem package in Ubuntu: Triaged Bug description: Ubuntu's default video app, Totem, includes a Channels tab with 3 web video providers: - Apple Movie Trailers - Euronews - Rai.tv Screenshot attached. I recommend that we disable this feature because - These are somewhat obscure video sources - It can be unexpected to parents, school administrators, etc. for this app to be able to view web content - Perhaps most importantly, none of these 3 sources seemed to work today in my clean Ubuntu 23.04 install. + Apple Movie Trailers worked after I installed the additional media support which is offered in the Ubuntu installer (ubuntu-restricted-addons which specifically installs gstreamer1.0-libav) + Based on the errors shown in my terminal, it looks like Euronews either changed their API or it's no longer available. - If these channels can be broken and we aren't getting bug reports, are people actually even using this feature? Implementation -- This feature is enabled by some plugins shipped in totem's src/plugins . They can be disabled by the meson build. Also, totem depends on grilo-plugins-0.3-base which provides supporting files. None of the plugins works if that dependency is removed. We would then also need to patch Totem to no longer show the Channels page in the Totem app. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/2028016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083657] Re: Remove oem-flavour.cfg for the OEM kernel retirement
autopkgtests green so far -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement Status in OEM Priority Project: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Won't Fix Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * This issue affects all Ubuntu OEM preloaded systems that are still utilizing the OEM kernel, particularly those equipped with NVIDIA graphics drivers. * Systems may fail to boot properly due to an outdated OEM kernel conflicting with newer NVIDIA drivers, leading to a black screen on reboot. [ Test Plan ] * To verify the fix, ensure that the file `/etc/default/grub.d/oem-flavour.cfg` is successfully removed from the affected system after applying the update. * After the system reboots, check that it boots into the general HWE kernel rather than the OEM kernel. * Idempotency Testing: - Perform the upgrade multiple times on the same system to verify that the upgrade process is idempotent, ensuring that repeated upgrades do not result in unexpected behavior or changes. * Non-OEM System Testing: - Test the upgrade on a system without OEM kernels to ensure that the upgrade does not affect systems that are not preloaded with the OEM kernel. - Confirm that the system continues to function normally and boots into the correct kernel after the update. [ Where problems could occur ] * Removing `/etc/default/grub.d/oem-flavour.cfg` may cause systems relying on the OEM kernel for specific hardware compatibility to lose access to certain OEM-specific optimizations. * There is a low risk that after removing the OEM kernel, some hardware features may not function as expected if the general HWE kernel does not fully support them. [ Other Info ] * This patch is targeted only for Ubuntu 22.04 and its associated OEM kernels. * The issue is specific to systems using NVIDIA drivers in conjunction with an outdated OEM kernel, which conflicts with updates to the HWE kernel and NVIDIA packages. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About $ lsb_release -rd Description: Ubuntu 22.04.4 LTS Release: 22.04 $ ubuntu-report show | grep DCD "DCD": "canonical-oem-sutton-jammy-amd64-20240606-874" 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.6 Candidate: 1:0.9.6.2~0.22.04.7 Version table: 1:0.9.6.2~0.22.04.7 500 500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages *** 1:0.9.6.2~0.22.04.6 100 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen * The system should seamlessly upgrade NVIDIA drivers and the HWE kernel without breaking the boot process. The system should boot into the latest supported HWE kernel without encountering compatibility issues with the NVIDIA drivers. 4) What happened instead * After unattended-upgrades, the system rebooted into the OEM kernel, which is outdated and incompatible with the new NVIDIA drivers. As a result, the screen remained black upon reboot. We need to remove /etc/default/grub.d/oem-flavour.cfg to avoid the system booting from deprecated OEM kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2084420] Re: Gedit Yaru theme unable to load
@batwan Thanks for the workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2084420 Title: Gedit Yaru theme unable to load Status in gedit package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Gedit will produce the following error on startup: (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit-gtksourceview-300/styles/Yaru.xml': missing 'version' attribute (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit- gtksourceview-300/styles/Yaru-dark.xml': missing 'version' attribute at the top of the files, a version number needs to be added like in the example below: from to once this is done, restart gedit and you will be able to enjoy the theme. Interestingly, these files aren't part of libgedit- gtksourceview-300-common so they must be added by a different package. Edit: is is part of yaru-theme-gtk ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gedit 46.2-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 14:50:25 2024 InstallationDate: Installed on 2022-04-06 (922 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to oracular on 2024-10-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2084420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2084420] Re: Gedit Yaru theme unable to load
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2084420 Title: Gedit Yaru theme unable to load Status in gedit package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Gedit will produce the following error on startup: (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit-gtksourceview-300/styles/Yaru.xml': missing 'version' attribute (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit- gtksourceview-300/styles/Yaru-dark.xml': missing 'version' attribute at the top of the files, a version number needs to be added like in the example below: from to once this is done, restart gedit and you will be able to enjoy the theme. Interestingly, these files aren't part of libgedit- gtksourceview-300-common so they must be added by a different package. Edit: is is part of yaru-theme-gtk ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gedit 46.2-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 14:50:25 2024 InstallationDate: Installed on 2022-04-06 (922 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to oracular on 2024-10-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2084420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2081672] Re: Scanning not enabled by the Bluetooth slider
** Description changed: [ Impact ] * Turning off bluetooth for over 1 minutes and turn on it in bluetooth panel. There is no devices list, and the bluetooth controller is not discoverable. [ Test Plan ] * Find a machine with bluetooth as the device under test (DUT) * Open g-c-c bluetooth panel on the DUT * Turn off the bluetooth on the DUT for 1 minutes * Put another bluetooth gadget to discovery mode * Turn on the bluetooth on the DUT in the bluetooth panel * There should be bluetooth device listed, and the DUT is also discoverable [ Where problems could occur ] - * The patch is adding a case where the device discovery will not be - enabled. If the condition was wrong the discovery state could be changed - incorrectly, leading to the computer not getting visible nor listing - other devices when it should or in the reverse way, being listed by - other devices when it shouldn't. In practice the computer should only be - available to other devices when the toggle is enable and the setting - panel displayed. + * The change capture the situation that the dicoverable flag is being + set wrongly, so that the application is not able to trigger scan + anymore. The issue might still happen if the adapter not able to be in + powered state, but it is not the situation that the patch is trying to + fix. [ Other Info ] * Upstream, https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/de707f592304309a59208e3ed1afbe4a37568bdd https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/3d45205c79b48dd3e15e1c4edb58cf8cd79f23ef -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2081672 Title: Scanning not enabled by the Bluetooth slider Status in OEM Priority Project: New Status in gnome-bluetooth3 package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Bug description: [ Impact ] * Turning off bluetooth for over 1 minutes and turn on it in bluetooth panel. There is no devices list, and the bluetooth controller is not discoverable. [ Test Plan ] * Find a machine with bluetooth as the device under test (DUT) * Open g-c-c bluetooth panel on the DUT * Turn off the bluetooth on the DUT for 1 minutes * Put another bluetooth gadget to discovery mode * Turn on the bluetooth on the DUT in the bluetooth panel * There should be bluetooth device listed, and the DUT is also discoverable [ Where problems could occur ] * The change capture the situation that the dicoverable flag is being set wrongly, so that the application is not able to trigger scan anymore. The issue might still happen if the adapter not able to be in powered state, but it is not the situation that the patch is trying to fix. [ Other Info ] * Upstream, https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/de707f592304309a59208e3ed1afbe4a37568bdd https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/commit/3d45205c79b48dd3e15e1c4edb58cf8cd79f23ef To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2083772] Re: System gets blank/black screen after login
Sorry for the delay even after switching back to the Wayland with the hack for almost 25 days i was unable to reproduce this and was about to conclude it to be fixed somehow, but today it happened(finally ! 🙃 ). Logs are attached as requested. ** Attachment added: "log.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083772/+attachment/5831059/+files/log.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2083772 Title: System gets blank/black screen after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: recently when logging in to Ubuntu desktop with GDM the screen appears black only with cursor appearing as it is, rebooting fixes the problem but only temporary as it occurs randomly initial guess was that this occurs due to the hack suggested at https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2077216/comments/4 for issue https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2077216 but even after disabling the hack(https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2077216/comments/15) this occurs. This is common to both x11 & wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 19:31:01 2024 InstallationDate: Installed on 2024-08-15 (52 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2083772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085388] Re: MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working
Can I get any suggestion on how to fix at least HDMI? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2085388 Title: MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working Status in alsa-driver package in Ubuntu: New Bug description: I am experiencing two significant issues on my MSI Bravo 15 laptop (AMD Ryzen™ 5 4600H with Radeon™ Graphics × 12) running Ubuntu 24.04.1 LTS: Fan Noise: The system is consistently making loud fan noises, even during low workloads. This happens immediately after boot and persists, affecting the overall user experience. HDMI Not Working: Despite various attempts (including driver updates, reconfiguring display settings, and using different HDMI cables), the HDMI output is completely non-functional. The system does not recognize external displays at all. These issues significantly impact usability, and I would greatly appreciate any assistance or insights on how to resolve them. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:purplebyteone 3166 F pipewire /dev/snd/controlC0: purplebyteone 3169 F wireplumber /dev/snd/controlC1: purplebyteone 3169 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 23:15:37 2024 InstallationDate: Installed on 2024-07-24 (90 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Bravo 15 A4DDR PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2020 dmi.bios.release: 1.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16WKAMS.110 dmi.board.asset.tag: Default string dmi.board.name: MS-16WK dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16WKAMS.110:bd10/29/2020:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnBravo15A4DDR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16WK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16WK.1: dmi.product.family: Br dmi.product.name: Bravo 15 A4DDR dmi.product.sku: 16WK.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2084420] Re: Gedit Yaru theme unable to load
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/2084420 Title: Gedit Yaru theme unable to load Status in gedit package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Gedit will produce the following error on startup: (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit-gtksourceview-300/styles/Yaru.xml': missing 'version' attribute (gedit:256008): libgedit-gtksourceview-WARNING **: 14:43:48.787: could not load style scheme file '/usr/share/libgedit- gtksourceview-300/styles/Yaru-dark.xml': missing 'version' attribute at the top of the files, a version number needs to be added like in the example below: from to once this is done, restart gedit and you will be able to enjoy the theme. Interestingly, these files aren't part of libgedit- gtksourceview-300-common so they must be added by a different package. Edit: is is part of yaru-theme-gtk ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gedit 46.2-3 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 14:50:25 2024 InstallationDate: Installed on 2022-04-06 (922 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gedit UpgradeStatus: Upgraded to oracular on 2024-10-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2084420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
This bug is supposed to be fixed in the kernel driver: https://bugzilla.kernel.org/show_bug.cgi?id=215203 Then it's been reported this workaround help people who don't have other option (like me) than HDMI and their monitor doesn't have menu option to disable automatic switching between ports: https://gitlab.freedesktop.org/drm/amd/-/issues/1840 I can't confirm yet if that workaround works for me. ** Bug watch added: Linux Kernel Bug Tracker #215203 https://bugzilla.kernel.org/show_bug.cgi?id=215203 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1840 https://gitlab.freedesktop.org/drm/amd/-/issues/1840 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in Mutter: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: [ Impact ] On some machines when the screen blanks, the LCD backlight stays on. [ Workarounds (reported to work by some people) ] * Configure the monitor (in its own menus) to not auto-switch inputs. * Change from HDMI to DisplayPort cables. * Disable HDMI audio output. [ Test Plan ] 0. Make sure you're using an LCD (not OLED) so you can see if the backlight is on. 1. In Settings -> Power -> Screen Blank, set the inactivity period to 1 minute. 2. Verify after 1 minute that the screen is blank and the backlight is also visibly off. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2032824] Re: Veth pairs fail activation on Jammy
** Description changed: - Network Manager 1.36 has a bug that prevents it to activate veth pairs. - The problem was found in the Netplan's CI with the new support for veths - in Netplan (because we run the tests on Jammy). + [ Impact ] + + * Network Manager 1.36 has a bug that prevents it to activate veth pairs. + * The problem was found in the Netplan's CI with the new support for veths in Netplan v0.107. + + * We cherry-pick upstream patches to fix the issue: + - https://gitlab.freedesktop.org/piotrdrag/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 + - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/07e0ab48d194b8bd6663a34887c2e753720ae4d3 + - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/50f738bde5b441b5ca52024c1a0998399b87337b + + [ Test Plan ] + + * Run netplan.io's autopkgtests against the new network-manager package and make sure it passes the veth tests, especially those two: +- test_create_veth_pair (__main__.TestNetworkManager) +- test_create_veth_pair_with_ip_address (__main__.TestNetworkManager) + + * In addition to that, reproduce the steps from this bug report: + 1) Launch a Jammy VM and install network-manager + + lxc launch ubuntu:jammy jammy --vm + lxc shell jammy + apt -y install network-manager + + 2) Set the default Netplan's renderer to NetworkManager so NM can manage + interfaces (it will make Netplan create the file + /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) + + netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager + netplan apply + + 3) Create the veth pair + + nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled + nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled + + 4) Reboot + + 5) Check with "nmcli con show" that the new connections were activated, + and created in the system. Also, check the systemd journal and you + should NOT see this error message: + + [1692805758.9025] manager: (veth-veth0) couldn't create the + device: Failed to create veth interface 'veth0' for 'veth-veth0': exists + + [ Where problems could occur ] + + * We're pulling upstream patchces to modify NetworkManager's + src/core/devices/nm-device-veth.c file. This could have side-effects on + veth functionality in general when NetworkManager is in use. + + [ Other Info ] + + * This issue appears to be fixed by this commit + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 + + * Danilo created a PPA with the fix here + https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager + + + === Original bug report === + Network Manager 1.36 has a bug that prevents it to activate veth pairs. The problem was found in the Netplan's CI with the new support for veths in Netplan (because we run the tests on Jammy). How to reproduce the problem: 1) Launch a Jammy VM and install network-manager lxc launch ubuntu:jammy jammy --vm lxc shell jammy apt -y install network-manager 2) Set the default Netplan's renderer to NetworkManager so NM can manage interfaces (it will make Netplan create the file /var/run/NetworkManager/conf.d/10-globally-managed-devices.conf) netplan set --origin-hint=50-cloud-init network.renderer=NetworkManager netplan apply 3) Create the veth pair nmcli con add type veth ifname veth0 peer veth1 ipv4.method disabled ipv6.method disabled nmcli con add type veth ifname veth1 peer veth0 ipv4.method disabled ipv6.method disabled 4) Reboot 5) Check with "nmcli con show" that the new connections were not activated, even though both interfaces were created in the system. Also, check the systemd journal and you should see this error message: [1692805758.9025] manager: (veth-veth0) couldn't create the device: Failed to create veth interface 'veth0' for 'veth-veth0': exists + Try the very same steps on Lunar and you'll see that the connections + will be activated just fine. - Try the very same steps on Lunar and you'll see that the connections will be activated just fine. - - - This issue appears to be fixed by this commit https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 + This issue appears to be fixed by this commit + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/4655b7c308461ae1f86d592ea6d45e00a2820423 I created a PPA with the fix here https://launchpad.net/~danilogondolfo/+archive/ubuntu/network-manager If you run the same steps again on Jammy with this PPA you'll see it fixes this issue. In fact, Netplan's integration tests will work on Jammy using the PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2032824 Tit
[Desktop-packages] [Bug 2085457] [NEW] after waking up gnome hase 'white screen'
Public bug reported: 1) has white screen 'oops smth went wrong' 2) extensions are turned off after restart ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-session 46.0-8ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 19:30:07 2024 PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to oracular on 2024-10-17 (6 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2085457 Title: after waking up gnome hase 'white screen' Status in gnome-session package in Ubuntu: New Bug description: 1) has white screen 'oops smth went wrong' 2) extensions are turned off after restart ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-session 46.0-8ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 19:30:07 2024 PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to oracular on 2024-10-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2085457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085359] Re: my brightness control from the drop down menu on the top right section of the screen does not reduce the brightness at all. screen is always at full brightness whi
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2085359 Title: my brightness control from the drop down menu on the top right section of the screen does not reduce the brightness at all. screen is always at full brightness which takes up a lot of battery. Status in xorg package in Ubuntu: New Bug description: my brightness control from the drop down menu on the top right section of the screen does not reduce the brightness at all. screen is always at full brightness which takes up a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:23:18 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu GraphicsCard: Intel Corporation Meteor Lake-P [Intel Arc Graphics] [8086:7d55] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Meteor Lake-P [Intel Arc Graphics] [1043:3778] NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] [10de:28e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. AD107M [GeForce RTX 4060 Max-Q / Mobile] [1043:35f8] InstallationDate: Installed on 2024-09-17 (35 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G16 GU605MV_GU605MV ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=a6edc1a4-a9b7-4013-b245-0e7d358193b7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2024 dmi.bios.release: 5.32 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GU605MV.322 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU605MV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.22 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGU605MV.322:bd07/23/2024:br5.32:efr3.22:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG16GU605MV_GU605MV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU605MV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G16 dmi.product.name: ROG Zephyrus G16 GU605MV_GU605MV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. nvidia-settings: ERROR: NVIDIA driver is not loaded version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2085359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028016] Re: Drop Channels feature?
By the way, any chance the broken grilo-plugins could be disabled directly in Debian instead of patching it in Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2028016 Title: Drop Channels feature? Status in Totem: New Status in totem package in Ubuntu: Triaged Bug description: Ubuntu's default video app, Totem, includes a Channels tab with 3 web video providers: - Apple Movie Trailers - Euronews - Rai.tv Screenshot attached. I recommend that we disable this feature because - These are somewhat obscure video sources - It can be unexpected to parents, school administrators, etc. for this app to be able to view web content - Perhaps most importantly, none of these 3 sources seemed to work today in my clean Ubuntu 23.04 install. + Apple Movie Trailers worked after I installed the additional media support which is offered in the Ubuntu installer (ubuntu-restricted-addons which specifically installs gstreamer1.0-libav) + Based on the errors shown in my terminal, it looks like Euronews either changed their API or it's no longer available. - If these channels can be broken and we aren't getting bug reports, are people actually even using this feature? Implementation -- This feature is enabled by some plugins shipped in totem's src/plugins . They can be disabled by the meson build. Also, totem depends on grilo-plugins-0.3-base which provides supporting files. None of the plugins works if that dependency is removed. We would then also need to patch Totem to no longer show the Channels page in the Totem app. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/2028016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085457] Re: after waking up gnome hase 'white screen'
by playing with extensions found that faulty one is 'Window List' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2085457 Title: after waking up gnome hase 'white screen' Status in gnome-session package in Ubuntu: New Bug description: 1) has white screen 'oops smth went wrong' 2) extensions are turned off after restart ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-session 46.0-8ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 19:30:07 2024 PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to oracular on 2024-10-17 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2085457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2084605] Re: File|(all options) can no longer be accessed via keystrokes
I found an older Ubuntu box (18.04) with older LO/Calc (6.4.7.2) and Gnome rather than Wayland, and it works correctly: [Alt+F] opens the File menu, and the New sub-menu then auto-opens, but the File menu’s options remain available for keystroke selection. I then installed LODev 6.4.0.0.alpha0+ for testing, and the issue is present using this version on my system. Thus, it does not appear to be only a LO issue. It has been suggested that this may be related to Wayland, rather than LO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2084605 Title: File|(all options) can no longer be accessed via keystrokes Status in libreoffice package in Ubuntu: New Bug description: $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04.1 LTS Release: 24.04 $ apt-cache policy libreoffice libreoffice: Installed: 4:24.2.6-0ubuntu0.24.04.1 Candidate: 4:24.2.6-0ubuntu0.24.04.1 Version table: *** 4:24.2.6-0ubuntu0.24.04.1 500 500 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages 100 /var/lib/dpkg/status 4:24.2.5-0ubuntu0.24.04.2 500 500 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages 4:24.2.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages I had to reinstall my OS last month, so this is a new installation, and I do not know how old my previous LibreOffice install was. I am no longer able to use keystrokes to access the Recent Documents list. Previously, [Alt+F],U would display the most recently accessed documents, but there is now only a 0.5 second window in which the ‘U’ can be pressed, before the File|New sub-menu appears, disabling the ability to keystroke-select the Recent Documents option on the File menu. What I expected to happen: [Alt+F],U would display the most recently accessed documents list What happened instead: Unless the 'U' is pressed very quickly (but not TOO quickly), the File|New sub-menu appears, disabling the ability to keystroke-select the Recent Documents option on the File menu. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libreoffice 4:24.2.6-0ubuntu0.24.04.1 ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12 Uname: Linux 6.8.0-47-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 15 14:45:59 2024 InstallationDate: Installed on 2024-09-12 (34 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2084605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2085473] [NEW] fail to connect to bt headphones until removed and repaired
Public bug reported: Since upgrading to 24.10, my bluetooth headphones often fail to connect until I remove them and re-pair. More specifically, they connect for a second or two and then immediately disconnect. Seems to happen more when I switch them to connect to a different device and come back to connect to the 24.10 machine, but not a clear pattern on what triggers it. Did not experience this on 24.04 fwiw. error messages in journalctl like: Oct 23 12:50:49 taplop bluetoothd[2047]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to XX:XX:XX:XX:XX:XX: Connection refused (111) Oct 23 12:50:49 taplop bluetoothd[2047]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to XX:XX:XX:XX:XX:XX: Connection refused (111) Oct 23 12:50:49 taplop gnome-shell[4441]: Failed to connect device "headphones": GDBus.Error:org.bluez.Error.Failed: br-connection-unknown ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Oct 23 13:44:33 2024 InstallationDate: Installed on 2019-08-17 (1895 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 031: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. XPS 15 9575 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-8-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: Upgraded to oracular on 2024-10-01 (22 days ago) dmi.bios.date: 07/11/2023 dmi.bios.release: 1.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.28.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.28.0:bd07/11/2023:br1.28:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:90:74:7A ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:9818817 acl:136395 sco:0 events:275478 errors:0 TX bytes:40769018 acl:48133 sco:0 commands:337 errors:0 modified.conffile..etc.bluetooth.main.conf: [modified] mtime.conffile..etc.bluetooth.main.conf: 2024-03-23T09:45:36.572752 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oracular wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2085473 Title: fail to connect to bt headphones until removed and repaired Status in bluez package in Ubuntu: New Bug description: Since upgrading to 24.10, my bluetooth headphones often fail to connect until I remove them and re-pair. More specifically, they connect for a second or two and then immediately disconnect. Seems to happen more when I switch them to connect to a different device and come back to connect to the 24.10 machine, but not a clear pattern on what triggers it. Did not experience this on 24.04 fwiw. error messages in journalctl like: Oct 23 12:50:49 taplop bluetoothd[2047]: src/profile.c:ext_connect() Hands-Free Voice gateway failed connect to XX:XX:XX:XX:XX:XX: Connection refused (111) Oct 23 12:50:49 taplop bluetoothd[2047]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to XX:XX:XX:XX:XX:XX: Connection refused (111) Oct 23 12:50:49 taplop gnome-shell[4441]: Failed to connect device "headphones": GDBus.Error:org.bluez.Error.Failed: br-connection-unknown ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: bluez 5.77-0ubuntu1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 Uname: Linux 6.11.0-8-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Oct 23 13:44:33 2024 InstallationDate: Installed on 2019-08-17 (1895 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0489:e0a2 Foxconn /
[Desktop-packages] [Bug 2085340] Re: Plenty of amdgpu backtraces post resume
> Now the problem is I can't reproduce this so far. gnome-shell/xwayland randomly exits at some point without any explanation (you can see it just starts broken pipe at 12:31:54, no crash before, I need to find the cause for that and report another bug :( Maybe this: https://gitlab.gnome.org/GNOME/mutter/-/issues/3723 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3723 https://gitlab.gnome.org/GNOME/mutter/-/issues/3723 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2085340 Title: Plenty of amdgpu backtraces post resume Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: This is a very weird case: The GNOME session crashed 3 times today, the last time, it went to gdm, but then gdm did not recognize it was docked and suspended. I think the kernel needed two attempts to resume, it got suspended again after the first one; and it produced a whole bunch of back traces in dmesg. [ 3300.659129] WARNING: CPU: 1 PID: 65823 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 dal_gpio_service_open+0x1b6/0x270 [amdgpu] [ 3410.146130] WARNING: CPU: 4 PID: 73742 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 dmub_psr_enable+0x102/0x110 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-9-generic 6.11.0-9.9 ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0 Uname: Linux 6.11.0-9-generic x86_64 ApportVersion: 2.30.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Oct 22 12:45:20 2024 InstallationDate: Installed on 2022-11-26 (696 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: LENOVO 21CF004PGE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.11.0-9-generic N/A linux-backports-modules-6.11.0-9-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2024 dmi.bios.release: 1.53 dmi.bios.vendor: LENOVO dmi.bios.version: R23ET77W (1.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CF004PGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T76538 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21CF004PGE dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2077797] Re: When you type on file, the letters are typed in an other open file
[Expired for gnome-text-editor (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-text-editor (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/2077797 Title: When you type on file, the letters are typed in an other open file Status in gnome-text-editor package in Ubuntu: Expired Bug description: When you type on file, the letters are typed in an other open file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/2077797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2079039] Re: signature stored on a nfs share not working with the snap
"browser.download.force_save_internally_handled_attachments" did only help for a week, after this weekend I have to configure the signatures each morning again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2079039 Title: signature stored on a nfs share not working with the snap Status in thunderbird package in Ubuntu: New Bug description: We work in workspace with changing pcs. (home folders are in the network) We migrated from Ubuntu 22.04 LTS Desktop to Ubuntu 24.04.1 LTS Desktop. We use thunderbird 128.1.0esr-1 through snap. Our signature all lie on an nfs mount (/var/nfs/oeffentlich/emailsignaturen/) (fstab: nfs.mydomain:/var/nfs /var/nfs nfs4 _netdev,default), where everybody as read access (drwxr-xr-x 1 nobody nogroup 5,3K Aug 28 09:27 emailsignaturen). After the update, Thunderbird no longer pointed to "/var/nfs/oeffentlich/emailsignaturen/mysignature.html" but to "/home/myuser/var/nfs/oeffentlich/emailsignaturen/mysignature.html". Correcting this to "/var/nfs/oeffentlich/emailsignaturen/mysignature.html" by directly editing the text, did not show an error, but the signature wasn't shown. Using the file open dialog and selecting "/var/nfs/oeffentlich/emailsignaturen/mysignature.html" Thunderbird / snap changed the link to: "/run/user/2087/doc/e967c83e/mysignature.html" Now the signature is shown, but only as long as I'm on the same pc. When switching to another PC the linked file isn't there and I again have no signature. No clue, whether this is a thunderbird or snap issue, but this is really a pain! Would be nice if this could be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2079039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
