Comment 6 for bug 1878336

I'd not noticed the loss of lxqt.debian.net in prior comment, until I tried to `apt source` today.

Thus I replaced package with standard debian package

guiverc@dc780-deb:~$ apt-cache policy pcmanfm-qt
pcmanfm-qt:
  Installed: 0.14.1-3+b1
  Candidate: 0.14.1-3+b1
  Version table:
 *** 0.14.1-3+b1 500
        500 http://deb.debian.org/debian testing/main amd64 Packages
        500 http://ftp.iinet.net.au/debian/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status

I've now RE-CREATED the issue on debian testing (bullseye/11), though it took some play as it changing the settings a number of times as the deleted image was sometimes visible, sometimes shown as black-screen (behavior felt different to Lubuntu but that could be my memory). To achieve issue this session I had to logout (image deleted last session) & login again before 100% thread could be re-created.

guiverc@dc780-deb:~$ ps -elf |grep pcmanfm
0 R guiverc 3146 2932 86 80 0 - 392369 - 11:45 ? 00:04:44 /usr/bin/pcmanfm-qt --desktop --profile=lxqt

Either way that thread is now pretty steady at 100% CPU; same issue as with Lubuntu.

Given it took me a bit of play on this box to accomplish (what I recall being easy on Lubuntu), maybe I'd just followed the instructions exactly in comment #5 and not re-created it thus giving debian-testing using the 0.14.2~166-g74a6f4d-1 package a faulty not-impacted (I doubt I logged out & logged back in comment #5 which is what I think allowed the issue to occur this time).