[Konsole-devel] [Bug 279915] "exec daemon konsole" fails

[Askar Safin]

https://bugs.kde.org/show_bug.cgi?id=279915


Askar Safin <safinaskar at mail.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




--- Comment #11 from Askar Safin <safinaskar mail ru>  2012-01-15 15:02:48 ---
* "konsole --nofork > /dev/null" bug fixed (see bug 288200)

* "exec daemon konsole" bug still exists

* If you don't want to deal with "daemon", "start-stop-daemon" etc, I recommend
another command: "trap '' HUP; setsid konsole < /dev/null > /dev/null 2>
/tmp/log & exit". This command actually daemonizes konsole without special
tools. Also you can see error message in /tmp/log:

unnamed app(2118): Communication problem with  "konsole" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not
receive a reply (timeout by message bus)" "

* Bug exists only if konsole started from menu, icon or by command "kdeinit4
konsole" from xterm

* Bug depends of Linux kernel version!! o_O I can reproduce bug on Debian Sid
or Wheezy with "linux-image-3.0.0-12-generic" from Ubuntu with proprietary
blobs. But I cannot reproduce on the same system with
"linux-image-3.1.0-1-amd64" from Debian without proprietary blobs

* I think reason is following: when I type "trap...", new konsole runs, but old
still running too. New konsole runs function KUniqueApplication::start(...)
from libkdeui and forks (in this function). Child tries to register in DBus,
but DBus says that service already registred (because old konsole runs). Then
old konsole terminates, and parent tries to connect to DBus. But it cannot,
because old konsole terminated and service is not registred anymore. So, parent
prints: "Communication problem..."

* When I add debug output, bug disappears o_O. This is Heisenbug. Bug is very
sensible to time intervals

* This is better way to reproduce bug: run konsole from menu (or icon), type
"trap...". If new konsole window appear, close it and run konsole from menu
again etc

*************
I think bug is very hard to fix, because one cannot make atomic registering in
DBus in one process and connecting to it in another process. So, I want to ask
developers: it is really important (and possible) to fix the bug? If no, I will
remove this bug with "RESOLVED/LATER" or something like that

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.