Never mind my previous message, I have found the problem:

k3b now forks itself into the background, exiting almost immediately.
If k3b is invoked from the command line while another k3b is running,
the arguments are passed to the existing process, which raises and focuses
itself.

My X session script runs k3b processes in an infinite loop due to the
chronic crashing bugs in previous versions (I would routinely drag a
file, save project, drag another file, crash, restart k3b automatically,
drag the file again, save project...about 10 times per CD).

With the new version of k3b, the script invokes k3b about once per second,
which causes the first k3b instance to keep focusing itself (I guess the
assumption is that I actually want to open a new k3b project every time).
This also adds the projects on the command line into k3b's open projects
list if they are not present, which gives the other odd behaviors I was
observing when trying to close a project.

The good news is that restarting k3b in an infinite loop doesn't seem to
be necessary any more--k3b no longer crashes on every 10th audio file.

OK, so it's not really a bug any more, but a feature request:  some
command-line option that gets back the previous 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...not good.

Attachment: signature.asc
Description: Digital signature

Reply via email to