| Summary: | hp-systray does not restart on logging back in | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Andrew Udvare <audvare> |
| Component: | Session Management | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Since writing this bug I installed Plasma on another machine from scratch and hp-systray restarts properly on that machine. Still does not restart on the machine I originally reported this bug on. I do not want to migrate to a new profile. Thanks. If it works on the other machine, then the code is doing the right thing, and the issue could be caused by: - a different, older, or broken version of hp-systray on the failing machine - a different, older, or broken version of ksmserver on the failing machine - some local override or configuration that breaks it on the failing machine (In reply to Nate Graham from comment #2) > Thanks. If it works on the other machine, then the code is doing the right > thing, and the issue could be caused by: > - a different, older, or broken version of hp-systray on the failing machine > - a different, older, or broken version of ksmserver on the failing machine > - some local override or configuration that breaks it on the failing machine How can I fully reset the relevant settings for the KDE part of this without making a new profile? It's impossible to know without details regarding the specific differences between the two systems, sorry. JFYI this isn't a place to get user support, it's a bug tracker. There is no indication that there's a bug in KDE software currently causing this issue. If you need help beyond that, I'd recommend asking in https://discuss.kde.org. |
SUMMARY STEPS TO REPRODUCE 1. Run hp-systray from HPLIP 2. Log out allowing session to save 3. Log back in OBSERVED RESULT Upon logging back in, hp-systray does not start. The following message is logged: hp-systray[9295]: hp-systray[9295]: error: option -s not recognized EXPECTED RESULT hp-systray should start and should not log any errors. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.16.5/5.23.5 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.23.5 Qt Version: 5.15.2 ADDITIONAL INFORMATION $ fgrep hp-systray ~/.config/ksmserverrc program1=/usr/bin/hp-systray restartCommand1=/usr/bin/hp-systray,-session,1014cd2d4cd000164398932500000094520009_1643989599_866247,-name,hp-systray I am not sure on the format of this file but it appears -session is being passed to hp-systray and does not get ignored. It results in hp-systray failing to start. $ hp-systray -session 101 HP Linux Imaging and Printing System (ver. 3.21.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. System Tray monitors the HP device status and Displays Usage: hp-systray [MODE] [OPTIONS] [MODE] Run in graphical UI mode: -u or --gui (Default) [OPTIONS] Use Qt5: --qt5 (Default) Set the logging level: -l<level> or --logging=<level> <level>: none, info*, error, warn, debug (*default) Run in debug mode: -g (same as option: -ldebug) This help information: -h or --help Startup even if no hplip -x or --force-startup CUPS queues are present: error: option -s not recognized I have tried editing the file to remove all mentions of hp-systray and this did not help.