[Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
I've also encountered this bug/crash since I always change the cursor to DMZ-White when I install Ubuntu and I reckon other ex-Windows users might also do. Before that I've noticed this weird "X" cursor when desktop was loading (see attachement). I've replicated the bug using only the live USB (try without installing Ubuntu 24.04). Just apt install gnome-tweaks and then change cursor to DMZ-White leads to crashing. Re-tried by first installing Nvidia drivers with no difference. ** Attachment added: "IMG_20240426_131608.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+attachment/5772389/+files/IMG_20240426_131608.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2062377/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation
** Changed in: subiquity Importance: Undecided => Medium ** Changed in: curtin Status: New => Triaged ** Changed in: curtin Importance: Undecided => Medium -- 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/1881932 Title: subiquity isn't able to create btrfs subvolumes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1881932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881932] Re: subiquity isn't able to create btrfs subvolumes during installation
@Jonas - please don't knowingly create duplicates. -- 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/1881932 Title: subiquity isn't able to create btrfs subvolumes during installation To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1881932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2059187] [NEW] fails in autopkgtest on gnome-desktop-testing
Public bug reported: flatpak fails autopkgtest like so: 1125s Updating appstream branch 1125s Updating summary 1125s ok app with mismatched metadata (in summary) can't be installed 1125s test-metadata-validation.sh:158 - app with mismatched metadata (in summary) can't be installed 1125s OK closing connection 1125s fusermount: entry for /tmp/test-flatpak-MPRPRX/runtime/doc not found in /etc/mtab 1125s PASS: Flatpak/test-metadata-validation.sh.test 1125s SUMMARY: total=45; passed=38; skipped=0; failed=7; user=205.6s; system=150.8s; maxrss=423860 1125s FAIL: Flatpak/test-bun...@system.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/testlibrary.test (Child process killed by signal 6) 1125s FAIL: Flatpak/test-bun...@system-norevokefs.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,deltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system,nodeltas.wrap.test (Child process exited with code 1) 1125s FAIL: Flatpak/test-run@system-norevokefs,nodeltas.wrap.test (Child process exited with code 1) 1125s /tmp/autopkgtest.Kstx4F/wrapper.sh: Killing leaked background processes: 9343 1125s PID TTY STAT TIME COMMAND 1125s9343 ?S 0:00 /usr/bin/python3 /usr/libexec/installed-tests/Flatpak/web-server.py repos 1125s autopkgtest [07:37:45]: test gnome-desktop-testing: ---] 1126s autopkgtest [07:37:46]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - 1126s gnome-desktop-testing FAIL non-zero exit status 2 https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/f/flatpak/20240324_073939_33ef3@/log.gz ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/2059187 Title: fails in autopkgtest on gnome-desktop-testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2059187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Hi Kai-Heng, It looks like you're working on this through Salsa. The debdiffs on this bug mean that this shows in the sponsor queue, so I'm removing Ubuntu Sponsors from this bug since there looks like no action to take for Sponsors. Please re-subscribe Sponsors if you feel otherwise. Thanks! -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Other packages that have been tested and found to be impacted by this bug have been added. ** Also affects: angelfish (Ubuntu) Importance: Undecided Status: New ** Changed in: angelfish (Ubuntu) Status: New => Confirmed ** Also affects: privacybrowser (Ubuntu) Importance: Undecided Status: New ** Changed in: privacybrowser (Ubuntu) Status: New => Confirmed ** Also affects: notepadqq (Ubuntu) Importance: Undecided Status: New ** Changed in: notepadqq (Ubuntu) Status: New => Confirmed ** Also affects: cantor (Ubuntu) Importance: Undecided Status: New ** Changed in: cantor (Ubuntu) Status: New => Confirmed ** Also affects: pageedit (Ubuntu) Importance: Undecided Status: New ** Changed in: pageedit (Ubuntu) Status: New => Confirmed ** Also affects: rssguard (Ubuntu) Importance: Undecided Status: New ** Changed in: rssguard (Ubuntu) Status: New => Confirmed ** Also affects: konqueror (Ubuntu) Importance: Undecided Status: New ** Changed in: konqueror (Ubuntu) Status: New => Confirmed ** Also affects: kiwix (Ubuntu) Importance: Undecided Status: New ** Changed in: kiwix (Ubuntu) Status: New => Confirmed ** Also affects: kchmviewer (Ubuntu) Importance: Undecided Status: New ** Changed in: kchmviewer (Ubuntu) Status: New => Confirmed ** Also affects: goldendict-webengine (Ubuntu) Importance: Undecided Status: New ** Changed in: goldendict-webengine (Ubuntu) Status: New => Confirmed ** Also affects: opam (Ubuntu) Importance: Undecided Status: New ** Changed in: opam (Ubuntu) Status: New => Confirmed ** Also affects: akregator (Ubuntu) Importance: Undecided Status: New ** Changed in: akregator (Ubuntu) Status: New => Confirmed ** Also affects: kalgebra (Ubuntu) Importance: Undecided Status: New ** Changed in: kalgebra (Ubuntu) Status: New => Confirmed ** Also affects: qmapshack (Ubuntu) Importance: Undecided Status: New ** Changed in: qmapshack (Ubuntu) Status: New => Confirmed ** Also affects: supercollider (Ubuntu) Importance: Undecided Status: New ** Changed in: supercollider (Ubuntu) Status: New => Confirmed ** Also affects: tellico (Ubuntu) Importance: Undecided Status: New ** Changed in: tellico (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to devhelp in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041672] Re: glob in mime/packages/freedesktop.org.xml is matching wrong files
removing and sudo update-mime-database /usr/share/mime fixes the issue locally until the next update ** Summary changed: - glob in mime/packages/freedesktop.org.xml is matching wrong files + in mime/packages/freedesktop.org.xml is matching wrong files -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2041672 Title: in mime/packages/freedesktop.org.xml is matching wrong files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2041672] [NEW] glob in mime/packages/freedesktop.org.xml is matching wrong files
Public bug reported: /usr/share/mime/packages/freedesktop.org.xml line 10466 -> value="import Qt" offset="0:3000" context: is matching python files using Pyside with imports like: from PySide2.QtCore import Qt, QSettings, QSize considering them 'Qt Markup Language files (text/x-qml)' thus wrecking havoc down the line. Maybe just remove this match entry as it seems very broad ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: mime pyside pyside2 pyside6 python qt ** Summary changed: - glob in mime/packages/freedesktop.org.xml is matching wron files + glob in mime/packages/freedesktop.org.xml is matching wrong files -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/2041672 Title: glob in mime/packages/freedesktop.org.xml is matching wrong files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/2041672/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037569] Re: udev issues with mantic beta
Marking invalid in systemd, other than long-standing udev rules being involved I'm not sure this will be fixed in systemd. Exploring if libblockdev with the s390 plugin enabled helps. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Also affects: libblockdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
No, only one that even has gnome in the name is network-manager-gnome. I haven't had any freezing issue the last couple days, but will run and post the journal commands next time it happens. Still getting JS Error workspace is undefined and stack traces every time I exit "activities" if my mouse cursor is hovering over an application window on a monitor other than my primary display, and can't' update stage views actor any time I resize any application on any monitor, with the exception of using the application controls to maximize (not full screen). -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+attachment/5705142/+files/prevjournal.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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Daniel, Attached are the files from the two journal commands. I have 2 .crash files in /var/crash: _usr_bin_evolution.1000.crash _usr_bin_nm-connection-editor.1000.crash Is it worth doing the ubuntu-bug command on any/all of those? I do see 50 error reports at https://errors.ubuntu.com/user/ID. Clicking any of the "received" links says "Sorry, you are not a member of a group that is allowed to see the data from error reports. Please fill out this form to request access." Is it safe to post my whoopsie ID here for you to see the list? I do not have the symptoms of the workspace dots staying active as described in #2000644. I have had my system set to fixed, 10 workspaces since installation. There are no files in ~/.local/share/gnome-shell/extensions/ ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+attachment/5705141/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] [NEW] GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Public bug reported: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome jammy -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031172] Re: Please take a stand on "screen: Use clean env when creating new tab"
> it exposes a deficiency in the desktop > environment in that the WM/shell's environment contains necessary > env vars (e.g. ssh-agent variables) that are missing from the > systemd --user / d-bus activation environment -- 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/2031172 Title: Please take a stand on "screen: Use clean env when creating new tab" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2031172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013255] Re: changing screen brightness with keyboard hotkeys reacts very slow
No, wayland not affected. -- 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/2013255 Title: changing screen brightness with keyboard hotkeys reacts very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2013255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Thanks, uploaded! ** Changed in: openbox (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Thanks for the patch, Aaron. I'm able to reproduce this bug using the firefox f11 -> open link in new window, when using the live session of the daily-live lubuntu iso. And the attached patch does seem to help. Overall the patch is what I was hoping to see, but I will request some changes. * The Maintainer field currently reads "Maintainer: Lubuntu Developers". I'd like you to go with the more conventional "Ubuntu Developers" attribution. `seeded-in-ubuntu` says that openbox is also used in Ubuntu Mate, and of course people can use openbox otherwise. The `update-maintainer` script is a convenient way to set this field to the value I'm suggesting (when starting from the original value). * There is a sponsorship process listed on the wiki, I think https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue is a good summary. This can also help, in the future, find someone to take a look at the patch as doing so means your work show up in the queue. http://reports.qa.ubuntu.com/reports/sponsoring/ Since I'm already looking at this I won't demand the SponsorsQueue bug changes but please keep that in mind for the next one. * I forget where I saw it but I like the convention that the patch has a change number, like it looks like you're on v4 of the patch. So it might have been called glib_crash_bugfix-v4.patch or something. A nice convention for when these keep changing. * One item also mentioned on the wiki is forwarding this patch to Debian. It is likely that the same problem applies there. https://wiki.ubuntu.com/Debian/Bugs talks about this in detail. I will ask that you do this before upload. For this particular bug I'd feel comfortable sharing the patch with Debian without reproducing on Debian, since it's already known to be happening elsewhere. Just say so when forwarding. * A tweak to the changelog would be nice. It isn't necessary to note the update to the maintainer field, that will be the case for most if not all packages with an Ubuntu delta. Also, the first segment about the patch is in my opinion too developer focused. I'd probably start with "Cherry-pick patch from A for crash issue when B + C happens", fill in appropriate details you think might be interesting for someone who might not look at the code. So Maintainer + Debian + Changelog tweaks and I will be happy to upload. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2011751] Re: openbox crashed with SIGABRT
Partial review of the patch so far. I haven't read much openbox code so take this with a grain of salt. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c9 mentions a concern that itPrev may still be pointing to invalid data. I share this concern. I think some interesting testcases are what happens with lists that have one or two elements, which then are modified by this function. In the single element case, I believe your itPrev now points to the deleted item, and in the two element case, itPrev may be ok but itPrev->prev or itPrev->next are both probably not valid. https://bugzilla.icculus.org/show_bug.cgi?id=6669#c5 mentions a work branch. I suggest tracking that down and considering it. It's presumably this patch https://bugzilla.icculus.org/attachment.cgi?id=3646=diff. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2011751 Title: openbox crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Thanks for the report. > do you think this bug will be corrected soon ? or i change parent directory name of mountpoints ? Probably better off changing the parent directory name, I'm afraid. ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1979064] [NEW] Context menu shows again on other screen
Public bug reported: When I right-click an application from the Dock, the context-menu/dialog comes up with the different options, but when I click on one of them, for some reason, the context-menu/dialog appears one more time but in the left screen and when I click again in the context option in which I'm interested it works correctly. I have 2 screens, the secondary is on the left, and the dock is on the primary. Im gonna attach screenshots of the process. In the first image I bring the cursor near the Dock and it opens. In the second image I right-click on an application, Terminal in this case. After that I click on 'New Window'. In the third image the context-menu/dialog shows up again in the secondary screen. 1. Description:Ubuntu 22.04 LTS Release:22.04 2. gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5 Candidate: 72~ubuntu5 Version table: *** 72~ubuntu5 500 500 http://es.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status 3. I expected to execute the action, instead of opening the context menu again but on the left screen. 4. The context menu opened again, but on the left screen. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Three merged images reproducing the issue" https://bugs.launchpad.net/bugs/1979064/+attachment/5597959/+files/MergedImages.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1979064 Title: Context menu shows again on other screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1979064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970978] [NEW] On Save As dialog, any navigation operation (e.g. change to sub-folder) takes focus away from file name entry and instead switches to search
Public bug reported: Within "Save As" dialogs from any desktop application, all navigation operations, specifically the most common one of changing folders, switches focus away from the file name input, resulting in the search input box accepting keyboard input instead of the filename input box. This is extremely frustrating for a several reasons: 1. After navigating to the desired folder, typing the name for the file is instead captured by the search input box instead of the expected filename input box 2. The search input box does not even appear until key presses are received, making it even more surprising that the filename is not being altered and is instead the beginning of a search 3. Using the mouse to re-focus on the filename input box deselects the originally selected default file name text, causing the user to have to re-select everything 4. Re-selecting everything (see previous item) causes the default file name extension (which is excluded in the initial selection) to also be selected, requiring the user to think about what it was and to re-enter that extension as well 5. "Tab" key navigation takes an inordinate number of tab key presses to return to the filename input box Sorry to complain about this, but I almost ALWAYS choose to change folders, and then when I type in the name, I have to re-do all the steps described above because the search input has invariably captured my key presses instead of the changing the filename. It is very annoying. I would like to suggest that the search input box either not be automatically switched to in the "Save As" mode of the dialog, or to have a separate and explicit search input box that does not automatically receive input after folder navigation operations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 11:06:32 2022 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2021-09-13 (227 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal save-as ** Description changed: Within "Save As" dialogs from any desktop application, all navigation operations, specifically the most common one of changing folders, switches focus away from the file name input, resulting in the search input box accepting keyboard input instead of the filename input box. This is extremely frustrating for a several reasons: 1. After navigating to the desired folder, typing the name for the file is instead captured by the search input box instead of the expected filename input box 2. The search input box does not even appear until key presses are received, making it even more surprising that the filename is not being altered and is instead the beginning of a search 3. Using the mouse to re-focus on the filename input box deselects the originally selected default file name text, causing the user to have to re-select everything - 4. Re-selecting everything (see #2 above) causes the default file name + 4. Re-selecting everything (see #3 above) causes the default file name extension (which is excluded in the initial selection) to also be selected, requiring the user to think about what it was and to re-enter that extension as well 5. "Tab" key navigation takes an inordinate number of tab key presses to return to the filename input box Sorry to complain about this, but I almost ALWAYS choose to change folders, and then when I type in the name, I have to re-do all 4 steps described above because the search input has invariably captured my key presses instead of the changing the filename. It is very annoying. I would like to suggest that the search input box either not be automatically switched to in the "Save As" mode of the dialog, or to have a separate and explicit search input box that does not automatically receive input on folder navigation operations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 11:06:32 2022 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2021-09-13 (227 days ago)
[Bug 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Hello, Thank you for your feedback. I hope we will have a solution, which we can deploy across our entire fleet. I thank you and wish you good luck. Thank you for your work on this bug. -- 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/1948008 Title: Copying and pasting files between desktop and Nautilus does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Any news ? :'( -- 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/1948008 Title: Copying and pasting files between desktop and Nautilus does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Oh dear, do you have a vision to know if the fix is on? Do you have any idea if there will be one? Because there are many of us who are affected by this problem. And we have just switched our park to 20.04 :/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting files between desktop and Nautilus does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948008] Re: Copying and pasting files between desktop and Nautilus does not work
Hi, We have a lot of computer using Ubuntu 20.04, in all of them, we can't copy/paste between Desktop and Nautilus, Focal is impacted, when we will have a fix ? a patch ? please ? We need to deploy it on all the computers in emergency. Thank you in advance for your help. -- 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/1948008 Title: Copying and pasting files between desktop and Nautilus does not work To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1948008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956059] [NEW] Backport gspawn fixes to impish
Public bug reported: A few changes for gspawn landed in the 2.67 series that had some bugs which were later fixed and backported to 2.70 as seen in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs are present in 2.68 as on impish, but that series won't see any more updates upstream. Currently this is causing a bug in the OSTree test suite as seen in https://github.com/ostreedev/ostree/issues/2495 with https://github.com/ostreedev/ostree/issues/2495#issuecomment-1000247260 confirming from glib's maintainer that these bugs are likely the issue. Attached is a debdiff with the 3 patches that were backported to 2.70. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Debdiff for 3 gspawn backport patches" https://bugs.launchpad.net/bugs/1956059/+attachment/5550436/+files/glib2.0_2.68.4-1ubuntu2.diff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956059 Title: Backport gspawn fixes to impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
possibly continued at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4759#register-pane ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4759 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4759 -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1285783] Re: Right panel has a transparent background
** Changed in: trusty-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1285783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326741] Re: Update GIMP to version 2.4.7 in hardy-backports
** Changed in: hardy-backports Status: New => Won't Fix -- 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/326741 Title: Update GIMP to version 2.4.7 in hardy-backports To manage notifications about this bug go to: https://bugs.launchpad.net/gutsy-backports/+bug/326741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 151207] Re: Error when trying to open a .wmf file, should use Gimp
** Changed in: hardy-backports Status: New => Won't Fix -- 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/151207 Title: Error when trying to open a .wmf file, should use Gimp To manage notifications about this bug go to: https://bugs.launchpad.net/hardy-backports/+bug/151207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 865907] Re: Please backport tracker to Oneiric
** Changed in: oneiric-backports Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/865907 Title: Please backport tracker to Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/oneiric-backports/+bug/865907/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945900] Re: icons in app launcher subfolders are too small
I did that and it did seem to fix the problem. I re-enabled Ubuntu Dock and it still is fixed though, so I'm not sure what that means. -- 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/1945900 Title: icons in app launcher subfolders are too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945900] [NEW] icons in app launcher subfolders are too small
Public bug reported: Relatively fresh install just after installing updates and a few pieces of software. Not sure what other info is needed other than all the info in the attachment but let me know if there is anything else. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 11:12:59 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-10-03 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Screenshot from 2021-10-03 11-12-38.png" https://bugs.launchpad.net/bugs/1945900/+attachment/5530276/+files/Screenshot%20from%202021-10-03%2011-12-38.png -- 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/1945900 Title: icons in app launcher subfolders are too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1945900/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721401] Re: eog fails to open png: Failed to register: Timeout was reached
Just for reference, i ran into this problem once again tonight (2021-07-30) on one of my xubuntu 20.04 systems. In this particular case it was due to running another copy of eog under gdb (which somehow made it out-of-reach to killall, and which i had forgotten about). I don't think this is what happened on 2021-05-25, because i didn't have the need to really hack into eog at that time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1721401 Title: eog fails to open png: Failed to register: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1721401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
please reopen if this is still an issue for systemd ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1699360 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Won't Fix -- 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/1676977 Title: Login prompt never presented with ldap login and ldapi set with a name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Trusty) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
> This should fix the problem: https://github.com/lxc/distrobuilder/pull/476 wow...all those 'fixes' lxd is adding look like things will continue to break in bad ways, like this bug. ouch. -- 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721401] Re: eog fails to open png: Failed to register: Timeout was reached
I have this problem as well, and it just started tonight (2021-05-25) on my xubuntu 20.04 system. I have another xubuntu 20.04 machine on which the problem does not occur. So, this may be transient, or mostly unrelated to eog. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1721401 Title: eog fails to open png: Failed to register: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1721401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926216] [NEW] drag and select does not work correctly on one monitor
Public bug reported: 1) hirsute hippo 2) 3.38.4-1ubuntu2 3) Being able to properly select the icons I have on one of my two monitors 4) On one of the monitors, drag and select works correctly, on the second one, however, it has a weird behaviour of selecting an incorrect area as seen in the video attached https://youtu.be/nC6pIn6uKgc ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 23:54:29 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1926216 Title: drag and select does not work correctly on one monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926216/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
I'm marking this invalid for systemd (the patch there was reverted) and fix released for plymouth, with the assumption this was fixed with the patch for bug 1817738. If anyone is able to reproduce the problem please add a comment. -- 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/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
Unfortunately I can't reproduce this bug, even with the 0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2. Also note that the [test case] in the description is wrong, that would be correct with the systemd change made earlier, but that change was reverted upstream and in ubuntu, so the test case steps aren't an accurate indication that the bug is fixed or not. Anyone on this bug able to reproduce the main problem, of key output (e.g. passwords) being printed on the console and visible between login sessions, and/or during shutdown? If not, I think we should consider this bug fixed. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Fix Released -- 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/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
As suggested in the freedesktop bug, this probably was fixed with the patch added for bug 1817738 which is this commit: https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/85d843af843589ce8538a59e5cb665b8253e380d I haven't been able to reproduce this myself yet (when using the plymouth version previous to that fix), but I'll try a few more times next week. -- 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/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1921651] [NEW] colon in name causes gvfs hang when copying to phone
Public bug reported: A colon in a file or directory name causes the operation to hang when copying to a phone via ptp. To reproduce: On android phone: 1) plug usb cable between phone and computer 2) Go to settings. Search for USB. Click on "Standard USB configuration". (Alternately, notice mystery status card at very bottom of notifications saying "Android system - charging over USB, click for options", and click on it.) 3) Select PTP. Then on Ubuntu 20.04 (and probably other recent vintages as well): 0) observe your phone popping up in dock and in Files 1) cp good.mp3 bad:.mp3 2) xdg-open . 3) In dock or Files, also open your phone 4) drag good.mp3 to your phone, note that it succeeds 5) drag bad:.mpd to your phone, note that it hangs ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 28 15:28:32 2021 InstallationDate: Installed on 2020-10-17 (162 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1921651 Title: colon in name causes gvfs hang when copying to phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1921651] Re: colon in name causes gvfs hang when copying to phone
Also: if the colon is in the name of a directory you are copying, the directory gets created with the colon in the name, but any attempt to put files in it hangs. Deleting the colon-named things via Files does seem to work, though. And transferring files with spaces, dashes, and umlauts in the names works fine, too. It's just the colon that causes trouble. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1921651 Title: colon in name causes gvfs hang when copying to phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1921651/+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
** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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 1685754] Re: 'systemd --user' unduly forces umask=0022
** Description changed:
+ [impact]
+
+ pam_umask, from /etc/passwd, is not honored in systemd --user instances
+
+ [test case]
+
+ on a desktop system, edit /etc/passwd to change the test user entry
+ (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
+ field). For example change:
+
+ ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash
+
+ to:
+
+ ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash
+
+ You may need to reboot for your X session to pick up the change.
+
+ Then, from the graphical desktop, open a terminal and run:
+
+ $ gnome-terminal -e sh
+
+ in the opened terminal, run:
+
+ $ umask
+
+ the number shown should be 0007, as set in the passwd file
+
+ [regression potential]
+
+ any regression would likely result in an incorrect umask for the user
+ whose passwd entry is modified.
+
+ [scope]
+
+ this is needed only for b
+
+ this is fixed in systemd upstream by commit
+ 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
+ v246, so this is fixed in g and later. This commit was also picked up by
+ Debian and included in the v245 release for focal, so this is fixed in
+ focal already.
+
+ [original description]
+
In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.
That is BAD, and is a security issue.
-
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
- umask "${UMASK#$USER:*,umask=}"
+ umask "${UMASK#$USER:*,umask=}"
fi
-
- In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
+ In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
+ unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-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 1685754] Re: 'systemd --user' unduly forces umask=0022
> REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy Gorilla), the issue had reappeared I just tested with groovy and can't reproduce the issue; umask is correct under gnome-terminal -- 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 1916319] Re: Excessive number of disparate fonts bundled together
Oy. Debian's ticketing system is the most archaic and arcane I've seen in the past 20 years. But after jumping through the hoops several times, here it is, (along with my email in clear for all to spam) - https://bugs.debian.org/983291 ** Bug watch added: Debian Bug tracker #983291 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983291 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1916319 Title: Excessive number of disparate fonts bundled together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1916319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916319] [NEW] Excessive number of disparate fonts bundled together
Public bug reported: The package `fonts-noto-core` contains 150+ highly exotic fonts, including cuneiform and hieroglyphics. These are high-quality but for all practical intents and purposes, never needed all at once, not even by a PhD in linguistics. 99%+ of the users will need only one language out of those. This sheer number of fonts clutters font selectors in applications, causing some to freeze[1], and the users to waste time hunting for the fonts they actually care about. Removing these fonts is an option, but it unnecessarily wastes the time of most users[2] (who use English[3]), is in some cases impossible[4], and far from simple. The question of how to remove unwanted fonts in Ubuntu has come again and again: * https://superuser.com/questions/248844/how-do-you-remove-fonts-from-ubuntu * https://askubuntu.com/questions/820746/remove-unused-fonts * https://askubuntu.com/questions/371213/how-to-delete-fonts-in-ubuntu * https://askubuntu.com/questions/1239037/removing-all-unnecessary-fonts-from-system * https://askubuntu.com/questions/978995/is-there-a-simple-way-for-uninstalling-fonts * https://forums.linuxmint.com/viewtopic.php?t=259109 * https://forums.linuxmint.com/viewtopic.php?t=297573 * https://forums.linuxmint.com/viewtopic.php?t=279672 * https://forums.linuxmint.com/viewtopic.php?f=29=339442 * https://askubuntu.com/questions/214950/how-can-i-remove-fonts-that-i-never-use-from-libreoffice-and-linux-in-general Removing some font packages solves part of the problem, but since `fonts-noto-core` bundles so many fonts together, users have no way of removing unwanted fonts from it. Can this package be broken up? An easy option, which I believe would cover 80% of the cases with far less than 20% of the effort, would be Latin vs. non-Latin. [1]: https://www.kubuntuforums.net/showthread.php/77868-How-can-we-reduce-the-crapton-of-fonts-installed-by-default [2]: https://discourse.ubuntu.com/t/excessive-fonts-installed-by-default/20924/5?u=dandv [3]: https://ubuntu.com/desktop/statistics [4]: https://bugs.kde.org/show_bug.cgi?id=433215 ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1916319 Title: Excessive number of disparate fonts bundled together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1916319/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Daniel, To be honest, I'm not quite sure what this ticket is all about. If it's just that people see these lines in their log, then surely, it's not worth having an open ticket about. On the other hand, I'm saying that I have been investigating this for two weeks, and I can say with 95% confidence that when my laptop freezes, the very last thing I see in my syslog, and in journalctl is a spam output of these lines. If you do a search for "keysym, ubuntu, freeze, dell, laptop", I'm pretty sure you'll be down a rabbit hole with many other people reporting similar freezes (e.g. https://itectec.com/ubuntu/ubuntu- ubuntu-19-04-stops-working/). There's also an issue in gnome/mutter that looks like it may be closer to the origin, but I'm not sure at this point (https://gitlab.gnome.org/GNOME/mutter/-/issues/606). Again, I'm just not sure. So, other than opening a vague ticket, do you have any suggestions as to where I can track this bug to the origin. Like I said, it's really killing our company's experience (we've got several new laptops running 20.04.1 LTS and none of us are using these machines for simple browsing -- in other words, it's critical that our work is not randomly lost due to a freeze). Also, note, I noticed this bug only once with the oem kernel (whereas it happened multiple times with the generic kernel). And also, I caught it once when I was explicitly looking for it to happen when I did a key press of one of the multimedia buttons (two key presses). ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #606 https://gitlab.gnome.org/GNOME/mutter/-/issues/606 -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
This is pretty nasty. I'm on a Dell laptop, running an oem kernel, with 20.04.1 lts, and some oem firmware for the nvidia prime tool. Anyway, a few times a day, the laptop freezes up, no hid available. When I reboot by powering down (only thing that works, not even ssh), I look into my logs, and always the last thing I see are these pesky lines. ``` gnome-shell[2261]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). ... ``` Not sure what this means, but I'm pretty sure its screwing up my experience with Ubuntu on dell laptop. -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1911655] [NEW] Can't enter period if one already exists
Public bug reported: I've pasted a number withe decimals in Calculator, and I want to calculate 1.5 minus that number, so I press Home, then start typing "1.5". That stops after "1". My input looks like this, where "|" is the cursor: 0.230179408 |0.230179408 1|0.230179408 At that point, I can't type the decimal point. I have to type "-", then arrow left, then the decimal point. ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1911655 Title: Can't enter period if one already exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1911655/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766938] Re: gnome-shell crashed in standard_pict_format_for_depth()
I no longer have access to the system in question, and haven't seen it anywhere else, may as well close as abandoned. -- 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/1766938 Title: gnome-shell crashed in standard_pict_format_for_depth() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
autopkgtests pass for bionic for all archs, except once for i386, for which I opened bug 1902554; the i386 test passed on retry. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
autopkgtests pass for focal for all archs (except i386 which is expected to fail for focal) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
Yes - "after login" means after I have successfully entered my password. Also, I have not been able to locate the 'Ubuntu on Wayland' selection. -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901342] Re: Xorg freeze on Intel Core 2 T5800
Attached prevboot.txt as instructed. Thanks for your assistance. ** Attachment added: "Output of 'journalctl -b-1 > prevboot.txt'" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901342/+attachment/5427638/+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/1901342 Title: Xorg freeze on Intel Core 2 T5800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1901342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
ble success rates. ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Description changed: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] - check systemd autopkgtest history + check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] - this is needed for x, b, and f. + for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** Merge proposal linked: https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/392373 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1860374] Re: External Editor plugin does not open external editor
The deficit here is not the action, but rather that the action is not documented in any way except in the source. >From the source there are two ways to open the editor, either by setting the "Automatically launch when a new mail is edited" option and then pressing any key in the Evolution editor, or by pressing Shift-Ctrl-E with or without that option set. ** Changed in: evolution (Ubuntu) Status: New => Invalid -- 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/1860374 Title: External Editor plugin does not open external editor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860374/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
ok, very sorry for my delay in looking at this. a quick scan of the results for x/b/f show: ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r xenial -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:53:00.893145-04:00' 88: boot-smoke FAIL non-zero exit status 1 (amd64:87 arm64:1) 39: systemd-fsckdFAIL non-zero exit status 1 (amd64:39) 47: boot-and-servicesFAIL non-zero exit status 1 (amd64:41 arm64:6) ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r bionic -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:53:18.194358-04:00' 132: systemd-fsckdFAIL non-zero exit status 1 (i386:14 amd64:117 ppc64el:1) 15: upstream FAIL non-zero exit status 1 (i386:3 amd64:10 ppc64el:1 arm64:1) 29: boot-smoke FAIL non-zero exit status 1 (i386:2 amd64:27) ddstreet@smaug:~$ autopkgtest-manager --distro systemd -a all -r focal -cv --since 2month --minimum 6 parsed '2month' as '2020-08-09T14:56:04.065710-04:00' 96: systemd-fsckdFAIL non-zero exit status 137 (amd64:68 ppc64el:20 s390x:8) 21: systemd-fsckdFAIL non-zero exit status 1 (amd64:1 ppc64el:4 s390x:16) I think the systemd-fsckd failures are issues with how the test is trying to detect 'good' and 'bad' service status, but in any case i rewrote some of the details of how the test works to be simpler and (hopefully) more accurate/reliable, I'm running it through tests from my ppa now, before I upload the test change. I'll take a look at the other test failures; the boot-and-services test has typically had a lot of trouble with services randomly not starting ok, but i'll check on the details. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896756] Re: tracker* startup is defined multiple times
** Package changed: systemd (Ubuntu) => tracker (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896756 Title: tracker* startup is defined multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
hi @cpaelzer, sorry i missed reading this earlier, i'll give all the test failures a look to see what can be done. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] Re: Notifications are pointlessly truncated even on ultrawide monitors
apport information ** Tags added: apport-collected focal ** Description changed: I tried to use ubuntu-bug -w to identify the component for this bug by clicking on a notification, but it failed with "xprop failed to determine process ID of the window". Sorry. - The bug is that notifications of adding/removing icons to Favorites in - the taskbar, are truncated for no good reason. I have a dual monitor - setup ridiculous amounts of horizontal space, yet the notification is - fixed size - which is fine, if it wrapped the text inside it. But it - doesn't. + The bug is that notifications of adding/removing icons to Favorites in the taskbar, are truncated for no good reason. I have a dual monitor setup ridiculous amounts of horizontal space, yet the notification is fixed size - which is fine, if it wrapped the text inside it. But it doesn't. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-11 (109 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405639/+files/Dependencies.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405640/+files/GsettingsChanges.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405642/+files/ProcEnviron.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405644/+files/monitors.xml.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405641/+files/ProcCpuinfoMinimal.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882023] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1882023/+attachment/5405643/+files/ShellJournal.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/1882023 Title: Notifications are pointlessly truncated even on ultrawide monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
N, please don't mark this as invalid. This is the most annoying notification on my wonderful Gnome desktop. It is so premature. First off, it thinks my MX Logitech keyboard is a mouse and secondly, it displays over and over long before the keyboard needs to be charged. I use this keyboard with 2 other operating systems and none of them have this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1850753] Re: Ubuntu 19.10 cannot set background to solid color
Looks like the removal of the solid background option was one dev's dictatorial and narrow-minded decision. What can I say. Enjoy open source. https://www.reddit.com/r/gnome/comments/dayto8/can_someone_point_me_to_the_train_of/ -- 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/1850753 Title: Ubuntu 19.10 cannot set background to solid color To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1850753/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery
A thousand thank yous. Disabling 'desktop icons' from the extensions app fixes this for me. Once disabled, even just the action of clicking on the toggle in the extensions app has the same effect, the desktop becomes unresponsive (though the mouse moves) for about 30 seconds, then finally the toggle redraws to show the extension is enabled. Totally repeatable, with them enabled, unlock takes forever, with them disabled, unlock is instant. This is 20.04 The 'Ubuntu Dock' extension is still enabled. -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
** Tags removed: ddstreet -- 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/1803993 Title: Password appears on the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
thanks Dan `killall -3 gnome-shell` keeps me sane. No longer need to reboot everyday. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
I'm seeing something very similar. Did a fresh install of 20.04 a week ago. After being logged in half a day things really start slowing down. Alt+Tab takes a few seconds to pop up, then you tab through to e.g. an open Calculator instance and that takes 8 seconds to come to the foreground. gnone-shell using 50% of one CPU. Have tried your suggestions to no avail. attaching the logs requested. journalctl shows a tone of javascript errors e.g. JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 $ sudo strace -c -p 7087 strace: Process 7087 attached ^Cstrace: Process 7087 detached % time seconds usecs/call callserrors syscall -- --- --- - - 34.730.215539 2 98592 sendmsg 23.990.148891 2 70929 36904 recvmsg 22.680.140739 2 68317 poll 16.420.101903 2 34030 writev 1.210.007527 4 1716 ioctl 0.460.002841 3 932 138 futex 0.250.001521 5 300 260 stat 0.100.000590 0 656 mprotect 0.060.000362 0 1165 write 0.040.000278 554 munmap 0.030.000205 0 305 getpid 0.010.89 0 383 read 0.000.22 113 timerfd_create 0.000.17 113 close 0.000.17 110 mmap 0.000.17 113 timerfd_settime 0.000.02 2 1 restart_syscall 0.000.00 0 2 getrusage -- --- --- - - 100.000.620560277431 37302 total Your journalctl command produced a 1.5Gb file. I have attached the last 100K lines. Let me know if you need more. ** Attachment added: "journal-tail.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393304/+files/journal-tail.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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
** Attachment added: "Screenshot from 2020-07-17 15-33-50.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393306/+files/Screenshot%20from%202020-07-17%2015-33-50.png -- 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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
lspci ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393305/+files/lspcik.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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
As I recall, in the many ubuntu installations I did, it was one where I put accountsservice on hold and then upgraded the system. Then, I run an apt-get upgrade instead of apt, or something similar, so the hold was not taken account of. I was afraid the PC would crash, but it did not, it however did freeze the computer a little bit, which still does not seem normal. The nvidia drivers had been installed previously. The two bugs you mentioned are clearly related or probably duplicate and, I may assume, they have yet to be properly fixed. Please let me know if I can help you further. Perhaps I could try to replicate the weird freezes (without crashed) that happen when accountsservice is being upgraded as: -I first install LightDM, activate it and then sudo apt upgrade, or -hold accountsservice, sudo apt upgrade all system, then unhold and sudo apt upgrade again Maybe a solution could lie at the journalctl of these two situations? If you think it is worth it, please tell me about nvidia drivers, should they be installed or not, or should I just use my laptop which has no nvidia on it? Indeed, this seems like a bug that can be avoided with a little experience, but a new or inexperienced ubuntu user could find it all too annoying and disrupting. -- 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/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1885452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
As I mentioned, I think the problem is not related to nvidia drivers. If I install nvidia drivers I have to do it by first disabling automatic log in at startup, otherwise I get a login loop after first reboot. If I disable automatic log in, then I do not get any crash when upgrading accountsservice. To sum up, accountsservice upgrade crashes only on 'GDM + login automatically'. On 'LightDM + login automatically', it stalls a bit but does not crash, while on 'GDM + disabled automatic login' it works perfectly. I installed ubuntu on an older laptop with no nvidia cards and the same problem appeared, otherwise I would not have reported this issue as it would have probably been related to a particular configuration, of my PC. Please let me know if you think I can try something else. Thanks! -- 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/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1885452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
I just reinstalled focal ubuntu with "log in automatically" checked and I recorded the journalctl and timed the error at approximately 14:31:54. I am attaching the log. The errors you saw previously such as (EE) NOUVEAU(0): [drm] failed to set drm interface version appear at 14:31:56 so after the screen has already crashed. some errors I see now are as follows: iul 01 14:31:54 daniel-System-Product-Name systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. - iul 01 14:31:54 daniel-System-Product-Name accounts-daemon[28222]: started daemon version 0.6.55 iul 01 14:31:54 daniel-System-Product-Name systemd[1]: Started Accounts Service. iul 01 14:31:54 daniel-System-Product-Name gnome-shell[1186]: GNOME Shell crashed with signal 11 - iul 01 14:31:54 daniel-System-Product-Name systemd[825]: gsd-keyboard.service: Main process exited, code=killed, status=11/SEGV iul 01 14:31:54 daniel-System-Product-Name systemd[825]: gsd-keyboard.service: Failed with result 'signal'. iul 01 14:31:54 daniel-System-Product-Name systemd[825]: Stopped target GNOME Keyboard handling. iul 01 14:31:54 daniel-System-Product-Name systemd[1]: gdm.service: Main process exited, code=killed, status=11/SEGV iul 01 14:31:54 daniel-System-Product-Name systemd-logind[685]: Session 1 logged out. Waiting for processes to exit. iul 01 14:31:54 daniel-System-Product-Name systemd[1]: gdm.service: Failed with result 'signal'. ** Attachment added: "latest_journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1885452/+attachment/5388728/+files/latest_journal.txt -- 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/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1885452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885452] Re: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install
The newest log has errors as you said at 14:54:52 and the last line of the log, probably when I saved it, reads 14:55:22. This means that between the time of errors and time of log saving 30 seconds passed, which seems correct as it is the amount of time it has taken me to ctrl- alt-f3, enter credentials and run command. I think it is fair to assume the errors that appeared at 14:54:52 are the ones that concern this bug. Please let me know if my line of reasoning seems correct. The errors indeed are related to gdm so they must be somehow linked to the crash. -- 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/1885452 Title: pc freezes and crashes during accountsservice upgrade on fresh ubuntu focal fossa install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1885452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885452] [NEW] pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install
Public bug reported: After a fresh install of Focal Fossa and running sudo apt update and sudo apt upgrade, when the upgrade reaches "setting up accountsservice" the PC freezes. After a reboot, the login screen did not appear anymore. This was reproducible on another computer (laptop). I reinstalled Ubuntu and put the package on hold. Later, I found that by installing and activating lightdm, this problem was remediated. Found this solution accidentally, while I was looking to correct login screen loops after I installed the nvidia drivers. This is unrelated, since the laptop does not have nvidia. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: accountsservice focal fossa lightdm -- 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/1885452 Title: pc freezes and crashes during accountservice upgrade on fresh ubuntu focal fossa install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1885452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871868] Re: Shell dialog text is truncated and ellipsized
I see a similar issue with the "Device not trusted yet" dialog when plugging in an iPhone. Is that the same bug? Please see the screenshot. ** Attachment added: "Device not trusted yet - text cut off, ellipsized" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+attachment/5387236/+files/Device%20not%20trusted%20yet%20text%20cut%20off.png -- 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/1871868 Title: Shell dialog text is truncated and ellipsized To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Whew, this is a long bug. So given comment 40 indicating part of this bug has been fixed in bug 1828639, and comment 42 indicating the any remaining patches should be sent to debian, it seems to me that the ubuntu-sponsors team does not need to be subscribed to this, as it's unclear what parts, if any of the attached patches still apply. Unsubscribing ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879776] Re: ubuntu 20 error mounting smb drive
fyi, this was an intentional upstream change, thanks @vtapia for pointing me to the upstream wiki: https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#SMB1_is_disabled_by_default -- 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/1879776 Title: ubuntu 20 error mounting smb drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1879776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Please push out a fix for this ASAP, once this tight loop is hit the machine becomes an unusable 100% CPU using mess. I know of several others suffering exactly the same bug. For me this can be reproduced by having a terminal using half the screen (using CMD+LEFT), then switching to fullscreen (F11) and back (F11). Repeating this some number of times triggers this tight loop of 100% CPU usage. After that, it's difficult to get window focus and windows are slow to respond to anything. To recover I use `killall -3 gnome-shell`, which allows Gnome to restart but then has the delightful affect of throwing windows around the screen randomly and forgetting there are multiple monitors. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1433774] Re: When double clicking an executable bash script in file manager, it opens in gedit rather than executing
Still an annoying problem in Ubuntu 20. -- 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/1433774 Title: When double clicking an executable bash script in file manager, it opens in gedit rather than executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880271] [NEW] -
Public bug reported: - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 07:59:11 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-21 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-23 (29 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880271 Title: - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880271/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center
@seb128: Maybe I didn't notice the search being this undiscoverable, or maybe I was using another theme that made it more obvious @amr: "just start typing" is not a discoverability UX hint. Users don't randomly start typing in dialogs without inputs. MAYBE the keyboard fanatics will try '?', but those use apt directly. IMO gnome-software should be as friendly as possible to people new to Ubuntu. -- 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/1878301 Title: Focal regression: poor discoverability for search in Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1878301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879016] Re: Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon
I have found a perfect reproducer; locking the screen (and so entering standby) reproduces this 100% of the time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1879016 Title: Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1879016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879016] [NEW] Crash with "Object .Gjs_AppIndicatorIconActor__1 ..." loss of Riot AppIndicator icon
Public bug reported: Sporadically, I see loss of the Riot-Desktop (https://github.com/vector- im/riot-web/ care of https://packages.riot.im/debian/) app indicator icon. This appears to be associated with the following log lines from `journalctl /usr/bin/gnome-shell` ``` May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 (0x55ec9dec3a00), has been already finalized. Impossible to set any property to it. May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for context 0x55ec9bc28340 == May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7fbed86c9340 @ 58) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #3 0x7ffd2838df70 b self-hosted:916 (0x7fbf1c1f12b8 @ 367) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #4 0x7ffd2838e060 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #5 0x55ec9c0c0c88 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7fbed86b6f78 @ 22) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #6 0x7ffd2838f3c0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #7 0x55ec9c0c0be0 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:219 (0x7fbed86b65e8 @ 225) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #8 0x7ffd28390720 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #9 0x55ec9c0c0b68 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/extension.js:61 (0x7fbed8688780 @ 37) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #10 0x55ec9c0c0aa8 i resource:///org/gnome/shell/ui/extensionSystem.js:83 (0x7fbf086592b8 @ 441) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #11 0x55ec9c0c0a28 i resource:///org/gnome/shell/ui/extensionSystem.js:354 (0x7fbf08659d58 @ 13) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #12 0x7ffd28391490 b self-hosted:251 (0x7fbf1c1c4ab0 @ 223) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #13 0x55ec9c0c09a8 i resource:///org/gnome/shell/ui/extensionSystem.js:353 (0x7fbf08659cd0 @ 64) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #14 0x55ec9c0c0928 i resource:///org/gnome/shell/ui/extensionSystem.js:371 (0x7fbf08659de0 @ 87) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #15 0x7ffd28392990 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fbf1c1d2230 @ 386) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #16 0x7ffd28393130 b resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7fbf083704d8 @ 254) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #17 0x7ffd28394520 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #18 0x55ec9c0c07e8 i resource:///org/gnome/shell/ui/sessionMode.js:167 (0x7fbf083702b8 @ 40) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #19 0x7ffd28395880 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube gnome-shell[1688]: Object .Gjs_AppIndicatorIconActor__1 (0x55ec9d075050), has been already finalized. Impossible to set any property to it. May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #20 0x55ec9c0c0740 i resource:///org/gnome/shell/ui/screenShield.js:1282 (0x7fbf08353a28 @ 188) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #21 0x7ffd28396be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #22 0x55ec9c0c0690 i resource:///org/gnome/shell/ui/screenShield.js:1331 (0x7fbf08353ab0 @ 391) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #23 0x7ffd28397f40 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fbf1c1b5de0 @ 71) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #24 0x55ec9c0c0610 i resource:///org/gnome/shell/ui/screenShield.js:854 (0x7fbf083519a0 @ 25) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: == Stack trace for context 0x55ec9bc28340 == May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #0 0x7ffd2838cb50 b resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7fbf1c1b5de0 @ 87) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #1 0x55ec9c0c0d10 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7fbed86c9340 @ 58) May 16 10:54:22 cube org.gnome.Shell.desktop[1688]: #2 0x7ffd2838deb0 b
[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 1878301] Re: Focal regression: poor discoverability for search in Ubuntu Software Center
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #986 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/986 -- 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/1878301 Title: Focal regression: poor discoverability for search in Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1878301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878301] [NEW] Focal regression: poor discoverability for search in Ubuntu Software Center
Public bug reported: I wanted to install a new package. Launched Ubuntu Software and... how do I search for anything? Search is a key function. It should be front and center. I couldn't see it. That was annoying enough that I wanted to file a bug against it. In the process I did notice the lens icon in the top left, but seriously - does that look easily discoverable to anyone? There's usually nothing in that cornerl so users don't look there, and the contrast is poor, which makes it very easy to not notice. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Poorly discoverable Search.png" https://bugs.launchpad.net/bugs/1878301/+attachment/5370677/+files/Poorly%20discoverable%20Search.png -- 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/1878301 Title: Focal regression: poor discoverability for search in Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875669] [NEW] autopkgtest failures
Public bug reported: [impact] gvfs autopkgtests are highly flaky and fail across different releases/archs for multiple different reasons. It's unclear if the failures are actual package bugs, or just testcase bugs. [test case] look at the autopkgtest results: http://autopkgtest.ubuntu.com/packages/gvfs [regression potential] TBD ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: seg sts-sponsor-volunteer ** Tags added: seg sts-sponsor-volunteer -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1875669 Title: autopkgtest failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1875669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798840] Re: Night Light is not functioning
Nightlight just stopped working on my ThinkPad X1C 7th gen with Ubuntu 18.04.4 too after the last updates. But on the other hand, the trackpad is now working again, yay. :-/ -- 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/1798840 Title: Night Light is not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
On Wed, Apr 22, 2020 at 02:53:48PM -, Jonathan Kamens wrote: > I understand that, but in this particular case we're talking about a > transition from a deb to a snap, not a snap update. Aha, apologies, I misread your previous comment. > Apparently there's special logic in update-manager to handle this, and > perhaps in do- release-upgrade as well, but I don't think either apt > nor snap auto- updates will handle this. There has been special logic in update-manager for other cases before, but this is not my area of expertise so I'll leave others to comment further. :) -- 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/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
On Wed, Apr 22, 2020 at 10:24:41AM -, Jonathan Kamens wrote:
> I'm a bit concerned about that, though, because the reason why I didn't
> get that update is because I pretty much exclusively use apt to do my
> updates, and apparently that's no longer sufficient to get all the
> updates needed on an Ubuntu system. I don't want to have to run the
> graphical update-manager to do updates. I know this is mostly off-topic
> here, but I don't suppose anyone knows whether there is a way to do the
> equivalent of what update-manager does, but from the command line?
Snaps are updated ("refreshed" in snap terms) automatically by snapd,
independent of the other update mechanisms for the system. If you run
`snap changes` after a system (with snaps installed, of course) has been
up for a few hours, you should see entries like:
ID Status Spawn Ready Summary
263 Doneyesterday at 17:53 EDT yesterday at 17:53 EDT Auto-refresh snap
"gtk-common-themes"
264 Donetoday at 03:03 EDT today at 03:04 EDT Auto-refresh snap
"lxd"
--
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/1861631
Title:
"The AppStream system cache was updated, but some components were
ignored. Refer to the verbose log for more information."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
