You are not logged in.
Hi,
I've got Krusader 2.2.0-beta1 autostarting after the today's KDE upgrade. On my notebook it autostarts even twice . ~/.kde4/Autostart is empty.
Offline
Do you have session saving enabled?
i assume, that Krusader was running at the time of logoff, hence KDE starts is again on next logon. Session saving is the default behaviour in KDE.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Do you have session saving enabled?
Probably I have. By the way, I can't find the option.
i assume, that Krusader was running at the time of logoff, hence KDE starts is again on next logon. Session saving is the default behaviour in KDE.
No. I close Krusader, relogin and it starts, twice.
Offline
No. I close Krusader, relogin and it starts, twice.
Three times, today
Offline
Hi,
I've got Krusader 2.2.0-beta1 autostarting after the today's KDE upgrade. On my notebook it autostarts even twice . ~/.kde4/Autostart is empty.
What about ~/.config/autostart
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
What about ~/.config/autostart
Just dropbox.desktop there.
Offline
Four times. Why am I not surprised?
Offline
I have two systems starting more and more krusader instances after kde start.
Offline
The issue is:
After exit from krusader the process still remains in the processlist. This is the reason why kde remembers and starts it again in next session.
I found no way to tell krusader not to do so.
Just a workaround would be to kill all these krusader processes before shutting down kde and the next startup will be clean.
Where can i tell kde to startup always clean (without remembering any previous sessions) ?
Offline
System settings / Advanced / Session management
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Maybe you have 'Start to tray' enabled in Krusader settings?
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
For me there were 9(!) krusader instances running today. Krusader simply doesn't exit its process properly and the zombie stays around being started by kde the next time. This is a bug, either in krusader or in kde. I tend to blame krusader. I use Alt-F2 and kill the krusader process(es) in the system monitor to work around this by now.
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Strange, I use Krusader Version 2.2.0-beta1 "DeKade" from the testing repo, extensively, and I dont have such problems. Maybe you could post your config here, to allow me reproduce the problem.
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Believe me, there is no chance to solve this with a config file. You can even delete krusaderrc and let the program recreate it. No change... So I guess there is no need to spam the forum with rcs ;-)
Harvey
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
What is an rcs?
zʇıɹɟʇıɹʞsuɐs AUR || Cycling in Budapest with a helmet camera || Revised log levels proposal: "FYI" "WTF" and "OMG" (John Barnette)
Offline
Linux is like a wigwam: No Gates, no Windows and an Apache inside
Offline
Fixed in krusader SVN.
Here's a bug report:
https://bugs.kde.org/show_bug.cgi?id=240319
Offline