hald-probe-input assert failure: *** glibc detected *** /usr/lib/hal/hald-probe-input: munmap_chunk(): invalid pointer: 0x080492f9 ***

Bug #505896 reported by C. Brayton
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: hal

This seems related to the 'hal not running at login' bug. That is, I got that message at login, then this one, after updating to 2.6.32-10. (cpufreq setting cpu to lowest frequency, and cannot be reset, may also be related. That one has me thinking of switching distros. I am basically working offa Puppy Linux all the time now, waiting for a fix.)

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/lib/hal/hald-probe-input: munmap_chunk(): invalid pointer: 0x080492f9 ***
Date: Mon Jan 11 10:53:12 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/hal/hald-probe-input
NonfreeKernelModules: nvidia
Package: hal 0.5.14-0ubuntu2
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/lib/hal/hald-probe-input
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
Signal: 6
SourcePackage: hal
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Tags: lucid
Title: hald-probe-input assert failure: *** glibc detected *** /usr/lib/hal/hald-probe-input: munmap_chunk(): invalid pointer: 0x080492f9 ***
Uname: Linux 2.6.32-10-generic i686
UserGroups: mythtv

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

visibility: private → public
tags: removed: need-i386-retrace
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.