https://bugs.kde.org/show_bug.cgi?id=433538
Rik Mills changed:
What|Removed |Added
CC||rikmi...@kde.org
--- Comment #14 from Rik Mills --
https://bugs.kde.org/show_bug.cgi?id=433538
Rik Mills changed:
What|Removed |Added
CC||c...@claydoh.com
--- Comment #13 from Rik Mills --
https://bugs.kde.org/show_bug.cgi?id=433538
Jonathan Riddell changed:
What|Removed |Added
CC||ws...@outlook.com
--- Comment #12 from Jonat
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #11 from Marco ---
Can anyone point me to the bug that has been fixed upstream? (the one related
to Dropbox and other apps forking in the background not working)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #10 from Marco ---
and, after running dropbox start -i, or insync start, I get back my console, so
they seem to fork in the background.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #9 from Marco ---
In my case, I do not even have the dropbox process running (neither for
insync).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #8 from Nate Graham ---
Actually that may be a dirty lie. It does not.
What I see is that the `dropbox` process is in fact autostarted and seems to be
working, but it has no item in the system tray when using systemd startup. If I
kill the
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #7 from Nate Graham ---
(In reply to David Edmundson from comment #6)
> Sounds like a different bug:
>
> Do you know if "dropbox start -i" forks into the background?
I can confirm that it does. What's the upstream bug?
https://github.com/
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #6 from David Edmundson ---
Sounds like a different bug:
Do you know if "dropbox start -i" forks into the background?
same for "insync start"
If so that's a known other bug. They do start, but then the main process quits
so we kill the wh
https://bugs.kde.org/show_bug.cgi?id=433538
Marco changed:
What|Removed |Added
CC||phoenix_8...@hotmail.com
--- Comment #5 from Marco ---
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #4 from Kevin Kofler ---
The weird thing is that systemd apparently has no problems silently ignoring
X-KDE-autostart-phase and just proceeding as if it were not there (at least, I
do not see it being processed anywhere in that source file),
https://bugs.kde.org/show_bug.cgi?id=433538
Nate Graham changed:
What|Removed |Added
URL||https://github.com/systemd/
|
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #3 from Rex Dieter ---
Filed this with systemd,
https://github.com/systemd/systemd/issues/18791
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433538
Alois Wohlschlager changed:
What|Removed |Added
CC||alo...@gmx-topmail.de
Resolution|-
https://bugs.kde.org/show_bug.cgi?id=433538
--- Comment #2 from Rex Dieter ---
So kde/plasma is just going to leave that broken?
Wasn't a problem when plasma implemented the xdg autostart internally (of
course), may have to leave at least part of that enabled for items like this?
--
You are re
https://bugs.kde.org/show_bug.cgi?id=433538
Nicolas Fella changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk,
|
16 matches
Mail list logo
