hammerhead plasma mobile Segmentation fault (Xwayland segfaults on ARMv7)

You selected mainline kernel in pmbootstrap init, right? I also wouldn't be totally surprised to see Plasma Mobile being too intensive for this old device. I also haven't checked Plasma Mobile on other msm8974 devices recently.

added categorydevice device-lg-hammerhead labels

Yes 'edge' (other simply does not have hammerdead target)

Here nothing intensive in showing black screen. I love this device, I'm using for years. Best price for given features. This device can handle a lot of graphics as well.

Anyway it looks like plasma issue, not device.

Anyway it looks like plasma issue, not device.

I doubt it. People are using Plasma Mobile just fine on other devices.

(EE) Segmentation fault at address 0xb69ac004 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting

This looks like xwayland part of plasma-wayland session is crashing

I was having the same segmentation fault when tinkering with cage on edge yesterday, but thought it was my setup. The log seem to have a little more info on Xwayland. Pasting it here in case someone find it useful:

$ XDG_RUNTIME_DIR=/tmp/$USER-runtime-dir cage xeyes
(EE) Segmentation fault at address 0xb68df004
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
00:00:01.956 [xwayland/server.c:247] Xwayland startup failed, not setting up xwm
Error: Can't open display: :0

I'm having the same crash on Phosh. Except it showing top menu, instead of blackscreen.

(EE) Segmentation fault at address 0xb68d6004
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)

https://paste.debian.net/1249823/

I can reproduce the same issue on samsung-m0. Seems it might be a general ARMv7 issue.

mushroom:~$ XDG_RUNTIME_DIR=/run/user/10000/ Xwayland
(EE) Segmentation fault at address 0xb6968004
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
Aborted

I opened an issue in Alpine: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14140

mentioned in issue #1663 (closed)

removed device-lg-hammerhead label

removed categorydevice label

added ~19350359 typebug labels

changed title from hammerhead plasma mobile Segmentation fault to hammerhead plasma mobile Segmentation fault (Xwayland segfaults on ARMv7)

In the case of Phosh, you can work around this by editing /usr/share/gnome-session/sessions/phosh.session and removing org.gnome.SettingsDaemon.XSettings; from the RequiredComponents line. I'm not sure about Plasma Mobile. Note that X11 apps won't work if you use this workaround.

mentioned in issue #1671 (closed)

mentioned in issue #1658 (closed)

mentioned in merge request !3371 (merged)

so the same pattern as #1658 (closed) Xorg crashes whenever some too new mesa-dri-gallium is installed and no hw 3d driver is present, things are closed? So we need to do some bisecting in Mesa? Find the first bad version and report to Alpine?

This should've been fixed (or at least, worked around) in Alpine now, so feel free to upgrade the packages on your devices and see if it helps. Make sure you have Mesa 22.1.7-r2.

This should've been fixed by https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/38222 (which now is merged), but please test it. I've only tested my basic glGetString program.

Xwayland works for me again on the samsung galaxy SIII, the oh no! screen is gone when starting phosh.

closed

hammerhead plasma mobile Segmentation fault (Xwayland segfaults on ARMv7)

Describe your issue

On what postmarketOS version did you encounter the issue?

On what environment did you encounter the issue?

Phone environments

Other

How did you get postmarketOS image?

What's the build date of the image? (in yyyy-mm-dd format)

Additional information

Child items 0

Activity