[drkonqi] [Bug 313823] New: DrKonqi should support correctly restarting PyKDE applications (like kajongg)
Jekyll Wu
adaptee at gmail.com
Thu Jan 24 12:17:23 GMT 2013
https://bugs.kde.org/show_bug.cgi?id=313823
Bug ID: 313823
Summary: DrKonqi should support correctly restarting PyKDE
applications (like kajongg)
Classification: Unclassified
Product: drkonqi
Version: 2.1.5
Platform: Other
OS: Linux
Status: CONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: adaptee at gmail.com
CC: kiagiadakis.george at gmail.com
PyKDE applications (like kajong)
If kajongg crashes, pressing the "Restart Application" will not successfully
restart kajongg.
The cause is drkonqi curretly relies upon /proc/<pid>/exe to determine the
binary path. However, for PyKDE applicaitons, that /proc/<pid>/exe points to
the python interpreter. So DrKonqi actually tries to restart python in that
kajongg case.
To solve the problem, DrKonqi could turn to /proc/<pid>/cmdline when it notices
the binary path is python. Or, maybe Drkonqi should just prefer
/proc/<pid>/cmdline, since that file usually contains all the exact arguments,
which means it is possible for DrKonqi to restart application in the exact same
arguements. One potential problem with /proc/<pid>/cmdline is some applications
might modify their cmdline arguments (like kdeinit4), which makes
/proc/<pid>/cmdline unusable for the restarting purpose.
Of course, the above usage of /proc is Linux centric.
Reproducible: Always
Steps to Reproduce:
1. start kajongg
2. kill -6 pid-of-kajongg
3. push the "Restart Application' button in DrKonqi
Actual Results:
kajongg not restarted
Expected Results:
kajongg restarted
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list