[Bug 1964711] Re: Locked Ubuntu is frozen and cannot be unlocked

** Package changed: gdm3 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1964711 Title: Locked Ubuntu is frozen and cannot be unlocked To manage notifications about

[Bug 1964711] Re: Locked Ubuntu is frozen and cannot be unlocked

Thanks for the bug report. Next time the freeze happens please: 1. Wait 10 seconds. 2. Shut down by pressing the power button. 3. Power on and then run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. 5. Look in /var/crash for crash files and if found run: u

[Bug 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep

Is it the IBM or the LG monitor that remains black? I can't see any hints of a problem in the log. It sounds like maybe GNOME can't uniquely identify one of the monitors and so can't remember its preferred setting. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New --

[Bug 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep

Maybe try enabling Wayland and then see if logging into 'Ubuntu on Wayland' avoids the problem. To enable Wayland you will need to change the kernel parameter: nomodeset to: nvidia-drm.modeset=1 and then run: sudo update-grub and reboot. -- You received this bug notification because

[Bug 1964711] Re: Locked Ubuntu is frozen and cannot be unlocked

Thank you for taking the time to report this bug and helping to make Ubuntu better. You've not given details as to your actual install; was it a Ubuntu Desktop 20.04 LTS or Ubuntu Server 20.04 LTS? You do mention moving mouse; a device not normally attached to servers, so I'm assume (rightly/wron

[Bug 1964711] [NEW] Locked Ubuntu is frozen and cannot be unlocked

You have been subscribed to a public bug: After locking Ubuntu and leaving it unattended for a while, the operating system cannot be unlocked anymore. No means of user input (e.g. typing on the keyboard, moving the mouse) produce the lock screen and I have to shut down my computer by pressing down

[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine

Report a bug as https://bugs.launchpad.net/oem-priority/+bug/1964747 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach a

[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine

It seems a regression since https://launchpad.net/ubuntu/+source/nvidia- graphics-drivers-510/510.54-0ubuntu0.18.04.1 because of ``` * debian/templates/control.in: - Set XB-Support to PB (production branch). ``` Checking with maintainer on https://chat.canonical.com/canonical/pl/5bheikgti7

[Bug 1964684] Re: Yaru (battery) icons in Power Statistics do not show correctly

** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1964684 Title: Yaru (battery) i

[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine

Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support nvidia-driver-510: package has invalid Support PBheader, cannot determine support level Mar 14 02:38:53 ubuntu ubiquity: WARNING:root:_pkg_get_support nvidia-driver-510-server: package has invalid Support PBheader, cannot determine

[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine

In daily build: kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 470.103.01 From comment#2: kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 510.39.01 In latest ubuntu archive: kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX

[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine

Still could reproduce this issue with Jammy daily build (3/13) $ sha256sum ~/Downloads/jammy-desktop-amd64.iso 1c46933bf1837e6427f994676c60d54515c6ce011276dbfe4c5a63e427fdc2c5 /home/jeremysu/Downloads/jammy-desktop-amd64.iso 1. Install third-part drivers during the installation. 2. After insta

[Bug 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments

That's great, but: (a) When you reported this bug in GNOME 41 you didn't have the triple buffering feature (libmutter-9-0 41.3-3ubuntu1); and (b) If you are using jammy-proposed then even that (mutter 42~beta-1ubuntu2) does not yet have the MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING feature. So it so

[Bug 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)

This sounds like a continuation of Nvidia bug 1799679. Please test regular Ubuntu 22.04 (GNOME 41) and/or Ubuntu 21.10 (GNOME 40) and tell us if the same problem exists there. I just want to confirm it's not a new problem in GNOME 42 here. ** Changed in: gnome-shell (Ubuntu) Status: New =>

[Bug 1959888] Re: Wayland sessions can't use external monitors that are connected to an Nvidia GPU with the proprietary driver

Proof of concept workaround/fix: https://gitlab.gnome.org/vanvugt/mutter/-/commit/8c57fd13766c74007c696a0fbb74f1b2a89ff099 But even when finished it will be a little slow. We're waiting for Nvidia to update their driver such that the GBM API doesn't fail when it's the secondary GPU. Until then we

[Bug 1962679] Re: Take screenshot in Totem does not work

** Summary changed: - take screenshot does not work + Take screenshot in Totem does not work -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962679 Title: Take screenshot in Totem d

[Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from gnome-clipbo...@b00f.github.io/searchBox.js:22

** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from gnome-clipbo...@b00f.github.io/searchBox.js:22 ** Summary chang

[Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()

The crash is in your extension: /home/ravage/.local/share/gnome- shell/extensions/gnome-clipbo...@b00f.github.io [74412.043807] esport gnome-shell[7855]: GNOME Shell crashed with signal 11 [74412.043807] esport gnome-shell[7855]: == Stack trace for context 0x55b8b5203170 == [74412.043807] esport

[Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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.ne

[Bug 1964678] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64()

** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 1964734] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke

*** This bug is a duplicate of bug 1964678 *** https://bugs.launchpad.net/bugs/1964678 ** This bug has been marked a duplicate of bug 1964678 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_entry_get_text() from ffi_call_unix64() -- You received this bug notifica

[Bug 1964734] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_entry_get_text:ffi_call_unix64:ffi_call_int:Gjs::Function::invoke

*** This bug is a duplicate of bug 1964678 *** https://bugs.launchpad.net/bugs/1964678 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

[Bug 1926862] Re: Unable to exit Activities Overview in Ubuntu 21.04

*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Comment #6 doesn't appear to be directly relevant to this bug. But most likely if you don't have the option to log into a Wayland session then you're probably using Nvidia and need to add the kernel paramete

[Bug 1964682] Re: IBus not starting properly at login with gnome-shell 42

The issue only happens when logging in to a wayland session. Also, I stumbled upon this upstream gtk issue: https://gitlab.gnome.org/GNOME/gtk/-/issues/4699 Currently we install ibus-gtk4 by default (ibus recommends it), which is my 'fault'. Assumed that it should be consistent with how ibus-gtk

[Bug 1964732] [NEW] [FFe] Include Desktop Icons Appearance Settings

Public bug reported: In Jammy the default desktop extension is providing lots settings in a non very integrated way, accessible from right-click: https://i.imgur.com/boMhCrH.png We got a community contribution (https://gitlab.gnome.org/Community/Ubuntu/gnome-control- center/-/merge_requests/9) t

[Bug 1964675] Re: Window dragging lag when rendering 3d objects. (GNOME 42, NVIDIA, glxgear, pymol)

Other DEs (xfce, icewm, and fvwm) do NOT have such issues. I guess this might be a gnome related bug. -- 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/1964675 Title: Window dragg

[Bug 1964679] Re: gnome-panel crashed with signal 5 in g_settings_get_value()

This bug was fixed in the package gnome-applets - 3.43.1-1 --- gnome-applets (3.43.1-1) experimental; urgency=medium * New upstream release. - Fixes crash when emptying trash (LP: #1964679). * Update build-dependencies. - Replace libgweather-3-dev with libgweather-4-dev.

[Bug 1964716] [NEW] Connection to Gmail addressbook failed

Public bug reported: 1) most recent release 2) most recent package 3 +4) see attached screenshot ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Evolution_Verbindung_zu_Adressbuch_fehlgeschlagen.jpg" https://bugs.launchpad.net/bugs/1964716

[Bug 1926862] Re: Unable to exit Activities Overview in Ubuntu 21.04

*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 How can I change from Wayland to Xorg if it doesn't appear as an option on my login screen? I am currently unable to exit this view and I can't seem to find any alternative ways of doing so. -- You receive

[Bug 1964679] Re: gnome-panel crashed with signal 5 in g_settings_get_value()

Thank you for your report. The fix is on its way to Jammy. ** Package changed: gnome-panel (Ubuntu) => gnome-applets (Ubuntu) ** Changed in: gnome-applets (Ubuntu) Status: New => Fix Committed ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-applets

[Bug 1769116] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'

I am seeing this after CDROM read errors of audio CDs using rhythmbox on Ubuntu 20.04 with an Nvidia video card. After that, rhythmbox fails to start, adding this complaint to /var/log/syslog, and cannot be restarted without logging off or rebooting. Nearby syslog entries appended. Mar 13 08:56

[Bug 1964701] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()

*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 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 #1962761, so is being marked as such.