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 341118 - Rythmbox crash when updating feed podcast
Rythmbox crash when updating feed podcast
Status: RESOLVED DUPLICATE of bug 339712
Product: rhythmbox
Classification: Other
Component: Podcast
0.9.4.1
Other other
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-09 10:08 UTC by Andrea V.
Modified: 2006-05-11 23:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Andrea V. 2006-05-09 10:08:53 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: rhythmbox
Severity: critical
Version: GNOME2.14.1 0.9.4.1
Gnome-Distributor: Red Hat, Inc
Synopsis: Rythmbox crash when updating feed podcast
Bugzilla-Product: rhythmbox
Bugzilla-Component: Podcast
Bugzilla-Version: 0.9.4.1
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Immediately after you open Rythmbox, if you try to update the podcast's
feeds the application will crash.

Steps to reproduce the crash:
1. Open Rythmbox
2. Click on Update all feeds

Expected Results:
Updating process completion correctly

How often does this happen?
Always

Additional Information:
You should insert at least 1 feed before trying to update it...


Debugging Information:

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)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208346144 (LWP 4757)]
[New Thread 146181024 (LWP 4770)]
[New Thread 119511968 (LWP 4760)]
(no debugging symbols found)
0x00209402 in __kernel_vsyscall ()

Thread 1 (Thread -1208346144 (LWP 4757))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 rhythmdb_entry_set_uninserted
  • #5 rb_podcast_manager_subscribe_feed
  • #6 g_list_remove_link
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main




------- Bug created by bug-buddy at 2006-05-09 10:08 -------

Comment 1 James "Doc" Livingston 2006-05-09 10:14:57 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Andrea V. 2006-05-09 20:41:06 UTC
Hope this will help:

Starting program: /usr/bin/rhythmbox
Reading symbols from shared object read from target memory...(no debugging symbols found)...done.
Loaded system supplied DSO at 0x209000
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208305184 (LWP 4087)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 18766752 (LWP 4090)]
[New Thread 146181024 (LWP 4091)]
[Thread 146181024 (LWP 4091) exited]
[New Thread 146181024 (LWP 4092)]
[Thread 146181024 (LWP 4092) exited]

(rhythmbox:4087): Rhythmbox-WARNING **: Unable to start mDNS browsing: Il servizion MDNS non è in esecuzione
[New Thread 146181024 (LWP 4093)]
[Thread 146181024 (LWP 4093) exited]
[New Thread 146181024 (LWP 4095)]
[Thread 146181024 (LWP 4095) exited]
[New Thread 146181024 (LWP 4096)]
[Thread 146181024 (LWP 4096) exited]
[New Thread 146181024 (LWP 4097)]
[Thread 146181024 (LWP 4097) exited]
[New Thread 146181024 (LWP 4098)]
[New Thread -1279263840 (LWP 4099)]
[Thread -1279263840 (LWP 4099) exited]
[New Thread -1279263840 (LWP 4100)]
[Thread -1279263840 (LWP 4100) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208305184 (LWP 4087)]
---Type <return> to continue, or q <return> to quit---
0x080de383 in rhythmdb_entry_set_uninserted ()
Comment 3 Andrea V. 2006-05-09 21:04:27 UTC
maybe this is better (sorry, if I am not help you guys but this is the first bug for me):

Debugging Information:

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

Using host libthread_db library "/lib/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1208423968 (LWP 4517)]
[New Thread 47041440 (LWP 4525)]
[New Thread 19397536 (LWP 4518)]
0x00209402 in __kernel_vsyscall ()

Thread 1 (Thread -1208423968 (LWP 4517))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 rhythmdb_entry_set_uninserted
    at rhythmdb.c line 2659
  • #5 rb_podcast_manager_event_loop
    at rb-podcast-manager.c line 1516
  • #6 g_list_remove_link
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main
    at main.c line 425

Comment 4 Andrea V. 2006-05-09 21:09:46 UTC
The following is the same backtrace made with gdb:

Thread 11 (Thread 156670880 (LWP 4671))

  • #0 __nptl_death_event
    from /lib/libpthread.so.0
  • #1 start_thread
    from /lib/libpthread.so.0
  • #2 clone
    from /lib/libc.so.6

Thread 10 (Thread 156670880 (LWP 4670))

  • #0 __nptl_death_event
    from /lib/libpthread.so.0
  • #1 start_thread
    from /lib/libpthread.so.0
  • #2 clone
    from /lib/libc.so.6

Thread 1 (Thread -1208813088 (LWP 4659))

  • #0 rhythmdb_entry_set_uninserted
    at rhythmdb.c line 2659
  • #1 rb_podcast_manager_event_loop
    at rb-podcast-manager.c line 1516
  • #2 g_list_remove_link
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #6 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #7 main
    at main.c line 425

Comment 5 Jonathan Matthew 2006-05-09 22:08:30 UTC
This is probably going to be specific to a particular podcast feed.  Can you give us your feed URLs?
Comment 6 Andrea V. 2006-05-10 15:26:48 UTC
This is the feed URL that I am using at the moment (only this one)...

http://www.ilsole24ore.com/rss/radio24_podcasting.xml
Comment 7 Jonathan Matthew 2006-05-11 23:06:32 UTC
This feed works fine for me with current CVS HEAD.  Judging by the stack trace, the problem was fixed in response to bug 339712, so I'm marking this as a duplicate.

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