I was attempting to DL 3 nvidia drivers consecutivly, and realised I did not need the older one so I cancled it and this is what caused the crash. a box opened earlyer telling me about un autherised drivers but vanish befor I counl click on it

[sixto Rodriguez Jr]

Binary package hint: upower

10.10 beta
running off of the cd, a box flashed informing me I needed au authorised driver or something. when I finish reading it it vanished.
I went to applications, software Center and typed Nvidia. I selected Transitional package for nvidia-gix-185, 173 and 96-dev.
while gix-185 started to DL I attempted to cansel 96 and thats when it crashed.

I was expecting to remove the 173 and 96-dev, but instead it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Mon Sep 13 01:43:08 2010
ExecutablePath: /usr/lib/upower/upowerd
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x1dbed8 <dbus_connection_send+40>: mov 0x4(%esi),%eax
 PC (0x001dbed8) ok
 source "0x4(%esi)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 dbus_connection_send () from /lib/libdbus-1.so.3
 dbus_g_method_return () from /usr/lib/libdbus-glib-1.so.2
 ?? ()
 g_cclosure_marshal_VOID__POINTER ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: upowerd crashed with SIGSEGV in dbus_connection_send()
UserGroups:

[Apport retracing service (apport)]

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 #623785, 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.