https://bugs.kde.org/show_bug.cgi?id=487905
hiburin...@googlemail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hiburin...@googlemail.com
--- Comment #5 from hiburin...@googlemail.com ---
Hi there,
I have this exact problem, after upgrading 'elisa-24.02.2-1' to
'elisa-24.05.0-1'.
If I downgrade the package it works just fine.
Elisa does start from the task manager (pinned) for the first time, but not
thereafter. Running it from the terminal, or the
application-launcher works just fine.
I am not the best at this stuff, but journalctl gave me just this (after
pinning elisa to the task manager and launching):
>Jun 05 06:39:55 coffee-arch kded6[980]: Registering ":1.96/StatusNotifierItem"
>to system tray
>Jun 05 06:39:57 coffee-arch kded6[980]: Service ":1.96" unregistered
>Jun 05 06:39:57 coffee-arch systemd[804]: dbus-:1.2-org.kde.elisa@0.service:
>Consumed 2.183s CPU time.
>Jun 05 06:39:58 coffee-arch plasmashell[1014]: error creating screencast
>"Could not find window id 0"
>Jun 05 06:40:01 coffee-arch plasmashell[1014]: error creating screencast
>"Could not find window id 0"
>Jun 05 06:40:39 coffee-arch plasmashell[1014]: error creating screencast
>"Could not find window id 0"
This comes up, when successfully starting it from the application-launcher:
>Jun 05 06:40:44 coffee-arch systemd[804]: Started Elisa - Music Player.
>Jun 05 06:40:44 coffee-arch elisa[7494]: org.kde.elisa.indexers.manager: Local
>file system indexer is inactive
>Jun 05 06:40:44 coffee-arch elisa[7494]: Unsupported option 'foreign_keys = ON'
>Jun 05 06:40:44 coffee-arch elisa[7494]: Unsupported option 'locking_mode =
>EXCLUSIVE'
>Jun 05 06:40:44 coffee-arch elisa[7494]: org.kde.elisa.indexers.manager: Local
>file system indexer is active
>Jun 05 06:40:44 coffee-arch elisa[7494]: org.kde.elisa.indexers.manager:
>trigger init of local file indexer
>Jun 05 06:40:46 coffee-arch wireplumber[925]: wp-event-dispatcher:
><WpAsyncEventHook:0x5c6a425921b0> failed: failed to activate item: >Object
>activation aborted: proxy destroyed
>Jun 05 06:40:46 coffee-arch wireplumber[925]: wp-event-dispatcher:
><WpAsyncEventHook:0x5c6a42599690> failed: ><WpSiStandardLink:0x5c6a427e2b40>
>link failed: 1 of 1 PipeWire links failed to activate
I looked at dbus-monitor while opening elisa from task manager and from app
launcher, and I do not understand much of it, but the main difference was, that
almost all arrays/dict entries were empty, whereas the messages were way longer
when starting from app launcher. No obvious error messages that weren't also in
the app launcher log.
Maybe that could help someone.
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
Manufacturer: ASUS
--
You are receiving this mail because:
You are watching all bug changes.
