SUMMARY As mentioned in https://github.com/xournalpp/xournalpp/issues/5198 When launching xournal++ (xournalpp) no window appears, but also no error log gets created in ~/.config/xournalpp. The app is running in the background but no window appears. In X11 mode it runs just fine. This has been an issue for almost a year, it has been confirmed by the app developer that it is a plasma bug and that they don't see what they could fix on their side. When launching through terminal I get the following: ``` xopp-Message: 10:13:58.352: TEXTDOMAINDIR = (null), Platform-specific locale dir = /usr/share/xournalpp/../locale, chosen directory = /usr/share/xournalpp/../locale ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map Cannot connect to server socket err = Nie ma takiego pliku ani katalogu 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 = Nie ma takiego pliku ani katalogu 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:999:(snd_pcm_dmix_open) unable to open slave xopp-Message: 10:13:58.433: Plugin "MigrateFontSizes" UI initialized ``` And the process keeps running after that, but with no window. If I do `xournalpp --disable-audio` the output is much shorter: ``` xopp-Message: 10:14:19.553: TEXTDOMAINDIR = (null), Platform-specific locale dir = /usr/share/xournalpp/../locale, chosen directory = /usr/share/xournalpp/../locale xopp-Message: 10:14:19.561: Plugin "MigrateFontSizes" UI initialized ``` The process again keeps running, but with no window STEPS TO REPRODUCE 1. Install xournal++ on any distribution running Plasma in Wayland mode 2. Run xournal++ from the shortcut or terminal, no window will appear 3. Run `xournalpp --disable-audio` - same result 4. Run the app in X11 mode `GDK_BACKEND=x11 xournalpp` - the app launches just fine OBSERVED RESULT On plasma the app only runs in X11 mode SOFTWARE/OS VERSIONS Linux: Solus 4.5 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Could it be related to this? https://bugs.chromium.org/p/chromium/issues/detail?id=1268758
fwiw cannot reproduce with xournal++ 1.2.3, plasma git build, wayland, arch linux. xournal++ launches fine on my end, both through the desktop file, and through invoking xournalpp in konsole. I don't have the environment variable `GDK_BACKEND` set.
Did you have problems like that before? Either this bug has just been fixed in git of Plasma, or there is something in how Solus is building Plasma or Xournal++ itself
(In reply to JacekJagosz from comment #2) > Did you have problems like that before? > Either this bug has just been fixed in git of Plasma, or there is something > in how Solus is building Plasma or Xournal++ itself I have been using xournal++ without issues on wayland since last year before the plasma 6.0 release. I also just verified through kwin debug console that it is a native wayland window.
This is also working fine for me, with version 1.2.3. What version are you using?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.