Bug#1027006: Acknowledgement (hexchat: URL handling mechanism is broke under KDE)
Found the source of the issue with the gio command when running: $ desktop-file-install --dir=$HOME/.local/share/applications .local/share/applications/firefox.desktop value "\\$HOME/.local/firefox/firefox %u" for key "Exec" in group "Desktop Entry" contains a reserved character '$' outside of a quote Adding quotes didn't help. The solution was to hard-code my home directory in the Exec= line instead of using $HOME. Then the gio command successfully runs: $ gio mime x-scheme-handler/http firefox.desktop Set firefox.desktop as the default for x-scheme-handler/http $ gio mime x-scheme-handler/https firefox.desktop Set firefox.desktop as the default for x-scheme-handler/https $ gio mime x-scheme-handler/https Default application for “x-scheme-handler/https”: firefox.desktop Registered applications: firefox.desktop chromium.desktop kfmclient_html.desktop Recommended applications: firefox.desktop chromium.desktop kfmclient_html.desktop On 12/25/22 23:06, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1027006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027006. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Mattia Rizzolo If you wish to submit further information on this problem, please send it to 1027...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#1027006: hexchat: URL handling mechanism is broke under KDE
Package: hexchat Version: 2.14.3-6+deb11u1 Severity: normal Dear Maintainer, According to the Hexchat FAQ [https://hexchat.readthedocs.io/en/latest/faq.html#how-do-i-change-what-browser-is-opened] in order to configure the file association for http and https links the user is directed to use the 'gio' utility. For example: gio mime x-scheme-handler/http firefox.desktop gio mime x-scheme-handler/https firefox.desktop For users of KDE these commands will not run successfully, and other methods of configuring http and https mimetype associations such as setting [Default Applications] in ~/.config/mimetypes.list or in ~/.local/share/applications/mimetypes.list also have no effect. Also note that the other two examples in the fact which use gvfs-mime will not work either in Bullseye because gvfs-mime is deprecated and points to gio. The end result is that it is not possible to configure the http and https mime type associations for Hexchat. Instead, Hexchat should use a destkop-environment-neutral mime mechanism such as xdg-mime. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-0.deb11.2-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hexchat depends on: ii hexchat-common 2.14.3-6+deb11u1 ii libc62.31-13+deb11u5 ii libcanberra0 0.30-7 ii libdbus-glib-1-2 0.110-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u1 ii libglib2.0-0 2.66.8-1 ii libgtk2.0-0 2.24.33-2 ii libnotify4 0.7.9-3 ii libpango-1.0-0 1.46.2-3 ii libproxy1v5 0.4.17-1 ii libssl1.11.1.1n-0+deb11u3 ii libx11-6 2:1.7.2-5~ubuntu18.04 Versions of packages hexchat recommends: ii ca-certificates 20210119 ii hexchat-perl 2.14.3-6+deb11u1 ii hexchat-plugins 2.14.3-6+deb11u1 ii hexchat-python3 2.14.3-6+deb11u1 ii libglib2.0-bin 2.66.8-1 Versions of packages hexchat suggests: pn hexchat-otr pn unifont -- no debconf information
Bug#1024581: Acknowledgement (linux-image-6.0.0-0.deb11.2-amd64: System freeze)
Sorry the initial report was terse because I tried to get the bug sent out while running the buggy kernel before it froze. Here is some more information: In syslog there are messages like the following: Message from syslogd@compute2 at Nov 21 08:38:58 ... kernel:[ 256.407191] watchdog: BUG: soft lockup - CPU#10 stuck for 44s! [kwor ker/u48:0:9] Message from syslogd@compute2 at Nov 21 08:39:18 ... kernel:[ 276.291100] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [migration/1:21] Message from syslogd@compute2 at Nov 21 08:39:26 ... kernel:[ 284.407071] watchdog: BUG: soft lockup - CPU#10 stuck for 70s! [kworker/u48:0:9] Message from syslogd@compute2 at Nov 21 08:39:46 ... kernel:[ 304.291026] watchdog: BUG: soft lockup - CPU#1 stuck for 49s! [migration/1:21] The machine is a SuperMicro SYS-1028R-WTNR server Please let me know if I can provide any more info. -- Felicia
Bug#1012785: libgsasl7 depends on outdated gsasl-common version 1.10.0-5
Please close this bug. It is no longer applicable. Thanks!
Bug#1012768: Bug#1012785: libgsasl7 depends on outdated gsasl-common version 1.10.0-5
On 6/14/22 03:59, Simon Josefsson wrote: 1) Testing contains libgsasl7 1.10.0-5 that has a hard versioned dependency on gsasl-common 1.10.0-5 for translation files. 2) Unstable now has libgsasl18 1.11.3-2 that depends on gsasl-common 1.11.3-2. But unstable also still has libgsasl7 1.10.0-5. Isn't it possible to update libgsasl7 in unstable to 1.11.3-2 to match gsasl-common's version or else just update the gsasl-common dependency in libgsasl7 to 1.11.3-2 ?
Bug#1012785: libgsasl7 depends on outdated gsasl-common version 1.10.0-5
Package: libgsasl7 Version: 1.10.0-5+b1 Severity: important Dear Maintainer, libgsasl7 depends on gsasl-common 1.10.0-5 however the current version of gsasl-common is now 1.11.3-2 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgsasl7 depends on: ii gsasl-common 1.10.0-5 ii libc6 2.33-7 ii libgssapi-krb5-2 1.19.2-2+b2 ii libidn12 1.38-4 ii libntlm0 1.6-4 libgsasl7 recommends no packages. libgsasl7 suggests no packages. -- no debconf information
Bug#1012637: libsystemd-shared: libsystemd-share dependency problem prevents configuration of systemd
It occurs when the command 'lb bootstrap' from the 'live-build' package is run, which in turn runs '/usr/lib/live/build/bootstrap' On 6/10/22 14:06, Michael Biebl wrote: Control: tags -1 + moreinfo Am 10.06.22 um 22:53 schrieb Felicia P: Package: libsystemd-shared Version: 251.2-4 Severity: important Dear Maintainer, While running the scripts to build a Debian-live system the following command is failing apparently due to an issue with libsystemd-shared_251.2-4_amd64.deb: Please provide instructions how this problem can be reproduced (i.e. please provide the full scripts that you are using).
Bug#1012637: libsystemd-shared: libsystemd-share dependency problem prevents configuration of systemd
Package: libsystemd-shared Version: 251.2-4 Severity: important Dear Maintainer, While running the scripts to build a Debian-live system the following command is failing apparently due to an issue with libsystemd-shared_251.2-4_amd64.deb: ## W: Failure trying to run: chroot "/root/live-build/baylive/chroot" dpkg --force-overwrite --force-confold --skip-same-version --install /var/cache/apt/archives/libapparmor1_3.0.4-2_amd64.deb /var/cache/apt/archives/libargon2-1_0~20171227-0.3_amd64.deb /var/cache/apt/archives/libcryptsetup12_2%3a2.4.3-1+b1_amd64.deb /var/cache/apt/archives/libip4tc2_1.8.8-1_amd64.deb /var/cache/apt/archives/libjson-c5_0.16-1_amd64.deb /var/cache/apt/archives/libkmod2_29-1+b1_amd64.deb /var/cache/apt/archives/dmsetup_2%3a1.02.175-2.1_amd64.deb /var/cache/apt/archives/libdevmapper1.02.1_2%3a1.02.175-2.1_amd64.deb /var/cache/apt/archives/libssl3_3.0.3-7_amd64.deb /var/cache/apt/archives/libsystemd-shared_251.2-4_amd64.deb /var/cache/apt/archives/systemd_251.2-4_amd64.deb /var/cache/apt/archives/libfdisk1_2.38-4_amd64.deb W: See /root/live-build/baylive/chroot/debootstrap/debootstrap.log for details (possibly the package /var/cache/apt/archives/libsystemd-shared_251.2-4_amd64.deb is at fault) E: An unexpected failure occurred, exiting... ## The log /root/live-build/baylive/chroot/debootstrap/debootstrap.log shows: ## Unpacking libssl3:amd64 (3.0.3-7) ... dpkg: regarding .../libsystemd-shared_251.2-4_amd64.deb containing libsystemd-shared:amd64, pre-dependency problem: libsystemd-shared pre-depends on libapparmor1 (>= 2.13) libapparmor1:amd64 is unpacked, but has never been configured. dpkg: error processing archive /var/cache/apt/archives/libsystemd-shared_251.2-4_amd64.deb (--install): pre-dependency problem - not installing libsystemd-shared:amd64 Preparing to unpack .../systemd_251.2-4_amd64.deb ... Unpacking systemd (251.2-4) ... Preparing to unpack .../libfdisk1_2.38-4_amd64.deb ... Unpacking libfdisk1:amd64 (2.38-4) ... Setting up libapparmor1:amd64 (3.0.4-2) ... Setting up libargon2-1:amd64 (0~20171227-0.3) ... Setting up libip4tc2:amd64 (1.8.8-1) ... Setting up libjson-c5:amd64 (0.16-1) ... Setting up libssl3:amd64 (3.0.3-7) ... dpkg: dependency problems prevent configuration of systemd: systemd depends on libsystemd-shared (= 251.2-4); however: Package libsystemd-shared is not installed. dpkg: error processing package systemd (--install): dependency problems - leaving unconfigured Setting up libfdisk1:amd64 (2.38-4) ... Setting up libkmod2:amd64 (29-1+b1) ... Setting up libdevmapper1.02.1:amd64 (2:1.02.175-2.1) ... Setting up libcryptsetup12:amd64 (2:2.4.3-1+b1) ... Setting up dmsetup (2:1.02.175-2.1) ... Processing triggers for libc-bin (2.33-7) ... Errors were encountered while processing: /var/cache/apt/archives/libsystemd-shared_251.2-4_amd64.deb systemd ## -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-3-amd64 (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsystemd-shared depends on: ii libacl1 2.3.1-1 ii libapparmor1 3.0.4-2 ii libaudit1 1:3.0.7-1+b1 ii libblkid1 2.38-4 ii libc6 2.33-7 ii libcap2 1:2.44-1 ii libcrypt1 1:4.4.27-1.1 ii libgcrypt20 1.10.1-2 ii libip4tc2 1.8.8-1 ii libkmod2 29-1+b1 ii liblz4-1 1.9.3-2 ii liblzma5 5.2.5-2.1 ii libmount1 2.38-4 ii libpam0g 1.4.0-13 ii libseccomp2 2.5.4-1 ii libselinux1 3.3-1+b2 ii libssl3 3.0.3-5 ii libzstd1 1.5.2+dfsg-1 libsystemd-shared recommends no packages. libsystemd-shared suggests no packages. -- no debconf information
Bug#1012529: libkf5xmlgui5: KDE doesn't remember window sizes
Package: libkf5xmlgui5 Version: 5.78.0-2 Severity: important Dear Maintainer, This is related to this bug: https://bugs.kde.org/show_bug.cgi?id=427875 and also mentioned here: https://www.reddit.com/r/kde/comments/pp08tg/kde_forgetting_window_size_and_placement/ KDE does not remember window sizes for windows. Thus, when windows are re-opened, they always are reset to a default size which is usually very small and inconvenient because it is necessary to constantly be resizing windows. This bug has been attributed to the use of a second monitor and I can confirm that at one point in the past I had an external monitor connected to my laptop although it is no longer connected. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkf5xmlgui5 depends on: ii libc6 2.31-13+deb11u3 ii libkf5attica5 5.78.0-2 ii libkf5configcore5 5.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5globalaccel-bin 5.78.0-3 ii libkf5globalaccel55.78.0-3 ii libkf5guiaddons5 5.78.0-3 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes5 5.78.0-2 ii libkf5itemviews5 5.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5xmlgui-data 5.78.0-2 ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-9 ii libqt5dbus5 5.15.2+dfsg-9 ii libqt5gui55.15.2+dfsg-9 ii libqt5network55.15.2+dfsg-9 ii libqt5printsupport5 5.15.2+dfsg-9 ii libqt5widgets55.15.2+dfsg-9 ii libqt5xml55.15.2+dfsg-9 ii libstdc++610.2.1-6 Versions of packages libkf5xmlgui5 recommends: ii libkf5xmlgui-bin 5.78.0-2 libkf5xmlgui5 suggests no packages. -- no debconf information
Bug#1012528: plasma-desktop-data: Application Launcher (Kickoff) search not working
Package: plasma-desktop-data Version: 4:5.20.5-4 Severity: normal Dear Maintainer, The search bar in the Application Launcher (i.e. Kickoff) doesn't work. This is probably related to this bug: https://bugs.kde.org/show_bug.cgi?id=443131 In my case, at one point in time I had an external monitor connected to my laptop which is no longer connected. I have also switched from the default Application Launcher to Kickoff/Grid (https://store.kde.org/p/1317546). However, even after switching back to the original Application Launcher, the search bar no longer works. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop-data depends on: ii python3 3.9.2-3 Versions of packages plasma-desktop-data recommends: ii plasma-framework 5.78.0-3 ii plasma-workspace 4:5.20.5-6 ii qml-module-org-kde-activities 5.78.0-2 ii qml-module-org-kde-kwindowsystem 5.78.0-2 ii qml-module-org-kde-newstuff 5.78.0-4 ii qml-module-qtquick-dialogs5.15.2-2 plasma-desktop-data suggests no packages. -- no debconf information
Bug#1012527: kde-config-gtk-style: $HOME/.config/gtkrc-2.0 contents overwritten by KDE
Package: kde-config-gtk-style Version: 4:5.20.5-2 Severity: normal Dear Maintainer, KDE is overwriting the contents of $HOME/.config/gtkrc-2.0 For example, I have interface customizations in the file, yet when the file gets overwritten by KDE, the customizations are erased. The top of the file contains the line: # created by KDE Plasma, Wed Jun 8 11:07:53 2022 But no warning is given to the user that the contents of the file will be overwritten. Due to the fact that the file is overwritten, it makes it impossible for the user to provide their own customizations. I did some research on this and it was suggested that it was xsettingsd that is overwriting the file, however I uninstalled xsettingsd from my system and the behavior is still occuring. It has also been suggested that the background service "GNOME/GTK Settings Syncrhonization Service" is performing the overwriting. I attempted to disable this background service however it is still enabled. Even if it is overwriting gtkrc-2.0, that does not seem to be the correct behavior. There is potentially more info about this here: https://bugs.kde.org/show_bug.cgi?id=417534 -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kde-config-gtk-style depends on: ii libc6 2.31-13+deb11u3 ii libglib2.0-0 2.66.8-1 ii libgtk-3-03.24.24-4+deb11u2 ii libkdecorations2-5v5 4:5.20.5-1 ii libkdecorations2private7 4:5.20.5-1 ii libkf5configcore5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons5 5.78.0-4 ii libkf5dbusaddons5 5.78.0-2 ii libkf5guiaddons5 5.78.0-3 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus5 5.15.2+dfsg-9 ii libqt5gui55.15.2+dfsg-9 ii libqt5svg55.15.2-3 ii libstdc++610.2.1-6 Versions of packages kde-config-gtk-style recommends: pn xsettingsd | xsettings-kde Versions of packages kde-config-gtk-style suggests: ii kde-config-gtk-style-preview 4:5.20.5-2 -- no debconf information
Bug#932385: Bug still exists
Just did a fresh install of Buster and can confirm that this bug is very annoying and still exists. I try to create custom shortcuts for Okular similar to single-key shortcuts in Acrobat DC: h - hand tool v - text selection tool F8 - toggle toolbar F9 - toggle menu bar Multiple times I edit the shortcuts and save, but they are not saved. Please fix this! ii okular 4:17.12.2-2.2 amd64 universal document viewer Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster
Bug#964895: Cancel bug
Please cancel this bug. The error was related to a non-standard pager being used for the 'man' command.
Bug#944738: Also occurs with openjdk-14-jdk 14.0.1+7-1
I can confirm that this jlink related bug also occurs with Debian openjdk-14-jdk:amd64 14.0.1+7-1. I installed Oracle JDK 14.0.1 https://jdk.java.net/14/ and the problem does not occur.
Bug#933264: gradle: update SID version to new version?
The current release of Gradle is 6.4. There are major differences between the current release and Debian's 4.4.
Bug#949645: firefox: Firefox crashes immediate upon startup. safe-mode/disabling plugins has no effect.
This is actually a bug with sqlite3. Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949644 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949646+ 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#949644: libsqlite3-0: Firefox immediately crashes at start with latest libsqlite3-0
I can confirm this bug. Downloading and installing the previous sqlite3 and libsqlite3 packages fixes the issue https://snapshot.debian.org/package/sqlite3/ look for versions 3.30.1+fossil191229-1 # dpkg -i libsqlite3-0_3.30.1+fossil191229-1_amd64.deb sqlite3_3.30.1+fossil191229-1_amd64.deb libsqlite3-0_3.30.1+fossil191229-1_i386.deb 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#947907: Same here
Also experiencing this same bug. $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux bullseye/sid Release: unstable Codename: sid ii ure 6.4.0~rc1-4 amd64 LibreOffice UNO runtime environment 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#942883: closed by Alf Gaida (Re: libqt5xdgiconloader3: Dependency upon qtbase-abi-5-11-3 prevents installation)
Thank you for the transition information On 10/22/19 1:12 PM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the libqt5xdgiconloader3 package: > > #942883: libqt5xdgiconloader3: Dependency upon qtbase-abi-5-11-3 prevents > installation > > It has been closed by Alf Gaida . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Alf Gaida > by > replying to this email. > > 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: More info
I installed docker.io on an Ubuntu 18.04 machine running kernel linux-image-5.0.0-29-generic and compared the output of the script /usr/share/docker.io/contrib/check-config.sh with the Debian machine running kernel linux-image-5.2.0-3-amd64. The output on the left is the Debian machine where docker will not run and the one on the right is the Ubuntu one: info: reading kernel config from /boot/config-5.2.0-3-amd | info: reading kernel config from /boot/config-5.0.0-29-ge - cgroup hierarchy: nonexistent?? | - cgroup hierarchy: properly mounted [/sys/fs/cgr (see https://github.com/tianon/cgroupfs-mount) < - CONFIG_NF_NAT_IPV4: missing | - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_NF_NAT_NEEDED: missing | - CONFIG_NF_NAT_NEEDED: enabled (cgroup swap accounting is currently not enabled, y | (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_NONE: enabled | - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled (containers using eglibc <= 2.13 will not work. Swi < "CONFIG_VSYSCALL_[NATIVE|EMULATE]" or use "vsyscal < on kernel command line. Note that this will disabl < VDSO which may assist in exploiting security vulne < - CONFIG_CGROUP_HUGETLB: missing | - CONFIG_CGROUP_HUGETLB: enabled - CONFIG_EXT4_FS: enabled (as module) | - CONFIG_EXT4_FS: enabled - CONFIG_CRYPTO_AEAD: enabled (as module) | - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) | - CONFIG_CRYPTO_GCM: enabled - CONFIG_CRYPTO_SEQIV: enabled (as module) | - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) | - CONFIG_CRYPTO_GHASH: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: missing | - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled (a - CONFIG_AUFS_FS: missing | - CONFIG_AUFS_FS: enabled (as module) (note that some kernels include AUFS patches but < - CONFIG_BLK_DEV_DM: enabled (as module) | - CONFIG_BLK_DEV_DM: enabled Basically you can see that on the Debian system where docker fails to run the following are reported as missing: cgroup hierarchy CONFIG_NF_NAT_IPV4 CONFIG_NF_NAT_NEEDED CONFIG_LEGACY_VSYSCALL_NONE CONFIG_CGROUP_HUGETLB CONFIG_AUFS_FS I was also researching on forums and found that running /usr/sbin/dockerd by itself is useful for debugging output. Here is what it reports on the Debian machine: Error starting daemon: Devices cgroup isn't mounted 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: Something that might be relevant
I was doing some researching on kernel features required for docker and found this document: https://metztli.blog/index.php/debian-revisited-patching-linux-kernel?blog=4 One of the tools it recommends is lxc-checkconfig. Interestingly, when I run this command here is the following output: $ lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-5.2.0-3-amd64 --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled --- Control groups --- Cgroups: enabled Cgroup v1 mount points: Cgroup v2 mount points: /sys/fs/cgroup Cgroup v1 systemd controller: missing Cgroup v1 freezer controller: missing Cgroup namespace: required Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled, not loaded Macvlan: enabled, not loaded Vlan: enabled, not loaded Bridges: enabled, loaded Advanced netfilter: enabled, loaded CONFIG_NF_NAT_IPV4: missing CONFIG_NF_NAT_IPV6: missing CONFIG_IP_NF_TARGET_MASQUERADE: enabled, not loaded CONFIG_IP6_NF_TARGET_MASQUERADE: enabled, not loaded CONFIG_NETFILTER_XT_TARGET_CHECKSUM: enabled, loaded CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled, not loaded FUSE (for use with lxcfs): enabled, loaded --- Checkpoint/Restore --- checkpoint restore: enabled CONFIG_FHANDLE: enabled CONFIG_EVENTFD: enabled CONFIG_EPOLL: enabled CONFIG_UNIX_DIAG: enabled CONFIG_INET_DIAG: enabled CONFIG_PACKET_DIAG: enabled CONFIG_NETLINK_DIAG: enabled File capabilities: Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: still not starting as of 18.09.9+dfsg1-2
Just wanted to update that as of docker.io 18.09.9+dfsg1-2 still having the problem. I completely removed docker with apt purge docker.io and rm -rf /etc/docker and reinstalled, but still get the error: $ sudo apt install docker.io Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: docker-doc aufs-tools btrfs-progs rinse xfsprogs zfs-fuse | zfsutils The following NEW packages will be installed: docker.io 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/59.0 MB of archives. After this operation, 262 MB of additional disk space will be used. Selecting previously unselected package docker.io. (Reading database ... 480600 files and directories currently installed.) Preparing to unpack .../docker.io_18.09.9+dfsg1-2_amd64.deb ... Unpacking docker.io (18.09.9+dfsg1-2) ... Setting up docker.io (18.09.9+dfsg1-2) ... Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. invoke-rc.d: initscript docker, action "start" failed. ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2019-09-20 10:31:13 MST; 22ms ago Docs: https://docs.docker.com Process: 22490 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 22490 (code=exited, status=1/FAILURE) CPU: 208ms dpkg: error processing package docker.io (--configure): installed docker.io package post-installation script subprocess returned error exit status 1 Processing triggers for systemd (243~rc2-1) ... Processing triggers for man-db (2.8.7-3) ... Errors were encountered while processing: docker.io needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) $ sudo systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-09-20 10:31:18 MST; 1h 4min ago Docs: https://docs.docker.com Process: 23275 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 23275 (code=exited, status=1/FAILURE) CPU: 162ms Sep 20 10:31:17 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 20 10:31:17 life systemd[1]: Failed to start Docker Application Container Engine. Sep 20 10:31:18 life systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. Sep 20 10:31:18 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 4. Sep 20 10:31:18 life systemd[1]: Stopped Docker Application Container Engine. Sep 20 10:31:18 life systemd[1]: docker.service: Start request repeated too quickly. Sep 20 10:31:18 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 20 10:31:18 life systemd[1]: Failed to start Docker Application Container Engine. 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: docker.io: Failed to start Docker Application Container Engine.
$ sudo systemctl status docker.service ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2019-09-08 21:16:42 MST; 58s ago Docs: https://docs.docker.com Process: 727741 ExecStart=/usr/sbin/dockerd -H fd:// $DOCKER_OPTS (code=exited, status=1/FAILURE) Main PID: 727741 (code=exited, status=1/FAILURE) CPU: 165ms Sep 08 21:16:42 life systemd[1]: Failed to start Docker Application Container Engine. Sep 08 21:16:42 life systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. Sep 08 21:16:42 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Sep 08 21:16:42 life systemd[1]: Stopped Docker Application Container Engine. Sep 08 21:16:42 life systemd[1]: docker.service: Start request repeated too quickly. Sep 08 21:16:42 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 08 21:16:42 life systemd[1]: Failed to start Docker Application Container Engine. 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: docker.io: Failed to start Docker Application Container Engine.
Oops sorry about that. Sep 08 20:48:33 life systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. Sep 08 20:48:33 life systemd[1]: Stopped Docker Application Container Engine. Sep 08 20:48:33 life systemd[1]: docker.socket: Succeeded. Sep 08 20:48:33 life systemd[1]: Closed Docker Socket for the API. Sep 08 20:48:33 life systemd[1]: Stopping Docker Socket for the API. Sep 08 20:48:33 life systemd[1]: Starting Docker Socket for the API. Sep 08 20:48:33 life systemd[1]: Listening on Docker Socket for the API. Sep 08 20:48:33 life systemd[1]: docker.service: Start request repeated too quickly. Sep 08 20:48:33 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 08 20:48:33 life systemd[1]: Failed to start Docker Application Container Engine. Sep 08 20:48:33 life systemd[1]: docker.socket: Failed with result 'service-start-limit-hit' 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: docker.io: Failed to start Docker Application Container Engine.
Hi Arnaud I removed the custom ExecStart and attempted to restart docker. Here is the relevant output from journalctl: Sep 08 19:04:37 life systemd[1]: Starting Docker Socket for the API. Sep 08 19:04:37 life systemd[1]: Listening on Docker Socket for the API. Sep 08 19:04:37 life systemd[1]: docker.service: Start request repeated too quickly. Sep 08 19:04:37 life systemd[1]: docker.service: Failed with result 'exit-code'. Sep 08 19:04:37 life systemd[1]: Failed to start Docker Application Container Engine. Sep 08 19:04:37 life systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: Bug 939539
I forgot to mention I also did: $ sudo apt remove --purge docker.io $ sudo rm -rf /var/lib/docker $ sudo apt install docker.io To make sure it was a clean installation 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939797: Remove Bug 939797
Please remove this bug. There is an option in Settings -> Configure Dolphin -> Startup -> Show filter bar which resolves this issue 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#939539: Bug 939539
If I run the following from the command line: $ sudo /usr/sbin/dockerd -H fd:// it produces the following output: Failed to load listeners: no sockets found via socket activation: make sure the service was started by systemd According to other forum posts I've read, one recommendation was to change fd:// to unix://. If I do that then it appears to initialize but then fails with the following output: Error starting daemon: Devices cgroup isn't mounted In order to override the systemd ExecStart command I did: $ sudo systemctl edit docker.service and put the following lines in the file: [Service] ExecStart= ExecStart=/usr/sbin/dockerd -H unix:// $DOCKER_OPTS 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#782336: Okular 4:17.12.2-2.2 not printing
Trying to print selected pages from a document with Okular with customized print settings Steps to reproduce: Ctrl-P -> select Pages From, Pages, or Current Page radio button, input desired page(s) Properties -> Advanced -> Color Model -> select Greyscale OK -> Print Nothing happens. No print job shows up in print queue But if I do: Ctrl-P -> Options -> Current Page -> Print it will print System info: Okular 4:17.12.2-2.2 amd64 felicia@life:~$ uname -a Linux life 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux felicia@life:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#928417: Temporary fix: set xpinstall.signatures.required to false
An immediate fix is to set xpinstall.signatures.required to false in about:config 0xCEC1B8C7E51FC983.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
