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 462896 - crash in Rhythmbox Music Player: Just playing music with ...
crash in Rhythmbox Music Player: Just playing music with ...
Status: RESOLVED DUPLICATE of bug 482819
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-02 19:39 UTC by jsj
Modified: 2007-11-28 22:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jsj 2007-08-02 19:39:15 UTC
What were you doing when the application crashed?
Just playing music with Jamendo


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.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 931737600 vsize: 931737600 resident: 244002816 share: 26902528 rss: 244002816 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186082120 rtime: 13223 utime: 11710 stime: 1513 cutime:6 cstime: 28 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496392144 (LWP 8327)]
[New Thread 1210108240 (LWP 8926)]
[New Thread 1189128528 (LWP 8924)]
[New Thread 1178638672 (LWP 8923)]
[New Thread 1147169104 (LWP 8922)]
[New Thread 1157658960 (LWP 8921)]
[New Thread 1115699536 (LWP 8918)]
[New Thread 1105209680 (LWP 8917)]
[New Thread 1126189392 (LWP 8914)]
[New Thread 1094719824 (LWP 8332)]
0x00000032d400d97f in __libc_waitpid (pid=8998, stat_loc=0x7fff23b2ab8c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 1 (Thread 46912496392144 (LWP 8327))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 ??
  • #4 g_source_callback_unref
    at gmain.c line 1178
  • #5 g_source_destroy_internal
    at gmain.c line 957
  • #6 IA__g_main_context_dispatch
    at gmain.c line 2069
  • #7 g_main_context_iterate
    at gmain.c line 2677
  • #8 IA__g_main_loop_run
    at gmain.c line 2881
  • #9 IA__gtk_main
    at gtkmain.c line 1154
  • #10 main
    at main.c line 384


----------- .xsession-errors (223 sec old) ---------------------
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-11-28 22:59:44 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 482819 ***