Bug 292068 - no option to start krfb in background
Summary: no option to start krfb in background
Status: RESOLVED FIXED
Alias: None
Product: krfb
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: George Goldberg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-20 21:24 UTC by illumilore
Modified: 2019-09-17 00:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description illumilore 2012-01-20 21:24:12 UTC 
Version:           unspecified
OS:                Linux

If running krfb as the default remote desktop server that autostarts with bootup, there is always a window that asks about new invitations, and there is no option to turn this off so it just starts silently

Reproducible: Always

Steps to Reproduce:
na

Actual Results:  
na

Expected Results:  
na

na
Comment 1 Andrew Crouthamel 2018-11-06 15:19:17 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-18 03:36:06 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bernard Gray 2019-09-17 00:01:08 UTC 
This can be closed:

commit d5aff98912deebf204ddcc773894b73a3163eb56
Author: Friedrich W. H. Kossebau <kossebau@kde.org>
Date:   Fri Mar 1 05:31:12 2019 +0100

    Properly add "nodialog" option before running QCommandLineParser::process()