[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]
This sounds like a simple bug in nvidia-drm-470 or kernel 5.13. Both have been upgraded in Ubuntu 22.04 already so there's a chance this issue is already fixed. Still, please follow the instruction in comment #7 because I would like to understand more about the system. ** Changed in: mutter (Ubuntu) Status: Confirmed => Opinion -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]
The strange thing to me is that Nvidia shouldn't be involved here. A USB-C port is likely to be wired to the Intel chips only. As a DisplayPort the USB-C is wired to the Intel GPU. And gnome-shell by default will use the integrated Intel GPU only for the desktop. Please reproduce the freeze again, then reboot and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1955001] Re: File reading speed is slow
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1955001 Title: File reading speed is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1955001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
** No longer affects: gnome-shell (Ubuntu) ** Also affects: snapd 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/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1960972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]
** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
** Tags added: impish ** Tags added: regression-update ** Also affects: snapd (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/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1960972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960865] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100]
Also tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1891 Importance: Unknown Status: Unknown -- 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/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1960865/+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
** Tags added: hybrid multigpu -- 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/ubuntu/+source/mutter/+bug/1959888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: No login screen after recent update
Can you check to see if fprintd is: (a) still running and hung (RedHat issue 1534873); or (b) crashed (most likely bug 1960387) If you can't find it still running then the steps to investigate crashes are https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - No login screen after recent update + No login screen when fprintd is installed ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High -- 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/1960336 Title: No login screen when fprintd is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] Re: All snap applications missing from gnome-search after update
Downgrading snapd to the previous version 2.53+21.10ubuntu1 resolves the issue. As such this may actually be a snapd issue, or something involving both communications between the two applications. Neither version of snapd logs any errors. -- 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/1960972 Title: All snap applications missing from gnome-search after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960972/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960972] [NEW] All snap applications missing from gnome-search after update
Public bug reported: After this "upgrade", snapd:amd64 2.53+21.10ubuntu1 2.54.2+21.10ubuntu1 (Some video drivers were upgraded at the same time, but this doesn't seem relevant.) ...all snap applications have disappeared from gnome-shell search. All snaps are still installed and can be executed with "snap run app". All applications work correctly when launched this way, except that they will be missing their dock icons showing the "gears"/missing icon indicator. Application icons are also missing in the Ubuntu Software Center. Reinstalling the snap applications affected does not help, including "snap remove --purge && snap install". Non-snap applications are unaffected. To reproduce, press super key and type the name of any installed in /snap. No snap applications appear but normal applications and files will be listed as usual. Tried to uninstall shell extensions removed and reboot. Nothing improved. --- gnome-shell logs complain of the following: Feb 15 15:26:56 gnome-shell[3135]: GNOME Shell started at Tue Feb 15 2022 15:26:53 GMT-0800 (PST) Feb 15 15:26:56 gnome-shell[3135]: Registering session with GDM Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: Slack1, Impossible to lookup icon for 'Slack1_2-panel' in path /run/user/1000/.org.chromium.Chromium.cgr> Feb 15 15:27:03 ubuntu-appindicat...@ubuntu.com[3135]: unable to update icon for Slack1 Feb 15 15:27:09 gnome-shell[3135]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity — escape ampersand as Feb 15 15:27:09 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:09 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:10 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:27:10 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:27:13 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Feb 15 15:27:13 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:06 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:06 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:33 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:33 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:29:34 gnome-shell[3135]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application Feb 15 15:29:34 gnome-shell[3135]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 5 but got 0 Feb 15 15:35:17 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:22 gnome-shell[3135]: Timelines with detached actors are not supported Feb 15 15:35:25 gnome-shell[3135]: Timelines with detached actors are not supported --- Description:Ubuntu 21.10 Release:21.10 gnome-shell: Installed:
[Bug 1960954] [NEW] Update gvfs to 1.50
Public bug reported: gvfs 1.50 switched to libsoup3 which we will not be including in Ubuntu 22.04 LTS.2 We should stay with the 1.48 series unless we want to revert this commit: https://gitlab.gnome.org/GNOME/gvfs/-/commit/beaaf78 https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/NEWS ** Affects: gvfs (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1960954 Title: Update gvfs to 1.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1960954/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center
+1000 Just installed Ubuntu for my mother today, and I learned her yesterday how to install a software. We were both confused (I'm a developer and I'm very confused about this "feature" too) about the fact that the search bar is hidden until we type some text on the keyboard. Today she called me trying to install a software (not listed in the featured softwares in the main page), and she didn't remember how to search for a particular software by name. Last month I installed Ubuntu for friends (30 years old, daly users of Android phone so used to softwares) and same thing: they called me 2 times to ask how to search for a software ? "is it possible to install another software than those that are listed in the main page ?" I've seen in Gnome's issues that Gnome devs thinks that this is a typical Gnome behavior; okay maybe; I hate Nautilus and most of Gnome apps for their "simple designs". But this is definitively not a typical Ubuntu design: when we display the "magical search bar" that appears after pressing super key, we see the search bar, really well highlighted in the center. I really think that software search bar should be obvious to find. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1878301 Title: Focal regression: poor discoverability for search in Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1878301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960947] [NEW] Graphical issues for GtKGL in software rendering
Public bug reported: * Issue GTK applications using GL graphic show corruption problems under software rendering * Test case 1. install gtk-3-examples 2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo 3. select the gl example, it should render without issues * Regression potentiel The change is in the GL backend so check for rendering issues in GTK softwares using GL, including flutter applications ** Affects: gtk+3.0 (Ubuntu) Importance: High Status: Fix Released ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960947 Title: Graphical issues for GtKGL in software rendering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: ipywidgets (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
That did not make a difference, no -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: The user session should run under systemd
@Paride, thanks, I'm going to close it if it was fixed it's not the same issue anymore, also Iain isn't working on it at this point? Bug #1959596 is likely the regression you mentioned ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Fix Released ** Tags removed: rls-jj-incoming -- 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/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959596] Re: Applications end up in session scope, rather than per .desktop scope
I feel the way we launch applications from the dock also may imapct... Just to be clear, do we have a difference here? App launched from overview VS app launched from dock -- 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/1959596 Title: Applications end up in session scope, rather than per .desktop scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: No login screen after recent update
confirmed that after reinstalling fprintd, the issue returns. First of all, it creates a delay until the login screen loads. then when the login screen loads, no user is visible to be clicked, also not after the 25000 ms timeout of the fprintd daemon. So it seems the cause of the issue is the login process in gdm3 is not handling this properly - ideally the user would get a message like - fprintd error: timeout xxx etc and the login would skip fingerprint related stuff and go to normal login. This is currently broken when the command fprintd-list times out like: gnome-shell[2622]: Failed to connect to Fprint service: Error calling StartServiceByName for net.reactivated.Fprint: Timeout was reached current work around: drop to safe login and type: apt remove fprintd reboot -- 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/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960917] [NEW] Please remove gnome-desktop3, replaced by gnome-desktop
Public bug reported: Please remove the gnome-desktop3 source package. Its binaries are now all provided by the gnome-desktop source package. We will be dropping the gnome-desktop3 source package from Debian soon too. ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1960917 Title: Please remove gnome-desktop3, replaced by gnome-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1960917/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: No login screen after recent update
I tracked down the cause, it has to do with sssd and how gdm3 handles it. Similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=1534873 First I removed kerberos auth, which did not seem to have had an effect. Then I saw that fprintd was showing errors and fprintd-list was throwing the same error as in the logs. I removed it and after that it worked. So it seems like a bug in sssd related to fingerprint auth, when that is not working properly. Regarding evdi - as you wrote, can be addressed separately. As I wrote , it does NOT work properly for me, not the beta driver, not even on 5.13 with beta driver. I just installed 5.12 kernel and latest release driver because the beta does not work properly on my system - I use a D6000 Dell dock. Regarding this bug - I will try to see if I can get frintd to work. I still have Ubuntu sessions showing that do not work, not sure where they came from, this is even after I purged gnome gnome-shell and gnome- session. can login now with gdm3 and gnome session. Is there anything else you need to pursue this ? ** Bug watch added: Red Hat Bugzilla #1534873 https://bugzilla.redhat.com/show_bug.cgi?id=1534873 -- 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/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1952107] Re: Google Contacts API Deprecated
Here just a little workaround for Ubuntu 18.04.6 LTS and Gnome 3.28.2. I suppose it could work with other distributions: 1-backup your evolution data 2-install to upgrade evolution from 3.28 to 3.42 via flatpack (https://flathub.org/apps/details/org.gnome.Evolution) 3-import evolution data from the previous backup 4-reboot and I have all contacts, calendars and tasks working again! -- 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/1952107 Title: Google Contacts API Deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
Launchpad has imported 15 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=2036604. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-01-03T11:10:45+00:00 khoorasan wrote: Description of problem: An application named "Backup" downloaded from the app store finished making back up of the whole system, then I unplugged the external USB, closed the application, a browser named "Brave" was running, when issued the command "poweroff" in the terminal, and my macbook pro 2012 shut down, once I restarted I noticed this error message. Version-Release number of selected component: gnome-shell-41.2-1.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline:/usr/bin/gnome-shell crash_function: meta_context_terminate executable: /usr/bin/gnome-shell journald_cursor: s=3036cc978c2c4faca5c818849161ed45;i=1432e;b=de82c8ea70844d16a59c2bf73d776781;m=5a37134;t=5d4495cd257c9;x=9eb7bfee5d98542a kernel: 5.15.11-200.fc35.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:42 Truncated backtrace: Thread no. 1 (4 frames) #0 meta_context_terminate at ../src/core/meta-context.c:451 #1 process_ice_messages at ../src/x11/session.c:116 #5 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4175 #7 meta_context_run_main_loop at ../src/core/meta-context.c:433 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/0 On 2022-01-03T11:10:47+00:00 khoorasan wrote: Created attachment 1848679 File: backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/1 On 2022-01-03T11:10:49+00:00 khoorasan wrote: Created attachment 1848680 File: core_backtrace Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/2 On 2022-01-03T11:10:50+00:00 khoorasan wrote: Created attachment 1848681 File: cpuinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/3 On 2022-01-03T11:10:51+00:00 khoorasan wrote: Created attachment 1848682 File: dso_list Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/4 On 2022-01-03T11:10:52+00:00 khoorasan wrote: Created attachment 1848683 File: environ Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/5 On 2022-01-03T11:10:53+00:00 khoorasan wrote: Created attachment 1848684 File: exploitable Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/6 On 2022-01-03T11:10:54+00:00 khoorasan wrote: Created attachment 1848685 File: limits Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/7 On 2022-01-03T11:10:55+00:00 khoorasan wrote: Created attachment 1848686 File: maps Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/8 On 2022-01-03T11:10:56+00:00 khoorasan wrote: Created attachment 1848687 File: mountinfo Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/9 On 2022-01-03T11:10:57+00:00 khoorasan wrote: Created attachment 1848688 File: open_fds Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/10 On 2022-01-03T11:10:58+00:00 khoorasan wrote: Created attachment 1848689 File: proc_pid_status Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/11 On 2022-01-03T11:10:59+00:00 khoorasan wrote: Created attachment 1848690 File: var_log_messages Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1959937/comments/12 On 2022-01-12T11:12:20+00:00 bkb wrote: *** Bug 2039748 has been marked as a duplicate of
[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject())
Please run this command: gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false and then reboot. Has that solved the problem? ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) from ubuntu- d...@ubuntu.com/locations.js:1108 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
