Bug#675249:

2013-11-06 Thread althaser
yep, it's fixed with gedit 3.8.3-4

Bug#675249: gedit: Crashes with too high column number given

2012-09-18 Thread Dawid Toton
Fixed upstream: http://git.gnome.org/browse/gedit/commit/?id=581297bd49268145c0ed958f74db81d4c709de10 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#675249: Properly formatted patch

2012-05-30 Thread Dawid Toton
I attach the same patch formatted with git. >From 1d21f97b4d3c1e184ea3b3cb9fba798d0aec7281 Mon Sep 17 00:00:00 2001 From: Dawid Toton Date: Wed, 30 May 2012 22:24:58 +0200 Subject: [PATCH] Avoid crash in case column number given in cmdline is too high - with already open files --- gedit/gedit-

Bug#675249: A patch for this

2012-05-30 Thread Dawid Toton
The attached change should be made to gedit-commands-file.c, it fixes the issue for already opened files. I believe the other case (newly opened files) is related to gedit-document.c, about line 1475. 161a162,164 > /* user side: 1-based idex; gedit internal: 0-based index */ >

Bug#675249: gedit: Crashes with too high column number given

2012-05-30 Thread Dawid Toton
Package: gedit Version: 3.4.2-1 Severity: important Dear Maintainer, To reproduce: echo four >/tmp/four gedit /tmp/four +1:6 Outcome: A crash with (gedit:26206): Gtk-ERROR **: Char offset 5 is off the end of the line Trace/breakpoint trap and data loss (changes in all open files in all ged