Bug 337428

Summary: can't start two processes of k3b
Product: [Applications] k3b Reporter: Stoat <stoatwblr>
Component: generalAssignee: k3b developers <k3b>
Status: CONFIRMED ---    
Severity: normal CC: aacid, stoatwblr, trueg
Priority: NOR    
Version: 2.0.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Stoat 2014-07-14 03:16:01 UTC 
This has been noted in the Ubuntu builds for a while (2+ years) but I don't see it as a KDE bugreport, so I'm putting it in now, in the hope that it can be resolved.

Symptom: 
Attempting to start multiple instances of k3b using the --nofork option gets the following error mesage:

$ k3b --nofork --device /dev/sr0
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(16946): KUniqueApplication: Can't setup D-Bus service. Probably already running. 

Repeatability: 100%, I've been experiencing this since Ubuntu 12.04 (possibly before then, as I didn't have multiple DVD writers installed)



Reproducible: Always

Steps to Reproduce:
1. start an instance of "k3b --nofork"
2. start a second instance  "k3b --nofork"

Actual Results:  
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(16946): KUniqueApplication: Can't setup D-Bus service. Probably already running. 



Expected Results:  
A second instance should start.
Comment 1 Albert Astals Cid 2014-09-28 00:25:43 UTC 
Actually what nofork does is not forking the process, and that works pretty well, creating two different instances is some other code.

Why do you need to run two instances of k3b?
Comment 2 Stoat 2015-10-20 23:34:47 UTC 
"Why do you need to run two instances of k3b?"

Multiple burners.

Unless you've changed the way it handles that.
Comment 3 Albert Astals Cid 2015-10-21 17:37:05 UTC 
So --nofork is not the problem, the problem is you can't start two processes, ok.
Comment 4 Stoat 2016-03-11 20:53:29 UTC 
--nofork USED to be the documented way of starting multiple k3b processes. It's been removed without any explanation other than "some users were inadvertently starting the program twice" - which is odd, because without --nofork, a second instance won't start.