[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
I'd like to add another debdiff to jammy which resolves the issue from the patch upstream Upstream MR: https://gitlab.freedesktop.org/hadess/iio-sensor- proxy/-/merge_requests/355 ** Patch added: "iio-sensor-proxy_3.3-0ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5570270/+files/iio-sensor-proxy_3.3-0ubuntu6.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
ok, I arranged one machine to give it a try. I will share the result here later. BTW, I'm not able to check bug 1965246 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLU
Comment #3 sounds like https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5197 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5137 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3165 and the fix hasn't landed yet: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2299 That should fix most recent occurrences of the crash. I'm not so sure about older releases though. The stack trace here is a little too terse so it will catch-all for other similar crashes too. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5197 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5197 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5137 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5137 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3165 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3165 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965437] Re: Cannot change background 22.04
Thanks for the bug report. I can't seem to be able to reproduce the problem here. Do you have any nonstandard extensions loaded? Please look in the Extensions app. If removing extensions doesn't explain it then please attach a video or screenshot showing how you are changing the background. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1965437 Title: Cannot change background 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965437] Re: Cannot change background 22.04
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965437 Title: Cannot change background 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965437] [NEW] Cannot change background 22.04
You have been subscribed to a public bug: Background stuck on black. Cannot change via GUI or CLI ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 18:57:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-22-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0584] InstallationDate: Installed on 2022-03-15 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 6430U ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=0b7063d6-5898-4f7f-ac0b-73d105ab566a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2018 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0JCV3H dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/30/2018:br4.6:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0JCV3H:rvrA02:cvnDellInc.:ct9:cvr:skuLatitude6430U: dmi.product.name: Latitude 6430U dmi.product.sku: Latitude 6430U dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build2 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-2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible ubuntu wayland-session -- Cannot change background 22.04 https://bugs.launchpad.net/bugs/1965437 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965457] [NEW] Missing (provide 'gtk-doc) in file gtk-doc.el
Public bug reported: At the end of the file: /usr/share/emacs/site-lisp/gtk-doc-tools/gtk-doc.el It is missing the statement: (provide 'gtk-doc) The file is provided by the package "gtk-doc-tools" . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-doc-tools 1.32-4 [modified: usr/share/emacs/site-lisp/gtk-doc-tools/gtk-doc.el] ProcVersionSignature: Ubuntu 5.4.0-104.118-generic 5.4.166 Uname: Linux 5.4.0-104-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Mar 17 20:07:18 2022 InstallationDate: Installed on 2018-05-21 (1396 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: gtk-doc UpgradeStatus: Upgraded to focal on 2021-09-16 (182 days ago) ** Affects: gtk-doc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk-doc in Ubuntu. https://bugs.launchpad.net/bugs/1965457 Title: Missing (provide 'gtk-doc) in file gtk-doc.el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk-doc/+bug/1965457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965453] Re: gjs-console assert failure: free(): invalid pointer
*** This bug is a duplicate of bug 1946165 *** https://bugs.launchpad.net/bugs/1946165 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 #1946165, 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/1965453/+attachment/5570215/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570217/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570221/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570222/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570223/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570224/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965453/+attachment/5570225/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1946165 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1965453 Title: gjs-console assert failure: free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1965453/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLU
I wonder if this is the same thing I just saw: https://paste.ubuntu.com/p/GSWYFy4jYh/ Or if it's not the same thing, I wonder if it is related. Also a clutter_acto_set_mapped: assertion failed crash. I have a crash log too, if you'd like to take a look. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964732] Re: [FFe] Include Desktop Icons Appearance Settings
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 39+20220316.cc9c7d3e-1 --- gnome-shell-extension-desktop-icons-ng (39+20220316.cc9c7d3e-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream git snapshot compatible with GNOME Shell 42 * Drop all patches: applied in new release [ Marco Trevisan (Treviño) ] * Add patch to use the Ubuntu Appearance panel to display settings in the Ubuntu session (LP: #1964732) * Add patches to show full settings directly from the Extensions apps -- Jeremy Bicha Thu, 17 Mar 2022 08:37:01 -0400 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964732 Title: [FFe] Include Desktop Icons Appearance Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731070] Re: "_Skip" button label translation not correctly applied
Ubiquity on Ubuntu 21.10 has the same problem. ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1731070 Title: "_Skip" button label translation not correctly applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1731070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965323] [NEW] Wayland: overview hotspot is not recognised if cursor slides to it along top of screen
Public bug reported: 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) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy rtl ** Description changed: 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 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). + 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 + 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) ** Tags added: rtl -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965319] Re: Evolution crashed with SIGSEGV
*** This bug is a duplicate of bug 1964922 *** https://bugs.launchpad.net/bugs/1964922 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 #1964922, 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/1965319/+attachment/5570088/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570090/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570093/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570094/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570095/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570096/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1965319/+attachment/5570097/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1964922 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1965319 Title: Evolution crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1965319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965067] Re: [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center
libhandy-1's behavior is working as intended by GNOME. Let's reassign to gnome-control-center. The upgrade scenario is being handled by LP: #1965189 and the new libhandy-1 is being held in jammy-proposed by LP: #1964841 ** Package changed: libhandy-1 (Ubuntu Jammy) => gnome-control-center (Ubuntu Jammy) ** Changed in: gnome-control-center (Ubuntu Jammy) Status: Confirmed => Triaged ** Changed in: gnome-control-center (Ubuntu Jammy) Assignee: Jeremy Bicha (jbicha) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965067 Title: [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965067] [NEW] [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center
You have been subscribed to a public bug: gnome-disks does not apply the Yaru theme, when all other GNOME applications respect the default theme. See attached screenshot. gnome-disks 42~rc-1ubuntu1 gnome-shell 42~beta-1ubuntu2 yaru-theme-gtk 22.04.1 ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Affects: gnome-control-center (Ubuntu Jammy) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Tags: jammy -- [42beta] (some) GNOME applications use light theme when dark is set in gnome-control-center https://bugs.launchpad.net/bugs/1965067 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965113] Re: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used
** Changed in: gnome-session (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1965113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview
Fix proposed: https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/2244 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965072 Title: In Xorg sessions, desktop icons flicker when entering the overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965072] Re: In Xorg sessions, desktop icons flicker when entering the overview
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => In Progress ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965072 Title: In Xorg sessions, desktop icons flicker when entering the overview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965072/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964037] Re: gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
Using the main branches: #0 0x7f3255a9fccf in g_log_structured_array () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3255a9ff99 in g_log_default_handler () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x5618851da1fd in default_log_handler (log_domain=0x7f3254e5b2c6 "mutter", log_level=6, message=0x5618885d6810 "Failed to create fallback offscreen framebuffer: Failed to create texture 2d due to size/format constraints", data=0x0) at ../src/main.c:297 #3 0x7f3255aa13fa in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3255aa16e3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3254dfec77 in create_fallback_offscreen (renderer_native=0x561885ea18f0, cogl_context=0x5618861d2750, width=1920, height=1200) at ../src/backends/native/meta-renderer-native.c:1213 #6 0x7f3254dfef76 in meta_renderer_native_create_view (renderer=0x561885ea18f0, logical_monitor=0x561886d4f540, output=0x56188865d4a0, crtc=0x7f320018a610) at ../src/backends/native/meta-renderer-native.c:1288 #7 0x7f3254c9a75d in meta_renderer_create_view (renderer=0x561885ea18f0, logical_monitor=0x561886d4f540, output=0x56188865d4a0, crtc=0x7f320018a610) at ../src/backends/meta-renderer.c:102 #8 0x7f3254c9a7cd in create_crtc_view (logical_monitor=0x561886d4f540, monitor=0x561888572e80, output=0x56188865d4a0, crtc=0x7f320018a610, user_data=0x561885ea18f0) at ../src/backends/meta-renderer.c:133 #9 0x7f3254c7ec1b in foreach_crtc (monitor=0x561888572e80, mode=0x56188772e740, monitor_crtc_mode=0x56188621d670, user_data=0x7fffdc9b9760, error=0x0) at ../src/backends/meta-logical-monitor.c:247 #10 0x7f3254c82d04 in meta_monitor_mode_foreach_crtc (monitor=0x561888572e80, mode=0x56188772e740, func=0x7f3254c7ebb4 , user_data=0x7fffdc9b9760, error=0x0) at ../src/backends/meta-monitor.c:1955 #11 0x7f3254c7ecb5 in meta_logical_monitor_foreach_crtc (logical_monitor=0x561886d4f540, func=0x7f3254c9a78d , user_data=0x561885ea18f0) at ../src/backends/meta-logical-monitor.c:274 #12 0x7f3254c9a8ee in meta_renderer_real_rebuild_views (renderer=0x561885ea18f0) at ../src/backends/meta-renderer.c:168 #13 0x7f3254dff4c8 in meta_renderer_native_rebuild_views (renderer=0x561885ea18f0) at ../src/backends/native/meta-renderer-native.c:1422 #14 0x7f3254c9a78b in meta_renderer_rebuild_views (renderer=0x561885ea18f0) at ../src/backends/meta-renderer.c:120 #15 0x7f3254e0ab20 in meta_stage_native_rebuild_views (stage_native=0x5618860ff500) at ../src/backends/native/meta-stage-native.c:66 #16 0x7f3254dc7e1b in meta_backend_native_update_screen_size (backend=0x561885ded120, width=5043, height=3360) at ../src/backends/native/meta-backend-native.c:411 #17 0x7f3254c6d7e7 in meta_backend_sync_screen_size (backend=0x561885ded120) at ../src/backends/meta-backend.c:285 #18 0x7f3254c6da07 in meta_backend_monitors_changed (backend=0x561885ded120) at ../src/backends/meta-backend.c:356 #19 0x7f3254c946a3 in meta_monitor_manager_notify_monitors_changed (manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:3476 #20 0x7f3254c948f9 in meta_monitor_manager_rebuild (manager=0x561885df0340, config=0x561886083e80) at ../src/backends/meta-monitor-manager.c:3566 #21 0x7f3254ddc7b1 in meta_monitor_manager_native_apply_monitors_config (manager=0x561885df0340, config=0x561886083e80, method=META_MONITORS_CONFIG_METHOD_PERSISTENT, error=0x7fffdc9b9a60) at ../src/backends/native/meta-monitor-manager-native.c:348 #22 0x7f3254c8e639 in meta_monitor_manager_apply_monitors_config (manager=0x561885df0340, config=0x561886083e80, method=META_MONITORS_CONFIG_METHOD_PERSISTENT, error=0x7fffdc9b9a60) at ../src/backends/meta-monitor-manager.c:635 #23 0x7f3254c8e836 in meta_monitor_manager_ensure_configured (manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:708 #24 0x7f3254c94a49 in meta_monitor_manager_reconfigure (manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:3622 #25 0x7f3254c94a74 in meta_monitor_manager_reload (manager=0x561885df0340) at ../src/backends/meta-monitor-manager.c:3629 #26 0x7f3254ddcd99 in handle_hotplug_event (manager=0x561885df0340) at ../src/backends/native/meta-monitor-manager-native.c:502 #27 0x7f3254ddce40 in on_kms_resources_changed (kms=0x561885def9c0, changes=META_KMS_UPDATE_CHANGE_FULL, manager=0x561885df0340) at ../src/backends/native/meta-monitor-manager-native.c:538 #28 0x7f3255b90376 in g_cclosure_marshal_VOID__FLAGSv () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #29 0x7f3255baf640 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #30 0x7f3255baf7a3 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #31 0x7f3254df2a37 in handle_hotplug_event (kms=0x561885def9c0, udev_device=0x561887a9f340, changes=META_KMS_UPDATE_CHANGE_FULL) at
[Bug 1965219] Re: gnome lock screen does not permit reentering password
You might be able to recover with something like: killall gnome-shell or killall -9 gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
The lock screen is rendered by the gnome-shell process (which then sends the image to Xorg for display in the case of a Xorg session). gdm3 does nothing graphical, only launches other programs. Even the login screen is rendered by a gnome-shell process. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795649] Re: evince from snap doesn't save position in pdf document
** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/-/issues/1642 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1795649 Title: evince from snap doesn't save position in pdf document To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1795649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
It's only the three built in extensions installed. Thanks I'll run journalctl -b-1 > prevboot.txt next time. ls /var/crash/ says _usr_lib_systemd_systemd-timesyncd.102.crash _usr_lib_systemd_systemd-timesyncd.102.upload _usr_lib_systemd_systemd-timesyncd.102.uploaded I only see a similar error on https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a Is the lock screen handled by gnome-shell itself or some outside process like gdm3? If there some signal or whatever I can send to gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965113] Re: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used
** Changed in: gnome-session (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1965113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"
Hi, > > *Do you experience the problem with CD-R or CD-RW media ?* > Yes. The exact same error message as when I tried to make a DVD. Then it is not exactly the same problem as with the DRW-24D5MT of Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718. Your Brasero version 3.12.1-4ubuntu2 seems slightly younger than the 3.12.3-1 of Mauro and the 3.12.2-5 which i tested. But there was no visible development in Brasero since quite a while. So i would not blame the difference on the versions ... for now. > > Does it help to blank the CD medium before using it with Brasero: > > xorriso -outdev /dev/sr0 -blank as_needed* > Unfortunately No. What about other burn programs (with a power-cycle between the last Brasero run and the the new experiment) ? Like: ISO="...path.to.your.iso.image.file..." xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO" Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1964554 Title: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1964554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
There are no crashes after 3.38 though, so I'm still hopeful this has been fixed in Ubuntu 21.10 onward. ** No longer affects: mutter (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()
Still happening in 3.36.9 (bug 1965252 as well as thousands of reports in https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa) ** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Confirmed ** Changed in: mutter (Ubuntu Focal) Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809058] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate_event() from clutt
*** This bug is a duplicate of bug 1558886 *** https://bugs.launchpad.net/bugs/1558886 ** This bug has been marked a duplicate of bug 1558886 gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809058 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate_event() from clutter_x11_handle_event() from handle_host_xevent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809058/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964037] Re: gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Summary changed: - gnome-shell crashes when attempting to enable second monitor + gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2182 https://gitlab.gnome.org/GNOME/mutter/-/issues/2182 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2182 Importance: Unknown Status: Unknown ** Information type changed from Private to Public ** Tags added: multimonitor ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964037 Title: gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965251] Re: gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader()
** Summary changed: - /usr/bin/gnome-shell:7:disk_cache_has_key:can_skip_compile:can_skip_compile:_mesa_glsl_compile_shader:_mesa_compile_shader + gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965251 Title: gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965251] [NEW] gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 41.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/467a5181bf7cf0a579af4944e8d42945282b2af4 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal hirsute impish jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965251 Title: gnome-shell crashed with SIGBUS in disk_cache_has_key() from can_skip_compile() from can_skip_compile() from _mesa_glsl_compile_shader() from _mesa_compile_shader() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965113] Re: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used
That's a known issue, see https://forum.snapcraft.io/t/cannot-open- display-after-session-type-changed-wayland-x11/23838. The problem appears to be partly in gnome-session (https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75), partly in the snapcraft desktop extensions that assume a wayland session if there's a lingering wayland socket (https://github.com/snapcore/snapcraft/blob/main/extensions/desktop/common/desktop- exports#L240). It is not specific to the firefox snap, and it can be worked around by running the apps with DISABLE_WAYLAND=1. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/-/issues #75 https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75 ** Package changed: firefox (Ubuntu) => gnome-session (Ubuntu) ** Also affects: gnome-session via https://gitlab.gnome.org/GNOME/gnome-session/-/issues/75 Importance: Unknown Status: Unknown ** Also affects: snapcraft Importance: Undecided Status: New ** Summary changed: - Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used + Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1965113 Title: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1965113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965113] [NEW] Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used
You have been subscribed to a public bug: Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions. $ /snap/bin/firefox Error: cannot open display: :0 $ echo $DISPLAY :0 And other X11 apps still work just fine. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: jammy snap x11 -- Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions if a Wayland session has been used https://bugs.launchpad.net/bugs/1965113 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver
I've just tested with jammy again and it definitely fails with Nvidia-510. The external monitor plugged into the secondary (Nvidia) GPU doesn't light up for Wayland sessions, while the primary monitor (Intel) works fine. Although you need to have the monitor plugged in before logging in to even get that far. If you try hotplugging a monitor on the secondary GPU in a Wayland session then you get bug 1965246 instead. I've been aware of it for quite some time but haven't yet got to triaging that crash. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1959888 Title: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Actually if you're using a Xorg session and only the mouse is working then it's likely the gnome-shell process alone is hung or crashed. Because the mouse movement is handled by Xorg, not gnome-shell. Please: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
Thanks for the bug report. Please open the 'Extensions' app and ensure no more than the three built-in Ubuntu extensions are enabled. If any others are listed then please disable/uninstall them and log in again. Also next time the problem happens, after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965219] [NEW] gnome lock screen does not permit reentering password
You have been subscribed to a public bug: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal freeze ubuntu -- gnome lock screen does not permit reentering password https://bugs.launchpad.net/bugs/1965219 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
