Version: (using KDE 4.1.3) OS: Linux Installed from: Slackware Packages way to reproduce: 1, In a terminal, use okular to open a pdf file, say temp.pdf 2, run this script in other terminal: ============================= #!/bin/bash i=1 while [ $i -lt 20 ]; do mv temp.pdf temp sleep 1 mv temp temp.pdf i=$[$i + 1] done ============================ 3, then close the okular window, the main window disappeared. But you can see okular doesn't quit. The last few messages are: okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added already watched Entry "/home/grissiom/sandbox" (for "/home/grissiom/sandbox/temp.pdf" ) okular(1920)/kio (KDirWatch) KDirWatch::setDirty: "KDirWatch-1" emitting dirty "/home/grissiom/sandbox" okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added already watched Entry "/home/grissiom/sandbox" (for "/home/grissiom/sandbox/temp.pdf" ) okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added already watched Entry "/home/grissiom/sandbox" (for "/home/grissiom/sandbox/temp.pdf" ) okular(1920)/kio (KDirWatch) KDirWatch::setDirty: "KDirWatch-1" emitting dirty "/home/grissiom/sandbox" okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added already watched Entry "/home/grissiom/sandbox" (for "/home/grissiom/sandbox/temp.pdf" ) okular(1920)/kio (KDirWatch) KDirWatch::setDirty: "KDirWatch-1" emitting dirty "/home/grissiom/sandbox" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox/temp.pdf" sub_entry: 0x0 okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added already watched Entry "/home/grissiom/sandbox/temp.pdf" (now 1 clients) "[KDirWatch-1]" okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring okular(1920)/kio (KDirWatch) KDirWatch::setCreated: "KDirWatch-1" emitting created "/home/grissiom/sandbox/temp.pdf" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox" sub_entry: 0x82ae1dc okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox/temp.pdf" sub_entry: 0x0 okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Cancelled INotify (fd 15, 1) for "/home/grissiom/sandbox/temp.pdf" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Removed File "/home/grissiom/sandbox/temp.pdf" for "" ["KDirWatch-1"] okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox" sub_entry: 0x0 okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Cancelled INotify (fd 15, 40) for "/home/grissiom/sandbox" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Removed Dir "/home/grissiom/sandbox" for "" ["KDirWatch-1"] okular(1920)/kdecore (trader) KMimeTypeTrader::query: query for mimeType "application/pdf" , "okular/Generator" : returning 1 offers okular(1920)/okular (app) Okular::Document::requestPixmaps: request id=3 866x1225@0 okular(1920)/okular (app) Okular::DocumentPrivate::sendGeneratorRequest: sending request id=3 866x1225@0 async == true okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/home/grissiom/sandbox/temp.pdf" for "" ["KDirWatch-1"] okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added Dir "/home/grissiom/sandbox" for "" ["KDirWatch-1"] okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring okular(1920)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring okular(1920)/okular (app) Okular::Document::requestPixmaps: request id=3 866x1225@0 okular(1920)/okular (app) Okular::Document::requestPixmaps: request id=3 866x1225@0 okular(1920)/okular (app) Okular::Document::requestPixmaps: request id=4 259x367@0 okular(1920)/okular (app) Okular::DocumentPrivate::sendGeneratorRequest: sending request id=4 259x367@0 async == true okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox/temp.pdf" sub_entry: 0x0 okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Cancelled INotify (fd 15, 41) for "/home/grissiom/sandbox/temp.pdf" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Removed File "/home/grissiom/sandbox/temp.pdf" for "" ["KDirWatch-1"] okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: path= "/home/grissiom/sandbox" sub_entry: 0x0 okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Cancelled INotify (fd 15, 42) for "/home/grissiom/sandbox" okular(1920)/kio (KDirWatch) KDirWatchPrivate::removeEntry: Removed Dir "/home/grissiom/sandbox" for "" ["KDirWatch-1"] okular(1920)/kio (bookmarks) KBookmarkManager::saveAs: KBookmarkManager::save "/home/grissiom/.kde/share/apps/okular/bookmarks.xml" okular(1920)/kparts KParts::Part::~Part: deleting widget Sidebar(0x8133ca8) "" symptoms： 1, open a system monitor, I can see okular consume nearly 50% "CPU System Load". When I try to kill it, it does not have any response. 2, When I lsof my system, I can see okular is using my disk. I wish I have provided enough info that you can debug into it.
*** Bug 179974 has been marked as a duplicate of this bug. ***
Can't reproduce it here :-/
KDE 4.2, I can reproduce this always, however in my case, the biggest problem is not CPU but after-quit effect. When the script is finished, I can normally used okular, for example go to next page, etc. But the moment I quit, entire system is frozen, including mouse, keyboard (caps lock, num lock), power off button too. Btw. my CPU is 64-bit and so the system. Please consider changing the status to crash -- it does not show the crash log, but technically it is crash (after all, all user can do is pull out the plug).
(In reply to comment #3) > KDE 4.2, I can reproduce this always, however in my case, the biggest problem > is not CPU but after-quit effect. Your problem is not this one, but bug #180521.
@anyone who can reproduce -this- bug: Which kernel are you using? Can you please try the instructions I gave in https://bugs.kde.org/show_bug.cgi?id=180521#c13 and see whether it changes anything? Thanks!
The problem listed in the original post was gone in KDE4.2. So mark it as resolved. Thanks for caring!