Summary: | Okular gives "Attempt to use QAction "bookmark_action_0" with KXMLGUIFactory!" warning | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Tim Landscheidt <tim> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | hazelnusse |
Priority: | NOR | ||
Version: | 0.8 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Tim Landscheidt
2009-03-14 21:06:14 UTC
What is the problem with those warnings? In Okular's context, they are harmless, and unuseful. (In reply to comment #1) > What is the problem with those warnings? In Okular's context, they are > harmless, and unuseful. I use vim to edit .tex files and have a mapping that calls okular to view the output .pdf file. When I do this, the error message: Attempt to use QAction "bookmark_action_0" with KXMLGUIFactory! shows up in the middle of my vim buffer. It goes away once I scroll that line off of the screen, but it is annoying. Is there a good reason for okular complaining when you ask it to do one of it's main tasks (open a .pdf)? Pino said it right: The warnings are "unuseful". They hamper work: Whether you start okular on the command line or (sorry, no vi here :-)) Emacs, they cluster your screen. I often use "okular * &" on the shell, and then "mv" or "rm" the shown files. With the unnecessary warnings, this requires periodic C-l to clear the screen. Besides that, they also overshadow any real issues that may be hidden beneath. As a non-developer, I cannot judge whether the warnings indicate a problem, or a problem soon to emerge, or if "they are harmless". That's why I filed the two bugs. Do I know whether the bookmark_action_0 warning reflects the missing xmlns in Konqueror's bookmarks.xml? No, and I do not want to ask every time I run okular. IMVHO a program should never output warnings in "normal" operations, so that the user does not become accustomed to them and misses a critical one. Or the developer when testing the program. Beside the fact you can redirect the stderr on console to /dev/null (okular 2>/dev/null), you can disable those warnings from `kdebugdialog`. At least, in KDE 4.3 they are not a problem anymore (not that they were a problem before, just a generic warning to a situation that is not problematic in Okular). |