Sorry I just realized -- this may not be a kernel regression at all.
Mutter 40 was when atomic KMS started being used by GNOME. But it
doesn't work reliably for all kernel drivers. If that happens to include
vc4 then we just need to add it to Mutter's atomic_driver_deny_list.
As a workaround you
** Changed in: mutter (Ubuntu Impish)
Status: Incomplete => 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/1944397
Title:
HDMI does not display anything with Impi
Sadly I'm still getting vc4 freezes in atomic KMS functions even when
GNOME has been told not to use it:
Oct 08 16:16:31 pi400 gnome-shell[968]: Mode setting implementation for
'/dev/dri/card1' (vc4) forced (non-atomic).
...
Oct 08 16:24:38 pi400 kernel: [drm:drm_crtc_commit_wait [drm]] *ERROR*
** Description changed:
[Impact]
Animations stutter constantly on Nvidia in GNOME 40.
We're missing:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1826
[Test Plan]
1. Run glxgears and maximize it.
2. Watch closely.
Expect consistently smooth animation.
[Wh
You have been subscribed to a public bug:
The snap-store process is intermittently using hundreds of megabytes of
RAM. Is this normal? Is there a solution?
Ubuntu 20.04
** Affects: gnome-software
Importance: Unknown
Status: Unknown
** Affects: snap-store-desktop
Importance:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launch
** Package changed: ubuntu => gnome-software (Ubuntu)
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/187
@vanvugt would you be willing to open an issue about this at
https://github.com/raspberrypi/linux/issues since this does look like a kernel
issue?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchp
I was able to reproduce this issue on focal and bionic but not on
impish. I'm still investigating why, since I don't see any changes in
policies that might affect this issue, but I could have missed
something.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This bug is awaiting verification that the linux-raspi/5.11.0-1021.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the
problem still exis
Upstream report was closed as "RESOLVED OBSOLETE" ON 2018-04-14
This report did not expire due to existence of bug watch
So closing now as "Invalid"
** Changed in: gnome-disk-utility (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of U
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/532005
Title:
gnome-power-manager doesn'
Upstream bug report was closed as "RESOLVED WONTFIX" on 2015-02-07
Removing Papercuts task as Ubuntu won't ever carry a patch to offer
this additional functionality through subsequent releases of gedit.
** No longer affects: hundredpapercuts
--
You received this bug notification because you are
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
No longer supported so closing Xenial tasks as "Invalid" (should be "Won
Fix").
** Changed in: hundredpapercuts
Status: Confirmed => Fix Released
** Changed in: appstream (Ubuntu Xenial)
Status: Confirmed => Invalid
** C
Upstream bug has moved to:
https://gitlab.gnome.org/GNOME/shotwell/-/issues/1912
** Bug watch added: gitlab.gnome.org/GNOME/shotwell/-/issues #1912
https://gitlab.gnome.org/GNOME/shotwell/-/issues/1912
** Changed in: shotwell
Status: New => Unknown
** Changed in: shotwell
Remote watch
Upstream issue has moved to:
https://gitlab.gnome.org/GNOME/shotwell/-/issues/1531
** Bug watch added: gitlab.gnome.org/GNOME/shotwell/-/issues #1531
https://gitlab.gnome.org/GNOME/shotwell/-/issues/1531
** Changed in: shotwell
Status: New => Unknown
** Changed in: shotwell
Remote wat
*** Bug 2010325 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2010904 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2010951 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2011127 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2011734 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2011182 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2012146 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
*** Bug 2012007 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manag
I'm also seeing this same issue with a 5.15-rc4 kernel built from
https://github.com/raspberrypi/linux/tree/rpi-5.15.y
[ 408.326395] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]]
*ERROR* [CRTC:77:crtc-3] flip_done timed out
[ 408.326477] [drm:drm_crtc_commit_wait [drm]] *ERROR* fl
linux-raspi/5.11.0-1021.22 does not fix this problem. I am still seeing
the flip_done timed out error message.
** Tags removed: verification-needed-hirsute
** Tags added: verification-failed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
Hello Matthew, or anyone else affected,
Accepted gnome-terminal into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gnome-
terminal/3.38.1-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new pac
Same by me. Update today Ubuntu Budgie 21.10 (roundabout 164MB) but issue is
going on. Starting Video and after some seconds screen freeze, mouse cursor
freeze, system freeze.
Standard after update is reboot before testing!
--
You received this bug notification because you are a member of Ubunt
We've found that this bug is much easier to create on certain monitors.
satmandu, dnoedelfan: what monitors are you using?
--
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/1944397
Title
@jawn-smith, I'm using this display:
https://www.waveshare.com/5.5inch-hdmi-amoled-with-case.htm
with this cmdline.txt:
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait quiet splash
video=HDMI-A-1:1080x1920M@60,rotate=90,panel_orientation=right_side_up
drm.edid_firmware=edid/Waveshare5.
The question is, though, have you *tried* to recreate the bug? A small
period of time logging in/out and trying to select Xorg, then seeing
what's running when you're logged in might give you some clue that it
might just be a universal problem that can be fixed is all that's
required here. Do you
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Impish)
--
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/1944397
Title:
HDMI does not display anything with
32 matches
Mail list logo
