Your message dated Mon, 07 Apr 2014 17:48:53 +0200
with message-id <[email protected]>
and subject line Re: New information?
has caused the Debian Bug report #457619,
regarding pavucontrol: Invalid memory reference
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
457619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457619
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pavucontrol
Version: 0.9.5-1
Severity: important
File: /usr/bin/pavucontrol

*** Please describe what you were doing when the application crashed ***

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6db06c0 (LWP 6879)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb71a4203 in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7f6a9e8 in ?? () from /usr/lib/debreaper/libviaticum.so
#3  0x00001b00 in ?? ()
#4  0xbfcc6f94 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread 0xb6db06c0 (LWP 6879)):
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb71a4203 in waitpid () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2  0xb7f6a9e8 in ?? () from /usr/lib/debreaper/libviaticum.so
No symbol table info available.
#3  0x00001b00 in ?? ()
No symbol table info available.
#4  0xbfcc6f94 in ?? ()
No symbol table info available.
#5  0x00000000 in ?? ()
No symbol table info available.
#0  0xffffe410 in __kernel_vsyscall ()

-- System Information:
Debian Release: lenny/sid
  APT prefers hardy-updates
APT policy: (500, 'hardy-updates'), (500, 'hardy-security'), (500, 'hardy-proposed'), (500, 'hardy-backports'), (500, 'hardy')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-2-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pavucontrol depends on:
ii  libatk1.0-0         1.20.0-1             The ATK accessibility toolkit
ii  libc6               2.7-4ubuntu1         GNU C Library: Shared libraries
ii libcairo2 1.5.4-0ubuntu1 The Cairo 2D vector graphics libra ii libcairomm-1.0-1 1.4.2-1 C++ wrappers for Cairo (shared lib
ii  libgcc1             1:4.2.2-4ubuntu2     GCC support library
ii libglade2-0 1:2.6.2-1 library to load .glade files at ru ii libglademm-2.4-1c2a 2.6.5-4 C++ wrappers for libglade2 (shared
ii  libglib2.0-0        2.15.0-0ubuntu1      The GLib library of C routines
ii libglibmm-2.4-1c2a 2.14.2-4 C++ wrapper for the GLib toolkit ( ii libgtk2.0-0 2.12.3-2 The GTK+ graphical user interface ii libgtkmm-2.4-1c2a 1:2.12.3-2 C++ wrappers for GTK+ 2.4 (shared ii libpango1.0-0 1.19.2-1ubuntu1 Layout and rendering of internatio ii libpulse-mainloop-g 0.9.8-1ubuntu3 PulseAudio client libraries (glib
ii  libpulse0           0.9.8-1ubuntu3       PulseAudio client libraries
ii libsigc++-2.0-0c2a 2.0.17-2ubuntu2 type-safe Signal Framework for C++
ii  libstdc++6          4.2.2-4ubuntu2       The GNU Standard C++ Library v3
ii  libxml2             2.6.30.dfsg-3ubuntu1 GNOME XML library

pavucontrol recommends no packages.



--- End Message ---
--- Begin Message --- As said, closing the bug because it is not reproducible and filed against a really old pavucontrol version (this may have been fixed in the meantime), consider opening a new bug with additional debug information if needed.

Cheers,

--
Léo

--- End Message ---
_______________________________________________
pkg-pulseaudio-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel

Reply via email to