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 489585 - crash in Rhythmbox Music Player: leer una pista de músuca
crash in Rhythmbox Music Player: leer una pista de músuca
Status: RESOLVED DUPLICATE of bug 484988
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-23 21:46 UTC by fernando
Modified: 2007-10-24 08:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description fernando 2007-10-23 21:46:43 UTC 
Version: 0.10.1

What were you doing when the application crashed?
leer una pista de músuca


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 415150080 vsize: 415150080 resident: 35237888 share: 18415616 rss: 35237888 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193175914 rtime: 87 utime: 78 stime: 9 cutime:0 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 0x2b2d813d1700 (LWP 6191)]
[New Thread 0x42003950 (LWP 6200)]
[New Thread 0x41001950 (LWP 6198)]
(no debugging symbols found)
0x00002b2d77e8ac7f in waitpid () from /lib/libpthread.so.0

+ Trace 172362

Thread 1 (Thread 0x2b2d813d1700 (LWP 6191))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #6 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (45 sec old) ---------------------
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat': Internal GStreamer error: state change failed.  Please 
Failed to set state on new child.]
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat': Internal GStreamer error: state change failed.  Please 
Failed to set state on new child.]
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=chat': Internal GStreamer error: state change failed.  Please 
Failed to set state on new child.]
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music': Internal GStreamer error: state change failed.  Please
Failed to set state on new child.]
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music': Internal GStreamer error: state change failed.  Please
Failed to set state on new child.]
sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink profile=music': Internal GStreamer error: state change failed.  Please
Failed to set state on new child.]
sh: jackd: command not found
sh: jackd: command not found
sh: jackd: command not found
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-24 08:51:27 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 484988 ***