Summary: | lxde-base/lxappearance-0.6.3-r2: segfault with dev-libs/glib-2.68.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Artem Ilgamov <a.ilgamov> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | a.ilgamov, jstein |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
See Also: | https://gitlab.gnome.org/GNOME/glib/-/issues/2361 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Artem Ilgamov
2021-03-22 12:44:10 UTC
It looks like this might resolve the issue: https://github.com/lxde/lxappearance/pull/4 Works for me. You seem to have mixed stable and ~unstable system, and/or maybe your binpkgs are somewhat broken and mixed between glib-2.68/2.66 as well? I'd suggest you to fully update your system, and maybe even run emerge -eav lxde-base/lxappearance --usepkg=n (In reply to Joonas Niilola from comment #2) > Works for me. > > You seem to have mixed stable and ~unstable system, and/or maybe your > binpkgs are somewhat broken and mixed between glib-2.68/2.66 as well? > Well disregard that, missed the report date initially. Was looking at your toolchain, but GCC-11 came later than this was reported. Anyway, is this still a problem for you? If you re-emerge lxappearance and its glib parts. I have no binpkgs present in my system :) Since dev-libs/glib were updated to 2.68.1, issue not reproduce anymore. lxapperance still segfaults if you try to launch it with 2.68.0, I just rechecked it. It still works for me with that combination, I installed glib-2.68.0 and emerged lxappearance-0.6.3-r2 and it works just fine here :\ It'd be rather easy to block a certain version from being compatible, but also a bit messy and it might mess with stabilization later on. That's why I'd prefer not to do it especially since this is not reproducible here. Maybe stracing or a proper gdb backtrace would prove more worthy in debugging this? Still an issue? I'm cannot test it (don't have this system anymore), but according to https://gitlab.gnome.org/GNOME/glib/-/issues/2361 the issue was fixed in glib 2.68.1 So I think it is safe to close this bug. Thanks! |