Not yet, but the good news is it's coming soon:
https://wiki.gnome.org/ThreePointThirtyseven
And should be in Ubuntu 20.10 soon after that.
Also note your log is still mentioning errors from:
/home/carlos/.local/share/gnome-shell/extensions/clipboard-
indica...@tudmotu.com/...
The simplest
> For me, only GNOME 3.38 (prerelease) is close to smooth at 4K.
Is there a reasonably simple way to test this in Ubuntu? Or maybe I
could look for a package in the AUR.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in U
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399150/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
> 1. Reboot, make sure you still see stuttering and then run these
commands:
Done
> 2. Completely uninstall these extensions:
They weren't installed in fact, just remaining configurations of old
installations. I've removed every reference to them from my settings
now.
> 3. Disable 'Ubuntu AppI
> Also remember to update your system because it appears to be out of
date...
Strange cause I manually run the GUI updater on a daily basis. But it's
showing no update while I get 7 upgradeable packages from the CLI. Done,
just small things, no difference.
--
You received this bug notification b
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890533/+attachment/5399149/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
Attaching original screenshots:
gnomeTerminalMaximiseBugScreenshot1-afterLScommand.png
gnomeTerminalMaximiseBugScreenshot2-afterMaximize.png
** Attachment added: "gnomeTerminalMaximiseBugScreenshots.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1890382/+attachment/5399148/
Also remember to update your system because it appears to be out of
date...
sudo apt update
sudo apt full-upgrade
Reboot
--
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/1890
I have encountered a seemingly related issue where ls is sometimes
displaying different output depending on the terminal display size (and
when the function is called), independent of maximisation.
** Attachment added: "gnomeTerminalDisplayBugScreenshot.png"
https://bugs.launchpad.net/ubuntu/+
Although I would not be surprised if those don't work adequately. For
me, only GNOME 3.38 (prerelease) is close to smooth at 4K. Although 3.36
is at least usable with the MESA_LOADER_DRIVER_OVERRIDE=i965 workaround.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Please try these. You can stop at any step if the problem goes away...
1. Reboot, make sure you still see stuttering and then run these
commands:
lspci -k > lspcik.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
2. Completely uninstall these extensions:
c
** Description changed:
This was first described upstream in https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2697
I'm reporting it here as requested in https://discourse.ubuntu.com/t
/gnome-shell-performance-improvements-in-
ubuntu-20-04/15972/38?u=memeplex
+
+ Please don't be m
Public bug reported:
This was first described upstream in https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2697
I'm reporting it here as requested in https://discourse.ubuntu.com/t
/gnome-shell-performance-improvements-in-
ubuntu-20-04/15972/38?u=memeplex
ProblemType: Bug
DistroRelease: Ubun
Actually the problem might just be that the Linux kernel doesn't
understand extended vendor-specific display timings. I've decoded your
monitor's EDID and it reveals that 3840x2160 30Hz is mentioned:
edid-decode (hex):
00 ff ff ff ff ff ff 00 04 69 a3 28 24 51 00 00
0e 1b 01 03 80 3e 22 78 3a 1c
Thanks. The file xrandr.txt indeed shows the HDMI connection is limited
to 1920x1080. It also shows that's the "current" mode but it lists no
"preferred" mode, which does support the idea that the monitor can do
higher resolution...
The manufacturer's specs mention that 4K is limited to 30Hz over
Done. 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/1890418
Title:
External monitor will not display to 4k
To manage notifications about this bug go to:
https://bugs.launch
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399092/+files/journal.txt
--
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/bu
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399093/+files/lspcik.txt
--
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
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399094/+files/xrandr.txt
--
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
Please run this command to attach more information about the system:
apport-collect 1890418
Please also run these commands:
lspci -k > lspcik.txt
journalctl -b0 > journal.txt
xrandr --verbose > xrandr.txt
and attach the resulting text files here.
** Tags added: focal
** Changed in: m
*** This bug is a duplicate of bug 1849142 ***
https://bugs.launchpad.net/bugs/1849142
You may also need to log out and in again. If the problem persists then
please provide a new log by running:
journalctl -b0 > journal-again.txt
--
You received this bug notification because you are a me
** Tags added: focal
--
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/1715602
Title:
ubiquity-dm / Install Ubuntu - Power button/menu does nothing
To manage notifications about
*** This bug is a duplicate of bug 1715602 ***
https://bugs.launchpad.net/bugs/1715602
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 1715602, so it is being marked as such. Please look
Given that we've implemented the only known solution for this in bug
1877075, the remaining explanation for it might not be thread-related.
Some kind of memory corruption (even single threaded) could have the
same effect.
--
You received this bug notification because you are a member of Ubuntu
De
Yes that stack looks the same as before.
--
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/1886059
Title:
gnome-shell crashed with assertion failure
"!xcb_xlib_threads_sequence_lost"
Hi All,
As described on June 20, the bug went away, but it is back now, so there
must be some way to make it come and go, but I haven't figured out what
I did.
Rob
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
h
After restarting the machine, launching rhythmbox from the command line does
not print messages.
Subsequent launches do however
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/18904
I am talking about the pause/play, previous song and next song keys.
On my Dell xps 13 laptop, those are f4, f5 and f6 (or fn + f4, fn + f5, fn + f6)
When opening Rhythmbox from the command line: (this is after having opened and
closed it once, so the media keys were already not working)
Opening
Thank you for your bug report. Could you start rhythmbox from a command line
and see if any error is printed?
What media keys are you talking about exactly?
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided => Low
** Changed in: rhythmbox (Ubuntu)
Status: New => Incomplete
--
Y
Public bug reported:
Closing Rhythmbox, does not free the media keys, and no program can use
them after that, not even Rhythmbox if you restart it.
This seems to be very close to bug #1036489, but that one was active 8
years ago, and was marked as expired 6 years ago.
Restarting the machine free
This still affects me in Ubuntu 20.04.
Fully closing Rhythmbox does not free up the media keys, and if you
reopen it later the media keys will not work (and won't work for other
programs either)
Different ways to reproduce (note that the only way to have the media
keys working again is to restart
*** This bug is a duplicate of bug 1849142 ***
https://bugs.launchpad.net/bugs/1849142
I looked and I already had Ubuntu AppIndicators turned off.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs
** Tags added: rls-bb-incoming
--
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/1838152
Title:
gnome-shell freezes on notification arrival (fixed upstream)
To manage notificatio
I've just got a similar crash when just clicking on a menu item, I've
got some more complete stacktrace, but don't think is really helpful
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
set =
{__val = {0, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558,
This crash doesn't seem to reproduce anymore, and there's no trace of it
in e.u.c since version 3.36.4 went in proposed.
❯ apt-cache policy libmutter-6-0
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
Reverting to both 100% and 200% works fine, without issues. g-c-c now
requires a further "apply" to turn it off, and mutter reacts properly
when setting it back to both 200% and 100%.
marco-ThinkPad-X1-Carbon-7th ~
13:22:00
❯ apt-ca
Marking this verified again, as it was verified as fixed in version
3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in
.2 [3] do not affect this behavior, we can safely consider it already
verified.
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/comments/30
Marking this verified again, as it was verified as fixed in version
3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in
.2 [3] do not affect this behavior, we can safely consider it already
verified.
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/16
Confirm the test case works correctly here:
❯ apt-cache policy libmutter-6-0
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://it.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Package
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1890427
Title:
package libp11-kit-gnome-keyring (not installed) failed to
install/upgra
Public bug reported:
bug while installing wine
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libp11-kit-gnome-keyring (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Thank you for your bug report. Could you add your 'journalctl -b 0'
after the system start? When the battery gets empty the system does try
to suspend or hibernate depending of your configuration so the next boot
is not a standard one but a resume which could explain you don't get
prompted to log i
It's reproducible in a VM. There is no related message in the journal.
** Package changed: ubuntu => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribe
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
--
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/1888480
Title:
problem in menu graphic
To manage notifications abo
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1886162
Title:
Gnome-Settings-Mouse and scr
I had the same issue with emacs-nox, but I have installed it on Windows
10 inside of WSL2 with Ubuntu 18.04.
I was able to workaround the issue with:
gpg --homedir ~/.emacs.d/elpa/gnupg --keyserver hkps://keyserver.ubuntu.com:443
--receive-keys 066DAFCB81E42C40
After successfully importing the k
You have been subscribed to a public bug:
[Summary]
After entering the OEM installation mode and then clicking the "Power off"
option, the system cannot be powered off.
[Steps to reproduce]
1. Plug the USB key which has the 20.04.01 build
2. Power on the system
3. Select USB drive to launch the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: emacs25 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to emacs25 in Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
I have a Toshiba radius 11 laptop which has a 4 k native screen. I have
connected an Asus PB287Q 28" external monitor (https://www.asus.com/us
/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays
the full 4K resolution when running under windows10 but will onl
I found a work-around: disabling animations in GNOME Tweaks solves the
issue and the whole Top Bar (not a ghost of it) and the Dock are visible
for a very short time until the window becomes fullscreen.
I suggest to include an option to disable these animations when
fullscreen windows are present
it's fixed in upstream git now
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Committed
--
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/1718135
Title:
nautilus cra
I think this bug might have already been fixed before Ubuntu 20.04 was
released. So there's another reason to upgrade :)
--
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/1732245
Title:
Thanks for the quick response!
Another detail I want to add is that it only happens after invoking the
switcher. I can control volume or screen brightness all good without any
problems but as soon as I switch windows and go back to my game the top
bar keeps appearing whenever the volume or screen
This bug is open again now so we don't need another report. 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/1732245
Title:
Fullscreen game windows vertically offset after ret
Hey, Daniel! You sent me here from #1890281
#1725649 is said to be fixed but the bug is still present on Ubuntu
18.04.4 running X. I've recently upgraded to Bionic and noticed this bug
immediately as I often play games.
Shall I file a new bug report?
Thanks in advance.
--
You received this bug
55 matches
Mail list logo
