Comment 0 for bug 2006584

I have been experiencing PCManFM freezes multiple times since several weeks, and it has come to such an extend that I have to look for another file manager as a replacement. While using it, I had to kill its process PID and restart it several times in a short span of time.

I have been using it in several computers for years now and never has it been such an issue.

At last yesterday using it after starting it in a gdb session. Here is what it ended with:

“
[Thread 0x7fffe2ffd700 (LWP 7587) exited]
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
pcmanfm: ../../src/xcb_io.c :260 : poll_for_event: l'assertion « !xcb_xlib_threads_sequence_lost » a échoué.
--Type <RET> for more, q to quit, c to continue without paging--

Thread 1 "pcmanfm" received signal SIGABRT, Aborted.
0x00007ffff718f00b in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb)
”

("à échoué", in the above block quote, means "failed")

This happened just by trying to open a regular directory.

Yesterday and now I am in a virtualbox machine. I'll join the full output from GDB, plus some related hardware and version context (lshw, lspci, lsb-release… )

I would love it to be fixed, and I hope my information helps.