Okular crash problem

English Applications
1

Hi guys and thanks in advance.
For info:
OS: Linux 2.6.27.39-0.2-default i686
System: openSUSE 11.1 (i586)
KDE: 4.1.3 (KDE 4.1.3) “release 4.11.1”

Okular
Version 0.7.3
Using KDE 4.1.3 (KDE 4.1.3) “release 4.11.1”

I’ve not been able to open any pdf of variable sizes in okular since I tried to copy and paste a medium (20-30 page) pdf to writer (the pdf was my own creation from tex).
Okular will open fine as a program, the problem is when I open a pdf.
There is no backtrace report (I request details but says none are available) and half the time the bug request screen crashes. The terminal on pdf load gives:

Bogus memory allocation size
KCrash: Application 'okular' crashing...
sock_file=/home/user/.kde4/socket-linux-x48a/kdeinit4__0

Have looked for similar stuff online but have not been faring well. I tried uninstalling & reinstalling. I tried clearing out the /home/user/.kde4/share/apps/okular/ folder.

Not really sure where to go from here.
Any suggestions appreciated.
Ben

2

Navigate to .kde4
find the folder /socket-linux-x48a
Hover over it and take note of the /tmp location too

delete the files in both the .kde4 and /tmp locations

see if that helps

3

Thanks for helping.
I tried that and all it seemed to do was say that Kcrash couldn’t find the file in that directory I just cleared in order to log the crash. Apart from that it still gave no error information on the crash.
I restarted and tried again and it recreated the files (some of them anyway) in the directory. back as it was. Same error.

4

Let’s make sure we get rid of stuff at boot, do this
Clear Temp Files at Boot - openSUSE Forums

delete this folder
.kde4/share/apps/okular

delete these files:
.kde4/share/config/okularpartrc
.kde4/share/config/okularrc

5

k, done that, restarting

6

Did that, same issue recurring.
That’s a pity.

7

Strange. It does seem like it must be related to what you were doing but I’m not sure.
I do know I would be updating my kde if I were you. But I don’t want to push that as a solution.

Try this first.
Create a new user and login with it
Does it happen there?
If not then it’s an issue in your user settings
You need auto login off to use multiple accounts
Disable Auto-Login - openSUSE Forums

If the new user is OK. You could go to the extreme of starting a new .kde4 in your normal login
From a terminal:

mv .kde4 .kde4-old

logout and in

8

Tried a new user and the same problem occured, except for the error message in the terminal just said Bogus memory…etc
It didn’t have the other lines about Kcrash and sock.
If it helps I could update to suse11.2. I haven’t done so because a run a few programs through wine and my setup works fine, and I didn’t want to rock the boat for no reason.

9

I was thinking keep 11.1 just update kde

KDE4.3.* Upgrade - HowTo - openSUSE Forums

10

Ok, that’s chugging away.
I’ll try again afterwards and post what happens.
thanks again for thus far.

11

Ok, I felt i followed instructions fairly well, but it’s gone horribly wrong.
Tried to update KDE and now plasma crashes on start, as does run command(?).
This is a bit more than an okular problem!
Help!
Should I post a new thread for this?

12

Did you make sure you had your repo priorities correct as outlined? Update repo in particular (which is default 20 in 11.1) needs changing to 99

You can get to yast from level 3
Level 3 Boot and Yast - Windows Live

All that may be needed is to console login as user and do this

mv .kde4 .kde4-old

http://public.bay.livefilestore.com/y1phHT9bsTPahYokC0lTEPeQvKmT3zwerZDYpMtCXJNOgAHoS9aXJw6q22hM-P9evEP9v0qnHq89KMC-El5iLCVfA/console.login.png

13

That didn’t work. I retreated back to 4.1 by undoing the upgrade process. Back to square one. I also tired okular in GNOME and it wouldn’t work there.
I did try it on a very small pdf and it loaded fine. I must have some how affected how much memoery okular thinks it has available to it.
How does okular do such things?

14

Have you had a look in Okular’s settings, there is a section on memory use.

You could always try adobe:O

15

I know there are others, I have evince and kpdf. But I like them for different things, and I prefer okular’s search cpabilities (it’s not much of a reason I know).
Any how…
I tried that before and it didn’t make much difference, except i also sometimes get the line

Unable to start Dr. Konqi

or

okular: Fatal IO error: client killed

in the terminal when it crashes.

16

I downgraded poppler pdf rendering program and it seems to be working fine. Might try upgrading back to see if resetting it helps. But it is working, and a downgraded poppler is accetable.
Thanks for your help along the way. Just the wireless problem now, but that’s got a new thread. Cheers.
Ben

17

Good news Ben
There were a bunch of Poppler updates just recently
So you rolled them back eh.
Well done.

18

And just to close off… poppler updated itself (the sly dog) and it all seems to be working.