Bug 78318 - Only katepart selectable as editor after upgrade to Qt 3.3.1
Summary: Only katepart selectable as editor after upgrade to Qt 3.3.1
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-23 18:19 UTC by Bernd Pol
Modified: 2004-04-16 20:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Pol 2004-03-23 18:19:23 UTC 
Version:           3.0.90-CVS (using KDE 3.2.90 (CVS >= 20040117), compiled sources)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:          Linux (i686) release 2.4.21-99-athlon

After a recent upgrade of KDE CVS to Qt 3.3.1 (qtcopy), the "Embedded Editor" selections are gone. (Well, at least I noticed it after that.)
The qeditor interface compiled flawlessly, but neither the Qt Editor nor the KVim plugin are available.
Comment 1 Daniel Franke 2004-03-23 18:40:26 UTC 
Can't confirm.
Compiled Qt-3.3.1, KDE-3.2.1 and kdevelop-3.0.2 from scratch last week. All editors available.
Comment 2 Bernd Pol 2004-03-23 23:21:32 UTC 
ARRGH!
I set up a brand-new user - all three selections are there.

But I have only one selection when I run KDevelop in two other, older users. One running an upgraded debug-compiled CVS, the other running a CVS clean compiled from scratch this weekend (but running in the old environment settings from a previous build). In both cases the problem showed up after upgrading Qt.

Deleting any kdev... file and directory in $KDEHOME/share did not help either.

I remember similar experiences about half a year ago. There I resorted to setting up a new user as well. But this is quite an effort I'd rather wanted to avoid.
---
BTW: This is on a SuSE 9.0 system.
Comment 3 Jens Dagerbo 2004-04-16 20:08:52 UTC 
Not a bug in KDevelop. The same problem was present in KWrite (IIRC) which suggests either a KTrader related complication or simply some kind of misconfiguration.