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 375373 - crash in Volume Control: I had just rebooted and ...
crash in Volume Control: I had just rebooted and ...
Status: RESOLVED DUPLICATE of bug 354483
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 375374 375376 375378 375388 447600 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-15 01:53 UTC by tylerwanner
Modified: 2007-07-26 04:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description tylerwanner 2006-11-15 01:53:00 UTC
What were you doing when the application crashed?
I had just rebooted and was logging in and I received the error while gnome was still loading.  I just yesterday upgraded from Dapper to Edgy and have been experiencing problems since the upgrade.  I had just rebooted because I was unable to login (my session would crash within 10 seconds and I would get the warning that my session had lasted less than 10 seconds and this may be because of an installation problem).  This time instead of my session ending within 10 seconds, I got this bug reporting tool.  If you can tell me what I need to do to get my Ubuntu back to normal, I would really appreciate it!


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 57208832 vsize: 0 resident: 57208832 share: 0 rss: 3698688 rss_rlim: 0
CPU usage: start_time: 1163555152 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226565968 (LWP 5720)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226565968 (LWP 5720))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 xmlParseChunk
    from /usr/lib/libxml2.so.2
  • #5 xmlReaderForFile
    from /usr/lib/libxml2.so.2
  • #6 xmlReaderForFile
    from /usr/lib/libxml2.so.2
  • #7 xmlTextReaderExpand
    from /usr/lib/libxml2.so.2
  • #8 xmlTextReaderRead
    from /usr/lib/libxml2.so.2
  • #9 gst_registry_xml_write_cache
    from /usr/lib/libgstreamer-0.10.so.0
  • #10 gst_registry_xml_read_cache
    from /usr/lib/libgstreamer-0.10.so.0
  • #11 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #12 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #13 g_option_context_parse
    from /usr/lib/libglib-2.0.so.0
  • #14 gst_init_check
    from /usr/lib/libgstreamer-0.10.so.0
  • #15 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #16 main
  • #0 __kernel_vsyscall

Comment 1 Susana 2006-11-15 08:46:45 UTC
*** Bug 375374 has been marked as a duplicate of this bug. ***
Comment 2 Susana 2006-11-15 08:47:35 UTC
*** Bug 375376 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2006-11-15 08:47:50 UTC
*** Bug 375378 has been marked as a duplicate of this bug. ***
Comment 4 Susana 2006-11-15 08:48:28 UTC
*** Bug 375388 has been marked as a duplicate of this bug. ***
Comment 5 Jens Granseuer 2006-11-25 15:20:26 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 354483 ***
Comment 6 Philip Withnall 2007-07-26 04:44:47 UTC
*** Bug 447600 has been marked as a duplicate of this bug. ***