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 603843 - crash in Terminal: fdisk on a usb thumb dri...
crash in Terminal: fdisk on a usb thumb dri...
Status: RESOLVED DUPLICATE of bug 596460
Product: gnome-terminal
Classification: Core
Component: BugBuddyBugs
2.28.x
Other All
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-12-05 12:47 UTC by drpaul65
Modified: 2009-12-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description drpaul65 2009-12-05 12:47:27 UTC
Version: 2.28.0

What were you doing when the application crashed?
fdisk on a usb thumb drive


Distribution:                   Solaris Express Community Edition snv_126 X86
Gnome Release: 2.28.0 2009-10-12 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 142716928 vsize: 142716928 resident: 21405696 share: 4370432 rss: 21405696 rss_rlim: 0
CPU usage: start_time: 1260017094 rtime: 24 utime: 214826 stime: 35100 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

6330:	gnome-terminal
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, 18c1, 8046850, 3)
 feea3305 waitpid  (18c1, 804690c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 828c640, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (828c688, 0, 0, 0, 8046a2c) + 5c
 fe071e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a6030, 18ba, 0, fe071ff2) + f3
 fe0720d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046ab4, feeee735, b, 0) + 12e
 fe071a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046b68, fecc2a00, fef81000, 8046b24) + 64
 feeee735 __sighndlr (b, 0, 8046b68, fe071a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 8046b68) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fdd8ce63 _vte_terminal_ring_append (81cb0f0, 0, 50, fddaf706) + 1f
 fddaf81d vte_sequence_handler_cd (81cafe8, 0, 826eeec, fddb2112) + 125
 fddb2178 vte_sequence_handler_erase_in_display (81cafe8, 8149a70, f, fddb376a) + 74
 fddb3895 _vte_terminal_handle_sequence (81cafe8, 81d4488, 50c, 8149a70) + 139
 fdd92d99 vte_terminal_process_incoming (81cafe8, 0) + 405
 fdda481c time_process_incoming (81cafe8, 1, 81cafe8, fdda48ae) + 2c
 fdda4a4c process_timeout (0, fedcc460, 8046fb8, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (80cd598, fdda48a0, 0, 8047030) + 23
 fed24eee g_main_context_dispatch (80cb5f8, 0, 826c2c0, b) + 262
 fed2559f g_main_context_iterate (80cb5f8, 1, 1, 80a6828) + 483
 fed25bc9 g_main_loop_run (82523e8, 82523e8, 80a9800, fe97e726) + 1dd
 fe97e7cf gtk_main (fefd4e56, 0, 8105684, feffb804, 8047210, fefdcf48) + b7
 0806b594 main     (1, 804726c, 8047274, feffb804) + 944
 080677fd _start   (1, 8047394, 0, 80473a3, 80473ed, 8047421) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (14, f83fef50, 14)
 fed270c1 child_watch_helper_thread (0, 826c290, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (826c290, fef81000, f83fefe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fe230a00) + 9b
 feeee650 _lwp_start (fe230a00, 0, 0, 0, 0, 0)
Comment 1 Fabio Durán Verdugo 2009-12-05 13:32:01 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 bug 470408 ***
Comment 2 Christian Persch 2009-12-05 13:45:35 UTC

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