Bug 390644 – crash in Terminal: Rythmbox just crashed & ...

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 390644 - crash in Terminal: Rythmbox just crashed & ...


Summary:	crash in Terminal: Rythmbox just crashed & ...


Status:	RESOLVED DUPLICATE of bug 348470

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-29 11:35 UTC by wybo_wiersma
Modified:	2006-12-29 19:22 UTC

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

Description wybo_wiersma 2006-12-29 11:35:53 UTC

Version: 2.16.1

What were you doing when the application crashed?
Rythmbox just crashed & I was using Vim


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

Memory status: size: 89673728 vsize: 0 resident: 89673728 share: 0 rss: 24678400 rss_rlim: 0
CPU usage: start_time: 1167227759 rtime: 0 utime: 16925 stime: 0 cutime:14372 cstime: 0 timeout: 2553 it_real_value: 0 frequency: 32290

Backtrace was generated from '/usr/bin/gnome-terminal'

(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 -1226455376 (LWP 4813)]
[New Thread -1276150880 (LWP 4817)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 97764

Thread 1 (Thread -1226455376 (LWP 4813))

#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 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#5 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#6 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#7 vte_terminal_feed_child_binary
from /usr/lib/libvte.so.9
#8 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#9 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gdk_window_is_viewable
from /usr/lib/libgdk-x11-2.0.so.0
#17 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#18 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
#25 ??
#26 _IO_stdin_used
#27 ??
#28 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2006-12-29 19:22:03 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 348470 ***