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 455894 - crash in Rhythmbox Music Player: verificando outro menu
crash in Rhythmbox Music Player: verificando outro menu
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-11 13:14 UTC by lmanuel.reis
Modified: 2007-07-12 09:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lmanuel.reis 2007-07-11 13:14:28 UTC
What were you doing when the application crashed?
verificando outro menu


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.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: 326586368 vsize: 326586368 resident: 166871040 share: 25104384 rss: 166871040 rss_rlim: 4294967295
CPU usage: start_time: 1184148554 rtime: 3132 utime: 2948 stime: 184 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 -1208731088 (LWP 3912)]
[New Thread -1361708144 (LWP 3989)]
[New Thread -1340728432 (LWP 3988)]
[New Thread -1319732336 (LWP 3987)]
[New Thread -1309242480 (LWP 3986)]
[New Thread -1298752624 (LWP 3985)]
[New Thread -1234003056 (LWP 3983)]
[New Thread -1256133744 (LWP 3980)]
[New Thread -1220940912 (LWP 3978)]
[New Thread -1330238576 (LWP 3977)]
[New Thread -1287996528 (LWP 3944)]
[New Thread -1245303920 (LWP 3918)]
(no debugging symbols found)
0x00139402 in __kernel_vsyscall ()

Thread 1 (Thread -1208731088 (LWP 3912))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyErr_Occurred
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyGC_Collect
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (278 sec old) ---------------------
amule: error while loading shared libraries: libcurl.so.2: cannot open shared object file: No such file or directory
/usr/bin/bittorrent:3761: GtkDeprecationWarning: gtk.threads_init is deprecated, use gtk.gdk.threads_init instead
  gtk.threads_init()
/usr/bin/bittorrent:2745: GtkDeprecationWarning: gtk.threads_enter is deprecated, use gtk.gdk.threads_enter instead
  gtk.threads_enter()
/usr/bin/bittorrent:2945: GtkDeprecationWarning: gtk.threads_leave is deprecated, use gtk.gdk.threads_leave instead
  gtk.threads_leave()
/usr/bin/bittorrent:3768: GtkDeprecationWarning: gtk.threads_enter is deprecated, use gtk.gdk.threads_enter instead
  gtk.threads_enter()
/usr/lib/python2.5/site-packages/BitTorrent/GUI.py:28: GtkDeprecationWarning: gtk.threads_enter is deprecated, use gtk.gdk.threads_enter instead
  gtk.threads_enter()
/usr/lib/python2.5/site-packages/BitTorrent/GUI.py:30: GtkDeprecationWarning: gtk.threads_leave is deprecated, use gtk.gdk.threads_leave instead
  gtk.threads_leave()
Aviso do gerenciador de janelas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800021 (Reprodutor)
Aviso do gerenciador de janelas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-12 09:26: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 436456 ***