Jack posted on Tue, 23 Sep 2025 19:23:26 -0400 as excerpted: > I've been getting more frequent, but not reproducible crashes in 0.164, > configured with meson and compiled with ninja. This is on Gentoo Linux, > running Wayland. > > Running in gdb, I see several New Thread messages, then > > Gdk-Message: 18:49:26.295: Error 22 (Invalid argument) dispatching to > Wayland display. > > followed by several tread exited messages, and > > [New process 11198] > [Inferior 1 (process 11198) exited with code 01] > (gdb) bt No stack. > > Any suggestions on where I might put a breakpoint to catch it before it > just kills itself or anything else to troubleshoot?
Fellow gentooer /and/ fellow pan user! =:^) Not sure it'll help but version comparisons would be near the top of my troubleshooting list, and given we're both gentoo that's easier than cross-distro. If you're ~amd64 you'll likely have many of the same versions I do (but where I'm running live-git-9999), but will be a bit behind on some if you're stable amd64. Here I'm running live-git pan (a pan-9999 ebuild based on the cmake-based version in the guru overlay... well, and the old live-git pan-9999 autotools build that I IIRC we were sharing back when gentoo dropped pan from the main gentoo repo while upstream was maintainerless before DD took over). I've not seen such problems here... I'm on wayland too, and pan releases are frequent enough that live-git isn't far ahead of the current 0.164 release, so that's unlikely to be a problem. But... unlike X where xorg was the simply assumed X, wayland's just a protocol, implemented by many different compositors. So just saying wayland isn't enough unless you're in a context where the wayland compositor can be assumed (like the kwin_wayland I run can be assumed for wayland when I'm on kde lists). So I'm on kde/plasma/kwin_wayland (also live-git -9999 packages, FWIW, via the gentoo/kde project overlay), while I'd /guess/ you're on some gtk- based (mutter-based?) wayland. But for all I know it's sway or wayfire or... maybe even the reference weston (which I have installed as a minimal-deps backup compositor in case my after all live-git kwin breaks, tho I've not had to actually resort to it in some years now) for that matter. And the maturity of that compositor and the degree to which it is keeping up with current wayland protocol extensions can matter. Then there's also the client-side wayland toolkit implementation. Pan is of course gtk, so it's the gtk wayland client implementation, for both you and I. What could matter there would be the gtk version, and pango and cairo and gdk-pixbuf and mesa and... BTW wayland (where I'm also live-9999 as live- kde was requiring not-yet-released wayland for support of a brand new protocol extension not long ago) includes some client libs too. I'm ~amd64 so should be pretty current -- if you're stable amd64 (or other arch) you'll be back a bit on some of those. FWIW, here's my versions (with a fresh --update --deep about a day ago, tho I'd been busy and had let it go a month before that) for you to compare against and see if anything looks like you might want to upgrade it. $$ equery l gtk+ pango cairo mesa wayland gdk-pixbuf * Searching for gtk+ ... [IP-] [ ] x11-libs/gtk+-3.24.50:3 * Searching for pango ... [IP-] [ ] x11-libs/pango-1.57.0:0 * Searching for cairo ... [IP-] [ ] x11-libs/cairo-1.18.4-r1:0 * Searching for mesa ... [IP-] [ ] media-libs/mesa-25.2.3:0 * Searching for wayland ... [IP-] [ ] dev-libs/wayland-9999:0 * Searching for gdk-pixbuf ... [IP-] [ ] x11-libs/gdk-pixbuf-2.42.12:2 -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman _______________________________________________ Pan-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/pan-users
