upowerd assert failure: *** glibc detected *** /usr/lib/upower/upowerd: double free or corruption (out): 0x004ffec0 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upower (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: upower
New Live boot of 10.10 RC
tried to set a Twitter account in Gwibber and it froze on Twitter authentication screen. It might be that my netbook has faulty memory. It is a memory-upgraded Acer Aspire One.
I also tried installing on same hardware and also could not authorise a Twitter account.
Will try it on another eeepc 1000 netbook.
Otherwise looking good. I love the new installer. with the arr that allow one to select the screens to read while installing as well as the fact that installation starts before all questions have been answered.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-3
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/
Date: Mon Oct 4 16:46:39 2010
ExecutablePath: /usr/lib/
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
ProcCmdline: /usr/lib/
ProcEnviron:
Signal: 6
SourcePackage: upower
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
?? () from /lib/libc.so.6
?? () from /lib/libc.so.6
Title: upowerd assert failure: *** glibc detected *** /usr/lib/
UserGroups:
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #648414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.