The scripts for automatically deciding what goes into the initrd can be
found in /usr/share/initramfs-tools/hooks/ and initramfs-tools in
general could certainly be made more user-friendly...
In the end the foundations/kernel teams will decide what goes in and
what doesn't. I just have a
Assuming this is https://gitlab.gnome.org/GNOME/mutter/-/issues/3372,
then it's really in upstream release 46.2. So see bug 2068598.
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3372
Importance: Unknown
Status: Unknown
--
You received this bug
Actually the fix for https://gitlab.gnome.org/GNOME/mutter/-/issues/3372
is not in 46.1-2ubuntu1, so that's not the right upstream link.
There are some other crashes fixed in 46.1 so please follow the steps in
comment #1 to identify which crash it is.
** No longer affects: mutter
--
You
Yeah that's not what a proper fix would do, it's just a workaround.
You can work around that new issue by adding 'amdgpu' or 'i915' to
'/etc/initramfs-tools/modules' and then run:
sudo update-initramfs -k all -u
or get the system to automatically insert all the modules you're
currently using
Yes it's been done before. I think the Nvidia drivers still do it
because they're designed for older kernel builds that don't have
SimpleDRM included.
But "needed" is a strong word in this case. It's unusual that you
wouldn't be able to see the primary boot display at boot time. So in
that case I
Verified fixed on a Raspberry Pi 400 using version
2.44.2-0ubuntu0.24.04.2
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified fixed on a Raspberry Pi 400 using version
2.44.2-0ubuntu0.24.04.2
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
Status: New => Fix Committed
--
You
Maybe this is now "Won't Fix" in favour of bug 2067597?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066044
Title:
New upstream release 535.179
To manage notifications about this bug go to:
Looks like this bug has only ever been observed with AMD CPUs, which
might be a factor.
Also I wonder if the Nvidia driver misconfiguration might be caused by
third party software like Steam?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In case the problem is bug 2062426, please try the workarounds from bug
2060268. If that does not solve it then please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash
The accented text colour is due to one or two factors:
1. Lossy video encoding (we're not going to change that)
2. GTK3 apps (including Desktop Icons NG) still use RGB font
antialiasing, which is no longer present in GTK4 apps. You can remove
that by running:
gsettings set
If you have a VM running KDE or LXQt and it boots to a black screen then
see bug 2063143.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To
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
** Tags added: simpledrm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069039
Title:
Disk password prompt isn't shown in external monitor
To manage notifications about this bug go to:
This is probably a "Won't Fix" but I'll give others time to chime in and
correct me...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069039
Title:
Disk password prompt isn't shown in external
Timo is right I think. Secondary monitors will only wake up after:
1. The native kernel DRM graphics driver is loaded.
2. Plymouth detects the new driver and switches to it.
And the native kernel DRM graphics drivers seem to be loading slightly
later now that we have kicked them out of the
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: xwayland (Ubuntu Oracular)
Importance: High
Status: Triaged
** Also affects: mutter (Ubuntu Noble)
Just tested again. Switching back to Nvidia 535.171.04-0ubuntu2 on Noble
I don't get any crashes in GNOME apps. Definitely using Wayland. They
all just work.
I wonder why it works for some people but not others. Maybe the driver
installation method? I ended up installing my driver using 'sudo apt
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
** This bug has been marked a duplicate of bug 2063827
Gnome apps segfault in Nvidia Wayland sessions on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was expecting the Ubuntu desktop but also without this bug :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To manage notifications about
Florian, please use bug 2062951 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066268
Title:
Sometimes screen flashes black, probably a driver issue?
To manage notifications about this
That sounds like a whole new bug. Try rebooting and be sure to select
'Ubuntu' before logging in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved
No please don't delete card1.
Try logging out and then on the login screen choose 'Ubuntu on Xorg'
from the menu in the bottom right corner. Then log in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu)
Assignee: Jeremy Bícha (jbicha) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068598
Title:
Mutter release 46.2
To man
Same problem here too, affects ZapZap and Yuki
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064177
Title:
Window borders and shadows missing from GTK3 dialogs (if autologin is
enabled and Xorg
It looks like you're using Xorg so that should be handling the cursor
movement independently of gnome-shell. Is it really just gnome-shell
using high CPU?
Please try:
gnome-extensions disable d...@rastersoft.com
** Summary changed:
- gnome-shell using more than 50% of CPU by simply moving
** Tags added: flicker i915 mantic noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
To manage notifications about
Does it sound like bug 2064177? Are you using Xorg or autologin?
Can you attach a screenshot?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please
"Scale Display: Always + Auto resize VM with window" sounds like a
feature of the hypervisor. Which hypervisor are you using?
Usually to resize a VM dynamically it either uses;
(a) A custom Xorg driver in the guest (but you're not using Xorg); or
(b) Virtually hotplugging the virtual monitor
Are there multiple card devices in /dev/dri/ ? If so then please try:
sudo rm /dev/dri/card0
and log in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution
** Summary changed:
- Resolution is not saved anymore
+ VM guest resolution is not saved anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved
** Tags added: jammy
** Summary changed:
- Desktop icons in Mantic doesn't honor dock margins in Jammy
+ Desktop icons from Mantic doesn't honor dock margins in Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like there's one root cause in mesa/egl-wayland/GNOME causing that
Zink error and the original crash here. Because I don't think(?) Nvidia
should be trying to use Zink, and if it didn't then the original crash
also would not happen.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 2026194 ***
https://bugs.launchpad.net/bugs/2026194
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 2026194, so it is being marked as such. Please
See also bug 2067872.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827
Title:
Gnome apps segfault in Nvidia Wayland sessions on Noble
To manage notifications about this bug go to:
Actually there is more relevant detail here so let's keep this one.
** This bug is no longer a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
** Summary changed:
- Gnome Control Center fails to open on Wayland
+ Gnome apps segfault in Nvidia Wayland sessions
Sorry I didn't see this bug earlier. For now I'm going to group it with
bug 2067872 because that one is more generic and has more relevant
links.
** This bug has been marked a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
--
You received this bug
That last issue is bug 1876632.
** Tags added: noble nvidia nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827
Title:
Gnome apps segfault in Nvidia Wayland sessions on Noble
To
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
Also reported in bug 2063827
** Changed in: egl-wayland (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => Confirmed
** This
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
** This bug is no longer a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
** This bug has been marked a duplicate of bug 2063827
Gnome Control Center fails to open on
The high CPU looks like it's just because the system is using software
rendering, because there's no GPU. Ideally moving a mouse cursor
shouldn't need a real GPU though, just basic display hardware.
While the high CPU is happening, please run:
sudo apt install drm-info
sudo drm_info >
The phantom display affects all Nvidia driver versions at the moment.
And yes simple-framebuffer is the same thing as simpledrm. I think the
former is just the internal backend name. Which is reported by
`drm_info` (from `sudo apt install drm-info`)?
--
You received this bug notification
Slightly more detail:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/comments/4
** Summary changed:
- Gnome apps segfault in wayland session (noble)
+ Gnome apps segfault in Nvidia Wayland session (noble)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 2067872 ***
https://bugs.launchpad.net/bugs/2067872
Already tracking in bug 2067872.
** This bug has been marked a duplicate of bug 2067872
Gnome apps segfault in wayland session (noble)
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 2067872 ***
https://bugs.launchpad.net/bugs/2067872
Looks like Nautilus is probably crashing in the same place:
https://errors.ubuntu.com/oops/aaa02b0a-26fb-11ef-8bb4-fa163ec8ca8c
https://errors.ubuntu.com/oops/ba059c7d-26ff-11ef-8bb5-fa163ec8ca8c
**
*** This bug is a duplicate of bug 2067872 ***
https://bugs.launchpad.net/bugs/2067872
From _usr_libexec_xdg-desktop-portal-gnome.1000.crash:
Stacktrace:
#0 _dl_close (_map=0x0) at ./elf/dl-close.c:770
map = 0x0
#1 0x70109e96f51c in __GI__dl_catch_exception
Phasing is complete and dist upgrades seem to work (just tested it).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
Dist upgrades from Jammy to Noble crash [Oh no! Something has gone
Public bug reported:
Using QXL graphics in a VM (the default for GNOME Boxes), the desktop
freezes in Wayland sessions for long periods of time. I think mostly
whenever I try to interact with an app window? If I'm only interacting
with the shell then it doesn't freeze.
First noticed in 22.04 and
** Summary changed:
- Irregular frame rate in fullscreen glxgears
+ Irregular frame rate in fullscreen glxgears on Intel Meteor Lake
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068567
Title:
While the problem is happening, please run:
ps -e -o pid,pcpu,comm --sort -pcpu | head -20 > tops.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Package changed: gnome-shell (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You
Please try the workarounds in bug 2060268.
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062426
Title:
simple-framebuffer: swiotlb buffer is full
To manage notifications
** Tags added: nvidia simpledrm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068574
Title:
Screen lock crashes after playing fullscreen games
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 2062426 ***
https://bugs.launchpad.net/bugs/2062426
** Tags added: nvidia simpledrm
** This bug has been marked a duplicate of bug 2062426
simple-framebuffer: swiotlb buffer is full
--
You received this bug notification because you are a member of
James, please try:
gnome-extensions disable tiling-assist...@ubuntu.com
and then log in again (inspired by bug 2068850). Does that avoid the
crash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2050865 ***
https://bugs.launchpad.net/bugs/2050865
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 2050865, so it is being marked as such. Please
Please try adding kernel parameter: i915.enable_psr=0
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The only problem I can see here is bug 2062426. You should be able to
use the workarounds from bug 2060268 to try and solve that. If you still
have issues with the workarounds in place then please follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
** Package changed: plymouth (Ubuntu) => flash-kernel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065831
Title:
On upgrade to 24.04 on Pi Zero 2W, package plymouth 24.004.60-1ubuntu7
*** This bug is a duplicate of bug 2065831 ***
https://bugs.launchpad.net/bugs/2065831
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 2065831, so it is being marked as such. Please
*** This bug is a duplicate of bug 2063970 ***
https://bugs.launchpad.net/bugs/2063970
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 2063970, so it is being marked as such. Please
That screenshot can't be accessed by Launchpad. Try renaming it with
latin characters.
Also it sounds like you might be talking about bug 1924689?
** Package changed: gdm3 (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because
> Something seems to run very frequent keeping cpu from going to sleep.
You can use 'powertop' to see what is waking up the CPU most frequently:
sudo apt install powertop
sudo powertop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Also that test failure reliability issue (bug 2068119) had already been
fixed in all later Ubuntu releases via Debian. It was unlucky that 22.04
was missing that fix because the fixed-in-Debian path only put it in
Mutter 43 and later. That has also been fixed now so future Jammy
updates won't get
I agree the time delay was unacceptable here. Although I did write the
fix immediately, it got stuck in red tape and an element of bad luck.
The offending change could not be rolled back because it fixed an issue
for a major partner as mentioned in comment #23.
For most of May I was away (work
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/323
** Changed in: plymouth (Ubuntu)
Status: Triaged => Fix Committed
** Tags added: fixed-in-plymouth-24.x fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Package appears to be missing the desktop and icon files when installed
using the package apt and does not appear in the menu system. Manually
downloading original tarball and placing files in standard locations
fixes the problem.
** Affects: xdemorse (Ubuntu)
Confirmed still happening on Noble, same as comment #3.
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967488
Title:
[nvidia] Chromium stable snap doesn't display anything on
Just ran into this again. The solution was to:
sudo apt install linux-modules-nvidia-535-`uname -r`
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: Incomplete => New
**
** Changed in: gnome-shell-extension-tiling-assistant (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063970
Title:
Enhanced tiling orange shading
** Tags added: fixed-in-tiling-assistant-47
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064646
Title:
Click on the topbar invokes the enhanced tiling on maximized windows
To manage
Please repeat:
ps -eo pid,pcpu,comm --sort -pcpu | head
several times to confirm which processes are the busiest.
** Summary changed:
- High power consumption of gnome-shell
+ High power consumption
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also confirmed in bug 2068574.
** Tags added: noble simpledrm
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can't see any gnome-shell crashes there, but I can see kernel bug
2062426 causing the X server some problems. Please try the workarounds
mentioned in bug 2060268.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 2050865 ***
https://bugs.launchpad.net/bugs/2050865
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 2050865, so it is being marked as such. Please
*** This bug is a duplicate of bug 2064646 ***
https://bugs.launchpad.net/bugs/2064646
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 2064646, so it is being marked as such. Please
*** 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
Please collect a log from the failed boot. If for example it was the
previous boot then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Matthew,
Thanks a lot for your reply! If you track the upstream stable queue and
cherry-pick everything that is really perfect. The vxlan fix I submitted
to stable yesterday and I'd expect it to be queued some time around next
week.
Thanks,
Daniel
--
You received this bug notification
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Jeremy Bícha (jbicha)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068598
Title:
Mutter release 46.2
To man
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068624
Title:
Testing, please ignore
To manage notifications about this bug go to:
After you replace the hard drive I would recommend installing Ubuntu
20.04 again because that's the last release to contain the correct
Nvidia driver version 340 required for your GeForce 8400 GS card.
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification
I can see two issues here that might explain "system gets jammed":
(a) sda (The Western Digital 80GB hard disk) is experiencing hardware
errors which can cause long freezes.
(b) nouveau doesn't have adequate firmware which can cause freezes
(actually nouveau can cause freezes regardless).
It can also happen if you accidentally press the Super (Windows) key.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Luke, you have the wrong bug. That's bug 2050865.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064037
Title:
gnome-shell crashes with SIGSEGV in tilingWindowManager.js:99
To manage notifications
Jon, thanks. I can see your recurring crash is a segfault in:
#0 653db2ce7fb8 i
file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/tilingWindowManager.js:99
(2e2d19d6b790 @ 78)
#1 653db2ce7ee0 i
Jon, it looks like simpledrm is also a factor for you due to Nvidia, so
please also try the workarounds mentioned in bug 2060268.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064037
Title:
=d6fe532b7499e4575f9647879b7a34625817fe7f
-
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3998d184267dfcff858aaa84d3de17429253629d
-
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1cd4bc987abb2823836cbb8f887026011ccddc8a
Thanks a lot for your help,
Daniel
Public bug reported:
Release Mutter 46.2 to Oracular and eventually SRU to Noble.
** Affects: mutter (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Tags: noble oracular
** Description changed:
- Release Mutter 46.2 to Oracular
I might have misinterpreted this bug and now wonder if it is similar to
bug 2040977. Can you try the workaround mentioned there?
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
Are you locking the screen while in the overview? If so then a fix for that is
coming:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3252
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu)
Importance: High => Medium
** Changed in: mutter (Ubuntu Jammy)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068119
Title:
Mutter
The scrolling issue is bug 2066126 so we can ignore that here.
As for the crash, please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found
Dist upgrades are known to fail mostly due to bug 2054761. The fix for
that is still not fully rolled out to all users so we don't recommend
upgrades just yet.
In my own testing I found this was able to recover such a failed
upgrade:
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3515
https://gitlab.gnome.org/GNOME/mutter/-/issues/3515
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3515
Importance: Unknown
If committed in readiness for 42.9-0ubuntu9, but there's no need to
actually release that right now.
https://salsa.debian.org/gnome-
team/mutter/-/commit/9dc8a804dd75f72cecaf938551d8d16044c2b49b
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received
In Progress
** Changed in: mutter (Ubuntu Jammy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug not
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Assignee: (unassigned) => Sundeep (smedius)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847712
Title:
Desktop icons vanishing
** Summary changed:
- Screen glitching
+ [nvidia] Whole screen pans with cursor movement
** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 117872 matches
Mail list logo
