pcmanfm-qt segfaults after some tricks (Lubuntu Next 18.04 and dailybuild of 19.05.2018)

[Dima]

1,2) Please see the apport attachment.
3) Steps to reproduce:
1. Open pcmanfm-qt.
2. Go to root dir /
3. Change the view of the dir to "Detailed list"
4. Open /etc dir with double click. If it opened in Icon View mode then step back and try to enter to /etc

4) pcmanfm-qt segfaults in my case. My current related dmesg output:
"
[ 99.878774] pcmanfm-qt[1051]: segfault at 560d40011390 ip 0000560d40011390 sp 00007ffe107ca5d8 error 15
[ 190.640536] pcmanfm-qt[1237]: segfault at 556c0b82dba0 ip 0000556c0b82dba0 sp 00007fffefd12e08 error 15
[ 1214.139394] pcmanfm-qt[1320]: segfault at 7f242900dda0 ip 00007f2428e39cde sp 00007ffc37114630 error 4 in libc-2.27.so[7f2428da2000+1e7000]
[ 1668.239954] pcmanfm-qt[3154]: segfault at 7fcb0f14f2b0 ip 00007fcb0f14f2b0 sp 00007ffe60521188 error 15 in libc-2.27.so[7fcb0f14e000+2000]
"

The last two is after installing of apport. But it maybe unrelated.
I've tried it on Lubuntu Next daily-build of 19.05.2018. And the problem is existing on it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pcmanfm-qt 0.12.0-5
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: LXQt
Date: Sat May 19 21:58:55 2018
LiveMediaBuild: Lubuntu-Next 18.04 LTS "Bionic Beaver" - Release amd64 (20180503)
SourcePackage: pcmanfm-qt
UpgradeStatus: No upgrade log present (probably fresh install)

[Simon Quigley (tsimonq2)]

I can confirm this.

Thanks for the report!

[Alf Gaida (agaida)]

importance can be lowered - fixed in 0.13.0

[Alf Gaida (agaida)]

Anyways - one can consider all libfm-qt and pcmanfm-qt bugs for versions < 0.13 not relevant for cosmic - libfm-qt and pcmanfm-qt got heavy modifications for 0.13 so most of the 0.12.0 bugs are not relevant for cosmic (massive parts of libfm-qt are rewritten in c++ and don't use the old libfm stuff anymore). The interesting thing will be to catch bugs in the new version and iron them out until 18.10

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

I'll call it not relevant once we have a release for 0.13!

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

Do you know which commit this was fixed in Alf?

[Alf Gaida (agaida)]

no, not really - but i know that we will release within the next day(s). So we could consider the behaviour as _not so nice_, but i wouldn't spend any time on it.

[Simon Quigley (tsimonq2)]

Fixed in 0.13.0.