[Bug 1862895] [NEW] [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
Public bug reported: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 12 10:02:11 blade apt-get: Libgcrypt warning: missing initialization - please fix the application Feb 12 10:02:12 blade /unattended-upgrade: Not running on this development release before 2020-04-01 Feb 12 10:02:12 blade systemd[1]: apt-daily.service: Succeeded. Feb 12 10:02:12 blade systemd[1]: Started Daily apt download activities. Feb 12 10:02:12 blade evolution-alarm[7943]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:02:12 blade pulseaudio[7212]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade at-spi-bus-launcher[7657]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade kdeconnectd[7947]:
[Bug 1854085] Re: Totem segfaults on launch
*** This bug is a duplicate of bug 1856927 *** https://bugs.launchpad.net/bugs/1856927 ** This bug has been marked a duplicate of bug 1856927 totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1854085 Title: Totem segfaults on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1854085] Re: Totem segfaults on launch
** Attachment removed: "_usr_bin_totem.1000.crash" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+attachment/5308002/+files/_usr_bin_totem.1000.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1854085 Title: Totem segfaults on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855546] Re: Desktop freezes a while than logs out
Still not resolved ** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- 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/1855546 Title: Desktop freezes a while than logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855546] Re: Desktop freezes a while than logs out
Still not resolved ** Changed in: gnome-shell (Ubuntu) Status: Expired => Incomplete -- 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/1855546 Title: Desktop freezes a while than logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855546] Re: Desktop freezes a while than logs out
Please remember to follow the steps in comment #4. -- 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/1855546 Title: Desktop freezes a while than logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855546] Re: Desktop freezes a while than logs out
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1855546 Title: Desktop freezes a while than logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855546] Re: Desktop freezes a while than logs out
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1855546 Title: Desktop freezes a while than logs out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862792] Re: gnome-shell always crash after boot
It sounds like the main issue is that Xwayland has crashed first: [ 31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to xwayland lost Please follow the steps in comment #2 to help us diagnose the problem further. -- 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/1862792 Title: gnome-shell always crash after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862792] Re: gnome-shell always crash after boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1862792 Title: gnome-shell always crash after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724098] Re: Panel menu icons are briefly way too big (when opened the first time)
I think this should be fixed in Gnome Shell 3.35 as the offending icons are no longer used. ** Tags added: fixed-in-3.35 fixed-upstream -- 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/1724098 Title: Panel menu icons are briefly way too big (when opened the first time) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
I think there is upstream work coming in Gnome Shell 3.36 related to this, but it doesn't seem to work in 20.04 right now. Which are you referring to? -- 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/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eog (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
This bug is not duplicate, or the 'duplicate' is private. Please address. ** This bug is no longer a duplicate of private bug 1671487 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1851807] Re: xdg-desktop-portal-gtk spams logs
This bug was fixed in the package xdg-desktop-portal - 1.4.2-2ubuntu1 --- xdg-desktop-portal (1.4.2-2ubuntu1) eoan; urgency=medium * d/p/background-Don-t-spam-the-logs.patch - Only warn once if we don't find the shell api (LP: #1851807) -- Ken VanDine Wed, 08 Jan 2020 09:26:04 -0500 ** Changed in: xdg-desktop-portal (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1851807 Title: xdg-desktop-portal-gtk spams logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1851807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection
This bug was fixed in the package poppler - 0.80.0-0ubuntu1.1 --- poppler (0.80.0-0ubuntu1.1) eoan; urgency=medium * Fix null pointer dereference when checking for glyphless font, thanks to Enrik Berkhan (LP: #1849773) -- Julian Andres Klode Mon, 16 Dec 2019 21:41:17 +0100 ** Changed in: poppler (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850707] Re: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts
Spoke too soon. Please ignore my previous comment. This is still happening, this time on Ubuntu 20.04 beta. I see the error every time whe launching Evolution. Oddly, I do not see this on my OpenSUSE Tumbleweed machine. Ubuntu has Evolution 3.34.1-3 whereas Tumbleweed has 3.34.3 in case that is relevant. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1850707 Title: "Data source "u...@gmail.com" does not support OAuth 2.0 authentication" shown each time Evolution starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1850707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1849773] Update Released
The verification of the Stable Release Update for poppler has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1849773 Title: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1849773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
nonetheless I do not experience the core issue (screensaver activating, and the unability to temporarily disable it while an mpv playback is running) alias mpv='mpv--no-audio-display --volume-max=132 --cache-secs=120 --alang=hu' No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan up-to-date -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
List of some mpv issues with gnome wayland, the window deco is somewhat mitigated by the new osc overlay that will, by default show in the absence of window deco. https://github.com/mpv-player/mpv/wiki/FAQ#i-use-gnome-wayland-and-i-have-xyz-problem -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
On 2/11/20 11:16 AM, Imre Péntek wrote: > as far as I can tell this bug is not present in 19.10 (fixed) > No, clearly never fixed and still an issue in 20.04. Only way around is for user from cli to use gnome-session-inhibit mpv /path/to/file -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
note to self: check my home ubuntu if I have any alias set for mpv -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
as far as I can tell this bug is not present in 19.10 (fixed) -- 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/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799073] Re: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10
This is fixed in Ubuntu 20.04 -- 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/1799073 Title: Full screen key chorded zoom (Alt+Super+=) fails in 18.04.1/18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799073/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862792] [NEW] gnome-shell always crash after boot
Public bug reported: gnome-shell always crash after boot with an UnreportableReason. This is in a Wayland session. There are no stability issues after boot. I get this information in the terminal after the command ubuntu-bug p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell p-i@pi-asus-b450f-gaming:~$ [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] GetVSyncParametersIfAvailable() failed for 1 times! ERROR:gl goes from 1 to 19. In Settings the Display is named Microstep 27" The problem might be hardware related: Mobo: ASUSTeK model: ROG STRIX B450-F GAMING GPU: AMD Navi 10 Radeon RX 5700 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 16:43:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-08 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1862792 Title: gnome-shell always crash after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862781] [NEW] GIMP crashed with a fatal error: fatal error: Aborted
Public bug reported:
```
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.1 (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 21396 - Thread 21396 #
[New LWP 21398]
[New LWP 21399]
[New LWP 21400]
[New LWP 21402]
[New LWP 21403]
[New LWP 21404]
[New LWP 21405]
[New LWP 21406]
[New LWP 21407]
[New LWP 21432]
[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=0x7ffd4c5fead0, fd=14) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f549f1cce00 (LWP 21396) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffd4c5fead0, fd=14) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f549e03b700 (LWP 21398) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f549d83a700 (LWP 21399) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f5495039700 (LWP 21400) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f5497285700 (LWP 21402) "gmain" 0x7f54a016ec2f in
__GI___poll (fds=0x56307b963b10, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7f5496a84700 (LWP 21403) "gdbus" 0x7f54a016ec2f in
__GI___poll (fds=0x56307b96c3a0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7f54808a9700 (LWP 21404) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f547bfff700 (LWP 21405) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
9Thread 0x7f547b7fe700 (LWP 21406) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
10 Thread 0x7f547affd700 (LWP 21407) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
11 Thread 0x7f5479a83700 (LWP 21432) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 11 (Thread 0x7f5479a83700 (LWP 21432)):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f54a0461d83 in g_cond_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f54a091f799 in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available.
#3 0x7f54a043f111 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f54a0255669 in start_thread (arg=) at
pthread_create.c:479
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {14795047680,
5299947660789190181, 140725884800318, 140725884800319, 140725884800464,
14795044096, -5249577578963890651, -5249945802672796123}, mask_was_saved =
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
#5 0x7f54a017b323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.
Thread 10 (Thread 0x7f547affd700 (LWP 21407)):
#0 syscall () at
[Bug 1856014] Re: Extension enable/disable slider switch missing
** Changed in: gnome-software Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1856014 Title: Extension enable/disable slider switch missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1856014/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1195911] Re: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for XXXX
I see this bug is still open. One work-around exists where ~/.ssh/config is used. Make an entry there for the host (or range of hosts using a pattern) and assign the right key using IdentityFile while also setting IdentitiesOnly to "yes". Both parts are needed for the work-around. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1195911 Title: ssh: Received disconnect from xx.yy.zz.aa: 2: Too many authentication failures for To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1195911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862767] Re: gnome-control-center crashes when try to open it
Strangely, purging nvidia drivers seems to fix the issue (following advice from https://askubuntu.com/a/1183137/44054). However, I had a different error as noted in the original bug description. However, now I can't have nvidia working with the settings. -- 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/1862767 Title: gnome-control-center crashes when try to open it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862767] [NEW] gnome-control-center crashes when try to open it
Public bug reported: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- 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/1862767 Title: gnome-control-center crashes when try to open it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
Paul, the "Stop & Quit" action is certainly a plus, but it doesn't solve this precise bug report, as there still is a case where "Rhythmbox stays running in the background after quit" (if you just close the window). I'm not the one to decide whether or not this is the desired behaviour, but I just think that the "Stop & Quit" action is only a workaround for this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
Julien, you are right in that the icon disappears if the program is simply closed with 'Quit'. However, I have added added rhythmbox to Ubuntu's dock so the icon is always visible. Right-clicking the icon displays "Stop & Quit". However, while the program is running, rather than just 'Quit' you can now 'Stop and Quit' from either the program icon or the icon that appears in the top bar while the program has focus. The new option in my view fixes the bug that was originally raised in that you can now quit and stop rhythmbox while music is playing, something that couldn't be done in previous releases. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Unfortunately when I run ubuntu-bug gnome-shell it collects the information but then when I tell it to send it just returns to the command line immediately rather than sending me to launchpad, so I will have to get that sorted first. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
@Paul White The problem is that, in gnome-shell, if you close Rhythmbox while music is playing, Rhythmbox's icon simply disappears. So, there is no way to reach this "Stop & Quit" quickmenu option. Unless I'm missing something, of course... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
In rhythmbox 3.4.4 there is an additional quickmenu option of 'Stop & Quit'. This version will be in Ubuntu 20.04. Does that addition fix this bug? It works for me but others may disagree. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862056] Re: Theme: use other exported colors
Here is the MR: https://gitlab.gnome.org/GNOME/gnome- software/merge_requests/421 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1862056 Title: Theme: use other exported colors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
This behaviour might me perfect in the default Ubuntu desktop (gnome- shell + Unity plugins), but it's broken if you use upstream gnome-shell because there is no tray to control Rhythmbox from once closed. I understand that Ubuntu's focus is on the default experience, but I guess it's also important to make it easy to use alternatives (especially when the "alternative" is actually upstream's default). So, wouldn't it be possible to detect whether the desktop has a "tray" (or "indicator" or whatever it's called in Unity), and really quit Rhythmbox on close if it doesn't? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
