paman crashes

[kylea]

Binary package hint: paman

2.6.31-13-generic #44-Ubuntu SMP Sat Oct 10 15:27:14 UTC 2009 x86_64 GNU/Linux
------------------
Description: Ubuntu karmic (development branch)
Release: 9.10

Pulseaudio Applet - paman (Pulseaudio manager crashes when selected from the Panel Applet)

apport (pid 4420) Tue Oct 13 21:38:59 2009: called for pid 4418, signal 6
apport (pid 4420) Tue Oct 13 21:38:59 2009: executable: /usr/bin/paman (command line "paman")
apport (pid 4420) Tue Oct 13 21:39:00 2009: this executable already crashed 2 times, ignoring
apport (pid 25831) Tue Oct 13 21:59:41 2009: called for pid 25830, signal 6
apport (pid 25831) Tue Oct 13 21:59:41 2009: executable: /usr/bin/paman (command line "paman")
apport (pid 25831) Tue Oct 13 21:59:41 2009: this executable already crashed 2 times, ignoring
apport (pid 26165) Tue Oct 13 22:00:11 2009: called for pid 26147, signal 6
apport (pid 26165) Tue Oct 13 22:00:11 2009: executable: /usr/bin/paman (command line "paman")
apport (pid 26165) Tue Oct 13 22:00:11 2009: this executable already crashed 2 times, ignoring

ProblemType: Bug
Architecture: amd64
Date: Tue Oct 13 22:06:51 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: paman 0.9.4-1ubuntu2
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: paman
Uname: Linux 2.6.31-13-generic x86_64

[kylea (kylea)]

Also getting the same behaviour with pavucontrol

apport (pid 2862) Tue Oct 13 22:15:16 2009: called for pid 2861, signal 6
apport (pid 2862) Tue Oct 13 22:15:16 2009: executable: /usr/bin/pavucontrol (command line "pavucontrol")
apport (pid 2862) Tue Oct 13 22:15:16 2009: this executable already crashed 2 times, ignoring

[kylea (kylea)]

And pavumeter

System tried to produce an crash report but it could not:

The Problem cannot be reported:

The program crashed on an assertion failure, but the message
could not be retrieved. Apport does not support reporting of these
crashes.

[kylea (kylea)]

Still Crashes after all updates

2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64 GNU/Linux
------------------
Description: Ubuntu 9.10
Release: 9.10

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael (miiichael)]

Maybe this is the problem?

michael@cnspc18:~$ ldd `which paman`|grep libpulsecommon
        libpulsecommon-1.1.so => not found
        libpulsecommon-4.0.so => /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so (0x00007fd7dc9dc000)

michael@cnspc18:~$ apt-cache policy libpulse0
libpulse0:
  Installed: 1:4.0-0ubuntu1
  Candidate: 1:4.0-0ubuntu1
  Version table:
 *** 1:4.0-0ubuntu1 0
        460 http://au.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status
     1:3.0-0ubuntu6 0
        470 http://au.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
     1:2.1-0ubuntu4.1 0
        480 http://au.archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages
     1:2.1-0ubuntu4 0
        480 http://au.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
     1:1.1-0ubuntu15.3 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
     1:1.1-0ubuntu15 0
        500 http://au.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

Why does paman (and pavucontrol) link to libpulsecommon-1.1.so? o_O

[Michael (miiichael)]

Actually, I just fixed it here by upgrading libpulse-mainloop-glib0.

I suspect something (or many somethings) somewhere needs its versioned dependency on libpulse0/libpulse-mainloop-glib0 tightened.