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 539824 - crash in Rhythmbox Music Player: Podcasts aktuallisiert
crash in Rhythmbox Music Player: Podcasts aktuallisiert
Status: RESOLVED DUPLICATE of bug 522247
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-23 20:36 UTC by meyfra_public
Modified: 2008-06-24 07:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description meyfra_public 2008-06-23 20:36:19 UTC 
Version: 0.11.5

What were you doing when the application crashed?
Podcasts aktuallisiert


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Thu Jun 12 15:38:32 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aero-ion3.1
Icon Theme: Neu

Memory status: size: 653869056 vsize: 653869056 resident: 57913344 share: 24879104 rss: 57913344 rss_rlim: 18446744073709551615
CPU usage: start_time: 1214253272 rtime: 610 utime: 525 stime: 85 cutime:7 cstime: 15 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f73e59737a0 (LWP 6878)]
[New Thread 0x434a9950 (LWP 6962)]
[New Thread 0x424a7950 (LWP 6961)]
[New Thread 0x43caa950 (LWP 6960)]
[New Thread 0x414a5950 (LWP 6959)]
[New Thread 0x40ca4950 (LWP 6949)]
[New Thread 0x42ca8950 (LWP 6892)]
[New Thread 0x41ca6950 (LWP 6884)]
(no debugging symbols found)
0x00007f73e4be6384 in __lll_lock_wait () from /lib/libpthread.so.0

+ Trace 201197

Thread 5 (Thread 0x414a5950 (LWP 6959))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #10 totem_pl_parser_new
    from /usr/lib/libtotem-plparser.so.10
  • #11 rb_podcast_parse_load_feed
  • #12 ??
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6
  • #16 ?? 


----------- .xsession-errors (13 sec old) ---------------------
** Message: GetValue variable 2 (2)
(firefox-bin:6610): Gdk-CRITICAL **: gdk_x11_visual_get_xvisual: assertion `visual != NULL' failed
(rhythmbox:6807): Rhythmbox-WARNING **: Could not open device /dev/radio0
Rhythmbox: could not connect to socket
Rhythmbox: Datei oder Verzeichnis nicht gefunden
(rhythmbox:6878): Rhythmbox-WARNING **: Could not open device /dev/radio0
Rhythmbox: could not connect to socket
Rhythmbox: Datei oder Verzeichnis nicht gefunden
Fenstermanager-Warnung:Received a _NET_WM_MOVERESIZE message for 0x3a00021 (Musik-Play); these messages lack timestamps and therefore suck.
Rhythmbox-Message: Missing plugin: gstreamer|0.10|rhythmbox-metadata|application/x-ms-dos-executable decoder|decoder-application/x-ms-dos-executable
keine Anwendung gefunden
Rhythmbox-Message: No installation candidate for missing plugins found.
--------------------------------------------------
Comment 1 Susana 2008-06-24 07:34:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 522247 ***