Version: 1.7 (using KDE 4.7.2) OS: Linux To open the KDE menu I click the K in the bottom-left corner of the screen. The menu pops open and freezes. This has happened maybe 5 times since I installed Kubuntu11.10 2 days ago. After maybe a minute it is responsive again and I can contnue to do what I want to do. This time however it did not. I had several programs open, including Google-Chrome, Amarok, Thunderbird and Dolphin. Chrome was fully responsive and I could stop the program the normal way, just as Thunderbird. The buttons in the lower panel however were not removed. When I wanted to stop Dolphin, with the close button ("X" in top-right corner)I got a message saying Dolphin did not respond. I waited some more but nothing changed so I used the powerswitch to shutdown the computer. Start went normal and now things are working again. Since I don't know how to file a bug for the freezing KDE-menu and I saw that Dophin did not respond I decided to file the bug about Dolphin. Reproducible: Didn't try Steps to Reproduce: Now things are working again, have to wait till the next time the menu freezes and see what happens then. Expected Results: The menu should not have frozen. Sorry, but what else can I write here? OS: Linux (x86_64) release 3.0.0-13-generic Compiler: gcc Kubuntu 11.10, with all updates installed. Computer: Samsung R730 laptop with P6100 dual-core processor and Intel integrated GPU, 4GB ram and no swapfile or partition.
Thanks for the report, but I doubt it is a Dolphin issue... I've reassigned it to the "KDE-menu" component and wildly guess it might be related to some blocking due to a mounted drive (but I think the plasma-guys might know it better).
Demus, can you switch the K menu to Classic Menu Style and see if you can reproduce please? Right click on the K icon to get the menu. Thanks in advance
Hello Anne-Marie, I switched to Classic Style, but as I wrote it happend maybe 5 times in 2 days I have to do things and wait till it happens again. Can take some time. Will let you know. Thanks for answering so fast. Met vriendelijke groet, With kind regards, Mit freundlichen Grüßen, Hormat saya, /*Jan Mussche*/ E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> On 12/02/2011 02:32 PM, Anne-Marie Mahfouf wrote: > https://bugs.kde.org/show_bug.cgi?id=288055 > > > Anne-Marie Mahfouf<annma@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |annma@kde.org > > > > > --- Comment #2 from Anne-Marie Mahfouf<annma kde org> 2011-12-02 13:32:56 --- > Demus, can you switch the K menu to Classic Menu Style and see if you can > reproduce please? Right click on the K icon to get the menu. > Thanks in advance >
do you have any remote drives mounted? (nfs, ssh etc).
Hi, I have an external hard-disk mounted with 2 partitons, one is NTFS and is Ext4. Then there are some (both mounted and not mounted) samba drives in other computers. Whether they are mounted or not depends on the fact if the computers are on, which not all of them are. I added those disks in my fstab file so, when possible, they get mounted at boot. I have had this for a long time already, it always worked. Now that I switched to a KDE version of Ubuntu I see a freezing menu. Could it be because of the shared drives? Met vriendelijke groet, With kind regards, Mit freundlichen Grüßen, Hormat saya, /*Jan Mussche*/ E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> On 12/02/2011 04:22 PM, Beat Wolf wrote: > https://bugs.kde.org/show_bug.cgi?id=288055 > > > Beat Wolf<asraniel@fryx.ch> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |asraniel@fryx.ch > > > > > --- Comment #4 from Beat Wolf<asraniel fryx ch> 2011-12-02 15:22:57 --- > do you have any remote drives mounted? (nfs, ssh etc). >
Indeed, there is a bugreport about shared drives that can freeze the whole desktop. The real cause is not totaly sure, but a possible fix in network manager has been identified. It should be included in kde 4.8. Look at the bugreport https://bugs.kde.org/show_bug.cgi?id=287002 Aaron seigo explains there how to narrow down the problem. Your help would be very welcome.
Well, I did what you asked me: I had the program gdb preset in the terminal and when the bug appeared I started it. When it stopped I typed bt and got some more information. Where can I get all the info so I can send it to you? I can't find a name and/or location of a file somewhere. Met vriendelijke groet, With kind regards, Mit freundlichen Grüßen, Hormat saya, /*Jan Mussche*/ E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> On 12/02/2011 07:06 PM, Beat Wolf wrote: > https://bugs.kde.org/show_bug.cgi?id=288055 > > > > > > --- Comment #6 from Beat Wolf<asraniel fryx ch> 2011-12-02 18:06:40 --- > Indeed, there is a bugreport about shared drives that can freeze the whole > desktop. The real cause is not totaly sure, but a possible fix in network > manager has been identified. It should be included in kde 4.8. > Look at the bugreport https://bugs.kde.org/show_bug.cgi?id=287002 > Aaron seigo explains there how to narrow down the problem. Your help would be > very welcome. >
Hi, I have just booted the computer with a completely empty desktop, while I used to have some stuff on it. When I wanted to add a new default panel the plasma desktop crashed. I reported the bug and it is added with bug 282552. Since I believe something is completely wrong here, I will do a complete re-install since I need a working computer. I can not go on with the setup I have now and only report bugs. Sorry for that. I do hope you have much information already and I really do hope the bugs are found and taken care of. Something I noticed when reporting the bug was in the list of similar bugs I saw ones with KDE4.60, 4.70 and 4.71. One of them, and I believe it was one with KDE version 4.70, was marked as solved. Unfortunately I did not write down the number. My mistake. Success. Met vriendelijke groet, With kind regards, Mit freundlichen Grüßen, Hormat saya, /*Jan Mussche*/ E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> On 12/02/2011 10:18 PM, Jan Mussche wrote: > Well, I did what you asked me: I had the program gdb preset in the > terminal and when the bug appeared I started it. When it stopped I > typed bt and got some more information. > Where can I get all the info so I can send it to you? I can't find a > name and/or location of a file somewhere. > > Met vriendelijke groet, > With kind regards, > Mit freundlichen Grüßen, > Hormat saya, > > /*Jan Mussche*/ > E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> > > > > > On 12/02/2011 07:06 PM, Beat Wolf wrote: >> https://bugs.kde.org/show_bug.cgi?id=288055 >> >> >> >> >> >> --- Comment #6 from Beat Wolf<asraniel fryx ch> 2011-12-02 18:06:40 --- >> Indeed, there is a bugreport about shared drives that can freeze the whole >> desktop. The real cause is not totaly sure, but a possible fix in network >> manager has been identified. It should be included in kde 4.8. >> Look at the bugreporthttps://bugs.kde.org/show_bug.cgi?id=287002 >> Aaron seigo explains there how to narrow down the problem. Your help would be >> very welcome. >>
Git commit 5c42768af6d3f9e38124e2641a48c47643e2ecf9 by Aaron Seigo. Committed on 03/12/2011 at 12:26. Pushed by aseigo into branch 'master'. thread the disk free info fetching so on systems where it is slow it doesn't hang the whole UI dolphin may wish to do similarly? CCMAIL:peter.penz19@gmail.com BUG:288055 M +82 -34 plasma/desktop/applets/kickoff/core/systemmodel.cpp M +33 -1 plasma/desktop/applets/kickoff/core/systemmodel.h http://commits.kde.org/kde-workspace/5c42768af6d3f9e38124e2641a48c47643e2ecf9
I have some new info which might help you: I have a desktop and a laptop computer both fitted with Kubuntu 11.10. I have all updates installed on both machines. In both machines I have partitions and/or folders shared in the smb.conf file. In the fstab file I made mountpoints for those external partitions and folders. It means when the computer boots the folders in the other machine are mounted. As long as I don't use samba to copy/move files from one machine to the other all runs well. But as soon as I start doing that, both machines have the freezing error. The kickoff menu is frozen en Dolphin is too. This takes a while and then things are back to normal. Hope this helps in any way. /*Jan Mussche*/ E-mail: _Jan.Mussche@gmail.com_ <mailto:Jan.Mussche@gmail.com> On 12/03/2011 12:28 PM, Aaron J. Seigo wrote: > https://bugs.kde.org/show_bug.cgi?id=288055 > > > Aaron J. Seigo<aseigo@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |FIXED > > > > > --- Comment #9 from Aaron J. Seigo<aseigo kde org> 2011-12-03 11:28:51 --- > Git commit 5c42768af6d3f9e38124e2641a48c47643e2ecf9 by Aaron Seigo. > Committed on 03/12/2011 at 12:26. > Pushed by aseigo into branch 'master'. > > thread the disk free info fetching so on systems where it is slow it doesn't > hang the whole UI > > dolphin may wish to do similarly? > > CCMAIL:peter.penz19@gmail.com > BUG:288055 > > M +82 -34 plasma/desktop/applets/kickoff/core/systemmodel.cpp > M +33 -1 plasma/desktop/applets/kickoff/core/systemmodel.h > > http://commits.kde.org/kde-workspace/5c42768af6d3f9e38124e2641a48c47643e2ecf9 >
Extra info relating my post: Comment #10 From DeMus 2011-12-04 16:38:12 At the end of the afternoon I couldn't do much with my computers. Every time I opened the Kickoff menu it froze, and so did Dolphin. I managed to change the fstab and the smb.conf file in both computers, taking out all mount-points and shared folders, and rebooted the computers. Since then I have no problem whatsoever (3+ hours). It means I have no network connection between the two but at the moment this is okay.
Maybe I have some more info: I have worked a few days without my Samba shares and I had no problem whatsoever. Now I re-instated Samba and the problems start again. Especially when a computer with shared folders shuts down, the other one, with the mounted shares, freezes immediately. The freezing lasts 20-30 seconds then the system responds again. DeMus
I was wondering if there is any news about this bug. I still can't use samba to connect my computers. I found out yesterday I also can't use VNC to connect them. As soon as I do this the K-Menu and also Dolphin are frozen stiff. The stupid thing is I can connect a Kubuntu machine to a Windows machine. This works great. Connecting 2 Kubuntu machines together makes things freeze.
Is there any news about this bug? It starts to be really annoying since it is not only happening when using Samba but also when using NFS to communicate with the other Kubuntu machine. Dolphin freezes and so does the Kickoff-menu. Thank you.
I have now installed Linux Mint 12 KDE on my laptop, while on my desktop I still have Kubuntu 11.10. Same problem. I can try Samba, I can try NFS but in both situatons Dolphin is freezing completely, making the computer unresponsive. I even installed KDE 4.8 RC2 hoping it would be solved but no, it did not. Any news about this bug? I hear nothing for several weeks now already and this is starting to become a major issue. Please help.
I can confirm this issue. I mount nfs4 exports using automount. After some time dolphin freezes. I tried to kill all kio processes and restart kded but that didn't help. kde 4.8 kubuntu
Can somebody please tell me if there is any news about this bug which is really bugging me since I can not even connect 2 Linux computers together. I filed the bugreport early December of last year and until now there is no solution. I really like to use KDE but this way it is very hard to do so. Please don't let me go to that horrible Gnome 3.
Is anybody working on this bug or do I have to file a new one?
Thank you for this crash report and helping to improve our software. Unfortunately we were not able to work on this specific report yet. Nowadays the version this crash was reported against is no longer maintained and this makes it very difficult to work on this report as the source code might have changed and the information in the backtrace is no longer valid. Also it is quite likely that this problem got fixed in a later version. Crash reports are very often reported multiple times. If you are able to reproduce this crash with the latest version of KDE Plasma (4.10.3) please reopen this report and adjust the version information in the dropdown above and please also include a new backtrace as generated by the crash reporting tool. Please also make sure that the steps on how to reproduce the crash are precise and correct. Thank you!