[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681807: okular: sometimes fails to start, but no error message



On 07/16/2012 08:15 PM, Pino Toscano wrote:
> Alle lunedì 16 luglio 2012, Felix Zweig ha scritto:
>> Sometimes, starting Okular fails without any error message.
> 
> "fails" is  bit too generic; what does it happen?
> You get back to the console prompt, or it hangs?

Yeah, you're right. Sorry for being to generic. :)
Nothing shoes up, but the terminal keeps running. So, no, I'm not
getting back to the console prompt.

> Since when it is happening?

I think it started after upgrading to 4.8.4-1. But it worked in the
meantime, but now the problem started again (no correlating to any
okular upgrade

> Does the problem happens only when okular is started without a document?

Both with or without a document.

>> How can I get a more verbose output the further diagnose the problem?
> 
> Run kdebugdialog and enable all the okular debug areas (even those 
> without a number, use the filtering line edit on the top).

Enabling only okular debug areas leads to no output at all. Enabling
everything just shows:

$ okular
okular(27821)/kdeui (KGlobalAccel) KActionCollection::addAction:
Registering action  "go_first"  under new name  "first_page"
okular(27821)/kdeui (KGlobalAccel) KActionCollection::addAction:
Registering action  "go_last"  under new name  "last_page"
okular(27821)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to
open ksycoca from "/var/tmp/kdecache-sqrt/ksycoca4"
okular(27821)/kdeui (KGlobalAccel) KActionCollection::addAction:
Registering action  "file_save_as"  under new name  "file_save_copy"
okular(27821)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(27821)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(27821)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(27821)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
^C

This, and the fact that it worked in the meantime without changing
anything Okular related leads me to believe that the problem might not
be Okular specific.

Btw: I don't have any other KDE software installed, just Okular (and
systemsettings) on top of an Openbox installation.


Reply to: