Summary: | KDevelop crashes when both llvm3.8 and 4.0 are installed | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | jacoposchiavon21 |
Component: | Packages User Edition | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bastisawesomeltd, brent, jan.koester, jr, mail, neon-bugs, nicolas, sitter, ych0023 |
Priority: | VHI | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
jacoposchiavon21
2017-08-03 13:56:33 UTC
You are mixing two versions of llvm (3.8 and 4.0). Do you build yourself ...? nope, I have installed the Neon LTS user edition distribution (https://neon.kde.org/download) and kdevelop from apt. Anyhow, from the apt package manager seems that both llvm are installed and updated! Should I try to remove the older one? Yes please try, and please also report a packaging bug to Ubuntu, this must not happen. They need to be properly seperated somehow. (In reply to Sven Brauch from comment #4) > Yes please try, and please also report a packaging bug to Ubuntu, this must > not happen. They need to be properly seperated somehow. I have tried, and removing llvm3.8 removes also kdevelop and everything. At the same time, pkgProblemResolver::Resolve interrupts the removing of llvm 4.0 saying that: Broken phonon-backend-gstreamer:amd64 Dipende on libqt4-opengl [ amd64 ] < 4:4.8.7+dfsg-5ubuntu2 > ( libs ) (>= 4:4.8.1) Considering libqt4-opengl:amd64 9 as a solution to phonon-backend-gstreamer:amd64 1 Holding Back phonon-backend-gstreamer:amd64 rather than change libqt4-opengl:amd64 I'm not sure of what is asking here: am I missing some package that llvm4.0 needs? Hm yeah, I guessed something like this would happen: you have two (or more) packages installed which need different versions of llvm. Still, sorry, you have to discuss this on your distribution's bugtracker -- we are the wrong people, we neither know exactly how it's supposed to work nor can we do anything about it :/ Thank you! At least now I have something that I can ask! I'll move to ubuntu bugtracker. Really thank you for your time Probably related: https://bugs.kde.org/show_bug.cgi?id=383086 Or even a duplicate. Sigh. Correct link: https://bugs.kde.org/show_bug.cgi?id=373614 yep, it appears to be similar! Is there a known way to get around? No easy fix for the KDevelop version you got via the PPA unfortunately. You could try the AppImage from https://www.kdevelop.org/download -- but honestly I'm not exactly sure whether you'll be running into the same issue with it. Please report back in any case. Now I'm trying to do. But interestingly, now a very similar crash happens with konqueror... The AppImage seems to work, anyhow... (In reply to Kevin Funk from comment #11) > You could try the AppImage from https://www.kdevelop.org/download -- but > honestly I'm not exactly sure whether you'll be running into the same issue > with it. Shouldn't happen (and apparently doesn't). Ok, for other reason I have reinstalled the OS, changing to Plasma 5.10.3 and checking that the only used LLVM was 4.0. Anyway, as soon as I install Kdevelop, it install also the 3.8 version, and then crashes as before. It would be cool if you could report this to ubuntu and post a link here as a cross-reference to keep track of what they say. I've posted a question here: https://answers.launchpad.net/ubuntu/+question/655238 *** Bug 383170 has been marked as a duplicate of this bug. *** (In reply to Sven Brauch from comment #17) > *** Bug 383170 has been marked as a duplicate of this bug. *** For the record, I am running KDE Neon on both systems where this bug occurred. So it must be their packaging. Do I understand correctly that removing LLVM is a workaround? Well, with my experience you can't really remove one of the two: 3.8 comes together with Kdevelop (Kdevelop asks for clang library based on LLVM 3.8), while 4.0 is needed for other things too, I understand. I think that the only thing we can do is hoping for the ubuntu team to repackage things, is it correct? In the meantime I advice you to give a look here: https://www.tecmint.com/best-linux-ide-editors-source-code-editors/ This is a bug in neon packaging I guess, maybe you can look at it there? *** Bug 383223 has been marked as a duplicate of this bug. *** @Neon packagers: There's a bug report from Debian packagers: https://bugs.kde.org/show_bug.cgi?id=373614 -- they have a patch for LLVM which mitigates this issue. @Neon packagers, to be clear: You need this patch for the LLVM version which KDevelop is linked against: https://reviews.llvm.org/D31524 Please report back if that fixes the issue for you. Wouldn't building kdevelop with llvm4 fix the problem as well? We do not build compilers, nor do I see us starting to do that. rebuilding with llvm 4.0 https://packaging.neon.kde.org/kde-std/kdevelop.git/commit/?id=5b2241fd8eea0b650d93d3b7c7629e28b0fda12a new kdevelop packages entering into user and user/lts in the next hour or so are compiled with llvm 4.0. Anyone able to test? Just updated, crash seems to be gone. Thanks! *** Bug 386950 has been marked as a duplicate of this bug. *** *** Bug 387322 has been marked as a duplicate of this bug. *** *** Bug 388832 has been marked as a duplicate of this bug. *** |