Bug#929511: qtcreator: Segfault on start

2019-05-28 Thread Alexander Kernozhitsky
Sorry for the last message being unfinished. > P.S. However, dpkg shouldn't have installed qtcreator in the first place, with that outdated lib still in place. So, maybe there's some little thing to do for the package maintainers after all. AFAIK, if that were the version of libllvm present in

Bug#929511: qtcreator: Segfault on start

2019-05-28 Thread Alexander Kernozhitsky
I think the bug should be closed now, because it's not Qt Creator problem > P.S. However, dpkg shouldn't have installed qtcreator in the first place, > with that outdated lib still in place. So, maybe there's some little thing > to do for the package maintainers after all. I -- Alexander

Bug#929511: qtcreator: Segfault on start

2019-05-27 Thread subhuman
I tried with a new user and got the same result. Reverse Depends: Depends: libgl1-mesa-dri Depends: libxatracker2 Home of the bug! They were both completely outdated. After the update I could safely remove the old llvm library, and now qtcreator works. Thx 2 u both, and sorry for bothering

Bug#929511: qtcreator: Segfault on start

2019-05-26 Thread Alexander Kernozhitsky
IMHO the problem here can be using a very outdated libLLVM version (which is even not in unstable). The things I don't understand are: 1) Why Qt Creator is still using this old version? According to the stack trace, libLLVM 7 is triggered, but then it starts calling functions from an older

Bug#929511: qtcreator: Segfault on start

2019-05-26 Thread Lisandro Damián Nicanor Pérez Meyer
Hi! On Sun, 26 May 2019 at 00:06, subhuman wrote: > > Hi Lisandro, > > thank you for your reply. My pleasure! > I will answer your questions in two parts, because I haven't got much time > right now - I'm to help with the European elections. What I can give you here > is the output from: > >

Bug#929511: qtcreator: Segfault on start

2019-05-25 Thread subhuman
Hi Lisandro, thank you for your reply. I will answer your questions in two parts, because I haven't got much time right now - I'm to help with the European elections. What I can give you here is the output from: ~$ qtcreator -profile Profiling started >loadLibrary Core

Bug#929511: qtcreator: Segfault on start

2019-05-25 Thread Lisandro Damián Nicanor Pérez Meyer
tag 929511 unreproducible moreinfo severity 929511 important thanks Hi Martin! On Sat, 25 May 2019 at 05:06, Martin Haase wrote: > > Package: qtcreator > Version: 4.8.2-1 > Severity: grave > Tags: upstream > Justification: renders package unusable I can't reproduce the behavior and I have also

Bug#929511: qtcreator: Segfault on start

2019-05-25 Thread subhuman
For some reason unknown to me there are several packages still depending on this special version of libLLVM. When I try to remove it, qtcreator is listed among them. As is xorg - which prevents me from performing the `apt-get remove`. On Sat, 25 May 2019 12:59:16 +0300 Alexander Kernozhitsky

Bug#929511: qtcreator: Segfault on start

2019-05-25 Thread Alexander Kernozhitsky
Hello, I am using Qt Creator on Buster and don't see any problems on start. BTW, why do you have /usr/lib/x86_64-linux-gnu/libLLVM-3.7.so.1? I searched on packages.debian.org and I didn't find the package with such library for amd64. Is it the old package that was manually installed or it

Bug#929511: qtcreator: Segfault on start

2019-05-25 Thread Martin Haase
Package: qtcreator Version: 4.8.2-1 Severity: grave Tags: upstream Justification: renders package unusable This is what I get when I try to start qtcreator: Program received signal SIGSEGV, Segmentation fault. 0x7fffe6091e3c in llvm::SmallPtrSetImplBase::Grow(unsigned int) () from