Your message dated Mon, 24 Aug 2015 23:29:48 +0100 with message-id <[email protected]> and subject line Re: Bug#791917: dbus: Missing dependency on mountpoint from util-linux package has caused the Debian Bug report #791917, regarding dbus: Missing dependency on mountpoint from util-linux package to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 791917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791917 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dbus Version: 1.8.18-1 Severity: important Dear Maintainer, after updating, decided to restart system after 20 days uptime. During startup dbus failed to start as it is using mountpoint in starting script to determine if /proc/ exists. System comes to a KDE login screen without network, keyboard and mouse. Unplugging and reconnecting keyboard makes it usable again. So I was able to switch to console as plasma ends in segfault and black screen. Running /etc/init.d/dbus start reveals the two line error: "mountpoint: not found" and an error that comes from that if statement in the script. Network could be restored with setting specific ip address: ifconfig eth0 up ifconfig eth0 SOME_VALID_LOCAL_IP_ADDRESS dhclient Reinstalling package makes no difference apt-get install --reinstall dbus After finding out in which package the mountpoint resides apt-get install util-linux Rebooting after the installation of the missing package gets the system to a normal state. I have no idea if the mountpoint command was in previous versions used. I haven't done any cleanups of unused packages, so i think there is no way that it got uninstalled. I'm running wheezy with testing sources for a few months now. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages dbus depends on: ii adduser 3.113+nmu3 ii libaudit1 1:2.4.2-1 ii libc6 2.19-18 ii libcap-ng0 0.7.6-1 ii libdbus-1-3 1.8.18-1 ii libexpat1 2.1.0-6+b3 ii libselinux1 2.3-2+b1 ii libsystemd0 215-18 ii lsb-base 4.1+Debian13+nmu1 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-x11 1.8.18-1 Versions of packages dbus is related to: ii dbus-x11 1.8.18-1 ii systemd 215-18 pn systemd-sysv <none> -- no debconf information
--- End Message ---
--- Begin Message ---Control: reassign 791917 initscripts Control: found 791917 2.88dsf-59.1 Control: fixed 791917 2.88dsf-59.2 On Sun, 02 Aug 2015 at 00:41:23 +0100, Simon McVittie wrote: > This means you had this as the broken situation: > > initscripts 2.88dsf-59.1 > sysvinit-utils 2.88dsf-59 > util-linux 2.25.2-6 > > initscripts 2.88dsf-59.2 has a Breaks on util-linux (<< 2.26.2-4~), and > has now replaced 2.88dsf-59.1 in testing, so this shouldn't happen again. > > > Can we get the depends/breaks between them so that you can't install a > > combination that doesn't work? > > My understanding is that this was a bug in initscripts 2.88dsf-59.1 and > was fixed in 2.88dsf-59.2: namely, it dropped mountpoint from the > Essential set, but did not ensure that a sufficiently new util-linux to > provide mountpoint was installed. Now that initscripts 2.88dsf-59.1 is > no longer available in any suite, upgrades from stable shouldn't run > into this. In the absence of any feedback to the contrary, I'm going to consider this to be a bug in initscripts, which was present in 2.88dsf-59.1 but fixed in 2.88dsf-59.2. Without a time machine to go back and fix this before it happened, I don't think we can fix these partial upgrades. There doesn't seem to be much I can or should do about this in dbus; partly because it affects other packages, not just dbus (e.g. uswsusp, #793886), and partly because if people are doing partial upgrades that pick up the latest initscripts without the latest util-linux, there doesn't seem to be anything to guarantee that they'll upgrade to the latest dbus either. S
--- End Message ---
_______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
