Created attachment 15036 [details] GDB trace in glib freeing Description of problem: gramps kept crashing in glib2.0 when editing notes See attached GDB trace Version-Release number of selected component (if applicable): lib64gtk+3_0-3.24.49-2.mga10 lib64glib2.0_0-2.84.2-1.mga10 How reproducible: always Steps to Reproduce: 1. starts gramps 2. edit an event note
URL: https://gramps-project.org/bugs/view.php?id=13795 => (none)Depends on: 34076 => (none)Source RPM: enchant2-2.8.7-1.mga10 => glib2.0-2.84.2-1.mga10.src.rpm
Trying to update glib to 2.84.3
Updating glib2.0 didn't fixes. It actually segfault in different places on different run. Prior to updating glib, I also had a crash in free().
Created attachment 15037 [details] GDB trace (seg in pyton GC)
Created attachment 15038 [details] GDB trace in glib in another place
Attachment 15036 description: GDB trace => GDB trace in glib freeing
Perhaps a link to bug 34437 ?
CC: (none) => yves.brungard
Why this comeback? Something in the build chain were updated & some other need rebuild against perhaps?
Assigning to basesystem for glibc - if that really is the culprit.
Assignee: bugsquad => basesystem
glibc hasn't been rebuild since end of May so I would suspect sg else. Interestingly, gramps was more stable if run on my Mageia box but with remote display on my FC box (aka : FC --> ssh --> mga) Though it would still crash sometimes.
Created attachment 15039 [details] crashes all over the place
I see mentions to libgtk-3.so.0.2417.32 libpython3.13.so.1.0 libglib-2.0.so.0.8400.3 It's possible that Mass rebuild ignore/build in wrong order affected packages?
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=34472
Interestingly, running in English makes it stable…
Summary: gramps kept crashing in glib2.0 when editing notes => gramps kept crashing in glib2.0 when editing notes (in French locale, stable in English)
To be honest, it's using waypipe instead of ssh, which makes it run in English
(In reply to Thierry Vignaud from comment #8) > Interestingly, gramps was more stable if run on my Mageia box but with > remote display on my FC box (aka : FC --> ssh --> mga) > Though it would still crash sometimes. Summary: running on X.org on Mga (FR) : keep crashing: running with ssh -X : gramps on Mga, xwayland on FC (FR) : a little bit more stable: running with waypipe : gramps on Mga, wayland on FC (EN) : looks solid
More stable but still some segfaults from times to times…
I've tried downgrading python3 from 3.13.5 3.13.4 to no avail.
Summary: gramps kept crashing in glib2.0 when editing notes (in French locale, stable in English) => gramps kept crashing in glib2.0 when editing notes (more stable under Wayland?)
I've pinpointed all the crashes to the GtkTreeView/GtkListView widgets. The crashes always happen when I'm browsing either a tree or a list: - list of persons : pressing the first letters of a name to pinpoint a person (eg: "Doe" for "Doe, John") - tree of places : pressing the first letters of a name to pinpoint a place - list of sources : pressing the first letters of a name to pinpoint a source (eg "Mariages Gourin" for being able to select with the mouse between "Mariages Gourin - 1899-1903", "Mariages Gourin - 1904-1911" …) NOT using the keyboard (aka selecting by pressing the first letters) seems to result in no crashes. For nearly a month, I used to segfault in a random part of the glib/gtk stack but it's always when trying to add a citation and source or trying to select a person. (or as today when selecting a place when I tried to confirm my theory about Gtk(List|Tree)View vs selecting by pressing the first letters of the item I want) The crash usually happens when selecting with the mouse the right item after having pressing a few characters to be in the right place in a long line. Often when confirming the choice by pressing OK with the mouse. If I don't press any keys, but only boringly browsing the list with the mouse wheel, then nothing happens.
Source RPM: glib2.0-2.84.2-1.mga10.src.rpm => gtk+3.0-3.24.49-2.mga10Summary: gramps kept crashing in glib2.0 when editing notes (more stable under Wayland?) => gramps kept crashing in either glib/gtk/libpython when browsing gtkTreeViewGtkListView using keyboard to select by pressing first letters (more stable under Wayland?)
I wonder if your discovery is related to all the crashes in draktools, by example in drakfirewall I can't add a custom port without get a crash
It certainly feels like "stable" gtk3 is rather unstable at the moment, which is very strange as gtk+3 last version was pushed in March. Though it has been rebuilt for mass rebuild on July 7th. Maybe a gcc miscompilation?
I've rebuild it locally with one patch. I've started doing again key selection in tree views. At first it looks like it worked, but on 2nd try it segfaulted again. So I'm back to not selecting by keyboard in gtk tree|List views :-(
(In reply to Thierry Vignaud from comment #19) > I've rebuild it locally with one patch. > I've started doing again key selection in tree views. At first it looks like > it worked, but on 2nd try it segfaulted again. > So I'm back to not selecting by keyboard in gtk tree|List views :-( That is interesting, drakfirewall crash when I try to type custom port
The bug was still an issue by mid August. It eventually disappeared early last week, sometimes between August 15th and 20th. I guess some package update in the gtk stack eventually fixed it. Too bad, GNOME got broken by the updates that I applied this morning :-)
Status: NEW => RESOLVEDResolution: (none) => FIXED