[Bug 1923845] Re: Please compress packages with zstd by default
** Bug watch added: Debian Bug tracker #878900 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900 ** Also affects: debian-el (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878900 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+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)
** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
Marking auto package testing as affected based on @paelzer's observation that it occurs only on Ubuntu's CI infra. I've also triggered the test with hello to see current status and for confirmation. ** Also affects: auto-package-testing Importance: Undecided Status: New -- 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 1923845] Re: Please compress packages with zstd by default
Debootstrap fix is merged in Debian: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New ** Also affects: aptly (Ubuntu) Importance: Undecided Status: New ** Also affects: boinc (Ubuntu) Importance: Undecided Status: New ** Also affects: busybox (Ubuntu) Importance: Undecided Status: New ** Also affects: cdebootstrap (Ubuntu) Importance: Undecided Status: New ** Also affects: cdist (Ubuntu) Importance: Undecided Status: New ** Also affects: debdelta (Ubuntu) Importance: Undecided Status: New ** Also affects: debian-el (Ubuntu) Importance: Undecided Status: New ** Also affects: debootstrap (Ubuntu) Importance: Undecided Status: New ** Also affects: debsigs (Ubuntu) Importance: Undecided Status: New ** Also affects: debsig-verify (Ubuntu) Importance: Undecided Status: New ** Also affects: diffoscope (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg-sig (Ubuntu) Importance: Undecided Status: New ** Also affects: file (Ubuntu) Importance: Undecided Status: New ** Also affects: libsolv (Ubuntu) Importance: Undecided Status: New ** Also affects: lintian (Ubuntu) Importance: Undecided Status: New ** Also affects: lutris (Ubuntu) Importance: Undecided Status: New ** Also affects: obs-build (Ubuntu) Importance: Undecided Status: New ** Also affects: osc (Ubuntu) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Also affects: radare2 (Ubuntu) Importance: Undecided Status: New ** Also affects: reprepro (Ubuntu) Importance: Undecided Status: New ** Also affects: vim-scripts (Ubuntu) Importance: Undecided Status: New ** Also affects: zeroinstall-injector (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Importance: Undecided => High ** Changed in: debootstrap (Ubuntu) Importance: Undecided => High ** Changed in: debootstrap (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846837] Re: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64
*** This bug is a duplicate of bug 1914044 *** https://bugs.launchpad.net/bugs/1914044 For the record 20.10 should be fixed already and the test packages referred to from the other bug should fix this problem. ** This bug has been marked a duplicate of bug 1914044 [SRU] gstreamer fails with "cannot allocate memory in static TLS block" error on aarch64 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: Totem and totem-video-thumbnailer in Ubuntu 20.04/20.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1846837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
** Also affects: wireshark (Ubuntu) Importance: Undecided Status: New -- 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/1916705 Title: glib2.0 >=2.67.3 breaks include from an extern C context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1916705/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1910994] [NEW] autopkgtest fails frequently in groovy on armhf
Public bug reported: https://autopkgtest.ubuntu.com/packages/s/snapd-glib/groovy/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/s/snapd- glib/20210110_213607_6d4d0@/log.gz ... Executing: snapd-glib/test-qt.test Test timed out after 300 seconds FAIL: snapd-glib/test-qt.test (Child process killed by signal 9) Running test: snapd-glib/test-markdown-qt.test # random seed: R02S8929c6fbcee911211dcbe25b8160bc06 1..13 # Start of markdown tests ... Reproduction in Canonistack with lxd shows no sigificant difference in run time when testing with and without glibc from -proposed. I assume the timeouts are results of the CI infrastructure running other tests in parallel on the same HW. ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse-groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1910994 Title: autopkgtest fails frequently in groovy on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1910994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1627564 Title: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1899179] [NEW] autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/ppc64el/x/xdg-desktop- portal/20200921_121654_3c330@/log.gz autopkgtest [12:16:41]: test gnome-desktop-testing: [--- Running test: xdg-desktop-portal/testdb.test # random seed: R02Sa8a2f882d5b075ef4489c354fb44d94b 1..3 # Start of db tests ok 1 /db/open ok 2 /db/serialize ok 3 /db/modify # End of db tests PASS: xdg-desktop-portal/testdb.test Running test: xdg-desktop-portal/test-doc-portal.test # random seed: R02S8cb58d429c0a974cbecf54d1746d684e outdir: /tmp/xdp-test-Q3WHR0 dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.portal.Documents' requested by ':1.0' (uid=1000 pid=1200 comm="/usr/libexec/installed-tests/xdg-desktop-portal/te" label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.1' (uid=1000 pid=1207 comm="/usr/libexec/xdg-document-portal " label="unconfined") dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' dbus-daemon[1202]: [session uid=1000 pid=1202] Successfully activated service 'org.freedesktop.portal.Documents' 1..4 # Start of db tests ok 1 /db/create_doc path: /tmp/xdp-test-Q3WHR0/doc/387dfbb5/recursive-file ok 2 /db/recursive_doc ok 3 /db/create_docs ** xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) Bail out! xdg-desktop-portal:ERROR:tests/test-doc-portal.c:607:test_add_named: assertion failed (error == NULL): Can't open /tmp/xdp-test-Q3WHR0/doc/f7828134/add-named-1 (g-file-error-quark, 23) cleaning up pid 1202 FAIL: xdg-desktop-portal/test-doc-portal.test (Child process killed by signal 6) SUMMARY: total=2; passed=1; skipped=0; failed=1; user=0.0s; system=0.0s; maxrss=9600 autopkgtest [12:16:42]: test gnome-desktop-testing: ---] autopkgtest [12:16:42]: test gnome-desktop-testing: - - - - - - - - - - results - - - - - - - - - - gnome-desktop-testing FAIL non-zero exit status 2 ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: xdg-desktop-portal (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Tags: update-excuse-bionic ** Summary changed: - autopkgtest fails in bionic (almost always) starting with 1.0.3 + autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3 ** Also affects: xdg-desktop-portal (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu Focal) Status: New => Fix Released ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1899179 Title: autopkgtest (almost always) fails in bionic on ppc64el starting with 1.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1899179/+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
@paelzer To correct myself this (s390x) regression is not due to the snapd seeding issue, but LP: #1895576 which may have been already fixed. -- 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
@paelzer I agree that the fact, i.e. that systemd autpkgtest is failing in Groovy/s390x, but this is a real regression which is not due to flakiness of tests-in-lxd. Please don't reopen this bug, but file a new one or find one already opened. As I see this is still LP: #1878225. I'm filing a hint for it for now. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's comment's about what his plan is after his revert. -- 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/glib2.0/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882034] Re: cannot start X session with NIS account
Since lightdm works OK there is most likely something that GDM could do differently. I think this is a duplicate of LP: #1745664 . Does installing ncsd resolve the issue with gdm3, too? -- 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/1882034 Title: cannot start X session with NIS account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882034] Re: cannot start X session with NIS account
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1882034 Title: cannot start X session with NIS account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
@eurbah 245.4-4ubuntu1 fixed the issue in systemd. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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: gnome-terminal 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: gnome-terminal unduly forces umask=0022
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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: gnome-terminal 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 1803993] Re: Password appears on the VT1 screen
** Changed in: systemd (Ubuntu) Assignee: Balint Reczey (rbalint) => (unassigned) -- 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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Incomplete -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Marking as invalid for systemd since there is not much pointing at systemd here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825515] Re: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.
Do you still observe the issue on 19.10 or later? I'm reassigning to a package more related to the potential bug. ** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825515 Title: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
Fixed in Focal, to be SRU-d to Eoan. ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
There is a systemd 243 build in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801 for Eoan, it may worth a shot to try it, but it looks like an issue with nvidia's drivers rather than a bug in systemd. -- 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/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
** Description changed: + [Impact] + + * Shutdown and restart options don't work from the login screen, when + the user is not logged in. + + [Test Case] + + * Start the system and don't log in, or log out in case the system is set up with autologin. + * Restart, then shut down the system using the option in the upper right corner of the login screen. + * Observe both operations working. + + [Regression Potential] + + * The fix is treating treating the greeter as user display sessions by + cherry-picking upstream's change released in v243. The fix itself is + very small, but there may be non-obvious security implications. + + [Original Bug Text] + When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
I've pushed the fix to schedule it for the next upload: https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-eoan I'm waiting a few days to see if there are other fixes showing up to include in the same upload. -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847896] Re: Unable to shutdown or restart from log-in screen
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- 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/1847896 Title: Unable to shutdown or restart from log-in screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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
** Description changed: + [Impact] + + * The keyboard on the graphical login screen started on VT1 may stop + working and or keypresses including passwords are leaked to the terminal + console running 'behind' the graphical login screen or environment. + + [Test Case] + + * Reboot after installing the fixed systemd package. + * Install sysdig + * Start sysdig on a remote connection or on a terminal console: + $ sudo sysdig evt.type=ioctl | grep request=4B4 + * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works + * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. + * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 + + [Regression Potential] + + * The fix checks the current keyboard mode of the VT and allows only + safe mode switches. The potential regression could be not allowing a + valid mode switch keeping a keyboard in a non-operational mode. Testing + covers that by typing the keyboard. + + (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 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 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
** Changed in: gdm3 (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Confirmed => Invalid -- 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
Forwarded proposed fix to systemd upstream: https://github.com/systemd/systemd/pull/12378 ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/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
** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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
It looks like systemd is changing the mode (see argument=3) on VT1 on logouts. #define K_RAW 0x00 #define K_XLATE 0x01 #define K_MEDIUMRAW 0x02 #define K_UNICODE 0x04 #define K_OFF 0x04 #define KDGKBMODE 0x4B44 /* gets current keyboard mode */ #define KDSKBMODE 0x4B45 /* sets current keyboard mode */ test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo sysdig evt.type=ioctl | grep request=4B45 [sudo] password for test: 5657343 15:21:51.819076315 1 Xorg (1069) > ioctl fd=11(/dev/tty1) request=4B45 argument=4 5657453 15:21:51.820019063 0 systemd-logind (575) > ioctl fd=22(/dev/tty1) request=4B45 argument=3 5753055 15:21:52.771635876 0 systemd-logind (575) > ioctl fd=21(/dev/tty1) request=4B45 argument=4 20723813 15:49:41.368621972 1 systemd (23717) > ioctl fd=3(/dev/tty2) request=4B45 argument=3 22605710 15:53:04.107253025 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) request=4B45 argument=4 22612602 15:53:04.142057934 1 Xorg (24089) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 24077108 15:53:28.705600119 0 Xorg (24089) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 24077278 15:53:28.706353493 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) request=4B45 argument=3 24626343 15:53:58.336589416 0 systemd-logind (575) > ioctl fd=22(/dev/tty1) request=4B45 argument=3 24804326 15:53:59.385872243 0 systemd-logind (575) > ioctl fd=21(/dev/tty1) request=4B45 argument=4 25515114 15:54:12.915072995 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) request=4B45 argument=4 25520504 15:54:12.929480424 1 Xorg (25112) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 26921037 15:54:46.872029874 1 Xorg (25112) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 26921239 15:54:46.872654795 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) request=4B45 argument=3 27104852 15:54:53.870639078 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) request=4B45 argument=4 27112208 15:54:53.894217722 1 Xorg (25697) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 28677455 15:55:44.581119464 0 Xorg (25697) > ioctl fd=11(/dev/tty3) request=4B45 argument=4 28678288 15:55:44.592966138 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) request=4B45 argument=3 ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
Tested with 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1260041:~# apt-mark auto linux-image-extra-4.8.0-56-generic linux-image-extra-4.8.0-58-generic linux-image-extra-4.8.0-54-generic linux-image-extra-4.8.0-53-generic linux-image-extra-4.8.0-56-generic set to automatically installed. linux-image-extra-4.8.0-58-generic set to automatically installed. linux-image-extra-4.8.0-54-generic set to automatically installed. linux-image-extra-4.8.0-53-generic set to automatically installed. root@x-uu-lp-1260041:~# unattended-upgrade --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates Removing unused kernel packages: linux-image-extra-4.8.0-54-generic linux-image-4.8.0-54-generic Keeping auto-removable linux-image-extra-4.8.0-54-generic package(s) because it would also remove the following packages which should be kept in this step: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev (Reading database ... 53554 files and directories currently installed.) Removing linux-image-extra-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Generating /boot/initrd.img-4.8.0-54-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Removing linux-image-4.8.0-54-generic (4.8.0-54.57~16.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic update-initramfs: Deleting /boot/initrd.img-4.8.0-54-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.8.0-54-generic /boot/vmlinuz-4.8.0-54-generic Packages that were successfully auto-removed: linux-image-4.8.0-54-generic linux-image-extra-4.8.0-54-generic Packages that are kept back: linux-image-extra-4.8.0-54-generic Packages that will be upgraded: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd-sysv_229-4ubuntu21.17_amd64.deb ... Unpacking systemd-sysv (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd-sysv (229-4ubuntu21.17) ... Log ended: 2019-03-13 17:17:36 Log started: 2019-03-13 17:17:36 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../udev_229-4ubuntu21.17_amd64.deb ... Unpacking udev (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libudev1_229-4ubuntu21.17_amd64.deb ... Unpacking libudev1:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for systemd (229-4ubuntu21.16) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libudev1:amd64 (229-4ubuntu21.17) ... Setting up udev (229-4ubuntu21.17) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for libc-bin (2.23-0ubuntu11) ... Processing triggers for initramfs-tools (0.122ubuntu8.14) ... update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Log ended: 2019-03-13 17:17:44 Log started: 2019-03-13 17:17:45 (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../libpam-systemd_229-4ubuntu21.17_amd64.deb ... Unpacking libpam-systemd:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Preparing to unpack .../libsystemd0_229-4ubuntu21.17_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... Setting up libsystemd0:amd64 (229-4ubuntu21.17) ... Processing triggers for libc-bin (2.23-0ubuntu11) ... (Reading database ... 47681 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.17_amd64.deb ... Unpacking systemd (229-4ubuntu21.17) over (229-4ubuntu21.16) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up systemd (229-4ubuntu21.17) ... addgroup: The
[Bug 1803993] Re: Password appears on the VT1 screen
It seems I can reproduce the issue in qemu and look at vt1 by stopping gdm3, since the switch to vt2 does not show vt1 even for a moment. -- 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 1803581] Re: PrepareForShutdown() signal from logind is not handled
I reported the GDM issue upstream, but LP does not handle Gitlab URLs yet: https://gitlab.gnome.org/GNOME/gdm/issues/443 ** Description changed: When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutdown() signal is emitted by logind: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ Processes holding delay inhibitor locks can start their pre-shutdown operations and until they finish there is no feedback in a Unity session for the logged in user that shutdown is successfully requested on Xenial. On Bionic, the default Gnome 3 session does handle the signal and logs the user off to GDM, but GDM does not tell that shutdown is pending and the user may think that she/he can log in again or should to something to really start the shutdown. With Ubuntu's default configuration the confusion only lasted up to 5 seconds (default max delay for inhibitor locks), but the next upload of unattended-upgrades increases the delay up to 30 seconds which is more than noticeable (LP: #1803137). Please consider either logging the user off from Unity and stopping GDM - to switch over the the plymouth shutdown screen of at least showing a + to switch over the plymouth shutdown screen or at least showing a notification about the ongoing shutdown. ** Also affects: gdm Importance: Undecided Status: New -- 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/1803581 Title: PrepareForShutdown() signal from logind is not handled To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1803581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803581] [NEW] PrepareForShutdown() is not handled
Public bug reported: When a user logged in to the GUI session and she/he request shutdown of the system a PrepareForShutdown() signal is emitted by logind: https://www.freedesktop.org/wiki/Software/systemd/inhibit/ Processes holding delay inhibitor locks can start their pre-shutdown operations and until they finish there is no feedback in a Unity session for the logged in user that shutdown is successfully requested on Xenial. On Bionic, the default Gnome 3 session does handle the signal and logs the user off to GDM, but GDM does not tell that shutdown is pending and the user may think that she/he can log in again or should to something to really start the shutdown. With Ubuntu's default configuration the confusion only lasted up to 5 seconds (default max delay for inhibitor locks), but the next upload of unattended-upgrades increases the delay up to 30 seconds which is more than noticeable (LP: #1803137). Please consider either logging the user off from Unity and stopping GDM to switch over the the plymouth shutdown screen of at least showing a notification about the ongoing shutdown. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1803581 Title: PrepareForShutdown() is not handled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
Verified with 3.28.1-0ubuntu4.18.04.3. -- 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/1775226 Title: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1775226 Title: [SRU] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
I don't remember what I did in the past, but I was able to reproduce the dialog with the following steps: 1. Upgrade fully and reboot the system. 2. Downgraded a package: sudo apt install unattended-upgrades=1.1ubuntu1 3. Disabled u-u: sudo dpkg-reconfigure unattended-upgrades 4. Opened Gnome Software (Ubuntu Software) 5. Clicked on Updates tab, then on the refresh/reload icon in the upper left corner. Gnome Software printed "Looking for updates", then misleadingly that "Software is up to date" despite u-u is still not upgraded. 6. The prepared-update file is now present: $ ls -alh /var/lib/PackageKit/prepared-update -rw-r--r-- 1 root root 93 srp 18 12:24 /var/lib/PackageKit/prepared-update 7. Clicking on Shutdown now offers installing updates which is executed, too. Upon next login a report is shown about installed updates. -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
** Attachment added: "Dump of transtactions.db" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+attachment/5164807/+files/dump-gnome-sw-transactions.db -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] Re: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
I'm sorry, I just upgraded my system and downgraded a package to test latest gnome sw. The current state is as follows: $ ls -alh --time-style=full-iso /var/lib/PackageKit/ total 148K drwxr-xr-x 2 root root 4,0K 2018-07-18 11:15:31.973829737 +0200 . drwxr-xr-x 65 root root 4,0K 2018-06-21 13:48:53.768046205 +0200 .. -rw-r--r-- 1 root root 11K 2018-06-05 18:42:56.26400 +0200 offline-update-competed -rw-r--r-- 1 root root 128K 2018-07-18 11:15:31.973829737 +0200 transactions.db $ cat /var/lib/PackageKit/offline-update-competed [PackageKit Offline Update Results] Success=true Role=update-packages Packages=bsdutils;1:2.31.1-0.4ubuntu3.1;amd64;... -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775226] [NEW] Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades
Public bug reported: In Ubuntu the GUI for upgrading packages is update-manager allowing debconf questions to be answered when needed and Ubuntu also offers unattended-upgrades for upgrading packages in the background and it keeps back packages from upgrading when configuration-file changes would need user interaction during the upgrade. Unattended-upgrades can be configured to perform upgrades during system shutdown. Gnome Software in Bionic started offering performing upgrades during shutdown using PackageKit independently from update-manager and unattended-upgrades without offering all of the features of either one. Unless there is a decision to fully switch to Gnome Software I suggest disabling the "Install pending software updates" on the shutdown screen to avoid confusing users. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Both update-manager and Gnome Software are offering upgrades" https://bugs.launchpad.net/bugs/1775226/+attachment/5149053/+files/Screenshot_bionic-test_2018-06-05_09%3A20%3A07.png -- 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/1775226 Title: Gnome Software offers installation of updates on shutdown independently from update-manager and unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772051] [NEW] piuparts report problems about systemd
Public bug reported: Running piuparts fails on systemd package: dget http://launchpadlibrarian.net/366689472/systemd_237-3ubuntu10_amd64.deb sudo piuparts -d bionic systemd_237-3ubuntu10_amd64.deb ... 4m28.6s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', '--purge', 'systemd'] 4m28.6s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', '--purge', '--pending'] 4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', '--purge', '--pending'] 4m28.7s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', '--remove', '--pending'] 4m28.7s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg', '--remove', '--pending'] 4m28.7s DEBUG: Starting command: ['lsof', '-w', '+D', '/tmp/tmpf5kGNh'] 4m29.1s DEBUG: Command failed (status=1), but ignoring error: ['lsof', '-w', '+D', '/tmp/tmpf5kGNh'] 4m29.4s ERROR: WARN: Broken symlinks: /etc/localtime -> /usr/share/zoneinfo/Etc/UTC /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> /lib/systemd/system/systemd-resolved.service /etc/systemd/system/multi-user.target.wants/systemd-resolved.service -> /lib/systemd/system/systemd-resolved.service /etc/systemd/system/multi-user.target.wants/ondemand.service -> /lib/systemd/system/ondemand.service 4m29.4s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg-divert', '--list'] 4m29.4s DUMP: diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash diversion of /bin/sh to /bin/sh.distrib by dash 4m29.4s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'dpkg-divert', '--list'] 4m29.4s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'apt-get', 'clean'] 4m29.4s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'apt-get', 'clean'] 4m30.7s DEBUG: Modified(uid, gid, mode, size, target): /etc/resolv.conf (0, 0, - 100644, 38, None) != (0, 0, l 120777, 39, ../run/systemd/resolve/stub-resolv.conf) 4m30.7s DEBUG: Modified(uid, gid, mode, size, target): /var/log/tallylog (0, 0, - 100600, 6464, None) != (0, 0, - 100600, 6592, None) 4m30.8s ERROR: FAIL: Package purging left files on system: /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> /lib/systemd/system/systemd-resolved.service not owned /etc/systemd/system/multi-user.target.wants/ not owned /etc/systemd/system/multi-user.target.wants/ondemand.service -> /lib/systemd/system/ondemand.service not owned /etc/systemd/system/multi-user.target.wants/systemd-resolved.service -> /lib/systemd/system/systemd-resolved.service not owned /var/log/apt/eipp.log.xz not owned /var/log/journal/ not owned 4m30.8s ERROR: FAIL: After purging files have been modified: /etc/resolv.conf not owned /var/log/tallylog not owned 4m30.8s ERROR: FAIL: Installation and purging test. 4m31.2s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', '/proc'] 4m31.2s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', '/proc'] 4m31.2s DEBUG: Starting command: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', '/dev/pts'] 4m31.2s DEBUG: Command ok: ['chroot', '/tmp/tmpf5kGNh', 'eatmydata', 'umount', '/dev/pts'] 4m31.2s DEBUG: Starting command: ['rm', '-rf', '--one-file-system', '/tmp/tmpf5kGNh'] 4m31.4s DEBUG: Command ok: ['rm', '-rf', '--one-file-system', '/tmp/tmpf5kGNh'] 4m31.4s DEBUG: Removed directory tree at /tmp/tmpf5kGNh 4m31.4s ERROR: piuparts run ends. I already proposed a fix for /var/log/journal/ at https://salsa.debian.org/debian/piuparts/merge_requests/1 , but most of the rest should be fixed in systemd. piuparts run on Debian's systemd_238-4_amd64.deb in sid passes. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1772051 Title: piuparts report problems about systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1772051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
@jarnos Verification is needed only for update-manager for now, thus I think you verified that the fix worked for Xenial. Could you please change the tag to reflect that or you would like to wait for the u-u fix, - which may come later? -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Description changed: [Impact] - * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. - * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. - * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. + * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. + * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. + * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] - 1. Install kernel packages to be removed, mark them auto-installed and + 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: - sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic - sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic - sudo /etc/kernel/postinst.d/apt-auto-removal + sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic + sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic + sudo /etc/kernel/postinst.d/apt-auto-removal - 2. Also downgrade a package to be upgraded: + 2. Also downgrade a package to be upgraded: -sudo apt-get install -y ca-certificates=20160104ubuntu1 + sudo apt-get install -y ca-certificates=20160104ubuntu1 - 3. (update-manager). Run update-manager and observe that kernel + 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. - sudo update-manager + sudo update-manager - 4. (update-manager) Click on Install Now and observe that the kernel + 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. - 3. (unattended-upgrades) Run unattended-upgrades manually and observe - the removal of the autoremovable kernel packages: + 3. (unattended-upgrades, the fix comes in an update of u-u) Run + unattended-upgrades manually and observe the removal of the + autoremovable kernel packages: - sudo unattended-upgrade -v + sudo unattended-upgrade -v [Regression Potential] - The change may cause update-manager or unattanded-upgrades to remove + The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] - - The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. + + The unattended-upgrades fix is uploaded with many other fixes and those + may cause regressions in other areas in unattended-upgrades. [Original bug text] When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDeskto
Re: [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
On Fri, Mar 30, 2018 at 3:12 PM, Jarno Suni <1624...@bugs.launchpad.net> wrote: > Brian, I tested the update-manager version you told. It is true that > update-manager removes the unused packages, but step 3. (unattended- > upgrades) does not remove the unused kernels. > > I add failed tag as this bug is originally about unattended-upgrades. Thanks for testing the fix and also thank you for preparing the linux-purge script. I read it but integrating it to to current tools would have been problematic and I hope you agree that the solution finally used is minimally intrusive and achieves removing unused kernels in a safe way. The fix for unattended-upgrades is not uploaded yet but is available Bionic and in the ppa:rbalint/scratch PPA if you would like to give it a try. -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Description changed: + [Impact] + + * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. + * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. + * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. + + [Test Case] + + 1. Install kernel packages to be removed, mark them auto-installed and + run apt's kernel hook script to make apt consider them autoremovable: + + sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic + sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic + sudo /etc/kernel/postinst.d/apt-auto-removal + + 2. Also downgrade a package to be upgraded: + +sudo apt-get install -y ca-certificates=20160104ubuntu1 + + 3. (update-manager). Run update-manager and observe that kernel + packages are offered for removal in Details of updates. + + sudo update-manager + + 4. (update-manager) Click on Install Now and observe that the kernel + packages are removed. + + 3. (unattended-upgrades) Run unattended-upgrades manually and observe + the removal of the autoremovable kernel packages: + + sudo unattended-upgrade -v + + [Regression Potential] + + The change may cause update-manager or unattanded-upgrades to remove + used kernel packages or fail to install other package updates. + + [Other Info] + + The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. + + [Original bug text] + When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades 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-software in Ubuntu. https://bugs.launchpad.net/bugs/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Changed in: unattended-upgrades (Ubuntu) Status: In Progress => Fix Committed -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
I'm working on removing old kernels in u-u and also make the similar changes to update-manager: https://github.com/mvo5/unattended- upgrades/pull/97 -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Changed in: unattended-upgrades (Ubuntu) Status: Opinion => In Progress ** Changed in: unattended-upgrades (Ubuntu Artful) Status: Opinion => In Progress -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: update-manager (Ubuntu Artful) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: update-manager (Ubuntu) Status: New => In Progress ** Changed in: update-manager (Ubuntu Artful) Status: New => Confirmed ** Changed in: update-manager (Ubuntu Artful) Status: Confirmed => In Progress -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
s/to title/the title/ -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
Changed to title to reflect that the issue is not about something not implemented, but something not set as default. -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software
** Summary changed: - By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. + By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu Artful) Status: New => Confirmed ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Opinion ** Changed in: unattended-upgrades (Ubuntu Artful) Status: Confirmed => Opinion -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
On Wed, Sep 27, 2017 at 2:42 PM, Julian Andres Klode wrote: > Hmm, I thought we would not do that anymore, and packages get marked as > manual when removing a meta package, but I might be missing something. I ran this on zesty, but if meta packages are handled differently then I could imagine a similar case when meta packages are not involved. -- 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/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
On Wed, Sep 27, 2017 at 1:49 PM, Brian Murray wrote: > @Balint re "@Jarno: IMO Unattended-Upgrade::Remove-Unused-Dependencies > is already a risky option and I don't recommend enabling it because it > may remove packages which are not used according the to package- > dependency chain but which users rely on using software that is not > packaged." > > Could you give me an example of how people would install dependencies > for software that is not package that would also set the > "is_auto_removable" flag in the apt cache to True? I can't think of a > situation like this. I had the opposite situation in my mind. People would remove packages which are not auto removable, like ubuntu-desktop (for example because something ubuntu-desktop depends on is acting badly) and then many package in ubuntu-desktop's dependency change become auto removable: $ sudo apt-get remove ubuntu-desktop Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: a11y-profile-manager-indicator activity-log-manager adium-theme-ubuntu aisleriot app-install-data-partner apturl apturl-common baobab bluez-cups ... xorg Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: ubuntu-desktop 0 upgraded, 0 newly installed, 1 to remove and 7 not upgraded. After this operation, 46,1 kB disk space will be freed. Do you want to continue? [Y/n] It is a simpler problematic situation than the one I originally mentioned, u-u would remove software which is probably in use, no additional software is broken. -- 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/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT
@xnox IMO watchdogs should not care if it is a "soft" or other kind of lockup. I'm closing the bug because the workaround for recovering from a potentially broken journal is working and there is no indication of a journal which is actually broken. ** Changed in: systemd (Ubuntu Artful) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with SIGABORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Submitted patch in the bug for Debian, waiting for comments. ** Summary changed: - DHCP exit hook for setting NTP servers doesn't work + DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work ** Bug watch added: Debian Bug tracker #861769 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861769 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861769 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1685484 Title: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685484/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640320] Re: FTBFS in zesty
** Changed in: location-service (Ubuntu) Assignee: Balint Reczey (rbalint) => (unassigned) ** Changed in: location-service (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640320] Re: FTBFS in zesty
Thomas will merge the fix from bzr and will take care of zesty landing thus this debdiff is obsolete. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
Please ignore, this is already in -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
Debian has a fix for random crashes, this could have been one of them: Changes: emacs25 (25.1+1-3) unstable; urgency=medium . * Configure with REL_ALLOC=no to fix crashes. Thanks to Santiago Vila for reporting the problem, and Sean Whitton for helping test the fix. (Closes: 842728) . * Disable xwidget (webkit) support. Thanks to David Bremner for reporting the issue. (Closes: 843462) . * Depend on liboss4-salsa-dev on hurd and kfreebsd. Thanks to Aaron M. Ucko for reporting the problem and Svante Signell for providing the fix. (Closes: 840702) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640320] Re: FTBFS in zesty
Now it contains the build-dependency changes as well, tested with sbuild and ratt ** Patch added: "debdiff for fixing all build issues" https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+attachment/4843340/+files/location-service_3.0.0+16.10.20160912-0ubuntu3.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640320] Re: FTBFS in zesty
The CMake part did not work for me, but the attached patch does. I kept the vector related part giving credit in d/changelog. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1640320] Re: FTBFS in zesty
** Changed in: location-service (Ubuntu) Status: Confirmed => In Progress ** Changed in: location-service (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1575340] Re: Gnome Software catalog entry missing for Wireshark
"I am not sure but I think the icon has to be in the wireshark-qt and wireshark-gtk packages, not wireshark-common." I would consider this as a bug (missing feature to get icon files from dependencies) in Gnome Software. Reassigning the bug for comments from gnome-software maintainers. ** Changed in: wireshark (Ubuntu) Status: Confirmed => Opinion ** Package changed: wireshark (Ubuntu) => gnome-software (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/1575340 Title: Gnome Software catalog entry missing for Wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1575340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs