Control: reassign -1 plasma-workspace 4:5.8.0-1
Control: severity -1 minor
Control: tag -1 + confirmed
Control: forwarded -1

¬°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:

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 /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature

Reply via email to