Geany segfaults after clicking new document 3 or 4 times #2736
Comments
|
More on that: If I open at least one document, "New document" works as expected. The issue appears only when I don't have any documents open and I click several times on "New document." So, to reproduce it, I just close all the documents, and hit "New document" several times: Segmentation Fault. |
|
Please verify that you have no plugins enabled. |
|
Note WFM on Linux Mint 20 which is derived from Ubuntu 20.04. |
|
I've disabled all plugins and the problem remains.
…On Tue, Jan 26, 2021 at 10:35 PM elextr ***@***.***> wrote:
Note WFM on Linux Mint 20 which is derived from Ubuntu 20.04.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2736 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/APXW3UGCPXCECMKTK7T3EP3S36CZZANCNFSM4WUQHIVQ>
.
--
*Nestor Alonso*
CTO
General Software Inc
(786) 230-8081 <+17862308081>
nestor@generalsoftwareinc.com | LinkedIn
<https://www.linkedin.com/in/nestor-alonso/>
<https://generalsoftwareinc.com>
|
|
try starting geany as |
|
The problem changes a little bit. Geany opens fine, and is not segfaulting,
but if I press "New document" nothing happens, but in the message console I
get:
08:50:51: This is Geany 1.37.1.
08:50:51: New file "untitled" opened.
08:50:54: File untitled closed.
08:50:54: New file "untitled" opened.
08:50:54: File untitled closed.
08:50:55: New file "untitled" opened.
08:50:55: File untitled closed.
08:50:55: New file "untitled" opened.
08:50:55: File untitled closed.
08:50:55: New file "untitled" opened.
Visually, there is only a new file tab in the editor area. Please see the
attached file.
…On Tue, Jan 26, 2021 at 11:57 PM elextr ***@***.***> wrote:
try starting geany as geany -c /tmp/something_that_does_not_exist and see
if the problem persists.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2736 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/APXW3UFUCHLADVMHQRVVA5DS36MJZANCNFSM4WUQHIVQ>
.
--
*Nestor Alonso*
CTO
General Software Inc
(786) 230-8081 <+17862308081>
nestor@generalsoftwareinc.com | LinkedIn
<https://www.linkedin.com/in/nestor-alonso/>
<https://generalsoftwareinc.com>
|
|
Now it is not segfaulting anymore even with the regular config. Maybe we should close this here and move forward with this last behavior. Thank you very much for your time |
Good, that means there is something in the setup or settings that is weird, but it nonetheless should not cause a segfault.
Thats weird, and bad because that means we can't track down what weirdness is causing the segfaulting and protect against it. If it happens again can you try running Geany under gdb and get a backtrace showing where it segfaults and re-open this and post here? The behaviour you describe with only one new document open is the intended behaviour. There is an option to always open a new document when the last is closed because someone didn't like having an empty space where the editor tabs go, but since it was just a space filler they deleted it when the user opened or created a document, but they did that always. So when you create a new document and there is only one existing document and it has no backing file and is unmodified it is deleted and you see that message in the status. A side effect of this is that unless you have more than one document open or one file backed or modified document open you can't open multiple empty documents. Although there have been various discussions about this over the years nobody has found the use-case of opening only multiple empty documents sufficiently important to make the code to change it. For example add a flag to the "fake" document and only delete the single document it if its flagged as well as being unmodified and not file backed, so not deleting user created empty documents. |
|
I too have this same issue... If I open Geany and press Ctrl+N start typing a file and save it then click in the text area of the file with my mouse it segfaults... I can confirm that spamming the mouse in the text area after pressing Ctrl+N also segfaults. I am running gentoo compiled from source... I'm about to get a gdb and will post the results as a follow up. |
|
gdb says... Edit: the other gdb log that I posted was erroneous. I consistently get the above error now. |
|
Need the whole backtrace, and watch it might print some and ask if you want to continue. |
|
|
I have figured out that the bug is only present in X11. When running Wayland the bug no longer happens. |
|
Without a backtrace have no idea whats wrong. |
Could you please tell me who to obtain a backtrace? |
|
When it stops at "(gdb)" type "backtrace" and return. |
Thanks... |
|
Not very helpful but it shows the problem is entirely within the GTK/GIO/GObject/Glib libraries, the only Geany code present is the initial call to GTK. So its something in the version of those libraries that doesn't like your X11. Is it actual Xorg X11 or XWayland? |
|
It is X11. I switched to Wayland and the issue went away. |
|
https://en.wikipedia.org/wiki/Intelligent_Input_Bus For a long time one of the reasons to avoid Wayland was to avoid IME problems. This issue may be a sign that the tide has turned in favour of Wayland. |
Hi, this is happening in Ubuntu 20.04, compiled version of geany 1.37.1. I'm a long time user of Geany, and I've always compiled from source. Compilation was fine, as usual.
╭─nalonso@satellite ~
╰─$ geany
[1] 1884036 segmentation fault (core dumped) geany
╭─nalonso@satellite ~
╰─$
If I open documents everything works fine.
[Edit: As you have discovered and cross posted, there is a separate issue about this]
Maybe unrelated, but Geany is taking a whole lot more time to load with a lot of documents. I use to have 30 or more files opened, mostly YAML and Dockerfiles, but up to 1.36 Geany was lightning fast even with all those documents open.The text was updated successfully, but these errors were encountered: