New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
caught signal: 6 (geany crash on vnc over ssh) #1668
Comments
Geany itself does not call abort() but any of the libraries it uses might if something goes very wrong, to find out run geany under gdb and after the crash get a backtrace to see where it happened and post the backtrace here (if its a long backtrace don't forget to press return to continue it before pasting). |
Correction, Geany doesn't call abort() directly, but it does use assert() which calls abort(). But still same thing is needed, the backtrace. |
Hi elextr - how do I run geany under gdb? I've done a little gdb but only with code I've written and can compile. I don't know how to do what your asking. Also, note that I wasn't compiling, building, or executing any code in geany when it crashed. I was just using the editor. - thank you |
at the gdb prompt
when the crash occurs and you are back at gdb prompt
and return as many times as it asks to continue. |
Could also be a crash in |
Ok, I don't get a backtrace on geany because it doesn't crash. The crash is happening in x11vnc. I can make it happen frequently when typing "if (syst" in geany. That is when I get the popup suggesting I'm going to type "system". All I get from gdb on geany is this: |
I did a gdb backtrace on x11vnc and I got the attached. I don't know what is special about geany but nothing else leads to this x11vnc crash. |
It may be that Geany/Scintilla just calls things in a different order to others (but still legal for a real GTK/X11). You mentioned the problem seems to be the autocomplete suggestions popup, thats a custom popup generated by Scintilla and it might do the calls to create it in a slightly different order to another GUI. And its also resized, which may confuse things. |
Ok, I've gone into geany preferences under "Editor" and tab "Completions" and disabled Snippet completion and Autocomplete symbols. This stopped the issue of x11vnc dying while I'm editing code in geany. So, naturally, I tried clicking around further to make it crash and I can - by clicking on the geany File menu item. It doesn't happen every time but frequently. When I restart x11vnc and reconnect my vnc session I see the opened up File menu and can access it fine. This is weird. |
The If you can build Geany from source you can configure it with |
Help-Debug shows: "GTK 2.24.31, GLib 2.50.3" I'm assuming I can compile with gcc. Can you recommend a complete command I should run to recompile? I did a "dpkg --get-selections | grep gtk3" and got the following: libavahi-ui-gtk3-0:amd64 install |
Yeah GTK2 Your package list shows that there is not a GTK3 package for Debian, thats why I said you need to compile to test it. You will need the debian Download the Geany source tarball and extract it to a new empty directory, lets say
(well you said you wanted one command :) That gives a completely isolated Geany in |
This fixed the problem. I did have to "apt-get install intltool" before I could successfully build geany but that was simple. No more crashing when going to the File menu and I've also re-enabled "Snippet completion" and "Autocomplete symbols" without any problems. Here is a snip from my new geany's "Help-> Debug Messages": After I quit geany I see some Gtk-WARNING messages in the shell window from where I started geany. I've attached them to this post. They seem benign. Much obliged to you elextr. relayman357 |
Neat :)
Sorry, I can never remember which tools you need for git but don't need for the tarball.
The markup one I know is fixed in git, not sure about the first two. |
Hi,
I'm running geany 1.29 "jowar" on a fresh Linux install. It is running Debian 4.9.511 (2017-09-28) x86_64 GNU/Linux on an AMD Athlon II X2 250 Processor. This is a headless system so I initiate an SSH connection to it and then start x11vnc with this command: "x11vnc -shared -display :0 -geometry 1920x1080". Next I remote in with RealVNC over localhost so it uses the SSH tunnel (I'm on a Windows 7 box).
This has worked fine for everything I've done so far except geany. In the middle of editing a code file the VNC window just goes away. The SSH terminal window gives me a "caught signal: 6" and puts me back at the bash prompt.
A "kill -l" shows that this is an abort signal coming from geany itself (I think). Since it only occurs with geany I think that may be a good assumption.
thanks,
relayman357
The text was updated successfully, but these errors were encountered: