Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issues with initially launched window on kde plasma 6 wayland (joplin flatpak) #217

Open
TheLizLee opened this issue Aug 30, 2024 · 1 comment

Comments

@TheLizLee
Copy link

TheLizLee commented Aug 30, 2024

hello,

in the "tools -> otions -> general -> application"-settings i have set joplin to
[v] show tray icon
[v] start application minimized in the tray icon

when i launch the app from the application launcher, the app does not open but gets "stuffed" into the system tray. this is of course the intended behavior. so far everything works as expected.

the issues arise when i initially open joplin from the tray after it has been launched by the application launcher to the tray. (note that subsequent opening of the app is not affected and works as it should.).

these issues are:

either:

  • the joplin window is not drawn at all. in this case the task-manager of the kde plasma panel shows it as opened, with the default wayland-icon ("stylized white W on orange background") in the according task-manager entry. the preview when hovering over the tsak manager entry is also not shown in this case. i have attached a screenshot:
    joplin initial window issue - not drawn at all

or:

  • the window is drawn but faces the following problems: it has a "normal" size (i.e. neither maximized nor minimized or even fullscreen) but is treated by the kwin window manager as maximizied. this means it can't be dragged along the screen, it cannot be resized and its shadows are not drawn. i have attached a screenshot:
    joplin initial window issues

after i close (!= quit the app) the initially opened window (either by clicking the cross in the title bar or by right clicking the task manager entry) and subsequently open the app again from the tray the issues are gone and the app behaves like normally.

on my journey solving this problem i have learned the following things:

  • setting up kwin window manager rules in the kde system settings menu does affect IF the window is initially drawn at all. it does not affect HOW it is drawn though. i.e. the values of rules like position or size are ignored anyways. it is unfortunately not reproducible what rules are leading to what effect.

here i have attached a detailed journalctl -f log with an exact description what actions do trigger what journalctl entries:

joplin timeline journalctl -f.txt

(jfyi: the vivaldi browser app shows very similar issues sometimes it is opened. i thought to mention this because both apps are built with the ozone-toolkit. maybe it helps to narrow the issue down.)

the problems do exist also on a fresh installation of fedora 40 kde spin in a vm that is fully updated but otherwise "virgin".

system info:

Operating System: Fedora Linux 40 (KDE Spin)
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon R9 380 Series
OpenGL renderer string: AMD Radeon R9 380 Series (radeonsi, tonga, LLVM 18.1.6, DRM 3.57, 6.10.6-200.fc40.x86_64)
OpenGL version string: 4.6 (Core Profile) Mesa 24.1.6
OpenGL platform interface: EGL
OpenGL shading language version string: 4.60

Flatpak Version: 1.15.8

kwin support information
kwin support information.txt

kwin wayland info:
kwin wayland info.txt

kwin xserver info:
kwin xserver info.txt

joplin app info

Joplin - open source note taking and to-do application
ID: net.cozic.joplin_desktop
Ref: app/net.cozic.joplin_desktop/x86_64/stable
Arch: x86_64
Branch: stable
Version: 3.0.15
License: MIT
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 760,5 MB
Runtime: org.freedesktop.Platform/x86_64/23.08
Sdk: org.freedesktop.Sdk/x86_64/23.08

joplin flatpak permissions

flatpak info --show-permissions net.cozic.joplin_desktop
[Context]
shared=network;ipc;
sockets=wayland;pulseaudio;pcsc;cups;
devices=all;
features=bluetooth;
filesystems=home;

[Session Bus Policy]
org.kde.StatusNotifierWatcher=talk
org.freedesktop.Notifications=talk
com.canonical.AppMenu.Registrar=talk

[System Bus Policy]
org.freedesktop.Avahi=talk

[Environment]
GTK_PATH=/app/lib/gtkmodules

flatpak runtime info

flatpak info org.freedesktop.Platform/x86_64/23.08
Freedesktop Platform - Runtime platform for applications
ID: org.freedesktop.Platform
Ref: runtime/org.freedesktop.Platform/x86_64/23.08
Arch: x86_64
Branch: 23.08
Version: freedesktop-sdk-23.08.21
License: MIT
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 598,3 MB

unsuccessful mitigation attempts:

  • reinstalling joplin with the "--delete-data"-flag and manually purging all joplin related folders (no wonder this didn't help, as the issues also exist on a freshly installed system)
  • experimenting with flatpak permissions: i tried several combinations of granting "x11", "x11 fallback", "wayland", "direct rendering access"
  • i tried adding/removing the "--ozone-platform=wayland"-flag to the command

please let me know if you need any further logfiles or debug info from joplin. i looked at the log.txt in the profile folder but imho it was only related to synchronisation and encryption stuff.

a crash file in the ~home folder has not been created by joplin, so i cannot provide that one.

Thank You!

@TheLizLee
Copy link
Author

TheLizLee commented Aug 30, 2024

anyways i managed to create a debug-level logfile according to this tutorial:
https://joplinapp.org/help/apps/debugging/

it has been produced on the beforementioned "clean install" fedora 40 vm
i attached it here:
joplin profile debug log.txt

  • the logfile starts with me launching joplin into the tray.
  • then i tried to open it from the tray unsuccessfully a first time (window was not drawn).
  • then i "closed" the (not drawn) window by right clicking the task-manager-entry.
  • subsequently i opened it from the tray again (this second time sucessfully, as always).
  • then i closed the window and quit the app. this is where the logfile ends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant