Xournall++ does not run in Wayland

Jtr1212 commented 7 months ago

Summary

I have encountered a problem: not starting xournall++ in a Wayland session, Solus 4.5 KDE. A similar problem is described here: https://github.com/xournalpp/xournalpp/issues/5198 I also tried running xournal++ from appimage, but also to no avail. I checked in live iso of Kubuntu, Fedora KDE. There is no such problem in these distributions. So it's specific to Solus. Is there any solution besides running with GDK_BACKEND=x11 xournalpp? I would be grateful for any advice.

Steps to reproduce

Launch xournal++

Expected result

Window pops up when I launch the app

Actual result

No window pops up when I launch the app

Environment

[X] Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Plasma

System details

Solus 4.5 KDE

Other comments

No response

joebonrichie commented 7 months ago

Interesting it runs fine on GNOME Wayland but I can replicate the issue on KDE Plasma.

sheepman4267 commented 7 months ago

My initial reaction was "What? I'm on Plasma Wayland and I use Xournal++", but then I realized that I'm apparently running the flatpak. However, I also have the eopkg version installed, and that package doesn't appear to be providing a .desktop file. It's not appearing in my applications menu, and I don't see it in /usr/share/applications. Can anyone else confirm that?

NVM, I can't read

Jtr1212 commented 7 months ago

Can anyone else confirm that?

I don't see it in /usr/share/applications as well. But I see it in application menu. Thank's for your attention.

sheepman4267 commented 7 months ago

It is there in /usr/share/applications. The file on my system is com.github.xournalpp.xournalpp.desktop. That exists, but it doesn't show up in the application menu.

sheepman4267 commented 7 months ago

I just built a test package from xournalpp's latest git commit. That seems to work. Maybe we can convince them to make a new release so we can package it properly?

Jtr1212 commented 7 months ago

The file on my system is com.github.xournalpp.xournalpp.desktop

Really, you are right. Sorry, I was not attentive. Searched at the end with "x"

sheepman4267 commented 7 months ago

The file on my system is com.github.xournalpp.xournalpp.desktop

Really, you are right. Sorry, I was not attentive. Searched at the end with "x"

Same here! And I wrote a whole paragraph about it before I realized my mistake!

More embarrassing, I've just realized that it wasn't in my menu because the flatpak version's .desktop has the same name and was overriding it. Oops. So we don't have a problem with .desktop files...

Justinzobel commented 7 months ago

This is the output from running from a terminal:

xournalpp
xopp-Message: 11:23:36.521: TEXTDOMAINDIR = (null), Platform-specific locale dir = /usr/share/xournalpp/../locale, chosen directory = /usr/share/xournalpp/../locale
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2721:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2721:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2721:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
xopp-Message: 11:23:36.879: Plugin "MigrateFontSizes" UI initialized

(com.github.xournalpp.xournalpp:53125): xopp-WARNING **: 11:23:36.967: No device found. Is Xournal++ running in debugger / Eclipse...?
Probably this is the reason for not finding devices!

(com.github.xournalpp.xournalpp:53125): xopp-WARNING **: 11:23:36.981: No device found. Is Xournal++ running in debugger / Eclipse...?
Probably this is the reason for not finding devices!

fish: Job 1, 'xournalpp' terminated by signal SIGSEGV (Address boundary error)

It leaves a coredump in coredumpclt list. So if someone wants to install the debugsymbols and report it upstream the developer might be able to diagnose what's happening.

getsolus / packages