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 399234 - crash in Rhythmbox Music Player: running software updates...
crash in Rhythmbox Music Player: running software updates...
Status: RESOLVED DUPLICATE of bug 359974
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-22 02:14 UTC by potoose
Modified: 2007-01-22 08:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description potoose 2007-01-22 02:14:56 UTC
What were you doing when the application crashed?
running software updates and applying changes


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 31186944 vsize: 0 resident: 31186944 share: 0 rss: 14856192 rss_rlim: 0
CPU usage: start_time: 1169432033 rtime: 0 utime: 114 stime: 0 cutime:96 cstime: 0 timeout: 18 it_real_value: 0 frequency: 5

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228236608 (LWP 10395)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1228236608 (LWP 10395))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 rb_proxy_config_new
  • #5 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_set
    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 rb_proxy_config_new
  • #11 rb_shell_new
  • #12 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #15 rb_shell_new
  • #16 main
  • #0 __kernel_vsyscall

Comment 1 James "Doc" Livingston 2007-01-22 08:18:48 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.

Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.


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