FS#65751 - [guake][vte3] Version 3.7.0 crashes at startup

Attached to Project: Community Packages
Opened by Trit' (trit) - Monday, 09 March 2020, 11:48 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 12 October 2020, 00:45 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Balló György (City-busz)
Eli Schwartz (eschwartz)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: after updating to version 3.7.0, Guake crashes at startup. Downgrading to 3.6.3 makes it works again.

Additional info:
Log message below, when I run it from a terminal:

$ guake
Guake not running, starting it
Loading Gnome schema from: /usr/share/glib-2.0/schemas
Language previously loaded from: /usr/share/locale
Guake Terminal 3.7.0
VTE 0.60.0
Gtk 3.24.14
created fresh notebook for workspace 0
Spawning new terminal at /home/×××××
current workspace is 0
can't bind show-focus key
Spawning new terminal at /home/×××××
Spawning new terminal at /home/×××××
Guake tabs restored from /home/×××××/.config/guake/session.json
Guake initialized
Guake tabs saved to /home/×××××/.config/guake/session.json
Segmentation fault (core dumped)

Steps to reproduce: update Guake to version 3.7.0 and try to start it up.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Monday, 12 October 2020, 00:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  vte3 0.62.1
Comment by Eli Schwartz (eschwartz) - Monday, 09 March 2020, 14:10 GMT
  • Field changed: Severity (Critical → High)
The OS doesn't crash on program startup, just the program itself, so this is severity "high" as opposed to "critical". See https://wiki.archlinux.org/index.php/Bug_reporting_guidelines#Severity
Comment by Eli Schwartz (eschwartz) - Monday, 09 March 2020, 14:14 GMT
I can successfully start guake after the upgrade.

Does it work if you login to a clean user account and try to start guake from there?
Comment by Trit' (trit) - Monday, 09 March 2020, 16:07 GMT
I tried to start it after having renamed its config folder (to start it from scratch), and it works. I guess the bug was just because of the JSON file. Thank you for your suggestion.

EDIT: or not. The bug occurs after I have closed Guake and restarted it with an existent ~/.config/guake folder. If the folder does not exist, Guake 3.7 works fine.
Comment by Eli Schwartz (eschwartz) - Monday, 09 March 2020, 16:09 GMT
If you can reproduce the problem with that json config file, you should consider submitting a bug to guake: https://github.com/Guake/guake/issues
Comment by Trit' (trit) - Monday, 09 March 2020, 18:46 GMT
Not just this JSON file. I want to say that as long as the ~/.config/guake folder exists (it is created when Guake is started for the first time, or when the folder is deleted), Guake 3.7 will segfault when started, even if it has created a new JSON config file.
Comment by Eli Schwartz (eschwartz) - Monday, 09 March 2020, 19:20 GMT
You can say it, but it isn't true, I've restarted guake, exited guake, restarted it again, exited it, rm -rf $HOME/.config/guake/ and restarted it again, and then exited and restarted it a few more times.

I CANNOT reproduce your crash.
Comment by Nicholas Wang (nicholascw) - Wednesday, 26 August 2020, 15:46 GMT
  • Field changed: Percent Complete (100% → 0%)
I have the same issue and the segfault happens randomly. Then I inspected my upgrade log, seems it's correlated with python-sphinx (3.2.0-1 -> 3.2.1-1). I then tried to downgrade it back to 3.2.0 and it works fine. I believe there may be a compatibility issue.
Comment by freswa (frederik) - Wednesday, 26 August 2020, 15:51 GMT Comment by Karthik (wpd) - Thursday, 27 August 2020, 14:25 GMT
Have you tried removing .config/guake/session.json and restarting guake? When guake segfaults, I remove my session.json file
Comment by Karthik (wpd) - Thursday, 27 August 2020, 14:28 GMT
Sorry, that's one of the solutions suggested in the same github issue
Comment by Eli Schwartz (eschwartz) - Thursday, 27 August 2020, 14:36 GMT
Thanks, freswa. The issue links to an upstream vte3 ticket: https://gitlab.gnome.org/GNOME/vte/-/issues/270

Seems like vte3 acknowledges and has isolated a re-entrancy bug calling a function with a null pointer. Hopefully they'll figure out a fix very soon.
Comment by Eli Schwartz (eschwartz) - Thursday, 27 August 2020, 14:38 GMT
Note that this is much more likely to happen if you have a high number of tabs being restored.
Comment by Eli Schwartz (eschwartz) - Monday, 05 October 2020, 00:42 GMT
Upstream vte added a workaround here: https://gitlab.gnome.org/GNOME/vte/-/issues/270#note_924869

The fix was released as vte3 0.62.1 and entered [extra] 31 hours ago. Can you verify the problem is solved?

Loading...