[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
The bug is also present in 20.04. I got it after a system resume from sleep. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867507] Re: nautilus crashed when opening session
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1867507 Title: nautilus crashed when opening session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1867507/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874262] Re: User session does not start: Problem with chrome-remote-desktop
After some further testing, fixing the GDM bug allows logging into both X11 and Wayland on 19.10 while Chrome Remote Desktop is running, but on 20.04, I cannot start a Wayland while CRD is running (X11 still works once the GDM fix is applied). Taking a brief look at the logs, it appears there is a separate but similar bug with how Gnome Shell attempts to determine its seat when running as a Systemd user service. My guess it that it is finding the CRD session, which doesn't have a seat, instead of its own, and then failing. -- 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/1874262 Title: User session does not start: Problem with chrome-remote-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1874262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863376] Re: Seg Fault during version check
** Changed in: nautilus (Ubuntu) Status: Invalid => Confirmed -- 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/1863376 Title: Seg Fault during version check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1863376/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 269441] Re: Trash always full
Linux Mint 19.3 Cinnamon - This issue has plagued me since I decided to share an entire volume over my home network with samba. One day, I noticed the sharing emblem on the volume's .Trash-1000 icon. Thus I right-clicked on it -> Properties -> Share tab, I switched off sharing of .Trash-1000 folder and BOOM! The issue disappeared. Strangely, the sharing emblem was just on .Trash-1000 icon. Just for the record, the "indicted" volume is formatted to ntfs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/269441 Title: Trash always full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders
In my experience, when I open an app and meanwhile open and close a folder the GNOME freezes. -- 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/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878592] Re: super key problem
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878592 Title: super key problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878766] Re: When press command button on Russian language keyboard Activities don't open
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878766 Title: When press command button on Russian language keyboard Activities don't open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878592] [NEW] super key problem
You have been subscribed to a public bug: in farsi language super key not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 14 15:22:42 2020 InstallationDate: Installed on 2020-05-11 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to focal on 2020-05-11 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- super key problem https://bugs.launchpad.net/bugs/1878592 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878766] [NEW] When press command button on Russian language keyboard Activities don't open
You have been subscribed to a public bug: It was working while I didn't installed one of the update and now it still does not work ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 15 10:19:14 2020 InstallationDate: Installed on 2020-04-08 (37 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- When press command button on Russian language keyboard Activities don't open https://bugs.launchpad.net/bugs/1878766 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877038] Re: Firefox seems to lack FIDO2 support with Yubikeys
Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370 ? If so, in the duplicate bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said "This is a 2020 goal." ** Package changed: evolution (Ubuntu) => firefox (Ubuntu) ** Bug watch added: Mozilla Bugzilla #1530370 https://bugzilla.mozilla.org/show_bug.cgi?id=1530370 ** Bug watch added: Mozilla Bugzilla #1619850 https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 -- 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/1877038 Title: Firefox seems to lack FIDO2 support with Yubikeys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877038/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878998] [NEW] Value in gnome-shell.css not used
Public bug reported: The value for selected-color at line 153 in the gnome-shell.css files for Yaru and Yaru-dark is ignored by the shell. (Selected text should change color from dark grey to white.) ** 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/1878998 Title: Value in gnome-shell.css not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878998/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878524] Re: folder icon can't link nautilus icon in unity launcher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1878524 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: nautilus (Ubuntu) => unity (Ubuntu) ** Changed in: unity (Ubuntu) Importance: Undecided => Low ** Changed in: unity (Ubuntu) Status: New => Incomplete -- 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/1878524 Title: folder icon can't link nautilus icon in unity launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1878524/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 888662] Re: Web browsers should share the cache
** Changed in: netsurf (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/888662 Title: Web browsers should share the cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amaya/+bug/888662/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()
No error reported for the SRU or groovy version for this crash at https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877212] Re: Update to 3.36.2 and SRU it
3.36.2-1ubuntu1~20.04.1 is now in proposed ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877212 Title: Update to 3.36.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877212/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876914] Re: Update to 1.64.2 and SRU it
1.64.2-1ubuntu1~20.04.1 is in focal proposed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1876914 Title: Update to 1.64.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1876914/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750818] Re: Already installed deb packages not showing as installed when opened
@asciiwolf, with just the other commit it definitely fixed the issue described in the bug report. I spent some time looking at the other and might cherry-pick that as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1750818 Title: Already installed deb packages not showing as installed when opened To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1750818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793496] Re: scaling changes when closing/re-opening the lid
This was already part of 3.36.1-3ubuntu2, so no need to perform verification (already done, BTW). ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1793496 Title: scaling changes when closing/re-opening the lid To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877209] Re: Update to 3.36.2 and SRU it
Version 3.36.2-1ubuntu1~20.04.1 is in proposed. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1877209 Title: Update to 3.36.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878988] [NEW] stuttering or dropped frames in Gnome
Public bug reported: experiencing frame "stutter" or regular dropped frames in gnome. Occurs with intel integrated graphics, AMD gpu with open source drivers, and nvidia gpu with proprietary drivers. This does not occur in KDE. I do not believe this occurring before upgrading from 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri May 15 16:20:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-06 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screen recording of stutter" https://bugs.launchpad.net/bugs/1878988/+attachment/5372282/+files/gnome-recording.mp4 -- 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/1878988 Title: stuttering or dropped frames in Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878670] Re: Gnome crash frequently
Hi, Thanks for the fast responses. I have tried to collect the requested information but: 1) There are no files in /var/crash 2) The only item in https://errors.ubuntu.com/user/8dfc634ec... is: 2020-04-28 23:042020-04-28 21:04 UTCCrash google-chrome-stable https://errors.ubuntu.com/oops/6c75c4c0-8996-11ea-a340-fa163e6cac46 3) I commented out line23 :"'problem_types': ['Bug', 'Package']," from /etc/apport/crashdb.conf, rebooted and managed to reproduce the crash. (it's not easily reproducible, or at least I haven't found out how to reliably reproduce). But still no files in var/crash. I also tried "apport-collect 1878670" (with and without sudo): kaa@kaa-XPS-13-9300:~$ apport-collect 1878670 ERROR: The python3-launchpadlib package is not installed. This functionality is not available. kaa@kaa-XPS-13-9300:~$ sudo apt list python3-launchpadlib Listing... Færdig python3-launchpadlib/bionic,bionic,now 1.10.6-1 all [Installeret] -- 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/1878670 Title: Gnome crash frequently To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)
Daniel, I reproduced the same issue in a VM in post #4, and I gave you the steps to reproduce it. I strongly suggest you *try* it. It is trivially simple, takes less than five minutes to reproduce, or 15 minutes tops if you want to spin up a new VM. This is exactly the same issue that I saw on my laptop. The reason I reproduced this on a VM was to confirm that the issue could be seen on other machines, and to give you an easily reproducible test case, so that you can confirm the bug and move it the right team to investigate. Otherwise, we can keep repeating this dance of asking for more information and moving the bug back to incomplete, but this does nothing to advance our mutual goal of helping make Ubuntu better. ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1878275 Title: wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)
** Attachment added: "journalctl -b-1 from laptop" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+attachment/5372266/+files/prevboot.txt -- 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/1878275 Title: wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878275] Re: wayland session hard freezes on login from GDM (X11 session works fine)
** Attachment added: "lspcik from laptop" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+attachment/5372265/+files/lspcik.txt -- 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/1878275 Title: wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878670] Re: Gnome crash frequently
Probably a duplicate of bug 1872001. -- 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/1878670 Title: Gnome crash frequently To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872364] Re: Launchpad translations are not exported back to the snap package
This string is also missing in pofiles in the Snap Store git. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1872364 Title: Launchpad translations are not exported back to the snap package To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1872364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872364] Re: Launchpad translations are not exported back to the snap package
Simos, the "Permissions" string translation is now correctly applied in Snap Store, however the "_Permissions" string one is not although the string is available and translated on Launchpad (https://translations.launchpad.net/snap-store). Here is a new ticket for this issue: https://bugs.launchpad.net/snap-store/+bug/1878672 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1872364 Title: Launchpad translations are not exported back to the snap package To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1872364/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878956] Re: Shutdown continues even after cancelled by application
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- 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/1878956 Title: Shutdown continues even after cancelled by application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1878956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750818] Re: Already installed deb packages not showing as installed when opened
Ken, I see that one of the MR commits was already added to snap-store git, however to make this fix actually work, the another one (https://gitlab.gnome.org/GNOME/gnome- software/-/merge_requests/457/diffs?commit_id=74980a2f94cefa1e75778bf8fcba55ddaa880405) needs to be added as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1750818 Title: Already installed deb packages not showing as installed when opened To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1750818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
An amendment to my previous post re selecting "say" File. Some applications ie. Arduino IDE behave correctly (e.g. selecting File produces a dropdown immediately under the File option in the same screen) whereas other apps ie. OpenOffice causes the dropdown under File to open in the other screen. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
I am still experiencing the bug. It seems that the delay is smaller, but as it is very random is difficult to be sure. -- 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/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
It is obviously related to yahoo for all of us, but that does not mean Yahoo caused it. While it might be that Yahoo has done some changes, I have other mail clients (Thunderbird on Ubuntu, K9 on Android, Mailmate on Mac) that have not been updated and have had no problem with yahoo. We are very specifically looking at Evolution in relation to Yahoo. Two mere suspicions, and I have no way to check due to lack of knowledge, a) there was an update on Ubuntu that caused the issue. b) indeed, yahoo did some changes, but they were no problem before. Whatever library in the background handles this, worked fine so far, but could not cope with this hypothetical change. Then it must be that Thunderbird works differently. cheers, Martin On Fri, 2020-05-15 at 14:17 +, richard wrote: > This same problem started the first week of May with my IMAP+ AT "Error > performing TLS handshake: ..." > Ubuntu Mate 16 Evolution 3.18.5.2-0ubuntu3.2 > > Sending SMTP still works. > > Reading through the posts it's clear that it's a Yahoo issue since Yahoo > manages AT, AOL, Verizon and Yahoo mail and those are the only ones > affected. > > Why has no fix-update been created yet? > It's not like people are so swamped with work they don't have time to. > -- 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878956] [NEW] Shutdown continues even after cancelled by application
Public bug reported: 1. Open a text editor of any kind and edit any document. Do not save 2. Initiate a shutdown from the GUI menu 3. The application will prompt you save because it's being closed. Select "cancel" to abort the save and close. The file won't be saved and the application will not close. 4. After a few seconds, the computer will immediately shut down, losing your document changes. This means that when a shutdown is initiated, there's nothing the user can do to abort the shutdown. What should have happened is that Ubuntu should have noticed that the shutdown was cancelled. That's how Windows and Mac works. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: shutdown ** Description changed: 1. Open a text editor of any kind and edit any document. Do not save 2. Initiate a shutdown from the GUI menu 3. The application will prompt you save because it's being closed. Select "cancel" to abort the save and close. The file won't be saved and the application will not close. 4. After a few seconds, the computer will immediately shut down, losing your document changes. This means that when a shutdown is initiated, there's nothing the user can do to abort the shutdown. + + What should have happened is that Ubuntu should have noticed that the + shutdown was cancelled. That's how Windows and Mac works. -- 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/1878956 Title: Shutdown continues even after cancelled by application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1878956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715188] Re: Artist / Album folder names not renamed after correcting ID3 tags (as Banshee does)
Well, this project seems to be dead. -- 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/1715188 Title: Artist / Album folder names not renamed after correcting ID3 tags (as Banshee does) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1715188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1310219] Re: Shutdown cannot be canceled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- 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/1310219 Title: Shutdown cannot be canceled To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310219/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750818] Re: Already installed deb packages not showing as installed when opened
** Changed in: snap-store Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: snap-store Status: New => Confirmed ** Changed in: snap-store Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1750818 Title: Already installed deb packages not showing as installed when opened To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1750818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
This affects me to. Brasero frezes while writing audio CD. Workaround alowed me to get stuck at cd-text part just as Paul said. I have to kill application to stop it. I have Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
@seb128: it's broken again in latest 3.36.0 release: Failed to load backend for 'application/pdf': libnss3.so: échec d'adressage (mapping) du segment de l'objet partagé -- 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/1869159 Title: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
** Changed in: accountsservice 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/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1832865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
** Changed in: accountsservice Status: New => Fix Released -- 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/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center crashes on setting up fingerprint
While g-c-c should probably not crash on errors, the main issue here is indeed that fprintd crashes, and given that the enroll UI is still something going to be deprecated so it's not worth to fix in here IMHO. What we do need to fix is libfprint, so moving the bug there instead. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu) Status: New => Triaged ** Changed in: libfprint (Ubuntu) Importance: Undecided => Low ** Changed in: libfprint (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint via https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/54 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #242 https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/242 ** Changed in: libfprint Remote watch: gitlab.freedesktop.org/libfprint/fprintd/-/issues #54 => gitlab.freedesktop.org/libfprint/libfprint/-/issues #242 -- 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/1878285 Title: gnome-control-center crashes on setting up fingerprint To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
I updated proposed mutter 3.36.2 and tried Libreoffice Calc sheet copy - paste, cut - paste in pretty much same way with the same pc I did at the time I reported the bug - only few times more. I did not run into error. I don't have any need for extensive copy - paste activity any time soon, so will not get any additional testing done. On Fri, 15 May 2020 at 16:25, Guillem Solivellas <1852...@bugs.launchpad.net> wrote: > I can tell you it's not. When using the cut-and-paste feature from > LibreOffice 8not first time..., the second and next...) you need to do the > copy action twice to get your string stored. > > > garrig...@gmail.com > > > Missatge de Adam Dingle del dia dv., 15 de maig 2020 a > les 6:26: > > > Hi Daniel - I'm the one who first reported this Launchpad bug back in > > November. :) I'm very happy to see that there is a proposed fix, since > > I (like many others) have continued to experience this bug on a daily > > basis for many months now. I appreciate your asking my opinion, though > > it certainly should not be the only one that counts here. > > > > I am running Focal (20.04) and I just installed the proposed > > 3.36.2-1ubuntu1~20.04.1 package. I'll need to run with it for a day or > > two before I'll have an opinion about whether the fix is adequate. Keep > > fingers crossed. :) > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1876445). > > https://bugs.launchpad.net/bugs/1852183 > > > > Title: > > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > > comment 93) > > > > Status in LibreOffice: > > Won't Fix > > Status in Mutter: > > Unknown > > Status in mutter package in Ubuntu: > > Fix Released > > Status in mutter source package in Eoan: > > Triaged > > Status in mutter source package in Focal: > > Fix Committed > > Status in mutter source package in Groovy: > > Fix Released > > > > Bug description: > > [ Impact ] > > > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > > > In this environment, copy/cut/paste often fails. Specifically, the > > paste command sometimes does not paste the text that was cut/copied > > most recently. Instead, it pastes text that was cut/copied at some > > prior time. > > > > [ Test case ] > > > > 1. Use use libreoffice writer/calc > > 2. Copy text around > > 3. Paste it and ensure it always work > > > > [ Regression potential ] > > > > Copy/paste won't work as expected, for non-text types > > > > - > > > > > > I use LibreOffice Writer a lot, and I now see this problem very often, > > i.e. many times every day. > > > > There is some discussion of the problem here: > > > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > > libreoffice-calc/ > > > > Several posters there say that they are also using Ubuntu 19.10. > > > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > > > https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 > > -Clipboard-Manager > > > > It seems like that could be related. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873686). > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > comment 93) > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > [ Test case ] > > 1. Use use libreoffice writer/calc > 2. Copy text around > 3. Paste it and ensure it always work > > [ Regression potential ] > > Copy/paste won't work as expected, for non-text types > > - > > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: >
[Bug 1878607] Re: gnome-system-monitor assert failure: ERROR:../src/load-graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (
Thank you for your bug report, the reports seem to be from armhf, could someone having the hardware and issue report it upstream to https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues ** Information type changed from Private to Public ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1878607 Title: gnome-system-monitor assert failure: ERROR:../src/load- graph.cpp:557:void net_scale(LoadGraph*, guint64, guint64): assertion failed: (new_max <= (coef10 * (G_GUINT64_CONSTANT(1) << (base10 * 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1878607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878933] [NEW] Lock screen ignores user input for a few seconds after "Please try again" message
Public bug reported: When I try to unlock my PC from the lock screen, I sometimes enter the wrong password. After checking the password (which takes ~1s), the lock screen displays the following message: "Sorry, that didn't work. Please try again." For ~2s after that, keyboard input is ignored, which means that if you start typing you password immediately after reading the "try again" prompt, the first few characters are discarded and your password is incorrect again. This is a bad user experience, and I'm not sure what the purpose of the delay is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 16:32:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-09 (96 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-10 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878933 Title: Lock screen ignores user input for a few seconds after "Please try again" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878933/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center crashes on setting up fingerprint
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878285 Title: gnome-control-center crashes on setting up fingerprint To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
This same problem started the first week of May with my IMAP+ AT "Error performing TLS handshake: ..." Ubuntu Mate 16 Evolution 3.18.5.2-0ubuntu3.2 Sending SMTP still works. Reading through the posts it's clear that it's a Yahoo issue since Yahoo manages AT, AOL, Verizon and Yahoo mail and those are the only ones affected. Why has no fix-update been created yet? It's not like people are so swamped with work they don't have time to. -- 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864307] Re: Many apps have no icon in Software on Focal
** Changed in: gnome-software (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878490] Re: Big delay between pressing the applications grid icon in dock and the start of the spring animation
Done, here is the settings.txt Oddly, while doing this I noticed that some extensions that I uninstalled long ago (even before upgrading to 20.04) where marked as active by gsettings. Pop-shell and cast-to-tv for example. I had to manually remove their entries using dconf. I will run in this configuration for a while and see if the bug is still present. ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878490/+attachment/5372134/+files/settings.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878490 Title: Big delay between pressing the applications grid icon in dock and the start of the spring animation To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878490/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864307] Re: Many apps have no icon in Software on Focal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864307 Title: Many apps have no icon in Software on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878670] Re: Gnome crash frequently
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority 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/1878670 Title: Gnome crash frequently To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
I can tell you it's not. When using the cut-and-paste feature from LibreOffice 8not first time..., the second and next...) you need to do the copy action twice to get your string stored. garrig...@gmail.com Missatge de Adam Dingle del dia dv., 15 de maig 2020 a les 6:26: > Hi Daniel - I'm the one who first reported this Launchpad bug back in > November. :) I'm very happy to see that there is a proposed fix, since > I (like many others) have continued to experience this bug on a daily > basis for many months now. I appreciate your asking my opinion, though > it certainly should not be the only one that counts here. > > I am running Focal (20.04) and I just installed the proposed > 3.36.2-1ubuntu1~20.04.1 package. I'll need to run with it for a day or > two before I'll have an opinion about whether the fix is adequate. Keep > fingers crossed. :) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1876445). > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > comment 93) > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > [ Test case ] > > 1. Use use libreoffice writer/calc > 2. Copy text around > 3. Paste it and ensure it always work > > [ Regression potential ] > > Copy/paste won't work as expected, for non-text types > > - > > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878912] [NEW] Gimp Crashed
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.4 (compiled against version 2.58.1) using GdkPixbuf version 2.40.0 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Abgebrochen Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fed836ed8c7] gimp-2.10(+0xd14a0)[0x56221a0334a0] gimp-2.10(+0xd18d8)[0x56221a0338d8] gimp-2.10(+0xd2037)[0x56221a034037] /lib/x86_64-linux-gnu/libpthread.so.0(+0x15540)[0x7fed82bfb540] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fed82a393eb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fed82a18899] /lib/x86_64-linux-gnu/libc.so.6(+0x25769)[0x7fed82a18769] /lib/x86_64-linux-gnu/libc.so.6(+0x37006)[0x7fed82a2a006] /lib/x86_64-linux-gnu/libX11.so.6(+0x3f493)[0x7fed828ee493] /lib/x86_64-linux-gnu/libX11.so.6(+0x3f53d)[0x7fed828ee53d] /lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5a)[0x7fed828ee83a] /lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fed828e0171] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5c3ef)[0x7fed837ae3ef] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d1)[0x7fed82daf4e1] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51a52)[0x7fed82dafa52] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7fed82dafe33] gimp-2.10(app_run+0x357)[0x56221a032cb7] gimp-2.10(main+0x395)[0x56221a0325b5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fed82a1a1e3] gimp-2.10(_start+0x2a)[0x56221a03273a] ``` ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1878912 Title: Gimp Crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1878912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878670] Re: Gnome crash frequently
Hi Kurt, I see you have a Ubuntu preload machine, we will try to see if we can reproduce your problem. Meanwhile, please upload more details by apport-collect as Daniel said. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1878670 Title: Gnome crash frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878906] [NEW] copy/paste (clipboard) is broken in Ubuntu 18.04
Public bug reported: Since 10 days copy/paste does not work as expected. As far as I have observed, the bug covers all applications, which are using system clipboard to copy and paste data. A very good example is the usage of LibreOffice Calc. You can copy some cells, which are marked with a blinking border, but you cannot paste the content otherwhere. Most of time, copying multiple times solves the problems, but that is not acceptable. Maybe, the root cause is identical to bug #1852183 ([X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Fri May 15 14:04:40 2020 InstallationDate: Installed on 2018-04-30 (745 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1878906 Title: copy/paste (clipboard) is broken in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878906/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876908] Re: Screen not locked after resume from suspend
I found the problem (and the solution ;)). It's actually the org.gnome.desktop.lockdown disable-lock-screen gesettings key that's been set to "true". No idea how it got set to "true" though because i never changed it, and it used to work before. Apparently, I'm not the only one in this case: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992 -- 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/1876908 Title: Screen not locked after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878838] Re: [nvidia] Black screen (wrong VT) upon login
With debug enabled, I restarted the computer and followed the same steps with workaround. Attached logs. ** Attachment added: "logs by 'journalctl -b 0'" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+attachment/5372016/+files/journaldebug.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
After doing manual dconf cleanup, I've been unable to reproduce the issue. That's since posting the previous comment, so a few days now. So I think I'll hold off on reporting this upstream for the time being, but I'll go ahead and do that if the problem still manifests itself. Thanks again, Daniel. -- 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/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I get the "Error performing TLS handshake: ..." message with Yahoo mail using IMAP or POP. My partner reports the same issue with AoL. -- 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878567] Re: gnome-software crashes with segmentation fault error
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-software (Ubuntu) Status: Confirmed => Incomplete -- 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/1878567 Title: gnome-software crashes with segmentation fault error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878567/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878838] Re: [nvidia] Black screen (wrong VT) upon login
Thank you for your bug report. Could you add your 'journalctl -b 0' log after triggering the issue? It would also be useful to get a log with debug enabled in /etc/gdm3/custom.conf ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878838] Re: Black screen (switched to wrong VT) upon login
Although the workaround is simple, this is a pretty serious bug for users who don't figure it out. ** Summary changed: - Black screen after Login + Black screen (switched to wrong VT) upon login ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Black screen (switched to wrong VT) upon login + [nvidia] Black screen (switched to wrong VT) upon login ** Summary changed: - [nvidia] Black screen (switched to wrong VT) upon login + [nvidia] Black screen (wrong VT) upon login ** Tags added: black-screen nvidia ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided => Medium -- 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/1878838 Title: [nvidia] Black screen (wrong VT) upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)
Sounds related to bug 1698083 -- 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/1837974 Title: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878718] Re: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable
** Summary changed: - Hotkey for switching display output unusable due to switching to next option immediately after release + HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable ** Package changed: mutter (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low ** Changed in: xorg-server (Ubuntu) Status: Incomplete => 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/1878718 Title: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
** Also affects: dbus (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-terminal (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-terminal (Ubuntu Bionic) Status: New => Invalid ** Changed in: dbus (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878838] [NEW] Black screen (switched to wrong VT) upon login
You have been subscribed to a public bug: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Black screen (switched to wrong VT) upon login https://bugs.launchpad.net/bugs/1878838 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 1878718] Re: Hotkey for switching display output unusable due to switching to next option immediately after release
The Super+P shortcut works! In the report, I used a dedicated fn key (situated on F1). With Super+P, the selection is confirmed when Super is released. That probably causes the bug when using the single fn key. -- 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/1878718 Title: Hotkey for switching display output unusable due to switching to next option immediately after release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()
or bug 1788429 -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)
Any "guestimate" about the solution? Thanks. -- 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/1837974 Title: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837974/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()
That sounds like bug 184 -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()
I don't know if this is related. It seems I always get a crash either when I start suspend or when I return from suspend. When I send the crash report launchpad don't open. The crash is in gnome-shell and the crash message is "gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()". It might be related to my installation and I will reinstall Focal later today. -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Description changed: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d + https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878777] Re: /usr/bin/gnome-shell:11:st_theme_node_lookup_length:st_theme_node_get_length:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function
*** This bug is a duplicate of bug 1871063 *** https://bugs.launchpad.net/bugs/1871063 ** This bug has been marked a duplicate of bug 1871063 gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() from st_theme_node_get_length() from ffi_call_unix64() -- 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/1878777 Title: /usr/bin/gnome- shell:11:st_theme_node_lookup_length:st_theme_node_get_length:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878781] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call_int
*** This bug is a duplicate of bug 1702151 *** https://bugs.launchpad.net/bugs/1702151 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878781 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call_int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878781/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760731] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from object_property_maybe_complete()
*** This bug is a duplicate of bug 1702151 *** https://bugs.launchpad.net/bugs/1702151 ** This bug has been marked a duplicate of bug 1702151 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() -- 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/1760731 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from object_property_maybe_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760731/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878781] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call_int
*** This bug is a duplicate of bug 1702151 *** https://bugs.launchpad.net/bugs/1702151 ** This bug has been marked a duplicate of bug 1702151 gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() -- 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/1878781 Title: /usr/bin/gnome- shell:11:g_type_check_instance_is_fundamentally_a:g_object_ref:st_theme_get_custom_stylesheets:ffi_call_unix64:ffi_call_int To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878781/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878777] [NEW] /usr/bin/gnome-shell:11:st_theme_node_lookup_length:st_theme_node_get_length:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function
*** This bug is a duplicate of bug 1871063 *** https://bugs.launchpad.net/bugs/1871063 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.1-5ubuntu2, the problem page at https://errors.ubuntu.com/problem/66cc3c6b0baf1cf6e4b51a794546b929809bacf4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878777 Title: /usr/bin/gnome- shell:11:st_theme_node_lookup_length:st_theme_node_get_length:ffi_call_unix64:ffi_call_int:gjs_invoke_c_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871063] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() from st_theme_node_get_length() from ffi_call_unix64()
Confirmed and tracking in: https://errors.ubuntu.com/problem/66cc3c6b0baf1cf6e4b51a794546b929809bacf4 ** Summary changed: - gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() + gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() from st_theme_node_get_length() from ffi_call_unix64() ** Description changed: + https://errors.ubuntu.com/problem/66cc3c6b0baf1cf6e4b51a794546b929809bacf4 + + --- + This is all the information I was able to gather. GS crashed right after pressing Win+L on a bluetooth keyboard. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 6 11:14:17 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-10-29 (524 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: - Segfault happened at: 0x7f3d04d6996d : mov(%rax),%rdi - PC (0x7f3d04d6996d) ok - source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region (needed readable region)! - destination "%rdi" ok + Segfault happened at: 0x7f3d04d6996d : mov(%rax),%rdi + PC (0x7f3d04d6996d) ok + source "(%rax)" (0xff0082c9ff0082c9) not located in a known VMA region (needed readable region)! + destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so - st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so - () at /usr/lib/x86_64-linux-gnu/libffi.so.7 - () at /usr/lib/x86_64-linux-gnu/libffi.so.7 - () at /usr/lib/libgjs.so.0 + st_theme_node_lookup_length () at /usr/lib/gnome-shell/libst-1.0.so + st_theme_node_get_length () at /usr/lib/gnome-shell/libst-1.0.so + () at /usr/lib/x86_64-linux-gnu/libffi.so.7 + () at /usr/lib/x86_64-linux-gnu/libffi.so.7 + () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() UpgradeStatus: Upgraded to focal on 2020-03-27 (9 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo separator: ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1871063 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_length() from st_theme_node_get_length() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871063/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878564] Re: GIMP 2.10.18 stack trace
This old description was multiple lines in bug search:
``` GNU Image Manipulation Program version 2.10.18 git-describe:
GIMP_2_10_16-38-gde7f04567d 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/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnuConfigured with: ../src/configure -v
--with-pkgversion='Ubuntu 9.3.0-8ubuntu1' --with-
bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-
languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-9 --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-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib=auto
--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,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnuThread model: posix
gcc version 9.3.0 (Ubuntu 9.3.0-8ubuntu1) # Libraries # using babl
version 0.1.74 (compiled against version 0.1.74) using GEGL version
0.4.22 (compiled against version 0.4.22) using GLib version 2.64.2
(compiled against version 2.64.1) using GdkPixbuf version 2.40.0
(compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled
against version 2.24.32) using Pango version 1.44.7 (compiled against
version 1.44.7) using Fontconfig version 2.13.1 (compiled against
version 2.13.1) using Cairo version 1.16.0 (compiled against version
1.16.0) ``` > GIMP-CRITICAL: _gimp_wire_read_int8: assertion 'count >=
0' failed Stack trace: ``` # Stack traces obtained from PID 56984 -
Thread 56984 # [New LWP 56987] [New LWP 56988] [New LWP 56989] [New LWP
56990] [New LWP 56991] [New LWP 56992] [New LWP 56993] [New LWP 56994]
[New LWP 56995] [New LWP 56998] [New LWP 56999] [New LWP 57228] [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=0x7ffe58be0370, fd=76) at ../sysdeps/unix/sysv/linux/read.c:26 Id
Target Id Frame * 1Thread
0x7fedf2b12340 (LWP 56984) "gimp-2.10" __libc_read (nbytes=256,
buf=0x7ffe58be0370, fd=76) at ../sysdeps/unix/sysv/linux/read.c:26 2
Thread 0x7fedf1b23700 (LWP 56987) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread
0x7fedf1322700 (LWP 56988) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread
0x7fedf0b21700 (LWP 56989) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread
0x7fedf0320700 (LWP 56990) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread
0x7fedefb1f700 (LWP 56991) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread
0x7fedef31e700 (LWP 56992) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread
0x7fedeeb1d700 (LWP 56993) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread
0x7fedecb41700 (LWP 56994) "gmain" 0x7fedf394996f in
__GI___poll (fds=0x558ecabddc50, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7fedc700 (LWP
56995) "gdbus" 0x7fedf394996f in __GI___poll
(fds=0x558ecabf5de0, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7fedc253e700 (LWP
56998) "gimp-2.10" futex_wait_cancelable (private=,
expected=0, futex_word=0x558ecadeda78) at ../sysdeps/nptl/futex-
internal.h:183 12 Thread 0x7fedc1d3d700 (LWP 56999) "async"
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 13
Thread 0x7fedb9293700 (LWP 57228) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 13 (Thread
0x7fedb9293700 (LWP 57228)): #0 syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No locals. #1
0x7fedf3c3f483 in g_cond_wait () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0 No symbol table info available. #2
0x7fedf413faad in ?? () from /lib/x86_64-linux-gnu/libgegl-0.4.so.0
No symbol table info available. #3 0x7fedf3c1b931 in ?? () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available.
#4 0x7fedf3a2f609 in start_thread (arg=) at
pthread_create.c:477 ret = pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf =
{140658990462720, 3262827062763670837, 140730387263950, 140730387263951,
140730387264096,
[Bug 1878775] [NEW] gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1878775 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878776] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_ti
** Summary changed: - /usr/bin/gnome-shell:11:g_type_check_instance:g_signal_connect_data:meta_window_ensure_close_dialog:meta_window_set_alive:meta_display_ping_timeout + gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() ** Tags removed: artful cosmic disco -- 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/1878776 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878775] Re: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_s
** Summary changed: - /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session + gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_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/1878775 Title: gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter
*** This bug is a duplicate of bug 1843982 *** https://bugs.launchpad.net/bugs/1843982 It's not a regression. It is in fact the same bug happening one last time. I just explained it in the other bug, hope that's clear. (If I'm not understanding right, please un-dupe and re-open this bug.) ** This bug has been marked a duplicate of bug 1843982 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() -- 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/1878611 Title: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1878611/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878776] [NEW] gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1~20.04.1, the problem page at https://errors.ubuntu.com/problem/124f859bf032d7ff89d6cc900eebf3dbda6716a2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic eoan focal groovy -- 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/1878776 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance() from g_signal_connect_data() from meta_window_ensure_close_dialog() from meta_window_set_alive() from meta_display_ping_timeout() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2584 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2584 ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2541 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #2584 -- 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/1868440 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()
The upstream bug claims to have the same root cause as Ubuntu bug 1868440 so it sounds like it's fixed in that case. ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2541 => None ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2596 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2596 ** Changed in: gnome-shell Remote watch: None => gitlab.gnome.org/GNOME/gnome-shell/-/issues #2596 ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-shell (Ubuntu Focal) Status: New => Fix Committed -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I have a similar problem, but it involves headphones rather than Bluetooth -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877553] Re: wifi gets automatically disabled when screen is locked and can be enabled only after a reboot.
I am talking about a physical switch or key on the laptop. That shouldn't be possible to automatically revert. Tap the wifi key on the laptop and then the toggle switch in gnome-shell should work. Even if it doesn't, when 'rfkill' shows 'HARD' = 'blocked' then that's a hardware problem and we can't solve it in gnome-shell. Although it *might* be a kernel bug after that. More likely you just need to press the wifi key on your keyboard and then also turn it on inside gnome-shell. -- 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/1877553 Title: wifi gets automatically disabled when screen is locked and can be enabled only after a reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877553] Re: wifi gets automatically disabled when screen is locked and can be enabled only after a reboot.
The toggle switch isn't working too, it automatically reverts back to disabled mode if you try to enable it. -- 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/1877553 Title: wifi gets automatically disabled when screen is locked and can be enabled only after a reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
