Bug 123392 - command-line option for K3b not to run in the background and exit right away
Summary: command-line option for K3b not to run in the background and exit right away
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-10 20:32 UTC by Francois Marier
Modified: 2006-11-24 11:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francois Marier 2006-03-10 20:32:12 UTC
Version:           0.12.12 (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Zygo Blaxell <zblaxell@furryterror.org> has requested the following feature on the Debian bug tracking system (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355772):

Some command-line option that gets back the previous (0.11) non-exiting 
behavior.

I have some other not-yet-upgraded systems which produce CD's and DVD's
with automated scripts that do various verification, bookkeeping and data
organization tasks.  The UI is almost entirely headless--an operator
inserts a disc into a drive, it is burned and verified, an appropriate
matching label is printed (no label if the verification failed), the
disc is ejected, and the script waits for another disc to be inserted.
The scripts support "custom" or "manual" operation by having an entry
type in the work queue database that means "invoke k3b on the console
X display and wait for it to exit."  If I were to upgrade k3b on these
systems, they would probably have k3b running at the same time as the
scripts are trying to take control of the drive to process the next disc
image in the queue...
Comment 1 Sebastian Trueg 2006-11-24 11:34:24 UTC
Every KUniqueApp has the --nofork parameter.