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 383605 - crash in Volume Control:
crash in Volume Control:
Status: RESOLVED DUPLICATE of bug 378525
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-08 03:57 UTC by plusdiversity
Modified: 2006-12-08 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description plusdiversity 2006-12-08 03:57:17 UTC 
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 80965632 vsize: 0 resident: 80965632 share: 0 rss: 8343552 rss_rlim: 0
CPU usage: start_time: 1165550284 rtime: 0 utime: 16 stime: 0 cutime:12 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208330016 (LWP 2623)]
(no debugging symbols found)
0x00b12402 in __kernel_vsyscall ()

+ Trace 92474

Thread 1 (Thread -1208330016 (LWP 2623))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 _gst_query_initialize
    from /usr/lib/libgstreamer-0.10.so.0
  • #5 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #6 g_option_context_parse
    from /lib/libglib-2.0.so.0
  • #7 gst_init_check
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #9 main
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-12-08 11:22:08 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 378525 ***