Version: 3.5 (using KDE 3.5 (RC1) Level "a" , SUSE 10.0 UNSUPPORTED) Compiler: Target: x86_64-suse-linux OS: Linux (x86_64) release 2.6.13-15-default I did my best to narrow this down, I am pretty sure it is a quanta problem, because I can access these files fine with kwrite, kate, kdevelop and even konq's built in text preview. At first I thought it was due to accessing project files from 3.4.3, so i recreated the project files(same issue), then i copied some single .php and .tpl files over to the 64bit box and it still has the same crash. Quanta appears to be fine on my 32bit box that has the same versions and updates.If i attempt to open a .php file or .tpl, both of which contain html code, quanta never displays the contents of the file, and it closes after a few seconds of trying to open the file. I can however open .ini and .txt files, and even .php files that do not contain "<?php ... ?>" Im not sure if it is related, but I have noticed a error message on occassion that says "Unable to load the debugger plugin, error code 5 was returned: ." I first saw this when I started quanta for the first time after updating to KDE3.5 rc1. I then recreated my project files and it went away, even though i never had a debugger specified in the project files. Please let me know if there is any other info that I can provide to help you solve this bug, or anything else I can do for that matter. Thank you, Jake
spin@blackrabbit:/srv/www/domains/MFS> quanta test.php *** glibc detected *** corrupted double-linked list: 0x00002aaaadb9d6f8 *** Alarm clock spin@blackrabbit:/srv/www/domains/MFS> Someone suggested execute quanta from shell to see if i can get an error output, and this is what I got. The same person was running 64bit and 3.5rc1 that they compiled themselves(suse 10), and they did not have a problem viewing php files, and i even sent them the test.php to confirm it.
The problem is I don't have an x86_64 system to test. :-( But there were some commits by another KDE devloper after RC1 was released that are supposed to fix many problems for 64 bits systems. So if you could try the latest svn version from the 3.5 branch (not trunk!), would be nice. It would help a lot to see if Quanta is still unusable for 64 bits systems or not.
Some things I forgot to write in the other comment. On Friday 18 November 2005 19:57, Jake wrote: > Im not sure if it is related, but I have noticed a error message on > occassion that says "Unable to load the debugger plugin, error code 5 > was returned: ." I first saw this when I started quanta for the first > time after updating to KDE3.5 rc1. I then recreated my project files > and it went away, even though i never had a debugger specified in the > project files. This error is fixed since some days. > Please let me know if there is any other info that I can provide to > help you solve this bug, or anything else I can do for that matter. Install a debug version (--debuginfo package for suse, or build with source with --enable-debug=full) and post a backtrace here when it crashes. If you don't get the KDE crash dialog use: gdb quanta run (when crashes) bt
Below is the debug output i saw after running, then opening a .php file. Also someone pointed me to this bug which seems similar: http://bugs.kde.org/show_bug.cgi?id=116176. I tried to downgrade my qt3 package but kdelib3 through a fit along with 50 other packages. I also started to try the trolltech snapshot of qt3.3.6, but the install directions scared the hell out of me. Thread debugging using libthread_db enabled] [New Thread 46912585239456 (LWP 7250)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) *** glibc detected *** corrupted double-linked list: 0x00002aaaadb9d6f8 *** Program received signal SIGABRT, Aborted. [Switching to Thread 46912585239456 (LWP 7250)] 0x00002aaaad9a443a in raise () from /lib64/tls/libc.so.6 (gdb)
>Below is the debug output i saw after running, then opening a .php >file. Also someone pointed me to this bug which seems similar: >http://bugs.kde.org/show_bug.cgi?id=116176. The symptoms are similar, so it might be a bug in the suse patch. > I also started to try the trolltech snapshot > of qt3.3.6, but the install directions scared the hell out of me. It is not that hard to build Qt. Some time ago I used (on suse): cd your_qt_source_dir export QTDIR=$PWD export YACC='byacc -d' export KDEDIR=/opt/kde3 export PATH=$QTDIR/bin:$KDEDIR/bin:$PATH export LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib:$LD_LIBRARY_PATH make -f Makefile.cvs ./configure -system-zlib -qt-gif -system-libpng -system-libjpeg -plugin-imgfmt-mng -thread -fast -no-exceptions -enable-opengl -I/usr/include/pgsql/ -I/usr/include/pgsql/server -I/usr/include/mysql -plugin-sql-mysql -plugin-sql-psql -dlopen-opengl -debug -v -prefix /usr/lib/qt3 make su - make install To use a non-debug build, remove "-debug". This will overwrite your suse version of Qt, but that should not be a problem and you can restore anytime by installing again the suse rpm.
I tried these directions and it didnt make for me, and your configure parameters dont work for me either, Im not that comfortable wtih compiling stuff, I can usually handle problems with ./configure, but if i have make problems I am SOL. make[2]: Entering directory `/home/spin/qt-3.3.6/src' g++ -c -pipe -I/usr/include/pgsql/ -I/usr/include/pgsql/server -I/usr/include/mysql -fno-exceptions -Wall -W -O2 -D_REENTRANT -fPIC -DQT_SHARED -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT -DQT_NO_CUPS -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_XINERAMA -DQT_NO_SHAPE -DQT_NO_XCURSOR -DQT_NO_XRANDR -DQT_NO_XRENDER -DQT_NO_XFTFREETYPE -DQT_NO_XKB -DQT_NO_SM_SUPPORT -DQT_NO_IMAGEIO_MNG -DQT_NO_IMAGEIO_JPEG -DQT_BUILTIN_GIF_READER=1 -DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE -DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC -I/home/spin/qt-3.3.6/mkspecs/linux-g++ -I. -I../include -I/usr/X11R6/include -I/usr/X11R6/include -I.moc/release-shared-mt/ -o .obj/release-shared-mt/qtaddons_x11.o kernel/qtaddons_x11.cpp In file included from kernel/qtaddons_x11.cpp:25: kernel/qt_x11_p.h:66:22: error: X11/Xlib.h: No such file or directory kernel/qt_x11_p.h:71:23: error: X11/Xutil.h: No such file or directory kernel/qt_x11_p.h:72:21: error: X11/Xos.h: No such file or directory kernel/qt_x11_p.h:73:23: error: X11/Xatom.h: No such file or directory make[2]: *** [.obj/release-shared-mt/qtaddons_x11.o] Error 1 make[2]: Leaving directory `/home/spin/qt-3.3.6/src' make[1]: *** [sub-src] Error 2 make[1]: Leaving directory `/home/spin/qt-3.3.6' make: *** [init] Error 2 blackrabbit:/home/spin/qt-3.3.6 #
And as far as 64bit problems go, I have not had quanta crash on me once in the 10 months i have been using it on this machine, And that is almost every single day. This was on suse 9.2 and kde 3.4 and and 9.3 and kde 3.4.1 and now on suse 10 with kde 3.4.2 and 3.4.3. This is the first issue i have had, and it does not even appear to be a quanta issue so much as qt3. So you are doing a great job :) As far as trying the svn, I dont think it is going to help me because i actually downgraded quanta back to 3.4.2 and still had the same issue, also i dont know a trunk from a head and have never used svn.
On Saturday 19 November 2005 00:05, Jake wrote: > kernel/qt_x11_p.h:66:22: error: X11/Xlib.h: No such file or directory > kernel/qt_x11_p.h:71:23: error: X11/Xutil.h: No such file or > directory kernel/qt_x11_p.h:72:21: error: X11/Xos.h: No such file or > directory kernel/qt_x11_p.h:73:23: error: X11/Xatom.h: No such file > or directory Install the -devel package for XOrg (and most probably for other packages as well). > As far as trying the svn, I dont think it is going to help me because > i actually downgraded quanta back to 3.4.2 and still had the same > issue, also i dont know a trunk from a head and have never used svn. First try to compile qt and see if it solves. Getting Quanta from svn is desribed on the FAQ page at quanta.kdewebdev.org.
well I got qt to compile after playing with the parameters and installing a few more -devel packages then recompiling countless times. ./configure -platform linux-g++-64 -fast -thread -qt-gif -no-exceptions -enable-opengl I did that then make; make install and it all went through finally. Once installed I had 'qtconfig' in my path and i ran it, it showed that it was using the qt3.3.6, as i figured that was a special instance i decided to exit kde and log back in, now qtconfig is no longer in the admin path, and im obviously still using 3.3.5. I really appreciate your help and I am hoping that you can tell me what i need to change to get my machine to use 3.3.6? the rpms for 3.3.5 qt3 and qt3-32bit are still installed, I started uninstall them but about 60kde packages suggested that it was a bad idea.
ok all of that ended badly, i got it installed, but was unable to get KDE to use the packages... in the process i discovered this brand new rpm of qt3.3.5-19 http://suse.inode.at/pub/x86_64/supplementary/KDE/update_for_10.0/base/qt3-3.3.5-19.x86_64.rpm it fixed me right up. YAY, i can get back to work again! Thanks again for all of your help Mantia! Please let me know if there is anything I can do to help you with quanta. Im not a c++ coder, but I am good with graphics and LAMP development.
whoops forgot to mark the bug resolved.
On Saturday 19 November 2005 08:32, Jake wrote: > http://suse.inode.at/pub/x86_64/supplementary/KDE/update_for_10.0/bas >e/qt3-3.3.5-19.x86_64.rpm > > it fixed me right up. YAY, i can get back to work again! Great! > > Thanks again for all of your help Mantia! You're welcome. > Please let me know if there is anything I can do to help you with > quanta. Im not a c++ coder, but I am good with graphics and LAMP > development. You might help with kdewebdev site development: http://mail.kdewebdev.org/mailman/listinfo/kdewebdev-site It's a low traffic list, so you might subscribe. Take a look at the current site and if you have ideas, let us know. We have (like selectable css style for the page, which is not yet implemented). Andras