Bug 353599 – crash in Terminal: Running 'mpg321 *mp3' in...

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 353599 - crash in Terminal: Running 'mpg321 *mp3' in...


Summary:	crash in Terminal: Running 'mpg321 *mp3' in...


Status:	RESOLVED DUPLICATE of bug 348979

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.15.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-08-30 20:59 UTC by dcantrell
Modified:	2006-09-17 19:48 UTC

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

Description dcantrell 2006-08-30 20:59:25 UTC

Version: 2.15.4

What were you doing when the application crashed?
Running 'mpg321 *mp3' in a terminal, selected Open New Tab to start a new shell.


Distribution: Fedora Core release 5.91 (FC6 Test2)
Gnome Release: 2.15.92 2006-08-21 (Red Hat, Inc)
BugBuddy Version: 2.15.92

Memory status: size: 68034560 vsize: 0 resident: 68034560 share: 0 rss: 16936960 rss_rlim: 0
CPU usage: start_time: 1156948775 rtime: 0 utime: 2333 stime: 0 cutime:1866 cstime: 0 timeout: 467 it_real_value: 0 frequency: 24798

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208891696 (LWP 2722)]
[New Thread -1215112304 (LWP 2772)]
(no debugging symbols found)
0xb7f3f402 in __kernel_vsyscall ()

+ Trace 71280

Thread 1 (Thread -1208891696 (LWP 2722))

#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 g_type_check_is_value_type
from /lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#8 g_signal_emit
from /lib/libgobject-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_rc_get_module_dir
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#30 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#31 g_main_context_check
from /lib/libglib-2.0.so.0
#32 g_main_loop_run
from /lib/libglib-2.0.so.0
#33 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#34 g_cclosure_marshal_VOID__OBJECT
#35 __libc_start_main
from /lib/libc.so.6
#36 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2006-09-08 17:58:15 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 Karsten Bräckelmann 2006-09-17 19:34:50 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.


Matches bug 348979, which is a duplicate of bug 348814.

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

Comment 3 Karsten Bräckelmann 2006-09-17 19:48:46 UTC

Moving around. Sorry for the noise.


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