Bug#1070906: ecryptfs-utils: mount fails with "No such file or directory" after user switch with sudo -i -u ...
Package: ecryptfs-utils Version: 111-6 Severity: normal Tags: patch Dear Maintainer, ecrypts-mount-private is failing when starting a user session via sudo (and probably other methods where no password is required for login, e.g. ssh with keyfile) Error message is: "mount: No such file or directory" and home directory is not mounted. Reason is that the user keyring is not linked to the session keyring. see also here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870126#15 Easy fix is to add a file into /etc/profile.d which does this linking, a one- liner in it is sufficient: keyctl link @u @s After this small change ecryptfs-mount-private is working as intended. This shouldn't raise any safety concerns as all is done with normal user permissions, the same is done by su (resp. pam) automatically. If the user keyring is already linked this additional command will do nothing and doesn't do any harm. So please include a file in the package which does this fix. -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (900, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ecryptfs-utils depends on: ii gettext-base0.21-12 ii keyutils1.6.3-2 ii libc6 2.36-9+deb12u4 ii libecryptfs1111-6 ii libgpgme11 1.18.0-3+b1 ii libkeyutils11.6.3-2 ii libpam-runtime 1.5.2-6+deb12u1 ii libpam0g1.5.2-6+deb12u1 ii libtspi10.3.15-0.3 ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: ii cryptsetup 2:2.6.1-4~deb12u2 ii rsync 3.2.7-1 -- no debconf information
Bug#1069903: gssproxy: directory /tmp/gssproxy/clients not available at service start
Package: gssproxy Version: 0.9.1-1+b1 Severity: important Tags: patch Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** I'm using gssproxy at my client for automatically getting a kerberos ticket for a service, without user intervention. I installed and startet the service but it was not working until i figured, that I need to create this directory as it is references in the default config file 99-nfs-client.config. And it has to be recreated after each restart of my client as files in /tmp do not survive a reboot. So I have added an override to /etc/systemd/system/gssproxy.service.d: [Service] ExecStartPre=/bin/mkdir -p /tmp/gssproxy/clients PrivateTmp=true To actually be used by rpc-gssd.service a second overriide is neccessary for this service: [Service] Environment=GSS_USE_PROXY=yes Without these two additions gssproxy was not working on my client, so I think they should be included in the package - or at least be mentioned in the docs and may be as a comment in the configuration file. -- System Information: Debian Release: 12.5 APT prefers stable APT policy: (990, 'stable'), (900, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gssproxy depends on: ii init-system-helpers 1.65.2 ii libc62.36-9+deb12u4 ii libgssapi-krb5-2 1.20.1-2+deb12u1 ii libgssrpc4 1.20.1-2+deb12u1 ii libini-config5 0.6.2-1 ii libk5crypto3 1.20.1-2+deb12u1 ii libkrb5-31.20.1-2+deb12u1 ii libpopt0 1.19+dfsg-1 ii libref-array10.6.2-1 ii libselinux1 3.4-1+b6 ii libverto10.3.1-1 gssproxy recommends no packages. gssproxy suggests no packages. -- Configuration Files: /etc/gssproxy/gssproxy.conf changed [not included] -- no debconf information [Service] ExecStartPre=/bin/mkdir -p /tmp/gssproxy/clients ProtectHome=true PrivateTmp=true ProtectSystem=full ProtectClock=true ProtectControlGroups=true ProtectKernelLogs=true RestrictRealtime=true
Bug#1034261: autofs attempts communication with portmapper (port 111) even for NFS4 mounts
Package: autofs Version: 5.1.8-1+b2 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrdae from bullseye to testing * What exactly did you do (or not do) that was effective (or ineffective)? I use autoount to mount a nfs4 share. Normal mount with mount command does work automount did work in bullseye but not in testing * What was the outcome of this action? relevant error meessage from automount: get_portmap_client: error 0x3 getting portmap client A workaround is to add the option "port=2049" to the automount map as suggested here: https://www.suse.com/support/kb/doc/?id=20650 With this option automount is working again, but it shouldn't be required for NFS v4 mounts when no portmapper is required and running * What outcome did you expect instead? successful mount when moving into mount directory without the extra port option If you don't want to fix the automount program itself maybe the otion can be added to the script /etc/auto.net for nfs4 mounts *** End of the template - remove these template lines *** -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages autofs depends on: ii init-system-helpers 1.65.2 ii libc62.36-8 ii libnsl2 1.3.0-2 ii libtirpc31.3.3+ds-1 ii libxml2 2.9.14+dfsg-1.1+b3 ii ucf 3.0043+nmu1 Versions of packages autofs recommends: ii e2fsprogs 1.47.0-2 ii kmod30+20221128-1 ii nfs-common 1:2.6.2-4 autofs suggests no packages. -- no debconf information
Bug#1029453: avahi-daemon fills log with Withdrawing address record / Registering address record for ipv6 address
Package: avahi-daemon Version: 0.8-5+deb11u1 Severity: normal Tags: ipv6 X-Debbugs-Cc: t...@security.debian.org Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As the headine nearly once every second a message is logged in the syslog that carrent ipv6 is withdraw followed by one which tells it is regitered again. The issue is for ipv6 only and I have multipe addresses assigned to the interface. The message is logged for the global and link local address which are auto- generated, but not for the manually assigned ULA address. I'm using current stable build and I haven't had the issue with the latest package before this version. ...and my DNS doesn't reslove the .local domain. Resolving .local with avahi still works *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.6 APT prefers stable-security APT policy: (990, 'stable-security'), (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-0.bpo.2-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages avahi-daemon depends on: ii adduser 3.118 ii bind9-host [host]1:9.18.10-2~bpo11+1 ii dbus 1.12.24-0+deb11u1 ii init-system-helpers 1.64~bpo11+1 ii libavahi-common3 0.8-5+deb11u1 ii libavahi-core7 0.8-5+deb11u1 ii libc62.31-13+deb11u5 ii libcap2 1:2.44-1 ii libdaemon0 0.14-7.1 ii libdbus-1-3 1.12.24-0+deb11u1 ii libexpat12.2.10-2+deb11u5 ii lsb-base 11.1.0 Versions of packages avahi-daemon recommends: ii libnss-mdns 0.14.1-2 Versions of packages avahi-daemon suggests: pn avahi-autoipd -- no debconf information
Bug#982324: ksplashqml crash at plasma workspace startup
To solve the issue I now have deinstalled everthing from plasma and kde and reinstalled again Now plasma is running without crash or black screen at startup. I suspect the package plasma-calendar-addons beeing the cause - but I not sure as I have not tested it again. I have read something about plasma-calendar issues here https://www.reddit.com/r/kde/comments/isi2s6/event_calendar_making_latest_plasma_and_qt_crash/[1] and this is the only package I remember which was installed before but I didn't install again now. Hope this help. Regards, trupf [1] https://www.reddit.com/r/kde/comments/isi2s6/event_calendar_making_latest_plasma_and_qt_crash/ signature.asc Description: This is a digitally signed message part.
Bug#982324: ksplashqml crash at plasma workspace startup
Package: plasma-workspace Version: 4:5.20.5-3 Hello, I just have migrated my laptop from Debian buster to unstable. I'm using KDE with x11. At login I get a message that ksplashqml produced a segmentation fault. Afterwards I get a black screen, but can add miniprograms (applets?) via mous right-click. This way I can add an application starter to the desktop and start applications as normal, even systemsettings. In systemsettings the Breeze theme is not shown, although all is installed if I look on synaptic (just the same plasma packages as I have installed on my desktop). If I use Gnome it starts as normal, so I guess it is not a video driver setting but has something to do with the upgrade process - but I cannot find out what went wrong. Regards, trupf signature.asc Description: This is a digitally signed message part.
Bug#932567: Found the issue
Sorry for the report I found the issue - is is the extension "Passman". I couldn't remove it easily due to the slow browser action but than I just deleted the user profile and the issue was gone. Installing the extensions one by led me to the above mentioned one. signature.asc Description: This is a digitally signed message part.
Bug#932567: chromium: extremly slow startup and operation
Package: chromium Version: 76.0.3809.62-1 Severity: important Tags: a11y Dear Maintainer, Chromium does startup extremly slow (like 2 min before I can enter a URL). After each action like opening a new tab, surfing to an url, opening settings page and so on I have to wait again somthing like 2 minutes or more. If a page is finally loaded, scrolling through it is o.k. Ican also enter a complete url, but once I press Enter I have to wait Browsing with firefox does not have this speed issues, so it has nothing to do with my internet connection speed. If I check the task manager is is the browser process which takes up full cpu power. * What led up to the situation? After upgrade from stretch to buster everything works fine but chromium is extremly slow even though it looks like it is the same chromium package (I was using testing for the chromium browser before). * What exactly did you do (or not do) that was effective (or ineffective)? After recommendation from reportbug I updated to latest unstable package, but the issue remains. I also disabled hardware acceleration in settings and chrome://flags. This didn't help either. * What was the outcome of this action? The issue is still there. * What outcome did you expect instead? Normal startup. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chromium depends on: ii chromium-common 76.0.3809.62-1 ii libasound2 1.1.8-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libatomic1 8.3.0-6 ii libatspi2.0-02.30.0-7 ii libavcodec58 7:4.1.3-1 ii libavformat587:4.1.3-1 ii libavutil56 7:4.1.3-1 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libcups2 2.2.10-6 ii libdbus-1-3 1.12.16-1 ii libdrm2 2.4.97-1 ii libevent-2.1-6 2.1.8-stable-4 ii libexpat12.2.6-2 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgtk-3-0 3.24.5-1 ii libharfbuzz0b2.3.1-1 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3 ii liblcms2-2 2.9-3 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.21-1 ii libnss3 2:3.45-1 ii libopenjp2-7 2.3.0-2 ii libopus0 1.3-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpci3 1:3.5.2-1 ii libpng16-16 1.6.36-6 ii libpulse012.2-4 ii libre2-5 20190101+dfsg-2 ii libsnappy1v5 1.1.7-1 ii libstdc++6 8.3.0-6 ii libvpx5 1.7.0-3 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.32-2 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages chromium recommends: pn chromium-sandbox Versions of packages chromium suggests: pn chromium-driver ii chromium-l10n76.0.3809.62-1 pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1 Versions of packages chromium-common recommends: pn chromium-sandbox ii fonts-liberation1:1.07.4-9 ii libgl1-mesa-dri 18.3.6-2 pn libu2f-udev ii notification-daemon 3.20.0-4 ii plasma-workspace [notification-daemon] 4:5.14.5.1-1 ii upower 0.99.10-1 -- Configuration Files: /etc/chromium.d/README changed [not included] -- no debconf information
Bug#849774: perl: SSl certificate verify failing for www.spdyn.de
You are right, I had version 2.039-1 and after installing 2.040-1 problem is fixed now.
Bug#849774: perl: SSl certificate verify failing for www.spdyn.de
Package: perl Version: 5.24.1~rc4-1 Severity: important Dear Maintainer, * What led up to the situation? update from Debian stable to testing * What exactly did you do (or not do) that was effective (or ineffective)? using ddclient with update.spdyn.de with ssl=true hich was working in jessie using "GET update.spdyn.de" produces same error in Perl * What was the outcome of this action? SSL connect attempt failed error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed at /usr/share/perl5/LWP/Protocol/http.pm line 47 * What outcome did you expect instead? successfol verification of server cert as with firefox or "openssl s_client -host update.spdyn.de -port 443" -- System Information: Debian Release: stretch/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages perl depends on: ii dpkg 1.18.15 ii libperl5.245.24.1~rc4-1 ii perl-base 5.24.1~rc4-1 ii perl-modules-5.24 5.24.1~rc4-1 Versions of packages perl recommends: ii netbase 5.3 pn rename Versions of packages perl suggests: ii libterm-readline-gnu-perl 1.35-1 ii make 4.1-9 pn perl-doc -- no debconf information
Bug#750122: exim4: The smarthost configuration should allow individual smarthosts for different users
Am Sonntag, 1. Juni 2014, 21:32:36 schrieb Marc Haber: Exim is not a suitable software to run against smarthosts that want to see certain envelope senders even after authenticating. Forcing it to do so has a number of issues that will certainly reduce reliability of the mail system. o.k. thanks for considering. Would you mind giving me some hints regarding which issues this are?
Bug#749769: Error message
The correct error message is no space left on device. File transfer is also working with gnome tools (nautilus), just all the KDE tools don't work.
Bug#749769: bug already filed upstream
look here: https://bugs.kde.org/show_b ug.cgi?id=334776
Bug#749769: kdelibs-bin: writing to mounted smb shares fails and no display of free space
Package: kdelibs-bin Version: 4:4.13.1-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-4.slh.3-aptosid-amd64 (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdelibs-bin depends on: ii libc6 2.18-7 ii libkdecore5 4:4.13.1-1 ii libkdeui5 4:4.13.1-1 ii libkio5 4:4.13.1-1 ii libkjsapi44:4.13.1-1 ii libkjsembed4 4:4.13.1-1 ii libkrosscore4 4:4.13.1-1 ii libnepomuk4 4:4.13.1-1 ii libnepomukutils4 4:4.13.1-1 ii libqt4-dbus 4:4.8.6+dfsg-1 ii libqt4-xml4:4.8.6+dfsg-1 ii libqtcore44:4.8.6+dfsg-1 ii libqtgui4 4:4.8.6+dfsg-1 ii libsoprano4 2.9.4+dfsg-1 ii libstdc++64.9.0-3 ii libx11-6 2:1.6.2-2 kdelibs-bin recommends no packages. kdelibs-bin suggests no packages. -- debconf-show failed SMB share is mounted with mount command and acces with not KDE related tools works as expected (cp, mc...) In KDE you can read from the share but not write to it. Error message is no free space on device available (translated from German). KDE does also not show how much free space is available on the device. Access to the share with smb://... does work normal and with successful file writing although. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749524: dbus Authentication AccessDenied after dist-upgrade
Package: dbus Version: 1.8.2-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-4.slh.3-aptosid-amd64 (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dbus depends on: ii adduser 3.113+nmu3 ii libaudit11:2.3.6-1 ii libc62.18-7 ii libcap-ng0 0.7.3-1+b1 ii libdbus-1-3 1.8.2-1 ii libexpat12.1.0-4 ii libselinux1 2.3-1 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii lsb-base 4.1+Debian12 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-x11 1.8.2-1 -- no debconf information After dist-upgrade with apt-get there are obviously authentication problems on the system dbus. The following was working before but is not any more: - mount smb shares with smb4k (translated error message from German: action execution has failes (Error code: AuthenticationDenied) - Hibernate and Suspend buttons are not more displayed in the KDE menu, where they have been before. It looks like a dbus or polkit issue as hibernation is still working when logged in as user root and can be fixed with some changes. For a fix add lines with allow_anyyes/allow_any to /usr/shar/polkit/actions/org.freedesktop.upower.policy in the appropriate sections. (but I guess this is not a correct solution...) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739344: chromium: VLC plugin crashes
Package: chromium Version: 31.0.1650.57-1 Severity: normal Dear Maintainer, in i386 the vlc plugin crashes when called by a web page in chromium. See details at http://code.google.com/p/chromium/issues/detail?id=240839 This is reproduceable with Google Chrome and Chromium but seems to be Debian specific as only useres of Debian and derivates have confirmed the bug so far. You can find procedures to reproduce the bug on the mentioned page. You can even use the fix in #11 and the vlc plugin will work. Regards, T. Rupf -- System Information: Debian Release: 7.0 Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-10.slh.2-aptosid-amd64 (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 31.0.1650.57-1 ii gconf-service3.2.6-1 ii libasound2 1.0.27.2-3 ii libatk1.0-0 2.10.0-2 ii libc62.17-0experimental2 ii libcairo21.12.16-2 ii libcups2 1.6.3-1 ii libdbus-1-3 1.8.0-1 ii libexpat12.1.0-4 ii libfontconfig1 2.11.0-2 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.7.2-5 ii libgconf-2-4 3.2.6-1 ii libgcrypt11 1.5.3-2 ii libgdk-pixbuf2.0-0 2.28.0-1 ii libglib2.0-0 2.36.1-1 ii libgnome-keyring03.4.1-1 ii libgtk2.0-0 2.24.22-1 ii libjpeg8 8d-1 ii libnspr4 2:4.9.6-1 ii libnss3 2:3.15.1-1 ii libpango-1.0-0 1.36.0-1+b1 ii libpangocairo-1.0-0 1.36.0-1+b1 ii libspeechd2 0.7.1-6.2 ii libspeex11.2~rc1-7 ii libstdc++6 4.8.2-14 ii libudev1 204-5 ii libx11-6 2:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxdamage1 1:1.1.3-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxml2 2.9.1+dfsg1-3 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.28-2 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.1-1 ii xdg-utils1.1.0~rc1+git20111210-7 chromium recommends no packages. Versions of packages chromium suggests: ii chromium-l10n 31.0.1650.57-1 -- Configuration Files: /etc/chromium/default changed [not included] -- no debconf information -- debsums errors found: sh: 1: /usr/sbin/dpkg-divert: not found -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
