Bug 511755

Summary: Tray icon is unresponsive and shows "JavaEmbeddedFrame" - Cryptomator App
Product: [Plasma] plasmashell Reporter: Camis <bugs.kde>
Component: System Tray widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: materka
Priority: NOR    
Version First Reported In: 6.5.1   
Target Milestone: 1.0   
Platform: CachyOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshot

Description Camis 2025-11-07 08:47:32 UTC
Created attachment 186576 [details]
Screenshot

Hello,

I've encountered an issue with the system tray icon for Cryptomator on a fresh installation of KDE Plasma 6. The icon itself is displayed correctly, but it is completely unresponsive and shows a generic tooltip.


Environment Details:

Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.7-3-cachyos (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Vega 8 Graphics


Steps to Reproduce:

Start a KDE Plasma 6 session.
Launch the Cryptomator application.
Observe the icon in the system tray.

Actual Behavior:

The Cryptomator icon is visible in the system tray.
When hovering the mouse over the icon, the tooltip displays the text "JavaEmbeddedFrame".
Left-clicking and right-clicking on the icon has no effect. The context menu does not appear, and the main window cannot be shown via the icon.

Expected Behavior:

The tooltip should display relevant status information (e.g., "Cryptomator" or the status of the vaults).
Left-clicking should open the main application window.

Right-clicking should open a context menu with options like "Show Window", "Lock All Vaults", "Quit", etc.
This seems to be a compatibility issue with how Java AWT/Swing applications interact with the new system tray implementation in KDE Plasma 6. Let me know if you need any further logs or information.
Comment 1 Konrad Materka 2025-11-16 19:31:36 UTC
This is a duplicate of Bug 498824

*** This bug has been marked as a duplicate of bug 498824 ***