Desktop will stop responding when moving Desktop files into a new folder created on the desktop

[amjjawad ]

Lubuntu 11.10 Fresh New Installation.
P4 - 2GB RAM - 40GB IDE HDD - Intel Graphics.

When I create a New Folder on the Desktop to move some files from the desktop into that new folder (drag and drop), the desktop will stop responding and when I move any open window, it leaves a shadow or tail, it's like copying itself on the desktop. Also, PCManFM is not responding and can not open it. Menu works but when I open any sub-menu, it got stuck there even when I click on the desktop.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: pcmanfm 0.9.9-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Wed Nov 16 11:50:46 2011
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
Pref_Config_System_lubuntu:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pcmanfm
UpgradeStatus: No upgrade log present (probably fresh install)

[amjjawad  (amjjawad)]

I forgot to add that ALL icons on Desktop will disappear and this is the first thing that will happen when I drag and drop files from desktop to any folder created on the desktop. Then, when I move any opened window for any application or even a folder, it will act all crazy just like the attached screenshot.

[amjjawad  (amjjawad)]

You see I can re-produce that bug. Sometimes, I can get my desktop back and use it normally with one log out. Sometimes, I have to log out twice. Today, I logged out 5 times but that did not fix anything so I had to reboot.

I had exactly the same issue on Lubuntu 11.04 so hope that will be fixed soon.

Thanks!

[amjjawad  (amjjawad)]

By any chance, is this bug: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1179167
Related somehow to this one?

[Dave Kokandy (drkokandy)]

I believe you may be right about the duplicate nature this. I am adding this as a duplicate of fixed bug 1179167, as I cannot reproduce this.

If you are still having this issue, please update. Thank you!