You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Saturday, September 25th 2004, 6:09pm

Kdevelop crashes!!!

I'm quite newbie in programming in Linux and Kdevelop and I would like to
try it, so far I have found some good tutorials about it but my problem is that
everytime I try to open the Kdevelop it crashes. I also tried to run it from
konsole and that worked until I tried to make my Project when kdevelop crashed again.
After that I deleted the Project and it worked, but everytime I try to make a new Project same thing happens I went to kde bugs and I learned there about some possible solutions about this problem and none of them worked for me so far.
I'm running MDK 10 with Kdevelop 3.0.1
I even tried to upgrade to 3.0.4 and I received 'relocation error'.


Can anyone help me?

Latem

Beginner

Posts: 31

Location: New Brunswick, Canada

Occupation: Student/Programmer

  • Send private message

2

Sunday, September 26th 2004, 4:34pm

hmm that is weird.
I have Mandrake 10.0 Official, that comes w/ KDE 3.2 and Kdevelop 3.0.1, and haven't had any such issues with it. The only problem I had was that I had Automake 1.4.7 (or some 1.4.x) and KDevelop needs 1.7. I updated to 1.7 using urpmi, and corrected all the symlinks, and works like a charm.

when you lauch it from console does it give any errors?

How did you install Kdevelop? with your linux install? using urpmi from CD? or manually from source?

If you did it with either one of the first two methods, you could try uninstalling it using package manager, and then installing it again.

I relly dont know.

Latem
The march of progress:
C:
printf("%10.2f", x);
C++:
cout << setw(10) << setprecision(2) << showpoint << x;
Java:
java.text.NumberFormat formatter = java.text.NumberFormat.getNumberInstance();
formatter.setMinimumFractionDigits(2);
formatter.setMaximumFractionDigits(2);
String s = formatter.format(x);
for (int i = s.length(); i < 10; i++) System.out.print(' ');
System.out.print(s);

3

Monday, September 27th 2004, 6:28pm

Well, I don't know how but I resolved the problem by reinstalling it.
As I said I upgraded to 3.0.4 and I uninstalled it after 'rellocation error' and then
I installed the old one and now it works fine, however now I have another problem,
when I try to build my Simple KDE application project I receive this message:

cd "/home/tomo/cpp/KDE/sigcreate/debug" && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake -k
*gmake all-recursive
*Making all in doc
*Making all in .
*gmake[3]: Nothing to be done for `all-am'.
*Making all in en
*gmake[3]: Nothing to be done for `all'.
*Making all in po
*gmake[2]: Nothing to be done for `all'.
*Making all in src
*/bin/sh ../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -g3 -fno-inline -O0 -g3 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -o sigcreate -R /usr/lib -R /usr/lib/qt3/lib -R /usr/X11R6/lib -L/usr/X11R6/lib -L/usr/lib/qt3/lib -L/usr/lib main.o sigcreate.o -lkdeui
*g++: /usr/X11R6/lib/libGL.so: No such file or directory
*gmake[2]: *** [sigcreate] Error 1
*
*gmake[2]: Target `all' not remade because of errors.
*gmake[1]: *** [all-recursive] Error 1
*gmake: *** [all] Error 2
**** Exited with status: 2 ***

This I don't understand because the wanted libGL.so file does exist but as a soft link.
I really don't know what is wrong now. And just to mention, I'm using both automake-1.4-23.p6mdk and automake1.7-1.7.9-1mdk, prehaps there lies problem.
I saw at rpm.pbone that there is even newer automake1.9-1.9-1mdk.noarch.rpm


These are the messages that I receive when I launch kdevelop from konsole (but this is after reinstall, I also had these messages before upgrade):

[tomo@su-076 tomo]$ kdevelop
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
QObject::connect: No such slot subversionPart::slotActionAdd()
QObject::connect: (sender name: 'subversion_add')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionRemove()
QObject::connect: (sender name: 'subversion_remove')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionAddToIgnoreList()
QObject::connect: (sender name: 'subversion_ignore')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionRemoveFromIgnoreList()
QObject::connect: (sender name: 'subversion_donot_ignore')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotStopButtonClicked(KDevPlugin*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'Subversion')
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.
ASSERT: "part && parent" in partwidget.cpp (41)
kdecore (KIconLoader): WARNING: Icon directory /usr/share/icons/lush-0.1.0/ group not valid.

If you can help me with this, please do.

wysota

Trainee

Posts: 65

Location: Warsaw, POLAND

  • Send private message

4

Monday, September 27th 2004, 11:42pm

Did it crash right from the beginning? If not, try to delete [projectname].kdevelop.pcs and [projectname].kdevses from your last opened project. I don't know why it happenes, but the session files sometimes cause kdevelop to crash on startup. Maybe that's your case too.
Live and let live - use the search engine.
"Use the docs Luke, use the docs!"

Latem

Beginner

Posts: 31

Location: New Brunswick, Canada

Occupation: Student/Programmer

  • Send private message

5

Tuesday, September 28th 2004, 3:20am

I think KDevelop requires version 1.6 or 1.7. Something bigger than 1.4.9 or whatever comes with Mandrake. I know I had to update automake.

make sure your symlinks are all pointing to the right place. make sure that /usr/bin/automake points to /etc/alternatives/automake, which in turn points to /usr/bin/automake-1.7.
Also /usr/bin/aclocal should point to /etc/alternatives/aclocal which points to /usr/bin/aclocal-1.7.

that's my system anyway.

as for the error messages, I dont know if you should worry about them or not, if KDevelop works.
this is what I get when I run KDevelop from console, but it has always worked fine for me, except for some drawing oddities here and there on occasion.

Quoted

QObject::connect: No such slot subversionPart::slotActionAdd()
QObject::connect: (sender name: 'subversion_add')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionRemove()
QObject::connect: (sender name: 'subversion_remove')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionAddToIgnoreList()
QObject::connect: (sender name: 'subversion_ignore')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotActionRemoveFromIgnoreList()
QObject::connect: (sender name: 'subversion_donot_ignore')
QObject::connect: (receiver name: 'Subversion')
QObject::connect: No such slot subversionPart::slotStopButtonClicked(KDevPlugin*)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'Subversion')
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance )
kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
kdecore (KAccel): WARNING: KKeySequence::init( seq ): key[0] is null.
ASSERT: "part && parent" in partwidget.cpp (41)


I guess if it works, even with those messages, what can u do really?
Latem
The march of progress:
C:
printf("%10.2f", x);
C++:
cout << setw(10) << setprecision(2) << showpoint << x;
Java:
java.text.NumberFormat formatter = java.text.NumberFormat.getNumberInstance();
formatter.setMinimumFractionDigits(2);
formatter.setMaximumFractionDigits(2);
String s = formatter.format(x);
for (int i = s.length(); i < 10; i++) System.out.print(' ');
System.out.print(s);

6

Tuesday, September 28th 2004, 9:34pm

It is OK now, due to this problem with kdevelop I learned that Linux is very much vulnerable to the power breakdowns because my problems were caused by lack of some crucial files that kdevelop needs.
Recently, I had three or four power breakdowns and I don't have an UPS to protect my system and that is the cause of missing files. I've reinstalled those packages which contain those missing files and now everything works fine.
Anyway, thank you very much for help.

Latem

Beginner

Posts: 31

Location: New Brunswick, Canada

Occupation: Student/Programmer

  • Send private message

7

Tuesday, September 28th 2004, 9:58pm

Quoted

due to this problem with kdevelop I learned that Linux is very much vulnerable to the power breakdowns


That's kinda true. IMHO some Linux apps do rely on intermediate or temporary files too much. It usually isn't a big deal if you know what file in question is the issue, but it's not easy to find out that detail. For example I used to work with PVM, and we had a power failure once or twice while it was running, and upon reboot PVM would not work at all, and spit a lot of error messages. The solution is simple, just delete pvmd.500 or something in some tmp directory (I dont remember the exact path any more). But really how's a normal user suppose to know that?? It would just seem that the failure really screwed up something, and a reinstall would seem the only fix.

Again I think the problem is usually with a specific application. I've had power go out while I wasnt really using any complex app, maybe just a web browser, or aKregator, and XMMS. and upon reboot everything worked fine. But for more complex stuff, some undeleted temp file, or something similar could cause problems.

Anyway, glad u got ur stuff sorted out.

Latem
The march of progress:
C:
printf("%10.2f", x);
C++:
cout << setw(10) << setprecision(2) << showpoint << x;
Java:
java.text.NumberFormat formatter = java.text.NumberFormat.getNumberInstance();
formatter.setMinimumFractionDigits(2);
formatter.setMaximumFractionDigits(2);
String s = formatter.format(x);
for (int i = s.length(); i < 10; i++) System.out.print(' ');
System.out.print(s);

wysota

Trainee

Posts: 65

Location: Warsaw, POLAND

  • Send private message

8

Tuesday, September 28th 2004, 10:11pm

Do you use a journaling filesystem? With REAL journaling?
Live and let live - use the search engine.
"Use the docs Luke, use the docs!"

Latem

Beginner

Posts: 31

Location: New Brunswick, Canada

Occupation: Student/Programmer

  • Send private message

9

Thursday, September 30th 2004, 2:25am

I use ext3, which as far as I know is a journaling system.
I've never had any problems w/ crashes and such with my current os, Mandrake 10. All such issues I've experienced with Rad Hat 8, and I don't know what FS I've used with that.
I don't fully understand what journaling is, and I can't quite get it from a few sites I just searched.
How does that protect in the the situation like the one I mentioned, with temporary files. For example PVM uses that file (I think it's called pvmd.500), and it stores info about current running tasks that it is managing. So when you try to run it again (after it was abruptly terminated), it sees that this file is there, and tries to do something with it thinking it has tasks to do, and goes all crazy.

Latem
The march of progress:
C:
printf("%10.2f", x);
C++:
cout << setw(10) << setprecision(2) << showpoint << x;
Java:
java.text.NumberFormat formatter = java.text.NumberFormat.getNumberInstance();
formatter.setMinimumFractionDigits(2);
formatter.setMaximumFractionDigits(2);
String s = formatter.format(x);
for (int i = s.length(); i < 10; i++) System.out.print(' ');
System.out.print(s);

wysota

Trainee

Posts: 65

Location: Warsaw, POLAND

  • Send private message

10

Thursday, September 30th 2004, 11:25am

You can have different modes of journaling in etx3:

1. journal
All data is written to the journal before writing it to the main filesystem

2. ordered (default)
All data is written to the main filesystem before its metadata is written to the journal

3. writeback
Data ordering is not preserved - data may be written into the main file system after its metadata has been committed to the journal. The fastest of all modes, but it can happen that old data and new data will be mixed after a crash.

So as you see, by default you have an UNREAL journalling :) See man mount for details.
Live and let live - use the search engine.
"Use the docs Luke, use the docs!"