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 422354 - crash in Rhythmbox Music Player: escuchar música
crash in Rhythmbox Music Player: escuchar música
Status: RESOLVED DUPLICATE of bug 361681
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-24 17:25 UTC by paredesmerino
Modified: 2007-03-26 03:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description paredesmerino 2007-03-24 17:25:20 UTC
What were you doing when the application crashed?
escuchar música


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

Memory status: size: 575209472 vsize: 0 resident: 575209472 share: 0 rss: 29134848 rss_rlim: 0
CPU usage: start_time: 1174738899 rtime: 0 utime: 1303 stime: 0 cutime:1225 cstime: 0 timeout: 78 it_real_value: 0 frequency: 5

Backtrace was generated from '/usr/bin/rhythmbox'

(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 -1228671312 (LWP 6354)]
[New Thread -1856226400 (LWP 6922)]
[New Thread -1847833696 (LWP 6917)]
[New Thread -1839440992 (LWP 6912)]
[New Thread -1831048288 (LWP 6909)]
[New Thread -1822655584 (LWP 6906)]
[New Thread -1814262880 (LWP 6903)]
[New Thread -1333789792 (LWP 6900)]
[New Thread -1805870176 (LWP 6897)]
[New Thread -1797477472 (LWP 6894)]
[New Thread -1789084768 (LWP 6891)]
[New Thread -1780692064 (LWP 6888)]
[New Thread -1772299360 (LWP 6885)]
[New Thread -1763906656 (LWP 6882)]
[New Thread -1755513952 (LWP 6877)]
[New Thread -1747121248 (LWP 6872)]
[New Thread -1738728544 (LWP 6858)]
[New Thread -1730335840 (LWP 6854)]
[New Thread -1721943136 (LWP 6850)]
[New Thread -1713550432 (LWP 6847)]
[New Thread -1705157728 (LWP 6843)]
[New Thread -1696765024 (LWP 6836)]
[New Thread -1671586912 (LWP 6833)]
[New Thread -1528910944 (LWP 6832)]
[New Thread -1428198496 (LWP 6831)]
[New Thread -1646408800 (LWP 6830)]
[New Thread -1663194208 (LWP 6825)]
[New Thread -1679979616 (LWP 6821)]
[New Thread -1315570784 (LWP 6812)]
[New Thread -1596052576 (LWP 6801)]
[New Thread -1654801504 (LWP 6792)]
[New Thread -1545696352 (LWP 6789)]
[New Thread -1604445280 (LWP 6772)]
[New Thread -1638016096 (LWP 6766)]
[New Thread -1621230688 (LWP 6758)]
[New Thread -1629623392 (LWP 6753)]
[New Thread -1612837984 (LWP 6738)]
[New Thread -1587659872 (LWP 6734)]
[New Thread -1411413088 (LWP 6731)]
[New Thread -1570874464 (LWP 6720)]
[New Thread -1579267168 (LWP 6709)]
[New Thread -1495340128 (LWP 6705)]
[New Thread -1562481760 (LWP 6699)]
[New Thread -1298785376 (LWP 6694)]
[New Thread -1554089056 (LWP 6673)]
[New Thread -1537303648 (LWP 6670)]
[New Thread -1478554720 (LWP 6664)]
[New Thread -1520518240 (LWP 6652)]
[New Thread -1512125536 (LWP 6649)]
[New Thread -1503732832 (LWP 6645)]
[New Thread -1486947424 (LWP 6640)]
[New Thread -1261261920 (LWP 6637)]
[New Thread -1436591200 (LWP 6611)]
[New Thread -1470162016 (LWP 6606)]
[New Thread -1461769312 (LWP 6602)]
[New Thread -1453376608 (LWP 6601)]
[New Thread -1307178080 (LWP 6534)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1228671312 (LWP 6354))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
    from /usr/lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgthread-2.0.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgthread-2.0.so.0
  • #13 ??
    from /usr/lib/libgthread-2.0.so.0
  • #14 ??
  • #15 ??
    from /usr/lib/libgthread-2.0.so.0
  • #16 ??
  • #17 ??
    from /usr/lib/libgthread-2.0.so.0
  • #18 ??
    from /usr/lib/libgstaudio-0.10.so.0
  • #19 ??
  • #20 ??
  • #21 gst_audio_sink_get_type
    from /usr/lib/libgstaudio-0.10.so.0
  • #22 gst_audio_sink_get_type
    from /usr/lib/libgstaudio-0.10.so.0
  • #23 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #24 gst_object_unref
    from /usr/lib/libgstreamer-0.10.so.0
  • #25 gst_object_unparent
    from /usr/lib/libgstreamer-0.10.so.0
  • #26 gst_base_audio_sink_get_type
    from /usr/lib/libgstaudio-0.10.so.0
  • #27 ??
    from /usr/lib/gstreamer-0.10/libgstalsa.so
  • #28 ??
  • #29 ??
  • #30 __after_morecore_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #31 ??
    from /usr/lib/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib/gstreamer-0.10/libgstalsa.so
  • #33 ??
    from /usr/lib/libgobject-2.0.so.0
  • #34 ??
  • #35 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #37 gst_object_unref
    from /usr/lib/libgstreamer-0.10.so.0
  • #38 gst_message_new_eos
    from /usr/lib/libgstreamer-0.10.so.0
  • #39 gst_mini_object_unref
    from /usr/lib/libgstreamer-0.10.so.0
  • #40 gst_bus_pop
    from /usr/lib/libgstreamer-0.10.so.0
  • #41 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #43 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #44 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 main
  • #0 __kernel_vsyscall

Comment 1 Alex Lancaster 2007-03-26 03:17:49 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 361681 ***