Bug#880645: apt: Hash Sum mismatch when running apt-get update
Package: apt Version: 1.6~alpha3 Severity: important Dear Maintainer, * What led up to the situation? Running `apt-get update` gave me the following output: ``` Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 http://ftp.us.debian.org/debian buster InRelease Hit:3 https://download.docker.com/linux/debian stretch InRelease Ign:4 https://dl.google.com/linux/chrome/deb stable InRelease Hit:5 http://ftp.us.debian.org/debian buster-updates InRelease Hit:6 https://dl.google.com/linux/chrome/deb stable Release Hit:7 https://mirrors.wikimedia.org/debian experimental InRelease Get:9 https://mirrors.wikimedia.org/debian unstable InRelease [235 kB] Get:10 https://mirrors.wikimedia.org/debian unstable/contrib Sources [50.8 kB] Get:11 https://mirrors.wikimedia.org/debian unstable/non-free Sources [83.8 kB] Get:12 https://mirrors.wikimedia.org/debian unstable/main Sources [7,848 kB] Get:13 https://mirrors.wikimedia.org/debian unstable/main amd64 Packages [7,777 kB] Get:14 https://mirrors.wikimedia.org/debian unstable/main Translation-en [5,867 kB] Get:15 https://mirrors.wikimedia.org/debian unstable/main amd64 DEP-11 Metadata [3,107 kB] Get:16 https://mirrors.wikimedia.org/debian unstable/main DEP-11 64x64 Icons [6,936 kB] Get:17 https://mirrors.wikimedia.org/debian unstable/contrib amd64 Packages [58.5 kB] Get:18 https://mirrors.wikimedia.org/debian unstable/contrib Translation-en [50.9 kB] Get:19 https://mirrors.wikimedia.org/debian unstable/contrib amd64 DEP-11 Metadata [2,924 B] Get:20 https://mirrors.wikimedia.org/debian unstable/contrib DEP-11 64x64 Icons [37.7 kB] Get:21 https://mirrors.wikimedia.org/debian unstable/non-free amd64 Packages [81.9 kB] Get:22 https://mirrors.wikimedia.org/debian unstable/non-free Translation-en [83.8 kB] Get:23 https://mirrors.wikimedia.org/debian unstable/non-free amd64 DEP-11 Metadata [6,384 B] Get:24 https://mirrors.wikimedia.org/debian unstable/non-free DEP-11 64x64 Icons [1,813 B] Err:23 https://mirrors.wikimedia.org/debian unstable/non-free amd64 DEP-11 Metadata Hash Sum mismatch Hashes of expected file: - Filesize:65721 [weak] - SHA256:0eb5ea70b4c46a7c0889e9601d16cedf3eb4ff55bf3b77ef2af2bcd3dcf48cec - MD5Sum:68fdfbc3bc806010ba4c9fc8d4cb133b [weak] Hashes of received file: - SHA256:5fa520cd26eac94e183632f84371643219fdf905dfd351b53bbcd7afa5c3b848 - MD5Sum:875dd6824d698bfa73c6517307f692f5 [weak] - Filesize:65721 [weak] Last modification reported: Mon, 30 Oct 2017 21:09:03 + Release file created at: Fri, 03 Nov 2017 02:41:19 + Reading package lists... Done E: Failed to fetch store:/var/lib/apt/lists/partial/mirrors.wikimedia.org_debian_dists_unstable_non-free_dep11_Components-amd64.yml.xz Hash Sum mismatch Hashes of expected file: - Filesize:65721 [weak] - SHA256:0eb5ea70b4c46a7c0889e9601d16cedf3eb4ff55bf3b77ef2af2bcd3dcf48cec - MD5Sum:68fdfbc3bc806010ba4c9fc8d4cb133b [weak] Hashes of received file: - SHA256:5fa520cd26eac94e183632f84371643219fdf905dfd351b53bbcd7afa5c3b848 - MD5Sum:875dd6824d698bfa73c6517307f692f5 [weak] - Filesize:65721 [weak] Last modification reported: Mon, 30 Oct 2017 21:09:03 + Release file created at: Fri, 03 Nov 2017 02:41:19 + E: Some index files failed to download. They have been ignored, or old ones used instead. ``` * What exactly did you do (or not do) that was effective (or ineffective)? Update works when disabling xz compression with the following command: `apt-get update -o Acquire::CompressionTypes::Order::=gz` -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-4\.12\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.13\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.12\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.13\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.12\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.13\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.12\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.13\.0-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.12\.0-2-amd64$"; APT::NeverAutoRemove::
Bug#803165: Same issue
Same here on Iceweasel 44.0a2 (2015-11-04) -- Ilan Cohen
Bug#793878: KDE settings on debian stretch
Same issue here since installing updates and new packages for KDE. Kwin wouldn't load at first, this was easily fixed by creating a symlink from /usr/bin/kwin to /usr/bin/kwin_x11 System settings works but shows only a few icons. packes installed and updated to create the issue: Install: libkf5waylandclient5:amd64 (5.3.2-1, automatic) qml-module-qtgraphicaleffects:amd64 (5.4.2-2, automatic) libkwinxrenderutils6:amd64 (5.3.2-2, automatic) kwin-x11:amd64 (5.3.2-2, automatic) qml-module-qtquick-layouts:amd64 (5.4.2-2, automatic) libxcb-cursor0:amd64 (0.1.1-3, automatic) qml-module-qtquick-window2:amd64 (5.4.2-4, automatic) libkwineffects6:amd64 (5.3.2-2, automatic) qml-module-qtquick2:amd64 (5.4.2-4, automatic) libkdecorations2private5:amd64 (5.3.2-1, automatic) libqt5multimedia5:amd64 (5.4.2-2, automatic) libkf5activities5:amd64 (5.12.0-2, automatic) libkwin4-effect-builtins1:amd64 (5.3.2-2, automatic) libkdecorations2-5:amd64 (5.3.2-1, automatic) qml-module-qtmultimedia:amd64 (5.4.2-2, automatic) libqt5multimediaquick-p5:amd64 (5.4.2-2, automatic) qml-module-qtquick-controls:amd64 (5.4.2-2, automatic) libkf5waylandserver5:amd64 (5.3.2-1, automatic) kwin-data:amd64 (5.3.2-2, automatic) qml-module-org-kde-kquickcontrols:amd64 (5.12.0-2, automatic) kwin-common:amd64 (5.3.2-2, automatic) plasma-framework:amd64 (5.12.0-1, automatic) libkf5plasma5:amd64 (5.12.0-1, automatic) libkwinglutils6:amd64 (5.3.2-2, automatic) libkf5plasmaquick5:amd64 (5.12.0-1, automatic) qml-module-org-kde-kquickcontrolsaddons:amd64 (5.12.0-2, automatic) libinput10:amd64 (0.17.0-1, automatic) Upgrade: libunwind8:amd64 (1.1-3.2, 1.1-4) libasan1:amd64 (4.9.3-2, 4.9.3-3) libqt5opengl5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5sql5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5qml5:amd64 (5.4.2-3, 5.4.2-4) libqt5core5a:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) kde-window-manager:amd64 (4.11.13-2, 5.3.2-2) libqt5xml5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) xserver-xorg-video-qxl:amd64 (0.1.4-1, 0.1.4-3) libqt5quick5:amd64 (5.4.2-3, 5.4.2-4) libqt5sql5-psql:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5test5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5printsupport5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5widgets5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5dbus5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) kscreen:amd64 (5.3.2-2, 5.3.2-4) libqt5gui5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) libqt5network5:amd64 (5.4.2+dfsg-4, 5.4.2+dfsg-5) ksnapshot:amd64 (4.12.2-2, 15.04.3-1) libdebconfclient0:amd64 (0.194, 0.195) -- Ilan Cohen
Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Hi, I have applied your patch changing the last line of /lib/udev/lmt-udev and my system still boots with / in read only mode. running: systemd 215 udevd 215 I have the same symptoms as you describe: # systemctl status systemd-remount-fs.service ● systemd-remount-fs.service - Remount Root and Kernel File Systems Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; static) Active: failed (Result: exit-code) since Fri 2014-09-26 12:54:16 IDT; 1min 32s ago Docs: man:systemd-remount-fs.service(8) http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Process: 510 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE) Main PID: 510 (code=exited, status=1/FAILURE) Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: mount: /usr not mounted or bad option Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: /bin/mount for /usr exited with exit status 32. Sep 26 12:54:16 thinkpad systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=1/FAILURE Sep 26 12:54:16 thinkpad systemd[1]: Failed to start Remount Root and Kernel File Systems. Sep 26 12:54:16 thinkpad systemd[1]: Unit systemd-remount-fs.service entered failed state. and in syslog from boot: [2.345523] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. -- Ilan Cohen
Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
Hi,
I have found the problem, and a solution.
The problem is not lmt, nor systemd. It's initramfs-tools not properly
mounting /usr (if LVM).
In initramfs-tools version 0.117 an option has been added to mount usr if
in fstab.
The initramfs init scripts are in /usr/share/initramfs-tools. The file
responsible for activating volume groups
is scripts/local-top/lvm2
It activates the root and optionally the resume volume group only, which
means the usr volume stays inactive
and can't be mounted.
I fixed this with a quick patch, adding lvm vgchange -ay (patch attached)
Ilan
On Fri, Sep 26, 2014 at 2:36 PM, Ritesh Raj Sarraf r...@researchut.com
wrote:
Hi,
Thank you for reporting this.
On Friday 26 September 2014 03:31 PM, Ilan Cohen wrote:
Hi,
I have applied your patch changing the last line of /lib/udev/lmt-udev
and my system still boots with / in read only mode.
Matthew: Can you please confirm your results ??
running:
systemd 215
udevd 215
I have the same symptoms as you describe:
# systemctl status systemd-remount-fs.service
● systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Fri 2014-09-26 12:54:16 IDT;
1min 32s ago
Docs: man:systemd-remount-fs.service(8)
http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
Process: 510 ExecStart=/lib/systemd/systemd-remount-fs (code=exited,
status=1/FAILURE)
Main PID: 510 (code=exited, status=1/FAILURE)
Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: mount: /usr not
mounted or bad option
Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: /bin/mount for /usr
exited with exit status 32.
Sep 26 12:54:16 thinkpad systemd[1]: systemd-remount-fs.service: main
process exited, code=exited, status=1/FAILURE
Sep 26 12:54:16 thinkpad systemd[1]: Failed to start Remount Root and
Kernel File Systems.
Sep 26 12:54:16 thinkpad systemd[1]: Unit systemd-remount-fs.service
entered failed state.
and in syslog from boot:
[2.345523] systemd[1]: /usr appears to be on its own filesytem and
is not already mounted. This is not a supported setup. Some things will
probably break (sometimes even silently) in mysterious ways. Consult
http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for
more information.
--
Ilan Cohen
I don't know how I should interpret this last statement. When systemd
itself reports it as a setup not supported, what should we expect out of it
?
What lmt-udev currently does, and with Matt's patch, it should work. Can
you capture the output from the initial boot to confirm _if_ it is an LMT
problem ? I do not have a setup where /usr is on a separate partition.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
Necessity is the mother of invention.
--
Ilan Cohen
--- lvm2 2014-09-26 14:53:20.648542077 +0300
+++ lvm2.patch 2014-09-26 14:55:00.736539886 +0300
@@ -1,66 +0,0 @@
-#!/bin/sh
-
-PREREQ=mdadm mdrun multipath
-
-prereqs()
-{
- echo $PREREQ
-}
-
-case $1 in
-# get pre-requisites
-prereqs)
- prereqs
- exit 0
- ;;
-esac
-
-activate_vg()
-{
- local dev=$1
-
- # Make sure that we have a non-empty argument
- if [ -z $dev ]; then
- return 1
- fi
-
- # Take care of lilo boot arg, risky activating of all vg
- case $dev in
- fe[0-9]*)
- lvm vgchange -aly --ignorelockingfailure
- exit 0
- ;;
- # FIXME: check major
- /dev/root)
- lvm vgchange -aly --ignorelockingfailure
- exit 0
- ;;
- esac
-
- # Make sure that we have a d-m path
- dev=${dev#/dev/mapper/}
- if [ $dev = $1 ]; then
- return 1
- fi
-
- eval $(dmsetup splitname --nameprefixes --noheadings --rows $dev)
-
- if [ $DM_VG_NAME ] [ $DM_LV_NAME ]; then
- lvm lvchange -aly --ignorelockingfailure $DM_VG_NAME/$DM_LV_NAME
- rc=$?
- if [ $rc = 5 ]; then
- echo Unable to find LVM volume $DM_VG_NAME/$DM_LV_NAME
- fi
- fi
-}
-
-if [ ! -e /sbin/lvm ]; then
- exit 0
-fi
-
-modprobe -q dm-mod
-
-activate_vg $ROOT
-activate_vg $resume
-
-exit 0
Bug#755518: laptop-mode-tools: USB Autosuspend + LVM2 filesystems = failed boot
sorry the attached patch earlier was the wrong file. Reattaching correct patch. On Fri, Sep 26, 2014 at 2:36 PM, Ritesh Raj Sarraf r...@researchut.com wrote: Hi, Thank you for reporting this. On Friday 26 September 2014 03:31 PM, Ilan Cohen wrote: Hi, I have applied your patch changing the last line of /lib/udev/lmt-udev and my system still boots with / in read only mode. Matthew: Can you please confirm your results ?? running: systemd 215 udevd 215 I have the same symptoms as you describe: # systemctl status systemd-remount-fs.service ● systemd-remount-fs.service - Remount Root and Kernel File Systems Loaded: loaded (/lib/systemd/system/systemd-remount-fs.service; static) Active: failed (Result: exit-code) since Fri 2014-09-26 12:54:16 IDT; 1min 32s ago Docs: man:systemd-remount-fs.service(8) http://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Process: 510 ExecStart=/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE) Main PID: 510 (code=exited, status=1/FAILURE) Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: mount: /usr not mounted or bad option Sep 26 12:54:16 thinkpad systemd-remount-fs[510]: /bin/mount for /usr exited with exit status 32. Sep 26 12:54:16 thinkpad systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=1/FAILURE Sep 26 12:54:16 thinkpad systemd[1]: Failed to start Remount Root and Kernel File Systems. Sep 26 12:54:16 thinkpad systemd[1]: Unit systemd-remount-fs.service entered failed state. and in syslog from boot: [2.345523] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. -- Ilan Cohen I don't know how I should interpret this last statement. When systemd itself reports it as a setup not supported, what should we expect out of it ? What lmt-udev currently does, and with Matt's patch, it should work. Can you capture the output from the initial boot to confirm _if_ it is an LMT problem ? I do not have a setup where /usr is on a separate partition. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. -- Ilan Cohen --- /usr/share/initramfs-tools/scripts/local-top/lvm2 2014-09-26 14:53:20.648542077 +0300 +++ /usr/share/initramfs-tools/scripts/local-top/lvm2.new 2014-09-26 15:00:22.752532840 +0300 @@ -62,5 +62,6 @@ activate_vg $ROOT activate_vg $resume +lvm vgchange -ay exit 0
Bug#758707: Fwd: plasma-desktop: crash on startup
Package: plasma-desktop Version: 4:4.11.11-1 Severity: important Application: plasma-desktop (4.11.11) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.14-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (jessie) -- Information about the crash: Logged into kdm, when kde started plasma-desktop crashed. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f549a990900 (LWP 1991))] Thread 3 (Thread 0x7f546ed1e700 (LWP 1993)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f5493d7a7fa in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f5493d7a829 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f548e5ec0a4 in start_thread (arg=0x7f546ed1e700) at pthread_create.c:309 #4 0x7f549a285fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f53ecfc7700 (LWP 1997)): #0 0x7f549a27d47d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f548dcce154 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f548dcce26c in g_main_context_iteration () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #3 0x7f5496db2017 in QEventDispatcherGlib::processEvents (this=0x7f53e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f5496d834f1 in QEventLoop::processEvents (this=this@entry=0x7f53ecfc6ca0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f5496d83805 in QEventLoop::exec (this=this@entry=0x7f53ecfc6ca0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f5496c81c39 in QThread::exec (this=this@entry=0xa47c00) at thread/qthread.cpp:538 #7 0x7f5496d65033 in QInotifyFileSystemWatcherEngine::run (this=0xa47c00) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f5496c8439f in QThreadPrivate::start (arg=0xa47c00) at thread/qthread_unix.cpp:349 #9 0x7f548e5ec0a4 in start_thread (arg=0x7f53ecfc7700) at pthread_create.c:309 #10 0x7f549a285fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f549a990900 (LWP 1991)): [KCrash Handler] #6 QVariant::userType (this=0x7200650065) at kernel/qvariant.cpp:1798 #7 0x7f546fc08cea in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #8 0x7f546fc00a39 in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #9 0x7f546fc00aab in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #10 0x7f549710fbf6 in QDBusConnectionPrivate::deliverCall (this=0xa037f0, object=0xef4060, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:951 #11 0x7f5496d9cf41 in QObject::event (this=0xef4060, e=optimized out) at kernel/qobject.cpp:1222 #12 0x7f5496118c0c in QApplicationPrivate::notify_helper (this=this@entry=0xa202a0, receiver=receiver@entry=0xef4060, e=e@entry=0x10dbae0) at kernel/qapplication.cpp:4570 #13 0x7f549611f360 in QApplication::notify (this=this@entry=0xa06a20, receiver=receiver@entry=0xef4060, e=e@entry=0x10dbae0) at kernel/qapplication.cpp:4356 #14 0x7f5497a8a79a in KApplication::notify (this=0xa06a20, receiver=0xef4060, event=0x10dbae0) at ../../kdeui/kernel/kapplication.cpp:311 #15 0x7f5496d8486d in QCoreApplication::notifyInternal (this=0xa06a20, receiver=receiver@entry=0xef4060, event=event@entry=0x10dbae0) at kernel/qcoreapplication.cpp:953 #16 0x7f5496d87f41 in sendEvent (event=0x10dbae0, receiver=0xef4060) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x989300) at kernel/qcoreapplication.cpp:1577 #18 0x7f5496d883d3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #19 0x7f5496db1eb3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #20 postEventSourceDispatch (s=0xa17020) at kernel/qeventdispatcher_glib.cpp:280 #21 0x7f548dccdecd in g_main_context_dispatch () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #22 0x7f548dcce1b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f548dcce26c in g_main_context_iteration () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #24 0x7f5496db2061 in QEventDispatcherGlib::processEvents (this=0x98ab30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #25 0x7f54961b82c6 in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #26 0x7f5496d88411 in QCoreApplication::processEvents (flags=...) at kernel/qcoreapplication.cpp:1140 #27 0x7f548f067b16 in waitForWatcher (_watcher=_watcher@entry=0x17e78f0, maxWait=maxWait@entry=3000) at /tmp/buildd/libdbusmenu- qt-0.9.2/src/dbusmenuimporter.cpp:447 #28 0x7f548f06a1b6 in
Bug#757924:
more debug info after installing additional -dbg packages -- Ilan Cohen Application: plasma-desktop (4.11.11) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.14-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (jessie) -- Information about the crash: In detail, tell us what you were doing when the application crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7ff1d70f3900 (LWP 2558))] Thread 3 (Thread 0x7ff1ab52c700 (LWP 2560)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff1d05487fa in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7ff1d0548829 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7ff1cadba0a4 in start_thread (arg=0x7ff1ab52c700) at pthread_create.c:309 #4 0x7ff1d69e704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7ff129807700 (LWP 2564)): #0 0x7ff1d69de50d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7ff1ca49dfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff1ca49e0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff1d3513017 in QEventDispatcherGlib::processEvents (this=0x7ff1240008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7ff1d34e44f1 in QEventLoop::processEvents (this=this@entry=0x7ff129806ca0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ff1d34e4805 in QEventLoop::exec (this=this@entry=0x7ff129806ca0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ff1d33e2c39 in QThread::exec (this=this@entry=0x2870a40) at thread/qthread.cpp:538 #7 0x7ff1d34c6033 in QInotifyFileSystemWatcherEngine::run (this=0x2870a40) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7ff1d33e539f in QThreadPrivate::start (arg=0x2870a40) at thread/qthread_unix.cpp:349 #9 0x7ff1cadba0a4 in start_thread (arg=0x7ff129807700) at pthread_create.c:309 #10 0x7ff1d69e704d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7ff1d70f3900 (LWP 2558)): [KCrash Handler] #6 QVariant::userType (this=0x30) at kernel/qvariant.cpp:1798 #7 0x7ff1ac416cea in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #8 0x7ff1ac40ea39 in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #9 0x7ff1ac40eaab in ?? () from /usr/lib/kde4/plasma_applet_menubar.so #10 0x7ff1d3870bf6 in QDBusConnectionPrivate::deliverCall (this=0x1ee07f0, object=0x2424540, msg=..., metaTypes=..., slotIdx=11) at qdbusintegrator.cpp:951 #11 0x7ff1d34fdf41 in QObject::event (this=0x2424540, e=optimized out) at kernel/qobject.cpp:1222 #12 0x7ff1d2879c0c in QApplicationPrivate::notify_helper (this=this@entry=0x1efd2a0, receiver=receiver@entry=0x2424540, e=e@entry=0x47c1710) at kernel/qapplication.cpp:4570 #13 0x7ff1d2880360 in QApplication::notify (this=this@entry=0x1ee3a20, receiver=receiver@entry=0x2424540, e=e@entry=0x47c1710) at kernel/qapplication.cpp:4356 #14 0x7ff1d41eb79a in KApplication::notify (this=0x1ee3a20, receiver=0x2424540, event=0x47c1710) at ../../kdeui/kernel/kapplication.cpp:311 #15 0x7ff1d34e586d in QCoreApplication::notifyInternal (this=0x1ee3a20, receiver=receiver@entry=0x2424540, event=event@entry=0x47c1710) at kernel/qcoreapplication.cpp:953 #16 0x7ff1d34e8f41 in sendEvent (event=0x47c1710, receiver=0x2424540) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1e66300) at kernel/qcoreapplication.cpp:1577 #18 0x7ff1d34e93d3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470 #19 0x7ff1d3512eb3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #20 postEventSourceDispatch (s=0x1ef4020) at kernel/qeventdispatcher_glib.cpp:280 #21 0x7ff1ca49de04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7ff1ca49e048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7ff1ca49e0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7ff1d3512ffd in QEventDispatcherGlib::processEvents (this=0x1e67b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #25 0x7ff1d29192c6 in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #26 0x7ff1d34e44f1 in QEventLoop::processEvents (this=this@entry=0x7fff966ffd10, flags=...) at kernel/qeventloop.cpp:149 #27 0x7ff1d34e4805 in QEventLoop::exec (this=this@entry=0x7fff966ffd10, flags=...) at kernel/qeventloop.cpp:204
Bug#755426: upower: unable to suspend/hibernate laptop from KDE after upgrade
Hi, After some more package upgrades (including kde packages), I decided to try upgrading upower again. As of today it works, not sure what package enabled sleep. This bug can be closed. On Fri, 25 Jul 2014 21:05:04 +0200 Aaron regtothism...@gmail.com wrote: Hi, The bug seems to be related to the init system. It seems to affect only the systems that have sysvinit as init system. See discussion here: https://lists.debian.org/debian-kde/2014/07/msg00030.html Regards, Aaron -- Ilan Cohen
Bug#755426: upower: unable to suspend/hibernate laptop from KDE after upgrade
Hi, My system got upgraded to systemd so I tried to upgrade upower again. Same deal, still doesnt work and pkaction | grep upower still shows nothing. -- Ilan Cohen
Bug#755426: upower: unable to suspend/hibernate laptop from KDE after upgrade
Hello, Same bug affects KDE as well. Reverting the upower to 0.9.23-2+b2 fixes the problem Running version 4.13.1 of KDE. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages upower depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii libgudev-1.0-0 204-14 ii libimobiledevice4 1.1.6+dfsg-2 ii libplist2 1.11-3 ii libpolkit-gobject-1-0 0.105-6 ii libupower-glib10.9.23-2+b2 ii libusb-1.0-0 2:1.0.19-1 ii pm-utils 1.4.1-15 ii systemd204-14 ii udev 204-14 Versions of packages upower recommends: ii policykit-1 0.105-6 upower suggests no packages.
Bug#743180: libgl1-mesa-glx: White boxes and stripes after upgrading to mesa 10
Reported upstream: Bug ID: 77109 https://bugs.freedesktop.org/show_bug.cgi?id=77109 On Sun, Apr 6, 2014 at 7:02 PM, Andreas Boll andreas.boll@gmail.comwrote: Please report this upstream at bugs.freedesktop.org following the instructions at https://01.org/linuxgraphics/documentation/how-report-bugs and let us know the bug number for tracking. Thanks, Andreas. -- Ilan Cohen
Bug#704304: e1000e driver hangs and system becomes unstable
Hi, Narrowed down the issue to laptop-mode-tools. If ethernet control is disabled the issue is solved. Tried with kernel 3.2.41-2, now available in testing, same results. Apr 5 18:51:02 laptop kernel: [7.928034] [ cut here ] Apr 5 18:51:02 laptop kernel: [7.928063] WARNING: at /build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-3.2.41/drivers/net/ethernet/intel/e1000e/netdev.c:5333 __e1000_shutdown+0x6f/0x3ea [e1000e]() Apr 5 18:51:02 laptop kernel: [7.928067] Hardware name: 7465CTO Apr 5 18:51:02 laptop kernel: [7.928069] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables tun bridge stp parport_pc ppdev lp parport bnep rfcomm uinput ext2 tp_smapi(O) thinkpad_ec(O) loop kvm_intel kvm snd_hda_codec_conexant arc4 thinkpad_acpi nvram snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd iwlwifi mac80211 psmouse iTCO_wdt btusb serio_raw bluetooth pcspkr cfg80211 coretemp i2c_i801 iTCO_vendor_support evdev soundcore rfkill i915 battery ac power_supply drm_kms_helper drm acpi_cpufreq wmi mperf video i2c_algo_bit i2c_core button processor ext4 crc16 jbd2 mbcache dm_mod microcode sg sd_mod crc_t10dif ahci libahci thermal thermal_sys uhci_hcd ata_generic libata scsi_mod ehci_hcd e1000e usbcore usb_common [last unloaded: scsi_wait_scan] Apr 5 18:51:02 laptop kernel: [7.928140] Pid: 11, comm: kworker/0:1 Tainted: G O 3.2.0-4-amd64 #1 Debian 3.2.41-2 Apr 5 18:51:02 laptop kernel: [7.928142] Call Trace: Apr 5 18:51:02 laptop kernel: [7.928149] [81046a55] ? warn_slowpath_common+0x78/0x8c Apr 5 18:51:02 laptop kernel: [7.928160] [a007cfc8] ? __e1000_shutdown+0x6f/0x3ea [e1000e] Apr 5 18:51:02 laptop kernel: [7.928171] [a007d374] ? e1000_runtime_suspend+0x31/0x39 [e1000e] Apr 5 18:51:02 laptop kernel: [7.928177] [811c5ce8] ? pci_pm_runtime_suspend+0x43/0xd6 Apr 5 18:51:02 laptop kernel: [7.928181] [811c5ca5] ? pci_legacy_suspend_late+0xbd/0xbd Apr 5 18:51:02 laptop kernel: [7.928186] [81257662] ? __rpm_callback+0x2c/0x50 Apr 5 18:51:02 laptop kernel: [7.928189] [81257bc1] ? rpm_suspend+0x271/0x401 Apr 5 18:51:02 laptop kernel: [7.928194] [8103981a] ? finish_task_switch+0x4e/0xb9 Apr 5 18:51:02 laptop kernel: [7.928197] [812588d7] ? pm_runtime_work+0x65/0x7e Apr 5 18:51:02 laptop kernel: [7.928202] [8105b225] ? process_one_work+0x161/0x264 Apr 5 18:51:02 laptop kernel: [7.928205] [8105c1e6] ? worker_thread+0xc2/0x145 Apr 5 18:51:02 laptop kernel: [7.928209] [8105c124] ? manage_workers.isra.25+0x15b/0x15b Apr 5 18:51:02 laptop kernel: [7.928213] [8105f321] ? kthread+0x76/0x7e Apr 5 18:51:02 laptop kernel: [7.928217] [81354ab4] ? kernel_thread_helper+0x4/0x10 Apr 5 18:51:02 laptop kernel: [7.928222] [8105f2ab] ? kthread_worker_fn+0x139/0x139 Apr 5 18:51:02 laptop kernel: [7.928225] [81354ab0] ? gs_change+0x13/0x13 Apr 5 18:51:02 laptop kernel: [7.928227] ---[ end trace 2ee513d3cae1946f ]--- Will let you know what happens with kernel 3.8.y once i upgrade. Ilan On Mon, Apr 1, 2013 at 5:50 AM, Jonathan Nieder jrnie...@gmail.com wrote: Ilan Cohen wrote: have done some more research, disabled the wol in pm-utils and disabled ethernet control in laptop-mode-tools and the problem has gone away. There was an e1000e fix in __e1000e_shutdown() in 3.2.41. Can you reproduce this with 3.2.41-2 from unstable? (If not, the fix will be coming to wheezy soon and we can close the bug.) If 3.2.41-2 produces the same symptoms, can you reproduce them with 3.8.y from experimental? (If not, we can try to find the fix and apply it to wheezy.) If 3.8.y produces the same symptoms, please send a summary of what you have tried and what happened to the upstream developers at e1000-de...@lists.sourceforge.net, cc-ing either me or this bug log so we can track it. Hopefully they will have ideas for tracking it down further. Thanks and hope that helps, Jonathan -- Ilan Cohen
Bug#704304: tested with kernel 3.8.y from expiremental
Hi, Tested with 3.8.y from expiremental. These are the results: 1. Ethernet works as expected without error messages, even with laptop-mode-tools controlling ethernet 2. Errors from e1000e on shutdown: Apr 5 19:20:03 laptop shutdown[4223]: shutting down for system reboot Apr 5 19:20:05 laptop kernel: [ 33.554616] Ebtables v2.0 unregistered Apr 5 19:20:06 laptop kernel: [ 34.434391] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:06 laptop kernel: [ 34.440663] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro,data=ordered,commit=0 Apr 5 19:20:07 laptop kernel: [ 35.229709] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:07 laptop kernel: [ 35.233200] wlan0: deauthenticating from 00:18:f8:e5:c8:45 by local choice (reason=3) Apr 5 19:20:07 laptop kernel: [ 35.235519] EXT4-fs (dm-4): re-mounted. Opts: data=ordered,commit=0 Apr 5 19:20:07 laptop kernel: [ 35.250113] cfg80211: Calling CRDA to update world regulatory domain Apr 5 19:20:07 laptop kernel: [ 35.262979] EXT4-fs (dm-5): re-mounted. Opts: data=ordered,commit=0 Apr 5 19:20:07 laptop kernel: [ 35.281082] EXT4-fs (dm-2): re-mounted. Opts: data=ordered,commit=0 Apr 5 19:20:07 laptop kernel: [ 35.302156] cfg80211: World regulatory domain updated: Apr 5 19:20:07 laptop kernel: [ 35.302160] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Apr 5 19:20:07 laptop kernel: [ 35.302163] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Apr 5 19:20:07 laptop kernel: [ 35.302166] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Apr 5 19:20:07 laptop kernel: [ 35.302169] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Apr 5 19:20:07 laptop kernel: [ 35.302172] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) Apr 5 19:20:07 laptop kernel: [ 35.302174] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Apr 5 19:20:08 laptop kernel: [ 36.060106] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:08 laptop kernel: [ 36.065235] EXT4-fs (dm-3): re-mounted. Opts: data=ordered,commit=0 Apr 5 19:20:09 laptop kernel: [ 36.855003] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:09 laptop kernel: [ 37.649951] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:10 laptop kernel: [ 38.444844] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:11 laptop kernel: [ 38.808254] uhci_hcd :00:1d.0: power state changed by ACPI to D2 Apr 5 19:20:11 laptop kernel: [ 39.239734] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:12 laptop kernel: [ 40.034930] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:13 laptop kernel: [ 40.829837] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:13 laptop kernel: [ 41.625049] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:14 laptop kernel: [ 42.419960] e1000e :00:19.0 eth0: Error reading PHY register Apr 5 19:20:15 laptop kernel: [ 43.215030] e1000e :00:19.0 eth0: Error reading PHY register 3. output of: # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 2 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: d Current message level: 0x0007 (7) drv probe link Link detected: no 4. example error from laptop-mode-tools command ethtool -s eth0 speed 1000 root@laptop:~# ethtool -s eth0 speed 1000 Cannot advertise speed 1000 root@laptop:~# Hope this helps, -- Ilan Cohen
Bug#704304: pm-utils
have done some more research, disabled the wol in pm-utils and disabled ethernet control in laptop-mode-tools and the problem has gone away. -- Ilan Cohen
Bug#465750: proftpd: uninstall does not remove user
On Thu, Feb 14, 2008 at 9:46 PM, Francesco P. Lovergine [EMAIL PROTECTED] wrote: On Thu, Feb 14, 2008 at 05:39:11PM +0200, Ilan wrote: Package: proftpd Version: 1.3.0-19 Severity: important When uninstall proftpd the script tries to remove user proftpd which does not exist. Installation of proftpd creates the ftp user. The proftpd user should be created as a system user when installed. It probably failed on your system at that time for some reason (some exotic auth schema used?). It is used in 1.3.0 instead of nobody. The ftp user is not removed because the anonymous user could be used for some reason by the admin. -- Francesco P. Lovergine You are right, the user is created and deleted when uninstalling the package. When the configuration files are purged the script tries to remove the user again ... # Removing proftpd ... Purging configuration files for proftpd ... userdel: user proftpd does not exist Ilan -- The most effective way to find and destroy a land mine is to step on it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
