Bug 405144 – crash in Sound: Nada: Abriendo este menú...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 405144 - crash in Sound: Nada: Abriendo este menú...


Summary:	crash in Sound: Nada: Abriendo este menú...


Status:	RESOLVED DUPLICATE of bug 363005

Product:	gnome-control-center
Classification:	Core
Component:	Sound
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-06 21:46 UTC by fjrubio1
Modified:	2007-02-06 22:04 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description fjrubio1 2007-02-06 21:46:44 UTC

Version: 2.16.0

What were you doing when the application crashed?
Nada: Abriendo este menú.


Distribution: PCLinuxOS release 2007 (PCLinuxOS) for i586
Gnome Release: 2.16.0 2006-11-20 (%vendor)
BugBuddy Version: 2.16.0

Memory status: size: 32948224 vsize: 0 resident: 32948224 share: 0 rss: 17133568 rss_rlim: 0
CPU usage: start_time: 1170798350 rtime: 0 utime: 34 stime: 0 cutime:34 cstime: 0 timeout: 0 it_real_value: 0 frequency: 8

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1497581872 (LWP 8820)]
(no debugging symbols found)
0xa7f85410 in __kernel_vsyscall ()

+ Trace 108570

Thread 1 (Thread -1497581872 (LWP 8820))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 main

Comment 1 Jens Granseuer 2007-02-06 22:04:36 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 363005 ***