[Desktop-packages] [Bug 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep
** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu) -- 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/1994125 Title: [Solved] Gnome desktop freezes after reboot or resume after sleep Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F wireplumber /dev/snd/controlC1: robert 2224 F wireplumber /dev/snd/seq:robert 2221 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware
[Desktop-packages] [Bug 1994125] [NEW] [Solved] Gnome desktop freezes after reboot or resume after sleep
You have been subscribed to a public bug: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F wireplumber /dev/snd/controlC1: robert 2224 F wireplumber /dev/snd/seq:robert 2221 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd.
[Desktop-packages] [Bug 1987928] Re: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987928 Title: gnome-control-center closes with Gtk Gio Error when trying to access keyboard shortcut details Status in gnome-control-center package in Ubuntu: Expired Bug description: Hello, I report this issue on behalf of someone else, I can't use the bug reporter on the Ubuntu machine. The same issue has been reported by other people on other places: Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728 Bug report for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493 --- lsb_release -rd --- Description: Ubuntu 22.04.1 LTS Release: 22.04 --- end lsb_release -rd --- --- apt-cache policy gnome-control-center --- gnome-control-center: Installé : 1:41.7-0ubuntu0.22.04.4 Candidat : 1:41.7-0ubuntu0.22.04.4 Table de version : *** 1:41.7-0ubuntu0.22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu13.2 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:41.4-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages --- end apt-cache policy gnome-control-center --- Issue started after update of gnome-control-center on 24 August 2022 (1:41.7-0ubuntu0.22.04.1 → 1:41.7-0ubuntu0.22.04.4) --- Snippet from /var/log/apt/history.log --- Start-Date: 2022-08-24 16:56:32 Commandline: /usr/sbin/synaptic Requested-By: michel (1003) Upgrade: gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubun tu0.22.04.4), thunderbird:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13. 0+build1-0ubuntu0.22.04.1), libpam-fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.0 4.1), isc-dhcp-common:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), thunderbir d-locale-en:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubun tu0.22.04.1), thunderbird-locale-fr:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1 , 1:91.13.0+build1-0ubuntu0.22.04.1), isc-dhcp-client:amd64 (4.4.1-2.3ubuntu2.1, 4.4.1-2.3ubuntu2.2), fprintd:amd64 (1.94.2-1, 1.94.2-1ubuntu0.22.04.1), gnome-c ontrol-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), gno me-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.4), thun derbird-locale-en-gb:amd64 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+bui ld1-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:91.12.0+build1-0ubuntu0 .22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1), thunderbird-gnome-support:amd6 4 (1:91.12.0+build1-0ubuntu0.22.04.1~mt1, 1:91.13.0+build1-0ubuntu0.22.04.1) End-Date: 2022-08-24 16:57:15 --- end /var/log/apt/history.log --- The user opens gnome-control-center, the main window appears. The user selects the keyboard tab and click on the arrow to open the keyboard shortcut binding interface. The user expects the interface for binding keyboard shortcuts to open. Instead, the main gnome-control-center window closes and outputs the following error in the terminal: --- output of gnome-control-center --- (gnome-control-center: 647357): GLib-GIO-ERROR **: 00:31:19.451: Settings schema 'org.gnome.settin gs-daemon.plugins.media-keys' does not contain a key named 'screenshot' Trappe pour point d'arrêt et de trace (core dumped) --- end output of gnome-control-center --- It was working some time before the update to 1:41.7-0ubuntu0.22.04.4. Downgrading the package to 1:41.4-1ubuntu13.2 doesn't fix the issue. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987928/+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 1988271] Re: Conversion to maildir fails
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1988271 Title: Conversion to maildir fails Status in thunderbird package in Ubuntu: Expired Bug description: The conversion of the mail storage format from mbox to maildir for my accounts and local folder fails: Account Settings -> Local Folders -> Message Storage Type -> File per message -> Continue -> Conversion failed Thunderbird version is 91.11.0 (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-22.22~20.04.1-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: pia 407619 F pulseaudio /dev/snd/controlC1: pia 407619 F pulseaudio /dev/snd/controlC0: pia 407619 F pulseaudio BuildID: 20220628000715 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Aug 31 09:46:32 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 'utf-8' codec can't decode byte 0xe4 in position 1246: invalid continuation byte DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2015-11-05 (2490 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 141.43.207.254 dev wlp2s0 proto dhcp src 141.43.206.95 metric 303 141.43.204.0/22 dev wlp2s0 proto dhcp scope link src 141.43.206.95 metric 303 MostRecentCrashID: bp-fd50f7d7-4956-4fdf-863c-4559b0210616 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "68.4.1" (prefs.js) security.sandbox.plugin.tempDirSuffix: "9eb2b85f-0d3f-4a8d-befb-123c16cf0c0a" (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile2PrefSources: prefs.js Profile2Prefs: accessibility.typeaheadfind.flashBar: 0 (prefs.js) extensions.lastAppVersion: "68.2.2" (prefs.js) places.history.expiration.transient_current_max_pages: 112348 (prefs.js) security.sandbox.plugin.tempDirSuffix: "f8e1a9f8-d09f-45f0-9e5e-e552e5fa973e" (prefs.js) Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile2 - LastVersion=68.2.2/20191201113928 (Out of date) Profile1 - LastVersion=68.4.1/20200108224327 (Out of date) Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to focal on 2020-09-10 (719 days ago) dmi.bios.date: 05/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: LENOVO dmi.bios.version: R1AET28W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20T6000MGE 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.4 dmi.modalias: dmi:bvnLENOVO:bvrR1AET28W(1.04):bd05/03/2020:br1.4:efr1.4:svnLENOVO:pn20T6000MGE:pvrThinkPadE14Gen2:rvnLENOVO:rn20T6000MGE:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20T6_BU_Think_FM_ThinkPadE14Gen2: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20T6000MGE dmi.product.sku: LENOVO_MT_20T6_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T14:28:39.455024 To
[Desktop-packages] [Bug 1988320] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1988320 Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: Expired Bug description: Please check into this after upgrading to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hacks 869 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Wed Aug 31 16:26:33 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-07-16 (46 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.8.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.8.0/24 dev wlp2s0 proto kernel scope link src 192.168.8.104 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-08-31 (0 days ago) dmi.bios.date: 12/28/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Caltech dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd12/28/2015:br1.10:efr1.10:svnAcer:pnAspireone1-131:pvrV1.10:rvnAcer:rnCaltech:rvrV1.10:cvnAcer:ct10:cvrChassisVersion:skuAO1-131_106C_1.10: dmi.product.family: BSW dmi.product.name: Aspire one 1-131 dmi.product.sku: AO1-131_106C_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988320/+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 1995231] [NEW] image viewer is not showing some JPEG images
Public bug reported: eog is not displaying some JPEG images which is fine with last 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: eog 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 08:16:18 2022 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1995231 Title: image viewer is not showing some JPEG images Status in eog package in Ubuntu: New Bug description: eog is not displaying some JPEG images which is fine with last 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: eog 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 31 08:16:18 2022 SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1995231/+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 1993751] Re: Rhythmbox won't launch
I just checked my laptop, and it also had those 2 installed. Not sure why that one works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1993751 Title: Rhythmbox won't launch Status in gcc-11 package in Ubuntu: New Status in rhythmbox package in Ubuntu: Incomplete Bug description: $ rhythmbox (gst-plugin-scanner:19184): GLib-GObject-WARNING **: 16:32:52.316: type name '-a-png-encoder-pred' contains invalid characters (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.316: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.316: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-WARNING **: 16:32:52.353: type name '-a-png-encoder-pred' contains invalid characters (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.353: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.353: g_type_set_qdata: assertion 'node != NULL' failed [2:02:31.297360952] [19184] ERROR Controls controls.cpp:689 Control 0x not in the idmap [2:02:31.297376891] [19184] FATAL default controls.cpp:654 assertion "validate()" failed in ControlInfoMap() ^C Hope this helps ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: rhythmbox 3.4.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Oct 20 16:33:01 2022 InstallationDate: Installed on 2022-01-14 (279 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rhythmbox UpgradeStatus: Upgraded to kinetic on 2022-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1993751/+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 1993751] Re: Rhythmbox won't launch
Turns out it was that package, or cpp-11, in 22.10 repo that was causing my issue as I'm now able to start it after removing cpp-11 & g++-11 packages. ** Also affects: gcc-11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1993751 Title: Rhythmbox won't launch Status in gcc-11 package in Ubuntu: New Status in rhythmbox package in Ubuntu: Incomplete Bug description: $ rhythmbox (gst-plugin-scanner:19184): GLib-GObject-WARNING **: 16:32:52.316: type name '-a-png-encoder-pred' contains invalid characters (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.316: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.316: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-WARNING **: 16:32:52.353: type name '-a-png-encoder-pred' contains invalid characters (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.353: g_type_set_qdata: assertion 'node != NULL' failed (gst-plugin-scanner:19184): GLib-GObject-CRITICAL **: 16:32:52.353: g_type_set_qdata: assertion 'node != NULL' failed [2:02:31.297360952] [19184] ERROR Controls controls.cpp:689 Control 0x not in the idmap [2:02:31.297376891] [19184] FATAL default controls.cpp:654 assertion "validate()" failed in ControlInfoMap() ^C Hope this helps ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: rhythmbox 3.4.6-2ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Oct 20 16:33:01 2022 InstallationDate: Installed on 2022-01-14 (279 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: rhythmbox UpgradeStatus: Upgraded to kinetic on 2022-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1993751/+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 1995073] Re: Ubuntu 22.10 deja-dup throws exception when login
The packaging suggests (but does not recommend) python3-pydrive. Which means it isn't installed by default when you install deja-dup. (Which I believe is done so that python3-pydrive doesn't have to be promoted to main.) But the packaging does also set it up so that Deja Dup *should* have offered to install python3-pydrive when you tried to back up and it wasn't installed... So that looks like the bug here. Wonder why it didn't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1995073 Title: Ubuntu 22.10 deja-dup throws exception when login Status in deja-dup package in Ubuntu: New Bug description: Can't login and restore from GDrive. See attached picture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1995073/+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 1995222] [NEW] Thunderbird; Cannot create filters does not work properly
Public bug reported: Am not able to create filters in thunderbird because the moveto field does not offer a field. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user980 F pulseaudio /dev/snd/controlC2: user980 F pulseaudio /dev/snd/controlC0: user980 F pulseaudio BuildID: 20220906224751 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 30 12:29:20 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-10-27 (3 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.0.1 dev enp1s0 proto dhcp metric 100 169.254.0.0/16 dev enp1s0 scope link metric 1000 192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.15 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 Profile0PrefSources: prefs.js Profile0Prefs: extensions.lastAppVersion: "102.2.2" (prefs.js) font.internaluseonly.changed: false (prefs.js) network.trr.blocklist_cleanup_done: true (prefs.js) places.database.lastMaintenance: 1666910472 (prefs.js) privacy.purge_trackers.date_in_cookie_database: "0" (prefs.js) Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.2.2/20220906224751 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2013 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: I7KT31AUS dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:br1.31:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:skuLENOVO_MT_1011: dmi.product.family: IdeaCentre dmi.product.name: 10117 dmi.product.sku: LENOVO_MT_1011 dmi.product.version: Lenovo H535 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1995222 Title: Thunderbird; Cannot create filters does not work properly Status in thunderbird package in Ubuntu: New Bug description: Am not able to create filters in thunderbird because the moveto field does not offer a field. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:102.2.2+build1-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user980 F pulseaudio /dev/snd/controlC2: user980 F pulseaudio /dev/snd/controlC0: user980 F pulseaudio BuildID: 20220906224751 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 30 12:29:20 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:306 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-10-27 (3 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.0.1 dev enp1s0 proto dhcp metric 100 169.254.0.0/16 dev enp1s0 scope link metric 1000 192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.15
[Desktop-packages] [Bug 1990189] Re: brlttty claiming CH341 usbtty device blocking access
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: brltty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1990189 Title: brlttty claiming CH341 usbtty device blocking access Status in brltty package in Ubuntu: Confirmed Bug description: While this problem seems to have been fixed for FTDI and CP210 based devices CH340/CH341 based (and possibly other USB serial adapters) are unusable except by brltty. Workaround: disable brltty sudo systemctl stop brltty-udev.service sudo systemctl mask brltty-udev.service sudo systemctl stop brltty.service sudo systemctl disable brltty.service [139099.253351] usb 1-2.1.2: new full-speed USB device number 17 using xhci_hcd [139099.370766] usb 1-2.1.2: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63 [139099.370777] usb 1-2.1.2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [139099.370782] usb 1-2.1.2: Product: USB2.0-Serial [139099.414885] ch341 1-2.1.2:1.0: ch341-uart converter detected [139099.429265] usb 1-2.1.2: ch341-uart converter now attached to ttyUSB0 [139100.045076] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input24 [139100.782817] usb 1-2.1.2: usbfs: interface 0 claimed by ch341 while 'brltty' sets config #1 [139100.786100] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [139100.786136] ch341 1-2.1.2:1.0: device disconnected [143917.740171] usb 1-2.1.2: USB disconnect, device number 17 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" ProblemType: BugDistroRelease: Ubuntu 22.04 Package: brltty 6.4-4ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Sep 19 12:01:21 2022 InstallationDate: Installed on 2022-08-23 (27 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1990189/+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 1995216] Re: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system
The same exact behavior HAPPENS if I switch from A HDMI to DisplayPort CABLE using the same system and methodology -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+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 1995216] Re: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system
The same exact behavior if I switch from HDMI to DisplayPort using the same system and methodology. -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+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 1995216] Re: X forgets monitor configuration when unplugged and replugged on a live system
** Attachment added: "The more I'll move it around the more "artifacts" will be displayed yet the resolution is now fine on both screens." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+attachment/5627894/+files/04-thisistheweirdest.png ** Summary changed: - X forgets monitor configuration when unplugged and replugged on a live system + X forgets monitor configuration when HDMI cable is unplug and then replugged in a running system. ** Summary changed: - X forgets monitor configuration when HDMI cable is unplug and then replugged in a running system. + X forgets monitor configuration when HDMI cable was unplugged and then re-plugged in a running system ** Summary changed: - X forgets monitor configuration when HDMI cable was unplugged and then re-plugged in a running system + X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1995216] Re: X forgets monitor configuration when unplugged and replugged on a live system
** Attachment added: "Based on 02, I need to move the monitor to match their physical setup and this is what happens on screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+attachment/5627893/+files/03-thisisgettingweird.png -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+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 1995216] Re: X forgets monitor configuration when unplugged and replugged on a live system
** Attachment added: "This is what DISPLAYS shows me after I immediately replugged the HDMI cable" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+attachment/5627892/+files/02-lostconfigafterreplug.png -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1995216/+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 1995216] [NEW] X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system
Public bug reported: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Sun Oct 30 12:25:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-50-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:0b04] InstallationDate: Installed on 2022-06-02 (149 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) LightdmDisplayLog: (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow (EE) event6 - Metadot - Das Keyboard Das Keyboard: client bug: event processing lagging behind by 36ms, your system is too slow MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_idi202@/vmlinuz-5.15.0-50-generic root=ZFS=rpool/ROOT/ubuntu_idi202 ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5809 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy resolution ubuntu ** Attachment added: "My regular monitor setup consisting of 2x screens in PORTRAIT mode" https://bugs.launchpad.net/bugs/1995216/+attachment/5627871/+files/01-myregularsetup.png -- 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/1995216 Title: X forgets monitor configuration when HDMI cable was unplugged and then re-plugged on a running system Status in xorg package in Ubuntu: New Bug description: Running 22.04.1, I am using a the following (See 01.png) monitor setup. When I unplug the HDMI cable from my video card and plug it back, the monitor has lost it's orientation (See 02.png) If I then reconfigure the monitors I get the following (See 03.png). However the changes are taken into consideration and the display is back to normal. Yet if I continue dragging the monitors around in that same interface odd interface behavior start happening more frequently (See 04.png). So this could perhaps be split into 2 bugs. I will let you decide. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 968213] Re: Too many icons in Gnome Shell Activities Overview require ellipses
** Changed in: gnome-shell Status: Unknown => New -- 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/968213 Title: Too many icons in Gnome Shell Activities Overview require ellipses Status in GNOME Shell: New Status in One Hundred Papercuts: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: Several apps in the default Ubuntu 17.04 or 17.10 install have Ellipses when shown in GNOME Shell's Activities Overview. This was made worse by switching GNOME Shell to use the Ubuntu font because the Ubuntu font is a bit wider than GNOME's default Cantarell font so some apps that didn't require ellipses in 17.04 require them now in 17.10 Alpha. The upstream GNOME bug proposes that apps names be allowed to use 2 lines. This is similar to what the Settings app (gnome-control-center) does. This is also really bad for languages that use more characters than English. Original Bug Title -- Gnome Shell Activities Overview should show full names on mouse hover Original Bug Report --- The title says it all --- especially when choosing recent documents, if they start with the same say 12 or 14 letters, it's impossible to differentiate them (see attached screenshot). When mouse is hovering an icon, the full name of the application/document should be shown. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/968213/+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 1910220] Re: Characters from dead keys shown in plan view in password field on login screen
** Changed in: gnome-shell Status: Unknown => New -- 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/1910220 Title: Characters from dead keys shown in plan view in password field on login screen Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) apt-cache policy gdm3 gdm3: Installed: 3.38.1-2ubuntu1.1 Candidate: 3.38.1-2ubuntu1.1 Version table: *** 3.38.1-2ubuntu1.1 500 500 http://se.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.38.1-2ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 3) I expect all characters, even those from dead keys, to be hidden the same ways as other characters 4) When using dead keys to add accents to letters on the password prompt on the login screen, before the letter the dead key is intended for is typed, the special characters from the dead keys are displayed in plain sight, instead of being obscured by dots as other letters and characters are. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gdm3 3.38.1-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 12:51:19 2021 InstallationDate: Installed on 2018-11-26 (770 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: Upgraded to groovy on 2020-11-01 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1910220/+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 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/501 --- lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-10-24 (1395 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (3 days ago) UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787822/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Bug description: [Impact] What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. [Test Case] Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Then install gnome-shell from bionic-proposed, reboot, and find that an added input source now is effective instantly without any of the mentioned workarounds. [Regression Potential] Minimal. The fix consists of a simple upstream commit which has been in use as from GNOME 3.32. [Other info] Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1918613] Re: [FFe] GDM background configurable with gsettings
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1918613 Title: [FFe] GDM background configurable with gsettings Status in gdm: Fix Released Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: [Description] Customization of the greeter is a requirement from Corporate customers. Currently the background (plain color or image) of the greeter is hard coded in the style embedded in the theme. Customizing this background requires to extract the style sheet from gnome-shell gresource file, modify it manually, recompile and deploy the new gresource, and add an alternative to it. This feature adds 4 gsettings keys to make the background of the greeter configurable via gsettings. The default value defined the in the theme is used for keys that are not set. [Rationale] Corporate customers use LTS releases and ultimately this will be released for 20.04. This changeset needs to land in hirsute before it can be SRUd into prior Ubuntu LTS releases. So we would like to submit this FFe to get it into Hirsute first. [Risks] The changeset is minimal, isolated and can be easily reverted. In case of error in the code, GDM will fail to load and it will be immediately visible. [Build] Builds and tested successfully locally. Besides the updated JS is not compiled as part of build. [Upstream Issue] https://gitlab.gnome.org/GNOME/gdm/-/issues/684 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1918613/+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 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages()
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from process_ice_messages() Status in GNOME Shell: Fix Released Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: The error occurred when I ran apt update/upgrade in a terminal window after logging in. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 09:03:52 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'41.3'" b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'hu')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['gnome-initial-setup']" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2022-02-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_context_terminate () from /lib/x86_64-linux-gnu/libmutter-9.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+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 1962566] Re: gnome-shell crash after resume from suspend in gdm/util.js:154
** Changed in: gnome-shell Status: Unknown => New -- 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/1962566 Title: gnome-shell crash after resume from suspend in gdm/util.js:154 Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Fix Released Bug description: ### Affected version * Your OS and version: ubuntu 22.04 (dev series, before release) * Affected GNOME Shell version: 41.3-1ubuntu1 * Issue appears in Wayland ### Bug summary Sometimes gnome-shell hangs when I open the laptop to login from the suspend state, preventing the rest of gdm to load. Because I am running wayland, I cannot open another tty either. If I close the laptop lid again and wait 30s or so and reopen to retry, it will work. ### Steps to reproduce Not 100% reproducible, happens sometimes. 1. open laptop to login from suspend 2. see login screen with time and all looks normal but is unresponsive ### What happened The login screen is hung and unresponsive to clicks/touches(touchscreen)/any keyboard input events. ### What did you expect to happen The login screen should be responsive to input. ### Relevant logs, screenshots, screencasts etc. After a successful login, I see a crash in journalctl: ``` Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.> _injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25 _makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17 ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31 _init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30 _ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28 _showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14 vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14 ``` ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: fprintd 1.94.2-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Mar 1 09:58:16 2022 ExecutablePath: /usr/libexec/fprintd ExecutableTimestamp: 1645749862 InstallationDate: Installed on 2020-06-29 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/libexec/fprintd ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: fprintd UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1962566/+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 1965897] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1965897 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from meta_window_unmanage() from meta_display_unmanage_windows() Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/0f9ebdf291c30c238c6f29d22b7d503ef8910bdd --- Crashed after I tried to restart the shell with the 'r' command. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 10:59:42 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-25 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/bin/gnome-shell RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0 shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() UpgradeStatus: Upgraded to jammy on 2022-03-14 (7 days ago) UserGroups: sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965897/+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 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969558/+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 1972113] Re: Ubuntu 22.04 screen keyboard shows but does not accept input
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1972113 Title: Ubuntu 22.04 screen keyboard shows but does not accept input Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Released Bug description: Dell Venue 11 Pro Windows Tablet, (Touchscreen - no keyboard/mouse) Screen keyboard works as expected on 21.10, on upgrade to 22.04 (or clean install) On screen keyboard works as expected in applications,but shows and does not accept input on authentication/logon prompts, keyboard does not appear to respond to any activity (Uppercase/special characters) 22.04 does not show screen keyboard at all during install (Can only be installed with physical keyboard attached) setting WaylandEnable=false in /etc/gdm3/custom.conf and restarting display manager (sudo systemctl restart gdm3) does not help. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1972113/+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 1973351] Re: Screenshot tool freezes on Chromium with secondary menu open
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1973351 Title: Screenshot tool freezes on Chromium with secondary menu open Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: In Progress Status in gnome-shell source package in Kinetic: Fix Released Bug description: Hi, I have found a behavior that I'm able to reproduce consistently (I have not tried with other browsers). Here are the steps to reproduce (should work on a clean Ubuntu 22.04 installation): 1. Install Chromium (apt install chromium-browser) 2. Open chromium 3. Open a website 4. Right click on an empty section of the website, so the secondary menu will open (the one that contains the "Back", "Reload", "Save as..." options) 5. Press the PrntScrn key, making the new screenshot UI to appear The screenshot UI freezes and cannot be closed neither by pressing Esc nor any other key combination. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973351/+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 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
** Changed in: gnome-shell Status: Unknown => New -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]
** Changed in: gnome-shell Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969893 Title: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: Impact == GNOME Shell crashes when it's restarted on Xorg. (There is no option to restart GNOME Shell on Wayland.) Test Case = Install the update On the login screen, select your name. Click the gear button in the lower right and choose Ubuntu on Xorg Enter your password to finish logging in. Open the file browser. Press Alt-F2. In the dialog, enter 'r' GNOME Shell should restart without a crash message. Your file browser window should remain open. What Could Go Wrong === See the master bug for this update LP: #1976381 More Details gnome-shell crashes with SIGSEGV just after logging: gnome-shell[3117]: JS ERROR: TypeError: window is null _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16 Examples: https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206 https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206 https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0 Tracking in: https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470 ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969893/+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 1973638] Re: gnome-shell 42 leaks tens of megabytes with every screenshot
** Changed in: gnome-shell Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1973638 Title: gnome-shell 42 leaks tens of megabytes with every screenshot Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: [Impact] gnome-shell's memory usage grows by tens of megabytes with every screenshot. A few screenshots make it 100MB larger and a few dozen screenshots make it 1GB larger. [Test Plan for GNOME Shell Fix] TODO [Test Plan for GJS Fix] 1. Log into gnome-shell. 2. Measure its real memory usage: grep RSS /proc/`pidof gnome-shell`/status 3. Take 20 full screen screenshots by pressing PrtScn each time. No need to save them anywhere. 4. Measure the memory usage again. Expected: Memory usage grows a little but growth does not exceed a few hundred megabytes. It should level off after a while and sometimes even shrink due to garbage collection. Observed: Memory usage grows without bounds, easily exceeding 1GB after about 20 screenshots (depending on screen resolution). It never shrinks significantly. [Where problems could occur] Since the fix affects GJS, problems could occur in any part of gnome- shell. [Other Info] This leak requires multiple fixes to minimize the memory usage. For the moment we are only aiming to fix the main GJS portion of the bug that allows memory usage to exceed 1GB. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1973638/+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 1970636] Re: Top bar menus are unavailable on login/lock screen
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1970636 Title: Top bar menus are unavailable on login/lock screen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: In a fresh new install of 22.04, In unlock session screen, it is impossible to activate on screen keyboard via accessibility menu. It was ok on 21.10. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970636/+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 1987631] Re: Screencast only records one second
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+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 1987734] Re: Icon grid is too narrow when Ubuntu Dock is enabled
** Changed in: gnome-shell Status: Unknown => New -- 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/1987734 Title: Icon grid is too narrow when Ubuntu Dock is enabled Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Bug description: Icon grid is too narrow (in gnome-shell 43 on kinetic) when Ubuntu Dock is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987734/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
I'm really new to the "bug"(?) and a bit overwhelmed about all the information here. The last post is over one year ago but the ticket is still open. Can someone please give a summary about the current state of the problem and maybe a workaround. I'm not sure but it seems to me that this really fresh upstream ticket (reported by me as one of the upstream maintainers) for "backintime" is related to it. https://github.com/bit-team/backintime/issues/1348 Can you confirm that this upstream ticket is related to the launchpad ticket here? ** Bug watch added: BackInTime Issues #1348 https://github.com/bit-team/backintime/issues/1348 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Released Status in Boot-Repair: Fix Released Status in GNOME Terminal: New Status in HPLIP: New Status in LightDM GTK Greeter Settings: New Status in OS-Uninstaller: Fix Released Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu
[Desktop-packages] [Bug 1993889] Re: nautilus does not launch
Also affects an upgraded Ubuntu from 22.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993889 Title: nautilus does not launch Status in nautilus package in Ubuntu: Confirmed Bug description: Problem: nautilus does not launch after it was closed previously. Expectation: Close nautilus, start nautilus again -> new nautilus window spawns. What happens: nautilus does not launch a second time. The cursor spins, but no window opens. Observations: the nautilus process does not get terminated properly. There is a nautilus process remaining with almost no CPU consumption. Workarounds: Killing the process and starting nautilus again works. Starting it via console and exiting it via X button does not end the task in the terminal. CTRL+C terminates the process and it's restarting fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:03:06 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)' InstallationDate: Installed on 2022-10-22 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1995207] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627853/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627854/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple
I reinstalled Ubuntu 22.10 and I can see no issues. It seems you were right Daniel. Please close this bug, nothing to see here. -- 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/1994019 Title: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple Status in gnome-shell package in Ubuntu: New Bug description: The same as in bug 1994000. I removed the oibaf PPAs altogether and now should be running the standard distro packages. The situation has not been solved. I also attach the prevboot file. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 24 11:27:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-26 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+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 1995207] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627851/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627852/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627850/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] [NEW] [22.10] gnome-shell: page allocation failure
Public bug reported: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287 mapped:352660 shmem:166458 pagetables:11885 bounce:0 kernel_misc_reclaimable:0 free:5048298 free_pcp:2656 free_cma:0 oct 30 13:36:19 z16 kernel: Node 0 active_anon:5432kB inactive_anon:3821164kB active_file:1793324kB inactive_file:3676728kB unevictable:856kB isolated(anon):0kB isolated(file):0kB mapped:1410640kB dirty:988kB writeback:8kB shmem:665832kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:24076kB pagetables:47540kB
[Desktop-packages] [Bug 1988393] Re: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
** Changed in: gjs Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1988393 Title: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 Status in gjs: Fix Released Status in gjs package in Ubuntu: In Progress Bug description: I'm seeing this in everyone's kinetic logs: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 and it appears gjs is the only place where too many arguments are provided. To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1988393/+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 1995135] Re: WiFi captive portals stopped working after Kinetic upgrade
*** This bug is a duplicate of bug 1995134 *** https://bugs.launchpad.net/bugs/1995134 ** This bug has been marked a duplicate of bug 1995134 WiFi captive portals stopped working after Kinetic upgrade -- 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/1995135 Title: WiFi captive portals stopped working after Kinetic upgrade Status in gnome-shell package in Ubuntu: New Bug description: After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer recognizes captive portals. Attempting to run /usr/libexec/gnome-shell-portal-helper produces this output: (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS module 'fileUtils' found in search path @resource:///org/gnome/shell/portalHelper/main.js:13:30 @:1:14 This may be normal because of the environment, but it is the best I have to go on now. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 19:26:44 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-08-06 (1179 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995135/+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 1995202] Re: Wacom input devices change button assignment depending on application
** Package changed: ubuntu => mutter (Ubuntu) -- 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/1995202 Title: Wacom input devices change button assignment depending on application Status in mutter package in Ubuntu: New Bug description: Ubuntu 22.04.1 LTS Expected: Wacom pen and mouse should send a middle and right mouseclick in every application. The key assignment should be done once in system-settings. Instead: Depending on the application, wacom input devices (pen, mouse...) change the assignment of the buttons. E.g. in firefox (snap) or blender the right wacom mouse button works as expected, in nautilus or libre offce it does not. Changing the system-settings for the wacom devices make it work in nautilus, but break it in firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter-common 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 30 12:09:13 2022 InstallationDate: Installed on 2020-08-26 (794 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-08-15 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1995202/+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 1995202] [NEW] Wacom input devices change button assignment depending on application
You have been subscribed to a public bug: Ubuntu 22.04.1 LTS Expected: Wacom pen and mouse should send a middle and right mouseclick in every application. The key assignment should be done once in system-settings. Instead: Depending on the application, wacom input devices (pen, mouse...) change the assignment of the buttons. E.g. in firefox (snap) or blender the right wacom mouse button works as expected, in nautilus or libre offce it does not. Changing the system-settings for the wacom devices make it work in nautilus, but break it in firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter-common 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 30 12:09:13 2022 InstallationDate: Installed on 2020-08-26 (794 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-08-15 (75 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Wacom input devices change button assignment depending on application https://bugs.launchpad.net/bugs/1995202 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995073] Re: Ubuntu 22.10 deja-dup throws exception when login
Yes it does. Why is this missing from the distro? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1995073 Title: Ubuntu 22.10 deja-dup throws exception when login Status in deja-dup package in Ubuntu: New Bug description: Can't login and restore from GDrive. See attached picture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1995073/+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 1982584] Re: wacom invisible cursor on startup, xorg 22.04
I have the same problem - any ongoing solutions ? You can override the problem with a second plugged mouse too, if you move it only one pixel at after startup the mousepointer appears and stay until shutdown. Maybe the problem is to initialise the pointer when using wacom ? The Wacom pointer is working but you can't see it, unless you bring the pointer to be visible by override it by another device. -- 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/1982584 Title: wacom invisible cursor on startup, xorg 22.04 Status in mutter package in Ubuntu: Confirmed Bug description: With a Wacom One attached, the mouse cursor doesn't show. The mouse cursor can be made to show if, after logging in using the keyboard, you type the super-key, type "zoom", and arrow key over to zoom, and activate the zoom functionality with the enter key. Then the mouse cursor appears once your view is zoomed in, and you can deactivate the zoom and go about everything as normal with the mouse cursor working normally again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 22 06:45:04 2022 InstallationDate: Installed on 2022-01-30 (172 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-05-16 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982584/+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 1995199] [NEW] Renaming home folders corrupts side panel behavior
Public bug reported: Hi! Renamed home folder is not synchronized with side panel. So, side panel's link does not work after renaming home folders. Expected, opening renamed folder from side panel. Due to lack of customization of side panel, links can not be changed to the new renamed location. It is not only my opinion that the side panel must have more customization features, including resizing and disabling it. Ubuntu 22.10 5.19.0-23-generic nautilus-data/kinetic,kinetic,now 1:43.0-1ubuntu1 all [installed,automatic] nautilus-extension-gnome-terminal/kinetic,now 3.46.2-1ubuntu1 amd64 [installed,automatic] nautilus/kinetic,now 1:43.0-1ubuntu1 amd64 [installed,automatic] ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-10-30 10-18-07.png" https://bugs.launchpad.net/bugs/1995199/+attachment/5627830/+files/Screenshot%20from%202022-10-30%2010-18-07.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1995199 Title: Renaming home folders corrupts side panel behavior Status in nautilus package in Ubuntu: New Bug description: Hi! Renamed home folder is not synchronized with side panel. So, side panel's link does not work after renaming home folders. Expected, opening renamed folder from side panel. Due to lack of customization of side panel, links can not be changed to the new renamed location. It is not only my opinion that the side panel must have more customization features, including resizing and disabling it. Ubuntu 22.10 5.19.0-23-generic nautilus-data/kinetic,kinetic,now 1:43.0-1ubuntu1 all [installed,automatic] nautilus-extension-gnome-terminal/kinetic,now 3.46.2-1ubuntu1 amd64 [installed,automatic] nautilus/kinetic,now 1:43.0-1ubuntu1 amd64 [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995199/+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 1995196] [NEW] package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1
Public bug reported: From a release upgrade from 22.04 to 22.10 (many moons ago) I had previously enabled pipewire on the 22.04 install with the following: sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth libspa-0.2-jack sudo apt install wireplumber pipewire-media-session- sudo apt remove pulseaudio-module-bluetooth systemctl --user --now enable wireplumber.service ProblemType: Package DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 28 07:09:19 2022 ErrorMessage: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2022-10-19 (9 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20V9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: bluez Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to kinetic on 2022-10-28 (0 days ago) dmi.bios.date: 05/10/2022 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: F9CN50WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: ThinkBook 13s G2 ITL dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrF9CN50WW:bd05/10/2022:br1.50:efr1.44:svnLENOVO:pn20V9:pvrThinkBook13sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG2ITL:skuLENOVO_MT_20V9_BU_idea_FM_ThinkBook13sG2ITL: dmi.product.family: ThinkBook 13s G2 ITL dmi.product.name: 20V9 dmi.product.sku: LENOVO_MT_20V9_BU_idea_FM_ThinkBook 13s G2 ITL dmi.product.version: ThinkBook 13s G2 ITL dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 64:79:F0:9D:09:A8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:21280 acl:17 sco:0 events:3348 errors:0 TX bytes:816597 acl:17 sco:0 commands:3319 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic ** Attachment added: "bt journal" https://bugs.launchpad.net/bugs/1995196/+attachment/5627802/+files/bt.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1995196 Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 Status in bluez package in Ubuntu: New Bug description: From a release upgrade from 22.04 to 22.10 (many moons ago) I had previously enabled pipewire on the 22.04 install with the following: sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth libspa-0.2-jack sudo apt install wireplumber pipewire-media-session- sudo apt remove pulseaudio-module-bluetooth systemctl --user --now enable wireplumber.service ProblemType: Package DistroRelease: Ubuntu 22.10 Package: bluez 5.65-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Oct 28 07:09:19 2022 ErrorMessage: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2022-10-19 (9 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20V9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: bluez Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1