On Windows, $KDEPREFIX%/bin/kdeinit4, when started at login, opens a command box. Instead of doing so, kdeinit4 should act like a service which does not open a command window. While it cannot be a system service, which could be controlled by Services.msc, having it load in the background without a window would integrate far better. Reproducible: Always Steps to Reproduce: 1. Install KDE for Windows 2. Set KDE to load services at login 3. Login to Windows Actual Results: See kdeinit4 open a command window Expected Results: Login, kdeinit4 launches, but does not open a window.
actually this is wanted behaviour. There are two (common) types of applications on Windows: GUI applications and console apps. The console apps automatically attach to a console (the black box) when started from e.g. explorer or from autostart. It would be theoretically possible to change kdeinit from console to GUI but that would also mean that we wouldn't get std streams (cout, cerr etc.) from them anymore without deeper modification. So the solution I would suggest is to add a wrapper executable which directly opens kdeinit (and which is a GUI application, so it won't open a console window). Is that ok for you?
Sent from my iPhone > On Aug 15, 2013, at 11:06 AM, Patrick Spendrin <ps_ml@gmx.de> wrote: > > https://bugs.kde.org/show_bug.cgi?id=323354 > > Patrick Spendrin <ps_ml@gmx.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |CONFIRMED > CC| |ps_ml@gmx.de > Ever confirmed|0 |1 > > --- Comment #1 from Patrick Spendrin <ps_ml@gmx.de> --- > actually this is wanted behaviour. There are two (common) types of applications > on Windows: GUI applications and console apps. The console apps automatically > attach to a console (the black box) when started from e.g. explorer or from > autostart. It would be theoretically possible to change kdeinit from console to > GUI but that would also mean that we wouldn't get std streams (cout, cerr etc.) > from them anymore without deeper modification. > So the solution I would suggest is to add a wrapper executable which directly > opens kdeinit (and which is a GUI application, so it won't open a console > window). Is that ok for you? > > -- > You are receiving this mail because: > You reported the bug.
Sorry for the messy reply from my phone.... Yes, using a wrapper would work fine. We could properly add the wrapper to the startup registry hive at that point (HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\) to allow it to start execution at login for the user. Doing it like this would require some small changes to the KDE Win32 control panel to write to the registry instead of adding an entry to the startup folder in the Start Menu hierarchy, but shouldn't be a huge task.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
The KDE Windows Bugzilla product is no longer maintained. If you have issues with some application on Windows, please report the issue at the bugtracker of the application. If you have issues that still persist with Craft itself, please report them here: https://invent.kde.org/packaging/craft/-/issues