[Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
This is a regression for our vast majority of users using the normal ubuntu product and quite visible one, I wouldn't put it as low. ** Changed in: gnome-shell (Ubuntu) Importance: Low => High ** Changed in: mutter (Ubuntu) Importance: Low => High -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
A black frame can also mean a zero FB ID, IIRC... Can you tell if the backlight is going off? -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Regardless, please also create an upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
It looks like modesetting, or at least a destructive probe of the attached displays. There's nothing KMS related in dmesg corresponding to the blanking, so I don't think it's an invalid FB (I'd expect i915 to spit something in dmesg in that case) -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Journal output attached ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285717/+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.launchpad.net/bugs/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
dmesg output attached ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+attachment/5285718/+files/dmesg.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.launchpad.net/bugs/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => Low -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
or * An invalid framebuffer being accidentally flipped. -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] Re: Volume up/down repeat keys don't work on Xorg
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842009] Re: [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Can you tell if the "blanking" is either: * The output entering sleep mode; or * A black frame being accidentally flipped. I guess checking if the backlight is still on would answer that. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: wayland ** Tags added: hybrid -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
Let's start by checking for crashes, which can confuse and break the console switching. Please try these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- 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/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
Please do it again and instead of saving the apport just copy the link and open it on another machine. You can then complete the new bug creation in the browser of that other machine. -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Please try: 1. Open a Terminal window and run: journalctl -f 2. Right click on the desktop and reproduce this bug. 3. Do you see any new messages in the Terminal window? -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841673] Re: GNOME Shell crashed
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => 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/1841673 Title: GNOME Shell crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831369] Re: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch
Thanks. That doesn't seem to show any single recurring problem though. So it looks like log file flushing is not the explanation for this bug. I wonder if disk performance is a factor. Can you please run: lsblk and sudo hdparm -I /dev/sda and send the output? -- 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/1831369 Title: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1842009] [NEW] [Wayland] Screen blanks for a second whenever discrete GPU is powered up
Public bug reported: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. Because the GPU powers down quite aggressively (I think it's about 5sec without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: On this Kaby Lake G laptop, GNOME Shell blanks the screen for a second each time the AMD GPU is powered up. Triggers for powering up include: launching something which loads GL such as Steam or glxinfo, loading the Display configuration page, and so on. This behaviour does *not* occur with GNOME Shell under X, so it's probably something to do with mutter's KMS interactions. + + Because the GPU powers down quite aggressively (I think it's about 5sec + without activity) this can be quite annoying :) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic 5.1.2 Uname: Linux 5.1.0+bcachefs.git20190828.bc3a6a71-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 30 09:48:25 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-29 (0 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1842009 Title: [Wayland] Screen blanks for a second whenever discrete GPU is powered up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842009/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
When running 'apport-cli --hanging $(pidof gnome-shell)' in a ssh shell, it wants to spawn a browser to login to launchpad.net; since it did not, I saved the apport and linked it here. After I ran the killall command and ran the ubuntu-bug command it did not show an ID to link here. ** Attachment added: "apport.gnome-shell.oeeef49r.apport" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+attachment/5285702/+files/apport.gnome-shell.oeeef49r.apport -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841679] Re: [nvidia] Login screen never wakes after sleeping and there is no way to recover
This is not a dual GPU system, only the Nvidia GPU is usable. -- 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/1841679 Title: [nvidia] Login screen never wakes after sleeping and there is no way to recover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1841673] Re: GNOME Shell crashed
"No errors have been reported from this system" чт, 29 авг. 2019 г. в 04:50, Daniel van Vugt : > Please follow the steps in comment #2, or choose one of the above bugs > you would like this to be a duplicate of. > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1841673 > > Title: > GNOME Shell crashed > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Photo of the problem: https://photos.app.goo.gl/D8PfrYnG2dt4B6N97 > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: gnome-shell 3.33.91-1ubuntu1 > ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 > Uname: Linux 5.2.0-13-generic x86_64 > ApportVersion: 2.20.11-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 28 00:04:20 2019 > DisplayManager: gdm3 > InstallationDate: Installed on 2019-08-25 (2 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841673/+subscriptions > -- 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/1841673 Title: GNOME Shell crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841673] Re: GNOME Shell crashed
After a while I have been not noticed the same problem, so I believe it had fixed. So I think we can change the status from "Incomplete" to "Fix released". ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1841673 Title: GNOME Shell crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1831369] Re: Gnome Shell pauses and stutters when under heavy load
Please, take the result. P.S. I will try to descibe the different problems in separate apports. Sorry for my mistakes. It's a less of my experience. чт, 29 авг. 2019 г. в 04:45, Daniel van Vugt : > Please be careful to only discuss one problem per bug report. If you're > experiencing multiple problems then please open separate bugs for them. > > Continuing with this bug... > > I suspect the problem here is that disk IO is directly affecting > animations. They shouldn't normally be related to each other, but one > way that can happen is if gnome-shell is blocked in writing a log > message. It can become blocked if there are regular log messages being > written, and then every 5 seconds the kernel will block in order to > flush to disk. > > Please run this command in a Terminal window: > > journalctl -f > > Now reproduce the problem again and please tell us if the Terminal > window shows NEW log messages while the freeze/stutter is happening. > > ** Changed in: gnome-shell (Ubuntu) >Status: Confirmed => Incomplete > > ** Summary changed: > > - Gnome Shell pauses and stutters when under heavy load > + Gnome Shell pauses and stutters while waiting (several seconds) for > programs to launch > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831369 > > Title: > Gnome Shell pauses and stutters while waiting (several seconds) for > programs to launch > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > My laptop: HP 250 G6, Intel Celeron N3350, integrated video card, 4 GB > RAM, Ubuntu 19.04 > Details in my video: https://photos.app.goo.gl/ERUaSS6Qc8jFhHnn9 > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-shell 3.32.0+git20190410-1ubuntu1 > ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 > Uname: Linux 5.0.0-15-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 2 14:32:17 2019 > DisplayManager: gdm3 > GsettingsChanges: >b'org.gnome.shell' b'app-picker-view' b'uint32 1' >b'org.gnome.shell' b'command-history' redacted by apport >b'org.gnome.shell' b'favorite-apps' redacted by apport >b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano']" >b'org.gnome.desktop.interface' b'gtk-im-module' > b"'gtk-im-context-simple'" > InstallationDate: Installed on 2019-05-31 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >LANGUAGE=ru_UA:ru >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=ru_UA.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+subscriptions > ** Attachment added: "bug.txt" https://bugs.launchpad.net/bugs/1831369/+attachment/5285672/+files/bug.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.launchpad.net/bugs/1831369 Title: Gnome Shell pauses and stutters while waiting (several seconds) for programs to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
It's not quite the same as bug 1724977. This doesn't happen when moving the cursor live, but the second copy "appears" after waking from screen lock. My guess is that the lock screen doesn't use the same video memory config as the desktop, but somehow they "overlap" and the cursor gets left over as you log back in from the lock screen. * The fact that the fake cursor image is large makes me think that it isn't using the same scaling * The fact that the fake cursor image is rotated (as if the screen is in normal landscape) makes me think that the lock screen is unaware of the desktop screen rotation. Both of these points may affect the video memory layout which will therefore be different between the desktop and the lock screen... Currently away from the machine, but I will do the apport-collect next week. -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841663] Re: Gnome freezes when right clicking an icon on desktop on wayland
Ran a terminal with dmesg -w running. Generated a 2gb file on my desktop, copied and pasted into home. After "finished copying" notification I right clicked "move to trash", and lockup. Didn't see anything in the console output. -- 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/1841663 Title: Gnome freezes when right clicking an icon on desktop on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841663/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834386] Re: Ebooks thumbnails fail in Nemo over SMB
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1834386 Title: Ebooks thumbnails fail in Nemo over SMB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1834386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825626] Re: nvLock: client timed out, taking the lock
Did anyone try setting __GL_MaxFramesAllowed=1 as discussed in https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 ? It helped me to get rid of the lockups on manjaro (didn't try on ubuntu though) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1202 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1202 -- 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/1825626 Title: nvLock: client timed out, taking the lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825626] Re: nvLock: client timed out, taking the lock
A discussion at https://forum.manjaro.org/t/desktop-gnome-frequently- get-frozen-few-seconds-and-works-again/81603/29 for manjaro seems to nail down: * It looks related to mutter (a gnome desktop component), since some guys report that the freeze disappears when updating mutter. * It does not seem to appear under under non-gnome desktop. ** Also affects: gnome-desktop Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841897] Re: Cursor missing from slider
The first one (global volume) is fixed by Robert already, but the second is not, I just reported that upstream. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #652 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/652 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/652 Importance: Unknown Status: Unknown -- 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/1841897 Title: Cursor missing from slider To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1841897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841929] [NEW] Volume up/down repeat keys don't work on Xorg
Public bug reported: GNOME Shell & mutter on 3.33.91 When pressing volume up or down on Xorg and keeping it pressed, only the first key event is sent, so the volume only goes up or down once, and doesn't scale up/down as long as you keep the button pressed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 13:45:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (461 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (232 days ago) ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1554 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1554 Importance: Unknown Status: Unknown ** Tags added: rls-ee-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/1841929 Title: Volume up/down repeat keys don't work on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841897] Re: Cursor missing from slider
Thank you for your bug report, could you report it upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues (confirmed and it does the same with Adwaita so not a theme issue) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** 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/1841897 Title: Cursor missing from slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1841897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841696] Re: Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries
It's because it recommends rygel now which recommends gst-libav, that goes lowered to a suggest now https://launchpad.net/ubuntu/+source/rygel/0.38.1-2ubuntu2 ** Package changed: gnome-control-center (Ubuntu) => rygel (Ubuntu) ** Changed in: rygel (Ubuntu) Status: New => Fix Released -- 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/1841696 Title: Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/1841696/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841926] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1841926/+attachment/5285611/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285613/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285618/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285619/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285620/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285622/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1841926/+attachment/5285623/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1841926 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841926/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutt
** Tags added: rls-ee-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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841794/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
Network connection does not die. (It appeared to first time but I think that's just my ongoing random - and irrelevant here - avahi issues on this machine.) But gnome-shell is *not* running after triggering the bug, so sudo killall on it just produces "gnome-shell: no process found". So that was the end of following the instructions above. :-) (Also this time round it did fail on the *first* logout too, so the fact of it not having done so the first couple of times may just have been a fluke. There are no other processes with gnome in the name running, nor is mutter. gdm3 and "gdm-session-worker [pam/gdm-autologin]" are apparently up. Using systemctl restart gdm3 seemed to work (I see a login screen) but doesn't really (it didn't autologin as expected per config, and attempting to log in just returns me to the login screen). I stopped gmd3 entirely (systemctl stop gdm3, then noticed "gdm-session- worker [pam/gdm-autologin]" was still running, though may have been a new instance as of the gmd3 restart (based on time started), so killed that manually), but then noticed there's a gnome-shell and other processes owned by me now running, but which I didn't get any sight of visually on the system's screen. After a while (while I was typing the above paragraph) they died on their own, and after *that*, a systemctl start gdm3 seems to have worked. As autologin is enabled, i got back into a new desktop session. This may point to it being related to console switching as suggested in the comments of the upstream bug. Stuff *is* happening (eg: gnome-shell *did* quit on logout, and it looks like I *did* login after the first gdm3 restart), but the console doesn't switch properly, so it appears dead. -- 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/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1840675] Re: Expose a button in the Network panel to open nm-connection-editor
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist -- 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/1840675 Title: Expose a button in the Network panel to open nm-connection-editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1840675/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
Strange, these two extensions('sensory-percept...@harlemsquirrel.github.io',
'temperature@xtranophilist', 'gnom...@panacier.gmail.com'
) I've already uninstalled from gnome-tweaks, for a long time.
If they are available and easy to install, I think there is some problem with
gnome shell extensions, it happens to many users that they can't start the
desktop with any extension that doesn't work well (I can fix it because I know
how to fix it, but many users, no).
The bug occurred only on one occasion, but I wanted to report it because I want
to help fix bugs, if there are any.
--
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/1841774
Title:
gnome-shell freezes and continuously logs "JS ERROR: TypeError: null
has no properties" in _addWindowEffect from vfunc_show (both in
closeDialog.js)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841921] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1841921/+attachment/5285596/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285598/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285603/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285604/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285605/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285607/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1841921/+attachment/5285608/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1841921 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
This might be somehow related to bug 1841873. To check that, please log in via ssh and force a crash dump while it is unresponsive: sudo killall -ABRT gnome-shell Then please report that in a new bug using: ubuntu-bug /var/crash/YOURFILE and tell us the new bug ID. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- 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/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841915] [NEW] black screen, unresponsive, after logout from gnome
Public bug reported: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen
** Bug watch added: bugzilla.gnome.org/ #789675 https://bugzilla.gnome.org/show_bug.cgi?id=789675 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #789675 => bugzilla.gnome.org/ #789675 -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841894] Re: Wayland: Image of mouse cursor left on screen after unlock
Sounds like bug 1724977, but we claim to have fixed that(?). also... Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1841894 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: disco ** 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841897] [NEW] Cursor missing from slider
Public bug reported: There is no cursor on the slider in gnome-control-center (cf screenshot) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 09:59:11 2019 InstallationDate: Installed on 2014-07-15 (1870 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2018-03-24 (522 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Attachment added: "2019-08-29_09-58.png" https://bugs.launchpad.net/bugs/1841897/+attachment/5285564/+files/2019-08-29_09-58.png -- 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/1841897 Title: Cursor missing from slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1841897/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841894] [NEW] Wayland: Image of mouse cursor left on screen after unlock
Public bug reported: Gnome 3 desktop Multi-monitor setup with one screen rotated right into portrait mode *Experimental* fractional scaling on Wayland with different scaling on each monitor. Configured using: ~~~ gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" ~~~ After wake from screen lock I often observe an "image" of an enlarged rotated mouse pointer on the second (rotated) monitor which doesn't move and doesn't appear on a screenshot. It overlays all other screen in formation and cannot be erased by moving the mouse over the area. Depending on where the mouse cursor was when sleeping it seems to appear in one of two places, either towards the bottom left or top right. After some time a block around the cursor image gets "corrupted". This behaviour is not observed if logging in to a X11 session Because this doesn't show up on a screenshot I have included a photo, which also shows the monitor setup. Description:Ubuntu 19.04 Release:19.04 mutter: Installed: 3.32.2+git20190711-2ubuntu1~19.04.1 Candidate: 3.32.2+git20190711-2ubuntu1~19.04.1 Version table: *** 3.32.2+git20190711-2ubuntu1~19.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Monitor layout showing fake cursor image" https://bugs.launchpad.net/bugs/1841894/+attachment/5285562/+files/CursorImage.jpg -- 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/1841894 Title: Wayland: Image of mouse cursor left on screen after unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
It doesn't look like https://gitlab.gnome.org/GNOME/mutter/issues/728. It is about the hardware limitation that DELL DOCK - WD19 130W only supports two external Full HD at the same time. However mutter doesn't know the hardware limitation. I guest mutter will try to set up external Ultra HD and external Full HD that is over the hardware limitation of DELL DOCK - WD19 130W so it failed. -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Are you able to supply apport info? apport-collect 1841886 ** Tags added: bionic ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #728 https://gitlab.gnome.org/GNOME/mutter/issues/728 -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
** Also affects: gnome-shell-extension-dashtodock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841886] Re: Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Sounds like this?... https://gitlab.gnome.org/GNOME/mutter/issues/728 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/728 Importance: Unknown Status: Unknown ** No longer affects: mutter -- 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/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841886] [NEW] Join Displays failed when using two external monitor of one Full HD and one Ultra HD
Public bug reported: [Summary] Join Displays failed when using two external monitor of one Full HD and one Ultra HD [Reproduce Steps] 1. Boot into the desktop environment with DELL DOCK - WD19 130W [1]. 2. Connect one Ultra HD (3840x2160) external monitor and one Full HD (1920x1080) external monitor. 3. Press Win+P to switch to Join Displays mode. [Results] Expected: All monitors including the internal monitor can display with Full HD (1920x1080). Actual: The Ultra HD monitor can not display. [Additional Information] 1. Using only Ultra HD (3840x2160) external monitor with internal Full HD (1920x1020) display works fine. 2. Executing the command like `xrandr --output eDP-1 --primary --preferred --output DP-1-1 --preferred --left-of eDP-1 --output DP-1-2 --above eDP-1 --mode 1920x1080 --rate 60` can work. (P.S. DP-1-2 is connected to Ultra HD.) [1] https://www.dellemc.com/resources/en-us/asset/data-sheets/products /electronics-accessories/dell_dock_wd19_130w_spec_sheet.pdf ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/bionic Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1841034 somerville ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841886 Title: Join Displays failed when using two external monitor of one Full HD and one Ultra HD To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1841886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34
Dash to Dock is currently broken as well. This branch https://github.com/3v1n0/dash-to-dock/tree/gnome-3-34 works, but the intelligent autohide brings down the entire gnome shell if enabled. GNOME Pomodoro currently works, but was compiled under 3.32 from the 3.32 branch. The package has not be in the repos since Cuttlefish. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1835706 Title: Extensions don't load in gnome-shell 3.33/3.34 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1835706/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
