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 453619 - crash in Rhythmbox Music Player: I am trying to open a pl...
crash in Rhythmbox Music Player: I am trying to open a pl...
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-04 08:15 UTC by danbeach
Modified: 2007-07-04 11:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description danbeach 2007-07-04 08:15:34 UTC 
What were you doing when the application crashed?
I am trying to open a playlist from Jame


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 265359360 vsize: 265359360 resident: 160079872 share: 20451328 rss: 160079872 rss_rlim: 4294967295
CPU usage: start_time: 1183536437 rtime: 2970 utime: 2870 stime: 100 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 -1208980944 (LWP 3190)]
[New Thread -1314825328 (LWP 3269)]
[New Thread -1272448112 (LWP 3197)]
(no debugging symbols found)
0x00117402 in __kernel_vsyscall ()

+ Trace 145654

Thread 1 (Thread -1208980944 (LWP 3190))

  • #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 __assert_fail
    from /lib/libc.so.6
  • #8 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib/libpython2.5.so.1.0
  • #10 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall 






Comment 1


Jonathan Matthew





          2007-07-04 11:41:50 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 436456 ***