[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
** Changed in: mutter Status: Unknown => Fix Released -- 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
The issue in comments #7 and #8 is being tracked separately in bug 2054769. -- 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/1872594 Title: Ubuntu logo shifts vertically when the login screen appears To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1872594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054769] Re: Boot animation and login screen use different display scales
See also bug 1872594. ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Changed in: plymouth (Ubuntu) Status: New => Triaged -- 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/2054769 Title: Boot animation and login screen use different display scales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054769] [NEW] Boot animation and login screen use different display scales
Public bug reported: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI ** Affects: mutter (Ubuntu) Importance: Low Status: Triaged ** Affects: plymouth (Ubuntu) Importance: Low Status: Triaged ** Tags: flickerfreeboot noble visual-quality ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/2054769 Title: Boot animation and login screen use different display scales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
Also the missing key was introduced in mutter-common version 44.0. It sounds like it must have been installed at the time of the crash, but not compiled yet? ** Changed in: mutter (Ubuntu) Status: Fix Released => 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
That's weird. The crash came from a system that already had mutter 45 in the process of upgrading (bug 2054319). Given the fix already existed in the new binary, I'm not sure what we could do to stop the old binary from crashing. Maybe more gentle upgrades somehow? ** Tags removed: rls-jj-incoming -- 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
The tracker-extract crash may be bug 1990630 or bug 1962585, because it looks like both fixes haven't made it into jammy yet. But also this bug list probably needs some maintenance: https://bugs.launchpad.net/ubuntu/+source/tracker-miners The gnome-shell crash is now tracked in bug 2054761. -- 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/2054319 Title: System installed from jammy point release iso cannot upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
Fix released in mutter 45.0. ** Tags added: rls-jj-incoming -- 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054761] [NEW] gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
Public bug reported: Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients' Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: jammy rls-jj-incoming ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3017 https://gitlab.gnome.org/GNOME/mutter/-/issues/3017 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3017 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: New => Fix Released -- 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/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054109] Re: nautilus fails to build on armhf
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- 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/2054109 Title: nautilus fails to build on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2054109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054109] Re: nautilus fails to build on armhf
** Changed in: nautilus Status: New => Fix Released -- 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/2054109 Title: nautilus fails to build on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2054109/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
This bug was fixed in the package tracker-miners - 3.3.3-0ubuntu0.20.04.2 --- tracker-miners (3.3.3-0ubuntu0.20.04.2) jammy; urgency=medium [ Denison Barbosa ] * Removes install section from tracker-extract.service to prevent it from being enabled by systemd. It is a helper service that should be managed by tracker-miner-fs.service, not systemd. (LP: #1779890) - d/p/lp1779890-remove-install-section-from-tracker-extract-service.patch - d/tracker-extract.postinst -- Matthew Ruffell Fri, 01 Dec 2023 17:27:37 +1300 ** Changed in: tracker-miners (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker-miners in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043119] Re: screen color calibration : no start button
Update: The button itself is tested to properly show up now. However, it's whether the whole process works. An `sudo apt install gnome-color- manager` may be able to fix that. # https://askubuntu.com/questions/1504329/ubuntu-23-10-display-color- calibration-problem#comment2639103_1504361 @DanielT I just retried displaycal, only this time I went all the way to the end... and it failed... and the terse error looked like it was complaining that it couldn't communicate with the color-manager, so I installed gnome-color-manager and then displaycal worked properly when rerun. – heynnema 32 mins ago # Updated question https://askubuntu.com/q/1504329/1004020 Update #1 - 2/21/24: This appears to be a bug that goes all the way back to Ubuntu 22.10. I'm told that it works fine in 22.04, but I haven't verified that yet. Update #2 - 2/22/24: After implementing the patch from the answer by Daniel T (thanks BTW), it does now get a "Start" button, but after clicking it, the color patch remains white, and it errors out with "internal error". See the following information from the terminal, and syslog. ``` al@al-Inspiron-7700-AIO:~/Desktop$ sh askubuntu_color_calibration_fix.sh 09:18:10.5465 cc-color-panel[18961]: WARNING: calibration failed with code 1: Timeout was reached al@al-Inspiron-7700-AIO:~/Desktop$ cd /var/log al@al-Inspiron-7700-AIO:/var/log$ tail syslog 2024-02-22T09:18:26.993688-08:00 al-Inspiron-7700-AIO ubuntu-report[3390]: level=error msg="data were not delivered successfully to metrics server, retrying in 120s" 2024-02-22T09:18:35.407512-08:00 al-Inspiron-7700-AIO systemd[3355]: Started app-gnome-org.gnome.Settings-19159.scope - Application launched by gnome-shell. 2024-02-22T09:18:35.707775-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c4 2024-02-22T09:19:21.000134-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor [:0x56149c6b1f90] is on because it needs an allocation. 2024-02-22T09:19:21.000796-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor [:0x56149e0ec310] is on because it needs an allocation. ``` Post note: I have a Dell AIO with a touch screen. -- 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/2043119 Title: screen color calibration : no start button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054734] [NEW] Missing dependency for "Rhythmbox" (Plugins-loading)
Public bug reported:
Package: rhythmbox
Version: 3.4.7-1ubuntu1
Missing dependency: "gir1.2-soup-3.0"
Without "gir1.2-soup-3.0" (see Screenshot):
- Some Plugins (e.g. Replay-Gain; Song Lyrics) cannot be activated.
- Error-message: "Dependency 'Shared plugin code' failed to load."
Below:
1) Package Dependencies
2) Shell-Output
1) Package Dependencies
Depends: libc6 (>= 2.34), libglib2.0-0 (>= 2.68.0),
libgstreamer-plugins-base1.0-0 (>= 1.4.0), libgstreamer1.0-0 (>= 1.4.0),
libgtk-3-0 (>= 3.20.0), libpeas-1.0-0 (>= 1.0.0), librhythmbox-core10 (=
3.4.7-1ubuntu1), libx11-6, rhythmbox-data (>= 3.4.7-1ubuntu1), dbus,
gstreamer1.0-plugins-base (>= 1.4.0), gstreamer1.0-plugins-good (>= 1.4.0),
gstreamer1.0-x, media-player-info
Recommends: yelp, avahi-daemon, notification-daemon, gvfs-backends,
rhythmbox-plugin-alternative-toolbar, rhythmbox-plugins
Suggests: gstreamer1.0-plugins-bad, gstreamer1.0-plugins-ugly,
gnome-codec-install, gnome-control-center | unity-control-center,
rhythmbox-plugin-cdrecorder, rhythmbox-plugin-zeitgeist
2) Shell-Output
** (rhythmbox:166393): WARNING **: 20:33:53.606: Error importing plugin 'rb':
Traceback (most recent call last):
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/rb/rb.py", line 37, in
from Loader import Loader
File "/usr/lib/x86_64-linux-gnu/rhythmbox/plugins/rb/Loader.py", line 28, in
gi.require_version('Soup', '3.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Soup not available
(rhythmbox:166393): libpeas-WARNING **: 20:33:53.607: Error loading
plugin 'rb'
** Affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot of Error"
https://bugs.launchpad.net/bugs/2054734/+attachment/5748584/+files/Screenshot_2024-02-22_20-35-38.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2054734
Title:
Missing dependency for "Rhythmbox" (Plugins-loading)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2054734/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
I broke out the policykit failure, with an apport-package bug, into https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716 -- 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/2054319 Title: System installed from jammy point release iso cannot upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** No longer affects: tracker-miners (Ubuntu) -- 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/2054319 Title: System installed from jammy point release iso cannot upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043119] Re: screen color calibration : no start button
I sent a MR to https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/2311 . My fix still needs to be tested (I don't have a colorimeter), then backported. -- 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/2043119 Title: screen color calibration : no start button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2043119] Re: screen color calibration : no start button
I attempted to write a hotfix at https://askubuntu.com/a/1504361/1004020 . If it works, I might upstream in the next few days. -- 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/2043119 Title: screen color calibration : no start button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Yeah, sorry, I forgot to mention. The crashes that happen in our Jenkins are already pushed to the error tracker. Here are links to the latest oopses: gnome-shell: https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c tracker-extract: https://errors.ubuntu.com/oops/7c05a805-d101-11ee-8a58-fa163ec8ca8c Maybe Tim will have a link for the polkit crash, but I couldn't find one. -- 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/2054319 Title: System installed from jammy point release iso cannot upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Tags added: rls-nn-incoming -- 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/2054319 Title: System installed from jammy point release iso cannot upgrade to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1085706] Re: pam_ecryptfs: seteuid error
I am not seeing this in kscreenlocker on 24.04. Unless someone else can confirm it I am closing kscreenlocker from this bug. ** Changed in: kscreenlocker (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1085706 Title: pam_ecryptfs: seteuid error To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036388] Re: Login screen grey background flickers
** Changed in: gnome-shell (Ubuntu) Status: Triaged => 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/2036388 Title: Login screen grey background flickers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036388/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054679] [NEW] seahorse crash, i believe this coincides with my pulseaudio crash when the computer attempted to idle down and isntead stayed logged in and the screen flickered and sound stopped w
Public bug reported: Description:Ubuntu 22.04.4 LTS Release:22.04 seahorse: Installed: 41.0-2 Candidate: 41.0-2 Version table: *** 41.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status I expected the computer to idle down and what happened instead is the computer did not idle down and the sound and brightness stopped working, the screen flickered dark to dim to bright. Keeping the dimmer at 5% keeps the brightness at 100% and stops the flickering. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: seahorse 41.0-2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 03:22:28 2024 InstallationDate: Installed on 2023-10-18 (126 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/2054679 Title: seahorse crash, i believe this coincides with my pulseaudio crash when the computer attempted to idle down and isntead stayed logged in and the screen flickered and sound stopped working. Keeping the dimmer at 5% keeps the brightness at 100% and stops the flickering. Bluetooth audio speaker works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2054679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054667] [NEW] Displays in the settings app can't be overlapped
Public bug reported: I have three displays: the laptop internal display and two 24" external displays. In the Gnome settings app, the displays can be overlapped, but then the Apply button is greyed out so I can't press it. The error message is "Changes Cannot be Applied, This could be due to hardware limitations." I wasn't actually trying to overlap the displays originally, but just change the arrangement of the displays. I found the solution accidentally, i.e. I didn't overlap the displays, and then the Apply button worked. 1) Ubuntu 22.04.4 LTS 2) gnome-control-center: Installed: 1:41.7-0ubuntu0.22.04.8 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 10:29:16 2024 InstallationDate: Installed on 2024-02-21 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2054667 Title: Displays in the settings app can't be overlapped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2054667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Mantic is awaiting sponsorship in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/comments/4 -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Here's the mantic debdiff for both bug 2054510 and bug 2051074. ** Changed in: mutter (Ubuntu Mantic) Status: Triaged => In Progress ** Patch added: "mutter_45.2-0ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/+attachment/5748404/+files/mutter_45.2-0ubuntu4.debdiff -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Jammy is awaiting sponsorship in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/comments/3 -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Here's the jammy debdiff for both bug 2054510 and bug 2051074. ** Patch added: "mutter_42.9-0ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/+attachment/5748381/+files/mutter_42.9-0ubuntu6.debdiff -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023322] Re: GTK internal browser does not render with Nvidia drivers
** Changed in: webkit Status: Confirmed => Fix Released ** Bug watch added: bugs.webkit.org/ #261874 https://bugs.webkit.org/show_bug.cgi?id=261874 -- 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/2023322 Title: GTK internal browser does not render with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023322]
After Sonny reached out on Mastodon, people reported a variety of problems that were either tracked down to misconfigured systems (e.g. missing NVIDIA GBM, no modesetting, etc), and the cases that did look like interesting cases seemed to be fixed with WebKitGTK 2.42.5. I think it's reasonable to assume this bug was fixed by the combination of the various refactorings to DMA-BUF handling code in WebKitGTK, and newer NVIDIA cards. If anyone can reproduce reproduce this with a modern version (2.42+) of WebKitGTK GTK4, please speak up and the issue can be reopened. But please make sure to read https://bugs.webkit.org/show_bug.cgi?id=261874#c32 and see if your issue is not described in that comment. -- 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/2023322 Title: GTK internal browser does not render with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
