Hi,
I just ran into a rather serious Geany bug that can cause file loss.
Incidentally I had the hard disk partition full (on Linux) and Geany was happily reporting that file saving is successful. I had about 20 open files, worth about 2 hours of work. When I was done I saved all the files and closed Geany. Seconds later, I realized that all my files have size of zero bytes. Not only that I lost the recent changes, but complete files. This happen just prior to the commit to Git repository I planned. Obviously, I have nothing to commit. :(
Le 10/11/2010 13:56, Milan Babuskov a écrit :
Hi,
I just ran into a rather serious Geany bug that can cause file loss.
Incidentally I had the hard disk partition full (on Linux) and Geany was happily reporting that file saving is successful. I had about 20 open files, worth about 2 hours of work. When I was done I saved all the files and closed Geany. Seconds later, I realized that all my files have size of zero bytes. Not only that I lost the recent changes, but complete files. This happen just prior to the commit to Git repository I planned. Obviously, I have nothing to commit. :(
Very sorry to hear :/
There is currently a discussion on the devel mailing list to improve file saving, but you can already use an alternative file saving method that is safer (e.g. will properly fail, and won't loose the original data) -- but has other disadvantages, see below. I don't know if there is a preference visible in the UI somewhere, but you can set the "use_safe_file_saving" preference to "true" in ~/.config/geany/geany.conf.
The problem of that alternative method is that it will (or might?) loose file attributes (e.g. permissions -- such as the executable bit --, etc).
Hope it helps in the meantime.
Regards, Colomban
On 11/10/2010 04:56 AM, Milan Babuskov wrote:
Hi,
I just ran into a rather serious Geany bug that can cause file loss.
Incidentally I had the hard disk partition full (on Linux) and Geany was happily reporting that file saving is successful. I had about 20 open files, worth about 2 hours of work. When I was done I saved all the files and closed Geany. Seconds later, I realized that all my files have size of zero bytes. Not only that I lost the recent changes, but complete files. This happen just prior to the commit to Git repository I planned. Obviously, I have nothing to commit. :(
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Jerry
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLisle jvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
Nick
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
Nick _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Le 10/11/2010 22:23, Jerry DeLisle a écrit :
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
Not sure, but looks like a GTK+ bug that was (is?) in 2.20 IIRC. Anyway, the bug was in the file chooser code that monitors changes, and since Geany never destroys it's file chooser (only hide it on close), it may crash even if the dialog is now closed. I don't know it Fedora 13 has this bug, but it's worth checking.
If so, basically you need to: 1) open the file chooser dialog of Geany (file -> open) 2) do things that would trigger a file chooser update (touching, creating, deleting, etc. files in the directory it monitors)
This wouldn't crash at every time, but e.g. building a moderately small application is likely to do enough changes.
BTW, if it is this bug, you must see a warning just before Geany quits, so you need to launch Geany from a terminal.
Regards, Colomban
On 11 November 2010 08:23, Jerry DeLisle jvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
Cheers Lex
Nick _______________________________________________ Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 11/10/2010 01:43 PM, Lex Trotman wrote:
On 11 November 2010 08:23, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
OK, finally caught it. Here is gdb session before and at the problem.
Hope this helps,
Jerry
[New Thread 0x7fffd7fff710 (LWP 16563)] [Thread 0x7fffd7fff710 (LWP 16563) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/pr45794.diff : Diff (UTF-8) [Thread 0x7ffff008e710 (LWP 16556) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/trans-expr.c : C (UTF-8) [New Thread 0x7ffff008e710 (LWP 16564)] [New Thread 0x7fffd7fff710 (LWP 16566)] [Thread 0x7ffff008e710 (LWP 16564) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/pr45794.diff : Diff (UTF-8) [Thread 0x7fffd7fff710 (LWP 16566) exited] [New Thread 0x7fffd7fff710 (LWP 16573)] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/ChangeLog : None (UTF-8) [Thread 0x7fffd7fff710 (LWP 16573) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/ChangeLog : None (UTF-8) [New Thread 0x7fffd7fff710 (LWP 16574)] [Thread 0x7fffd7fff710 (LWP 16574) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/ChangeLog : None (UTF-8) [New Thread 0x7fffd7fff710 (LWP 16576)] [Thread 0x7fffd7fff710 (LWP 16576) exited] Geany-INFO: /home/jerry/prs/pr45794/pr45794.f90 : Fortran (UTF-8) [New Thread 0x7fffd7fff710 (LWP 22662)] [New Thread 0x7ffff008e710 (LWP 22663)] [Thread 0x7fffd7fff710 (LWP 22662) exited] [New Thread 0x7fffd7fff710 (LWP 22664)] [Thread 0x7fffd7fff710 (LWP 22664) exited] [New Thread 0x7fffd7fff710 (LWP 22665)] [New Thread 0x7fffd75fe710 (LWP 22666)] [Thread 0x7fffd75fe710 (LWP 22666) exited] [Thread 0x7fffd7fff710 (LWP 22665) exited] [Thread 0x7ffff008e710 (LWP 22663) exited] [New Thread 0x7ffff008e710 (LWP 22667)] [New Thread 0x7fffd7fff710 (LWP 22668)] [New Thread 0x7fffd75fe710 (LWP 22669)] [New Thread 0x7fffeebfd710 (LWP 22670)] [Thread 0x7ffff008e710 (LWP 22667) exited] [Thread 0x7fffeebfd710 (LWP 22670) exited] [Thread 0x7fffd75fe710 (LWP 22669) exited] [New Thread 0x7fffd75fe710 (LWP 22671)] [Thread 0x7fffd7fff710 (LWP 22668) exited] [Thread 0x7fffd75fe710 (LWP 22671) exited] [New Thread 0x7fffd75fe710 (LWP 22692)] [New Thread 0x7fffd7fff710 (LWP 22693)] [New Thread 0x7fffeebfd710 (LWP 22694)] [New Thread 0x7ffff008e710 (LWP 22695)] Geany-INFO: /home/jerry/gcc/trunk/gcc/testsuite/gfortran.dg/optional_mask.f90 : Fortran (UTF-8) [Thread 0x7ffff008e710 (LWP 22695) exited] [Thread 0x7fffeebfd710 (LWP 22694) exited] [Thread 0x7fffd75fe710 (LWP 22692) exited] [New Thread 0x7fffd75fe710 (LWP 22696)] [New Thread 0x7fffeebfd710 (LWP 22697)] [New Thread 0x7ffff008e710 (LWP 22698)] [Thread 0x7fffeebfd710 (LWP 22697) exited] [Thread 0x7fffd7fff710 (LWP 22693) exited] [Thread 0x7ffff008e710 (LWP 22698) exited] [Thread 0x7fffd75fe710 (LWP 22696) exited] Geany-INFO: /home/jerry/gcc/trunk/gcc/fortran/ChangeLog : None (UTF-8) [New Thread 0x7fffd75fe710 (LWP 22867)] [Thread 0x7fffd75fe710 (LWP 22867) exited] [New Thread 0x7fffd75fe710 (LWP 22870)] [New Thread 0x7ffff008e710 (LWP 22871)] [New Thread 0x7fffd7fff710 (LWP 22872)] [New Thread 0x7fffeebfd710 (LWP 22873)] [New Thread 0x7fffee0e2710 (LWP 22874)] [New Thread 0x7fffe5856710 (LWP 22875)] [New Thread 0x7fffe4e55710 (LWP 22876)] [Thread 0x7ffff008e710 (LWP 22871) exited] [Thread 0x7fffe4e55710 (LWP 22876) exited] [Thread 0x7fffee0e2710 (LWP 22874) exited] [Thread 0x7fffd75fe710 (LWP 22870) exited] [Thread 0x7fffe5856710 (LWP 22875) exited] [Thread 0x7fffd7fff710 (LWP 22872) exited] [New Thread 0x7fffd7fff710 (LWP 22878)] [New Thread 0x7fffe5856710 (LWP 22879)] [New Thread 0x7fffd75fe710 (LWP 22880)] [New Thread 0x7ffff008e710 (LWP 22881)] ** Gtk:ERROR:gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion failed: (r == n_visible_rows)
Program received signal SIGABRT, Aborted. Dwarf Error: wrong version in compilation unit header (is 256, should be 2, 3, or 4) [in module /home/jerry/gcc/usr/lib64/libstdc++.so.6] (gdb) c Continuing. Dwarf Error: bad offset (0x2d0300) in compilation unit header (offset 0x0 + 6) [in module /home/jerry/gcc/usr/lib64/libgcc_s.so.1] (gdb) c Continuing. [Thread 0x7ffff008e710 (LWP 22881) exited] [Thread 0x7fffd75fe710 (LWP 22880) exited] [Thread 0x7fffe5856710 (LWP 22879) exited] [Thread 0x7fffd7fff710 (LWP 22878) exited] [Thread 0x7fffeebfd710 (LWP 22873) exited] [Thread 0x7fffecf5c710 (LWP 3157) exited]
Program terminated with signal SIGABRT, Aborted. The program no longer exists.
On 13 November 2010 10:13, Jerry DeLisle jvdelisle@frontier.com wrote:
On 11/10/2010 01:43 PM, Lex Trotman wrote:
On 11 November 2010 08:23, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
OK, finally caught it. Here is gdb session before and at the problem.
Hope this helps,
Jerry
<snip>
[New Thread 0x7ffff008e710 (LWP 22881)] ** Gtk:ERROR:gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion failed: (r == n_visible_rows)
Ok, this comes from inside the GTK file dialog, what were you doing at the time?
Program received signal SIGABRT, Aborted. Dwarf Error: wrong version in compilation unit header (is 256, should be 2, 3, or 4) [in module /home/jerry/gcc/usr/lib64/libstdc++.so.6]
I'm presuming that this file is one you compiled yourself (being in your home dir and all) probably not good for stability that Geany is using it unless Geany has been compiled against it ??
Cheers Lex
(gdb) c Continuing. Dwarf Error: bad offset (0x2d0300) in compilation unit header (offset 0x0 + 6) [in module /home/jerry/gcc/usr/lib64/libgcc_s.so.1] (gdb) c Continuing. [Thread 0x7ffff008e710 (LWP 22881) exited] [Thread 0x7fffd75fe710 (LWP 22880) exited] [Thread 0x7fffe5856710 (LWP 22879) exited] [Thread 0x7fffd7fff710 (LWP 22878) exited] [Thread 0x7fffeebfd710 (LWP 22873) exited] [Thread 0x7fffecf5c710 (LWP 3157) exited]
Program terminated with signal SIGABRT, Aborted. The program no longer exists.
Le 13/11/2010 01:07, Lex Trotman a écrit :
On 13 November 2010 10:13, Jerry DeLisle jvdelisle@frontier.com wrote:
On 11/10/2010 01:43 PM, Lex Trotman wrote:
On 11 November 2010 08:23, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
Maybe related. I have been seeing geany self exit. I am trying to nail down what I am doing to cause it. Generally I will have a separate gnome-terminal session going. Some times I will touch open files so to force re-compilation (gcc/gfortran development so I am building gcc all the time) Somewhere in this process geany just exits. Running on x86-64-Linux Fedora 13, latest updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
OK, finally caught it. Here is gdb session before and at the problem.
Hope this helps,
Jerry
<snip> > [New Thread 0x7ffff008e710 (LWP 22881)] > ** > Gtk:ERROR:gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion > failed: (r == n_visible_rows) >
Ok, this comes from inside the GTK file dialog, what were you doing at the time?
Program received signal SIGABRT, Aborted. Dwarf Error: wrong version in compilation unit header (is 256, should be 2, 3, or 4) [in module /home/jerry/gcc/usr/lib64/libstdc++.so.6]
I'm presuming that this file is one you compiled yourself (being in your home dir and all) probably not good for stability that Geany is using it unless Geany has been compiled against it ??
As already said, I think it is not a Geany but a GTK+ bug. BTW, https://bugzilla.redhat.com/show_bug.cgi?id=603781
This bug (that isn't fedora-specific) happens sometimes when the GTK+ file chooser gets updated. Since Geany never destroys its filechooser, it makes it more vulnerable to this bug than some other software.
Regards, Colomban
On 13 November 2010 11:36, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 13/11/2010 01:07, Lex Trotman a écrit :
On 13 November 2010 10:13, Jerry DeLisle jvdelisle@frontier.com wrote:
On 11/10/2010 01:43 PM, Lex Trotman wrote:
On 11 November 2010 08:23, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote:
On Wed, 10 Nov 2010 08:48:24 -0800 Jerry DeLislejvdelisle@frontier.com wrote:
> Maybe related. I have been seeing geany self exit. I am trying to > nail > down > what I am doing to cause it. Generally I will have a separate > gnome-terminal > session going. Some times I will touch open files so to force > re-compilation > (gcc/gfortran development so I am building gcc all the time) Somewhere > in > this > process geany just exits. Running on x86-64-Linux Fedora 13, latest > updates
Doesn't sound related.
What version of Geany?
Version is 0.19.1
It would help to fix your segfault if you can get a backtrace in a debugger - see: http://www.geany.org/Support/Bugs
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
OK, finally caught it. Here is gdb session before and at the problem.
Hope this helps,
Jerry
<snip> > [New Thread 0x7ffff008e710 (LWP 22881)] > ** > Gtk:ERROR:gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion > failed: (r == n_visible_rows) >
Ok, this comes from inside the GTK file dialog, what were you doing at the time?
Program received signal SIGABRT, Aborted. Dwarf Error: wrong version in compilation unit header (is 256, should be 2, 3, or 4) [in module /home/jerry/gcc/usr/lib64/libstdc++.so.6]
I'm presuming that this file is one you compiled yourself (being in your home dir and all) probably not good for stability that Geany is using it unless Geany has been compiled against it ??
As already said, I think it is not a Geany but a GTK+ bug. BTW, https://bugzilla.redhat.com/show_bug.cgi?id=603781
This bug (that isn't fedora-specific) happens sometimes when the GTK+ file chooser gets updated. Since Geany never destroys its filechooser, it makes it more vulnerable to this bug than some other software.
Regards, Colomban
Thanks, Colomban, yes that looks like it.
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 11/12/2010 04:50 PM, Lex Trotman wrote:
On 13 November 2010 11:36, Colomban Wendlinglists.ban@herbesfolles.org wrote:
Le 13/11/2010 01:07, Lex Trotman a écrit :
On 13 November 2010 10:13, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 01:43 PM, Lex Trotman wrote:
On 11 November 2010 08:23, Jerry DeLislejvdelisle@frontier.com wrote:
On 11/10/2010 09:16 AM, Nick Treleaven wrote: > > On Wed, 10 Nov 2010 08:48:24 -0800 > Jerry DeLislejvdelisle@frontier.com wrote: > >> Maybe related. I have been seeing geany self exit. I am trying to >> nail >> down >> what I am doing to cause it. Generally I will have a separate >> gnome-terminal >> session going. Some times I will touch open files so to force >> re-compilation >> (gcc/gfortran development so I am building gcc all the time) Somewhere >> in >> this >> process geany just exits. Running on x86-64-Linux Fedora 13, latest >> updates > > Doesn't sound related. > > What version of Geany?
Version is 0.19.1 > > It would help to fix your segfault if you can get a backtrace in a > debugger - see: > http://www.geany.org/Support/Bugs >
I will see what I can do. It's one of those intermittent sort.
You can also run geany with --verbose and see what messages (Geany or GTK) you get when it happens.
OK, finally caught it. Here is gdb session before and at the problem.
Hope this helps,
Jerry
<snip> > [New Thread 0x7ffff008e710 (LWP 22881)] > ** > Gtk:ERROR:gtkfilesystemmodel.c:746:gtk_file_system_model_sort: assertion > failed: (r == n_visible_rows) >
Ok, this comes from inside the GTK file dialog, what were you doing at the time?
I just completed a Copy/Paste from geany to gnome terminal during an svn commit in one directory, then I opened another file in a different directory to edit it. One was gcc/fortran/ChangeLog the other was gcc/testsuite/ChangeLog. I recall that I ran svn update on that second file to make sure I was editing the latest version. That would mean the contents got changed while geany had the file opened.
I suspect the gtk guys need to do
Program received signal SIGABRT, Aborted. Dwarf Error: wrong version in compilation unit header (is 256, should be 2, 3, or 4) [in module /home/jerry/gcc/usr/lib64/libstdc++.so.6]
I'm presuming that this file is one you compiled yourself (being in your home dir and all) probably not good for stability that Geany is using it unless Geany has been compiled against it ??
Yes I did build it. gdb/dwarf obviously does not like it. :)
As already said, I think it is not a Geany but a GTK+ bug. BTW, https://bugzilla.redhat.com/show_bug.cgi?id=603781
Yes,, this looks like a GTK bug. Anyone here have comment rights on that bugzilla already and could post this info their? Otherwise, I have to go set up yet another bugzilla. :)
This bug (that isn't fedora-specific) happens sometimes when the GTK+ file chooser gets updated. Since Geany never destroys its filechooser, it makes it more vulnerable to this bug than some other software.
Regards, Colomban
Thanks, Colomban, yes that looks like it.
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Yes,, this looks like a GTK bug. Anyone here have comment rights on that bugzilla already and could post this info their? Otherwise, I have to go set up yet another bugzilla. :)
Sorry, but you've got all the info. There are lots of filechooser crash critical bugs in the list, several look much the same as yours. But many are pretty old. New info may galvanise the maintainers (then again it might not :-)
It looks to me like a race between the change in the underlying directory and the chooser updates and user actions which cause an something to use the outdated information. Probably missing gdk_threads_enter/leave pair. For instance the function where your assert failed is comparing a local variable to one which could be updated by a different thread but isn't protected by threads_enter/leave, but it depends where its called from it might be protected there.
Cheers Lex
This bug (that isn't fedora-specific) happens sometimes when the GTK+ file chooser gets updated. Since Geany never destroys its filechooser, it makes it more vulnerable to this bug than some other software.
Regards, Colomban
Thanks, Colomban, yes that looks like it.
Cheers Lex
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sat, 13 Nov 2010 14:02:53 +1100, Lex wrote:
Yes,, this looks like a GTK bug. Anyone here have comment rights on that bugzilla already and could post this info their? Otherwise, I have to go set up yet another bugzilla. :)
Sorry, but you've got all the info. There are lots of filechooser crash critical bugs in the list, several look much the same as yours. But many are pretty old. New info may galvanise the maintainers (then again it might not :-)
Some time ago, I reported crashes with similar assertion messages like yours:
https://bugzilla.gnome.org/show_bug.cgi?id=615576
this seems to be fixed in GTK, at least it doesn't happen for me in 2.20.1 anymore. Not sure whether this had the cause as your crashes have, but as already said, it's most likely a GTK issue.
IIRC, there are also some more such crash reports in the Gnome bugzilla (as Lex said), so I'd suggest to search there and/or try to uprade the GTK version on your system.
Regards, Enrico
2010/11/14 Enrico Tröger enrico.troeger@uvena.de:
On Sat, 13 Nov 2010 14:02:53 +1100, Lex wrote:
Yes,, this looks like a GTK bug. Anyone here have comment rights on that bugzilla already and could post this info their? Otherwise, I have to go set up yet another bugzilla. :)
Sorry, but you've got all the info. There are lots of filechooser crash critical bugs in the list, several look much the same as yours. But many are pretty old. New info may galvanise the maintainers (then again it might not :-)
Some time ago, I reported crashes with similar assertion messages like yours:
https://bugzilla.gnome.org/show_bug.cgi?id=615576
this seems to be fixed in GTK, at least it doesn't happen for me in 2.20.1 anymore.
Ahh, I wasn't able to reproduce it either and I'm on 2.20.1
Cheers Lex
Not sure whether this had the cause as your crashes have, but as already said, it's most likely a GTK issue.
IIRC, there are also some more such crash reports in the Gnome bugzilla (as Lex said), so I'd suggest to search there and/or try to uprade the GTK version on your system.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Wed, 10 Nov 2010 13:56:10 +0100 Milan Babuskov milan.babuskov@gmail.com wrote:
I just ran into a rather serious Geany bug that can cause file loss.
Incidentally I had the hard disk partition full (on Linux) and Geany was happily reporting that file saving is successful. I had about 20 open files, worth about 2 hours of work. When I was done I saved all the files and closed Geany. Seconds later, I realized that all my files have size of zero bytes. Not only that I lost the recent changes, but complete files. This happen just prior to the commit to Git repository I planned. Obviously, I have nothing to commit. :(
Sorry this happened.
As of this morning Geany should at least now warn the user when files aren't saved. There was a bug that prevented this.
As Columban mentioned, the issue of not overwriting the existing file if saving fails is difficult to fix whilst still maintaining correct file metadata e.g. permissions.
Nick
On Wed, Nov 10, 2010 at 6:22 PM, Nick Treleaven nick.treleaven@btinternet.com wrote:
As of this morning Geany should at least now warn the user when files aren't saved. There was a bug that prevented this.
That's great. Thanks,