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 441657 - crash in Rhythmbox Music Player: Opened app for the very ...
crash in Rhythmbox Music Player: Opened app for the very ...
Status: RESOLVED DUPLICATE of bug 426586
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-27 19:33 UTC by briansullivan
Modified: 2007-05-27 22:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description briansullivan 2007-05-27 19:33:21 UTC
What were you doing when the application crashed?
Opened app for the very first time ever and click once on Mangatune in left column then double clicked on a song title and then it started putting red dash circles on the screen one after another for 9 circles then started it crash.


Distribution: Fedora release 6.93 (Rawhide)
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: 125370368 vsize: 125370368 resident: 45871104 share: 17883136 rss: 45871104 rss_rlim: 4294967295
CPU usage: start_time: 1180294215 rtime: 878 utime: 835 stime: 43 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 -1208112592 (LWP 3311)]
[New Thread -1219974256 (LWP 3324)]
[New Thread -1244296304 (LWP 3319)]
(no debugging symbols found)
0x00672402 in __kernel_vsyscall ()

Thread 1 (Thread -1208112592 (LWP 3311))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyObject_RichCompare
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #6 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #7 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #8 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #10 PyEval_EvalCodeEx
    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 ??
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #15 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #16 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #17 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (44 sec old) ---------------------
localuser:root being added to access control list
No profile for user 'root' found
SESSION_MANAGER=local/k724g:/tmp/.ICE-unix/3015
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-05-27 22:25:32 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 426586 ***