** Summary changed:
- 24.04 Wayland vs Nautilus performance problem
+ Nvidia drivers fail to install libnvidia-egl-wayland1, resulting in Zink
being used
** Package changed: nautilus (Ubuntu) => nvidia-graphics-drivers-545
(Ubuntu)
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
** Tags added: udeng-1398
--
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/2036336
Title:
gnome-shell crashed with SIGSEGV in meta_drm_buffer_gbm_finalize()
To manage
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (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/2071463
Title:
Duplicate unread message
*** This bug is a duplicate of bug 2068539 ***
https://bugs.launchpad.net/bugs/2068539
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068539, so it is being marked as such. Please
** Changed in: gnome-shell (Ubuntu)
Status: Expired => 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/2064169
Title:
Keyboard shortcuts
To manage notifications
Public bug reported:
I have an Nvidia graphics hybrid setup (Geforce GTX 960M + Intel HD
Graphics 530), and Ubuntu 24.04 failed to boot after clean installing.
I switched to the 470-series driver instead of the default 535-series
one, via "Recover mode" and things got working, until I performed
Public bug reported:
This concerns rhythmbox-plugin-alternative-toolbar 0.20.4-1 on Ubuntu
noble.
I see this on installation:
Setting up rhythmbox-plugin-alternative-toolbar (0.20.4-1) ...
/usr/lib/rhythmbox/plugins/alternative-toolbar/alttoolbar_plugins.py:171:
SyntaxWarning: invalid escape
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[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.
[Expired for gimp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gimp (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
I completely forgot about bug 2063036 because I hadn't seen it in a
while.
Please try:
gnome-extensions disable d...@rastersoft.com
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: gnome-calendar (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1865177
Title:
There is an erroneous
While this is being investigated and a fix will be pushed, by disabling
auto login (For the moment) fixes the issue.
--
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/2064177
Title:
While this is being investigated and a fix will be pushed, by disabling
auto login (For the moment) fixes the issue.
--
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/2064177
Title:
> Assuming your analysis identified to be a risk and that's why you
mentioned it, surely this is a scenario that should be part of your Test
Plan?
A corresponding section has been added to the testplan now
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons-ng (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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Description changed:
Impact
--
nautilus-sendto is installed by default in Noble but it is not being used in
nautilus since nautilus dropped the code that used the extension[1] in favor
use the xdg-desktop-portal interface instead.
The issue is that the portal can’t be used to
I've not looked into this in detail yet, but just passing by:
> The original logic must remain unaltered for the case nautilus-sendto
is not installed.
Assuming your analysis identified to be a risk and that's why you
mentioned it, surely this is a scenario that should be part of your Test
Plan?
I don't think that bug you linked is my problem because I'm running an
X11 session and haven't plugged any external displays into the computer.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Journal text files"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2071508/+attachment/5793769/+files/journals.zip
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
1. Yes, I was working for hours, the battery was well over 50% when I
started. The whole issue happened multiple times this year, and twice in
a day last week.
2. I forgot that the laptop was not plugged in, and only noticed the 0%
notification. It is possible that the value jumps, I'll try to
The upstream bug for this was fixed in gjs 1.77.1, so Ubuntu 23.10 and
later. If you have any ongoing issues then please open new bugs.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Also affects: gjs (Ubuntu Mantic)
Importance: Undecided
Status: New
**
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2760
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2760
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Thanks, yes I can see that machine has only successfully sent one of the
gnome-shell crash reports. Unfortunately there seems to be a secondary
bug in either gnome-shell's logging or the crash reporter whereby we
can't see the correct section of the system log. Only that gnome-shell
crashed with
I just reproduced the crash, and now step 3 yielded this:
https://errors.ubuntu.com/oops/0ae6e12e-3774-11ef-8bf5-fa163ec8ca8c
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Doing step 2 and pressing send just closes the window and doesn't
actually give me any output. I've done it twice now. The crash does not
show up on the list of things after following step 3.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
What I had done was purposely caused the crash, then looked in
var/crash, and gnome-shell was the only thing generating crash logs. I
can reliably reproduce the crash. What is the best way to capture the
event?
--
You received this bug notification because you are a member of Ubuntu
Desktop
30 matches
Mail list logo
