You are not logged in.
Hi, I think I found a bug in glycin 2.2.3, but I am not sure, so decided to write a forum post first.
After a recent full system upgrade Firefox started to crash by following these steps:
1. Find any image
2. Click RMB > Copy Image
3. Paste into anything (firefox itself or any other app)
It didn't report any errors, just crash dialog window + minidump. With an option to upload this dump to firefox. So that's what I did (link: https://crash-stats.mozilla.org/report/ … 2b0261018). I hope links are okay?
I'll be honest: I am not good at reading dump files, so I asked an LLM to check what was wrong. It pointed me to libglycin.so and advised to test previous version. I checked /var/cache/pacman/pkg, found glycin-2.2.2-1-x86_64.pkg.tar.zst, and downgraded it. It indeed did help!
So am I right to assume this is indeed a bug and not a user error of some kind? Meaning the right thing to do is to report this properly. Only question is where to report it? I assume it's not really an arch linux problem, but rather original author's (which seems to be GNOME team)
PS: I did some internet (and Arch Linux forum too!) search and found nothing on the topic. Which actually was surprising as this issue seems to me like it would be affecting a lot of people.
Last edited by ABrony (Today 14:37:32)
Offline
Possibly same as https://bbs.archlinux.org/viewtopic.php?id=315241 or https://gitlab.gnome.org/GNOME/glycin/-/work_items/342 but the minidump lackst the symbols from libglycin and it also doesn't look like anyone from https://bbs.archlinux.org/viewtopic.php?id=315241 has reported that upstream.
Offline
Unable to replicate with FF 158.0.1 pasting from web page to krita.
glycin 2.2.3-1 is installed.
Running on Hyprland with no display manager.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
The crash report link returns a "Page not found" error for me.
You might want to report this upstream at https://gitlab.gnome.org/GNOME/glycin if further investigation points to a glycin regression.
[shridhyan@archlinux ~]$ pacman -Q firefox glycin gdk-pixbuf2
firefox 158.0.1-1
glycin 2.2.3-1
gdk-pixbuf2 2.44.8-1I cannot reproduce the crash. Both libglycin-2.so.0 and libgdk_pixbuf-2.0.so.0 are mapped into my Firefox process, so at least both libraries are loaded in my setup.
Currently, I'm running XFCE with X11 and Compiz, using LY as my display manager.
Is anything special about your setup? Wayland/X11, compositor, sandbox configuration, etc.?
Edit:
Missed responses.
Last edited by 5hridhyan (Today 13:53:26)
Offline
The crash report link returns a "Page not found" error for me.
I'm sorry, it is because of closing parenthesis at the end of the link. I guess I had to add whitespace between link end and ")". Not really familiar with markup language used here.
Regarding setup: most notably hyprland and nothing special else really. Output of "pacman -Qqe" if you're interested - https://pastebin.com/Kg9VwWAH
Thinking of unusual bits of config: I only can imagine using VRR, but it's probably unrelated.
Offline
@5hridhyan, it's the closing brace
https://crash-stats.mozilla.org/report/ … nvironment logs HW and geo location but not the display server (I however doubt that's super-relevant here)
Since glycin is listed in https://debuginfod.archlinux.org/packages I'd first and foremost try to get a more complete backtrace that exposes where glycin is aborting.
Offline
I'll be super glad to gather as much info as possible but can't think of anything except attaching debugger to firefox. I've never done anything like that, but can try. What you can recommend?
Offline
Thanks for the correction. I probably need spectacles ATP
What can you recommend?
https://wiki.archlinux.org/title/Debugg … ing_traces would be a good start. Try to obtain a backtrace with Glycin debug symbols available, since the minidump doesn't expose enough information to identify where it's aborting...
Offline
Ok, that was super weird. Ran firefox through GDB with debuginfod enabled but couldn't trigger a crash. I did upgrade glycin back. What's the chance of libglycin.so just being corrupted from some system crash in the past? Anyway, probably should mark thread as solved, as an issue is no longer exist... What a weird thing this was...
Thanks everyone!
Offline