Your message dated Mon, 2 Jul 2012 22:19:29 +0100
with message-id <[email protected]>
and subject line Re: Bug#672358: dbus: some machines do not shutdown
has caused the Debian Bug report #672358,
regarding dbus: some machines do not shutdown properly and do not do poweroff
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.)
--
672358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672358
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbus
Version: 1.5.12-1
Justification: breaks the whole system
Severity: critical
Dear Maintainer,
I have some desktop, server and notebooks running debian.
All machines have nvidia graphic cards and driver are proprietary from nvidia.
Until 05/2012 I run debian squeeze on all machines.
In 05/2012 I begin update to debian wheezy with fresh install.
Kernel used is taken from kernel.org without any patches, configuration is
taken from debian experimental.
All machines uses kde as window system.
With debian wheezy (testing), last dist-upgrade 09.05.2012, on all type of
machines, I have got problems with full shutdown by running
shutdown -h now
or
shutdown -hP now
on notebook system, which is an Acer Aspire 8930G-944. The system hang on try
to kill remaining processes.
Desktop system do the shutdown.
For I'am using a new kernel on the notebook, I think this may be a kernel/bios
problem and I try the typical acpi, etc. kernel options with no success.
After this probes I think it maybe a problem with nvidia driver and try
several versions, no success.
At least I inspect the run level and found that there is no dbus kill link in
run level 0 for dbus.
I added a link to stop dbus lately after kdm and after adding this kill link
the shutdown process finished successfully.
Inspecting lsb header of dbus script in /etc/init.d I see that there is no
entry for Default-Stop.
It seem that the finishing kill on remaining processes at end of shutdown do
not stop dbus and related processes.
I add a file dbus to /etc/insserv/overrides with content
### BEGIN INIT INFO
# Provides: dbus
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: D-Bus systemwide message bus
# Description: D-Bus is a simple interprocess messaging system, used
# for sending messages between applications.
### END INIT INFO
It is not clear to me whether this file is honored on update of dbus because I
have problems understanding the complex handling of program update-rc.d.
Please enter proper stop directives (0 1 6) to lsb header in init script and
postinst script to honor this change.
Thanks in advance
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.5-ksamd64 (SMP w/8 CPU cores)
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+nmu1
ii libc6 2.13-32
ii libdbus-1-3 1.5.12-1
ii libexpat1 2.1.0-1
ii libselinux1 2.1.9-2
ii libsystemd-login0 37-1.1
ii lsb-base 4.1+Debian2
dbus recommends no packages.
Versions of packages dbus suggests:
ii dbus-x11 1.5.12-1
--- End Message ---
--- Begin Message ---
On Mon, Jul 02, 2012 at 10:55:07PM +0200, Jürgen Kaiser wrote:
> please close this bug forwarded from dbus maintainers because I do not know
> how to close a bug report triggered by myself.
Just send a mail (like this one) to [email protected]
> As I mentioned at end of my last email (Message #20 from Thu, 10 May 2012)
> this bug anounced by myself seems to be more a hardware
> problem of my notebook machine and not a bug in debian system software!
>
> I have serialized the shutdown and had no problems anymore to shutdown.
While it's possibly related to the hardware, the software should
still not be hanging at shutdown. However, without being able to
reproduce it, it's hard to investigate this further. If you do
ever find out more about this, please do reopen the bug and
provide any additional information you need.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
