Bug 335362 - Okular can not open PDF and DVI files
Summary: Okular can not open PDF and DVI files
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (show other bugs)
Version: 0.19.0
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-26 11:23 UTC by Antonio
Modified: 2014-05-27 12:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio 2014-05-26 11:23:43 UTC
The messages in Terminal when okular is open is
%%%%%%%%%%%%%
~$ okular
okular(24291)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "okular/Generator"  not found 
okular(24291)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(24291)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(24291)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(24291)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(24291)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
%%%%%%%%%%%%%%%%%%%%%%%%

And when I try to open a file  I get the message "No se puede abrir /.../file.pdf" (Can't open .../file.pdf)
In the terminal OKULAR writes

%%%%%%%%%%%%%%%
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /home/apall/.local/share
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /etc/mtab
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /etc/fstab
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /home/apall/Documentos
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /home/apall/Documentos
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /home/apall/Documentos/ViejoUbuntu
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No queda espacio en el dispositivo
QFileSystemWatcher: failed to add paths: /home/apall/Documentos/ViejoUbuntu/Escritorio
okular(24516)/kdecore (trader): KMimeTypeTrader: couldn't find service type "okular/Generator" 
Please ensure that the .desktop file for it is installed; then run kbuildsycoca4. 
okular(24516)/okular (app) Okular::Document::openDocument: No plugin for mimetype '"application/pdf"'.




Reproducible: Always




I just install Ubuntu 14.04 (64) and the packages kile and okular that are in the ubuntu repositories using synaptic.
The problem starts just the first time I try to open a pdf or a dvi build with kile calling okular from this program, and later I open okular directly and I get the same error.
Comment 1 Christoph Feck 2014-05-26 12:12:24 UTC
Does this happen on a freshly created user account?
Comment 2 Antonio 2014-05-26 12:15:12 UTC
yes

The SO was installed yesterday on a formatted disk, and the user is new


El 26/05/14 14:12, Christoph Feck escribió:
> https://bugs.kde.org/show_bug.cgi?id=335362
>
> --- Comment #1 from Christoph Feck <christoph@maxiom.de> ---
> Does this happen on a freshly created user account?
>
Comment 3 Luigi Toscano 2014-05-26 19:22:17 UTC
(In reply to comment #0)
> QFileSystemWatcher: failed to add paths: /home/apall/Documentos
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> queda espacio en el dispositivo
> QFileSystemWatcher: failed to add paths: /home/apall/Documentos
> QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> queda espacio en el dispositivo

Doesn't "No queda espacio en el dispositivo" mean "No space left on device"? Could you please recheck the space on your system?
Comment 4 Antonio 2014-05-26 20:58:59 UTC
Dear Luigi

I just recheck the space in the ext4 volume for the system
and I have almost 1.2 Tb of free space.

Thanks for your work






El lun, 26-05-2014 a las 19:22 +0000, Luigi Toscano escribió:
> https://bugs.kde.org/show_bug.cgi?id=335362
> 
> Luigi Toscano <luigi.toscano@tiscali.it> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |luigi.toscano@tiscali.it
> 
> --- Comment #3 from Luigi Toscano <luigi.toscano@tiscali.it> ---
> (In reply to comment #0)
> > QFileSystemWatcher: failed to add paths: /home/apall/Documentos
> > QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> > queda espacio en el dispositivo
> > QFileSystemWatcher: failed to add paths: /home/apall/Documentos
> > QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No
> > queda espacio en el dispositivo
> 
> Doesn't "No queda espacio en el dispositivo" mean "No space left on device"?
> Could you please recheck the space on your system?
>
Comment 5 Luigi Toscano 2014-05-26 21:03:15 UTC
(In reply to comment #4)
> I just recheck the space in the ext4 volume for the system
> and I have almost 1.2 Tb of free space.

Just to be totally sure: is the partion unique? (== is /home on the same partition of the system, or in a separate one?)
Comment 6 Antonio 2014-05-26 22:16:01 UTC
Ir is in the same partición. In fact I have one small for the interchange swap and one big for the all the rest

Tanks once more



Enviado desde mi iPad

> El 26/05/2014, a las 23:03, Luigi Toscano <luigi.toscano@tiscali.it> escribió:
> 
> https://bugs.kde.org/show_bug.cgi?id=335362
> 
> --- Comment #5 from Luigi Toscano <luigi.toscano@tiscali.it> ---
> (In reply to comment #4)
>> I just recheck the space in the ext4 volume for the system
>> and I have almost 1.2 Tb of free space.
> 
> Just to be totally sure: is the partion unique? (== is /home on the same
> partition of the system, or in a separate one?)
> 
> -- 
> You are receiving this mail because:
> You reported the bug.
Comment 7 Antonio 2014-05-27 10:17:42 UTC
Dear Luigi

This morning Ubuntu offered an updated for  the linux-core,
I istall it and after that I unistall okular and kile and I reinstall 
both programs

The problem I had, disappears. Now both programs works properly

Thanks for your work.

Antonio Pallares






El 26/05/14 23:03, Luigi Toscano escribió:
> https://bugs.kde.org/show_bug.cgi?id=335362
>
> --- Comment #5 from Luigi Toscano <luigi.toscano@tiscali.it> ---
> (In reply to comment #4)
>> I just recheck the space in the ext4 volume for the system
>> and I have almost 1.2 Tb of free space.
> Just to be totally sure: is the partion unique? (== is /home on the same
> partition of the system, or in a separate one?)
>
Comment 8 Luigi Toscano 2014-05-27 12:55:47 UTC
(In reply to comment #7)
> This morning Ubuntu offered an updated for  the linux-core,
> I istall it and after that I unistall okular and kile and I reinstall 
> both programs
> 
> The problem I had, disappears. Now both programs works properly

Thanks for the feedback! I would say the problem was related to some temporary glitch on the system. I'm going to close this bug, if it reappears consistently feel free to reopen it.