Am Donnerstag, 10. Jänner 2019, 21:23:55 CET schrieb Lisandro Damián Nicanor Pérez Meyer: > El miércoles, 9 de enero de 2019 20:06:33 -03 Johannes Zarl-Zierl escribió: > > Am Mittwoch, 9. Jänner 2019, 23:37:45 CET schrieb Lisandro Damián Nicanor > > > > Pérez Meyer: > > > Can you tell us which exactly was? In this way: > > > > > > - other users reading the report might benefit from it > > > - we might end up finding a proper solution > > > > Sorry, I thought that was clear from the context. With QT_XCB_NO_MITSHM=1, > > qtcreator does not freeze for me. > > And no ssh forwarding / X2Go, right? No ssh forwarding, and no X2Go. Everything runs local. I also tested just now (in case qtcreator tries to communicate with ssh-agent anyways) in a shell with SSH_AUTH_SOCK unset that the bug still appears. > > P.S.: I did read your other mail regarding testing without clang-related > > plugins under another user. Disabling those plugins under the same user > > does not change anything. I hope I can test with a fresh user tomorrow… > Please do. I can't reproduce the issue, so this will probably give us a > better idea. I just tested with a fresh user, and surprise: the bug does not appear! This is with ClangCodeModel and ClangTools enabled (as per default), without the QT_XCB_NO_MITSHM workaround. This prompted me to move ~/.config/QtProject out of the way on my regular account. This also worked. I then tried copying QtCreator.ini and QtCreator.db back into the QtProject directory, and everything still works. I also tried copying the toolchains/profiles/qtversion files back, but at that point I realized that to do this correctly I would need more knowledge about the internals than I have. So, in summary: 1. *Something* in my ~/.config/QtProject folder caused the problem. 2. Starting with a fresh QtProject folder, the problem disappears. 3. I could salvage my QtCreator.ini without apparent problems (recreating my kits is acceptable for me). I guess this can be attributed to some cruft accumulating in my QtProject folders over the years? If so, I guess it is fair to close this bug as invalid/worksforme/whatever… Thanks again, Johannes
Attachment:
signature.asc
Description: This is a digitally signed message part.