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 521208 - Restarting HAL causes rhythmbox to freeze up and consume 100% CPU
Restarting HAL causes rhythmbox to freeze up and consume 100% CPU
Status: RESOLVED DUPLICATE of bug 547851
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-08 16:16 UTC by Sam Morris
Modified: 2008-08-14 23:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Morris 2008-03-08 16:16:31 UTC 
Steps to reproduce:
1. Run Rhythmbox
2. Restart hal-daemon


Stack trace:
(gdb) bt full

+ Trace 191757

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/i686/cmov/libpthread.so.0
  • #2 _L_lock_95
    from /lib/i686/cmov/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #4 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #5 rhythmdb_push_event
    at rhythmdb.c line 341
  • #6 dispatch_job_callback
    at gnome-vfs-job.c line 229
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #9 ?? 


Other information:
Using 0.11.4
Comment 1 Sam Morris 2008-03-16 17:11:25 UTC 
Actually, it looks like this isn't caused by restarting hal alone--but restarting the whole system-wide dbus daemon triggers it.
Comment 2 Jonathan Matthew 2008-08-14 23:21:58 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 547851 ***