Bug 323354 - kdeinit4.exe on Windows opens a command window, instead of operating as a service
Summary: kdeinit4.exe on Windows opens a command window, instead of operating as a ser...
Status: CONFIRMED
Alias: None
Product: kde-windows
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.10
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-10 21:55 UTC by Gary L. Greene, Jr.
Modified: 2021-03-09 23:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary L. Greene, Jr. 2013-08-10 21:55:45 UTC
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.
Comment 1 Patrick Spendrin 2013-08-15 18:06:12 UTC
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?
Comment 2 Gary Greene 2013-08-15 20:22:05 UTC
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.
Comment 3 Gary L. Greene, Jr. 2013-08-15 20:28:50 UTC
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.
Comment 4 Justin Zobel 2021-03-09 23:01:52 UTC
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.