Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#46183 closed defect (fixed)

okular @4.13.3_0 Cannot open files directly from the command line

Reported by: dsfrancis03@… Owned by: NicosPavlov
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: mkae (Marko Käning), RJVB (René Bertin), francnet00@…
Port: okular

Description

Hello,

I have a Late 2008 15" Macbook Pro. I recently installed Yosemite (clean install) on my Macbook and also installed kde4-kile through macports 2.3.3. The installations of all the related ports seemed fine except for two ports, okular @4.13.3_0 and kde4-kile @2.1.3_1. In this post, I'd like to discuss my problem regarding okular.

If I open okular first and then open a file from File - Open menu, then okular opens the file with no problem. However, if I try to open a file using okular from kile, or if I try to open a file using okular from the command line (e.g, '/Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular abc.pdf'), then okular fails to open the file. Here is the error message:

okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(609)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
KCrash: Application 'okular' crashing...
KCrash: Attempting to start  directly
KCrash failed to exec(), errno = 2

And, here are more about okular:

$ /Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular --version 
Qt: 4.8.6
KDE Development Platform: 4.13.3
Okular: 0.19.3

Please help me solve this issue and let me know if more information is needed.

I have another issue regarding kile, which doesn't open a file by drag-and-drop, and I'll probably open a new ticket later. But, before I open a new ticket, if anyone is familiar with this issue, please advise.

Change History (12)

comment:1 Changed 10 years ago by larryv (Lawrence Velázquez)

Owner: changed from macports-tickets@… to nicos@…
Port: okular added; Okular removed

Thanks for the report. In future tickets, please Cc any port maintainers (port info --maintainers okular).

comment:2 Changed 10 years ago by NicosPavlov

The issue seems to be due to some linkage error:

dyld: lazy symbol binding failed: Symbol not found: __ZN11KFileDialog4execEv
  Referenced from: /Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular
  Expected in: /opt/local/lib/libkio.5.dylib

dyld: Symbol not found: __ZN11KFileDialog4execEv
  Referenced from: /Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular
  Expected in: /opt/local/lib/libkio.5.dylib

Trace/BPT trap: 5

It also occurs when trying to open files from the interface menu, but the drag and drop is working. I unfortunately have no solution for this now.

comment:3 Changed 10 years ago by NicosPavlov

After the upgrade to 4.14.3, the opening from the menu seems to work again for me, which means that the problems of lazy binding may not be relevant for the reported issue.

comment:4 Changed 10 years ago by dsfrancis03@…

I haven't experienced a similar issue when opening a file from the menu. The issue appears when I try to open from the command line. I upgraged okular to 4.14.3 too, but the issue of failing to open a file from the command line still appears.

comment:5 in reply to:  1 Changed 10 years ago by leonidas61@…

I have the same problem with okular 4.14.3. As I remember some old versions worked as expected (I used okular about 2 years ago)

comment:6 Changed 10 years ago by mkae (Marko Käning)

Cc: mk@… added

Cc Me!

comment:7 Changed 10 years ago by mkae (Marko Käning)

Cc: rjvbertin@… added
Version: 2.3.3

René, does this sound familiar to you?

comment:8 Changed 10 years ago by RJVB (René Bertin)

Sorry, no. I simply get a crash in that scenario that's not due to a symbol not being found.

comment:9 Changed 10 years ago by francnet00@…

Cc: francnet00@… added

Cc Me!

comment:10 Changed 10 years ago by NicosPavlov

Resolution: fixed
Status: newclosed

It seems to me that the fix proposed for ticket #47054 also solved this issue.

comment:11 Changed 9 years ago by theufman@…

I just installed kile 2.1.3_1 and okular 4.14.3_0 and I am having the same issue. I cannot open okular from the command line and kile cannot open an okular instance either.

Last edited 9 years ago by theufman@… (previous) (diff)

comment:12 Changed 9 years ago by NicosPavlov

Then you should update your port database with

sudo port selfupdate

and upgrade the outdated ports, as the fix which closed this ticket is included in okular 4.14.3_1.

Note: See TracTickets for help on using tickets.