my computer runs only on 600 MHz

Bug #613518 reported by Joakim Piläng
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: upower

Computer type: Dell D800

Runs onlo on 600 MHz despite of full battery and original power adapter.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-1
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Aug 4 16:59:42 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100630.2)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x3bd7f8 <dbus_connection_send+40>: mov 0x4(%esi),%eax
 PC (0x003bd7f8) 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:

Revision history for this message
Joakim Piläng (joakim-pilang) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 shared_connections_shutdown (data=0x10)
 object_registration_message (connection=0x9ff0058,
 up_daemon_hibernate_allowed (daemon=0x9fd8c10,
 g_signal_get_invocation_hint ()
 tristring_alloc_from_strings (padding_before=0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in upower (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.