[Okular-devel] [okular] [Bug 348212] Okular 1.0.0 is crashing an all documents (pdf, ps, epub...)

[Jorge Adriano]

https://bugs.kde.org/show_bug.cgi?id=348212

--- Comment #13 from Jorge Adriano <jorge.adriano at gmail.com> ---
(In reply to Ivan Čukić from comment #5)
> This seems to be happening only on opensuse so far (I'm marking this as a
> duplicate).
> 
>  Jorge, are you able to compile libkactivities with patches that I provide
> so that we can test?
> What output does 'kactivitymanagerd status' give you?
> 
> *** This bug has been marked as a duplicate of bug 347817 ***

OK this seems a bit messy, so it may be a packaging problem. 

Like I said in another comment, I moved from the stable Frameworks 5 branch to
wolfie's so I could test/use the newer Okular, which is what interests me the
most. And on moving, I was careful to 'switch system packages' to wolfie's to
make sure I didn't end up with a mix of stable/unstable. The repository is:
http://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Frameworks5/openSUSE_13.1/

I should also note that my current working desktop is 4.14, as the packages
allow (for the most part), to keep both. 

So I am running  4.14, and /usr/bin/kactivitymanagerd refers to the 4.14
version, and this doesn't take the "status argument". There is also
/usr/bin/kactivitymanagerd5, and its output is:

--------------------------------------------
kactivitymanagerd5 status
The service is running, version: 
--------------------------------------------
Like that ^, with no version is specified by the output. 

However, this made me realise the installed kactivitymanagerd5 is being
provided by the stable Frameworks 5  repository and not wolfie's, as the latter
installs binaries in /opt/kf5/bin/. Searching in wolfie's repository, it
doesn't appear to provide any kactivitymanagerd (which I guess is why it wasn't
replaced I guess, no dependency issues are detected though). I don't know if
this omission hints at some packaging problem...

As for compiling it libkactivities myself, quite frankly I'd be a bit wary of
trying that. Not much time on my hands and afraid to mess up mess up my working
system. I think contacting openSUSE's wolfi323 could be the way to go. He
should probably be interested in integrating the potential fix in his unstable
branch
https://build.opensuse.org/project/show/home:wolfi323

-- 
You are receiving this mail because:
You are the assignee for the bug.