Launchpad has imported 56 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=184062.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-02-11T22:32:39+00:00 Exabyte-g wrote: Version: (using KDE 4.2.0) Compiler: GCC 4.3.1 OS: Linux Installed from: Gentoo Packages How I manage to reproduce this on my machine: Use kickoff menu, have a NFS mount (in my case, mounted before KDE started), unplug the network cable and wait. Plasma hangs after a few seconds-minutes and comes back to life when I plug my network cable back. Also, adding the kickoff plugin when the network cable is unplugged results in a immediate crash. I ran strace on plasma and the result when the hang appears is this: lstat("/dev/md1", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 1), ...}) = 0 lstat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 lstat("/dev/md2", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 2), ...}) = 0 lstat("/volatile", {st_mode=S_IFDIR|0755, st_size=56, ...}) = 0 lstat("/dev/md0", {st_mode=S_IFBLK|0640, st_rdev=makedev(9, 0), ...}) = 0 lstat("/boot", {st_mode=S_IFDIR|0755, st_size=1024, ...}) = 0 lstat("firebird:/home/ftp/pub", 0x7fffda66dec0) = -1 ENOENT (No such file or directory) lstat("/home/ftp/pub", <unfinished ...> So it is obviosly trying to lstat all devices *and* mountpoints. This leads to hangs, and I believe stating the nfs path is incorrect behaviour either way. Of course, such hangs in apps are expected (and wanted) when nfs goes away, but having the whole plasma hang is quite an unpleasant side effect, and likely possible to fix. :) Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/0 ------------------------------------------------------------------------ On 2009-02-27T10:02:34+00:00 Francis-mestdagh wrote: *** Bug 185552 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/1 ------------------------------------------------------------------------ On 2009-05-19T01:43:58+00:00 Jirik-0 wrote: I am confirming this. It is really annoying. This should not happen. KDE components should not have dependency on components like NFS. Can someone please fix it urgently. Environment: Debian Unstable, KDE 4.2.2 Problem: When NFS mounted and unplug cable plasma process reports "disk sleep". Any part of Plasma is not responsive. Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/2 ------------------------------------------------------------------------ On 2009-05-26T23:01:58+00:00 Arkadi-shishlov wrote: Same with CIFS mounts on Fedora: Plasma freezes when network mount is unavailable https://bugzilla.redhat.com/show_bug.cgi?id=491211 Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/3 ------------------------------------------------------------------------ On 2009-05-29T16:49:30+00:00 Dario Andres wrote: Have you tried removing the Kickoff menu and reproduce the NFS disconnection to test if it is indeed related to Kickoff or to another component? (I'm also thinking about the Device Manager; or the base lib for this: Solid) Thanks Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/4 ------------------------------------------------------------------------ On 2009-05-30T08:12:31+00:00 Jirik-0 wrote: If you umount the NFS export (umount /mnt/data -l) then everything becomes responsive again in about 1 minute. Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/5 ------------------------------------------------------------------------ On 2009-05-30T14:20:00+00:00 Exabyte-g wrote: (In reply to comment #4) > Have you tried removing the Kickoff menu and reproduce the NFS disconnection > to > test if it is indeed related to Kickoff or to another component? (I'm also > thinking about the Device Manager; or the base lib for this: Solid) > Thanks Yes, when there is no Kickoff menu the NFS disconnection doesn't lead to Plasma hang. There was some strange behaviour in some gadgets and apps, but I can't recall what it was, but the behaviour described in the report happens due to Kickoff. I don't claim that the root cause is Kickoff's code, though. But the "Computer" section in the menu is what most probably triggers it. To be clear what I mean by "some strange behaviour" above: Trying to open a folder containing a disconnected NFS mount with Dolphin is an example. Dolphin is responsive, but huge part of the files and folders in the folder simply aren't shown until NFS comes back. Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/6 ------------------------------------------------------------------------ On 2009-05-30T16:42:58+00:00 Dario Andres wrote: Thanks for the tests. Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/7 ------------------------------------------------------------------------ On 2009-06-20T18:47:20+00:00 Michal Witkowski wrote: Yes i can confirm the same behaviour with Arch Linux KDE 4.2.4. I've got two NFS shares mounted upon connecting to my home wireless server. Whenever I turn my wifi-switch off, plasma hangs. This doesn't happen when NFS shares are unmounted. I've also tested the case with a cable connection. Same story: when NFS shares are mounted, unplugging the cable causes plasma to freeze. With no NFS shares, everything works alright. Reply at: https://bugs.launchpad.net/kde-baseapps/+bug/406154/comments/8 ------------------------------------------------------------------------ On 2009-08-02T22:42:41+00:00 Dario Andres wrote: *** Bug 202242 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/13 ------------------------------------------------------------------------ On 2009-08-03T08:53:08+00:00 aseigo wrote: *** Bug 201897 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/14 ------------------------------------------------------------------------ On 2009-08-03T14:44:09+00:00 Dario Andres wrote: *** Bug 202271 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/15 ------------------------------------------------------------------------ On 2009-08-30T18:34:58+00:00 Michal Witkowski wrote: The bug is very much alive in KDE 4.3.0. In can be reproduces exactly as before (see comment #8). Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/16 ------------------------------------------------------------------------ On 2009-09-04T18:48:08+00:00 Jithin Emmanuel wrote: Why is this bug still unconfirmed? I am having this issue every time I plug my usb drive. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/18 ------------------------------------------------------------------------ On 2009-09-06T12:11:39+00:00 giaso wrote: I can confirm the bug is still alive in KDE 4.3.1 on kubuntu jaunty packages. I can reproduce it by the following steps (using kickoff as launcher): - Login as user A - Let network manager put up wireless connection and mount nfs share - Log out - Log in as user B - Plasma hangs on splash Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/19 ------------------------------------------------------------------------ On 2009-09-15T13:26:31+00:00 glesik wrote: *** This bug has been confirmed by popular vote. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/20 ------------------------------------------------------------------------ On 2009-09-15T14:27:08+00:00 Jithin Emmanuel wrote: The issue I had I think is kubuntu specific one. I moved to arch linux. Now its plasma is not freezing on mounting usb drive. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/21 ------------------------------------------------------------------------ On 2009-10-13T17:00:35+00:00 Jithin Emmanuel wrote: I can confirm that this issue with usb drive freezing plasma is because of 2.6.31 kernel. Noticed when 2.6.31 kernel was available in arch. Downgrading to 2.6.30 kernel fixed the issue. Is the problem with kde or kernel. Can any kde devs confirm? Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/25 ------------------------------------------------------------------------ On 2009-10-19T14:27:09+00:00 Pcgscrap wrote: This bug still exists in kdebase-workspace-4.3.1-9.fc10.i386 and is simple to reproduce, see following link below for steps. And https://bugzilla.redhat.com/show_bug.cgi?id=529373 shows another older report of same problem linked to it. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/26 ------------------------------------------------------------------------ On 2009-10-22T02:06:23+00:00 Sebastian Sauer wrote: Created attachment 37728 cd ~/path/to/source/of/kdebase && patch -p0<bug184062.diff && make install Is the hang gone with the attached patch bug184062.diff? Best way to test that is to have only the kickoff applet running and no other applet. Background; KDirWatch blocks :-/ Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/27 ------------------------------------------------------------------------ On 2009-10-22T02:47:47+00:00 Sebastian Sauer wrote: Created attachment 37729 updated patch Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/28 ------------------------------------------------------------------------ On 2009-11-07T15:48:33+00:00 Jithin Emmanuel wrote: Without the patch and kernel 2.6.32-rc6 fixes the issue for me. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/29 ------------------------------------------------------------------------ On 2009-12-07T15:17:02+00:00 Asraniel wrote: what is the status of this bug? what about the patch? can we get this fixed for 4.4 final? thank you (if the submitter of the patch does not have an svn account, consider uploading the patch to reviewboard.kde.org) Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/30 ------------------------------------------------------------------------ On 2009-12-08T04:55:54+00:00 Jirik-0 wrote: Can anyone increase this as the HIGH priority to fix. All my notebooks have got same issue. This is really annoying issue. More annoying is that nobody is trying to fix it. This issue goes from 4.1 release. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/31 ------------------------------------------------------------------------ On 2009-12-08T10:41:39+00:00 Asraniel wrote: problem is that there is no real maintainer for kickoff currently.. but i increased the priority Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/32 ------------------------------------------------------------------------ On 2009-12-08T10:49:20+00:00 Asraniel wrote: i forgot to mention, please test the proposed patch, i can commit it if needed, but somebody has to test it. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/33 ------------------------------------------------------------------------ On 2009-12-16T12:19:29+00:00 Asraniel wrote: if anybody cares about this patch, it has to be tested and submitted to the right people. please contact the plasma developers in IRC or on the plasma-devel mailing list. thank you Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/34 ------------------------------------------------------------------------ On 2009-12-16T13:13:51+00:00 sebas wrote: The patch looks wrong, porting from KDirWatch to QFileSystemWatcher is the wrong thing to do. KDirWatcher should simply not block, and that's the real cause of the problem. Now the question is "where does it block (when it shouldn't)?". Anyone who can reproduce the problem, please attach a debugger to your Plasma and tell us where it blocks. Those that have reported crashers, please supply a backtrace. The s/KDirWatch/QFileSystemWatcher workaround is unlikely to go in like this. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/35 ------------------------------------------------------------------------ On 2009-12-19T17:32:18+00:00 BRULE Herman wrote: I thinks I have the same bug here. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/36 ------------------------------------------------------------------------ On 2010-05-11T05:58:05+00:00 aseigo wrote: *** Bug 181323 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/37 ------------------------------------------------------------------------ On 2010-05-18T10:43:45+00:00 Asraniel wrote: Any work beeing done on this bug? having a patch (even if it is wrong) at least helps to identify the problem. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/38 ------------------------------------------------------------------------ On 2010-05-20T18:03:43+00:00 David Faure wrote: Well, the backtrace requested in comment #27 would be much more useful than a bad patch (we use KDirWatch everywhere else in KDE, so the problem would just move to somewhere else). But this is really odd, the patch is about the RecentDocuments directory which is something like $KDEHOME/share/apps/RecentDocuments/, and which contains only desktop files, this should be totally unrelated to NFS mounts. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/39 ------------------------------------------------------------------------ On 2010-05-22T01:11:30+00:00 aseigo wrote: *** Bug 194196 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/40 ------------------------------------------------------------------------ On 2010-05-22T01:11:34+00:00 aseigo wrote: *** Bug 197962 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/41 ------------------------------------------------------------------------ On 2010-05-22T01:11:40+00:00 aseigo wrote: *** Bug 235730 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/42 ------------------------------------------------------------------------ On 2010-05-22T01:11:43+00:00 aseigo wrote: *** Bug 236907 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/43 ------------------------------------------------------------------------ On 2010-05-22T08:38:04+00:00 Sebastian 'polrus' Turzanski wrote: As aaron already connected my bug report with this one I'd just like to add that the same kind of behaviour happens to me even though I don't use NFS neither samba disks mapped. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/44 ------------------------------------------------------------------------ On 2010-07-05T09:35:06+00:00 Squan wrote: If I shut down an autofs mounted device while a konsole sessions current working directory is still set on this device I experience freeze of all konsole instances. Is this the same bug or shall I file a new one? Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/45 ------------------------------------------------------------------------ On 2010-09-01T18:28:53+00:00 Raffaele Sgarro wrote: I'm on 4.5 and suffer from this bug, but it's a bit different. I use an USB wireless dongle to connect to my router, but some days the signal is very very weak and connection is dropped or is near to 0 (zero). Every time network is lost I get plasma-desktop freezes. I'm sure it's only a plasma bug because other apps work, either KDE apps (kate) or GNOME apps (gedit), Qt and gtk ones (amarok and firefox). Even KRunner starts and runs normally if I type Alt+F2, but plasma-desktop becomes unresponsive: the desktop doesn't respond to mouse clicks, neither the panel. Also, the UI doesn't get updated (eg when I hover workspace or taskbar or kickoff icon). I don't know how to attach information, but I see this bug is 2 years old and since it's very very annoying I think you should set its priority to HIGH and fix it as soon as possible, because it makes it impossible to use the box 'til the network is back I love KDE but this bug makes me waste hours, waiting for the taskbar to get my click and change the application in foreground, just to do a copy and paste. Please, fix it Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/46 ------------------------------------------------------------------------ On 2010-09-04T18:51:25+00:00 Raffaele Sgarro wrote: http://pastebin.com/GPAQFCmZ Backtrace of plasma-desktop when freezes Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/47 ------------------------------------------------------------------------ On 2010-09-04T19:47:06+00:00 aseigo wrote: Raffaele: your backtrace points to a different issue, in particular a python based weather applet that is doing its own network fetching; if you remove that python weather widget, do things go back to normal? Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/48 ------------------------------------------------------------------------ On 2010-09-04T20:07:31+00:00 Raffaele Sgarro wrote: I think they were related problem because I didn't think that a misimplemented script could lead to whole plasma freezes :/ Anyway I have removed the plasmoid and I am seeing what happens with normal usage Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/49 ------------------------------------------------------------------------ On 2010-09-13T22:35:10+00:00 Björn Ruberg wrote: *** Bug 161205 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/50 ------------------------------------------------------------------------ On 2010-09-16T00:23:40+00:00 Björn Ruberg wrote: I'm trying to investigate this and get a backtrace - or maybe fix it. But I cannot reproduce the problem. I see a short block of plasma when an USB device is attached. But this was too short for me to find a blocking code. I'm trying to reproduce the nfs problems in KDE 4.4 and 4.6 trunk. But I wasn't lucky. I mounted an nfs folder of another laptop - killed its wifi - and plasma was running flawlessly. The only block I can observe is dolphin which blocks if I add an nfs folder to its places. Can anyone help me finding a way to reproduce this? Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/51 ------------------------------------------------------------------------ On 2010-09-16T08:40:28+00:00 BRULE Herman wrote: You can try freeze udev process via gdb attach, seem work here. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/52 ------------------------------------------------------------------------ On 2010-09-16T15:13:38+00:00 Björn Ruberg wrote: No - no luck. Can it be that hard to freeze plasma? :) Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/53 ------------------------------------------------------------------------ On 2011-02-06T15:22:23+00:00 Dplater wrote: This bug is still here in 4.6, took a lot to track down until somebody on the opensuse-kde list pointed me here. In my case the vista machine I've mounted cifs shares from shuts down and the kick off menu becomes unusable. I click, it opens but from then on the panel and all it's widgets freeze, after about 30 secs the kickoff retracts and the panel becomes usable but I can only run apps from the "run command" or command line. The kick off menu is unusable until I unmount the shares as root. Anything I can gdb? This should be easily reproducible though. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/54 ------------------------------------------------------------------------ On 2011-05-28T23:21:49+00:00 Denis Kniazhev wrote: I use Kubuntu 11.04 64-bit with KDE 4.6.2, and this bug is 100% reproducible for me. I use small 3-d party tool to connect to l2tp VPN (http://code.google.com/p/vpnpptp/). Whenever the VPN drops, or when I hit "Disconnect" button, plasma freezes hardly - no application launching, no widgets activity. I still can use ALT+F2 to get Konsole (Dolphin can be started too, but is very slow) to do "sudo reboot" - this is the only way I'm aware of to get back to working machine. Command "kbuildsycoca4 && pkill plasma && kstart plasma-desktop" doesn't work for me - plasma gets killed but fails to start. I should mention that I have experienced this same bug when disconnecting my 3G modem. I have seen this 3 or 4 times, but it isn't as stable as with l2tp vpn. As someone suggested, I've ran "sudo gdb --pid `pidof plasma-desktop`" , then 'freezed' plasma, then ran "bt" I'm not sure this is the right way of dyagnozing, but here's what I've got: #0 0x00007f4a605ecf03 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f4a54fcf104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f4a54fcf639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f4a5d7fb3ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #4 0x00007f4a5cc38dfe in ?? () from /usr/lib/libQtGui.so.4 #5 0x00007f4a5d7cf882 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #6 0x00007f4a5d7cfabc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #7 0x00007f4a5d7d3ecb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #8 0x00007f4a608e6897 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so #9 0x00007f4a60532eff in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000400669 in _start () If I can provide any more detailed stacktraces, please let me know - this bug is really annoying and I will provide any help with it. Unfortunatly I'm java programmer, not C++, otherwise I would volunteer with the fix. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/55 ------------------------------------------------------------------------ On 2011-08-11T09:26:29+00:00 Bugs-kde-org wrote: I have the same "bug" when I use the "Application Launcher Menu" (probably named Kickoff if I look a the BT) and within Dolphin. I think is not fixed in 2.6.32+ like Emmaneul is telling ------- Comment #21 From Jithin Emmanuel 2009-11-07 15:48:33 (-) [reply] ------- Without the patch and kernel 2.6.32-rc6 fixes the issue for me. I use kernel 2.6.38 and still hang I use a cifs share over VPN. $ mount ... //apodc-02/utilisateurs/ on /mnt/smb/intranet type cifs (rw,mand) ... If the remote server is unavailable or the VPN is down or i lost the network link, the "Application Launcher Menu Settings" freeze on fisrt access to "K" start menu for 300seconds I must wait 300 sec for the kernel disable the cifs share : Aug 10 17:05:08 PC-TEC-12 kernel: [26029.864385] CIFS VFS: Server apodc-02 has not responded in 300 seconds. Reconnecting... "umount -f" failed ~# umount -f /mnt/smb/intranet umount2: Device or resource busy umount: /mnt/smb/intranet: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) umount2: Device or resource busy Reproductible 100% Distibution Kubuntu fresh new install natty 11.04 amd64 dpkg -l | grep plasma-desktop ii plasma-desktop 4:4.6.2a-0ubuntu5.1 Package up-to-date apt-cache policy plasma-desktop plasma-desktop: Installé : 4:4.6.2a-0ubuntu5.1 Candidat : 4:4.6.2a-0ubuntu5.1 Table de version : *** 4:4.6.2a-0ubuntu5.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages 100 /var/lib/dpkg/status dpkg -l | grep dolphin ii dolphin 4:4.6.2-0ubuntu1 root@PC-TEC-12:~# apt-cache policy dolphin dolphin: Installé : 4:4.6.2-0ubuntu1 Candidat : 4:4.6.2-0ubuntu1 Table de version : *** 4:4.6.2-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages 100 /var/lib/dpkg/status # uname -a Linux PC-TEC-12 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Workaround: If I switch "Application Launcher Menu Settings" to old style menu it not hang anymore: -> unlock widget -> right click on "K" start menu -> "Switch to Classic Menu Style" gdb hand for a while when attaching to process: ( 300sec ) .. then I can make a BT for plasma or dolphin .. see attached : kickoff_bt.txt and kickoff_bt.txt Maybe it's to late because of un-hang after 300sec .. Same behaviour with Dolphin when the share is unavailable, Dolphin hang for 300secs Dolphin suffer from the same hang while disconnecting network because dolphin list all local disks and shares mounted .. Dolphin hang until kernel disconnect the unavailable share : CIFS VFS: Server apodc-02 has not responded in 300 seconds. Reconnecting... Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/56 ------------------------------------------------------------------------ On 2011-08-11T09:27:12+00:00 Bugs-kde-org wrote: Created attachment 62744 Back trace from kickoff Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/57 ------------------------------------------------------------------------ On 2011-08-11T09:27:47+00:00 Bugs-kde-org wrote: Created attachment 62745 dolphin_bt.txt Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/58 ------------------------------------------------------------------------ On 2011-10-29T09:59:24+00:00 Bugs-kde-org2 wrote: I experience the same but it isn't just limited to nfs/cifs... also sshfs mounts that can't be accessed because of network problems. Plasma / Dolphin also stalls there for some time. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/60 ------------------------------------------------------------------------ On 2011-10-29T10:00:22+00:00 Bugs-kde-org2 wrote: Btw: Using Kubuntu Oneiric 64bit with Kubuntu Team PPA Platform Version 4.7.2 (4.7.2) Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/61 ------------------------------------------------------------------------ On 2011-12-03T19:49:42+00:00 aseigo wrote: the kickoff issue in comment #46 and #50 is something different, and i fixed it today by putting the disk stating code in a thread so it won't block. (worst case scenario: the thread just block indefinitely). dolphin should do similarly. the KDirLister freezing issue is the real remaining issue here and until someone can provide a backtrace (as Phillippe did in comment #50 for the kickoff issue: thanks!) it will be very hard to know what to do with this. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/62 ------------------------------------------------------------------------ On 2012-01-27T10:39:18+00:00 Lamarque wrote: *** Bug 292536 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/63 ------------------------------------------------------------------------ On 2012-05-09T04:37:00+00:00 DeMus wrote: Now it is May 2012 and this bug is still there. I use Kubuntu 12.04 with KDE 4.8.2 and kernel 3.2.0 and still experience the same. Why isn't this a major priority for the software guys (and girls)? I mean, hanging systems are not very user-friendly, especially when they hang since at least 2009 already. Please fix this issue a.s.a.p. Reply at: https://bugs.launchpad.net/kde- baseapps/+bug/406154/comments/64 ** Bug watch added: Red Hat Bugzilla #491211 https://bugzilla.redhat.com/show_bug.cgi?id=491211 ** Bug watch added: Red Hat Bugzilla #529373 https://bugzilla.redhat.com/show_bug.cgi?id=529373 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/406154 Title: [karmic] plasma panel freezes for a few seconds when opening a usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/406154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
