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 132497 - GEdit crash during editing
GEdit crash during editing
Status: RESOLVED DUPLICATE of bug 105745
Product: gedit
Classification: Applications
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2004-01-25 18:17 UTC by martin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description martin 2004-01-25 18:17:44 UTC 
Package: gedit
Severity: critical
Version: 2.2.0
Synopsis: GEdit crash during editing
Bugzilla-Product: gedit
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

The application GEdit crashed with a segmentation fault during editing.
I didn't use any special features of the program however I think I
accidentally pressed some strange key-combination involving multiple
keys on the lower-left side of the keyboard (possible, ctrl, alt, shift,
"windows key" maybe in combination with one or more letters).

Steps to reproduce the problem:

I'm not aware of how to reproduce the problem.

Actual Results:

Program crash.

Expected Results:

Normal operation.

How often does this happen?

First time.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gedit'

(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)...(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)...[New
Thread 1091429216 (LWP 3643)]
0xffffe002 in ??
    ()

+ Trace 43479

Thread 1 (Thread 1091429216 (LWP 3643))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




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

The original reporter (martin@thiim.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, maggi@athena.polito.it.
Comment 1 Elijah Newren 2004-01-29 23:51:31 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 105745 ***