Re: [opensuse-kde] Konqueror 4.1 giving error pages on almost any URL I direct it to
On Tuesday 05 August 2008 7:49:09 pm Rajko M. wrote:
On Tuesday 05 August 2008 04:01:32 pm Constantinos Maltezos wrote: ...
As stated in my comments on the bug report, I've had this problem since 4.0 came out.
KDE4 4.1 openSUSE ??
No... I was talking about Konqueror. Right now it's at 4.1, but I've had the problem since 4.0, when KDE 4 was first released. Since I said I didn't have this problem with Konqueror 3.5.9, it'd be pretty difficult to have had this problem since SuSE 4.0. And I only started with 6.2. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday 05 August 2008 09:10:30 pm Constantinos Maltezos wrote:
On Tuesday 05 August 2008 7:49:09 pm Rajko M. wrote:
On Tuesday 05 August 2008 04:01:32 pm Constantinos Maltezos wrote: ...
As stated in my comments on the bug report, I've had this problem since 4.0 came out.
KDE4 4.1 openSUSE ??
No... I was talking about Konqueror. Right now it's at 4.1, but I've had the problem since 4.0, when KDE 4 was first released. Since I said I didn't have this problem with Konqueror 3.5.9, it'd be pretty difficult to have had this problem since SuSE 4.0. And I only started with 6.2.
KDE4 is available for 10.3 and 11.0. I was using Konqueror quite a bit since your email, and there was one stray kio_http process that was taking more than 90% of CPU time, but I can't reproduce the error. I checked all web pages in recent history, and none produced problem again. My KDE4 setup: Machine is 32 bit openSUSE 11.0. I have separate user for KDE4. It is running as a second session right now. From your mail it seems that you are using the same user for both. I tried and desktop was messed up, icons in all sizes, etc, but second user had no problem. It is Konqueror kde4-konqueror-4.1.0-23.4. Last clean setup (renaming ~/.kde4) was a week ago, right after update that didn't work as expected. Well, that kind of numbers is what I expected to be able to search Novell bugzilla, Google etc. BTW, have you checked what is running with ps afx I have a 70 kio_file and kio_http. # ps afx | grep kio_http |wc -l 58 # ps afx | grep kio_file |wc -l 12 # killall -i kio_http kio_file will solve the problem for now. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday 05 August 2008 10:45:11 pm Rajko M. wrote:
KDE4 is available for 10.3 and 11.0.
I'm using 10.3
I was using Konqueror quite a bit since your email, and there was one stray kio_http process that was taking more than 90% of CPU time, but I can't reproduce the error. I checked all web pages in recent history, and none produced problem again.
I haven't noticed any hit in system performance. Just the inability to connect to the web servers (I think).
My KDE4 setup: Machine is 32 bit openSUSE 11.0. I have separate user for KDE4. It is running as a second session right now. From your mail it seems that you are using the same user for both. I tried and desktop was messed up, icons in all sizes, etc, but second user had no problem.
Correct about using the same user.
It is Konqueror kde4-konqueror-4.1.0-23.4. Last clean setup (renaming ~/.kde4) was a week ago, right after update that didn't work as expected.
Well, that kind of numbers is what I expected to be able to search Novell bugzilla, Google etc.
BTW, have you checked what is running with ps afx
I have a 70 kio_file and kio_http. # ps afx | grep kio_http |wc -l 58 # ps afx | grep kio_file |wc -l 12
I only had three each when I tried those commands after reading this email. So I dropped the wc command and these are what I got: user@machine:~> ps afx | grep kio_http 12499 ? Sl 0:00 \_ kdeinit4: kio_http [kd up 12527 ? Sl 0:00 \_ kdeinit4: kio_http [kd up 12560 pts/1 S+ 0:00 \_ grep kio_http user@machine:~> ps afx | grep kio_file 11411 ? S 0:00 \_ kdeinit4: kio_file [kd up 14132 ? S 0:00 \_ kio_file [kdeinit] file /tmp/ksocket-use 12570 pts/1 S+ 0:00 \_ grep kio_file (I changed ksocket-user to ksocket-use because for some reason, it dropped the last letter of my user name.)
# killall -i kio_http kio_file will solve the problem for now.
Well, guess what? It did. But only for a bit. After a couple of times, I took out the -i because even if there was something I should keep, I wouldn't know what it was, I think, but what happened was this: after using killall, I could connect to a website. I could maybe follow one or two links and I would have the problem again. I would use killall again and wherever I was going would load. And so on. Sometimes, the connection failed while the page was loading - leaving some images broken, for instance. I would then killall and refresh and it loaded okay. Until the next time. Okay, so kio_http (most of the time I used the killall command, I'd get "kio_file: no process killed", ruling that out) is somehow getting stuck on something? What's going on? Can I fix it? Do you have any suggestions as to how I could isolate the problem? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (2)
-
Constantinos Maltezos -
Rajko M.