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 164024 - gnome-terminal crashed during editing (using vim)
gnome-terminal crashed during editing (using vim)
Status: RESOLVED DUPLICATE of bug 162433
Product: gnome-terminal
Classification: Core
Component: general
2.7.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-14 02:17 UTC by ml+gnome-bugs
Modified: 2005-01-14 02:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description ml+gnome-bugs 2005-01-14 02:17:44 UTC 
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.0 2.7.x
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-terminal crashed during editing (using vim)
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.7.x
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
gnome-terminal crashed during editing (using vim).  The top of the
terminal screen was reverse video, probably due to inadvertent selection
by accidentally hitting mouse button and maybe moving cursor on laptop.

I don't think this problem will be readily reproducible.

How often does this happen?

I've been able to make it happen several times, but it's difficult
to say how to reproduce.  Editing with vim, I was about four lines
down in a file, inserting the string "$TXTPATH" with the right shift
key held down and probably hit mouse buttons and mouse position knob
inadvertently (due to laptop keyboard layout and size).  I believe that
(due to that) I had selected the text from the line being editing up through
the top of the file/screen.  The crash seems to be related to that.

The above seems to be consistent with the stack trace showing a
failure from within strcmp, called from vte_terminal_get_text_range.
Presumably strcmp was called with bad args.

+ Trace 54489

Thread 1 (Thread -1208149792 (LWP 5667))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/libc.so.6
  • #5 vte_terminal_get_text_range
    from /usr/lib/libvte.so.4
  • #6 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-13 21:17 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was ml+gnome-bugs@riyescott.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Elijah Newren 2005-01-14 02:21:23 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 162433 ***