Bug 118771 – abort() in vte_terminal_fork_command (gnome-terminal)

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 118771 - abort() in vte_terminal_fork_command (gnome-terminal)


Summary:	abort() in vte_terminal_fork_command (gnome-terminal)


Status:	RESOLVED DUPLICATE of bug 107234

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-07-31 13:56 UTC by David Eriksson
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description David Eriksson 2003-07-31 13:56:36 UTC

Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: abort() in vte_terminal_fork_command (gnome-terminal)
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Versions:

vte-0.10.25-1
gnome-terminal-2.2.1-3

Comments:

The backtrace is quite useless as I don't know where to find the
apropriate -debuginfo packages.

This is quite similar to bug #87786 but as the backtrace was different I
decided to make a new bug.




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1087605760 (LWP 551)]
0xffffe002 in ??
    ()

+ Trace 39186

Thread 1 (Thread 1087605760 (LWP 551))

#0 ??
#1 libgnomeui_segv_handle
at gnome-ui-init.c line 646
#2 <signal handler called>
#3 ??
#4 abort
from /lib/tls/libc.so.6
#5 g_logv
from /usr/lib/libglib-2.0.so.0
#6 g_log
from /usr/lib/libglib-2.0.so.0
#7 vte_terminal_fork_command
from /usr/lib/libvte.so.4
#8 g_main_context_wakeup
from /usr/lib/libglib-2.0.so.0
#9 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#13 gtk_main
at gtkmain.c line 1092
#14 main
#15 __libc_start_main
from /lib/tls/libc.so.6
#0 ??



-- 
-\- David Eriksson -/-                              www.2GooD.nu
 
"I personally refuse to use inferior tools because of ideology."
                                                - Linus Torvalds




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-31 09:56 -------

Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.

Comment 1 David Eriksson 2003-07-31 14:01:27 UTC

Correcting reference to similar bug:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=87786

Comment 2 Elijah Newren 2003-07-31 18:28:18 UTC

Thanks for trying to look for duplicates.  However, this is a
duplicate of bug 107234, not the others.  The good news is that this
bug has been fixed, so when you upgrade, you shouldn't experience this
problem anymore.

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