Your message dated Wed, 26 Jun 2013 21:57:47 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#714192: upower faiuls to
detect devices => breaks battery monitor plasma applet
has caused the Debian Bug report #714192,
regarding upower faiuls to detect devices => breaks battery monitor plasma
applet
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.)
--
714192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714192
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 0.9.20-2
Severity: critical
Justification: causes serious data loss
upower is currently broken on at least tree machines I have. ACPI info for
battery is there, acpi -V works correctly
but upower fails with :
upower --monitor-detail
(upower:7148): libupower-glib-WARNING **: Couldn't enumerate devices: Launch
helper exited with unknown return code 127
(upower:7148): UPower-WARNING **: failed to enumerate: Launch helper exited
with unknown return code 127
Conseqaunetly the battery monitor applet reports incorrect information on
battery state and kde is unable
to preventively shutdown properly the laptop => risk of data lost.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.9.7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages upower depends on:
ii dbus 1.7.4-1
ii libc6 2.17-5
ii libdbus-1-3 1.7.4-1
ii libdbus-glib-1-2 0.100.2-1
ii libglib2.0-0 2.36.3-1
ii libgudev-1.0-0 175-7.2
ii libimobiledevice2 1.1.5-1
ii libplist1 1.8-2
ii libpolkit-gobject-1-0 0.110-3
ii libupower-glib1 0.9.20-2
ii libusb-1.0-0 2:1.0.15-1
ii pm-utils 1.4.1-9
ii udev 175-7.2
Versions of packages upower recommends:
ii policykit-1 0.110-3
upower suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 26.06.2013 21:50, schrieb Eric Valette:
>
>>>> What's the output of
>>>> # ps aux | grep dbus-daemon | grep system
>
> That command tries to see if dbus is working. Not waste time because
> reinstalling without dbus running kde ouputs lots of ertor/alram and
>
>>>> Please also post the output of the following three commands:
>>>> # getent group messagebus
>>>> # getent passwd messagebus
>>>> # ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper
>
>
> Again you are searching problem with dbus but dbus is working fine and
> reinstalling git version of the package compiled reusing 0.9.20 debian
> directory works fine. So do not search a problem outside your packages.
> It may just be a compatibility problem between some experimental
> packages I have on my system and upower. I did not try just rebuilding
> as I saw problem fixed in upower git chnagelog...
>
>>>> Have you checked your system with debsums?
>
> I have the same problem on several system and it occurred recently. I
> just did not know that battery monitor was using upower so wasted some
> time tryiong to understand what was wrong.
>
>
>>> Blabla. No change in the dbus area noting just the package produced by
>>> upower and voila it works. So the fi has to be in your package...
>>
>> You haven't provided any useful information so far which would help
>> diagnose this problem, instead you are just being rude.
>
> Because you are hunting the bug where it is not.
>
I explicitely asked you for the output of the upowerd daemon (as my
first request).
The reason why I asked for the information regarding dbus is, that the
error code 127 from dbus often indicates a problem in
dbus-daemon-launch-helper which needs to be owned by the correct user
and be set suid root.
Anyway, since you are not willing to provide the information I asked
for, I'm closing the bug.
If you feel like you have to re-open it, I'll ask the BTS admins to ban
your email address.
You are acting like an asshole and I won't put up with such behaviour.
Thanks you,
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 ---
