Version: (using KDE KDE 3.5.3) Installed from: Debian testing/unstable Packages OS: Linux since upgrading to KDE 3.5.2 (I guess) akregator refuses to start, problem consists after upgrading to 3.5.3. akregator itself shows a window (where some part in the upper left is not painted), which doesn't show any content (except for the default window color ...) running "strace akregator" shows: [...] connect(3, {sa_family=AF_FILE, path="/tmp/.ICE-unix/dcop12177-1152135557"}, 38) = 0 fcntl64(3, F_SETFD, FD_CLOEXEC) = 0 write(3, "\0\1\0\0\0\0\0\0", 8) = 8 read(3, "\0\1\0\0\0\0\0\0", 8) = 8 [...] write(3, "\1\2\1\0I\0\0\0\0\0\0\0", 12) = 12 write(3, "\0\0\0\0\0\0\0\vDCOPServer\0\0\0\0\1\0\0\0\0\25regi"..., 53) = 53 write(3, "\0\0\0\20anonymous-12678\0", 20) = 20 read(3, "\2\3\0\0028\0\0\0", 8) = 8 read(3, "\210\0\0\0", 4) = 4 read(3, "\0\0\0\vDCOPServer\0\0\0\0\0\0\0\0\tQCString\0"..., 56) = 56 write(3, "\1\2\1\0`\0\0\0\210\0\0\0", 12) = 12 write(3, "\0\0\0\20anonymous-12678\0\0\0\0\vDCOPServ"..., 82) = 82 write(3, "\0\0\0\nakregator\0", 14) = 14 read(3, "\2\3\0\0024\0\0\0", 8) = 8 read(3, "\210\0\0\0", 4) = 4 read(3, "\0\0\0\vDCOPServer\0\0\0\0\20anonymous-126"..., 52) = 52 write(3, "\1\2\1\0j\0\0\0\2\0\0\0", 12) = 12 write(3, "\0\0\0\20anonymous-12678\0\0\0\0\nakregato"..., 70) = 70 write(3, "\0\0\0\f/home/apexo\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0"..., 36) = 36 read(3, "\2\5\0\2&\0\0\0", 8) = 8 read(3, "\2\0\0\0", 4) = 4 read(3, "\0\0\0\nakregator\0\0\0\0\20anonymous-1267"..., 38) = 38 read(3, and that's it. Ctrl+C changed the last line to read(3, <unfinished ...> oddly enough it works when running as root ... (which is quite the only other user there is to test that) when starting kontact everything is fine, as long as the akregator-component is not activated; if it is - well, it just hangs, same symptoms KDE works fine otherwise (except for a crashing kwalletmanager on session end (bug #129329 probably))
I suspect this to be a duplicate of http://bugs.kde.org/show_bug.cgi?id=116482 Sometimes it crashes, sometimes it hangs. If it hangs, you should observe akregator hogging lots of memory, eventually leading to a freezing system. Move the *.mk4 files from .kde/share/apps/akregator/Archive to another directory and try again. Does it still freeze?
Uh right. Akregator consumes lots of CPU time. Memory usage (as top reports) quite steady at 1.5% (out of 1.5GiB) though (5 minutes running). Moving the *.mk4-files out of the way indeed fixes that. Didn't think it was related to that problem since strace didn't show anything (but forgot that strace didn't follow forks ...). Well, time to close this bug. Sorry for bothering.
duplicate of bug #116482