Bug 74202 - Konqueror (and others) freeze when reading from DCOP socket
Summary: Konqueror (and others) freeze when reading from DCOP socket
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-05 07:16 UTC by jhsterne
Modified: 2004-11-19 15:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jhsterne 2004-02-05 07:16:49 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.1 
OS:          Linux

This seems to affect konqueror, knode and kopete (and perhaps others), but I had to choose somewhere to put it. ;) The problem is only intermittent: at times (and quite frequently with 3.2.0), konqueror will simply hang upon selecting a web page (or not start at all, if I select the URL from the desktop right-click menu). This appeared very rarely in 3.2rc1, but much more frequently in 3.2.0! I noticed that netstat showed no network activity, so I ran an strace and found konqueror hanging at

write(11, "\2\2\2\0\213\0\0\0b\0\0\0", 12) = 12
write(11, "\0\0\0\17konqueror-1076\0\0\0\0\5kded\0\0\0\0\t"..., 66) = 66
write(11, "\0\0\0\10\0h\0t\0t\0p\377\377\377\377\377\377\377\377\0"..., 73) = 73
read(11,

where fd 11 is $HOME/.DCOPserver__<domain-name>__0

Deleting the socket, and restarting dcopserver and kdeinit will get konqueror working again, but of course that leaves kdesktop and kicker unable to contact klauncher, requiring a restart of X/KDE!

I'm using Linux 2.6.2, if that means anything (this also appeared with 2.6.1).
Comment 1 Chuck Slivkoff 2004-08-31 18:31:41 UTC
I'm experiencing this same problem with my primary user account. Another account does not have this problem.

This is an extremely annoying problem that makes Kopete, Kmail, & other clients completely unusable. Any reference to a URL in these clients and they will hang on a socket read, same as what has been described.

I'm running SuSE 9.1 with KDE 3.2.1. I'm in the process of downloading 3.3 RPMs, but would like to find some pointers on how to debug this issue.

Comment 2 Chuck Slivkoff 2004-09-03 00:17:26 UTC
Well, I installed 3.3. Kopete does not hang now when I "hover" over a URL, but selecting it pops a window that seems to imply a message being sent to konqueror, but then it hangs, same as before.

Anyone have any ideas?
Comment 3 Stephan Kulow 2004-11-19 15:50:39 UTC
no idea. Please try strace on dcopserver to see what it's doing. And also kill klipper - which likes to cause such problems.