This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Dolphin start-up very slow

Tags: None
(comma "," separated)
mcaceres
Registered Member
Posts
100
Karma
0

Dolphin start-up very slow

Tue Feb 18, 2014 4:22 am
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

Code: Select all
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SU_208DB_R93W6YVD600MPK" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "Device" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "Device" does not exist


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
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Dolphin start-up very slow

Tue Feb 18, 2014 11:44 pm
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]
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Wed Feb 19, 2014 2:43 am
bcooksley wrote: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)?


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)

Code: Select all
okular(16282) KSambaSharePrivate::isSambaInstalled: Samba is not installed!
okular(16282) KSambaSharePrivate::isSambaInstalled: Samba is not installed!


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

Code: Select all
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
konqueror(7986)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "searchproviders/wikit.desktop" not found
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "New &Window" under id 2
void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&New Tab" under id 3
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SU_208DB_R93W6YVD600MPK" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/Samsung_SSD_840_Series_S14JNEACC18108Z" : property "Device" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/TOSHIBA_MQ01ABD100_82NCFG1YS" : property "Device" does not exist


After starting it in the konsole and doing File > Open. Any ideas? What can i do to debug? Many thanks!
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Dolphin start-up very slow

Wed Feb 19, 2014 10:57 pm
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]
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Thu Feb 20, 2014 5:40 am
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).
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Dolphin start-up very slow

Thu Feb 20, 2014 6:56 am
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]
freininghaus
Moderator
Posts
224
Karma
1
OS

Re: Dolphin start-up very slow

Thu Feb 20, 2014 11:56 am
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.
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Thu Feb 20, 2014 4:40 pm
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

Code: Select all
konqueror(25544) KSambaSharePrivate::isSambaInstalled: Samba is not installed!
konqueror(25544) KSambaSharePrivate::isSambaInstalled: Samba is not installed!
konqueror(25544)/kio KNFSShare::KNFSSharePrivate::findExportsFile: Could not find exports file! /etc/exports doesn't exist. Configure it in share/config/knfsshare, [General], exportsFile=....


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).
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Dolphin start-up very slow

Sat Feb 22, 2014 2:52 am
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]
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Wed Feb 26, 2014 4:35 pm
bcooksley wrote: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.


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.
freininghaus
Moderator
Posts
224
Karma
1
OS

Re: Dolphin start-up very slow

Thu Feb 27, 2014 7:30 am
mcaceres wrote:Is there a way to file this as a bug?

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.

mcaceres wrote: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?

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.
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Fri Feb 28, 2014 1:03 am
freininghaus wrote: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.


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
Code: Select all
thread apply all backtrace


Code: Select all
Thread 8 (Thread 0x7fffcafee700 (LWP 28659)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffb80008c0, flags=...)
    at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffcafeddb0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffcafeddb0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0x14185b0) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffcafee700) at pthread_create.c:311
#9  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 7 (Thread 0x7fffcbc14700 (LWP 28654)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffc00269d0, flags=...)
    at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffcbc13db0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffcbc13db0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0x133f520) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffcbc14700) at pthread_create.c:311
#9  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7fffd9122700 (LWP 28643)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712af6 in QEventDispatcherGlib::processEvents (this=0x7fffc40008c0, flags=...)
    at kernel/qeventdispatcher_glib.cpp:427
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffd9121d70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffd9121d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=this@entry=0xac94a0) at thread/qthread.cpp:537
#7  0x00007ffff36c5a33 in QInotifyFileSystemWatcherEngine::run (this=0xac94a0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ffff35e331f in QThreadPrivate::start (arg=0xac94a0) at thread/qthread_unix.cpp:349
#9  0x00007fffef769f6e in start_thread (arg=0x7fffd9122700) at pthread_create.c:311
#10 0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fffd9f92700 (LWP 28642)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffd00008c0, flags=...)
    at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffd9f91db0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffd9f91db0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0xac5cf0) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffd9f92700) at pthread_create.c:311


Many thanks again!
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: Dolphin start-up very slow

Fri Feb 28, 2014 8:32 am
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]
mcaceres
Registered Member
Posts
100
Karma
0

Re: Dolphin start-up very slow

Fri Feb 28, 2014 10:42 am
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.

Code: Select all
Thread 9 (Thread 0x7fffcb291700 (LWP 9096)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffb8003fe0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffcb290db0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffcb290db0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0x13ee710) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffcb291700) at pthread_create.c:311
#9  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 7 (Thread 0x7fffcbcae700 (LWP 9093)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffc00269d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffcbcaddb0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffcbcaddb0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0x1324920) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffcbcae700) at pthread_create.c:311
#9  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 5 (Thread 0x7fffd9122700 (LWP 9086)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712af6 in QEventDispatcherGlib::processEvents (this=0x7fffc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffd9121d70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffd9121d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=this@entry=0xabe1b0) at thread/qthread.cpp:537
#7  0x00007ffff36c5a33 in QInotifyFileSystemWatcherEngine::run (this=0xabe1b0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ffff35e331f in QThreadPrivate::start (arg=0xabe1b0) at thread/qthread_unix.cpp:349
#9  0x00007fffef769f6e in start_thread (arg=0x7fffd9122700) at pthread_create.c:311
#10 0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fffd9f92700 (LWP 9085)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x7fffd00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffd9f91db0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffd9f91db0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#7  0x00007ffff35e331f in QThreadPrivate::start (arg=0x73d220) at thread/qthread_unix.cpp:349
#8  0x00007fffef769f6e in start_thread (arg=0x7fffd9f92700) at pthread_create.c:311
#9  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fffda8f1700 (LWP 9084)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712af6 in QEventDispatcherGlib::processEvents (this=0x7fffcc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffda8f0d70, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffda8f0d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ffff35e0c4f in QThread::exec (this=this@entry=0x9b13a0) at thread/qthread.cpp:537
#7  0x00007ffff36c5a33 in QInotifyFileSystemWatcherEngine::run (this=0x9b13a0) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007ffff35e331f in QThreadPrivate::start (arg=0x9b13a0) at thread/qthread_unix.cpp:349
#9  0x00007fffef769f6e in start_thread (arg=0x7fffda8f1700) at pthread_create.c:311
#10 0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fffdb436700 (LWP 9081)):
#0  0x00007ffff7860de3 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffff36c2371 in QProcessManager::run (this=0x7ffff3a4c540 <processManager()::processManager>) at io/qprocess_unix.cpp:270
#2  0x00007ffff35e331f in QThreadPrivate::start (arg=0x7ffff3a4c540 <processManager()::processManager>) at thread/qthread_unix.cpp:349
#3  0x00007fffef769f6e in start_thread (arg=0x7fffdb436700) at pthread_create.c:311
#4  0x00007ffff78689cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7ffff7f947c0 (LWP 9077)):
#0  0x00007ffff785bf7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fffef2916a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fffef2917ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff3712ad5 in QEventDispatcherGlib::processEvents (this=0x613a60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007ffff4179cb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#5  0x00007ffff36e430f in QEventLoop::processEvents (this=this@entry=0x7fffffffdb70, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007ffff36e4605 in QEventLoop::exec (this=this@entry=0x7fffffffdb70, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007ffff36e9deb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#8  0x00007ffff7b86ee7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so
#9  0x00007ffff778fde5 in __libc_start_main (main=0x4006d0, argc=1, ubp_av=0x7fffffffddd8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffddc8) at libc-start.c:260
#10 0x00000000004006fe in _start ()
freininghaus
Moderator
Posts
224
Karma
1
OS

Re: Dolphin start-up very slow

Fri Feb 28, 2014 1:51 pm
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.


Bookmarks



Who is online

Registered users: Bing [Bot], gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]