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 490319 - crash in Rhythmbox Music Player: Nothing
crash in Rhythmbox Music Player: Nothing
Status: RESOLVED DUPLICATE of bug 434996
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-25 23:39 UTC by gfeiden
Modified: 2007-10-27 03:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gfeiden 2007-10-25 23:39:35 UTC
Version: 0.10.1

What were you doing when the application crashed?
Nothing


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Oxygen-Refit

Memory status: size: 703598592 vsize: 703598592 resident: 74252288 share: 25452544 rss: 74252288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193350605 rtime: 12156 utime: 10748 stime: 1408 cutime:3 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496392112 (LWP 3512)]
[New Thread 1115699536 (LWP 4123)]
[New Thread 1178638672 (LWP 3541)]
[New Thread 1105209680 (LWP 3520)]
(no debugging symbols found)
0x00000038d70c82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1115699536 (LWP 4123))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 g_object_set_valist
    from /lib64/libgobject-2.0.so.0
  • #5 g_object_set
    from /lib64/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib64/gstreamer-0.10/libgstplaybin.so
  • #7 ??
    from /usr/lib64/gstreamer-0.10/libgstplaybin.so
  • #8 ??
    from /usr/lib64/gstreamer-0.10/libgstplaybin.so
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 ??
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #14 ??
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib64/gstreamer-0.10/libgstqtdemux.so
  • #18 ??
    from /usr/lib64/gstreamer-0.10/libgstqtdemux.so
  • #19 ??
    from /usr/lib64/libgstreamer-0.10.so.0
  • #20 ??
    from /lib64/libglib-2.0.so.0
  • #21 ??
    from /lib64/libglib-2.0.so.0
  • #22 start_thread
    from /lib64/libpthread.so.0
  • #23 clone
    from /lib64/libc.so.6


----------- .xsession-errors (118 sec old) ---------------------
JACK tmpdir identified as [/dev/shm]
(mail-notification:3123): mail-notification-WARNING **: feiden@imap-server.oswego.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3123): mail-notification-WARNING **: feiden@imap-server.oswego.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
(mail-notification:3123): mail-notification-WARNING **: feiden@imap-server.oswego.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
JACK tmpdir identified as [/dev/shm]
(mail-notification:3123): mail-notification-WARNING **: feiden@imap-server.oswego.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
Launched application : 4513
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-27 03:39:34 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 434996 ***