Summary: | kdeinit4.exe on Windows opens a command window, instead of operating as a service | ||
---|---|---|---|
Product: | kde-windows | Reporter: | Gary L. Greene, Jr. <greeneg> |
Component: | general | Assignee: | KDE-Windows <kde-windows> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | ps_ml, toddrme2178 |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
Gary L. Greene, Jr.
2013-08-10 21:55:45 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? 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. |