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 146487 - terminal crash when using vi to open a remote file
terminal crash when using vi to open a remote file
Status: RESOLVED DUPLICATE of bug 139542
Product: gnome-applets
Classification: Other
Component: mini-commander
1.0.x
Other other
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-06-10 04:20 UTC by wlin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description wlin 2004-07-09 05:44:10 UTC 
Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-applets
Severity: normal
Version: GNOME2.6. 2.6.0
Gnome-Distributor: Red Hat, Inc
Synopsis: term error when i use vi to open a remote file
Bugzilla-Product: gnome-applets
Bugzilla-Component: mini-commander
Bugzilla-Version: 2.6.0
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...[Thread debugging using libthread_db enabled]
[New Thread -151082368 (LWP 14456)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x00925402 in ?? ()

+ Trace 47972

Thread 1 (Thread -151082368 (LWP 14456))

  • #0 ??
  • #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 ??
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_string_erase
    from /usr/lib/libglib-2.0.so.0
  • #10 _g_log_fallback_handler
    from /usr/lib/libglib-2.0.so.0
  • #11 g_log_default_handler
    from /usr/lib/libglib-2.0.so.0
  • #12 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #13 g_log
    from /usr/lib/libglib-2.0.so.0
  • #14 vte_terminal_set_default_colors
    from /usr/lib/libvte.so.4
  • #15 vte_terminal_fork_command
    from /usr/lib/libvte.so.4
  • #16 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 01:44 -------


Unknown version 2.6.0 in product gnome-applets. Setting version to "1.0.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-applets".
   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 wlin@ict.ac.cn.
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 Christian Neumair 2004-07-22 14:57:38 UTC 
Thanks for your bug report. Could you please be a bit more precise, though? What
do you mean by opening remote files via vim? Is this crash reproducible? If so,
what are the concrete steps required to do so?
I'm not sure whether you filed the bug against the right software product either.

regs,
 Chris
Comment 2 Elijah Newren 2004-11-08 15:59:37 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 the stack trace in bug 153615, which has been marked as a duplicate of
139542.
Comment 3 Elijah Newren 2004-11-08 15:59:53 UTC 

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