[Bug 2008165] Re: Settings takes ~25 seconds to load on lunar

It only seems to happen in Wayland sessions. In Xorg, Settings will start immediately. -- 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/2008165 Title: Settings takes

[Bug 2008165] [NEW] Settings takes ~25 seconds to load on lunar

Public bug reported: Settings takes ~25 seconds to load on lunar So long that you think it's broken. But being 25 seconds is suspicious because that's the default DBus timeout. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44~alpha-0ubuntu1 ProcVersionSignature:

[Bug 1976554] Re: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend

The same is happening on ubuntu 22.04.2 LTS on my Lenovo ThinkPad X1 Yoga 4th. Giampiero's details are the same on my machine. A few more notes that may or may not be relevant: * The screen has for me always been rotated in the direction that it would rotate if the screen rotation would have

[Bug 1976554] Re: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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.

[Bug 1868332] Re: Scrolling jumps after switching windows

The same is here Ubuntu 22.04.1 LTS -- 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/1868332 Title: Scrolling jumps after switching windows To manage notifications about this bug

[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

Hi Sergio, I tried your workaround, but the KRB5CCNAME environment variable is not set, because I don't use krb5-user and libpam-krb5. In my case the authentication is made by sssd-krb5 and the kerberos ticket is stored in /tmp/krb5cc_... -- You received this bug notification because you are a

[Bug 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

I found something odd... Setting KRB5CCNAME in /etc/environment does work, but setting "default_ccache_name" in /etc/krb5.conf doesn't. In theory, when KRB5CCNAME isn't set, kerberos should use that value for the cache file. And although the command line tools do use it, it seems that gvfsd

[Bug 2008067] [NEW] To support Elan fp device [04F3:0C82]

Public bug reported: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/2b760dfa380ceff152ff8105a2aad76d85ec1ddc This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C82] fingerprint component will get supported. [Test Plan] * Find a machine with this

[Bug 2007739] Re: gjs-console crashed with SIGABRT

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

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

Unfortunately I still can't reproduce the bug (on 23.04) using those steps. -- 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/1968040 Title: Blanked screen doesn't wake up after

[Bug 1800043] Re: nautilus cannot write on nfs file share base dir

Same issue with Nautilus on Ubuntu 22.04 Observations: Thunar file manager had the same issue, PCManFM works fine. -- 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/1800043 Title:

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

I found an easier way to reproduce this issue by the following steps: 1. Log out and select xorg 2. Log in and log out again to select wayland session 3. super + L to make screen blank. I can reproduce this issue easily. I tried the latest drm-tip/linux-next then I can't reproduce this issue.