The error message makes this quite clear:
A handler is already registered for
/org/freedesktop/UPower/devices/battery_hid_00o12oa1o68oa3o1b_battery
So this seems to happen if you have a wireless mouse or keyboard, which
powers down due to inactivity, and then gets repowered and it tries to
** Bug watch added: Red Hat Bugzilla #962080
https://bugzilla.redhat.com/show_bug.cgi?id=962080
** Also affects: upower via
https://bugzilla.redhat.com/show_bug.cgi?id=962080
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Crash when returning from a lock screen after an inactivity period.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
upowerd crashed with signal 5 in
if it was fixed ... well, sorry but seems that it come back in 13.10...
or maybe its another one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
upowerd crashed with
** Changed in: upower (Ubuntu)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
upowerd crashed with signal 5 in
** Changed in: upower (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
upowerd crashed with signal 5 in
@vvekecki: where is the fix? I can't find it in the upower (ubuntu) code
branches..
I'm open to repackage it in my PPA and test if needed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
The kernel recompile worked for me. Any chance this'll be patched in as
an option for 13.10. I read somewhere (can't remember where) that the
capacity warning was being worked on but bringing in a patched kernel is
a good temporary fix.
--
You received this bug notification because you are a
** Attachment added: 13.04 amd64 stacktrace with some debug info
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/+attachment/3566966/+files/stacktrace.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in
According to my syslog, upowerd crash always follows a power_supply
error, so I thought there must be some connection:
Mar 10 02:59:45 dev kernel: [ 160.051819] power_supply
hid-00:12:a1:68:a3:1b-battery: driver failed to report `capacity' property: -5
Mar 10 02:59:45 dev kernel: [ 160.137237]
Bluetooth keyboard and mouse here too. I need to re-sync the mouse and
then re-issue
xinput --set-prop vila’s mouse Device Accel Adaptive Deceleration 4.0
xinput --set-prop vila’s mouse Device Accel Velocity Scaling 1.0
each time it occurs (I've put the above in .xprofile but having to do '.
I would like to get this fixed. I've packaged upower 0.9.19 for quantal
in my PPA (https://launchpad.net/~plaxx/+archive/random-fixes) and
installed it on my system. If it doesn't resolve it (i'll know in a
couple of days), I intend to engage with upstream to try to find out
exactly what is going
also on
12.10 ubuntu 32-bit
Lenovo V570
hp X4000b mouse
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
upowerd crashed with signal 5 in
The first occurence I can see is on precise which has upower 0.9.15
The crasher also occures on quantal with upower 0.9.17
and is still there in raring with upower 0.9.19.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in
@jm-leddy
o.K,
I have looked a little bit arround.
Looking at:
https://bugs.launchpad.net/ubuntu/+source/upower/+bugs?orderby=-heatstart=0
upower bugs seems to get not so much attention(to say it nice).There lay
60 open reports arround. Even when you use advance search you see that
there
Hi Till,
this here is a problem.
apport-retracing was not able to create a stacktrace(usefull one because
of ?? are still there) and there is also not a reproducing procedure.
Both are mostly necessary.
Can I ask you to provide a manually created stacktrace?
This may help
Unfortunately, I cannot reproduce this bug. Here and there a pop-up
comes up, mostly right after login, telling that upowerd has crashed.
Most of the times I have simply clicked Cancel and now I have sent out
the crash report.
By the way, the hardware is the Pandaboard ES.
--
You received this
17 matches
Mail list logo
