| Summary: | Something has broken tint2, probably recent glib2.0 update | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Stig-Ørjan Smelror <smelror> |
| Component: | RPM Packages | Assignee: | Stig-Ørjan Smelror <smelror> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, mageia, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | tint2-17.1.3-1.mga.src.rpm, glib2.0-2.76.2-2.mga9.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | tint2 gdb backtrace with debug packages installed | ||
|
Description
Stig-Ørjan Smelror
2023-05-05 13:21:41 CEST
Created attachment 13804 [details]
tint2 gdb backtrace with debug packages installed
Addition to the attachment.
(gdb) where
#0 handle_x_event (e=0x7fffffffd240) at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:539
#1 0x000000000041e5a7 in handle_x_event (e=0x7fffffffd240) at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:447
#2 handle_x_events () at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:603
#3 0x000000000041eefa in run_tint2_event_loop () at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:781
#4 0x000000000041ef75 in tint2 (argc=<optimized out>, restart=0x7fffffffdbfc, argv=0x7fffffffdd28)
at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:824
#5 tint2 (argc=<optimized out>, argv=0x7fffffffdd28, restart=0x7fffffffdbfc) at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/s
rc/main.c:812
#6 0x0000000000414957 in main (argc=1, argv=0x7fffffffdd28) at /usr/src/debug/tint2-17.1.3-1.mga9.x86_64/src/main.c:871
The crash may be related to an updated glib2. https://bbs.archlinux.org/viewtopic.php?id=284293 Well discovered. I think you are right. Glib2 was updated (with a lot of other stuff) on my system on 3 May. Tint2 is not the only application which may suffer. That Arch reference is lengthy (avoid patches mentioned), and the conclusion: "You need a patched version of tint2 to stop the tint2 from crashing" is preceded by: "glib2 won't fix, so unless they revert to the previous the g_slice behavior out of, i don't know, a minimal sense of responsibility to not go around and break stuff because tehy feel like and wrt" which derides glib2 for a change that is not likely to be undone; and "I don't want to keep ignoring glib2 or stand in the way of progress" which is a resignation to live with the consequences - even if that means abandoning Tint2 panel/taskbar. The solution of downgrading glib2 is short-term only. It seems you are the tint2 packager, so giving you this bug. I suspect you can do nothing unless & until tint2 is updated to cope with the changed glib2. You can close it 'wontfix'; earmarked for Errata9. CC'ing tmb & neoclust for info re glib2.0 Keywords:
(none) =>
FOR_ERRATA9 Reported it upstream. https://gitlab.com/nick87720z/tint2/-/issues/4 I note in the upstream bug "your patch is now applied to the Mageia package with a reference to your comment." So, issue solved? CC:
(none) =>
fri Yes, issue solved. Thanks for the reminder. Status:
NEW =>
RESOLVED
Stig-Ørjan Smelror
2023-07-07 16:33:04 CEST
Keywords:
FOR_ERRATA9 =>
(none) |