Bug 252342 - Konqueror freezes on opening files/dirs and copying/moving them
Summary: Konqueror freezes on opening files/dirs and copying/moving them
Status: RESOLVED DUPLICATE of bug 232054
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.5.1
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 252343 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-09-25 15:25 UTC by ultr
Modified: 2010-09-25 23:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description ultr 2010-09-25 15:25:15 UTC 
Version:           4.5.1 (using KDE 4.5.1) 
OS:                Linux

Konqueror freezes on:
1) opening files/dirs
2) copying/moving them from one window to another (before displaying overwrite dialog)

Running another instance of Konqueror instantly unfreezes the previous window.

It also unfreezes itself automatically after 10-20 seconds.

Happens randomly, but very often.

Reproducible: Sometimes
Comment 1 Frank Reininghaus 2010-09-25 23:13:08 UTC 
Thanks for the bug report. Could you try if disabling tool tips and/or disabling Nepomuk helps? This is most likely an issue in the D-Bus library which leads to freezes and crashes (see, e.g., bug 226725). It's fixed in D-Bus 1.3.1 and later.
Comment 2 ultr 2010-09-25 23:28:24 UTC 
Disabling tool tips seems to eliminate the problem. Thanks.

And I had Nepomuk disabled already. Enabling it does not change anything.

My libdbus version is 1.2.24 (Debian testing).
Comment 3 Frank Reininghaus 2010-09-25 23:41:08 UTC 
Thanks for the quick update. I'm pretty sure that this is the same D-Bus issue that causes bug 226725/bug 232054 then. Updating to D-Bus 1.3.1 or 1.4.0 should fix it.

*** This bug has been marked as a duplicate of bug 232054 ***
Comment 4 Frank Reininghaus 2010-09-25 23:50:48 UTC 
*** Bug 252343 has been marked as a duplicate of this bug. ***