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 482394 - crash in Rhythmbox Music Player: did not start and plugin...
crash in Rhythmbox Music Player: did not start and plugin...
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-01 23:03 UTC by ankitgupta26
Modified: 2007-10-02 23:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ankitgupta26 2007-10-01 23:03:22 UTC
What were you doing when the application crashed?
did not start and plugins missing


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 120426496 vsize: 120426496 resident: 30609408 share: 17612800 rss: 30609408 rss_rlim: 4294967295
CPU usage: start_time: 1191279857 rtime: 548 utime: 497 stime: 51 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208436176 (LWP 7163)]
[New Thread -1256133744 (LWP 7235)]
[New Thread -1287603312 (LWP 7214)]
[New Thread -1298093168 (LWP 7213)]
[New Thread -1234343024 (LWP 7169)]
(no debugging symbols found)
0x00155402 in __kernel_vsyscall ()

Thread 2 (Thread -1256133744 (LWP 7235))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0


----------- .xsession-errors ---------------------
/home/ankit/Desktop/RealPlayer10GOLD.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/home/ankit/Desktop/RealPlayer10GOLD.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/home/ankit/Desktop/RealPlayer10GOLD.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/home/ankit/Desktop/real: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/home/ankit/Desktop/real: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Loading "installonlyn" plugin
/home/ankit/Desktop/livna-release-7.rpm is already installed
No packages were given for installation.
(rhythmbox:7163): Rhythmbox-CRITICAL **: rb_player_gst_play: assertion `mp->priv->playbin != NULL' failed
(rhythmbox:7163): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-10-02 23:37:03 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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