https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in
proposed and I was looking forward to a bunch of custom triggers this
morning.
But I found everything migrated this morning despite those new tests not being
done.
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging
there.
In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there
** Tags added: multimonitor
--
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/1892296
Title:
gnome-control-center cannot change resolution of external monitor
To manage notifications
** No longer affects: gnome-control-center (Ubuntu Focal)
** No longer affects: gnome-control-center (Ubuntu)
** No longer affects: nvidia-graphics-drivers-340 (Ubuntu Focal)
** No longer affects: nvidia-graphics-drivers-340 (Ubuntu)
** No longer affects: nvidia-graphics-drivers-440 (Ubuntu
** No longer affects: nvidia-graphics-drivers (Ubuntu Focal)
** No longer affects: nvidia-graphics-drivers (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/1873403
Title:
This bug was fixed in the package gnome-control-center -
1:3.37.90-1ubuntu2
---
gnome-control-center (1:3.37.90-1ubuntu2) groovy; urgency=medium
* d/p/0009-lock-Add-Lock-Screen-on-Suspend-option.patch,
d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
-
This bug was fixed in the package gnome-control-center -
1:3.37.90-1ubuntu2
---
gnome-control-center (1:3.37.90-1ubuntu2) groovy; urgency=medium
* d/p/0009-lock-Add-Lock-Screen-on-Suspend-option.patch,
d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch:
-
Please also check /var/crash for any crash files. If you find some then
please turn those into new bugs using the 'ubuntu-bug' command. And tell
us the new bug IDs.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Next time the hang occurs, please reboot and then immediately run:
journalctl -b-1 > prevboot.txt
lspci -kv > lspci.txt
gsettings list-recursively org.gnome.shell > settings.txt
and attach the resulting text files here.
Please also run this command to complete the bug report:
It appears you are somehow missing the latest updates. To get them
please:
sudo apt update
sudo apt full-upgrade
Reboot.
Then if the problem still happens please report it to the developers at:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
and tell us the new issue ID.
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. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1878775 ***
https://bugs.launchpad.net/bugs/1878775
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gdm3. This problem was most recently seen with package version
3.34.1-1ubuntu1, the problem page at
*** This bug is a duplicate of bug 1878775 ***
https://bugs.launchpad.net/bugs/1878775
** This bug has been marked a duplicate of bug 1878775
Various programs crashed with SIGSEGV in g_str_hash() from
g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from
Public bug reported:
Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia-
driver-440. Both drivers expressly support the hardware. All varieties
of desktop environment (Xorg, Gnome Classic, Ubuntu)
Bug summary
Screen hangs randomly and iretrievably with the only possibility of
*** This bug is a duplicate of bug 1892440 ***
https://bugs.launchpad.net/bugs/1892440
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 1892440, so it is being marked as such. Please
** Summary changed:
- [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia
cards
+ [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
> it looks like g-c-c has chosen a mode that doesn't actually exist for
xrandr, because none of the modes have an asterisk next to them.
Good point. Please report that as a bug to mutter here:
https://gitlab.gnome.org/GNOME/mutter/issues
--
You received this bug notification because you are
My concern is that you might be taking functionality (deep/wide colour)
away from people for whom it works.
--
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/1890772
Title:
No signal
Thanks.
That new issue you mention is bug 1892521.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: gnome-control-center (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)
** No longer affects:
Just wait for the mutter version 3.36.5 update.
--
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/1855757
Title:
[nvidia] Background image corrupted after standby or resume from
Although as a workaround, changing your background wallpaper should also
resolve it each time.
--
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/1855757
Title:
[nvidia] Background
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Please also use the 'ubuntu-bug' command to create bugs in future.
--
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/1892759
Title:
Glitches in the application menu
To manage
I've heard enough reports of this bug recently from multiple people that
it is confirmed at least.
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
You're probably not using 'gnome-shell-extension-brightness-control'.
Please run this command to send us more information about the system:
apport-collect 1892747
** Package changed: gnome-shell-extension-brightness-control (Ubuntu) =>
gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Please open a separate bug for each issue.
The first issue about page indicators is already bug 1889102.
** Package changed: menu (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
You have been subscribed to a public bug:
Whenever I change my display's brightness using keyboard shortcuts (For
me F11 & F12), Ubuntu hangs a little, the brightness is changed
immediately, but everything (except the mouse) hangs while it is being
changed and sometimes for quite some time after.
You have been subscribed to a public bug:
There is a bug where when a folder is open and closed, the number of
page indications increase for no reason, more than the required number
(Refer attachment):
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3091
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3091
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Also tracking in https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/3091
--
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/1682542
Title:
Add support for top bars on all
I`m facing the same issues on both Ubuntu 20.04.1 and Pop Os 20.04.
Intel® Core™ i3-9100T CPU @ 3.10GHz × 4
Mesa Intel® UHD Graphics 630 (CFL GT2)
Gnome version 3.36.2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
Public bug reported:
The gnome sound settings show wrong icons
https://pasteboard.co/Jo3btdG.png
(here e.g. Chromium icon for Opera)
In the program menu all icons are correct.
(Ubuntu 20.04, Gnome 3.36.1)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center
Public bug reported:
Seeing this on groovy installs after an update.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.36.4-1ubuntu2~build1
Uname: Linux 5.8.3-050803-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Aug 25
Error still present after update for me.
Two 3840x2160 screens - one a DELL XPS 15 laptop screen which is half
the physical size of my BenQ monitor.
Using NVIDIA driver metapackage 440.
With fractional scaling, if I set the inbuilt monitor to 150%, the
EXTERNAL monitor seems to half its
The verification of the Stable Release Update for gnome-panel has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for gnome-panel has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gnome-panel - 1:3.36.2-0ubuntu1
---
gnome-panel (1:3.36.2-0ubuntu1) focal; urgency=medium
* New upstream bugfix release (LP: #1887521).
- gp_menu_utils_launch_uri now mounts volumes if needed (LP: #1876281).
-- Dmitry Shachnev Tue, 14 Jul
This bug was fixed in the package gnome-panel - 1:3.36.2-0ubuntu1
---
gnome-panel (1:3.36.2-0ubuntu1) focal; urgency=medium
* New upstream bugfix release (LP: #1887521).
- gp_menu_utils_launch_uri now mounts volumes if needed (LP: #1876281).
-- Dmitry Shachnev Tue, 14 Jul
Public bug reported:
This is a regression bug as I have no problems with another laptop
running Ubuntu 18.04 LTS.
Trying to access Samba file share on my Synology Diskstation
(smb://diskstation.local) gives me just "Failed to retrieve file list
from server: Software caused connection abort". See
I should add, I don't have an NVIDIA card - intel integrated HD
graphics. As it stands, GNOME is a mess with differential scaling
everywhere some parts are smaller, some are larger (notably the menu
bar).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Summary changed:
- [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04
with nvidia cards
+ [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia
cards
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Also struggling since the latest mutter and/or gnome-shell update
(3.36.4). Font scaling is mismatched throughout the entire GUI. It's
larger than normal in the menu-bar, while it's smaller/squished in
terminal. This makes it difficult to fix. If I scale down to 0.9 to fix
the menu bar, text
It affects Intel integrated GPUs too.
You can downgrade libmutter package temporarily as a workaround:
sudo apt install libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3
sudo apt-mark hold libmutter-6-0
Remember to unhold after fix comes out!
--
You received this bug notification
Public bug reported:
When using nautilus renaming multiple files
file-001, file-002, ..., file-009
to
file-009, file-008, ..., file-001,
the program is not responding and take up more and more memory (up to 2GB).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
Still doesn't work for me after all updates :(
GPU: GeForce MX 250
Command output:
libmutter-6-0:
Installed: 3.36.4-0ubuntu0.20.04.2
Candidate: 3.36.4-0ubuntu0.20.04.2
Version table:
*** 3.36.4-0ubuntu0.20.04.2 500
500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently
forgot setting that in my email. the last systemd upload should fix everything
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45] rbalint: " the last systemd upload" means groovy I guess,
what
Seems like everyone having a AMD GPU is the common denominator.
--
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/1875528
Title:
Extra frozen / stuck mouse cursor after auto screen
Just to confirm my monitor is set to 100% scaling and I still get the
duplicate cursor after wake from sleep. 20.04.1 here with latest updates
still has the issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's
comment's about what his plan is after his revert.
--
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/1892358
Title:
Public bug reported:
If you use an external application to ask totem to start/stop repeating
(via e.g. `playerctl loop -p totem None` or `playerctl loop -p totem
Playlist`), then the "Repeat" checkbox in the UI changes state, but
totem doesn't actually start/stop repeating the track.
Concretely:
To address the two other commenters who mentioned fractional scaling -
that's definitely the cause of the extra mouse cursor in my case. If I
set the display scaling back to 100%, the extra cursor goes away and
stays away between reboots and logout/login cycles. Upon setting it back
to 125%, the
Issue is fixed for me with mutter 3.36.4.
And yes, I got the scaling bug mentioned by Wallo013, too. Although mine
isn't that heavy. I use 100 % and something is setting it below that (75
% - 90 %?). If I change scaling to 125 % and back to 100 %, everything
is fine. After Relogin or Reboot,
Public bug reported:
Hi,
after the latest update to mutter, gnome-shell is constantly resetting
font-scaling after reboot. All programs scale fine, even nautilus, it's
just the shell ui that is being reset.
I get this bug in 2 different ubuntu installations on 2 different pcs. I
use
How do I implement this fix for my system?
--
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/1855757
Title:
[nvidia] Background image corrupted after standby or resume from
suspend
The issue is fixed for me, however now fonts in GDM and gnome desktop (toolbar
at the top and file font on the desktop, but not normal apps) are at least 200%
the normal size. However all config are good (gnome-tweak indicate fonts are at
100% and the screen configurations are all to 100%
No, that doesn't help - the screen stays blank if I set it to 1920x1080
using g-c-c and then run the set max bpc command.
I also tried setting 1920x1080i using xrandr in case that's what g-c-c
was choosing but it worked fine.
With the 1920x1080 setting chosen in g-c-c (and the monitor
o.walbert - that is a really neat trick.
--
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/1892521
Title:
UI bug - system fonts enlarge after every reboot
To manage notifications
Hi!
I have the same problem and it all started after the last update of the
mutter package!
dpkg -l | grep mutter | awk '{print $2,$3}'
gir1.2-mutter-6:amd64 3.36.4-0ubuntu0.20.04.2
libmutter-6-0:amd64 3.36.4-0ubuntu0.20.04.2
mutter 3.36.4-0ubuntu0.20.04.2
mutter-common 3.36.4-0ubuntu0.20.04.2
Here's the output log when I try to open the file with Evince via
terminal.
** Attachment added: "evince-log.txt"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+attachment/5404387/+files/evince-log.txt
--
You received this bug notification because you are a member of Ubuntu
I afraid we can not just trust (EDID_version >= 1.4 &&
EDID_supports_10bit). Because this issue caused by any problematic
component in the middle of pipeline. To ensure the compatibility, better
to just defautly set bpc=8.
Think of one scenario, a speaker get his Ubuntu machine onto stage, plug
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1066
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1066
Importance: Unknown
Status: Unknown
--
You received this
Thank you for your bug report. Could you add it to the bug or if not at
least attach the 'journalctl -b 0' log from the system after getting the
issue
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
Status: New => Incomplete
--
You received
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
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 1892814
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
To re-create the bug, load a photo into gimp and invoke Fx-Foundry
-> Photo -> Enhancement -> Vivid Saturation, the tool does not come up.
It worked until recently and is one of my favorites.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gimp 2.10.18-1
Uname:
Public bug reported:
Fractional Scaling toggle is blank/missing in Settings
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.37.90-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu44
How many people feel mutter 3.36.4 has fixed this bug for them?
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => Incomplete
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Same here. Tried an older nvidia driver (435) but it didn't help.
Affects the desktop and gdm.
Temporary workaround for the desktop: add an autostart command to set
the scaling to a slightly different value and back to the original
value:
dconf write
** Project changed: xorg-server => gnome-control-center
--
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/1890772
Title:
No signal on 4K 60Hz DisplayPort monitor by default, until
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1108
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
** Also affects: xorg-server via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1108
Importance: Unknown
Status: Unknown
msznapka - its the 'Scaling factor' Setting in Gnome Teaks Fonts section
that brings things back to normal if you increase the value and then
reset to 100%. Not the Fractional Scaling in the Ubuntu settings ( not
for me anyway). You need to apt install gnome-tweaks to reset it.
--
You received
I have Lenovo P52 with Nvidia GP107GLM running on Ubuntu 20.04.1 LTS and
after mentioned update my Gnome desktop is weird - top panel font and
all desktop icons font is scaled up to 200%.
Setting Fractional Scaling in Ubuntu settings doesn't help.
--
You received this bug notification because
Oh.. thanks for letting me know!
--
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/1855757
Title:
[nvidia] Background image corrupted after standby or resume from
suspend
To manage
I have Lenovo P52 with Nvidia GP107GLM running on Ubuntu 20.04.1 LTS and
after mentioned update my Gnome desktop is weird - top panel font and
all desktop icons font is scaled up to 200%.
Setting Fractional Scaling in Ubuntu settings doesn't help.
--
You received this bug notification because
Though the issue seems more likely some kind of bad choice of refresh
rate, or doublescan, or interlacing... I am also reminded that we're
still missing this fix:
https://gitlab.gnome.org/GNOME/mutter/-/issues/275#note_776751
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #275
I have low vision and I thought my vision was just deteriorating!
I happened to boot into 18.04 and even after updating it I noticed my fonts in
18.04 were much better on the same hardware. It is most noticeable in the
pull-down panels.
In 20.04, sure enough if I change the scaling factor from
77 matches
Mail list logo
