Segmentation fault, when start.

[TerminalHash]

Starting program: /usr/bin/mlvwm -debug
Welcome to MLVWM World !
Display Startup Screen !
Pixmap Create !

Program received signal SIGSEGV, Segmentation fault.
#0  0x00007ffff7e82714 in XmbTextExtents () from /usr/lib/libX11.so.6
#1  0x00005555555776e7 in ?? ()
#2  0x000055555557111c in ?? ()
#3  0x0000555555576bce in ?? ()
#4  0x000055555557793e in ?? ()
#5  0x0000555555579b55 in ?? ()
#6  0x00007ffff7c5f290 in ?? () from /usr/lib/libc.so.6
#7  0x00007ffff7c5f34a in __libc_start_main () from /usr/lib/libc.so.6
#8  0x0000555555559a75 in ?? ()

[morgant]

Thanks for reporting this, @TerminalHash. I'll need a little more information to try to triage this segfault, can you tell me what OS you're running mlvwm under, whether you installed it via a package manager or built it from source, and whether you're using the default configuration files or those from the mlvwmrc project?

I hope I can help figure this out for you.

[TerminalHash]

I'll need a little more information to try to triage this segfault, can you tell me what OS you're running mlvwm under, whether you installed it via a package manager or built it from source, and whether you're using the default configuration files or those from the mlvwmrc project?

I'm using Arch Linux, built from PKGBUILD on AUR, configuration for WM picked from this repo

[cowtoolz]

Getting the same with the AUR package. Going to attempt to build from source.

[zulc22]

this segfault happens if XCreateFontSet returns NULL here.

[zulc22]

i have confirmed this to happen on mainline Arch and Arch Linux 32.

[zulc22]

it does NOT happen on Debian 12, though.

[morgant]

this segfault happens if XCreateFontSet returns NULL here.

Many thanks for your further investigation of this issue, @zulc22!

Sometime around OpenBSD 7.2 or so, through 7.3, I noticed that the default font was not found, causing significant delays (see Issue #30). PR #31 addresses this issue, though I haven't tested it yet, so I'm wondering if you're able to manually build under Arch with that patch applied and if it resolves the issue.

The issue resolved itself with OpenBSD 7.4 and I haven't investigated further, so I'm not sure if I installed a font or whether it's something that was resolved in X11 or OpenBSD's xenocara.

[dchmelik]

Zulc22 said I reported this last year in #37, which was on Slackware GNU/Linux 15+current (64-bit).

[zulc22]

Sometime around OpenBSD 7.2 or so, through 7.3, I noticed that the default font was not found, causing significant delays (see Issue #30). PR #31 addresses this issue, though I haven't tested it yet, so I'm wondering if you're able to manually build under Arch with that patch applied and if it resolves the issue.

I tried it and it did not. I forgot to reply after trying it.

I can also say that in my experience in the past, the significant delay from being unable to find fonts was never resolved with Xorg. I believe the issue somehow lies in the way Xorg expects you to treat XCreateFontSet, but given all the docs I mulled over back when I debugged it, I couldn't really see what could've been done differently. It all seemed right to me.

EDIT - Maybe it's a locale issue, like seen on this mailing list? I can investigate more sometime, I'm sure.

I think I have tracked the failure down to the /usr/share/X11/locale/*/XLC_LOCALE file that gets chosen,
but I don't know what the problem with it is yet.
This highly cryptic file controls how XCreateFontSet chooses fonts for a locale.