Bug#840478: ksmserver: autostart service "/usr/bin/conky" finished with exit code 0
¡hola, max! I think the busted .desktop file happened when I tried to attach the same file to reportbug twice; the .desktop file itself is fine. But - still no joy. Since you were able to get yours to autostart I'm going to assume that the issue is on my end and most likely in my conky config as it's a little complex; I've tried not daemonizing, starting conky in the background and starting it with no command line options - mine just refuses to start although krunner or a terminal session will start it just fine. Please feel free to close this bug - and many thanks. allan
Bug#840478: ksmserver: autostart service "/usr/bin/conky" finished with exit code 0
Control: reassign -1 plasma-workspace 4:5.8.0-1 Control: severity -1 minor Control: tag -1 + confirmed Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=370528 ¡Hola allan! El 2016-10-11 a las 17:55 -0400, allan grossman escribió: Package: kde-baseapps-bin Version: 4:16.08.0-1 Severity: important * What led up to the situation? Upgraded Debian Unstable today. * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted machine and started KDE as normal. conky refused to start and .xsession-errors gave the error above. Starting conky in a terminal window or with krunner works, it just won't autostart. ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 A similar report with some workarounds can be found in: https://bbs.archlinux.org/viewtopic.php?id=217920 The problem seems to be that conky's stderr is closed when started from the autostart in daemonize mode. Redirecting stderr or not daemonizing solves the problem. Please note that using stderr after daemonizing a process is usualy a bad practice, and conky should at least check for errors when writting to it before bailing out. (Consider a daemon started from a terminal, what happens when the user closes the terminal?) * What was the outcome of this action? As mentioned, conky exits. * What outcome did you expect instead? Expected conky to autostart. *** /home/wizard/.config/autostart/conky.desktop [Desktop Entry] Exec=/usr/bin/conky -d Icon=system-run Path= [Desktop Entry] Exec=/usr/bin/conky -d Icon=system-run Path= Terminal=false Type=Application Your desktop file seems to list two desktop entries, this seems to be wrong. -- "When explaining a command, or language feature, or hardware widget, first describe the problem it is designed to solve." -- David Martin Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Processed: Re: Bug#840478: ksmserver: autostart service "/usr/bin/conky" finished with exit code 0
Processing control commands: > reassign -1 plasma-workspace 4:5.8.0-1 Bug #840478 [kde-baseapps-bin] ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 Bug reassigned from package 'kde-baseapps-bin' to 'plasma-workspace'. No longer marked as found in versions kde-baseapps/4:16.08.0-1. Ignoring request to alter fixed versions of bug #840478 to the same values previously set Bug #840478 [plasma-workspace] ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 Marked as found in versions plasma-workspace/4:5.8.0-1. > severity -1 minor Bug #840478 [plasma-workspace] ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 Severity set to 'minor' from 'important' > tag -1 + confirmed Bug #840478 [plasma-workspace] ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 Added tag(s) confirmed. > forwarded -1 https://bugs.kde.org/show_bug.cgi?id=370528 Bug #840478 [plasma-workspace] ksmserver: autostart service "/usr/bin/conky" finished with exit code 0 Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=370528'. -- 840478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840478 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#840478: ksmserver: autostart service "/usr/bin/conky" finished with exit code 0
Package: kde-baseapps-bin Version: 4:16.08.0-1 Severity: important * What led up to the situation? Upgraded Debian Unstable today. * What exactly did you do (or not do) that was effective (or ineffective)? Rebooted machine and started KDE as normal. conky refused to start and .xsession-errors gave the error above. Starting conky in a terminal window or with krunner works, it just won't autostart. * What was the outcome of this action? As mentioned, conky exits. * What outcome did you expect instead? Expected conky to autostart. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kde-baseapps-bin depends on: ii kde-baseapps-data 4:16.08.0-1 ii kde-runtime4:16.08.0-1 ii libc6 2.24-3 ii libkdecore54:4.14.23-1 ii libkdeui5 4:4.14.23-1 ii libkfile4 4:4.14.23-1 ii libkio54:4.14.23-1 ii libkparts4 4:4.14.23-1 ii libqt4-dbus4:4.8.7+dfsg-9 ii libqt4-xml 4:4.8.7+dfsg-9 ii libqtcore4 4:4.8.7+dfsg-9 ii libqtgui4 4:4.8.7+dfsg-9 ii libstdc++6 6.2.0-6 ii libx11-6 2:1.6.3-1 kde-baseapps-bin recommends no packages. kde-baseapps-bin suggests no packages. -- no debconf information *** /home/wizard/.config/autostart/conky.desktop [Desktop Entry] Exec=/usr/bin/conky -d Icon=system-run Path= [Desktop Entry] Exec=/usr/bin/conky -d Icon=system-run Path= Terminal=false Type=Application
