[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
In my case it's not only on Chrome, resizing and moving any application can reproduce this issue in Ubuntu 23.04 GFX Card: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] GFX driver: nvidia-driver-525 gnome-shell: 44.0-2ubuntu3 Kernel: 6.2.0-19-generic -- 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/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
I'm not sure, but I think the issue was present in kinetic. Hence not a regression (probably). I agree. Only this issue would not motivate a respin, and mentioning it in the release note sounds reasonable. -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999578] Re: Bursts of high CPU usage after triggering overview
Fixed in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2823 ** Changed in: gnome-shell (Ubuntu) Status: Opinion => Fix Committed ** Tags added: fixed-in-mutter-44.1 fixed-upstream ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1999578 Title: Bursts of high CPU usage after triggering overview To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1999578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_
** Changed in: indicator-messages (Ubuntu) Status: Confirmed => Invalid ** Changed in: accountsservice (Ubuntu) Assignee: Sebastien Bacher (seb128) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
Gunnar, thanks for reporting on this bug. A quick question: since the original issue got reported in 2022 before kinetic release, what was the status for this in 22.10? Was this also broken there? It's important for us to know if this is a regression or not. Also, with a visible workaround (re-running firefox), my recommendation would be to release note it, and maybe only include it in case we will need to do a full respin of all desktop RC images for 23.04. -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.
Confirmed the bug is fixed in 23.04. Also I do still have the smooth theme switch animation. ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Triaged => 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/1989477 Title: Switching to dark mode in settings does not change shell theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-44.1 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), 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. [windowPreview.js:566] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-gnome-shell-44.1 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/1968390 Title: JS ERROR: TypeError: this.window_container is null To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
Marco Trevisan submitted an upstream mutter merge request with a fix of this issue. I have applied it to the Ubuntu package through a PPA, installed the resulting binaries, and accomplished some tests: * I can no longer reproduce the issue with a black window when opening Firefox in wayland, not even after having run "killall Xwayland". * This sequence: killall Xwayland; sleep 3; GDK_BACKEND=x11 gedit results in a normal gedit window as far as I can tell. * I also entered an x11 session, and also there I can open Firefox without issues. So I uploaded mutter to the lunar unapproved queue for consideration by the release team. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016914] Re: gsd-smartcard: segfault on startup
Sure! I've gone ahead and updated the description with a better description of the problem. I have the crashdump files as well, if those can be uploaded somewhere. ** Description changed: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. + + + System Info: + This is Ubuntu 22.04.2 LTS at Kernel 5.19.0-38-generic + The Smart Card reader is an Identiv uTrust 4711 F with both SAM and Contactless slots + The system is an HP ZBook Firefly 14 G7 + + Detailed issue: + When the smartcard reader is plugged into the system, and an NXP SAM AV3 card is inserted into the physical smartcard slot, upon login several (5) Ubuntu Error report windows will open asking to report a crash. The reader lights will flicker for about 5 minutes until they finally stop. No other issues are seen with the system during this time. + + Upon looking at /var/log/syslog, the errors listed in the attachment are + visible as it appears gsd-smartcard is in a loop of restarting and + crashing following an error. + + /var/crash contains two files from the crash loop, + _usr_libexec_gsd_smartcard.1000.crash and + _usr_libexec_gsd_smartcard_127.crash + + Eventually the crashes seem to stop and the light stops flickering, but + a logout and log back in will restart the issue again, as will rebooting + the machine. Re-plugging the device while logged in does not seem to + cause it to start the crash loop again. + + To complete the standard questions: + 1. I logged into my computer and saw error messages + 2. I expected the smart card to be ignored if there was a card inserted that was unexpected or incompatible with the gnome settings daemon + 3. I encountered several crash reporter messages upon logging in, which seem to have come from the gsd-smartcard program -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window on wayland
** Summary changed: - firefox black window + firefox black window on wayland ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/1987976 Title: firefox black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
*** This bug is a duplicate of bug 1987976 *** https://bugs.launchpad.net/bugs/1987976 Let's use the original bug report instead. ** This bug has been marked a duplicate of bug 1987976 firefox black window -- 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
Attached is a v2 debdiff for Focal, after Denison correctly pointed out that I was missing a patch. ** Description changed: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 - Focal requires three additional patches to solve the issue, namely: + Focal requires four additional patches to solve the issue, namely: commit 8065985c8d818414a36fe151862afdf42c5eda8a Author: Laurent Bigonville Date: Sat, 4 Apr 2020 19:18:00 +0200 Subject: Move the Install section to the systemd .service file instead - of the udev one + of the udev one Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/8065985c8d818414a36fe151862afdf42c5eda8a commit 74ae33ce01b8d314d6e33746915f75f270b0e21d Author: Sam Thursfield Date: Tue, 3 Nov 2020 12:50:02 +0100 Subject: miners: Opt out of systemd / XDG autostart integration Link: https://gitlab.gnome.org/GNOME/tracker-miners/-/commit/74ae33ce01b8d314d6e33746915f75f270b0e21d commit 3a75f93865e8eb002a377a341a72b1a4b22a8040 Author: Sam Thursfield Date: Tue, 27 Oct 2020 22:05:07 +0100 Subject: miners: Tie systemd startup to gnome-session.service
[Bug 2016914] Re: gsd-smartcard: segfault on startup
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
I applied a mutter patch written by Marco Trevisan and uploaded to a PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/mutter With the binaries from that PPA build I can no longer reproduce the black window issue described in this bug. Not even after having run: killall Xwayland So I pushed the patch to the repo. https://salsa.debian.org/gnome-team/mutter/-/commit/a400e60d ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
** Changed in: mutter Status: Unknown => 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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016428] Re: nautilus crashes when entering a query into the search box
Update: It seems to be fixed by a tracker3 reset --filesystem. I'll see how it goes... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016428 Title: nautilus crashes when entering a query into the search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] Re: Firefox snap opens a black window on wayland
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2472 https://gitlab.gnome.org/GNOME/mutter/-/issues/2472 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2472 Importance: Unknown Status: Unknown ** Also affects: xwayland (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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995092] Re: Wrong ubuntu logo in About section in darkmode
Thanks for the report, it was a packaging bug, a fix is commited now in https://salsa.debian.org/gnome-team/gnome-control- center/-/commit/0357698d ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- 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/1995092 Title: Wrong ubuntu logo in About section in darkmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1995092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016918] [NEW] Firefox snap opens a black window on wayland
Public bug reported: This may actually be a duplicate of bug #1987976, but I was advised to file a new bug to get attention to this issue for the 23.04 release and consider a possible workaround. https://irclogs.ubuntu.com/2023/04/18/%23ubuntu-desktop.html#t17:42 In short: On a fresh 23.04 install, the first time in each wayland session I try to launch Firefox via the icon in the dock, it just opens a black window. I can close Firefox, and try again, and then it opens as expected. I'd better mention that I have a NVIDIA card, but the issue is present both with the NVIDIA and the Nouveau driver. While it might be some kind of race condition (not everyone is affected), in my case it happens every time. I have a proposed workaround: use the xrefresh command. That could for instance be done with this file: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true That idea isn't new. We have shipped a similar file (for a similar reason) with ibus-mozc for a few cycles: https://salsa.debian.org/debian/mozc/-/commit/4e48b655 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: High Status: New ** Also affects: firefox (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/2016918 Title: Firefox snap opens a black window on wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016914] Re: gsd-smartcard: segfault on startup
Have attempted to use apport to attach the crash dump but have so far been unsuccessful. It doesn't seem to upload anything. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window
Simple way to reproduce is: killall XWayland # may kill other apps! start firefox Now, it happens in all the installation where something doesn't bring X11 on startup and firefox is the first app launched. -- 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/1987976 Title: firefox black window To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016914] [NEW] gsd-smartcard: segfault on startup
Public bug reported: A smartcard reader attached to the computer on startup, containing a non-standard smartcard (in this case an NXP AV3 SAM card) causes gsd- smartcard to segfault and restart 200 times after login. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Syslog snipped from crash loop" https://bugs.launchpad.net/bugs/2016914/+attachment/5665043/+files/gsd-smartcard_crash_syslog.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2016914 Title: gsd-smartcard: segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2016914/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016906] [NEW] Inactive zombie ghost icons left behind on desktop when copying files
Public bug reported: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release:22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Example Zombie Ghost Icons On Desktop" https://bugs.launchpad.net/bugs/2016906/+attachment/5665032/+files/Screenshot%20from%202023-04-08%2007-54-06.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2016906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
On Tue, Apr 18, 2023 at 12:36 AM Daniel van Vugt <2006...@bugs.launchpad.net> wrote: > > Wow, great work Dann! Would you like to distro patch it or shall I? I'm happy either way, though I don't know the workflow vis-à-vis salsa here. -dann -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b
** Changed in: gnome-shell Status: Unknown => 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/1968383 Title: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), 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. [windowPreview.js:566] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016855] Re: padlock icon is missing sometimes
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016855 Title: padlock icon is missing sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989477] Re: Switching to dark mode in settings does not change shell theme.
I'm running 23.04 daily build and I can confirm the issue is gone here. Though the smooth theme switch animation that Gnome has is also gone, but I assume that is because the method of changing theme is changed to fix the aforementioned problem? -- 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/1989477 Title: Switching to dark mode in settings does not change shell theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
Upstream project will include the fix for 44.1. ** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016855] [NEW] padlock icon is missing sometimes
Public bug reported: The directory icon modifier which is the padlock is missing from a child directory after a recursive "read-only" chmod on a parent directory. This bug has been around for years. Full description at... https://askubuntu.com/questions/1462795/padlock-on-directory-icons-may-be-missing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 05:38:36 2023 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1080, 749)' b'org.gnome.nautilus.preferences' b'show-image-thumbnails' b"'never'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'date_modified', 'date_modified_with_time', 'starred']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2022-08-27 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2016855 Title: padlock icon is missing sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999578] Re: Bursts of high CPU usage after triggering overview
** Changed in: gnome-shell 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/1999578 Title: Bursts of high CPU usage after triggering overview To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1999578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
** Description changed: [ Impact ] Switching to a second user falls back to Wayland even when Xorg was explicitly selected. [ Test Plan ] - 1. Create multiple accounts. - - 2. Log in to user1 using a Xorg session. Don't log out. - - 3. Log in to user2 using a Xorg session. - - Verify you are in a Xorg session and not Wayland. + TBC by affected users. [ Where problems could occur ] Any part of the login procedure as that is what is being modified. [ Original Description ] I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Fix proposed: https://salsa.debian.org/gnome- team/gdm/-/merge_requests/18 -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Still here in 22.04 LTS; the workaround I use is the last one suggested in https://askubuntu.com/a/1428798/16395 (WARNING; that will allow evince to launch *any* snap in your system. But otherwise, evince is severely limited...) -- 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/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
** Changed in: gdm3 (Ubuntu Jammy) Assignee: dann frazier (dannf) => Daniel van Vugt (vanvugt) ** Changed in: gdm3 (Ubuntu Jammy) Status: Triaged => In Progress -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987976] Re: firefox black window
This fixes the issue for me: $ cat /etc/xdg/autostart/firefox-snap-launch-xwayland.desktop [Desktop Entry] Name=Launch Xwayland on startup of wayland session Comment=This allows to start the Firefox snap from the dock without a black window Type=Application Exec=sh -c 'if [ "$XDG_SESSION_TYPE" = "wayland" ]; then xrefresh; fi' TryExec=xrefresh OnlyShowIn=GNOME; NoDisplay=true How about letting some package install that, or maybe make use of the xrefresh command in some other way. -- 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/1987976 Title: firefox black window To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016743] Re: Unable to switch windows while drag-and-drop in Xorg sessions
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/2016743 Title: Unable to switch windows while drag-and-drop in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016743] Re: Unable to switch windows while drag-and-drop in Xorg sessions
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/2016743 Title: Unable to switch windows while drag-and-drop in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016743] Re: Unable to switch windows while drag-and-drop
** Tags added: dnd ** Summary changed: - Unable to switch windows while drag-and-drop + Unable to switch windows while drag-and-drop in Xorg sessions -- 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/2016743 Title: Unable to switch windows while drag-and-drop in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2016743/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Wow, great work Dann! Would you like to distro patch it or shall I? ** No longer affects: gnome-session (Ubuntu) ** No longer affects: systemd (Ubuntu) ** Tags added: fixed-in-gdm3-43.0 fixed-upstream ** Also affects: gdm3 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: gdm3 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: gdm3 (Ubuntu Lunar) Status: Confirmed => Fix Released ** Changed in: gdm3 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gdm3 (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: gdm3 (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: gdm3 (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: gdm3 (Ubuntu Jammy) Status: Confirmed => Triaged ** Description changed: + [ Impact ] + + Switching to a second user falls back to Wayland even when Xorg was + explicitly selected. + + [ Test Plan ] + + 1. Create multiple accounts. + + 2. Log in to user1 using a Xorg session. Don't log out. + + 3. Log in to user2 using a Xorg session. + + Verify you are in a Xorg session and not Wayland. + + [ Where problems could occur ] + + Any part of the login procedure as that is what is being modified. + + [ Original Description ] + I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
