Reopened. Still happening on Oracular using a Zenbook S 13. Putting the
screen to sleep didn't fix it, but putting the whole machine to sleep
did fix it.
This reminds me of a (cursor timers) fix that went into Mutter in the
last couple of months which I will need to find...
** Tags added: oracul
Thanks for the bug report. Please start by removing all local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => 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/2086176
Title:
No password dialog after waking up from sleep
I don't suppose it's just disabled?
gsettings get org.gnome.desktop.lockdown disable-lock-screen
--
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/2086176
Title:
No password dial
Thanks for the extra files. It's possible (actually not uncommon) that
the lock/unlock screen is being broken by a buggy extension so the first
thing to try is to remove all local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
--
You received this bug no
If you would like to report a bug about "DMAR" then that would be a
kernel bug. But those messages are common and I don't think they're
important.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
The errors in that screenshot don't sound related to this bug. Please
run:
apport-collect 2086176
which should gather more relevant information now the bug has been moved
to gnome-shell.
** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Stat
The same dependency still exists implicitly in mutter/gnome-shell
because those can't start without Xwayland (unless given the --no-x11
option).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.laun
Please attach a copy of your: /etc/gdm3/custom.conf
--
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/2084727
Title:
Xorg external monitor issue after dist upgrade to 24.04
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2084727
When reporting bugs in the future please use apport by using 'ubuntu-
Yes I still experience the problem too. I think there's confusion
between our desire to remove the feature and upstream having modified
the feature.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubunt
Thanks. I can see the monitor is connected, detected and off...
Next I would like to find out why the system didn't offer Wayland.
Please run this on the machine:
journalctl -b0 > journal.txt
and attach the resulting text file here.
--
You received this bug notification because you are a mem
** Tags removed: fixed-in-mutter-47
** Tags added: fixed-in-mutter-46.4
** Changed in: mutter (Ubuntu Noble)
Milestone: None => noble-updates
** Changed in: mutter (Ubuntu Noble)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop B
g in avoid the
issue?
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Tags added: nvidia-wayland
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this
** Changed in: mutter (Ubuntu)
Milestone: None => ubuntu-25.04
** No longer affects: gnome-shell (Ubuntu)
** Also affects: mutter (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Plucky)
Importance: High
Assignee: Nathan Teodosio (nteodosi
** Tags added: performance
--
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/2085356
Title:
gnome-shell consumes 100% cpu while doing nothing
To manage notifications about this b
** Tags added: performance
--
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/2085772
Title:
High CPU usage when software rendering
To manage notifications about this bug go to:
h
I wonder if dash-to-panel is doing a runtime disable of ubuntu-dock...
Please try explicitly disabling it with:
gnome-extensions disable ubuntu-d...@ubuntu.com
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
--
You received this bug notification becaus
> Do you think it is still worth to try the above ?
Yes please try the commands in comment #2 and log in again.
--
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/2085795
Title:
This can happen when there is a buggy extension. When locking/unlocking
the screen, extensions are told to deactivate/reactivate, and if any
crash during that time then it can leave the shell in a bad state.
To fix this, just delete all locally installed extensions:
cd ~/.local/share/gnome-shel
GNOME is not well optimized for software rendering. But GNOME is not
alone there... It just uses OpenGL for everything and Mesa implements
OpenGL either on a GPU or by using a bunch of CPU cores(!). So really
it's GNOME's fault for not having a true native software-rendering
backend to bypass Mesa.
If you can find a graphics card that is not Matrox, like AMD, Nvidia or
Intel, then that should work around the issue.
** Summary changed:
- high cpu usage
+ High CPU usage when software rendering
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
That should be impossible... Is there anything at all changing on
screen?
Two things I can see so far worth noting:
* Repeated log messages "Can't update stage views actor" suggest X11
apps are running. So when you say "4 shell's", what apps are you
referring to?
* monitors.xml shows a very high
OK. I still can't find an easy explanation for the black screen. One
issue that might be related is the kernel complaining that:
kernel: EDID block 0 is all zeroes
This means there is a problem in the monitor's display cable or the
monitor has buggy firmware. It *might* cause a black screen or
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
--
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/2085728
Title:
Dark Mode
To manage notifications about
** Package changed: gnome-shell (Ubuntu) => gnome-clocks (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/2085794
Title:
Incorrect timezone offset displayed in World Clo
Please try this and tell us if it at least prevents the entire shell
from freezing:
gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false
gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts-network
false
You may need to log in again to test it.
** Changed in
** Summary changed:
- can´t see Carpeta personal and derivatives
+ gnome-control-center: "No Ubuntu settings found"
** Package changed: ubuntu => gnome-control-center (Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => New
--
You received this bug notification be
High CPU is probably expected here. The Matrox graphics card does not
have a GPU so the system has to emulate a GPU on the CPU. Hence very
high CPU usage.
** Changed in: gnome-shell (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
D
** Tags added: noble
--
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/2085755
Title:
Cannot change "enterprise" account password
To manage notifications about this bug
*** This bug is a duplicate of bug 2085356 ***
https://bugs.launchpad.net/bugs/2085356
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 2085356, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1924689 ***
https://bugs.launchpad.net/bugs/1924689
Thanks for the bug report. It is a known limitation that Xorg sessions
cannot set different displays to different scaling factors.
As for "window freezes and creates graphical irregularites", that is bug
19
The screenshot shows a cross next to 'Block Caribou 36' so it's possible
that's crashing and causing other extensions' activate/deactivate calls
to be skipped.
Please try removing 'Block Caribou 36'.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug n
** Also affects: totem (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: totem (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: totem (Ubuntu Noble)
Status: New => Triaged
** Changed in: totem (Ubuntu Noble)
Importance: Medium => Low
** Changed
Please attach a screenshot of the problem so we can better understand
it.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Tags added: oracular plucky
--
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/2085683
Title:
Mouse animations don't show when using gnome-session
To manage notificati
*** This bug is a duplicate of bug 2085356 ***
https://bugs.launchpad.net/bugs/2085356
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 2085356, so it is being marked as such. Please look
** Tags added: fixed-in-totem-43.1 fixed-upstream
** Changed in: totem (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2085575
Title:
Seeki
Thanks for the bug report. Next time the problem happens, as soon as it
recovers please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Freeze
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2085130
When reporting bugs in the future please use apport by using 'ubuntu-
gdm3 is not involved in the lock screen. Are you using Wayland or a Xorg
session?
** Tags added: noble
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://
** Tags added: noble
--
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/2085423
Title:
"Privacy screen enabled" / "disabled" the wrong way on Ubuntu 24.04
LTS
To manage notifications
** Package changed: gnome-session (Ubuntu) => gnome-shell-extensions
(Ubuntu)
** Summary changed:
- after waking up gnome hase 'white screen'
+ gnome-shell crashes on wakeup when 'Window List' extension is enabled
--
You received this bug notification because you are a member of Ubuntu
Desktop
This isn't being reported in the top 100 gnome-shell crashes and doesn't
look familiar to me. Since Marco wrote the privacy screen feature I have
subscribed him...
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
Please also try this as a workaround in /etc/environment:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
and reboot.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Yo
I couldn't find anything telling in those logs. Do you know the exact
date and time the bug occurred?
--
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/2083772
Title:
System gets
Thanks for the bug report. Please start by removing all local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
tell us which processes are using the next most CPU.
Also are there any apps that might be renderin
It didn't occur to me at the time that this would be Xorg and not
Wayland. So there's a chance it's actually Xorg that's frozen. Although
usually that means the cursor wouldn't move, whereas it sounds like the
cursor is still moving here.
--
You received this bug notification because you are a me
Thanks but that backtrace doesn't seem to be frozen. What do the other
threads look like?
--
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/2084015
Title:
gnome-shell has no respo
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
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/2081728
Title:
Startup crash (meta_seat_impl_run_input_task
** Description changed:
+ [ Impact ]
+
+ GNOME Shell Wayland sessions crash on startup if Mouse Keys (and other?)
accessibility features are enabled. This seems to affect a large number of
people:
https://errors.ubuntu.com/problem/8a95f1902f49fc831d4bee942899ed1239896c64
+
+ [ Test Plan ]
+
** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator
in Ubuntu.
https://bugs.launchpad.net/bugs/2085020
Title:
Wrong tray
** Package changed: gnome-shell (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
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/2084959
Title:
Alert Soun
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
Please try deleting any locally installed extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
--
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/
*** This bug is a duplicate of bug 2085061 ***
https://bugs.launchpad.net/bugs/2085061
** This bug is no longer a duplicate of private bug 2081846
** This bug has been marked a duplicate of bug 2085061
gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from
g_hash_table_lookup()
*** This bug is a duplicate of bug 2085060 ***
https://bugs.launchpad.net/bugs/2085060
** This bug is no longer a duplicate of private bug 2081830
** This bug has been marked a duplicate of bug 2085060
gsd-power crashed with SIGSEGV in __GI___libc_free() from
g_hash_table_unref() from g_ha
** Summary changed:
-
/usr/libexec/gsd-power:11:g_hash_table_lookup_node:g_hash_table_lookup:g_dbus_interface_info_lookup_signal:on_signal_received:emit_signal_instance_in_idle_cb
+ gsd-power crashed with SIGSEGV in g_hash_table_lookup_node() from
g_hash_table_lookup() from g_dbus_interface_info
*** This bug is a duplicate of bug 2085060 ***
https://bugs.launchpad.net/bugs/2085060
** This bug is no longer a duplicate of private bug 2082606
** This bug has been marked a duplicate of bug 2085060
gsd-power crashed with SIGSEGV in __GI___libc_free() from
g_hash_table_unref() from g_ha
*** This bug is a duplicate of bug 2085060 ***
https://bugs.launchpad.net/bugs/2085060
For system components like that you might have to use 'sudo apport-cli'
or 'sudo ubuntu-bug'. If the upload succeeds then there should be an
'.uploaded' file created with the upload ID we can use.
One of yo
** Summary changed:
-
/usr/libexec/gsd-power:11:__GI___libc_free:g_hash_table_unref:g_hash_table_unref:info_cache_free:g_hash_table_remove_internal
+ gsd-power crashed with SIGSEGV in __GI___libc_free() from
g_hash_table_unref() from g_hash_table_unref() from info_cache_free() from
g_hash_table
OK, please run:
sudo apt install drm-info
sudo drm_info > drminfo.txt
xrandr --verbose > xrandr.txt
lspci -k > lspci.txt
and attach the resulting text files here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubun
The fix seems to be missing from Salsa (ubuntu/latest). So not 'Fix
Committed' for Plucky.
** Also affects: gnome-shell (Ubuntu Plucky)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: Fix Committed
** Changed in: gnome-shell (Ubuntu Plucky)
Status: Fix
** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: mutter (Ubuntu)
** Tags added: fixed-in-tiling-assistant-48
Remember each bug report should describe ONE problem only.
The problems I can see so far are gnome-shell repeatedly crashing on
shutdown/logout in:
gnome-shell[24010]:
libmutter:ERROR:../src/backends/x11/meta-barrier-x11.c:231:meta_x11_barriers_free:
assertion failed: (g_hash_table_size (x11_
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
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/2084846
Title:
gnome-shell lags after 24.10 upgrade
To mana
This sounds like bug 1967488 so I'd guess each snap needs to get a
similar fix. Regardless, the affected snaps don't sound like part of the
Ubuntu distro so we can't track the bug here. Please report the bug to
the affected app(s):
https://community.brave.com/
https://www.plex.tv/
You can pro
Please open a Terminal window, press Alt+Space and make it 'Always on
Top'. Then run the command 'top'. Now please reproduce the lag problem.
While it is happening, do you see anything using high CPU in the
Terminal window?
** Tags added: performance
--
You received this bug notification because
** Tags added: nvidia nvidia-wayland
--
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/2084853
Title:
[nvidia] Windows experience artifacting. White and Black boxes upon
opening
I never experienced the bug. I'm just trying to get this closer to a
conclusion.
--
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/2026194
Title:
When clicking on some maximized or til
1. The command you want already exists: apport-collect 2084841
2. Yes we can and do automate collection of some information. But it's a
different script per package. If a person reports a bug against the
wrong package then they've automatically got irrelevant or insufficient
automatic attachments
I'm more suspicious of the app's memory efficiency, keeping in mind a
single uncompressed 4K image is 24MB...
20:39:15 systemd: app-gnome-org.gnome.Settings-19194.scope: Consumed
1min 37.065s CPU time, 5.9G memory peak, 144.3M memory swap peak.
But I also don't know if systemd is measuring virtua
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
an
The fix for https://gitlab.gnome.org/GNOME/gnome-control-
center/-/issues/3167 is already in gnome-control-center versions >=
47.rc, so unfortunately that's not the same issue.
** Tags added: performance
** Summary changed:
- Settings app crashes on Appearance tab
+ Settings app slows down and
It looks like this bug should have closed automatically years ago. Which
Ubuntu release are you using?
--
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/1750146
Title:
Xb
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3748
https://gitlab.gnome.org/GNOME/mutter/-/issues/3748
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3748
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Maybe this is the final patch required:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451#note_2250262
--
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/2026194
Title:
When clicking
Should this be tracking https://gitlab.gnome.org/GNOME/gtk/-/issues/6558
? That is indeed fixed in GTK 4.15.0 and 4.14.6, so yes that's in
Oracular.
EDIT: That's GTK4, not GTK3. Maybe not relevant.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6558
https://gitlab.gnome.org/GNOME/gtk
Also the crashes seem to be from Xorg sessions. So gnome-shell might
have been restarted during the upgrade.
--
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/2084761
Title:
gnome
The 'accent-color' key was added in gsettings-desktop-schemas 47.alpha.
It looks like the crashes are from upgrades, which despite having the
newer version of gsettings-desktop-schemas installed, still can't find
the new key just yet.
--
You received this bug notification because you are a member
** Summary changed:
-
/usr/bin/gnome-shell:5:g_settings_schema_get_value:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_enum:st_settings_init
+ gnome-shell crashes with SIGTRAP ("Settings schema
'org.gnome.desktop.interface' does not contain a key named 'accent-color'")
*
*** This bug is a duplicate of bug 2081728 ***
https://bugs.launchpad.net/bugs/2081728
Thanks for the information. Using the config in comment #10 I can
confirm this is another form of bug 2081728. It seems your setting:
[a11y/keyboard]
enable=true
triggers the same crash as bug 2081728.
**
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3749
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/2084189
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => ChunAnWu (kiya956)
** Changed in: gnome-control-center (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-contro
** Changed in: gnome-control-center (Ubuntu Noble)
Assignee: (unassigned) => Dirk Su (dirksu)
** Changed in: gnome-control-center (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: gnome-control-center (Ubuntu Noble)
Milestone: None => noble-updates
--
You received thi
Please try disabling fractional scaling in settings and then log in
again.
Also I expect using a Wayland session would not have this bug. You can
select it on the login screen from the menu in the bottom right (it's
the one called 'Ubuntu' and not 'Ubuntu on Xorg'). Is there any
particular reason
** Tags added: udeng-4796
--
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/1978905
Title:
Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to
Intel GPU display po
** Tags removed: mantic
** Tags added: noble
--
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/2043591
Title:
Starting gnome-control-center resets icon theme
To manage n
Does this need reopening? Are people still experiencing the issue in
24.04 or later?
--
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/1825710
Title:
Remove "Application is ready"
I believe you can do it with "udevadm monitor".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1971434
Title:
Display powersave only blanks, but does not turn off
To
This does not sound related to #2065081 and #2065122 because those seem
to be Nvidia Xorg driver bugs. You have neither Nvidia or Xorg here.
Please elaborate on what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
"some message back to the computer" is probably a hotplug (or unplug)
event. That's why the first workaround works for you, because the
monitor is no longer doing a logical disconnection when it goes to
sleep.
If we could reproduce this reliably in development then it might be
possible to just ign
Fix proposed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4083
--
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/2081728
Title:
Startup crash (meta_seat_impl_run_input_tas
** Changed in: mutter (Ubuntu Oracular)
Status: Triaged => In Progress
--
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/2081728
Title:
Startup crash (meta_seat_impl_run_input_t
Thanks. Those logs show kernel crashes in the i915 driver. But there's
still a chance it could be the Nvidia driver's fault.
Since you're using X11 there's actually no way gnome-shell/mutter could
cause a single display to freeze because X11 forces us to redraw them
all at the same time in a singl
Normally we would say this is a model-specific bug. But I've actually
seen it happen on two laptops of my own. In my case the screen
brightness becomes uncontrollable sometimes after suspend/resume.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-settings-daemon (Ubun
Thanks. There isn't sufficient detail in that crash report:
https://errors.ubuntu.com/oops/9480c9f2-89c2-11ef-a067-fa163ec44ecd
So please continue to report the new crash IDs when it happens again.
** Summary changed:
- Old User Cannot login to Wayland Session After Upgrading to Ubuntu 24.10
G
Please report the issue upstream so that all the GNOME developers can see it:
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Tags added: oracular regression-release
--
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 2051383 ***
https://bugs.launchpad.net/bugs/2051383
I forgot about bug 2051383. It's the same Ubuntu release and close
enough to this one. We should group it there.
** This bug has been marked a duplicate of bug 2051383
gnome-shell high CPU utilization wh
The "ready" notifications were historically related to focus stealing
prevention. So I expect they happen within a fraction of a second of
using a keyboard or keyboard-like device. The shell is trying to avoid
popping up a window in front of you when it thinks you're typing
somewhere else.
Bug 182
1 - 100 of 5364 matches
Mail list logo
