Color schemes can't be disabled

Bug #144859 reported by Daniel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Incomplete
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

gEdit in Gutsy Gibbon is missing the option to disable colour schemes for syntax highlighting. This is especially painful since gEdit is already freezing with an MySQL dump file of 400kb size.

Is there any chance to get the option to disable syntax highlighting back until gEdit can handle larger files better?

ProblemType: Bug
Architecture: i386
Date: Tue Sep 25 18:51:02 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: fglrx
Package: gedit 2.20.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gedit
ProcCwd: /home/theluda
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
Uname: Linux dsr-laptop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
Daniel (theluda) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, Does disable the highlight by gconf-editor -> apps/gedit-2/syntax_highlighting works for you? May you please also try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. for seeing why it's hanging ? thanks in advance.

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Daniel (theluda) wrote :

I have now tried disabling syntax highlighting by disabling it with gconf-editor under apps/gedit-2/preferences/syntax_highlighting. gedit starts and opens files now without syntax highlighting (as expected), but the SQL file still leads to gedit freezing. I am now going to produce a backtrace for you. Hopefully that will work. More coming soon.

Revision history for this message
Daniel (theluda) wrote :

Well, I have tried hard to create a backtrace, but actually the program does not crash, it just seems to fall asleep for endless time. I nailed down the issue with some trial and error sessions. Apparently the issue is not really the file size, but rather the long text lines.

I tried an indented version of the same SQL file, where INSERT statements had been split into multiple lines and it loaded fine, and gedit did not freeze.
Using the same file with INSERT statements in on long line (189 INSERT rows, each about 200 characters), gedit just did nothing. I could browse a few lines down, then the text edit control went all white and stayed this way for ages. Gave up after waiting a few hours in the evening.

Is there anything else I can do to help finding the reason for this freeze or slowdown? Backtrace wasn't the thing to do it seems, as it does not crash. Shall I try Valgrind?

Revision history for this message
Daniel (theluda) wrote :

Forgot this one. I am now attaching the SQL file, probably it helps to try the thing for yourself.

Revision history for this message
Sebastien Bacher (seb128) wrote :

looks something similar to bug #26439

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.