Dolphin Version 2.2 Unter KDE 4.10.3 .8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Dolphin takes more than 10 seconds to start on fast laptop i7-3 I did like suggested in an other post , removed all "places" , but not "Geräte", to prevent long presearch . I even purged dolphin, removed all .config files and reinstalled. No changes . (Test with Thunar - running fast.) . When dolphin is up it behaves "normal" , although I feel , it was faster before this problem came up. Happens after upgrading Kubuntu Kernel and KDE from ??? . Had contact to Frank with the problem of freezing - that is solved. Takes the long time also when starting from terminal , no errors Reproducible: Always Steps to Reproduce: 1. Start Dolphin - wait 10-15 seconds 2. 3. Expected Results: Before that last upgrade dolphin was fast and I like get that again.
If I can track the problem down, I like to help. Give me some debug instructions, please Waldi
Thanks for the bug report. What exactly do you mean with "removed all places"? Did you disable the places panel? Simply removing some "places" is unlikely to change anything. I would try to run Dolphin in gdb. In a terminal, enter gdb dolphin At the gdb prompt, enter "run". When it's frozen, press Ctrl+Z. When the gdb prompt reappears, enter "thread apply all backtrace" and attach or paste the output here.
Dear Frank, first thank you for answering so fast. Yes , I removed all Places in the Sidepanel, so there are now no placest at all .The sidepanel exists with entries for "Geräte" . Wenn running "gdb dolphin " and then "run" , Dolphin starts after waiting the 10-20 seconds. I dont understand what you mean with gdb freezing . Should the prompt appear while dolphin is running ? the prompt only reappears when stoppin dolphin or pressing CTL+Z. Stopping dolphin and thread apply all backtrace generates no output, while CTRL+Z gives the following: ############################################################ waldi@waldi-Pc:~$ gdb dolphin GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/dolphin...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffdc8e0700 (LWP 4847)] [New Thread 0x7fffd796a700 (LWP 4848)] [New Thread 0x7fffd66c1700 (LWP 4857)] ^Z Program received signal SIGTSTP, Stopped (user). 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread apply all backtrace Thread 4 (Thread 0x7fffd66c1700 (LWP 4857)): #0 0x00007ffff7864233 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff36e1132 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fffd796a700 (LWP 4848)): #0 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef09c1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef09c304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff3731036 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff370138f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff3701618 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007ffff3603410 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff36e2edf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fffdc8e0700 (LWP 4847)): #0 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef09c1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef09c304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff3731036 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff370138f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff3701618 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007ffff3603410 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff36e2edf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7ffff7fa87c0 (LWP 4822)): ---Type <return> to continue, or q <return> to quit--- ############################## Thanks Waldi (auf englisch bleiben ? ) 2013/5/25 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report. What exactly do you mean with "removed all > places"? > Did you disable the places panel? Simply removing some "places" is > unlikely to > change anything. > > I would try to run Dolphin in gdb. In a terminal, enter > > gdb dolphin > > At the gdb prompt, enter "run". When it's frozen, press Ctrl+Z. When the > gdb > prompt reappears, enter "thread apply all backtrace" > and attach or paste the output here. > > -- > You are receiving this mail because: > You reported the bug. >
(In reply to comment #3) > Yes , I removed all Places in the > Sidepanel, so there are now no placest at all .The sidepanel exists with > entries for "Geräte" . Doing this, but keeping the panel with the devices enabled is not expected to have any effect at all. Any slowness on startup which is related to the Places Panel is probably due to delays when trying to access the devices. The only way to work around that is to hide the panel, then close Dolphin and re-open. > Wenn running "gdb dolphin " and then "run" , Dolphin starts after waiting > the 10-20 seconds. I dont understand what you mean with gdb freezing . > Should the prompt appear while dolphin is running ? the prompt only > reappears when stoppin dolphin or pressing CTL+Z. Yes, the prompt should only appear when pressing Ctrl+Z or terminating the application. > Thread 1 (Thread 0x7ffff7fa87c0 (LWP 4822)): > ---Type <return> to continue, or q <return> to quit--- This is exactly the point where the interesting part starts. Please repeat the procedure and press "Return" at this point. > (auf englisch bleiben ? ) Yes. All communacation at bugs.kde.org should be in English. One of the reasons is that it might be necessary to forward the report to other people. I think that your problem is most likely not a Dolphin bug, so we probably have to re-assign the report if you manage to gather any useful information.
Here we are again: waldi@waldi-Pc:~$ gdb dolphin GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/dolphin...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffdc8e0700 (LWP 28057)] [New Thread 0x7fffd796a700 (LWP 28058)] [New Thread 0x7fffd66c1700 (LWP 28064)] ^Z Program received signal SIGTSTP, Stopped (user). 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) (gdb) thread apply all backtrace Thread 4 (Thread 0x7fffd66c1700 (LWP 28064)): #0 0x00007ffff7864233 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff36e1132 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fffd796a700 (LWP 28058)): #0 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef09c1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef09c304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff3731036 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff370138f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff3701618 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007ffff3603410 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff36e2edf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fffdc8e0700 (LWP 28057)): #0 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef09c1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef09c304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff3731036 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff370138f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x00007ffff3701618 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007ffff3603410 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff36e2edf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff3605bec in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x00007fffef56ef8e in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007ffff786be1d in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7ffff7fa87c0 (LWP 28036)): ---Type <return> to continue, or q <return> to quit--- #0 0x00007ffff785f3cd in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007fffef09c1dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffef09c304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff3731016 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff41911ae in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #5 0x00007ffff370138f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x00007ffff3701618 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x00007ffff3706cf6 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff7b897b7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so #9 0x00007ffff7793ea5 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000400701 in _start () (gdb) 2013/5/25 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report. What exactly do you mean with "removed all > places"? > Did you disable the places panel? Simply removing some "places" is > unlikely to > change anything. > > I would try to run Dolphin in gdb. In a terminal, enter > > gdb dolphin > > At the gdb prompt, enter "run". When it's frozen, press Ctrl+Z. When the > gdb > prompt reappears, enter "thread apply all backtrace" > and attach or paste the output here. > > -- > You are receiving this mail because: > You reported the bug. >
In Addition, I think you maybe right that the problem is not dolphin (dolphin wasn't upgraded I think). Do you think it would be of any use for you to try the same with a "Live_Cd" eg. to make sure thats a UBUNTU KDE Problem ? Ca you recommend something for that ? Waldi 2013/5/25 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report. What exactly do you mean with "removed all > places"? > Did you disable the places panel? Simply removing some "places" is > unlikely to > change anything. > > I would try to run Dolphin in gdb. In a terminal, enter > > gdb dolphin > > At the gdb prompt, enter "run". When it's frozen, press Ctrl+Z. When the > gdb > prompt reappears, enter "thread apply all backtrace" > and attach or paste the output here. > > -- > You are receiving this mail because: > You reported the bug. >
Thanks, but the backtrace shows no signs of a freeze. It looks like the event loop is running normally. I don't have any other ideas how to debug a problem that I cannot reproduce.
Does Dolphin only freeze on startup or also when you go to another directory?
I would not use the word freezing, because dolphin comes up after 10-20 seconds. After that it behaves more normal - as I said, no so fast as I am was used, I can see some icons changing their image when switching to another directory. But that's only a short time , up to 1 second only. I could live with that. I get the feeling , that after some switches odf directories/places , its going even faster (caching something or just psychologically ;-) ) Thanks for your answer Waldi (H.Herwig) 2013/5/27 Emmanuel Pescosta <emmanuelpescosta099@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > Emmanuel Pescosta <emmanuelpescosta099@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| > |emmanuelpescosta099@gmail.c > | |om > > --- Comment #8 from Emmanuel Pescosta <emmanuelpescosta099@gmail.com> --- > Does Dolphin only freeze on startup or also when you go to another > directory? > > -- > You are receiving this mail because: > You reported the bug. >
Does disabling the Places Panel help (see comment 4)?
No, disabling the panel doesn't change anything. I disabled all side panels now. 2013/5/28 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #10 from Frank Reininghaus <frank78ac@googlemail.com> --- > Does disabling the Places Panel help (see comment 4)? > > -- > You are receiving this mail because: > You reported the bug. >
Dear Frank, some additional information. I installed some more filemanager just to see if my filesystem may be the problem. So xfm , mc and konqueror have been installed. xfm, mc (and as written former times thunar ) work just fine. Konqueror startet fast with an empty page , but then shows the first directories also with the same delay as dolphin. In the address line a can see very fast autofill of possible directories, but after selecting one, the delay starts . As I know had dolphin and konquerror close connections (same origin maybe ? ). Maybe this information is usefull. In addition this morning came some kdelib-upgrades, but nothing changed. regards Waldi 2013/5/28 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #10 from Frank Reininghaus <frank78ac@googlemail.com> --- > Does disabling the Places Panel help (see comment 4)? > > -- > You are receiving this mail because: > You reported the bug. >
Thanks for the new information. Konqueror and Dolphin share a lot of file-management related code indeed. I think, however, that the cause of the problems might actually have something to do with kdelibs. Does Konqueror react to mouse clicks (e.g., in the menu) while it's loading the directory?
No, it doesn't . First I thought, it would going to freeze totally - because there were no reaction on mouse-clicks or moving. I can share the feeling about kdelibs, indeed, this all happens after "upgrading" KDE. 2013/5/29 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #13 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the new information. Konqueror and Dolphin share a lot of > file-management related code indeed. I think, however, that the cause of > the > problems might actually have something to do with kdelibs. > > Does Konqueror react to mouse clicks (e.g., in the menu) while it's > loading the > directory? > > -- > You are receiving this mail because: > You reported the bug. >
Hallo Frank, mit dem heutigen upgrade meines Kubuntu läuft dolphin wieder einwandfrei. Ca. 187 packages. After upgrading my Kubuntu today, dolphin works fine - fast - again. Do you need any dpkg list or something for your information ? Greetings Waldi (herbert Herwig) 2013/5/29 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #13 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the new information. Konqueror and Dolphin share a lot of > file-management related code indeed. I think, however, that the cause of > the > problems might actually have something to do with kdelibs. > > Does Konqueror react to mouse clicks (e.g., in the menu) while it's > loading the > directory? > > -- > You are receiving this mail because: > You reported the bug. >
Thanks for the feedback - good to know that it works now! (In reply to comment #15) > Do you need any dpkg list or something for your information ? No, thanks. To be honest, I wouldn't know what to do with it. If it's a Kubuntu specific issue, we cannot do anything about it anyway.
Dear Frank, just to give you a feedback. In the meantime dolphin had started again with a long waittime. But just now I got rid of akonadi (will not use any PIM-function) and helas ! Dolphin starts fast. So maybe you were right, it is/was an issue of Kubuntu/KDE Greetings Waldi 2013/6/7 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |WORKSFORME > > --- Comment #16 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the feedback - good to know that it works now! > > (In reply to comment #15) > > Do you need any dpkg list or something for your information ? > > No, thanks. To be honest, I wouldn't know what to do with it. If it's a > Kubuntu > specific issue, we cannot do anything about it anyway. > > -- > You are receiving this mail because: > You reported the bug. >
Thanks for the update! I still have no idea what the actual problem was, but it's good to know that Dolphin starts faster for you now.
Dear Frank, one normally gets only complaints. I like to tell you, that after going to KDE 4.11. dolphin ist starting faster as ever. Fine. Best regards h.Herwig (waldi) 2013/9/2 Frank Reininghaus <frank78ac@googlemail.com> > https://bugs.kde.org/show_bug.cgi?id=320262 > > --- Comment #18 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the update! I still have no idea what the actual problem was, > but > it's good to know that Dolphin starts faster for you now. > > -- > You are receiving this mail because: > You reported the bug. >
I'm glad to hear that! Thanks for letting us know.