This forum has been archived. All content is frozen. Please use KDE Discuss instead.

[Solved] kdevelop 4.1: Process exited with status 0

Tags: None
(comma "," separated)
kapz
Registered Member
Posts
25
Karma
0
Hi I have KDE 4.5.3 installed on PCLinuxOS 2010.10 and everytime I open kdevelop I get the dialog: Process exites with status 0. Clinking ok button closes the dialog and i can navigate kdevelop and even create a Project, after typing the name for the project and all, nothing happens, no text editor etc shows up.
Then I am allowed to close kdevelop.

If clicked on menu: Session->Start New Session I get the same process exit dialog.

Running kdevelop from konsole gives following output:

Code: Select all
[kapz@kpzL0S ~]$ kdevelop
QFSFileEngine::map: Mapping a file beyond its size is not portable
QFSFileEngine::map: Mapping a file beyond its size is not portable
QFSFileEngine::map: Mapping a file beyond its size is not portable
QFSFileEngine::map: Mapping a file beyond its size is not portable
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QFSFileEngine::map: Mapping a file beyond its size is not portable
QFSFileEngine::map: Mapping a file beyond its size is not portable
Object::disconnect: Unexpected null parameter
Undecodable sequence: \001b(hex)[36l
Undecodable sequence: \001b(hex)[36l
Object::disconnect: No such signal QObject::patchChanged()
QFSFileEngine::map: Mapping a file beyond its size is not portable
kdevelop(13892) Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive
[kapz@kpzL0S ~]$


Can I do anything about it or it's still a bug?(and if it is then it's really an old one! Googling showed a bug report for kdevelop version 3.xx)

Thanks :)

Last edited by kapz on Tue Nov 23, 2010 4:46 pm, edited 1 time in total.


ONLY KDE. Nothing else will do! It just..wont!
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Please remove ~/.kde4/share/apps/kdevelop/*ui.rc with KDevelop closed.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
kapz
Registered Member
Posts
25
Karma
0
Hi!

I couldn't find any files there, all I can find in ~/.kde4/share/apps/kdevelop/ is
a directory called sessions and it has 4 directories named like '{ee8b37ed-365b-46be-9458-48b80b97c6b2}' (1 guess 1 dir for every session)which are have sessionrc filesin them(if kdevelop is closed) and have a file named lock in addition to sessionrc and a folder called recovery(if kdevelop is open), however the lock file and recovery folder disappear if I close kdevelop.

Removing the dir and/or sessionrc in the directories does not help, it still gives the same dialog box when starting up.


ONLY KDE. Nothing else will do! It just..wont!
airdrik
Registered Member
Posts
1854
Karma
5
OS
I've seen that dialog pop up when starting Kdevelop as well (4.1 on KDE 4.5.3 on PCLinuxOS). I haven't looked further into it, but it could be a debug dialog (exit status of 0 generally means success).

When you create a new project, does it show the new project in the projects side bar? IIRC, it doesn't open a text editor window because it doesn't create any text files for you other than the project files (e.g. CMakeFile) - you get to create those yourself which you should be able to do by right-clicking on the project and navigating the context menu (I'm not at my home computer so I can't get into more details than that).


airdrik, proud to be a member of KDE forums since 2008-Dec.
kapz
Registered Member
Posts
25
Karma
0
Thanks airdrik, I was unable to find projects side bar at first, but after fiddeling a bit I managed to open it, yes I can see the projects and yeah I can find and open the files from context menu.

it could be a debug dialog (exit status of 0 generally means success).


The titlebar for the error dialog box says 'Process Error - KDevelop'


ONLY KDE. Nothing else will do! It just..wont!
cplater
Registered Member
Posts
1
Karma
0
OS
I've seen this issue on a new install of Fedora 14. Because it happened right after the splash logo appeared and before any messages on a command line invocation I surmised it may be a plugin that is failing. In checking the setting for plugins it had everything enabled by default. I my case Git was not installed and disabling that solved the problem.
kapz
Registered Member
Posts
25
Karma
0
Many thanks cplater, disabling GIT plugin solved the problem! ^-^


ONLY KDE. Nothing else will do! It just..wont!
alveda
Registered Member
Posts
1
Karma
0
OS
Thanks, works on me too.
uessebe
Registered Member
Posts
3
Karma
0
OS
worked for me too.. thanks []


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell