the problem to help developers, but, Im
investigating the problem to see if I can find solutions.
Im using Ubuntu 10.10 with kernel 2.6.35-24-generic.
Thanks in advance,
Cristiano Nunes
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Public bug reported:
Binary package hint: brasero
In Ubuntu 10.10 (kernel 2.6.35-25-generic), Brasero version 2.32.0.
When open an image .iso (without option -i) and close and reopen Brasero
again, the program has an large delay to open.
If open the image with option -i the problens not ocurr.
Same problem here too.
I have two computers. (desktop and notebook)
Here, the problem occur only in notebook.
Hardware of notebook: [Ubuntu 10.10 kernel 2.6.35-25 and glChess 2.32.0]
*-cpu
product: Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz
version: 6.7.10
Today I was tested with version 2.32.1 and the problem persists
again.
This problem happens since the release of Ubuntu 9.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
https://bugs.launchpad.net/bugs/713665
data.iso, the
problens not ocurr.
** Changed in: brasero (Ubuntu)
Assignee: (unassigned) = Cristiano Nunes (cfgnunes)
** Changed in: brasero (Ubuntu)
Assignee: Cristiano Nunes (cfgnunes) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: brasero
When burn an image to DVD, and check this DVD checksum, the value has different.
Example: I trying burn ubuntu-11.04-desktop-i386.iso with MD5:
8b1085bed498b82ef1485ef19074c281
After read the iso of DVD, the MD5 is:
The burners burn in blocks of 32kB each.
When iso's are not exact multiples of 32kB they pad the iso's with 0's when
they write them.
The burning software calculates the MD5 checksum on the original, unpadded iso
image
The MD5 sum calculated after burning includes the padded zeros and will not
*** This bug is a duplicate of bug 878993 ***
https://bugs.launchpad.net/bugs/878993
** This bug has been marked a duplicate of bug 878993
x.org lockup after dragging archived file to desktop
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I have same problem here with Lubuntu 12.04 i386
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/878993
Title:
x.org lockup after dragging archived file to desktop
To manage
Same problem:
Lubuntu 12.04
file-roller:
Installed: 3.4.1-0ubuntu1
pcmanfm:
Installed: 0.9.11~bzr523+201205240448~precise1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/882556
Title:
Crash with drag and drop with LXDE
To manage notifications about this bug go to:
Public bug reported:
The program crash with drag and drop with LXDE using 7zip files
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: file-roller 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
*** This bug is a duplicate of bug 878993 ***
https://bugs.launchpad.net/bugs/878993
This bug is back again in lubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
This bug is back on lubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/878993
Title:
x.org lockup after dragging archived file to desktop (lxde)
To manage
Public bug reported:
Can't extract files into Desktop using File Roller on Xubuntu 15.04.
Steps to reproduce:
- Open an archive with the file-roller gui
- Drag the contents of file-roller (to extract them) over Desktop;
Expected Results:
- The files must be extracted in Desktop filder
Actual
Fix committed:
https://git.gnome.org/browse/file-
roller/commit/?id=17a2be90d8242378000342ce96c29b9f40c221ab
** Changed in: file-roller (Ubuntu)
Status: New = Incomplete
** Changed in: file-roller (Ubuntu)
Status: Incomplete = Fix Committed
--
You received this bug notification
Fix committed, see:
https://git.gnome.org/browse/file-
roller/commit/?id=af95f7d8db4e99e7c661022f77097c69b0becfe2
** Changed in: file-roller (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: file-roller (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1461671
Title:
Can't extract files into Desktop
As long as developers don't perform a code fix, (as a workaround) you
can change the format of your system to the "United States".
Go to "Settings -> Region & Language -> Formats" and change the format.
(more details is explained in
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1412)
--
You
The bug occur if you use the system format that uses 'comma' instead of
'dot' as decimal separator.
** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #502
https://gitlab.gnome.org/GNOME/nautilus/-/issues/502
--
You received this bug notification because you are a member of
This bug occur only in Ubuntu 20.04. I have not found this behavior with
the previous versions.
--
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/1871296
Title:
Activities not
Public bug reported:
I am facing an issue with the new version of Gnome (3.36) in Ubuntu
20.04.
The problem is as follows:
I copied files inside home folder (e.g., documents, images, videos) and
subfolders, then waited for tracker to index, then do a search trough overview
and in Nautilus. The
There is a duplicate in:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/502
** Summary changed:
- Activities not showing some files search in overview
+ Activities not showing some files in search in overview
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #502
Addition: The files are displayed only if they are on "Recent" list.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1871296
Title:
Activities not showing some files in search in
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1412
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1412
** Changed in: nautilus (Ubuntu)
Assignee: (unassigned) => Cristiano Nunes (cfgnunes)
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Com
Same problem here with Ubuntu 20.04.1.
--
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/1423773
Title:
Gnome-Shell don't free ram when I change a wallpaper
To manage notifications
Dear Stefan,
This thread is about a bug in "mutter 3.36.4-0ubuntu0.20.04.2". Just it.
(not about arguing philosophies).
As it is a bug, it ends up embarrassing people. It's normal.
"Freedom of choice" doesn't mean bad software. It is a wrong idea. Also,
Canonical is a company and there are
Other users has a same problem. See:
https://askubuntu.com/questions/906723/fn-media-keys-slow-delayed-on-
ubuntu-gnome-17-04
This problem appears on Ubuntu 17.04, 18.04 and 20.04.
** Package changed: x11-xkb-utils (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because
I use Ubuntu 20.04 and I have the same problem.
A similar bug I reported here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1895486
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome
This validation is blocking the commit for the bug 1892440 (that has
exhaustively already validated).
--
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/1558886
Title:
gnome-shell
I've also tried to reproduce adding a delay (sleep 0.1) between the
commands, but without success.
I've tried:
$ xinput (to get the number of my mouse)
$ while true; do xinput disable ; sleep 0.1; xinput enable ; sleep 0.1;
done
--
You received this bug notification because you are a member
I can't reproduce the crash by using the steps mentioned in "[Test
case]".
After following these steps, the process Xorg consume about 100% of CPU.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Hi, @vanvugt.
The bug 1558886 is a bit complicated to reproduce. I also have tried
some times.
In this case, it would be possible to mark the bug 1558886 as "opened
until validation" and commit the fix for this current bug 1892440 to the
"-updates"?
Because, if we wait someone validate the bug
Public bug reported:
[groovy] Drag and drop files from Desktop to Nautilus freezes gnome-
shell in Ubuntu 20.10 (beta).
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
Hi Daniel! Thanks for your response.
F.Y.: this bug is different from bug 1813441. There, it is not possible
to drag and drop (only).
This bug, in addition to not being able to drag and drop, gnome-shell
crashes.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
It is not possible to see some text/comment on annotations in a PDF
file.
This bug was tracking on:
https://gitlab.gnome.org/GNOME/evince/-/issues/1347
I've replicated this bug here to document and add more people to help
solve the problem.
I've also tested using:
- Ubuntu
** 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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1892440/+attachment/5403290/+files/ProcCpuinfoMinimal.txt
--
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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1892440/+attachment/5403291/+files/ProcEnviron.txt
** Tags added: nvidia xrandr-scaling
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1892440/+attachment/5403289/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Public bug reported:
The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
causes small text in GNOME Shell menu with NVIDIA cards.
With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem
is after update to the (3.36.4-0ubuntu0.20.04.2).
---
ProblemType:
A workaround is set the "Fractional Scaling" to other value and back it
to 100%, to fix the font sizes. But after a reboot, all fonts still
smaller again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
After update to the mutter version (3.36.4-0ubuntu0.20.04.2) the fonts
were smaller (top menu and desktop menu) from Gnome Shell.
I have two computers here, the bug occur with only the computer with
NVIDIA card.
--
You received this bug notification because you are a member of Ubuntu
Desktop
** This bug has been marked a duplicate of bug 1889686
[focal] [nvidia] Patch causes small text in Pop!OS:
x11-Add-support-for-fractional-scaling-using-Randr.patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
New this bug occur in Ubuntu 20.04 with mutter version
(3.36.4-0ubuntu0.20.04.2) as reported in #1892440.
I'm waiting a fix for this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Marco Trevisan will save us! Grazie mille! ;)
--
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/1892440
Title:
[focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu
Hi, Sujit Kumar. The solution of disabling NVIDIA drivers is not so
right, because I need to use my hardware completely (use the NVIDIA
hardware to compute complex matrices in my work).
But thanks for your reply.
--
You received this bug notification because you are a member of Ubuntu
Desktop
7 days have passed. I'm waiting the package be released to "-updates".
LoL
--
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/1892440
Title:
Shell text with wrong size in mutter
Thanks, Brian.
I'll test the new package coming soon.
--
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/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1.
BUT
After an "Automatic Screen Lock", the display turned off, the Gnome
Shell crash and show us a blank screen with the message "Oh no!
Something has gone wrong."
This bug did not appears before the update.
I have a NVIDIA
@ Marco Trevisan,
I'll do that.
Anyway, thanks for the fix. ;)
--
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/1892440
Title:
Shell text with wrong size in mutter
Public bug reported:
[ Impact ]
GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2),
all works fine.
[ Test case ]
Steps to reproduce the error:
1) Lock screen;
2) Turn off the display;
3) Turn
There is a problem:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
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/1896332
Title:
SRU 3.36.6
To manage notifications
@ Marco Trevisan,
After I power down my display and power up again (in the lock screen),
the problem is:
gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor-
manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
I've fill another bug:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818
--
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/1892440
Title:
Shell text with wrong size in
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413599/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413602/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
See also:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
** Description changed:
+ In Ubuntu 20.04.1 (focal):
+
[ Impact ]
GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1.
With the old version (3.36.4-0ubuntu0.20.04.1) and
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413601/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I've tested in a fresh install also.
--
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/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413600/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Attachment added: "lsusb-v.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413598/+files/lsusb-v.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413597/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
In my syslog:
gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor-
manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta-
monitor-manager-
Thanks, Trevinho! ;)
--
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/1896818
Title:
Gnome-shell crash after turn display off in mutter
3.36.6-ubuntu0.20.04.1 (NVIDIA)
To manage
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I've tested the mutter 3.36.6-1ubuntu0.20.04.2~wip1 (in the PPA).
Now, all works fine!
Thanks for your attention and work.
--
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/1896818
Hi, Brian and Marco,
I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed"
repository).
Now, all works fine! Without problems.
Thanks for your attention and work! :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
For ABNT2 keyboards, I've removed the "Scroll Lock" key, see:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/merge_requests/112
It is not the right solution (I even regretted it), but it works...
--
You received this bug notification because you are a member of Ubuntu
** Changed in: mutter (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
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/1892440
Title:
Shell text with wrong size in mutter
The updated package will be released to "-updates" after the bug fixed
have been verified and the package has been in "-proposed" for a minimum
of 7 days.
In this case, the status is: "Fix Committed" (not "Fix Released").
--
You received this bug notification because you are a member of Ubuntu
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1877209
Title:
Update to 3.36.2 and SRU it
To manage
** Changed in: mutter (Ubuntu Focal)
Status: Fix Released => Fix Committed
--
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/1892440
Title:
Shell text with wrong size in mutter
Now, I'm waiting for the SRU team release this fix to "-updates". :)
--
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/1896332
Title:
SRU 3.36.6
To manage notifications about this
Public bug reported:
I'm using Ubuntu 20.10 (beta).
The title bar thickness is different between gtk3 / gtk2 applications.
Gtk3 applications have a thicker title bar. I think all thickness must
be the same to keep the visual identity of the OS.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Public bug reported:
I'm using Ubuntu 20.10 groovy (beta).
The Gnome calendar is not syncing with Google calendar online account.
In Ubuntu 20.04 (focal) there is no such problem.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-calendar 3.38.0-1
ProcVersionSignature: Ubuntu
In Ubuntu 20.04 there is no such problem: all title bars have the same
thickness.
--
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/1898324
Title:
[groovy] Different thickness
Grazie mille, Trevinho!
--
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/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
on Nvidia)
To manage
I did all the tests, and everything seems to be correct.
--
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/1896332
Title:
SRU 3.36.6
To manage notifications about this bug go to:
** Summary changed:
- Shell text is the wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on
Nvidia)
+ Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on
Nvidia)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I did all the tests with PPA, and everything seems to be correct.
--
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/1892440
Title:
Shell text with wrong size in mutter
Marco Trevisan, I found a problem with this fix from PPA:
After an "Automatic Screen Lock" with a monitor turned off, the Gnome
Shell crash and show us a blank screen with the message "Oh no!
Something has gone wrong."
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Gnome-Shell don't free ram when I change a wallpaper
+ [memory leak] Gnome-Shell don't free ram when changing the wallpaper
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Summary changed:
- gnome-shell using a lot of RAM after repeatedly opening the overview
+ [memory leak] gnome-shell using a lot of RAM after repeatedly opening the
overview
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I use Ubuntu 20.04.1 (focal), and I have the same problem. I confirm
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/1532508
Title:
Screen contents revealed briefly
Bug tracking in:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1821
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1821
** Summary changed:
- [media-keys] Fn media keys with lag slow/delay on Gnome
+
87 matches
Mail list logo
