[Desktop-packages] [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Looks like we even declared it fixed in bug 1945008. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2006059] Re: gdm requires a second login to start xorg session instead of wayland
All upstream references do seem to point to https://gitlab.gnome.org/GNOME/gdm/-/issues/733 but the "fix" for that is already in gdm3 version 41.3 and later. Yet the bug still happens. Some people are focussed on the cgroup errors that come before it, but I'm not sure if they're really related: https://www.reddit.com/r/gnome/comments/oknd9c/failed_to_start_application_launched_by/ ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #733 https://gitlab.gnome.org/GNOME/gdm/-/issues/733 ** Summary changed: - gdm requires a second login to start xorg session instead of wayland + systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Please try editing /usr/lib/systemd/user/org.gnome.Shell@x11.service and comment out: # ExecCondition=/bin/sh -c 'test "$XDG_SESSION_TYPE" = "%I" || exit 2' If that doesn't fix it then it would seem the issue is that Xorg hasn't been set up for us before we try to start gnome-shell on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Please also enable debug in /etc/gdm3/custom.conf and check for any crash reports in /var/crash/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
Comment #11 is still the same as comment #3: #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140206817158592) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=140206817158592) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140206817158592, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f8476b4b476 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #4 0x55b6f0c1b7aa in ?? () #5 #6 __strlen_avx2_rtm () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #7 0x7f846972092a in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #8 0x7f8469720567 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #9 0x7f8469aaeed0 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #10 0x7f8469aaa825 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #11 0x7f8469aac4c7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #12 0x7f84699930da in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #13 0x7f846997423f in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so #14 0x7f84767a7cf2 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #15 0x7f84767a4b3c in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #16 0x7f84767a4fee in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #17 0x7f84767b5c71 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #18 0x7f847679dc76 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #19 0x7f84767cceb2 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #20 0x7f84767cd233 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #21 0x7f84767cd4c6 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #22 0x7f84767cdf4f in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #23 0x7f84767d5343 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #24 0x7f8477a8bf80 in g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f84767d4e7b in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #26 0x7f84767d7e30 in cogl_blit_framebuffer () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #27 0x7f8477017b4d in clutter_stage_view_before_swap_buffer () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 #28 0x7f8476db6803 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #29 0x7f8476dbaf71 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #30 0x7f8476ea682b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #31 0x7f8477018258 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 #32 0x7f8476fe0da9 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-clutter-10.so.0 #33 0x7f8477a91d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f8477ae66c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f8477a912b3 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f8476e01909 in meta_context_run_main_loop () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ** Summary changed: - Multi-NVIDIA-GPU system crashes starting Wayland session + NVIDIA quad-GPU system crashes starting Wayland session -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.reg
[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Comment #11: Corrupt (bug 2015857) Comment #13: Missing some debug symbols (library unloaded?!) but getting closer: #10 0x7f9a42e7e71f in () at /lib/x86_64-linux-gnu/libX11.so.6 #11 0x7f9a434e4b50 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #12 0x7f9a434e4dc4 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #13 0x7f9a4347587f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #14 0x7f9a43475a19 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #15 0x7f9a43478a3f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #16 0x7f9a434e40e1 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0 #17 0x7f9a43713ebb in clutter_seat_handle_event_post () at /usr/lib/x86_64-linux-gnu/mutter-12/libmutter-clutter-12.so.0 #18 0x7f9a43707183 in _clutter_process_event () at /usr/lib/x86_64-linux-gnu/mutter-12/libmutter-clutter-12.so.0 Comment #14: SUCCESS! #11 0x7fed52e7e67f in XSync () at /lib/x86_64-linux-gnu/libX11.so.6 #12 0x7fed52e7e71f in () at /lib/x86_64-linux-gnu/libX11.so.6 #13 0x7fed534e4b50 in change_property (settings=, device=0x558b3a712470, property=, type=156, format=32, data=0x7ffe3f8a1b74, nitems=1) at ../src/backends/x11/meta-input-settings-x11.c:184 #14 0x7fed534e4dc4 in meta_input_settings_x11_set_speed (settings=settings@entry=0x558b3a7073e0, device=0x558b3a712470, speed=speed@entry=0) at ../src/backends/x11/meta-input-settings-x11.c:249 #15 0x7fed5347587f in settings_device_set_double_setting (value=0, func=0x7fed534e4d50 , device=, input_settings=0x558b3a7073e0) at ../src/backends/meta-input-settings.c:231 #16 settings_set_double_setting (value=0, func=0x7fed534e4d50 , unset_capabilities=CLUTTER_INPUT_CAPABILITY_TOUCHPAD, capabilities=CLUTTER_INPUT_CAPABILITY_POINTER, input_settings=0x558b3a7073e0) at ../src/backends/meta-input-settings.c:248 #17 update_device_speed (input_settings=0x558b3a7073e0, device=) at ../src/backends/meta-input-settings.c:511 #18 0x7fed53475a19 in apply_device_settings (input_settings=0x558b3a7073e0, device=0x0) at ../src/backends/meta-input-settings.c:1483 #19 0x7fed53478a3f in meta_input_settings_remove_device (input_settings=0x558b3a7073e0, device=0x558b3a6f8140) at ../src/backends/meta-input-settings.c:1629 --Type for more, q to quit, c to continue without paging-- #20 0x7fed534e40e1 in meta_seat_x11_handle_event_post (event=0x558b3d639db0, seat=0x558b3a6dbc70) at ../src/backends/x11/meta-seat-x11.c:836 #21 meta_seat_x11_handle_event_post (seat=0x558b3a6dbc70, event=0x558b3d639db0) at ../src/backends/x11/meta-seat-x11.c:810 #22 0x7fed53713ebb in clutter_seat_handle_event_post (seat=0x558b3a6dbc70, event=0x558b3d639db0) at ../clutter/clutter/clutter-seat.c:598 #23 0x7fed53707183 in _clutter_process_event (event=0x558b3d639db0) at ../clutter/clutter/clutter-main.c:919 #24 0x7fed5371aa20 in _clutter_stage_process_queued_events (stage=0x558b3a6e8690) at ../clutter/clutter/clutter-stage.c:757 #25 0x7fed53706f69 in clutter_do_event (event=event@entry=0x558b3d5860a0) at ../clutter/clutter/clutter-main.c:840 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-23.04 ** No longer affects: xorg-server (Ubuntu) ** No longer affects: xserver-xorg-input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gno
[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Ken, it sounds like zero is somehow out of range for "libinput Accel Speed" on your touchpad. Annoyingly this doesn't seem to be true for everyone -- mine allows -1.0 to 1.0. You can inspect the setting using the 'xinput' command... But I'll do a general fix for mutter/gnome-shell so it doesn't crash. -- 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/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2016244] [NEW] Intel Tiger Lake internal sound card not detected
You have been subscribed to a public bug: Huawei Matebook D14 with Core i3-1115G4 no sound card at all, "Dummy output" only, no even HDMI output. The codec is ESSX8336 I suppose. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 14:38:26 2023 InstallationDate: Installed on 2023-04-10 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2022 dmi.bios.release: 2.29 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.29 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B5 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.29 dmi.modalias: dmi:bvnHUAWEI:bvr2.29:bd04/21/2022:br2.29:efr2.29:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B5:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC170: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C170 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- Intel Tiger Lake internal sound card not detected https://bugs.launchpad.net/bugs/2016244 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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 2016244] Re: Intel Tiger Lake internal sound card not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2016244 Title: Intel Tiger Lake internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Huawei Matebook D14 with Core i3-1115G4 no sound card at all, "Dummy output" only, no even HDMI output. The codec is ESSX8336 I suppose. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 14:38:26 2023 InstallationDate: Installed on 2023-04-10 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2022 dmi.bios.release: 2.29 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.29 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B5 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.29 dmi.modalias: dmi:bvnHUAWEI:bvr2.29:bd04/21/2022:br2.29:efr2.29:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B5:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC170: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C170 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2016244/+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 1993347] Re: Wrong audio output selected by default on Pi 4
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3158 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993347 Title: Wrong audio output selected by default on Pi 4 Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 4, the new pipewire stack selects the "Analogue Output - Built-in Audio" by default when the system is first installed, when the HDMI output probably ought to be selected by default (the analogue output is notably lower quality due to the low resolution DAC used, and tends to only be used when there is no alternative, e.g. on DPI/DSI displays with no audio channel). This is a low priority since the default is easily changed in the gnome control center, and the new selection persists across boots (in contrast to the same issue in the older pulseaudio stack; LP: #1877194). However, it is a minor annoyance that a non-technical user may struggle to figure out initially (it also means the first-time setup sound isn't audible on first boot). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993347/+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 1993316] Re: Non-existent audio output selected on Pi 400
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3158 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 ** Also affects: pipewire via https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3158 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1993316 Title: Non-existent audio output selected on Pi 400 Status in PipeWire: Unknown Status in pipewire package in Ubuntu: Confirmed Bug description: When testing the Ubuntu 22.10 (kinetic) Desktop for Raspberry Pi on a Raspberry Pi 400 (the keyboard-based model), the new pipewire stack selects a non-existent audio output by default. Specifically, the output device listed in the gnome control center is "Analogue Output - Built-in Audio". On the Raspberry Pi 4 this refers to the auxiliary output (the 3.5mm headphone jack on the board), however the Pi 400 has no such output. Under the older pulseaudio stack, this was correct (no analogue output was listed) and the HDMI output was correctly selected on the Pi 400 (though, notably, the older stack got the default output wrong on the Pi 4; see LP: #1877194). This is a low priority since the default selection is easily changed from the gnome control center, and the new selection persists across boots (in contrast to the aforementioned pulseaudio bug). To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/1993316/+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 1993054] Re: USB key eject does not eject
Sorry for my post #5 I gave misleading info. now I repeated the operation and found the problem only with show unmounted volumes NO, if all unmounted volumes are show eject from the dock works fine. I ran again the test with show unmounted YES and NO and attaching both journals show-no.txt and show-yes.txt ** Attachment added: "show-no.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+attachment/5663910/+files/show-no.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 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: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 1993054] Re: USB key eject does not eject
attaching journal with show-YES ** Attachment added: "show-yes.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+attachment/5663911/+files/show-yes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1993054 Title: USB key eject does not eject Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I insert an USB key: icon appear in the dock and in the nautilus sidebar with title and a small arrow right click on icon in the dock and select 'Eject': the icon disappear in the dock but does NOT disappear from the nautilus sidebar click on the arrow near the icon in nautilus sidebar: the icon disappear and I see a message in notification area with: '... USB flash memory ... can be removed' problem happens when org.gnome.shell.extensions.dash-to-dock show-mounts-only-mounted is set to TRUE the problem does not occur if show-mounts-only-mounted is set to FALSE ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 74ubuntu2 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: Sun Oct 16 09:48:16 2022 InstallationDate: Installed on 2022-09-30 (15 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993054/+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 2016281] [NEW] Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys
Public bug reported: After each brightness-step change (via using Fn+arrow up-/arrow-down keys), system freezes for ~500ms. With my notebook's 10 brightness- levels, this often results in total delay from 10x 500ms, = 5 entire seconds for the notebook finishing a multi-step brightness-change in very very laggy steps, when the user input already stops within 1-2 seconds. Also, the brightness update-rate symbology is often freezing entirely for up to 5 seconds before indicating that brightness was changed at all (see screenshot in comment #2 for symbology) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 11:17:18 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-03-30 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c2574575-ad11-44a8-9aa0-69c2e7c72473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA 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. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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 false-gpu-hang freeze jammy ubuntu -- 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/2016281 Title: Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys Status in xorg package in Ubuntu: New Bug description: After each brightness-step change (via using Fn+arrow up-/arrow-down keys), system freezes for ~500ms. With my notebook's 10 brightness- levels, this often results in total delay from 10x 500ms, = 5 entire seconds for the notebook finishing a multi-step brightness-change in very very laggy steps, when the user input already stops within 1-2 seconds. Also, the brightness update-rate symbology is often freezing entirely for up to 5 seconds before indicating that brightness was changed at all (see screenshot in comment #2 for symbology) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.d
[Desktop-packages] [Bug 2016281] Re: Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys
** Attachment added: "brightness.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2016281/+attachment/5663971/+files/brightness.png ** Description changed: After each brightness-step change (via using Fn+arrow up-/arrow-down keys), system freezes for ~500ms. With my notebook's 10 brightness- levels, this often results in total delay from 10x 500ms, = 5 entire seconds for the notebook finishing a multi-step brightness-change in very very laggy steps, when the user input already stops within 1-2 seconds. Also, the brightness update-rate symbology is often freezing entirely for up to 5 seconds before indicating that brightness was changed at all - (see screenshot for symbology) + (see screenshot in comment #2 for symbology) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 - GCC version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 + GCC version: ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 11:17:18 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] - NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor Graphics Controller [1462:10d7] + NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GTX 660M] [1462:10d7] InstallationDate: Installed on 2023-03-30 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. GE60 0NC\0ND ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=c2574575-ad11-44a8-9aa0-69c2e7c72473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GAIMS.513 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GA 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. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GAIMS.513:bd11/08/2012:br4.6:svnMicro-StarInternationalCo.,Ltd.:pnGE600NC\0ND:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GA:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GE60 0NC\0ND dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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 -- 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/2016281 Title: Xorg freezing entirely for up to 5 seconds after brightness-change via hotkeys Status in xorg package in Ubuntu: New Bug description: After each brightness-step change (via using Fn+arrow up-/arrow-down keys), s
[Desktop-packages] [Bug 1965323] Re: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL
My current gnome-shell version is 44.0. As I noted, this happens on current Ubuntu Lunar. Reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6599 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6599 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6599 -- 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/1965323 Title: Wayland: overview hotspot is not recognised if cursor slides to it along top of screen on RTL Status in gnome-shell package in Ubuntu: Incomplete Bug description: Using Wayland, ubuntu-gnome, nvidia-510, RTL locale (hebrew). When sliding the cursor along the top (horizontal) edge of the screen to the hotspot at the top right corner of the screen (where the activities menu is found in an rtl environment), gnome-shell does not go into overview mode (and back). When sliding the cursor to the very same hotspot along the right (vertical) edge of the screen, gnome-shell works properly and goes to overview mode (and back). This problem exists only in wayland gnome sessions. It does not occur in x11 gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Mar 17 17:21:49 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-31 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=he_IL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965323/+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 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS
This was fixed-released in livecd-rootfs 2.818 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2013080 Title: On rpi desktop images, grow root leaving slack for LUKS Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: To aid in user-implemented FDE we wish to leave 16MB of the file- system unexpanded during first boot. The growth of the partition is unaffected, but rather than relying on systemd's growfs facility in fstab, we should use a service that runs a simple script to handle calculating the resize in early boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+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 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs
Fix-released in livecd-rootfs 2.818 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2004430 Title: Migrate raspberry pi image hacks from livecd-rootfs Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are currently several "hacks" in livecd-rootfs that introduce unpackaged files and/or services. In particular, everything in https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with the fstab and the swapfile needs to go. The new ubuntu-image based process for generating images won't be using these; anything to do with the fstab needs to go in the image-definition yaml, and the swapfile services ought to be owned by the ubuntu-raspi-settings- desktop package anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2016285] [NEW] Redundant creation of oem user in rpi desktop images
Public bug reported: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem- config-prepare is installed at the time that ubuntu-raspi-settings- desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Milestone: None => ubuntu-23.04 ** Changed in: ubuntu-settings (Ubuntu) Milestone: None => ubuntu-23.04 ** Merge proposal linked: https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/441071 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016286] [NEW] growroot-almost service failure after upgrade
Public bug reported: Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar may notice that the new growroot-almost.service persistently fails as the root is already resized. The unit should be updated to fail silently and prevent future runs. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016286 Title: growroot-almost service failure after upgrade Status in ubuntu-settings package in Ubuntu: New Bug description: Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar may notice that the new growroot-almost.service persistently fails as the root is already resized. The unit should be updated to fail silently and prevent future runs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2016286/+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 2016285] Re: Redundant creation of oem user in rpi desktop images
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016285] Re: Redundant creation of oem user in rpi desktop images
Setting to critical as this currently prevents the creation of the ubuntu rpi desktop images. ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Proposed fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2960 -- 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/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 2016289] Re: gnome-shell crash
*** This bug is a duplicate of bug 2014986 *** https://bugs.launchpad.net/bugs/2014986 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2014986, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2016289/+attachment/5664002/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2016289/+attachment/5664004/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2016289/+attachment/5664005/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 2014986 gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/2016289 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: Received an error window when I booted up ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 Uname: Linux 6.2.0-20-generic x86_64 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 14 16:27:45 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1680272303 ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= Signal: 5 SourcePackage: gnome-shell UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016289/+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 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)
Skype has the exact same problem, where files downloaded from chats to /tmp are not visible to other applications. Should I raise a separate bug ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1790608 Title: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp) Status in snapd: New Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1790608/+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 1995092] Re: Wrong ubuntu logo in About section in darkmode
** Description changed: - Bug only on Ubuntu 22.10 + Bug only on Ubuntu 22.10 and Ubuntu 23.04 The ubuntu logo used when darkmode is selected on the "About" page of Settings is not the right one. There is two ubuntu logo stored in /usr/share/pixmaps/: -ubuntu-logo-text.png -ubuntu-logo-text-dark.png It seams that for some reasons the "ubuntu-logo-text-dark.png" is not used at it should be in darkmode. -- 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/1995092 Title: Wrong ubuntu logo in About section in darkmode Status in gnome-control-center package in Ubuntu: Triaged Bug description: Bug only on Ubuntu 22.10 and Ubuntu 23.04 The ubuntu logo used when darkmode is selected on the "About" page of Settings is not the right one. There is two ubuntu logo stored in /usr/share/pixmaps/: -ubuntu-logo-text.png -ubuntu-logo-text-dark.png It seams that for some reasons the "ubuntu-logo-text-dark.png" is not used at it should be in darkmode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995092/+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 1995092] Re: Wrong ubuntu logo in About section in darkmode
** Tags added: 22.10 23.04 about control-center dark logo -- 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/1995092 Title: Wrong ubuntu logo in About section in darkmode Status in gnome-control-center package in Ubuntu: Triaged Bug description: Bug only on Ubuntu 22.10 and Ubuntu 23.04 The ubuntu logo used when darkmode is selected on the "About" page of Settings is not the right one. There is two ubuntu logo stored in /usr/share/pixmaps/: -ubuntu-logo-text.png -ubuntu-logo-text-dark.png It seams that for some reasons the "ubuntu-logo-text-dark.png" is not used at it should be in darkmode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995092/+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 2016298] [NEW] Not all networks showing in wifi connections
Public bug reported: When trying to find my home network in the wifi network list I am not able to view it. I can view the network with Windows (on same hardware), with my phone, my various smart devices can all find and connect to it to, just not my Ubuntu OS. Two other nearby networks show up though. Ubuntu 22.10 network-manager 1.40.0-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 14:14:56 2023 InstallationDate: Installed on 2023-04-14 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.50.1 dev enp2s0 proto dhcp src 192.168.50.102 metric 100 192.168.50.0/24 dev enp2s0 proto kernel scope link src 192.168.50.102 metric 100 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 0864981a-325c-3852-92ec-4bdc5620cb39 ethernet 1681477915 Fri 14 Apr 2023 14:11:55 BST yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0 ethernet connected full limited /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 0864981a-325c-3852-92ec-4bdc5620cb39 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp4s0 wifi disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2016298 Title: Not all networks showing in wifi connections Status in network-manager package in Ubuntu: New Bug description: When trying to find my home network in the wifi network list I am not able to view it. I can view the network with Windows (on same hardware), with my phone, my various smart devices can all find and connect to it to, just not my Ubuntu OS. Two other nearby networks show up though. Ubuntu 22.10 network-manager 1.40.0-1ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 14:14:56 2023 InstallationDate: Installed on 2023-04-14 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.50.1 dev enp2s0 proto dhcp src 192.168.50.102 metric 100 192.168.50.0/24 dev enp2s0 proto kernel scope link src 192.168.50.102 metric 100 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
[Desktop-packages] [Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
The .crash file from comment 11 has been submitted via ubuntu-bug in bug 2016299 - I'll leave it to the developers to determine which one should be the dupe. -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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/mutter/+bug/2015386/+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 2016301] [NEW] Certain keyboard shortcuts stopped working; crash in gnome-control-center
Public bug reported: I am using the Lunar (23.04) development release. Recently some keyboard shortcuts have stopped working, notably Ctrl+Alt+T to open a new terminal. Also -- I don't know if this is related, but it seems likely -- gnome- control-center crashes when clicking "View and Customize Shortcuts" under "Keyboard Shortcuts" in "Keyboard". This error message is printed when it crashes: 09:54:46.0351 GLib-GIO[ 8829]: ERROR: Settings schema 'org.gnome.settings-daemon.plugins.media-keys' does not contain a key named 'terminal' [1]8829 trace trap gnome-control-center ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/2016301 Title: Certain keyboard shortcuts stopped working; crash in gnome-control- center Status in gnome-control-center package in Ubuntu: New Bug description: I am using the Lunar (23.04) development release. Recently some keyboard shortcuts have stopped working, notably Ctrl+Alt+T to open a new terminal. Also -- I don't know if this is related, but it seems likely -- gnome- control-center crashes when clicking "View and Customize Shortcuts" under "Keyboard Shortcuts" in "Keyboard". This error message is printed when it crashes: 09:54:46.0351 GLib-GIO[ 8829]: ERROR: Settings schema 'org.gnome.settings-daemon.plugins.media-keys' does not contain a key named 'terminal' [1]8829 trace trap gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016301/+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 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
** Tags added: nvidia-wayland -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session Status in mutter package in Ubuntu: New Bug description: When logged into a desktop session, I created a new user account and then tried to "switch to" it. A new gnome session started for that user (test1), but after a few seconds, gnome-shell appears to have crashed. This only seems to happen on the first attempt to "switch to" a new user. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.89.02 Wed Feb 1 23:23:25 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 5 17:23:28 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: NVIDIA DGX Station ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0406 dmi.board.asset.tag: Default string dmi.board.name: X99-E-10G WS dmi.board.vendor: EMPTY dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EMPTY dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000: dmi.product.family: DGX dmi.product.name: DGX Station dmi.product.sku: 920-22587-2510-000 dmi.product.version: System Version dmi.sys.vendor: NVIDIA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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/mutter/+bug/2015386/+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 2016301] Re: Certain keyboard shortcuts stopped working; crash in gnome-control-center
This was fixed by reinstalling `gnome-settings-daemon` and rebooting. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2016301 Title: Certain keyboard shortcuts stopped working; crash in gnome-control- center Status in gnome-control-center package in Ubuntu: Invalid Bug description: I am using the Lunar (23.04) development release. Recently some keyboard shortcuts have stopped working, notably Ctrl+Alt+T to open a new terminal. Also -- I don't know if this is related, but it seems likely -- gnome- control-center crashes when clicking "View and Customize Shortcuts" under "Keyboard Shortcuts" in "Keyboard". This error message is printed when it crashes: 09:54:46.0351 GLib-GIO[ 8829]: ERROR: Settings schema 'org.gnome.settings-daemon.plugins.media-keys' does not contain a key named 'terminal' [1]8829 trace trap gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016301/+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 2016308] [NEW] Sweethome3D kills desktop session on loading files
Public bug reported: Hello, This bug is triggered by Sweethome 3D but the underlying problem is probably an xorg-issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session (aka xserver) is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to make the xserver crash. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2016308 Title: Sweethome3D kills desktop session on loading files Status in xorg-server package in Ubuntu: New Bug description: Hello, This bug is triggered by Sweethome 3D but the underlying problem is probably an xorg-issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session (aka xserver) is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to make the xserver crash. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2016308/+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 2016308] Re: Sweethome3D kills desktop session on loading files
** Attachment added: "testfile.sh3d" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2016308/+attachment/5664045/+files/testfile.sh3d -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2016308 Title: Sweethome3D kills desktop session on loading files Status in xorg-server package in Ubuntu: New Bug description: Hello, This bug is triggered by Sweethome 3D but the underlying problem is probably an xorg-issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session (aka xserver) is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to make the xserver crash. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2016308/+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 2016312] [NEW] /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g
*** This bug is a duplicate of bug 2015962 *** https://bugs.launchpad.net/bugs/2015962 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2016312 Title: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit Status in accountsservice package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2016312/+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 2016312] Re: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_s
*** This bug is a duplicate of bug 2015962 *** https://bugs.launchpad.net/bugs/2015962 ** Package changed: indicator-messages (Ubuntu) => accountsservice (Ubuntu) ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2015962 indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2016312 Title: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages- service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit Status in accountsservice package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2016312/+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 2016315] [NEW] mouse and touchpad panel: assets have black background
Public bug reported: The assets used in mouse and touchpad panel have black background that is not present in upstream assets. Perhaps this is caused during improper rendering of assets from the script used for changing colors ? ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: lunar -- 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/2016315 Title: mouse and touchpad panel: assets have black background Status in gnome-control-center package in Ubuntu: New Bug description: The assets used in mouse and touchpad panel have black background that is not present in upstream assets. Perhaps this is caused during improper rendering of assets from the script used for changing colors ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2016315/+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 2016308] Re: Sweethome3D kills desktop session on loading files
2023-04-14T16:44:07.804148+02:00 ubuntu-00 systemd[1478]: Started app-gnome-sweethome3d-2690.scope - Application launched by gnome-shell. 2023-04-14T16:44:08.003473+02:00 ubuntu-00 systemd[1478]: Started app-gnome-ubuntu\x2dadvantage\x2dnotification-2720.scope - Application launched by gnome-session-binary. 2023-04-14T16:44:08.004736+02:00 ubuntu-00 systemd[1478]: Started app-gnome-update\x2dnotifier-2723.scope - Application launched by gnome-session-binary. 2023-04-14T16:44:08.228668+02:00 ubuntu-00 sweethome3d.desktop[2690]: Java 3D: implicit antialiasing enabled 2023-04-14T16:44:08.998009+02:00 ubuntu-00 systemd[1]: systemd-timedated.service: Deactivated successfully. 2023-04-14T16:44:09.030348+02:00 ubuntu-00 java[2690]: Failed to load module "canberra-gtk-module" 2023-04-14T16:44:30.450559+02:00 ubuntu-00 systemd[1]: systemd-hostnamed.service: Deactivated successfully. 2023-04-14T16:44:33.945268+02:00 ubuntu-00 gnome-shell[1701]: ** 2023-04-14T16:44:33.945283+02:00 ubuntu-00 gnome-shell[1701]: libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) 2023-04-14T16:44:33.945291+02:00 ubuntu-00 gnome-shell[1701]: Bail out! libmutter:ERROR:../src/core/window.c:1533:meta_window_unmanage: assertion failed: (window->display->focus_window != window) 2023-04-14T16:44:33.945299+02:00 ubuntu-00 gnome-shell[1701]: GNOME Shell crashed with signal 6 2023-04-14T16:44:33.945309+02:00 ubuntu-00 gnome-shell[1701]: == Stack trace for context 0x55afca89a820 == 2023-04-14T16:44:33.960887+02:00 ubuntu-00 update-notifier[2723]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961034+02:00 ubuntu-00 xdg-desktop-por[2158]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961178+02:00 ubuntu-00 xdg-desktop-por[2231]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961376+02:00 ubuntu-00 evolution-alarm[2040]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961508+02:00 ubuntu-00 gsd-wacom[2001]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961647+02:00 ubuntu-00 gsd-power[1979]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961766+02:00 ubuntu-00 gsd-media-keys[1977]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.961925+02:00 ubuntu-00 gnome-shell[1943]: Error getting buffer 2023-04-14T16:44:33.962111+02:00 ubuntu-00 snapd-desktop-i[2334]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.962526+02:00 ubuntu-00 gsd-keyboard[1974]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.962810+02:00 ubuntu-00 nautilus[2619]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.962841+02:00 ubuntu-00 gnome-shell[1943]: (EE) failed to read Wayland events: Connection reset by peer 2023-04-14T16:44:33.963394+02:00 ubuntu-00 gsd-color[1966]: Error reading events from display: Broken pipe 2023-04-14T16:44:33.964791+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.001551+02:00 ubuntu-00 systemd[1478]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=6/ABRT 2023-04-14T16:44:34.002095+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Color.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.003871+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.004873+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.005682+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.006401+02:00 ubuntu-00 systemd[1478]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.006512+02:00 ubuntu-00 systemd[1478]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.006977+02:00 ubuntu-00 systemd[1478]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE 2023-04-14T16:44:34.007114+02:00 ubuntu-00 systemd[1478]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.008206+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.008571+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Color.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.008898+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.009142+02:00 ubuntu-00 systemd[1478]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'. 2023-04-14T16:44:34.009398+02:00 ubuntu-00 sy
[Desktop-packages] [Bug 2016286] Re: growroot-almost service failure after upgrade
This bug was fixed in the package ubuntu-settings - 23.04.5 --- ubuntu-settings (23.04.5) lunar; urgency=medium * ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in postinst; there's no guarantee oem-config is installed yet and it cannot be a dependency as it's uninstalled after first boot (LP: #2016285) * ubuntu-raspi-settings-desktop: Don't attempt to expand an already expanded rootfs (LP: #2016286) -- Dave Jones Fri, 14 Apr 2023 11:13:13 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016286 Title: growroot-almost service failure after upgrade Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar may notice that the new growroot-almost.service persistently fails as the root is already resized. The unit should be updated to fail silently and prevent future runs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2016286/+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 2016285] Re: Redundant creation of oem user in rpi desktop images
This bug was fixed in the package ubuntu-settings - 23.04.5 --- ubuntu-settings (23.04.5) lunar; urgency=medium * ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in postinst; there's no guarantee oem-config is installed yet and it cannot be a dependency as it's uninstalled after first boot (LP: #2016285) * ubuntu-raspi-settings-desktop: Don't attempt to expand an already expanded rootfs (LP: #2016286) -- Dave Jones Fri, 14 Apr 2023 11:13:13 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016308] Re: libmutter: GNOME Shell crashed with signal 6
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/2016308 Title: libmutter: GNOME Shell crashed with signal 6 Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Hello, This bug is triggered by Sweethome 3D but the underlying problem seems to be a libmutter issue. Setup: Ubuntu 23.04 Ryzen 6000 AMD 680 Gnome 44 Sweethome 3D 7.0.2 (from the repositories) Whenever I load a file in Sweethome 3D my desktop session is killed instantly. I am either thrown back to the desktop login or it stays black. This seems like a severe problem to me. Under no circumstances should an app like Sweethome 3D be able to crash mutter. I don't know how to give any logs. But I attach a sample file for Sweethome 3D. Actually it crashes with any file. Steps to reproduce: Start Sweethome 3D Draw some walls to make Draw a room Save to file Quit Sweethome 3D Start Sweethome 3D Load the file Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016308/+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 2016323] [NEW] Many problems displaying web pages & launching apps
Public bug reported: Web pages display and app launch are VERY slow for a PC having this configuration. There is really a problem about display since I bougth this PC. And ... Since last big upgrade (including some Nvidia stuff) : No more gear on login to switch to Wayland/X11. Night mode in screen parameters doesn't work. Steam game (Northgard) launches very slowly and is unplayable I have uncommented the line #WaylandEnable=true in /etc/gdm3/custom.conf and restarted with no success. Thank you in advance for your help. Release Ubuntu 22.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 18:53:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Installed on 2023-01-27 (77 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Notebook NH5xVR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1008-oem root=UUID=c6e942e5-1878-4e2a-8d85-81abebd32761 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2021 dmi.bios.release: 7.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NH5xVR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.3 dmi.modalias: dmi:bvnInsydeCorp.:bvr1.07.06:bd02/18/2021:br7.6:efr7.3:svnNotebook:pnNH5xVR:pvrNotApplicable:rvnNotebook:rnNH5xVR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: NH5xVR dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9 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 ubuntu ** Summary changed: - Many problems! + Many problems displaying web pages & launching apps -- 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/2016323 Title: Many problems displaying web pages & launching apps Status in xorg package in Ubuntu: New Bug description: Web pages display and app launch are VERY slow for a PC having this configuration. There is really a problem about display since I bougth this PC. And ... Since last big upgrade (including some Nvidia stuff) : No more gear on login to switch to Wayland/X11. Night mode in screen parameters doesn't work. Steam game (Northgard) launches very slowly and is unplayable I have uncommented the line #WaylandEnable=true in /etc/gdm3/custom.conf and restarted with no success. Thank you in advance for your help. Release Ubuntu 22.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1008.8-oem 6.1.14 Uname: Linux 6.1.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 14 18:53:58 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/525.105.17: added ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3070 Mobile / Max-Q] [10de:249d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GA104M [GeForce RTX 3070 Mobile / Max-Q] [1558:50f4] InstallationDate: Inst
[Desktop-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
This bug was fixed in the package livecd-rootfs - 2.828 --- livecd-rootfs (2.828) lunar; urgency=medium * 099-ubuntu-image-customization.chroot: Remove redundant creation of oem user and oem-config-prepare (LP: #2016285) -- Dave Jones Fri, 14 Apr 2023 09:48:31 +0100 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016331] [NEW] On Ubuntu 20.4, the PC shuts down when the screen is locked. This happens despite automatic suspend being off.
Public bug reported: Using release 20.04.6 LTS gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What happens: Ubuntu shuts down after some time when the screen is locked, despite automatic suspend being off. Expected: The workstation should remain on even if locked, which is especially important for remote access. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Package changed: gdm3 (Ubuntu) => gnome-power-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2016331 Title: On Ubuntu 20.4, the PC shuts down when the screen is locked. This happens despite automatic suspend being off. Status in gnome-power-manager package in Ubuntu: New Bug description: Using release 20.04.6 LTS gnome-power-manager: Installed: 3.32.0-2 Candidate: 3.32.0-2 Version table: *** 3.32.0-2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What happens: Ubuntu shuts down after some time when the screen is locked, despite automatic suspend being off. Expected: The workstation should remain on even if locked, which is especially important for remote access. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/2016331/+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 2016330] [NEW] gnome-shell memory leak
Public bug reported: gnome-shell memory usage is getting worse every hour by exhausting more than 4 GB OF RAM and then getting frozen for some minutes till it get crashed without logging out the user (which means all my USER's running processes didn't get killed anyway and are being running in the background) **free --giga --human**: ``` total used free shared buff/cache available Mem: 7.6G 4.0G 374M 351M 3.3G 3.0G Swap: 23G 117M 23G ``` **gnome-extensions list --enabled**: ``` unbl...@sun.wxg@gmail.com unlockdialogbackgro...@sun.wxg@gmail.com prevent-double-empty-win...@silliewous.nl user-th...@gnome-shell-extensions.gcampax.github.com workspace-indica...@gnome-shell-extensions.gcampax.github.com fq@megh caffe...@patapon.info no-overview@fthx arcm...@arcmenu.com noannoya...@daase.net quick-lang-swi...@ankostis.gmail.com primary_input_on_lockscr...@sagidayan.com lockk...@vaina.lt notification-posit...@drugo.dev favourites-in-appg...@harshadgavali.gitlab.org notification-banner-reloa...@marcinjakubowski.github.com date-menu-format...@marcinjakubowski.github.com auto-move-wind...@gnome-shell-extensions.gcampax.github.com recentit...@bananenfisch.net openweather-extens...@jenslody.de remove-alt-tab-de...@daase.net NotificationCounter@coolllsk workspace-switcher-mana...@g-dh.github.com screenshot-window-si...@gnome-shell-extensions.gcampax.github.com native-window-placem...@gnome-shell-extensions.gcampax.github.com notification-time...@chlumskyvaclav.gmail.com ubuntu-d...@ubuntu.com ubuntu-appindicat...@ubuntu.com d...@rastersoft.com ``` **ps auxw | grep gnome**: ``` USER PR NI VIRT RES SHR %CPU %MEM TIME+ COMMAND johnm 5474 0.0 0.0 242108 7204 ? SLl 03:15 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login johnm 5478 0.0 0.0 163440 6112 tty2 Ssl+ 03:15 0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu johnm 5485 0.0 0.1 224196 15580 tty2 Sl+ 03:15 0:00 /usr/libexec/gnome-session-binary --session=ubuntu johnm 5546 0.0 0.0 92960 5104 ? Ssl 03:15 0:00 /usr/libexec/gnome-session-ctl --monitor johnm 5569 0.0 0.2 521284 17692 ? Ssl 03:15 0:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu johnm 5774 11.2 4.5 5446336 359844 ? Ssl 03:15 3:01 /usr/bin/gnome-shell johnm 5807 0.0 0.2 1059236 20344 ? Sl 03:15 0:00 /usr/libexec/gnome-shell-calendar-server johnm 5948 0.0 0.3 2670180 27068 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications johnm 5950 0.0 0.0 162676 7332 ? Sl 03:15 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session johnm 6014 0.5 2.6 868404 210992 ? Sl 03:15 0:08 /usr/bin/gnome-software --gapplication-service johnm 6216 0.0 0.3 2670180 26836 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver johnm 6283 0.0 0.4 67 33288 ? Ssl 03:16 0:00 /usr/libexec/xdg-desktop-portal-gnome johnm 6286 0.1 1.0 3020104 78652 ? Sl 03:16 0:02 gjs /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js -E -P /usr/share/gnome-shell/extensions/d...@rastersoft.com -M 0 -D 1280:0:1366:768:1:27:56:0:0:0 -D 0:0:1280:1024:1:0:56:0:0:1 johnm 7274 0.0 0.2 37388 19824 ? S 03:17 0:00 /usr/bin/python3 /usr/bin/gnome-terminal --wait johnm 7277 0.0 0.3 384004 27960 ? Sl 03:17 0:00 /usr/bin/gnome-terminal.real --wait johnm 7287 0.8 0.7 902128 59084 ? Ssl 03:17 0:13 /usr/libexec/gnome-terminal-server johnm 8027 0.0 0.0 3644 1100 ? S 03:23 0:00 bwrap --args 38 gnome-extensions-app johnm 8164 0.0 0.0 3768 1472 ? S 03:23 0:00 bwrap --args 38 gnome-extensions-app johnm 8165 0.0 0.0 7704 3224 ? S 03:23 0:00 /bin/sh /app/bin/gnome-extensions-app johnm 8166 0.4 1.8 3867112 141276 ? Sl 03:23 0:05 /usr/bin/gjs /app/share/gnome-extensions-app/org.gnome.Extensions johnm 8311 0.0 0.6 2912668 53152 ? Sl 03:23 0:01 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions johnm 9499 0.0 0.4 207508 35856 ? Sl 03:25 0:00 /usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/lib/mozilla/native-messaging-hosts/org.gnome.chrome_gnome_shell.json chrome-gnome-sh...@gnome.org ``` **ps auxw | grep gjs**: ``` USER PR NI VIRT RES SHR %CPU %MEM TIME+ COMMAND johnm 5948 0.0 0.3 2670180 27068 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications johnm 6216 0.0 0.3 2670180 26836 ? Sl 03:15 0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver johnm 6286 0.1 1.0 3020104 78652 ? Sl 03:16 0:02 gjs /usr/share/gnome-shell/extensions/d...@rastersoft.com/ding.js -E -P /usr/share/gnome-shell/extensions/d...@rastersoft.com -M 0 -D 1280:0:1366:768:1:27:56:0:0:0 -D 0:0:1280:1024:1:0:56:0:0:1 johnm 8166 0.4 1.8 3867112 141276 ? Sl 03:23 0:05 /usr/bin/gjs /app/share/gnome-extensions-app/org.gnome.Extensions johnm 8311 0.0 0.6 2912668 53152 ? Sl 03:23 0:01 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions ``` **ps auxw | grep gdm**: ``` USER PR NI VIRT RES SHR %CPU %MEM TIME+ COMMAND root 2806 0.0 0.1 242376 9004 ? Ssl 03:12 0:00 /usr/s
[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hi, Daniel I performed next changes: 1. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0xff" 2. Add to /etc/environment: MUTTER_DEBUG=kms ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5664106/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
I commented out the suggested line but the only effect is that switching accounts is now completely impossible. More specifically, it prevents me from getting past the login screen: 1. I select "switch user" from my running user session 2. I am sent to the login screen 3. I select a different user and submit the password 4. the screen goes black for a second 5 and I find myself back at step 2 6. All I can do at this stage is log in again as my initial user After enabling debugging in /etc/gdm3/custom.conf, /var/crash has received a pulseaudio related crash message. I see the owner is my initial user so I am not sure it has anything to do with my other user accounts. Should I append the crash file here as an attachment? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en- US/quick-docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m
Ken VanDine verified that the patch from merge request 2960 fixed his crashes. -- 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/2014986 Title: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial error_code 8 request_code 131 (XInputExtension) minor_code 57)] Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4 ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Apr 2 01:49:43 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-03-30 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+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 1964458] Re: [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl
** Changed in: gjs Status: New => 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/1964458 Title: [jammy] gnome-shell live session crashes with SIGSEGV in js::gc::Cell::storeBuffer from js::gc::PostWriteBarrierImpl Status in gjs: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Core was generated by `gnome-shell --sm-disable --mode=ubiquity'. Program terminated with signal SIGSEGV, Segmentation fault. In mozjs91: #0 0x7f5a697c3f44 in js::gc::Cell::storeBuffer (this=, this=) at .././js/src/gc/Cell.h:357 #1 js::gc::PostWriteBarrierImpl (next=, prev=, cellp=) at .././js/src/gc/StoreBuffer.h:654 #2 js::gc::PostWriteBarrier (next=, prev=, vp=) at .././js/src/gc/StoreBuffer.h:666 #3 js::InternalBarrierMethods::postBarrier (next=, prev=, vp=0x7f5a5002b200) at .././js/src/gc/Barrier.h:333 #4 js::InternalBarrierMethods::postBarrier (vp=0x7f5a5002b200, prev=, next=) at .././js/src/gc/Barrier.h:332 #5 0x7f5a6b637722 in js::BarrierMethods::postWriteBarrier (next=, prev=, vp=, vp=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:770 #6 JS::Heap::postWriteBarrier (next=, prev=, this=, this=, prev=, next=) at /usr/include/mozjs-91/js/RootingAPI.h:361 #7 JS::Heap::~Heap (this=, this=) at /usr/include/mozjs-91/js/RootingAPI.h:323 #8 mozilla::detail::VectorImpl, 0ul, js::SystemAllocPolicy, false>::destroy ( aEnd=0x7f5a5002b218, aBegin=) at /usr/include/mozjs-91/mozilla/Vector.h:65 #9 mozilla::Vector, 0ul, js::SystemAllocPolicy>::~Vector (this=, this=) at /usr/include/mozjs-91/mozilla/Vector.h:901 #10 JS::GCVector, 0ul, js::SystemAllocPolicy>::~GCVector (this=, this=) at /usr/include/mozjs-91/js/GCVector.h:43 #11 GjsContextPrivate::~GjsContextPrivate (this=, this=) at ../gjs/context.cpp:482 #12 0x7f5a6b638978 in gjs_context_finalize (object=0x557e2a3f7180) at ../gjs/context.cpp:495 #13 0x7f5a6c0d2dfd in g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7f5a6c31d77d in _shell_global_destroy_gjs_context (self=) at ../src/shell-global.c:703 #15 0x557e2950bece in main (argc=, argv=) at ../src/main.c:659 In mozjs78: See bug 1947130 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1964458/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
I was experiencing the same issue on Kubuntu 22.04.2. It ships 22.0.1 mesa version and this bug was fixed on 22.3.0 (as the tag says). Search for kisak-mesa stable ppa to upgrade your mesa version to 22.3.7, issue is gone there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin package in Debian: New Bug description: ... To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** 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/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() Status in gjs: Fix Released Status in Spidermonkey Javascript engine: Invalid Status in OEM Priority Project: Confirmed Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mozjs102 package in Ubuntu: Invalid Status in mozjs91 package in Ubuntu: Invalid Status in gnome-shell package in Fedora: Confirmed Bug description: https://errors.ubuntu.com/problem/256d1c0d1aad03bb024b525f4c80868e8f6a85b4 https://errors.ubuntu.com/problem/b1669e114babda005eb5a6414867a0eb7293f7e7 Description: Ubuntu 22.04 LTS Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 16:06:35 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1649813447 InstallationDate: Installed on 2022-05-05 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/ubuntu RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmozjs-91.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () Title: gnome-shell crashed with SIGSEGV in g_object_unref() 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/gjs/+bug/1974293/+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 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
** Bug watch added: Debian Bug tracker #989493 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989493 ** Also affects: udisks2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989493 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Status in udisks2 package in Debian: Unknown Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+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
