Bug 383705 – crash in Rhythmbox Music Player: je bouffais des chips et...

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 383705 - crash in Rhythmbox Music Player: je bouffais des chips et...


Summary:	crash in Rhythmbox Music Player: je bouffais des chips et...


Status:	RESOLVED DUPLICATE of bug 359974

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-08 12:12 UTC by vincent_w_6
Modified:	2006-12-08 15:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description vincent_w_6 2006-12-08 12:12:09 UTC

What were you doing when the application crashed?
je bouffais des chips et alors qu'est-ce que sa peut te foutre??


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

Memory status: size: 32227328 vsize: 0 resident: 32227328 share: 0 rss: 15577088 rss_rlim: 0
CPU usage: start_time: 1165579855 rtime: 0 utime: 60 stime: 0 cutime:56 cstime: 0 timeout: 4 it_real_value: 0 frequency: 4

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 -1228982608 (LWP 6658)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92548

Thread 1 (Thread -1228982608 (LWP 6658))

#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 Alex Lancaster 2006-12-08 15:07:47 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 359974 ***