Your message dated Thu, 15 Oct 2009 17:43:12 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#550907: Bug#550907:
Bug#550907: dbus: fails to start at boot and doesn't works very well
after it's, started manually
has caused the Debian Bug report #550907,
regarding dbus: fails to start at boot and doesn't works very well after it's,
started manually
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.)
--
550907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dbus
Version: 1.2.16-2
Severity: important
Hello,
Since last update, dbus fails to start at boot (hal problem ?).
At a boot :
When X server and GDM started, I loose keyboard (ctrl+alt+Fx function
doesn't works, only "magic keys" are ok), mouse and network with
networkmanager doesn't work (I must use "/etc/network/interfaces method"
to have an active iface ok at boot).
After restart it, keyboard, mouse and networkmanager works perfectly, I
can logging my gnome session.
On my session, the function "ajusting brightness" on the laptop is often
corrupted. The luminosity of the laptop's screen varies between 80% and
100% in the form of regular blinking (I do _nothing_, just starting a
session). The second problem is dbus eats all of the CPU.
These problems can be partially resolved with restarting dbus. But,
Nautilus crashes, the brightness applet can't connect to dbus/hal and
suspend to ram doesn't work after.
If I launch a video from VLC (from example), the OSD for the brightness
applet appears as I use the applet.
I'm not sure, but I think theses bug reports are about the ame problem :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537572
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539044
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dbus depends on:
ii adduser 3.111 add and remove users and groups
ii libc6 2.9-27 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.16-2 simple interprocess
messaging syst
ii libexpat1 2.0.1-4 XML parsing C library -
runtime li
ii libselinux1 2.0.85-4 SELinux runtime shared
libraries
ii lsb-base 3.2-23 Linux Standard Base 3.2
init scrip
dbus recommends no packages.
Versions of packages dbus suggests:
ii dbus-x11 1.2.16-2 simple interprocess
messaging syst
-- no debconf information
--- End Message ---
--- Begin Message ---
Fred wrote:
> Michael Biebl a écrit :
>> Hm, check the boot log. dbus is never started during boot.
>> Have you removed the start symlinks?
>>
> I never removed any symlink before and when the problem apeared. Ok, I
> remember one thing but finally it'll be not "really" the problem because
> it's was made _after_ the problem . When I saw that dbus doesn't
> started, I tried an update-rc.d command with "default" option but I saw
> no change... Now I've just replaced the good configuration with your
> command "
>
> update-rc.d dbus start 12 2 3 4 5 . stop 88 1 .
>
> " but it's the same problem (really the same problem).
>> What's the output of
>> ls /etc/rc?.d/???dbus
>>
>>
> ls /etc/rc?.d/???dbus
> /etc/rc1.d/K03dbus /etc/rc3.d/S03dbus /etc/rc4.d/S03dbus
> /etc/rc5.d/S03dbus
>> As I said before, this looks like a misconfiguration of your system.
It is: the default runlevel is 2, and you are missing the symlink (for whatever
reasons, but definitely not a packaging issue) in rc2.d.
Remove the existing ones:
update-rc.d -f dbus remove
and add the old ones with the command above.
I see from the start/stop priorities, that you are using the dependency based
boot sequencing. Have you maybe edited the dbus init script header. What's the
output of
grep Default-Start /etc/init.d/dbus
Make sure it is 2 3 4 5
and you should be fine.
Closing as not a bug.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
