| Summary: | Kdevelop fails on startup | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Sean Clarke <sean.clarke> |
| Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Sean Clarke
2004-01-21 02:11:09 UTC
Yes, this is either a packaging bug or a user error... ;) If you've installed it without "--force" and with the 3.2 RC1 kdelibs package, report it to SUSE, in this case it's a packaging error. If you've installed the KDevelop 3.0 RC1 rpm on a system other than KDE-3.2 RC1, this is what will happen, and is a user error as the rpm wasn't built for this. (The KDevelop 3.0 RC1 source will only compile on kdelibs-3.2 RC1 or KDE-3.0.x/3.1.x) No --force and no seperate KDevelop (source or RPM) weer used. I downloaded the KDE/SUSE 3.2 RC1 packages from ftp.kde.org and installed them on an otherwise "stock" SUSE 9.0 machine. What is the best way to highlight it to SuSE? Thanks for your help Jens. Yep, I think it is a packaging bug, just updated another SuSE machine, this time SUSE 8.2 (not 9.0) and I get the same error: kdevelop (core): SPLASH: message=Starting core application kdevelop (core): SPLASH: message=Loading Settings kdevelop: relocation error: kdevelop: undefined symbol: _ZN11KMdiMainFrm25setStandardMDIMenuEnabledEv |