Public bug reported:
Dell Intel 12th generation CPU (i5-12400), integrated graphics (UHD
Graphics 730)
Monitor is AOC 27 inch, the standard resolution is 2560x1440
After installing Ubuntu 22.04, the maximum resolution of the
display(using HDMI cable) can only maximum support 1980 x 1080
I have
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-44 fixed-upstream
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
Ubuntu 22.04 Remote Desktop can only show the screen of the main monitor
but not for the second monitor. It did work in Ubuntu 20.04 without any
problem on the same computer.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.7-0ubuntu0.22.04.1
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
--
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/2003237
Title:
Monitor does not turn off after idle
Scott,
Please open a new bug by running:
ubuntu-bug gnome-shell
so that we can investigate your system separately.
--
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/1982560
You have been subscribed to a public bug:
My Screen Blank setting is set to 15 minutes. My Lock Screen settings
are also set to automatically lock the system after the blank screen
timeout is reached.
After 15 minutes Ubuntu does lock me out, but the monitor does not power
off as it's supposed
I was expecting upstream to say "won't fix". Aside from the protocol
saying it's the expected behaviour, we also wouldn't want to impact
performance of fullscreen games just because they accidentally used RGBA
instead of RGBX or RGB. So disallowing anything to show through in full
screen makes
That's probably not as good as sticking to nouveau because it will fall
back to software rendering instead. But the third and best option is to
install an Nvidia driver using the 'Additional Drivers' app.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Tags added: gamma nightlight
--
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/1752680
Title:
Night light does not work after resume from suspend or unlock.
To manage
** Tags added: gamma nightlight
--
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/1772212
Title:
[nvidia] Night light doesn't cover all monitors fully
To manage notifications about
** Tags added: nightlight
--
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/1995783
Title:
Nightlight fails after suspend
To manage notifications about this bug go to:
** Tags added: nightlight
--
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/1972720
Title:
Night light does not work on laptop screen when disconnecting from
external screen
To
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
--
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/1999122
Title:
Gnome 42.5 Nigth Light does not work properly with dual
** Changed in: mutter
Status: Unknown => New
--
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/2003104
Title:
gnome-terminal transparency ignored in full screen mode
To manage
I verified that this regression also shows in Fedora 37. I verified
there because Fedora and Ubuntu ship a patch to enable transparency in
gnome-terminal; gnome-terminal upstream does not have that feature.
I also verified that this regression was introduced in mutter 43.1.
(transparency works in
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
Thank you for reporting this bug and helpinig to make Ubuntu better.
I'm going to collect more data to report this issue upstream since this
issue is blocking us from being able to successfully SRU 43.2 to Ubuntu
22.10.
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
**
I have blacklisted this now using:
sudo vim /etc/modprobe.d/blacklist-nouveau.conf
adding:
blacklist nouveau
options nouveau modeset=0
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2003108/+attachment/5642301/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
apport information
** Tags added: apport-collected jammy third-party-packages wayland-
session
** Description changed:
After I click on the "unmount" icon next to the USB device in the file
tree sidebar on Nautilus, the notification appears with the text "do not
unplug/remove the device".
I accomplished the steps in the test plan using gnome-control-
center{,-data} 1:41.7-0ubuntu0.22.04.6 from jammy-proposed. Issue fixed
as expected.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug
Yes, it is. I tested it in a VM, and can reproduce it.
--
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/2003104
Title:
gnome-terminal transparency ignored in full screen mode
To
** Merge proposal linked:
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435960
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** Changed in: metacity (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/2003176
Title:
SRU: metacity crashes while minimizing a
Sergio, you mean that it looks like this bug was triggered when your
system updated from mutter 43.0-1ubuntu5 to
https://launchpad.net/ubuntu/+source/mutter/43.2-4ubuntu1 right?
** Summary changed:
- Transparency ignored in full screen mode
+ gnome-terminal transparency ignored in full screen
** Merge proposal unlinked:
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435957
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** Changed in: metacity (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/2003176
Title:
SRU: metacity crashes while minimizing a
** Merge proposal linked:
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/metacity/+git/metacity/+merge/435956
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** Description changed:
[General information about the SRU]
* It includes the fix for the bug
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
* The fix is already included in 3.46.0 release:
Public bug reported:
Setting the key binding theme for GTK to Emacs through the usual method
of running
```
gsettings set org.gnome.desktop.interface gtk-key-theme Emacs
```
has no effect. Opening Nautilus, typing a word, and then pressing ctrl-a
will select the whole word instead of moving the
It's not random, at least in my system. Also, the tricks in that bug
report don't work: I tried changing the transparency value, disabling
and enabling again, but no dice.
If I had to bet, I would say that the problem is in the fullscreen
redirection to avoid composition overload with games...
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-terminal (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Confirmed that this happens when libmutter/mutter-common are updated to
version 11.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2003104
Title:
Transparency ignored in
** Description changed:
[General information about the SRU]
* It includes the fix for the bug
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
- * The fix is already included in 3.46.0 version:
Reproducer script:
** Attachment added: "Untitled.py"
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/2003176/+attachment/5642194/+files/Untitled.py
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
Public bug reported:
[General information about the SRU]
* It includes the fix for the bug
https://gitlab.gnome.org/GNOME/metacity/-/issues/31
* The fix is already included in 3.46.0 release:
** Summary changed:
- gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] on Alder Lake with older kernels
+ gnome-shell deadlocked on startup [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] on Alder Lake with older (than
Answer from email to comment #57:
It appears your CPU/GPU (i7-1280P) is too new for that old kernel
(5.14.0-1055-oem). And so you are hitting this bug:
https://launchpad.net/bugs/1991777
But the solution is simple: Just install 22.10 and don't downgrade the
kernel. It should be kernel version
If atomic KMS is disabled then the same bug may present as:
Failed to post KMS update:
drmModeCrtcSetGamma on CRTC 80 failed: Function not implemented
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Please collect a log from the previous boot where it froze:
journalctl -b-1 > prevboot.txt
and create a new bug with that file attached.
Also check for /var/crash files and create new bugs for each using
'ubuntu-bug'.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
SIdebar, files gets unresponsive after unlocking locked season.
Clicking on search bar also freezes the whole season. Issue requires
Restarting GTK3 or restarting the season.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock
I have the same or similar bug. I tried the workaround to
Add to /etc/environmen in Ubuntu 22.10 and later:
MUTTER_DEBUG_FORCE_KMS_MODE=simple
And my computer froze on startup on the Ubuntu screen. When I deleted
the line, my computer again booted up fine.
I have a Thinkpad X1 with Ubuntu
44 matches
Mail list logo
