[Desktop-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox
There's 6.5.0-15 package incoming on mantic-update, does it contains the
fix?
--
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/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Confirmed
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
The only extensions installed are: > $ gnome-extensions list > lockk...@vaina.lt > d...@rastersoft.com > ubuntu-appindicat...@ubuntu.com > ubuntu-d...@ubuntu.com > tiling-assist...@ubuntu.com -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
Lots of crashes on https://errors.ubuntu.com/user/a5880f5d67200136401b48e606e90173fb34300b11a89ca2507124cd0b5a044b7751eefba0fc9f16b27183bed1a11134c74d956b2b7161ee37aa1ee5d1d5c8ed The one we are interested in is https://errors.ubuntu.com/oops/ad78e2e9-9344-11ee-8949-fa163ec8ca8c but I'm not able to access to its content. -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+attachment/5726374/+files/journal.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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
it was uploaded already but I dont know where: > $ sudo cat /var/crash/_usr_bin_gnome-shell.1000.uploaded > ad78e2e9-9344-11ee-8949-fa163ec8ca8c -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2045632] Re: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+attachment/5726373/+files/prevjournal.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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: Incomplete Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2045632] [NEW] gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed
Public bug reported: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2045632 Title: gnome-shell libmozjs g_closure_unref: assertion closure->ref_count > 0 failed Status in gnome-shell package in Ubuntu: New Bug description: While just using my system, GNOME Shell suddenly disappeared and logs shows: déc. 05 09:02:23 portable-alex gnome-shell[4341]: g_closure_unref: assertion 'closure->ref_count > 0' failed déc. 05 09:02:23 portable-alex gnome-shell[4341]: GNOME Shell crashed with signal 11 déc. 05 09:02:23 portable-alex gnome-shell[4341]: == Stack trace for context 0x55996924e410 == déc. 05 09:02:23 portable-alex kernel: traps: JS Helper[4367] general protection fault ip:7fe24f05d21c sp:7fe2339fec80 error:0 in libmozjs-115.so.115.3.0[7fe24ef18000+b73000] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 5 09:08:03 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (519 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-3ubuntu3.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045632/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done-mantic -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Enabled proposed repo on 23.10 ``` $ $ sudo apt install -t mantic-proposed mutter Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Le paquet suivant a été installé automatiquement et n'est plus nécessaire : libjs-jquery-ui-theme-base Veuillez utiliser « sudo apt autoremove » pour le supprimer. Les paquets supplémentaires suivants seront installés : gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin Les NOUVEAUX paquets suivants seront installés : mutter Les paquets suivants seront mis à jour : gir1.2-mutter-13 libmutter-13-0 mutter-common mutter-common-bin 4 mis à jour, 1 nouvellement installés, 0 à enlever et 26 non mis à jour. Il est nécessaire de prendre 1 727 ko dans les archives. Après cette opération, 205 ko d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] Réception de :1 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 mutter-common all 45.0-3ubuntu3.1 [45,5 kB] Réception de :2 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 gir1.2-mutter-13 amd64 45.0-3ubuntu3.1 [130 kB] Réception de :3 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 libmutter-13-0 amd64 45.0-3ubuntu3.1 [1 391 kB] Réception de :4 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 mutter-common-bin amd64 45.0-3ubuntu3.1 [49,3 kB] Réception de :5 http://fr.archive.ubuntu.com/ubuntu mantic-proposed/universe amd64 mutter amd64 45.0-3ubuntu3.1 [111 kB] 1 727 ko réceptionnés en 0s (7 132 ko/s) (Lecture de la base de données... 313559 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../mutter-common_45.0-3ubuntu3.1_all.deb ... Dépaquetage de mutter-common (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../gir1.2-mutter-13_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../libmutter-13-0_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Préparation du dépaquetage de .../mutter-common-bin_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de mutter-common-bin (45.0-3ubuntu3.1) sur (45.0-3ubuntu3) ... Sélection du paquet mutter précédemment désélectionné. Préparation du dépaquetage de .../mutter_45.0-3ubuntu3.1_amd64.deb ... Dépaquetage de mutter (45.0-3ubuntu3.1) ... Paramétrage de mutter-common (45.0-3ubuntu3.1) ... Paramétrage de mutter-common-bin (45.0-3ubuntu3.1) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 (2.78.0-2) ... Traitement des actions différées (« triggers ») pour libglib2.0-0:i386 (2.78.0-2) ... Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) ... Traitement des actions différées (« triggers ») pour man-db (2.11.2-3) ... Paramétrage de libmutter-13-0:amd64 (45.0-3ubuntu3.1) ... Paramétrage de mutter (45.0-3ubuntu3.1) ... update-alternatives: utilisation de « /usr/bin/mutter » pour fournir « /usr/bin/x-window-manager » (x-window-manager) en mode automatique Paramétrage de gir1.2-mutter-13:amd64 (45.0-3ubuntu3.1) ... Traitement des actions différées (« triggers ») pour libc-bin (2.38-1ubuntu6) ... ``` Closed GNOME session, reopened it, unplugged from dock, force lock screen, and I cannot reproduce the problem anymore. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [
[Desktop-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox
Thanks, I'll try and keep you updated, however I am also facing bug
2039958 (probably a dupe of bug 2034619), so I might still need GNOME
45.1 to be released.
--
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/2039868
Title:
amdgpu reset during usage of firefox
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
New
Bug description:
Running nightly on 23.10 (since monday), I have been experiencing a
few amdgpu resets in the past hours
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 18:26:43 2023
HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
InstallationDate: Installed on 2022-07-04 (472 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
dmi.bios.date: 05/15/2023
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET54W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias:
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2039958] Re: gnome-shell session dies when locking laptop screen
dupe of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2034619 ? -- 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/2039958 Title: gnome-shell session dies when locking laptop screen Status in gnome-shell package in Ubuntu: New Bug description: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE) failed to read Wayland events: Broken pipe oct. 20 11:40:18 portable-alex update-notifier[28393]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta.desktop[27371]: The Wayland connection broke. Did the Wayland compositor die? oct. 20 11:40:18 portable-alex xdg-desktop-por[26680]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex snapd-desktop-i[26606]: Error reading events from display: Broken pipe oct. 20 11:40:18 portable-alex solaar[26327]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex evolution-alarm[26356]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex xdg-desktop-por[26746]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta[27371]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-wacom[26213]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-color[26168]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-power[26183]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-keyboard[26178]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gnome-terminal-[27151]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-media-keys[26180]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct. 20 11:40:18 portable-alex sudo[28424]: pam_unix(sudo:session): session closed for user root oct. 20 11:40:18 portable-alex io.github.Hexchat.desktop[27864]: hexchat: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0. oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:03:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (473 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+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 2039958] Re: gnome-shell session dies when locking laptop screen
Disabling all extensions does not help -- 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/2039958 Title: gnome-shell session dies when locking laptop screen Status in gnome-shell package in Ubuntu: New Bug description: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE) failed to read Wayland events: Broken pipe oct. 20 11:40:18 portable-alex update-notifier[28393]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta.desktop[27371]: The Wayland connection broke. Did the Wayland compositor die? oct. 20 11:40:18 portable-alex xdg-desktop-por[26680]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex snapd-desktop-i[26606]: Error reading events from display: Broken pipe oct. 20 11:40:18 portable-alex solaar[26327]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex evolution-alarm[26356]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex xdg-desktop-por[26746]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta[27371]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-wacom[26213]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-color[26168]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-power[26183]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-keyboard[26178]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gnome-terminal-[27151]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-media-keys[26180]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct. 20 11:40:18 portable-alex sudo[28424]: pam_unix(sudo:session): session closed for user root oct. 20 11:40:18 portable-alex io.github.Hexchat.desktop[27864]: hexchat: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0. oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:03:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (473 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039958/+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 2039958] [NEW] gnome-shell session dies when locking laptop screen
Public bug reported: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE) failed to read Wayland events: Broken pipe oct. 20 11:40:18 portable-alex update-notifier[28393]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta.desktop[27371]: The Wayland connection broke. Did the Wayland compositor die? oct. 20 11:40:18 portable-alex xdg-desktop-por[26680]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex snapd-desktop-i[26606]: Error reading events from display: Broken pipe oct. 20 11:40:18 portable-alex solaar[26327]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex evolution-alarm[26356]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex xdg-desktop-por[26746]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex vorta[27371]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-wacom[26213]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-color[26168]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-power[26183]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-keyboard[26178]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gnome-terminal-[27151]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex gsd-media-keys[26180]: Error reading events from display: Relais brisé (pipe) oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit UNIT has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. oct. 20 11:40:18 portable-alex sudo[28424]: pam_unix(sudo:session): session closed for user root oct. 20 11:40:18 portable-alex io.github.Hexchat.desktop[27864]: hexchat: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0. oct. 20 11:40:18 portable-alex systemd[3731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:03:36 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-07-04 (473 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 45.0-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-16 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2039958 Title: gnome-shell session dies when locking laptop screen Status in gnome-shell package in Ubuntu: New Bug description: Started after migrating to 23.10 STR: - Boot laptop - Login - Start GNOME Terminal - Lock screen Expected: - Screen is locked, I can unlock and recover my session Actual: - Screen gets locked, does not unlock, and ends up starting a new gnome session This only reproduces in the simple case of laptop with its integrated screen being used. When I connect to my docking station, with two external monitors and the internal screen disabled, I can properly perform the locking/unlocking. journalctl does not show anything useful besides: oct. 20 11:40:13 portable-alex kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 oct. 20 11:40:18 portable-alex gnome-shell[27866]: (EE)
[Desktop-packages] [Bug 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
~~Just upgraded my laptop to 23.10 release, and I can confirm the issue is STILL present. This is NOT fixed.~~ It is indeed fixed, I am now facing bug 1969598, since running `gnome- extensions disable d...@rastersoft.com` helps. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Do you know if it's part of the lunar-updates 44.2-0ubuntu1 ? Looking at the changelog it's not clear to me. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Has upstream just reverted the offending change? https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2909 -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in mutter package in Ubuntu: Confirmed Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Disabling this extension and logging out / logging back in, I still have the problem -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in mutter package in Ubuntu: Incomplete Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Thanks, I just tried and for now it does not help. The other bug mentions one might need to restart the session which I can't do at the moment but will try later. -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in mutter package in Ubuntu: Incomplete Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020672/+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 2020672] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020672/+attachment/5675434/+files/ProcCpuinfoMinimal.txt -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
apport information ** Tags added: apport-collected lunar wayland-session ** Description changed: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2022-07-04 (324 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + NonfreeKernelModules: zen_workaround + Package: libmutter-12-0 44.0-2ubuntu4 + PackageArchitecture: amd64 + ProcEnviron: + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + RebootRequiredPkgs: Error: path contained symlinks. + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2020672/+attachment/5675433/+files/Dependencies.txt -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2022-07-04 (324 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: zen_workaround Package: libmutter-12-0 44.0-2ubuntu4 PackageArchitecture: amd64 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RebootRequiredPkgs: Error: path contained symlinks. Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (33 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020672] Re: Focus constantly moves to the secondary screen upon workspace switch
Would it have been fixed by https://gitlab.gnome.org/GNOME/mutter/-/commit/0d69fabbe6895fdac31e044060ed16bd1f1c344a ? -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020672] [NEW] Focus constantly moves to the secondary screen upon workspace switch
Public bug reported: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Focus constantly moves to the secondary screen upon desktop switch + Focus constantly moves to the secondary screen upon workspace switch ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2548 https://gitlab.gnome.org/GNOME/mutter/-/issues/2548 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2548 Importance: Unknown Status: Unknown -- 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/2020672 Title: Focus constantly moves to the secondary screen upon workspace switch Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: I have two screen, side by side, with IDs (2) and (3) ; physically and within GNOME Control Center, the setup is as is: [ (3) ][ (2) ] The Screen with identifier (2) is defined as the main screen. My multiscreen setup in GNOME Control Center is: - Fixed number of workspace (12) - Workspaces only on main screen The issue is that whenever I move from one workspace to the other (using keyboard shortcuts CTRL+ALT+(<-|->), the system gives focus to the secondary screen, identifier (3) above. This is really super painful on a day-to-day basis because I spend half of my time fixing the focus and/or inputing in the wrong window. It already made me loose valuable work because of a CTRL+C in the wrong window. As much as I can recall, this was not the behavior in previous releases. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2020672/+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 2020655] Re: XDG Desktop Portal should show "nice" user path
A fix was made by upstream at https://github.com/flatpak/xdg-desktop- portal/pull/1007 and I could verify a local rebuild of 22.04 package with this applied does fix it, including for Firefox Snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2020655 Title: XDG Desktop Portal should show "nice" user path Status in firefox snap: Unknown Status in xdg-desktop-portal: Unknown Status in xdg-desktop-portal package in Ubuntu: New Bug description: Users hould not see "/run/xxx" but rather e.g., "/tmp/" To manage notifications about this bug go to: https://bugs.launchpad.net/firefox-snap/+bug/2020655/+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 2020655] [NEW] XDG Desktop Portal should show "nice" user path
Public bug reported: Users hould not see "/run/xxx" but rather e.g., "/tmp/" ** Affects: firefox-snap Importance: Unknown Status: Unknown ** Affects: xdg-desktop-portal Importance: Unknown Status: Unknown ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #973 https://github.com/flatpak/xdg-desktop-portal/issues/973 ** Also affects: xdg-desktop-portal via https://github.com/flatpak/xdg-desktop-portal/issues/973 Importance: Unknown Status: Unknown ** Bug watch added: Mozilla Bugzilla #1775497 https://bugzilla.mozilla.org/show_bug.cgi?id=1775497 ** Also affects: firefox-snap via https://bugzilla.mozilla.org/show_bug.cgi?id=1775497 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2020655 Title: XDG Desktop Portal should show "nice" user path Status in firefox snap: Unknown Status in xdg-desktop-portal: Unknown Status in xdg-desktop-portal package in Ubuntu: New Bug description: Users hould not see "/run/xxx" but rather e.g., "/tmp/" To manage notifications about this bug go to: https://bugs.launchpad.net/firefox-snap/+bug/2020655/+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 2017907] Re: cups-browsed high CPU usage
same for me, I have not verified what was causing it, this is the first time it happens for me though I upgraded to 23.04 a few weeks ago already. Connected over WiFi, as someone mentions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/2017907 Title: cups-browsed high CPU usage Status in cups-filters package in Ubuntu: Confirmed Bug description: Hi, Using Lunar wifi connected to an enterprise network. cups-browsed uses a lot of CPU %, I need to kill it to save my battery. 2.0rc1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/2017907/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
Yann, your screenshots are not accessible to me. For firefox, could you share `about:support` with and without `MOZ_ENABLE_WAYLAND` ? We have had several reports as well that got duped to https://bugzilla.mozilla.org/show_bug.cgi?id=1828196 ** Bug watch added: Mozilla Bugzilla #1828196 https://bugzilla.mozilla.org/show_bug.cgi?id=1828196 -- 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/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Possible, proposed solutions Please install from these channels and report back with success or failure. snap refresh --channel candidate/core22 firefox snap refresh --edge chromium If nothing works, it is possible around the issue by disabling hardware acceleration. Original bug report --- Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10
[Desktop-packages] [Bug 1988292] Re: Voices aren't listed
As much as I can say: - I had the bug (hence sebastian filing this) - I am on proposed - 0.11.1-1ubuntu2 is installed (I apt purge'd it and reinstalled) - I cannot reproduce anymore, neither in `spd-say -L` nor in Firefox. Looks like the backport works. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1988292 Title: Voices aren't listed Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Bug description: * Impact In the default speech-dispatcher configuration no voices are listed while some are installed. Voices are needed for speechsynthesis to work in webbrowser as described on bug #1987979 * Test case $ spd-say -L should list voices the fix is also part of making speech-dispatcher work with firefox but more fixes are needed for the feature to work in the snap * Regression potential The wrong voices could be selected, check that spd-say respects the selected voice and language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1988292/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
I gave a try and I can confirm that following the modemmanager docs to enable FCC unlock procedure at ModemManager level, the modem is properly unlocked and connects to the internet. However, this is another issue, but the firmware crashing persist when trying to make use of the LTE connection a bit more than just sending a ping. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
Thanks, I just saw that Jammy has 1.26.2. I might try and give it a try to verify the behavior of the LTE modem there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
That would mean that Jammy, a LTS, will not be able to make use of LTE modems on 2021 shipped ThinkPad ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Closing as invalid, since I can't repro anymore and I can't explain why. ** Changed in: modemmanager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: Invalid Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Trying to investigate https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1949621 I made a few local backports of modemmanager / libmm / libqmi packages from next 22.04 (but the source was still too old to handle the modem), and when I reverted to latest impish version, it seems the bug disappeared? I can now successfully: - use mmcli, as a standard user, like before - use modem-manager-gui, as a standard user, like before - see modem from GNOME Control Center and interact with it, as a standard user, like before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
** Summary changed: - libmbim cannot make use of Quectel EM120 + modemmanager/libmbim cannot make use of Quectel EM120 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: libmbim cannot make use of Quectel EM120
I just had a look and next version of Ubuntu uses ModemMamager 1.18.2 as of now, so it does not have the handling for FCC unlock procedure. ** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] Re: libmbim cannot make use of Quectel EM120
** Description changed: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? + + I understand it might require a backport, since they merged it against + 1.26 and it does not seems to apply cleanly on 1.24. I also suspect + upgrading libmbim to 1.26 is not acceptable for impish release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1949621] [NEW] libmbim cannot make use of Quectel EM120
Public bug reported: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? ** Affects: libmbim (Ubuntu) Importance: Undecided Status: New ** Tags: hw-specific impish patch-accepted-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
** Attachment added: "Running as normal user" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534920/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Running GNOME Control Center as root (not a good idea, I know), clearly gets the ModemManager connection to work. ** Attachment added: "GNOME Control Center (root)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534919/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
NetworkManager itself is able to properly talk to ModemManager: > $ nmcli con show |grep gsm > Orange Internet0a196fc4-89e3-479b-b049-ab13dfff897b gsm -- And a `nmcli con "Orange Internet" up` works (assuming you have enabled the modem which is blocked on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402 in my case) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
According to the policies in place for ModemManager in /etc/dbus-1/system.d/org.freedesktop.ModemManager1.conf it looks like only root can really do something. Assuming this is right, then I'm wondering why GNOME Control Center tries to directly access ModemManager instead of going via NetworkManager ? At least that is what I am wondering from the error in message #1 from `(uid=1000 pid=49211 comm="gnome-control-center " label="unconfined")` ** Summary changed: - NetworkManager cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" + GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" ** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues #402 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/402 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Looks like https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402#note_1064882 does help, I have been able to enable my EM120 on 21.10. Take care to change the proper defines in the provided C code. The `mbim2sar.so` comes from the Snap package linked above. Thanks to Joar Wandborg ! ** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues #402 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/402 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Fix Released Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Sadly, Quectel EM120 is not supported, so I can't use mine on ThinkPad P14s Gen2 laptop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Fix Released Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there is a
[Desktop-packages] [Bug 1695601] Re: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
Newer versions of NetworkManager, after upgrading from 17.04, have been bundling the proper fix. -- 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: Confirmed Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1695601/+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 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
Same on upgrade from Ubuntu 18.04 to 18.10, fuser -v confirms exclusive access taken by timidity on the sound device, removing timidity* fixes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+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 1799007] Re: no sound after 18.10 upgrade
Ok, in my case, |fuser -v| reveals that it's being blocked by timidity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1799007] Re: no sound after 18.10 upgrade
I'm also facing the same issue, and "apport-collect 1799007" does not accept to run for me, stating I'm not on the bug :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1799007 Title: no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1695601] Re: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
I just got confirmation from Beniamino Galvani that this is consistent with his change. Also, the patch is part of the 1.4 branch and should be in the next release: https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/?h=nm-1-4 -- 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: New Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1695601/+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 1695601] [NEW] IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
Public bug reported: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] > platform-linux: event-notification: NEWADDR, seq 0: > 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime > 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] > platform-linux: event-notification: NEWADDR, seq 0: > 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime > 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: New Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt
[Desktop-packages] [Bug 1073372] Re: Xorg produces high CPU usage after a few days
What do you mean by 'red herring' ? As far as I can tell, I reproduced the issue a couple of times since my latest comment, and each time I just had to kill the empathy process to get my system back. -- 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/1073372 Title: Xorg produces high CPU usage after a few days Status in “xorg” package in Ubuntu: Confirmed Bug description: Thinkpad X220 (Intel video, chipsets, etc) After a few days of uptime and usage on this laptop, the xorg process will start randomly (but consistently over time) producing high CPU usage, even with all applications closed. CPU according to top will vary between about 10% and 90%, and at high CPU times, the system fans will be running rather high. Also, the UIs will slow down and there will be a lot of latency on keypresses (sometimes up to 1 second), with the occasional loss of keypresses. In gnome-terminal, this has the effect of feeling like you're over a cellular modem, even on a local terminal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,move,gnomecompat,compiztoolbox,imgpng,mousepoll,regex,place,snap,unitymtgrabhandles,resize,grid,session,animation,workarounds,expo,wall,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Tue Oct 30 16:30:09 2012 DistUpgraded: 2012-09-15 22:41:29,902 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller MachineType: LENOVO 4286CTO ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-09-16 (44 days ago) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET61WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1073372/+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 1073372] Re: Xorg produces high CPU usage after a few days
FYI I've reinstalled my distro just after my previous report. Until today, no reproducing. Today, it started to be reproduced, and it seems to be fixed when I kill telepathy and empathy processes. -- 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/1073372 Title: Xorg produces high CPU usage after a few days Status in “xorg” package in Ubuntu: Confirmed Bug description: Thinkpad X220 (Intel video, chipsets, etc) After a few days of uptime and usage on this laptop, the xorg process will start randomly (but consistently over time) producing high CPU usage, even with all applications closed. CPU according to top will vary between about 10% and 90%, and at high CPU times, the system fans will be running rather high. Also, the UIs will slow down and there will be a lot of latency on keypresses (sometimes up to 1 second), with the occasional loss of keypresses. In gnome-terminal, this has the effect of feeling like you're over a cellular modem, even on a local terminal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,move,gnomecompat,compiztoolbox,imgpng,mousepoll,regex,place,snap,unitymtgrabhandles,resize,grid,session,animation,workarounds,expo,wall,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Tue Oct 30 16:30:09 2012 DistUpgraded: 2012-09-15 22:41:29,902 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller MachineType: LENOVO 4286CTO ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-09-16 (44 days ago) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET61WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1073372/+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 1073372] Re: Xorg produces high CPU usage after a few days
Looks like the description matches my experience on ThinkPad T420s, with Intel card. -- 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/1073372 Title: Xorg produces high CPU usage after a few days Status in “xorg” package in Ubuntu: Confirmed Bug description: Thinkpad X220 (Intel video, chipsets, etc) After a few days of uptime and usage on this laptop, the xorg process will start randomly (but consistently over time) producing high CPU usage, even with all applications closed. CPU according to top will vary between about 10% and 90%, and at high CPU times, the system fans will be running rather high. Also, the UIs will slow down and there will be a lot of latency on keypresses (sometimes up to 1 second), with the occasional loss of keypresses. In gnome-terminal, this has the effect of feeling like you're over a cellular modem, even on a local terminal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,move,gnomecompat,compiztoolbox,imgpng,mousepoll,regex,place,snap,unitymtgrabhandles,resize,grid,session,animation,workarounds,expo,wall,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Tue Oct 30 16:30:09 2012 DistUpgraded: 2012-09-15 22:41:29,902 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller MachineType: LENOVO 4286CTO ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-09-16 (44 days ago) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET61WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1073372/+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 1060059] Re: Xorg crashed with SIGABRT in ResFindAllRes()
I'm reproducing it as well here, up-to-date quantal, ThinkPad T420s with only Intel HD enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1060059 Title: Xorg crashed with SIGABRT in ResFindAllRes() Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Quantal: Triaged Bug description: Crashed as soon as xrestop is run ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Tue Oct 2 17:43:30 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExecutableTimestamp: 1348785641 GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV730XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21b2] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2) MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcCwd: /etc/X11 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-16-generic root=UUID=e9e28db6-3c36-4e13-bea1-017b97bd28d8 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () FindAllClientResources () ?? () ?? () ?? () Title: Xorg crashed with SIGABRT in FindAllClientResources() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/30/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1060059/+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
