Registered Member
|
Hello!
I am using KDE 4.11.5 inside Ubuntu 13.10 and there is a 3+ second lag whenever I start Dolphin. This is an SSD so it should be instant (Konqueror, Okular, Konsole, etc. all start up instantly). If I start from a konsole I get this output
I get a very similar output when I start gwenview, which also lags 3+ seconds. A search around the web returns several forums where users have had this issue across several distros, but no solution. Any ideas? I appreciate any help! Some links to posts I've read of users complaining Dolphin is slow---they have output similar to mine form the Konsole: http://forums.debian.net/viewtopic.php?f=10&t=109219 (attributed to issue with Debian's version of Akonadi) http://forum.kde.org/viewtopic.php?f=224&t=110048 (says there is a patch for Arch) http://forum.manjaro.org/index.php?topic=2182.0 (maybe a Udisk2 issue?) http://chakra-project.org/bbs/viewtopic.php?pid=76338 (suggests samba or upower might be the problem; I don't have samba) https://plus.google.com/+SwapnilBhartiya/posts/QXpxfTzLHYb |
Administrator
|
Other than Dolphin and Gwenview, do any other applications start slowly?
Does the file picker (File > Open in any KDE application) also open slowly (at least at first)?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Yes, actually, it does take a second or two (by contrast FIle > Open in Gtk apps is instant). And in particular when I start Okular from the terminal and then do File > Open I get the same error messages as when I start dolphin. As a bonus, I get this from Okular (after it prints out the messages above)
Same for Gwenview. For Konqueror and Kate, for instance, File > Open only prints the message I get when I start up Dolphin. This is from konqueror
After starting it in the konsole and doing File > Open. Any ideas? What can i do to debug? Many thanks! |
Administrator
|
Do subsequent opens of the file picker in the same application have the same performance delay and debug messages?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
The lag is reduced when I do file > open multiple times. I don't see the messages.
I tried upgrading to KDE 4.12.2 today via Kubuntu backports. The lag has been reduced by half (so dolphin takes just over a 1 to 1.5 seconds to start) and the messages no longer appear at all. I still find this lag annoying since Nautilus starts faster and the file picker in gtk apps is still instant vs 1+ seconds...same for starting okular / konqueror / kate / etc. Instant vs 1+ second lag (it bugs me because I only see the lag for Dolphin, Gwenview, and the File > Open; by the way, several things I do in dolphin have some type of lag: Split view and open tab lag for an instant before working, for example). |
Administrator
|
My guess is it is either:
1) Enumerating Samba shares 2) Enumerating hardware devices This is why subsequent opens of the file dialog are much quicker - as these details are cached. I'm not sure how to debug any further however. You could try running "kdebugdialog" and enabling everything - then running Dolphin and see what is output. Something relevant might be printed with all debug output enabled.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Moderator
|
To find out more about where in the code of an application or library the cause of the slowness is, you can also follow
http://community.kde.org/Dolphin/FAQ/Freeze The backtrace might provide some hints about what's going wrong. Doing this for Dolphin might not be easy in your case because it's slow on startup. Maybe it's easier to do this with an application that freezes while opening the file dialog. |
Registered Member
|
Thanks for the suggestions! Maybe enumerating shares / devices is the problem. With all the options enabled on kdebugdialog, I see this output on Dolphin startup / File > Open
That happens on every application. There are messages around it, of course, but they get repeated on subsequent File > Open and the messages above don't. So, I don't use Samba and I never actually installed it. How do I prevent Dolphin / etc from trying to enumerate Samba drives? At a glance the help online is about doing the opposite (i.e. mounting Samba shares, which I don't want to do). |
Administrator
|
I'm afraid, as far as I can tell there isn't a way to stop Dolphin / KDE applications from attempting to enumerate local Samba / NFS shares - part of the code checks for each directory whether it has been shared.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Is there a way to file this as a bug? I don't understand how this is acceptable. Nautilus startup and most other applications' startup is instant. File Exploer on windows is also instant. But Dolphin lags and that's just normal? Or, is there a way to re-install dolphin without reinstalling all of KDE? If so, I could try to figure out if it's somehitng I did. Right now trying to uninstall dolphin uninstalls all of KDE. |
Moderator
|
Yes, but please follow my earlier comment first to find out where the bug is, and then file it for the correct product (you can ask for guidance here, of course). If you file this as a Dolphin bug, all I can do is to say "Sorry, but I cannot reproduce the problem", and nothing will happen because I don't have a clue what the source of the problem is. It has most likely nothing to do with Dolphin itself.
Please try to keep the discussion productive. We obviously cannot reproduce this problem, and everyone here is spending their free time to solve your problem. |
Registered Member
|
Indeed. I sincerely apologize for my demeanor and appreciate your response. My frustration got the better of me here. As for the debugging, I was initially ambivalent as to whether to follow the instructions for the freeze since Dolphin doesn't freeze. Further, I didn't quite know how to interpret this output. But I follow the instructions and this is what the output looks like after
Many thanks again! |
Administrator
|
That backtrace seems to be missing threads 1, 2 and 3 unfortunately - can you please try and regenerate it?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
That's my bad. Here is the full backtrace. I start dolphin, open a new tab, open a new dolphin window, and then stop gdb.
|
Moderator
|
The backtrace shows no signs of a freeze. But maybe that is to be expected because you said that Dolphin is slow on startup, and the backtrace was generated after opening a new window (which is not slow AFAIU).
The backtrace is only helpful if it shows the state of the application while it's frozen. As I said in viewtopic.php?f=223&t=119733&p=303334#p302572, that might be easier to do by debugging an application that's frozen while opening a file dialog. The idea would be: open application in GDB, then open the file dialog, then immediately go to the gdb window and press Ctrl+Z. |
Registered users: Bing [Bot], gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]