[Bug 2037151] Re: Chromium glitches, Brave too, might be GPU
** Package changed: gnome-panel (Ubuntu) => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/2037151 Title: Chromium glitches, Brave too, might be GPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2037151/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013042] Re: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out
Confirmed in Ubuntu 23.04. The issue happens on my external monitor (2560x1440@60Hz) set as primary monitor and located above the laptop's internal FullHD display (both physically and virtually). Background with no elements on it is only displayed on my secondary monitor (laptop screen when external monitor is plugged in) when lock screen is displayed. If I unplug the external monitor, lock screen is correctly displayed on my internal laptop screen, together with the background. -- 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/2013042 Title: Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2013042/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
I see the same on Jammy, like the others it is reproducible easily by hitting the meta key and exiting from there in any way (hit ESC, select anything to start, ...). Sadly setting fixed workspaces (10) did not work around the issues for me, like it did for others. Occasionally (seems to depend if this issue races with something else as it seems more likely if the system has more apps running and me doing more things) I also get the stuck-desktop experience out of that. Usually starting with the mouse not being able to click everything anymore and a while after with a totally stuck desktop (not even ctrl-alt-f# gets me out anymore). That "stuckness" if it is still phase-I (mouse can't clock it all) sometimes resolves itself after a few minutes - no log entries in journal when that un-stucking happens. -- 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037141] Re: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary
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/2037141 Title: Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037088] Re: While using secondary display - Top right display not responsive
*** This bug is a duplicate of bug 2037141 *** https://bugs.launchpad.net/bugs/2037141 ** This bug has been marked a duplicate of bug 2037141 Multi monitor with different scale factors causes windows to use scale factor of adjacent monitor before arriving at boundary -- 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/2037088 Title: While using secondary display - Top right display not responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023322]
(In reply to Michael Catanzaro from comment #57) > (In reply to Thomas Zajic from comment #56) > > Is this the same bug that is being discussed here? > > No, because the problem here is specific to GTK 4 and has been around for > years. That is, since you didn't have this problem with 2.40, this bug is > not your bug. > > You're probably hitting either bug #259644 or bug #261874, depending on > whether or not you see those KMS DRM_IOCTL_MODE_CREATE_DUMB error messages. > Please confirm. I'm not using modesetting (KMS), I'm not using flatpak, and I don't see those error messages in any of my logs. So, which of the two "alternative bugs" is "mine"? :-) Thanks, Thomas -- 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/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023322]
Here's my copy/paste of webkit://gpu, in case that matters. Note that
I'm currenty setting "WEBKIT_DISABLE_COMPOSITING_MODE=1" globally from
/etc/profile, to work around the rendering bug in liferea.
{
"Version Information": {
"WebKit version": "WebKitGTK 2.42.0 (tarball)",
"Operating system": "Linux 6.1.54 #1 SMP PREEMPT_DYNAMIC Tue Sep 19
15:59:34 CEST 2023 x86_64",
"Desktop": "GNOME-Flashback:GNOME",
"Cairo version": "1.16.0 (build) 1.16.0 (runtime)",
"GStreamer version": "1.22.5 (build) GStreamer 1.22.6 (runtime)",
"GTK version": "4.12.1 (build) 4.12.2 (runtime)"
},
"Display Information": {
"Type": "X11",
"Screen geometry": "1920,0 1920x1080",
"Screen work area": "1920,28 1920x1020",
"Depth": "24",
"Bits per color component": "8",
"DPI": "96"
},
"Hardware Acceleration Information": {
"Policy": "never",
"WebGL enabled": "Yes"
}
}
--
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/2023322
Title:
Unable to setup Google Online Accounts with Nvidia drivers
To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037121] Re: Freeze when going full screen while watching video
Mine has been doing this as well since kernel 6 Ubuntu 22.04.3 LTS Device: AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.52, 6.3.7-060307-generic) (0x73bf) OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.5-0ubuntu0.1~22.04.3 Multi Display seems to happen when ever something full-screen is used and then go click on an unfocused window and screen stops getting drawn clock and everything then alt-f1 / alt-f7 back to desktop and it works again however for me all syslog shows is Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1d64bc9! Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. you should probably file a bug about this. Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1c000f7! Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. you should probably file a bug about this. -- 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/2037121 Title: Freeze when going full screen while watching video To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037161] [NEW] drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110
Public bug reported: I noticed that when I choose Wayland to logon to my Ubuntu 23.04 desktop PC, the display would crash at least once within 6 hours. Crash means total dark screen. Mouse,keyboard, or replugging the HDMI cable doesn't have any effects. Once the display crashes, ssh is possible but reboot commands would time out. sudo commands take more than 10 seconds. The problem does not occur if I choose xorg to logon to the desktop. The hardware specifications are: amd-ryzen5-4600g description: Computer width: 64 bits capabilities: smp vsyscall32 *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 15GiB *-cpu product: AMD Ryzen 5 4600G with Radeon Graphics vendor: Advanced Micro Devices [AMD] physical id: 1 bus info: cpu@0 version: 23.96.1 size: 4291MHz capacity: 4307MHz width: 64 bits Kernel info: uname -a Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux more logs in the attachment. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu ** Attachment added: "kernel log and display info" https://bugs.launchpad.net/bugs/2037161/+attachment/5703736/+files/logs.txt ** Description changed: I noticed that when I choose Wayland to logon to my Ubuntu 23.04 desktop PC, the display would crash at least once within 6 hours. Crash means total dark screen. Mouse,keyboard, or replugging the HDMI cable doesn't have any effects. Once the display crashes, ssh is possible but reboot commands would time out. sudo commands take more than 10 seconds. The problem does not occur if I choose xorg to logon to the desktop. The hardware specifications are: amd-ryzen5-4600g - description: Computer - width: 64 bits - capabilities: smp vsyscall32 - *-core -description: Motherboard -physical id: 0 - *-memory - description: System memory - physical id: 0 - size: 15GiB - *-cpu - product: AMD Ryzen 5 4600G with Radeon Graphics - vendor: Advanced Micro Devices [AMD] - physical id: 1 - bus info: cpu@0 - version: 23.96.1 - size: 4291MHz - capacity: 4307MHz - width: 64 bits + description: Computer + width: 64 bits + capabilities: smp vsyscall32 + *-core + description: Motherboard + physical id: 0 + *-memory + description: System memory + physical id: 0 + size: 15GiB + *-cpu + product: AMD Ryzen 5 4600G with Radeon Graphics + vendor: Advanced Micro Devices [AMD] + physical id: 1 + bus info: cpu@0 + version: 23.96.1 + size: 4291MHz + capacity: 4307MHz + width: 64 bits Kernel info: uname -a Linux amd-ryzen5-4600g 6.2.0-32-generic #32-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 14 10:03:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux + + more logs in the 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/2037161 Title: drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037121] Re: Freeze when going full screen while watching video
Hi. Would you mind clicking the button "This bug affects you"? This way the issue gets more attention. Meanwhile, it seems I found a workaround. I installed an extension [0] which disables unredirect fullscreen windows in gnome-shell and so far the freeze has not happened again. Maybe you wanna give it a try too. Still, this is something that needs to be fixed. [0]: https://extensions.gnome.org/extension/1873/disable-unredirect- fullscreen-windows/ -- 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/2037121 Title: Freeze when going full screen while watching video To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037121] Re: Freeze when going full screen while watching video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2037121 Title: Freeze when going full screen while watching video To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034069] Re: Animation when exiting the overview doesn't appear to complete properly
Likewise I haven't noticed this for a while either. -- 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/2034069 Title: Animation when exiting the overview doesn't appear to complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037166] [NEW] Entering/Waking up from sleep kills active session
You have been subscribed to a public bug: I have reported this bug against gdm3 but I do not know if it is the cause of the bug. My experience is this: I work on my laptop as usual, and I may have an application loaded. This could be anything - my browser, a temrinal or even just nautilus. Why my laptop goes to sleep either manually through the top right menu or I type sleep of suspend into the application launcher, or if it's automatically by letting the laptop fall asleep automatically after a period of time or I close the laptop lid, when I next wake from sleep my active session will be terminated. All applications which were running will no longer be running. I have fully reinstalled my mantic instance, and have also ensured that my packages are all up to date, but the problem persists. Additional Drivers and Firmware Updates are reporting that there is nothing to install or update. ``` $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 12:41:07 2023 InstallationDate: Installed on 2023-09-20 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230919) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- Entering/Waking up from sleep kills active session https://bugs.launchpad.net/bugs/2037166 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037166] Re: Entering/Waking up from sleep kills active session
** Package changed: ubuntu => gdm3 (Ubuntu) -- 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/2037166 Title: Entering/Waking up from sleep kills active session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037121] Re: Freeze when going full screen while watching video
well I am using "Unity" and the other seems to be using "Gnome" this is the only other reported instance in the last year that is similar to whats happening and nothing really shows in logs so no idea what the issue is has been happening all year from kernel 6 - 6.4 pretty sure it did not happen with 5.18 still deciding if I should roll back kernel to 5's or try 6.5 on next reboot to see if its kernel related or mesa / some other update related but then my VR headsets will break again going back to 5's I can trigger it every-time so if their are any commands to run for debugging let me know other things that are in the logs when it happen are connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 23 22:11:53 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:53 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:53 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:53 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:54 aio cpufreq-applica[1406267]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 23 22:11:54 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:54 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:54 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:54 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:55 aio systemd[1]: collectd.service: Scheduled restart job, restart counter is at 710586. Sep 23 22:11:55 aio systemd[1]: Stopped Statistics collection and monitoring daemon. Sep 23 22:11:55 aio systemd[1]: Starting Statistics collection and monitoring daemon... Sep 23 22:11:55 aio collectd[285530]: Parse error in file `/etc/collectd/collectd.conf', line 889 near `': block not closed Sep 23 22:11:55 aio collectd[285530]: yyparse returned error #1 Sep 23 22:11:55 aio collectd[285530]: configfile: Cannot read file `/etc/collectd/collectd.conf'. Sep 23 22:11:55 aio collectd[285530]: Unable to read config file /etc/collectd/collectd.conf. Sep 23 22:11:55 aio collectd[285530]: Error: Parsing the config file failed! Sep 23 22:11:55 aio collectd[285530]: block_begin = Plugin; block_end = Listen; Sep 23 22:11:55 aio systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE Sep 23 22:11:55 aio systemd[1]: collectd.service: Failed with result 'exit-code'. Sep 23 22:11:55 aio systemd[1]: Failed to start Statistics collection and monitoring daemon. Sep 23 22:11:55 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1d5bd3a! Sep 23 22:11:55 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. you should probably file a bug about this. Sep 23 22:11:55 aio hud-service[36594]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/228589571" Sep 23 22:11:55 aio cpufreq-applica[1406267]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 23 22:11:55 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:55 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:55 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:55 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:56 aio cpufreq-applica[1406267]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 23 22:11:56 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:56 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:56 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:56 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:57 aio cpufreq-applica[1406267]: Attempting to run a JS ca
[Bug 2037121] Re: Freeze when going full screen while watching video
*** This bug is a duplicate of bug 2035016 *** https://bugs.launchpad.net/bugs/2035016 MasterCATZ, this bug is about Ubuntu 23.10; it is different than an issue affecting Ubuntu 22.04 LTS. Also, this is a bug about Mutter (or GNOME Shell), not about Compiz and Unity. Please file a new bug for your issue. https://help.ubuntu.com/community/ReportingBugs -- 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/2037121 Title: Freeze when going full screen while watching video To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037121] Re: Freeze when going full screen while watching video
*** This bug is a duplicate of bug 2035016 *** https://bugs.launchpad.net/bugs/2035016 Johon, we fixed a fullscreen freeze issue with mutter 45.0-2ubuntu1 several hours ago. Please check for and install updates, then restart your computer. If you still have an issue with the new mutter version, please open a new bug using ubuntu-bug libmutter-13-0 ** This bug has been marked a duplicate of bug 2035016 one of 3 monitors "frozen" when a window moves there -- 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/2037121 Title: Freeze when going full screen while watching video To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037166] Re: Entering/Waking up from sleep kills active session
** Also affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/2037166 Title: Entering/Waking up from sleep kills active session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034069] Re: Animation when exiting the overview doesn't appear to complete properly
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: New => 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/2034069 Title: Animation when exiting the overview doesn't appear to complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034069] Re: Animation when exiting the overview doesn't appear to complete properly
Thanks @jbicha for the pointer on managing the bug status. Will do that going forward -- 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/2034069 Title: Animation when exiting the overview doesn't appear to complete properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2034069/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037182] [NEW] Restarting GNOME doesn't work
Public bug reported: Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 14:56:37 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (53 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2037182 Title: Restarting GNOME doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037181] [NEW] Gimp 2.10.30 crashed couple seconds after fresh install on virtual machine
Public bug reported:
EDIT:
App crashed couple seconds after I opened it on virtual machine (Ubuntu desktop
with i3 windows manager)
uname -a:
Linux marek-VirtualBox 6.2.0-33-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Thu Sep 7 10:33:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```
GNU Image Manipulation Program version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
11.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-11
--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-bootstrap --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
--enable-libphobos-checking=release --with-target-system-zlib=auto
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-O5cEXJ/gcc-11-11.2.0/debian/tmp-gcn/usr
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.2.0 (Ubuntu 11.2.0-16ubuntu1)
# Libraries #
using babl version 0.1.92 (compiled against version 0.1.88)
using GEGL version 0.4.34 (compiled against version 0.4.34)
using GLib version 2.72.4 (compiled against version 2.71.1)
using GdkPixbuf version 2.42.8 (compiled against version 2.42.6)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.6 (compiled against version 1.50.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
# Stack traces obtained from PID 386576 - Thread 386576 #
[New LWP 386577]
[New LWP 386578]
[New LWP 386579]
[New LWP 386580]
[New LWP 386581]
[New LWP 386591]
[New LWP 387164]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7fff6b34ef90, fd=17) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target Id Frame
* 1Thread 0x7f339dcf5e80 (LWP 386576) "gimp" __GI___libc_read
(nbytes=256, buf=0x7fff6b34ef90, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f339cc4c640 (LWP 386577) "worker"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f339c44b640 (LWP 386578) "worker"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f339bc4a640 (LWP 386579) "worker"syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f339afb2640 (LWP 386580) "gmain" 0x7f339e318d7f in
__GI___poll (fds=0x55ab790d1ad0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7f339a7b1640 (LWP 386581) "gdbus" 0x7f339e318d7f in
__GI___poll (fds=0x55ab790e4440, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7f339968b640 (LWP 386591) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f3370be2640 (LWP 387164) "pool-gimp" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7f3370be2640 (LWP 387164) "pool-gimp"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1 0x7f339e67e04c in g_cond_wait_until () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2 0x7f339e5fe3e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3 0x7f339e5fe566 in g_async_queue_timeout_pop () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4 0x7f339e660759 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5 0x7f339e65da51 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6 0x7f339e294b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
out =
unwind_buf = {cancel_jmp_buf =
[Bug 2037191] [NEW] Lockscreen sometimes doesn't render
Public bug reported: Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions". But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open. There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta. There are however, some really suspicious error messages in the logs: Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91) Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28) Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48) Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 == Sep 23 17:31:26 user-83
