Public bug reported:
Hey,
running on Ubuntu 22.04.2 LTS.
I upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and suddenly
experienced the problem described here:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966808
black screen and logs like in #2 of above post.
My own Logs:
Jul
Hey Daniel,
new bug opened:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656
thanks
--
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/1966808
Title:
[radeon] gnome-shell
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.
https://bugs.launchpad.net/bugs/202
At least one more colleague in my company just experienced the same
issue after upgrading.
--
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/2027656
Title:
blank screen after mutter up
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3047
https://gitlab.gnome.org/GNOME/glib/-/issues/3047
** Also affects: glib via
https://gitlab.gnome.org/GNOME/glib/-/issues/3047
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
You have been subscribed to a public bug:
The ubuntu version is automatic updated and then i am facing this issue
that there is not britness control is there in my system ment and my
briness key also not wokring
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.2-0ubuntu1
ProcV
** Package changed: ubuntu => gnome-shell (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/2027645
Title:
britness option is not working and not showing in system menu
*** This bug is a duplicate of bug 2026887 ***
https://bugs.launchpad.net/bugs/2026887
Thanks. Merging into bug 2026887.
** This bug has been marked a duplicate of bug 2026887
[Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15
kernels (Failed to lock front buffer on /de
Nevermind. This bug is affecting regular Ubuntu Desktop too, for those
running the original 22.04 release. It shouldn't happen if you're using
22.04.2 though because that has a new enough kernel to support the
hardware, in theory.
** Also affects: mutter (Ubuntu)
Importance: Undecided
St
Suggested workarounds:
* Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment
* sudo apt install linux-generic-hwe-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/2026887
T
It's a regression introduced in mutter 42.9 by Intel:
https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7
Although they would probably argue it's not a regression so long as you
have a new enough kernel. Since we don't always have a new enough kernel
in jammy w
Please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** 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://
** Description changed:
- Hi Ubuntu Team,
+ [ Impact ]
- MY ISSUE:
- I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy
Jellyfish)).
- But with updated for all packages and with reboot PC, i have error with
starting gdm and access to /dev/dri/card0.
+ gnome-shell/mutter 42.9 f
On Thu, 13 Jul 2023 at 14:10, Daniel van Vugt <2027...@bugs.launchpad.net>
wrote:
> Please run:
>
> journalctl -b0 > journal.txt
>
> and attach the resulting text file here.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification bec
> On test plans, I see both this bug and the other one will be individually
> tested,
> but what's the plan to ensure that other behaviour in mutter isn't regressed?
Mutter and GNOME Shell are massive projects so the next bug is always
somewhere you don't expect. I would not recommend focussing p
Verified fixed on jammy in 42.9-0ubuntu2. Tested using the test plan at
the top of the page and also a 1000Hz Microsoft Classic IntelliMouse. I
actually don't think the bug was as visible in 42.x as it was in 44.x.
The reason is likely because triple buffering in 42.x didn't rely on the
problematic
See also: bug 1899626, bug 1944094, bug 1995173
** Summary changed:
- britness option is not working and not showing in system menu
+ [Lenovo Legion 5] Brightness option is not working and not showing in system
menu
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
** Changed in: linu
drminfo.txt
** Attachment added: "drminfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+attachment/5686013/+files/drminfo.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.lau
--
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/2027631
Title:
[ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI
port
To manage notifications about this bug go to:
connections.txt
** Attachment added: "connections.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+attachment/5686014/+files/connections.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
http
Daniel above are the txt files you've requested.
Have tried 6.2 6.4 kernels in my previous installation with no success.
That's when decided to reinstall and report the bug on clean system with
supported kernel.
Have also tried reinstalling gpu drivers with this guide no success, either
https://d
Fix proposed: https://salsa.debian.org/gnome-
team/mutter/-/merge_requests/100
--
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/2026887
Title:
gnome-shell 42.9 Wayland sessions fail t
** Description changed:
[ Impact ]
gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder
Lake systems running older kernels such as 5.15.
[ Test Plan ]
Try to log into gnome-shell. Verify there is a picture on the screen.
[ Where problems could occur ]
T
** Changed in: glib
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2026826
Title:
glib2.0 (2.77.0 ) breaks Netplan build
To manage notifications abou
I'm setting the importance to Critical per #6 at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
** Changed in: mutter (Ubuntu Jammy)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubu
Public bug reported:
When on home as seen on the image https://imgur.com/a/61q20OR if you
right click for context menu, not right click on a file, but on the
space between the files, after the context menu opens, if the context
option you want to click is on top of a file it cant be clicked and it
This is only happening on the home folder. I have tested other folders
and they work properly.
To replicate this, do the following steps 1 to 3 times. It will
eventually happen. Sometimes on the first try or 2nd try, but I was able
to confirm that up to a maximum of 3 tries are needed to always ge
Daniel van Vugt wrote:
> On the slight chance this is related to another AMD GPU issue I've heard
> about in 42.9, please try adding this to /etc/environment:
> MUTTER_DEBUG_USE_KMS_MODIFIERS=0
This didn't help, unfortunately. What I did:
- Re-enabled hardware acceleration in chrome
- Confirmed
I've cherry-picked the !3498 upstream merge proposal for this issue.
** Changed in: glib2.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad
Fixed for me too. Also fixes drag and drop issues in many apps in where
I would have to make multiple attempts before it would randomly succeed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.n
Package version tested was 42.9-0ubuntu2 (replacing 42.9-0ubuntu1).
Tested in a session running many active applications (Firefox, multiple
windows with video, totem, Various chat applications, etc.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
This bug was fixed in the package evince - 44.1-1ubuntu0.1
---
evince (44.1-1ubuntu0.1) lunar; urgency=medium
* Allow evince to spawn browsers distributed as snaps (LP: #1794064)
- debian/apparmor-profile: include snap-browsers abstracted profile
and allow transitions to t
Thank you! The Netplan build seems to be fixed now. Removing the tag.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2026826
Title:
glib2.0 (2.77.0
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glib2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2
I've tested the mutter packages from -proposed in an AWS Workspace:
https://pastebin.ubuntu.com/p/9Yvgfs7yZr/
And I'm able to successfully change the scale to 200% and then revert
the setting.
The following messages are logged when changing to 200%:
https://pastebin.ubuntu.com/p/Y5QdXSqcsW/
An
** Description changed:
[Impact]
gnome-control-center crashed when switching to mirror mode and monitors don't
have matched resolution
[Test case]
Mirror mode is only an option if there are only 2 monitors connected even if
one monitor is disabled. A laptop's internal screen counts as
Thank you for helping to make Ubuntu better. I have uploaded these fixes
for Jammy and Lunar. They will need to be manually approved by a member
of the Ubuntu SRU team before they will be made available as proposed
updates.
I am unsubscribing ubuntu-sponsors now. Feel free to resubscribe if you
ha
Fabio, just to be clear, could you be specific about what version of
Ubuntu you were using and what version of mutter you had installed?
If this update has fixed the issue here, you can also change the bug tag
from verification-needed-jammy to verification-done-jammy
--
You received this bug not
Actually, we're uploading a new version to jammy-proposed 42.9-0ubuntu3
so you can wait and test that version.
--
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/2020782
Title:
Xdcv: Ch
Public bug reported:
My google account credentials say expired and the control center says I
need to log in so I click on it, select to log in. A window for google
sign in pops up with my email already entered and a next button. when
you click the next button nothing happens. Ubuntu 23.04, gnome-c
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2
with Jammy. I'll test again when 42.9-0ubuntu3 is available in
-proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.n
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2020782
Title:
Xdcv: Changing display scale setting
I'm still struggling to understand how gnome-shell is triggering the
corruption. Maybe try switching between 42.5 and 42.9 a few times again
and verify in both cases the mutter packages remain 42.9.
Also can you find any other app affected?
--
You received this bug notification because you are a
You have been subscribed to a public bug:
I guess it is related to the latest updates. Before I can change refresh rate.
As for now, the refresh rate is fixed (59.88Hz) and I don't have any option to
change it.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersio
Thanks. The kernel is reporting only one official refresh rate for that
monitor:
│ │ ├───Modes
│ │ │ └───3840x2160@60.01 preferred driver phsync nvsync
So that's all you will see in Wayland sessions. To get more custom modes
you can try logging into 'Ubuntu on Xorg' instead. There is a
** No longer affects: mutter (Ubuntu Jammy)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided
Status
The kernel is only seeing the built-in display as "connected":
/sys/class/drm/card0-DP-1/status:disconnected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-eDP-1/status:connected
If we assume one of those DP ports is actually the HDMI port then the
problem would be a connector
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: New => Fix Released
** Description changed:
[ Impact ]
gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder
Lake systems running old
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6831
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6831
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6831
Importance: Unknown
Status: Unknown
--
You received this bug no
49 matches
Mail list logo
