From 14286a0eb6ec163c90e3d13c27fea147dbb82481 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sl=C3=A1vek=20Banko?= Date: Fri, 5 Jul 2013 19:06:59 +0200 Subject: Initial import --- BUGS | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 BUGS (limited to 'BUGS') diff --git a/BUGS b/BUGS new file mode 100644 index 0000000..98f495d --- /dev/null +++ b/BUGS @@ -0,0 +1,29 @@ +Known issues +------------ +1. Error messages are not transmitted from the previous instance of KDocker to +the latest instance. So, if you already have KDocker running and you start +another instance of KDocker saying "kdocker blah", you wont receive any error +message. + +2. Problem with relative paths if new instance of KDocker and old instance of +KDocker are started from different directories (the current directory +information is not transmitted across instances) + +Reporting Bugs +-------------- +Bugs and wishes to gramakri at uiuc dot edu. Follow the guidelines below , if +possible and send it to me at gramakri at uiuc dot edu. + +* Add the following line in kdocker.pro (in fact just uncomment it) + DEFINES += ENABLE_TRACING +* Now do a "make clean" and "then make". +* Launch KDocker. Recreate the problem. +- Right Click on the tray icon. +- Choose "About KDocker" +- You should see a button called "Show Trace". Please note that this button + will appear only when compiled with tracing +- If you send SIGUSR1 to the KDocker process, it will dump all the trace to + ~/kdocker.trace. Send that file to me. + +May the force be with you. + -- cgit v1.2.1