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 127900 - gedit crashes after "Display Line Numbers" de-selected
gedit crashes after "Display Line Numbers" de-selected
Status: RESOLVED DUPLICATE of bug 120118
Product: gedit
Classification: Applications
Component: general
2.4.x
Other Linux
: Normal critical
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2003-11-25 16:21 UTC by s.i.meredith
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description s.i.meredith 2003-11-25 16:21:47 UTC
Loaded a text file
Selected [Preferences]
Selected [Line Numbers]
Tick "Display Line Numbers"
then un-tick "Display Line Numbers" and... CRASH!

For an extra crash, now select the option to report to BugZilla!
Comment 1 s.i.meredith 2003-11-26 09:51:42 UTC
Starting program: /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)...
(no debugging symbols found)...(no debugging symbols found)...[New 
Thread 16384 (LWP 12929)]
 
(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)...
(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)...
 
(gedit:12929): GnomeUI-WARNING **: While connecting to session 
manager:
Authentication Rejected, reason : None of the authentication protocols 
specified are supported and host-based authentication failed.
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.

Thread 16384 (LWP 12929)

  • #0 gdk_window_get_toplevel
  • #1 ??


Comment 2 s.i.meredith 2003-11-26 09:54:09 UTC
Error occurs at point

"Program received signal SIGSEGV, Segmentation fault."

in above gdb listing when I de-select line numbers
Comment 3 s.i.meredith 2003-11-26 10:01:18 UTC
gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice)
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There 
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.


Compiler options

CHOST="i686-pc-linux-gnu"
CFLAGS="-O1 -mcpu=i686"

and tried CFLAGS="-O2 -mcpu=i686"
Comment 4 Paolo Maggi 2003-12-11 15:20:46 UTC

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