Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#80265 - [meld] segfaults on start
Attached to Project:
Arch Linux
Opened by mephinet (mephinet) - Wednesday, 15 November 2023, 15:23 GMT
Last edited by Toolybird (Toolybird) - Thursday, 16 November 2023, 22:09 GMT
Opened by mephinet (mephinet) - Wednesday, 15 November 2023, 15:23 GMT
Last edited by Toolybird (Toolybird) - Thursday, 16 November 2023, 22:09 GMT
|
DetailsDescription:
After running "pacman -Syu" a few days ago, meld dies instantly on start with a segfault: $ meld Segmentation fault (core dumped) Wenn running meld in the debugger: gdb -ex "set args $(which meld)" /usr/bin/python ... Starting program: /usr/bin/python /usr/bin/meld ... [Thread 0x7fffe3fff6c0 (LWP 26823) exited] Thread 1 "python" received signal SIGSEGV, Segmentation fault. 0x00007ffff6a0ac86 in cache_alias_lookup (alias=alias@entry=0x7fffe35ac8e8 "application/x-executable") at ../glib/gio/xdgmime/xdgmimecache.c:312 312 for (i = 0; _caches[i]; i++) Additional info: meld 3.22.0-2 python-gobject 3.46.0-1 |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 16 November 2023, 22:09 GMT
Reason for closing: Not a bug
Additional comments about closing: At least not a packaging issue. Refer comments.
Thursday, 16 November 2023, 22:09 GMT
Reason for closing: Not a bug
Additional comments about closing: At least not a packaging issue. Refer comments.
$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)
Then post gdb.txt
Please read the following links [1][2] for more details about creating good traces.
[1] https://blogs.gnome.org/mcatanzaro/2021/09/18/creating-quality-backtraces-for-crash-reports/
[2] https://wiki.archlinux.org/title/Debugging/Getting_traces
I just double-checked with my second notebook which I just updated, and you're right, meld is working fine on this machine, so it must be an issue local to the other device. If I find out anything of interest, I'll follow up here, but I think we're good closing this issue for now. Thanks for your quick response!
removing ~/.local/share/recently-used.xbel
I'll try to create a reproducer and report the issue upstream...
[1] https://bbs.archlinux.org/viewtopic.php?id=290292