[hardy] pavucontrol crashed with SIGSEGV in strlen()

[Stefan Fleiter]

Binary package hint: pavucontrol

Entering pavucontrol at the command line I immediately get a core dump. The upcoming
window can only be seen as a quick flickering.

This is version 0.9.5-1ubuntu1 on amd64 architecture (Intel core 2 duo).

Please tell me if I can provide further information.

ProblemType: Crash
Architecture: amd64
Date: Wed Feb 20 19:39:35 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pavucontrol
NonfreeKernelModules: nvidia
Package: pavucontrol 0.9.5-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: pavucontrol
ProcCwd: /home/shared/Pictures/Oberlin-Kindergarten/stefanie
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/stfl/bin:/usr/lib/ccache:~/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/sf/opt/java/grails/bin
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: pavucontrol
StacktraceTop:
 strlen () from /lib/libc.so.6
 Glib::ustring::operator= ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/libpulse.so.0
Title: pavucontrol crashed with SIGSEGV in strlen()
Uname: Linux stfl-nb-lx 2.6.24-8-generic #1 SMP Thu Feb 14 20:13:27 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:strlen () from /lib/libc.so.6
Glib::ustring::operator= () from /usr/lib/libglibmm-2.4.so.1
MainWindow::updateServer (this=0x8a5800, info=@0x7fff2ccc9970)
server_info_cb (i=0x0, userdata=0x8a5800) at pavucontrol.cc:1046
context_get_server_info_callback (pd=<value optimized out>, command=2,

[Dimitrios Symeonidis (azimout)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Stefan Fleiter (stefan-fleiter)]

This does not happen in karmic any more.

[Dimitrios Symeonidis (azimout)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.