[Bug 1873638] Re: Weird close button in settings
dpkg-query -W gnome-control-center output: gnome-control-center 1:3.36.1-1ubuntu5 -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
24.38% in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
The actual proportions of Ubuntu users with Nvidia are: 21.94% in Ubuntu 18.04 24.10% in Ubuntu 19.10 And even fewer will be using automatic login. So to say that most users have Nvidia is false. And to imply that even most Nvidia users can't login is false. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Daniel Van Vugt. I appreciate your feedback, and I do very much appreciate it, However I think it is worth a try. I think it is more of Nvidia screwing with us rather than we creating problems for ourselves, It is like a chicken and and egg situation, You enable nvidia- drm.modeset=1 and then you have flicker free boot and potential to suffer from other bugs (Most of them are unconfirmed for the want of testing). Or you can not do anything and suffer this bug. then go and remove splash and from kernel parameters and go on with your life, However in either Case Nvidia needs special treatment from someone, because there is still more than 75 % Linux users using Nvidia, and would expect Flicker Free boot to work or atleast be able to login after installing the nvidia drivers. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867610] Re: snap-store cannot install local deb packages
Still not working for me. $snap info snap-store snap-id: gjf3IPXoRiipCu9K0kVu52f0H56fIksg tracking: latest/stable/ubuntu-20.04 refresh-date: 3 days ago, at 22:12 CEST channels: latest/stable:20191114.a9948d5 2019-11-14 (209) 44MB - latest/candidate: 20191126.6a93891 2019-11-26 (214) 45MB - latest/beta: 20200416.9be6785 2020-04-16 (399) 51MB - latest/edge: 20200414.ac9047f 2020-04-14 (375) 50MB - installed: 20200415.e028804(394) 51MB - ** Attachment added: "Screenshot from 2020-04-20 07-43-36.png" https://bugs.launchpad.net/snap-store/+bug/1867610/+attachment/5357000/+files/Screenshot%20from%202020-04-20%2007-43-36.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1867610 Title: snap-store cannot install local deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1867610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873725] [NEW] Folder under applications menu doesn't show text below last line of icons.
Public bug reported: Under the applications menu the "Utilities" folder does not show the last line of text below the icons. If you launch one of the applications on the last line ie terminal then it will reveal the text below the icon. Description:Ubuntu 20.04 LTS Release:20.04 nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 22:46:39 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "photo_2020-04-19_22-39-08.jpg" https://bugs.launchpad.net/bugs/1873725/+attachment/5356975/+files/photo_2020-04-19_22-39-08.jpg -- 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/1873725 Title: Folder under applications menu doesn't show text below last line of icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
There's a surprising number of clipboard fixes already landed upstream and waiting to be released in mutter 3.36.2 -- we should probably wait and see if they help. Most of them don't have associated bug reports :/ Also, in case you haven't already please try both 'Ubuntu' and 'Ubuntu on Wayland'. In case one works better than the other. It looks like some upstream fixes are specific to one or the other. -- 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/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
*** This bug is a duplicate of bug 1872527 *** https://bugs.launchpad.net/bugs/1872527 Actually this sounds related to bug 1872527. Maybe we should just use that for now. ** This bug has been marked a duplicate of bug 1872527 Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
"screens go black" reminds me of bug 1873403 which might be somehow related. ** Summary changed: - cannot change main monitor after setting scaling for monitors w/nvidia drivers + [nvidia] cannot change main monitor after setting scaling for monitors -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Can you please look in Settings > Screen Display and tell us if 'Fractional Scaling' is enabled? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
Now we are getting somewhere. X windows system implicated. Though the 2d video shows how fast the shortcut boot is, I thought I should get a firm number so I did the shortcut boot and logged in to get output of 'systemd-analyze critical- chain' and I got the following very interesting responses, shell dialogue copied below. The same processes (I would assume) are hanging for 1m44s, but the shortcut somehow allows the user to log in while waiting for them to finish (as well as solving the other problems of clipboard and screen size, which seem to go with the more primitive login screen). Whether those processes should take 1m44s or not, I don't know, maybe it is normal, but the user should be able to log in before they are complete, as I can do with shortcut boot. If those processes are taking inordinately long, then shortcut boot gives opportunity to log in and catch them as they struggle, as seen below. The time I had to wait to get the critical-chain result was about as long as I had to wait to log in at all, under stock 19.10 without shortcut-boot procedure: wift@stock19:~$ sudo -i [sudo] password for swift: root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemctl list-jobs JOB UNIT TYPE STATE 48 setvtrgb.service start waiting 137 system-getty.slice start waiting 1 graphical.target start waiting 102 systemd-update-utmp-runlevel.service start waiting 83 plymouth-quit-wait.service start running 2 multi-user.targetstart waiting 6 jobs listed. root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# systemd-analyze critical-chain Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0). Please try again later. Hint: Use 'systemctl list-jobs' to see active jobs root@stock19:~# date Sun 19 Apr 2020 10:50:27 PM EDT root@stock19:~# systemd-analyze critical-chain The time when unit became active or started is printed after the "@" character. The time the unit took to start is printed after the "+" character. graphical.target @1min 44.881s └─multi-user.target @1min 44.881s └─xrdp.service @1.496s +1.036s └─xrdp-sesman.service @1.474s +20ms └─network.target @1.470s └─NetworkManager.service @1.381s +88ms └─dbus.service @1.379s └─basic.target @1.375s └─sockets.target @1.375s └─snapd.socket @1.373s +1ms └─sysinit.target @1.372s └─systemd-timesyncd.service @1.175s +196ms └─systemd-tmpfiles-setup.service @1.160s +10ms └─local-fs.target @1.158s └─home-swift-shared\x2ddrives.mount @11.731s └─local-fs-pre.target @177ms └─lvm2-monitor.service @116ms +61ms └─dm-event.socket @115ms └─system.slice @110ms └─-.slice @110ms root@stock19:~# -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu. Yes, I am able to select the “restart” button with
the keyboard. But then the shortcut doesn’t work; what triggers the
shortcut is powering off the VM.
https://chaetura.net/ms-vid2-bug-1848534.webm
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3.
Reasonable conclusion is that all three problems have the same cause,
which somehow the shortcut boot avoids:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas
stock 19.10 came in one size only and user has no opportunity to select;
goes hand in hand with the different login screen, as you can see in
video.
3) after login, cut-and-paste from guest to host is possible. Not
functional with stock 19.10.
I see that graphical artifact at some point during boot of any Ubuntu VM
in Hyper-V. You can see it in the video too. In 19.10 it comes while the
Spectre mitigation message is on the screen in console, at a point where
console changes its rendering/mode somehow and the message reappears in
a slightly different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10
it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the shortcut boot sequence. On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot now (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less than 2s to "graphical.target", compared with 104s for
19.10.
swift@Riflebird:~$ sudo -i
[sudo] password for swift:
root@Riflebird:~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @1.836s
└─multi-user.target @1.836s
└─kerneloops.service @1.829s +6ms
└─network-online.target @1.827s
└─NetworkManager-wait-online.service @663ms +1.163s
└─NetworkManager.service @566ms +96ms
└─dbus.service @538ms
└─basic.target @5
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Tags added: leak ** 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/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Thanks for the clarification. Can you please report that second "real" issue as a new bug by running: ubuntu-bug linux ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
A stray click sent my previous message before I had finished editing it, and I see no way to edit my post. I will post fully complete/edited version momentarily. I hope an admin will delete this message and my prior message to avoid cruft in this thread. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873625] Re: Mouse moves at the bottom right of the screen at log-in
This is a "feature" but efforts are underway upstream to change it: https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #651 https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/651 Importance: Unknown Status: Unknown ** Summary changed: - Mouse moves at the bottom right of the screen at log-in + Center the mouse cursor at startup ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1873625 Title: Center the mouse cursor at startup To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873625/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described earlier, but which I have simplified to simply pulling
the plug with "power off" from Hyper-V at the grub menu, do not close
the Connection window, restart, and 19.10 will boot fast. Note that
"system setup" (I previously mistakenly wrote "system startup") doesn't
appear in the grub menu of stock 19.10; it appears only after updating
packages in Ubuntu.
Furthermore, the shortcut boot of 19.10 solves *THREE* significant
problems with stock 19.10 that are not problems with stock 18.04.3:
1) avoids the long delay in startup
2) allows user to select any screen size for the Connection (whereas stock
19.10 came in one size only
and user has no opportunity to select; goes hand in hand with the
different login screen, as you
I see that graphical artifact at some point during boot of any Ubuntu VM in
Hyper-V. You can see it in the video too. In 19.10 it comes while the Spectre
mitigation message is on the screen in console, at a point where console
changes its rendering/mode somehow and the message reappears in a slightly
different font.
I forgot to show /proc/cmdline and "uname -a" in the video but for 19.10 it is:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=PARTUUID=[blahblah] ro quiet
splash
Linux stock19 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
and in 18.04.3 it is
BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=LABEL=desktop-rootfs ro
quiet splash vt.handoff=1
Linux stock18 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Note that I installed my 19.10 via Hyper-V Manager's "quick-create"
rather than from an .iso downloaded separately. Same kernel version, but
mine is an earlier packaging number, and who knows what else may be
different about the install image. The manager says the image was
updated 17 October 2019. The Manager downloads a zip file from partner-
images.canonical.com via https so I cannot snoop the URL looking at the
packets. I have a copy of the .vhdx which is insie the zip file, and I'm
messing around with trying to mount it in another VM but I haven't
solved that yet.
My Windows 10 Pro x64 build (today) is Win10: Version 1909 (OS Build
18363.778). No further windows updates are available, and I don't
understand Windows version numbers, so I can't explain the discrepancy
from yours.
The startup delay persists after updating the stock install of 19.10
(using aptitude; all available updates accepted but the grub packages
held back till I learn how to do them; they broke my last install).
I noticed while making the video that during the long startup delay, the
process is using GPU at 5% -- significant amount of usage (documented in
video). Therefore I've included my GPU information at bottom below.
I boot stock quick-create 19.10. I change the name of the VM only
("Stock19"). Default ethernet adapter. Note that the first boot is
immediate; the only one that will ever be that fast, unless I go through
the restart sequence described last time. (On that subject, I don't get
the "system setup" grub option in the stock 19.10, only after updates.
You probably figured out I mistakenly wrote "system startup" earlier
instead of "system setup" as well. And yes, keyboard can select
"restart" but in this case, the shortcut does *NOT* work. Only pulling
the plug on the VM from Hyper-V ) On first boot, I go through Ubuntu
configuration screens minimally. Post-install runs. No further updates,
just reboot noq (because critical-chain timings are much longer the
first boot than all subsequent boots). Login, run terminal, sudo-i, then
systemd-analyze critical-chain:
first line is: graphical.target @1min 44.651s
This is typical of all subsequent boots.
I'm not copying the full output all because cut-and-paste text from
guest to host is broken for me in 19.10. It is not broken in an 18.04.3
guest ("updated 19 August 2019" in Hyper-V Manager).
Also in 19.10 I never get the choice of a screen size for the guest when
connecting; it is always the same size. I get the choice in 18.04 and
can choose any size including full-screen, and it just works.
I understand that these other problems with 19.10 guest may be off-
topic; I am mentioning them here in case they correlate to the current
topic. In summary, four significant problems with 19.10 that do not
exist in 18.04, both out of the box quick-create, using same host: 1)
the long delay at startup. 2) no cut-and-paste from guest to host. 3) no
capability to resize Hyper-V Connection screen. 4) requires research to
get past a grub update.
Here for comparison is the critical-chain for 18.04, which I can cut-
and-paste. Less th
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Using GNOME in the guest isn't removing it from the equation, it's only changing the equation. Actually this could equally be a problem with virt-manager. What happens if both the host and guest are not GNOME? -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
And yes nvidia-drm.modeset=1 will give you back the missing boot animation, but that discussion should stay in bug 1868240. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note that we don't recommend use of nvidia-drm.modeset=1 for most users because it still results in some bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset And I'm not sure that's even a complete list. So you should be aware of what you're getting into. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841145] Re: Impossible de switch user from lock screen on GDM3 18.04
Christian, I'm not sure that's exactly the same as this bug since this bug is about "flicker" and failure to log in, while you refer to "artifacts". It's probably best if you report a new bug for that by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1841145 Title: Impossible de switch user from lock screen on GDM3 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Sorry - not a total noob here, but enough to embarrass myself... I had to boot with "nomodeset" in order to get my machine to boot. That caused the situation I described here. When I blacklisted the nouveau video driver, I got my functionality back. For those who know better how to fix these things - the real problem is that the nouveau driver didn't work on my XPS 13 9365, causing it to hang while trying to boot. -- 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/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
I have a feeling you are right that it may not be gnome-control-center doing this as setting the default value of show-banners in /usr/share/glib2.0/schemas to false ends up being ignored at login. It is unclear to me what the desired behaviour is from those discussions, but my expectation is that an exposed user setting will stay set until I unset it. -- 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/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
** 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/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873700] [NEW] Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
You have been subscribed to a public bug: I lost ability to rotate the display upon upgrade to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 15:04:26 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands https://bugs.launchpad.net/bugs/1873700 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
There's a patch in #71. Unfortunately, I don't know how to properly submit the patch. -- 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/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
Thanks for your report! I can confirm it. When "Do Not Disturb" is enabled, this dconf value is set: $ gsettings get org.gnome.desktop.notifications show-banners false But something always sets it to "true" at login. (That something is reasonably not gnome-control-center, btw, since it's not launched automatically at login.) The feature was preceded by long discussions: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/56 https://gitlab.gnome.org/GNOME/gnome-shell/issues/239 I have a feeling that the behavior is intentional, even if I didn't find any explicit statement in that direction. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #56 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/56 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #239 https://gitlab.gnome.org/GNOME/gnome-shell/issues/239 ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
Also loses focus on Microsoft To-Do app. Hope that is enough to change the status from Undecided to actual real 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/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 130213] Re: rhythmbox doesn't play the next song after first song finished
I have had this (or a similar) problem for the last month or so, Rhythmbox is stuck in shuffle mode. I'm using Ubuntu 16:04, which I've had installed for close to four years now, but this problem suddenly popped up very recently. I've uninstalled and reinstalled, but no luck. Doesn't matter if I try to activate repeat before starting to play the first song in a list or before selecting all or while I'm playing a song, it is completely stuck in shuffle mode. Also, the sign that is supposed to say it's in repeat or shuffle mode is very faint, just a very narrow band around that button. Wouldn't it be better to make this clearer? Im attaching the output to stderr when I run rhythmbox --debug. ** Attachment added: "stderr.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+attachment/5356888/+files/stderr.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/130213 Title: rhythmbox doesn't play the next song after first song finished To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 130213] Re: rhythmbox doesn't play the next song after first song finished
I have had this (or a similar) problem for the last month or so, Rhythmbox is stuck in shuffle mode. I'm using Ubuntu 16:04, which I've had installed for close to four years now, but this problem suddenly popped up very recently. I've uninstalled and reinstalled, but no luck. Doesn't matter if I try to activate repeat before starting to play the first song in a list or before selecting all or while I'm playing a song, it is completely stuck in shuffle mode. Also, the sign that is supposed to say it's in repeat or shuffle mode is very faint, just a very narrow band around that button. Wouldn't it be better to make this clearer? Im attaching the output to stderr when I run rhythmbox --debug. ** Attachment added: "stderr.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+attachment/5356887/+files/stderr.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/130213 Title: rhythmbox doesn't play the next song after first song finished To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Rajat Pandita: awesome, thanks for sharing! I came here to report that I too was experiencing this bug: GTX 1060, up-to-date Focal Fossa beta, NVidia 440 driver series, 5.4.0-24 kernel. Couldn't log in. Removing `splash` from grub's kernel parameters solved the issue, but adding `nvidia-drm.modeset=1` is a much better solution since it leaves the splash screen unaffected (so you get a nice-looking boot). Besides, I remember from using KDE on Archlinux that `nvidia-drm.modeset=1` is required to get decent performance from NVidia drivers on KDE (though on Ubuntu I'm using Gnome). The driver install script should really edit and update grub configuration accordingly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868872] Re: Nautilus Cant open files in shared folders
Great, thanks for confrming, closing the bug! ** Changed in: nautilus (Ubuntu) Status: Incomplete => Fix Released -- 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/1868872 Title: Nautilus Cant open files in shared folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873694] [NEW] fatal crash while editing text
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)
using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.62.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 7081 - Thread 7081 #
[New LWP 7082]
[New LWP 7083]
[New LWP 7084]
[New LWP 7085]
[New LWP 7086]
[New LWP 7100]
[New LWP 7116]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffc4dec6e90, fd=14) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f699d42fe00 (LWP 7081) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffc4dec6e90, fd=14) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f699ccd2700 (LWP 7082) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f699b188700 (LWP 7083) "gmain" 0x7f699e3d1c2f in
__GI___poll (fds=0x557cb6577560, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f699a5a8700 (LWP 7084) "gdbus" 0x7f699e3d1c2f in
__GI___poll (fds=0x557cb658e6e0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7f6984a02700 (LWP 7085) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f6984201700 (LWP 7086) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f6982f09700 (LWP 7100) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f6983a00700 (LWP 7116) "paint" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7f6983a00700 (LWP 7116)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f699e6c4d83 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x557cb4050cdd in ?? ()
No symbol table info available.
#3 0x7f699e6a2181 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f699e4b8669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140091156596480,
-2492501370317008292, 140721615826510, 140721615826511, 140721615826656,
140091156592896, 2574893548899177052, 2574906297765237340}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#5 0x7f699e3de323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 7 (Thread 0x7f6982f09700 (LWP 7100)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f699e6c4d83 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f699eb82799 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f699e6a2181 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f699e4b8669 in start_thread (arg=) at
[Bug 1873692] [NEW] Do Not Disturb setting does not persist across login sessions
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] Re: Weird close button in settings
On 2020-04-19 19:28, Dragosh wrote: > From my point on view the version of gnome-control-center can be > determined from the screenshot, That shows the upstream version of some of the many GNOME packages (don't know which one). Besides, there are several non-trivial gnome- control-center patches in Ubuntu, so what does this command output: dpkg-query -W gnome-control-center With desktop environment I meant to ask if you possibly are on one of the Ubuntu flavors. I think Ubuntu Budgie uses gnome-control-center by default. Yes, knowing how to reproduce is always useful, of course. (But I still can't reproduce it.) You seem to be using some other theme but the default Yaru one. Wondering if it may be a theme issue. -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841145] Re: Impossible de switch user from lock screen on GDM3 18.04
Hey. I ran into the same problem but with Ubuntu 20.04 (arm64) on the raspberry pi 4. Disabling Wayland fixed it, since then I don't see any artifacts when starting gnome. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841145/+attachment/5356833/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1841145 Title: Impossible de switch user from lock screen on GDM3 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] Re: Weird close button in settings
OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. ** Description changed: Unexpected button location on settings. Check image as screenshot attachment . + + OS: Ubuntu 20.04 + OS Type: 64-bit + Gnome: 3.36.1 + Windows System: X11 / Xorg + + May the question show be how to reproduce? To switch button on the left + side. -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] Re: Weird close button in settings
>From my point on view the version of gnome-control-center can be determined from the screenshot, the gnome-control-center 3.36.1 as the version of gnome / the screenshot from is settings and we OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873675] [NEW] GIMP crashed just after saving
Public bug reported:
I have not done anything in particular. Just saved a new project with
File → Save As… In several seconds, GIMP crashed. I'm not sure that the
saving is relevant.
I'm using Ubuntu 19.10.
Auto-generated report follows.
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx
--enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1)
using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.62.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 3298 - Thread 3298 #
[New LWP 3301]
[New LWP 3302]
[New LWP 3303]
[New LWP 3304]
[New LWP 3305]
[New LWP 3322]
[New LWP 6455]
[New LWP 6902]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffe80d05690, fd=14) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7fcb70d76e00 (LWP 3298) "gimp-2.10" __libc_read
(nbytes=256, buf=0x7ffe80d05690, fd=14) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7fcb7061f700 (LWP 3301) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7fcb6e5ea700 (LWP 3302) "gmain" 0x7fcb71d18c2f in
__GI___poll (fds=0x55b193fe0d80, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7fcb6dde9700 (LWP 3303) "gdbus" 0x7fcb71d18c2f in
__GI___poll (fds=0x55b193ff5b20, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7fcb57fff700 (LWP 3304) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7fcb577fe700 (LWP 3305) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7fcb56423700 (LWP 3322) "swap writer"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7fcb56ffd700 (LWP 6455) "paint" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7fcb457fc700 (LWP 6902) "pool-gimp-2.10" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 9 (Thread 0x7fcb457fc700 (LWP 6902)):
#0 0x7fcb71d1e94d in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fcb7200bea6 in g_cond_wait_until () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fcb71f903e1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x7fcb71f90a06 in g_async_queue_timeout_pop () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fcb71fe9969 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x7fcb71fe9181 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x7fcb71dff669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140511021090560,
-2552484345361049313, 140731059548782, 140731059548783, 140731059548928,
140511021086976, 2523506718432975135, 2523461361759967519}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#7 0x7fcb71d25323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 8 (Thread 0x7fcb56ffd700 (LWP 6455)):
#0 0x7fcb71d1e94d in syscal
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Did a Fresh Install today, and Selected the option to automatically install proprietary drivers, Something changed and my Installation Failed, I got a message saying that there was already a bug for that, I followed along and updated my situation in that bug report, because why not, It is just a 2 Minute Job. So this time around I changed the kernel parameters before installing Nvidia Drivers using the ubuntu-drivers autoinstall command. I edited by /etc/default/grub and I added nvidia-drm.modeset=1, Did not remove splash or any other parameters. I then ran sudo ubuntu-drivers autoinstall and waited for that to finish, Once done, I ran sudo update-grub. Then rebooted. This way I now have the flicker free boot/Animation and I can get into the desktop without any issues, GDM autologin works absolutely fine. I rebooted again just to be sure, and things stayed good. I wanted to update here so others can benefit while the bug is addressed. This is a working solution for me. I have a GTX 1070 CPU. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, > Since your setup only uses gnome-shell in the host and not the guest it Host is KDE Plasma, guest is GNOME => I have problems with clipboard when I close virt-manager or shutdown the guest => no problems So if I remove GNOME from the equation, then it's OK. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792085] Re: Regression: MTP not working/very slow
I have the same Problem on Ubuntu 19.10 with a Samsung Galaxy S10 (SM- G973F) Kernel: 5.3.0-46-generic x86_64 Architecture: arm64 Desktop: Gnome 3.34.2 gvfs: amd64 1.42.1-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] Re: Weird close button in settings
That's weird. For me the close button is in the top right corner as expected. Which version of gnome-control-center are you using? Which desktop environment? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Sebastien, I can confirm that the updated package fixes the problem. Thanks for your work! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
The GNOME issue is completely separate from the problem of "triggering layout change on press", as GNOME does not use the kxb behavior at all - it actually disables any options set using setxkbmap - instead it listens to keyboard events and implements its own custom behavior that mimics Mac OS. Note that with the current release (19.10, but also tested 20.04) on Kubuntu with xserver 1.20 that *does not* include the patch from freedesktop.org bug 865, layout switching works on release - as requested. I'm not sure what introduced this behavior and whether it is in X.org or in KDE. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
I am running ubuntu 19.10 with recent gnome 3 and did not find any working solution to switch layout on Ctrl +Shift shortcuts key release. Eventualy i wrote a dirty workoround to fit my needs. https://gitlab.com/softkot/gnome3_xinput_layout_switch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] Re: Weird close button in settings
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: focal -- 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/1873638 Title: Weird close button in settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873638] [NEW] Weird close button in settings
You have been subscribed to a public bug: Unexpected button location on settings. Check image as screenshot attachment . ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: settings -- Weird close button in settings https://bugs.launchpad.net/bugs/1873638 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873038] Re: Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)
This bug was fixed in the package gtk+3.0 - 3.24.18-1ubuntu1 --- gtk+3.0 (3.24.18-1ubuntu1) focal; urgency=medium * Update to the current stable version (based on Debian) (lp: #1873038) -- Sebastien Bacher Thu, 16 Apr 2020 11:23:10 +0200 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1873038 Title: Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1873038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871913] Re: super key does not work with secondary keyboard layout
Obviously this is an upstream bug reported to gnome / mutter developers a while ago. As usual, they responded by being arrogant and refusing to acknowledge the problem. We will have to wait for them to open their eyes. -- 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/1871913 Title: super key does not work with secondary keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 689139] Re: Shotwell doesn't import across symbolic link
Any news? I am on Ubuntu 20.04 with Shotwell 0.30.8-0ubuntu2 and I am unable to add a folder that is a symlink to another folder.. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/689139 Title: Shotwell doesn't import across symbolic link To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/689139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873625] [NEW] Mouse moves at the bottom right of the screen at log-in
Public bug reported: When I open a session, the mouse cursor moves at the bottom-right of the screen, at a fixed position. The coordinates are about (x:1730, y:970) on a 1920x1080 screen. When I close the session, the mouse goes again to this position. I am not sure if the issue really comes from mutter, or gdm, or other component. This behavior is specially annoying because your first action after log- in will probably consist in launching an application by clicking its icon at opposite position of the screen, in the top-left part of the launch bar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 09:03:01 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873625 Title: Mouse moves at the bottom right of the screen at log-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873625/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
