pommed crashed with SIGSEGV in snd_mixer_handle_events()

Bug #721200 reported by Mario Vukelic on 2011-02-18
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Mactel Support
pommed (Ubuntu)

Bug Description

Binary package hint: pommed

This happened immediately after login. Never did this before I upgraded the machine from Maverick to Natty, nor when it was Lucid.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: pommed 1.37~dfsg-1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Fri Feb 18 01:41:39 2011
ExecutablePath: /usr/sbin/pommed
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100131)
ProcCmdline: /usr/sbin/pommed
ProcEnviron: PATH=(custom, no user)
 Segfault happened at: 0x7fa1d3cd3b30 <snd_mixer_handle_events+48>: mov -0x8(%rbx),%rdi
 PC (0x7fa1d3cd3b30) ok
 source "-0x8(%rbx)" (0x30000000010) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pommed
 snd_mixer_handle_events () from /usr/lib/libasound.so.2
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: pommed crashed with SIGSEGV in snd_mixer_handle_events()

Mario Vukelic (mario-vukelic) wrote :
visibility: private → public

 #0 0x00007fa1d3cd3b30 in snd_mixer_handle_events (mixer=0xfba3a0)
     at mixer.c:632
  err = <value optimized out>
  s = Unhandled dwarf expression opcode 0x9f
StacktraceTop: snd_mixer_handle_events (mixer=0xfba3a0)

Changed in pommed (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Clint Byrum (clint-fewbar) wrote :

I also just had this happen on Natty on a Macbook 5,1 15". With 6 others affected, I'm marking this as confirmed.

Changed in pommed (Ubuntu):
status: New → Confirmed
Alex Murray (alexmurray) wrote :

@Clint - slightly unrelated but there should be no need for pommed on your MacBook 5,1 now in Natty as all functions should (hopefully) be support out of the box without it I think...

Mario Vukelic (mario-vukelic) wrote :

I'm the original reporter, and I've just had this reappear in up-to-date Quantal, on the same machine my original report came from. It happened immediately when logging in.

Mario Vukelic (mario-vukelic) wrote :

This is a new install by the way (recently installed from 12.04.1 and immediately upgraded to Quantal shortly after Beta1). And regarding comment #5: indeed basic functions work, but if I want to change the defaults (like how to treat Fn keys, or keyboard light timeout) I still seem to need pommed (on this MacBook Pro 5,3)

Mario Vukelic (mario-vukelic) wrote :

I still have the same machine (upgraded/reinstalled to each Ubuntu version since) and the problem has not happened in agesa

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers