Normally and everyday I use Firefox as my browser, but sometimes I like to use Konqueror (which has improved a lot).
It works fine with the biggest part of the web pages, a few times not so well, but zdnet.com makes is crash, always. Not zdnet.co.uk, nor zdnet.com.au, only .com.
Is it only my Konqueror or does it happen to everyone here?
> Is it only my Konqueror or does it happen to everyone here?
mine (Konqueror 3.5.7 using KDE3.5.7 “release 72.11” openSUSE 10.3)
runs fine on zdnet.com, so there you go.
–
decorated_warrior
somebody_else adjusted his/her AFDB on Monday 25 May 2009 18:47 to write:
>> Is it only my Konqueror or does it happen to everyone here?
>
> mine (Konqueror 3.5.7 using KDE3.5.7 “release 72.11” openSUSE 10.3)
> runs fine on zdnet.com, so there you go.
>
Goes down like a very heavy thing from a very great height with a following
wind here.
Segfaults, on ver 4.2.86 release 126,.64bit
Now my crash reading is a bit iffy at the best but it could be qt related?
However I will stress that this system is my sorta sandbox and is not a run
of the mill install so YMMV.
Mark
Nullus in verba
Nil illegitimi carborundum
somebody_else wrote:
>> Is it only my Konqueror or does it happen to everyone here?
The top “konqueror-killer” is usually some piece of javascript code. Try to
disable just for this site and see what happens.
> mine (Konqueror 3.5.7 using KDE3.5.7 “release 72.11” openSUSE 10.3)
> runs fine on zdnet.com, so there you go.
I’m using konqueror 3.5.9 (openSUSE 10.3) and cannot access to any article
inside “linuxjournal” site. Just “breaks”. Always 
I.e.
http://www.linuxjournal.com/content/one-two-three-or-more-view-it-displaylink-and-usb
Greetings,
–
Camaleón
The same thing happens with java and javascript disabled, konqueror simply starts to load the page and next to the end of the load it crashes.
Maybe the people of the konqueror project should know about it
I forgot to mention that I am using Konqueror 4.2.
isaba wrote:
> The same thing happens with java and javascript disabled, konqueror
> simply starts to load the page and next to the end af the load it
> crashes.
Try to disable plugins and recheck.
Second “konqueror-killer” is “flash” O:-)
> Maybe the people of the konqueror project should know about it
Sure
Greetings,
–
Camaleón
> http://www.linuxjournal.com/content/one-two-three-or-more-view-it-displaylink-and-usb
whoa! that kills mine also…(but, works great in Firefox)
–
decorated_warrior
> Just opened zdnet.com in Konqueror 4.2.3 with no problems at all.
Me also. I browsed a few articles as well. No issues.
Maybe it would be wiser to simply update your KDE4 and Konqueror to 4.2.3? 
(it works in KDE 4.2.3 for me also)
warnec adjusted his/her AFDB on Tuesday 26 May 2009 21:26 to write:
>
> Maybe it would be wiser to simply update your KDE4 and Konqueror to
> 4.2.3?
>
> (it works in KDE 4.2.3 for me also)
>
>
I am still getting it but it does now load the background and header, gets
to about loading 110 of 180`ish images and then segfaults:
<<smip>>
Application: Konqueror (konqueror), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f730e83c760 (LWP 7688))]
Thread 3 (Thread 0x7f7304335950 (LWP 7692)):
#0 0x0000003c48c0afdd in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x00007f730fa32df7 in QWaitCondition::wait(QMutex*, unsigned long) ()
from /usr/lib64/libQtCore.so.4
#2 0x00007f730fa28a99 in ?? () from /usr/lib64/libQtCore.so.4
#3 0x00007f730fa31e65 in ?? () from /usr/lib64/libQtCore.so.4
#4 0x0000003c48c07070 in start_thread () from /lib64/libpthread.so.0
#5 0x0000003c480d310d in clone () from /lib64/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 2 (Thread 0x7f7303335950 (LWP 7704)):
#0 0x0000003c48c0afdd in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1 0x00007f730fa32df7 in QWaitCondition::wait(QMutex*, unsigned long) ()
from /usr/lib64/libQtCore.so.4
#2 0x00007f730fa28a99 in ?? () from /usr/lib64/libQtCore.so.4
#3 0x00007f730fa31e65 in ?? () from /usr/lib64/libQtCore.so.4
#4 0x0000003c48c07070 in start_thread () from /lib64/libpthread.so.0
#5 0x0000003c480d310d in clone () from /lib64/libc.so.6
#6 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f730e83c760 (LWP 7688)):
[KCrash Handler]
#5 0x00000030cfababc9 in ?? () from /usr/lib64/libkhtml.so.5
#6 0x0000000000000005 in ?? ()
#7 0x0000000000000000 in ?? ()
>>pins<<
If I restart konq straight away it does complete the page and then konq just
disappears with a slightly different segfault error.
If I go to zdnet.co.uk all is fine.
Works fine in fiirefox though.
–
Mark
Nullus in verba
Nil illegitimi carborundum
I’m not sure this helps as much as it might, but I’ve just tried 3.5.10 and 4.2.3 and neither crash.
The reason that this is less helpful than it might be is that the GUI I’m currently running is kde 4.2 on e16 (which is an experiment, and one that initially happened by accident) and that’s not really mainstream.