[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
libdrm.so.2 => /opt/amdgpu/lib/x86_64-linux-gnu/libdrm.so.2 (0x785c9fdef000) -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
just realised mutter isn't even installed on fresh 24.04 installs, that's why i failed to reproduce that on a fresh install -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2061320] [NEW] In the filesystem view, the available space column overflows the window if all columns are selected
Public bug reported: In the filesystem view, the available space column overflows the window to the side if all columns are selected (GNOME System Monitor 46.0-1build1) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Attachment added: "Ekran Görüntüsü - 2024-04-14 22-59-01.png" https://bugs.launchpad.net/bugs/2061320/+attachment/5765352/+files/Ekran%20G%C3%B6r%C3%BCnt%C3%BCs%C3%BC%20-%202024-04-14%2022-59-01.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/2061320 Title: In the filesystem view, the available space column overflows the window if all columns are selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2061320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
IDK if it matters, but the configuration I have been using is an in- place upgrade from 22.04. -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Attachment added: "environment dump as requested" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763589/+files/env.txt -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
The "symbol lookup error" happens regardless of what way it has been started, even invoking "mutter --version" from the command line fails. -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Journal dump uploaded. ** Attachment added: "boot.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763348/+files/boot.log -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
The "journalctl -xb" one, right? -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Attachment added: "libdrm.so.2" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763104/+files/libdrm.so.2 -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Attachment added: "libmutter-14.so.0" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763105/+files/libmutter-14.so.0 -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
note that this started happening after 64-bit time_t transistion of dependency packages last week -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
the version of libdrm.so.2 is identical to the version packaged, I have purged and reinstalled the package three times to make sure this is the case -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Attachment added: "packages.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+attachment/5763093/+files/packages.txt -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
possible duplicate of https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285 ? -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Purging and reinstalling libmutter-14-0 and libdrm2 didn't work either -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
The bug persists after reinstalling libdrm2. -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Yes, I do have librdm2 version 2.4.120-2 both for amd64 and i386 (dpkg won't let me install different versions for each). As the graphical session failed to start, I tried to invoke apport-collect from terminal (with multi-user.target -ish level of services having already started), but it redirected me to the "default" browser, which happens to be firefox for GUI and lynx for terminal in my case. I couldn't progress after the password prompt as lynx apparently doesn't support http Referer feature. Here, apport should present its own login prompt or allow fetching the access token from system keyring for more robustness. -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
** Tags added: regression-release -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1630931] Re: Wayland turkish language bug
** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1630931 Title: Wayland turkish language bug To manage notifications about this bug go to: https://bugs.launchpad.net/kiddomonster/+bug/1630931/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060391] [NEW] gnome desktop cannot start as mutter fails to find drmModeCloseFB
Public bug reported: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Summary changed: - mutter fails to find drmModeCloseFB + gnome desktop cannot start as mutter fails to find drmModeCloseFB ** Tags removed: regression-release -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009712] Re: Gnome lock screen loses focus if a window opens while screen is locked
Reason of focus loss is different in mantic (GNOME 40 series) than before (GNOME 3 series). For GNOME 40 series, I have temporarily applied a workaround in my personal configuration to disable the lock screen, but wouldn't recommend that in a work or school computer. ** Tags added: noble -- 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/2009712 Title: Gnome lock screen loses focus if a window opens while screen is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1708850] Re: Strange colour artifacts on GNOME desktop
** Changed in: gnome-desktop3 (Ubuntu) Assignee: (unassigned) => Erkin Alp Güney (erkinalp9035) ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Invalid -- 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/1708850 Title: Strange colour artifacts on GNOME desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1708850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009712] Re: Gnome lock screen loses focus if a window opens while screen is locked
** Information type changed from Public to Public Security -- 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/2009712 Title: Gnome lock screen loses focus if a window opens while screen is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1504 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1504 Importance: Unknown Status: Unknown -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
Failure to understand why that option is hidden, or in some cases, that the profile is actually available but the gnome-control-center hides it anyway. -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
The selector defaults to balance, but an inexperienced gamer or a desparate power user may force the performance profile via the command line, despite the fact gnome-control-center thinks it is not available. -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
> The fact that we didn't see reports about it until now is also an indication that it's not a common problem Hard to encounter by a casual office user, but power users, overclockers and high performance gamers are very likely to encounter this bug ("performance" profile is conditionally hidden by the gnome-control- center but the test hiding it does not always work correctly, sometimes it is hidden even when it is actually available by the hardware, such as I encountered in my Zen 3 processor). -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
> Could you provide some details on how you set a profile which isn't available? I invoked powerprofilectl and "fixed" the performance profile using that. And then gnome-control-center would throw a fatal assertion failure (UI cannot open, basically total non-function of the app), and stop working. If the profile setting is rolled back using the same powerprofilectl, it can be opened again. The patch from upstream converts this error into a logged non-fatal warning. -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
related freeze exception from upstream: https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues/101 ** Tags added: jammy ** Bug watch added: gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues #101 https://gitlab.gnome.org/Teams/Releng/freeze-breaks/-/issues/101 -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 + + I had to wait for this long because I expected a 42.x backport in the + backports repository of .1 release, but no one bothered to do such a + backport. -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] [NEW] [jammy]backport #1453 from upstream
Public bug reported: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gnome-control-center (Debian) Importance: Undecided Status: New ** Tags: cherry-pick ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. + The bug in question makes the gnome-control-center crash if an unsupported + power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 ** Also affects: gnome-control-center Importance: Undecided Status: New ** No longer affects: gnome-control-center ** Also affects: gnome-control-center (Debian) Importance: Undecided Status: New -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 150373] Re: creating a 7zip gives error
Still present in cosmic. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/150373 Title: creating a 7zip gives error To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/150373/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1708850] [NEW] Strange colour artifacts on GNOME desktop
Public bug reported: Randomly, strange color artifacts related to antialiasing happen on GNOME 3 on Wayland session ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "How it looks like" https://bugs.launchpad.net/bugs/1708850/+attachment/4927651/+files/2017-08-05%2018-24-09%20ekran%20g%C3%B6r%C3%BCnt%C3%BCs%C3%BC.png -- 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/1708850 Title: Strange colour artifacts on GNOME desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1708850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1358717] [NEW] nautilus crashed with signal 5 in wl_display_connect()
Public bug reported: Nautilus crashes just after login. Autologin and desktop icons are enabled. Manual execution of nautilus is not affected. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu12 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 Date: Sun Aug 17 11:01:07 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-08-11 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140811) ProcCmdline: /usr/bin/nautilus Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_connect () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_manager_open_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gtk_init_check () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with signal 5 in wl_display_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: nautilus (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash utopic ** Description changed: Nautilus crashes just after login. Autologin and desktop icons are - enabled. + enabled. Manual execution of nautilus is not affected. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu12 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 Date: Sun Aug 17 11:01:07 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: - + InstallationDate: Installed on 2014-08-11 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140811) ProcCmdline: /usr/bin/nautilus Signal: 5 SourcePackage: nautilus StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 - wl_display_connect () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 - gdk_display_manager_open_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 - gtk_init_check () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 + wl_display_connect () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + gdk_display_manager_open_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + gtk_init_check () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with signal 5 in wl_display_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Information type changed from Private to Public -- 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/1358717 Title: nautilus crashed with signal 5 in wl_display_connect() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1358717/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60961] Re: /me-messages are not shown
*** This bug is a duplicate of bug 60527 *** I am using de_DE.UTF-8 ... might be, this is the translation-bug. I will mark this one as a duplcate for #60527 and file a new bug if it does not disappear if #60527 is closed. ** This bug has been marked a duplicate of bug 60527 xchat-gnome /me misbehaviour -- /me-messages are not shown https://launchpad.net/bugs/60961 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60527] Re: xchat-gnome /me misbehaviour
** Bug 60961 has been marked a duplicate of this bug -- xchat-gnome /me misbehaviour https://launchpad.net/bugs/60527 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60961] /me-messages are not shown
Public bug reported: (edgy) When sending a message with /me sometimes the sended message is not displayed, only the own nick is shown. The message is posted, it's just not shown in the senders xchat. ** Affects: xchat-gnome (Ubuntu) Importance: Untriaged Status: Unconfirmed -- /me-messages are not shown https://launchpad.net/bugs/60961 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 43681] User gets no shutdown/reboot notification
Public bug reported: Affects: notification-daemon (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Binary package hint: notification-daemon On RedHat systems at our university installation, the xconsole application pops up a GUI notification when the system is due to be rebooted or shut down. On Ubuntu, there is no GUI notification. The machine just reboots while the user is in the middle of their work, without any notification that there will be a reboot! The exception is if the user has a tty open, in which case they will get the message: Broadcast message from [EMAIL PROTECTED] (pts/11) (Mon May 8 21:23:22 2006): The system is going DOWN for reboot in 10 minutes! Unfortunately, most users today don't keep an X terminal running these days, so such notifications should reach the user, perhaps via notification-daemon. An alternative might be to have some kind of egg-timer along the lines of the battery applet, but this might be too invasive/overengineering for the dapper release. -- User gets no shutdown/reboot notification https://launchpad.net/bugs/43681 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37159] Screenshot
It's Dapper Drake. Screenshot at http://muehlenschulte.de/home/fileadmin/downloads/Screenshots/Rhythmbox-Podcastbug.png hth, Albrecht -- Window not resizable with specific podcasts https://launchpad.net/malone/bugs/37159 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37159] Window not resizable with specific podcasts
Public bug reported: https://launchpad.net/malone/bugs/37159 Affects: rhythmbox (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: When playing a podcast, the applicationwindow is no longer resizable, for the podcast-title does not get shorted and has to be displayed completly. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37159] Window not resizable with specific podcasts
Public bug report changed: https://launchpad.net/malone/bugs/37159 Task: ubuntu rhythmbox Severity: Normal = Minor -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37159] Window not resizable with specific podcasts
Public bug report changed: https://launchpad.net/malone/bugs/37159 Task: ubuntu rhythmbox Binarypackagename: None = rhythmbox -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36497] Crash when closing beep-media-player
Public bug reported: https://launchpad.net/malone/bugs/36497 Affects: metacity (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: metacity crashes under these conditions: Ubuntu dapper Fri Mar 24 22:17:43 GMT 2006 Start beep-media-player Make playlist visible Close beep-media-player Start beep-media-player (playlist should now be visible at start) Minimize main window (playlist window is not minimised, contrary to expected behaviour, and at this point it's impossible to unminimize the main player window until you close the playlist window) Right click on beep-media-player's taskbar entry, click Close. metacity crashes. This is probably triggered by unusual or buggy NETWM use in beep-media-player, but in any case, metacity should not crash as it does now. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36497] Crash when closing beep-media-player
Public bug report changed: https://launchpad.net/malone/bugs/36497 Comment: wm crash has been confirmed on #ubuntu-desktop by seb128 and zyga -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs