tde-devels

devels@trinitydesktop.org

10 participants
3780 discussions

No WILD GEESE gcc 4.7 => kwrite/kate crash, gcc 4.6 current code == All Good!

by David C. Rankin

Tim, Darrell, All, After much (wasted) effort, I have come to the definite conclusion that the crash seen in kwrite/kate/quanta/konqueror(filemanagement katepart) is 100% due to gcc 4.7. I just finished a rebuild of current code on gcc 4.6 and kwrite works perfectly/wraps without problem, etc... See: http://www.3111skyline.com/dl/dt/trinity/ss/kwrite-gcc46-allgood.jpg Repeating, just a Darrell confirms, building from current GIT on gcc 4.6 is fine, building on gcc 4.7 causes the crash with no FTBFS. I have no clue what to do next. It is probably premature for a bug against gcc 'wrong code' until somebody can confirm that katerenderer.cpp doesn't violate coding standards. Sorry for the long troubleshooting process. I should have just taken Tim's advice and rebuilt from 46 is a first step, but sometimes the long way around just can't be avoided. What to do next? -- David C. Rankin, J.D.,P.E.

12 years, 11 months

kwrite crash - it's gcc 4.7 - rebuilt 3/29 sources on gcc 4.7 - same crash

by David C. Rankin

Tim, Darrell, all It's confirmed - the same kwrite crash occurs when the 3/29 sources are rebuilt on gcc 4.7. We are challenged with what will be a fun bug hunt that will take a skilled dev who is familiar with this type of debug. I did have full debug built into the packages and here is the backtrace. I'm at a standstill. I know not where to go next. Experts, please weigh in.... Loaded symbols for /lib/libnss_files.so.2 0x00007f5859c98200 in isSpace () from /opt/tqt3/lib/libtqt-mt.so.3 (gdb) bt #0 0x00007f5859c98200 in isSpace () from /opt/tqt3/lib/libtqt-mt.so.3 #1 0x00007f585a0a6a6c in TQChar::isSpace (this=0x1c9b010) at tools/qstring.cpp:475 #2 0x00007f5853f5ffc1 in KateRenderer::textWidth (this=0x1aa9210, textLine=..., startcol=0, maxwidth=817, needWrap=0x7fffc9605ea8, endX=0x7fffc9605e9c) at /build/src/tdelibs/kate/part/katerenderer.cpp:806 #3 0x00007f5853f41674 in KateViewInternal::range (this=this@entry=0x1a66ce0, realLine=realLine@entry=0, previous=previous@entry=0x0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1331 #4 0x00007f5853f42b32 in KateViewInternal::range (this=this@entry=0x1a66ce0, realLine=0, viewLine=viewLine@entry=1) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1418 #5 0x00007f5853f444c9 in KateViewInternal::viewLineOffset (this=this@entry=0x1a66ce0, virtualCursor=..., offset=0, keepX=keepX@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1578 #6 0x00007f5853f47d25 in KateViewInternal::makeVisible (this=this@entry=0x1a66ce0, c=..., endCol=115, force=force@entry=false, center=center@entry=false, calledExternally=calledExternally@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:781 #7 0x00007f5853f48352 in KateViewInternal::updateCursor (this=this@entry=0x1a66ce0, newCursor=..., force=force@entry=true, center=center@entry=false, calledExternally=calledExternally@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:2204 #8 0x00007f5853f4c4c0 in KateViewInternal::editEnd (this=0x1a66ce0, editTagLineStart=0, editTagLineEnd=<optimized out>, tagFrom=<optimized out>) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:3385 #9 0x00007f5853ee8ef0 in KateDocument::editEnd (this=0x199d150) at /build/src/tdelibs/kate/part/katedocument.cpp:1032 #10 0x00007f5853ee2f5b in KateDocument::paste (this=0x199d150, view=0x1aa6630) at /build/src/tdelibs/kate/part/katedocument.cpp:3249 #11 0x00007f5853f1aa53 in KateView::paste (this=0x1aa6630) at /build/src/tdelibs/kate/part/kateview.cpp:1597 #12 0x00007f5853f4a102 in KateViewInternal::mouseReleaseEvent (this=0x1a66ce0, e=0x7fffc96067b0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:2965 #13 0x00007f5859de2343 in TQWidget::event (this=0x1a66ce0, e=0x7fffc96067b0) at kernel/qwidget.cpp:4725 #14 0x00007f5859d4c559 in TQApplication::internalNotify (this=0x7fffc9607010, receiver= 0x1a66ce0, e=0x7fffc96067b0) at kernel/qapplication.cpp:2638 #15 0x00007f5859d4bbe3 in TQApplication::notify (this=0x7fffc9607010, receiver=0x1a66ce0, e=0x7fffc96067b0) at kernel/qapplication.cpp:2424 #16 0x00007f585ad045c4 in KApplication::notify (this=0x7fffc9607010, receiver=0x1a66ce0, event=0x7fffc96067b0) at /build/src/tdelibs/tdecore/kapplication.cpp:583 #17 0x00007f5859cde6b3 in TQApplication::sendSpontaneousEvent (receiver=0x1a66ce0, event=0x7fffc96067b0) at kernel/ntqapplication.h:526 #18 0x00007f5859cd7f53 in TQETWidget::translateMouseEvent (this=0x1a66ce0, event=0x7fffc9606cc0) at kernel/qapplication_x11.cpp:4380 #19 0x00007f5859cd5871 in TQApplication::x11ProcessEvent (this=0x7fffc9607010, event=0x7fffc9606cc0) at kernel/qapplication_x11.cpp:3557 #20 0x00007f5859cf0c44 in TQEventLoop::processEvents (this=0x18e3e80, flags=4) at kernel/qeventloop_x11.cpp:195 #21 0x00007f5859d5f818 in TQEventLoop::enterLoop (this=0x18e3e80) at kernel/qeventloop.cpp:201 #22 0x00007f5859d5f6e9 in TQEventLoop::exec (this=0x18e3e80) at kernel/qeventloop.cpp:148 #23 0x00007f5859d4c689 in TQApplication::exec (this=0x7fffc9607010) at kernel/qapplication.cpp:2761 #24 0x00007f585e0303a8 in kdemain (argc=1, argv=0x7fffc96075e8) at /build/src/tdebase/kate/app/kwritemain.cpp:692 #25 0x000000000040082c in main (argc=1, argv=0x7fffc96075e8) at /build/src/build/kate/app/kwrite_tdeinit_executable.cpp:2 (gdb) -- David C. Rankin, J.D.,P.E.

12 years, 11 months

kwrite Crash - Now Down To 3/29 -> 4/1 (this may not be good -- gcc to blame?)

by David C. Rankin

Tim, Darrell, All: I rebuilt TDE from 4/1 sources with full debug in attempt to further look into the kwrite crash that Darrell and I have experienced with TDE built on gcc 4.7. With this build, if it is a source/bad patch/tde issue, then with my 3/29 build giving no crash and my 4/1 build crashing, that would point to some problem in between those two dates. However, I am coming around to the thought that -- this isn't a TDE problem and is more likely a problem introduced by the gcc 4.7 interpretation of the TDE code. I will still have to build the 3/29 sources with gcc 4.7 to confirm that to be the case. I have 3/29 binaries that work fine (which I'm fairly sure were built on gcc 4.7, but I can't remember). If I rebuild with gcc47 on the 3/29 sources and get the same failure -- that, in my mind, conclusively points to the problem being gcc47. If that is the case -- how in the heck do you debug something like that? I don't even know where to begin. (well, I do, but that's by asking). So with full debug packages built, on the 4/1 sources, I get the following backtrace. If this doesn't point to anything specific, then all we can do is wait on the 3/29 build to finish. Let me know if you see anything in this backtrace: 0x00007f1723b65947 in KateLineRange (this=0x7ffffcad3100) at /build/src/tdelibs/kate/part/katelinerange.h:25 25 /build/src/tdelibs/kate/part/katelinerange.h: No such file or directory. (gdb) bt #0 0x00007f1723b65947 in KateLineRange (this=0x7ffffcad3100) at /build/src/tdelibs/kate/part/katelinerange.h:25 #1 KateViewInternal::range (this=this@entry=0x152c5d0, realLine=realLine@entry=4, previous=previous@entry=0x0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1308 #2 0x00007f1723b66b32 in KateViewInternal::range (this=this@entry=0x152c5d0, realLine=4, viewLine=viewLine@entry=1) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1418 #3 0x00007f1723b66fd3 in KateViewInternal::nextRange (this=this@entry=0x152c5d0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1391 #4 0x00007f1723b6ec7f in KateViewInternal::cursorDown (this=0x152c5d0, sel=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1772 #5 0x00007f1723b4bc9c in KateView::tqt_invoke (this=0x173dac0, _id=172, _o=0x7ffffcad3370) at /build/src/build/kate/part/kateview.moc:772 #6 0x00007f17299d0d35 in TQObject::activate_signal (this=0x16805c0, clist=0x14729f0, o=0x7ffffcad3370) at kernel/qobject.cpp:2383 #7 0x00007f17299d0bbb in TQObject::activate_signal (this=0x16805c0, signal=2) at kernel/qobject.cpp:2352 #8 0x00007f172ba21a24 in KAction::tqt_invoke (this=0x16805c0, _id=15, _o=0x7ffffcad3480) at /build/src/build/tdeui/kaction.moc:216 #9 0x00007f17299d0d35 in TQObject::activate_signal (this=0x172ae50, clist=0x16d2780, o=0x7ffffcad3480) at kernel/qobject.cpp:2383 #10 0x00007f17299d0bbb in TQObject::activate_signal (this=0x172ae50, signal=2) at kernel/qobject.cpp:2352 #11 0x00007f172a9bacc5 in KAccelPrivate::emitActivatedSignal ( this=this@entry=0x172ae50, pAction=0x14b2fa0) at /build/src/tdelibs/tdecore/kaccel.cpp:403 #12 0x00007f172a9bc8db in KAccelPrivate::eventFilter (this=0x172ae50, pEvent= 0x7ffffcad3ab0) at /build/src/tdelibs/tdecore/kaccel.cpp:373 #13 0x00007f17299ce4cc in TQObject::activate_filters (this=0x152c5d0, e=0x7ffffcad3ab0) at kernel/qobject.cpp:930 #14 0x00007f17299ce326 in TQObject::event (this=0x152c5d0, e=0x7ffffcad3ab0) at kernel/qobject.cpp:762 #15 0x00007f1729a06237 in TQWidget::event (this=0x152c5d0, e=0x7ffffcad3ab0) at kernel/qwidget.cpp:4701 #16 0x00007f1729970559 in TQApplication::internalNotify (this=0x7ffffcad4170, receiver=0x152c5d0, e=0x7ffffcad3ab0) at kernel/qapplication.cpp:2638 #17 0x00007f172996f9eb in TQApplication::notify (this=0x7ffffcad4170, receiver=0x152c5d0, e=0x7ffffcad3ab0) at kernel/qapplication.cpp:2395 ---Type <return> to continue, or q <return> to quit--- #18 0x00007f172a92a844 in KApplication::notify (this=0x7ffffcad4170, receiver=0x152c5d0, event=0x7ffffcad3ab0) at /build/src/tdelibs/tdecore/kapplication.cpp:583 #19 0x00007f172a9b8f88 in sendEvent (event=0x7ffffcad3ab0, receiver=<optimized out>) at /opt/tqt3/include/ntqapplication.h:523 #20 KAccelEventHandler::x11Event (this=<optimized out>, pEvent=<optimized out>) at /build/src/tdelibs/tdecore/kaccel.cpp:147 #21 0x00007f172a92c5a8 in publicx11Event (e=0x7ffffcad3e20, this=<optimized out>) at /build/src/tdelibs/tdecore/kapplication.cpp:1782 #22 KApplication::x11EventFilter (this=0x7ffffcad4170, _event=0x7ffffcad3e20) at /build/src/tdelibs/tdecore/kapplication.cpp:2094 #23 0x00007f17298ef48f in qt_x11EventFilter (ev=0x7ffffcad3e20) at kernel/qapplication_x11.cpp:422 #24 0x00007f17298f929a in TQApplication::x11ProcessEvent (this=0x7ffffcad4170, event=0x7ffffcad3e20) at kernel/qapplication_x11.cpp:3422 #25 0x00007f1729914c44 in TQEventLoop::processEvents (this=0x1378ec0, flags=4) at kernel/qeventloop_x11.cpp:195 #26 0x00007f1729983818 in TQEventLoop::enterLoop (this=0x1378ec0) at kernel/qeventloop.cpp:201 #27 0x00007f17299836e9 in TQEventLoop::exec (this=0x1378ec0) at kernel/qeventloop.cpp:148 #28 0x00007f1729970689 in TQApplication::exec (this=0x7ffffcad4170) at kernel/qapplication.cpp:2761 #29 0x00007f172dc5f3a8 in kdemain (argc=1, argv=0x7ffffcad4748) at /build/src/tdebase/kate/app/kwritemain.cpp:692 #30 0x000000000040082c in main (argc=1, argv=0x7ffffcad4748) at /build/src/build/kate/app/kwrite_tdeinit_executable.cpp:2 (gdb) -- David C. Rankin, J.D.,P.E.

12 years, 12 months

Odd FTBFS in kdepim 3.5.13

by Francois Andriot

Hello, I'm trying to rebuild kdepim 3.5.13 on redhat-based distributions, and on some variants, I get an FTBFS, not on other. It used to work before, so I'm disappointed. The FTBFS is: (taken from RHEL 5 x86) ---------- [ 1%] Building CXX object ktnef/gui/CMakeFiles/ktnef.dir/attachpropertydialogbase.cpp.o cd /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui && /usr/lib/ccache/c++ -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i686 -mtune=generic -fasynchronous-unwind-tables -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui -I/home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/ktnef -I/home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/libkdepim -I/opt/trinity/include -I/usr/lib/qt-3.3/include -I/opt/trinity/include/tqt -o CMakeFiles/ktnef.dir/attachpropertydialogbase.cpp.o -c /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp: In constructor 'AttachPropertyDialogBase::AttachPropertyDialogBase(QWidget*, const char*, bool, uint)': /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:101: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:102: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:103: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:104: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:105: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:105: error: incomplete type 'KListView' used in nested name specifier /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:107: error: no matching function for call to 'QGridLayout::addMultiCellWidget(KListView*&, int, int, int, int)' /usr/lib/qt-3.3/include/qlayout.h:336: note: candidates are: void QGridLayout::addMultiCellWidget(QWidget*, int, int, int, int, int) /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp: In member function 'virtual void AttachPropertyDialogBase::languageChange()': /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:149: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.cpp:150: error: invalid use of undefined type 'struct KListView' /home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build/ktnef/gui/attachpropertydialogbase.h:21: error: forward declaration of 'struct KListView' make[2]: *** [ktnef/gui/CMakeFiles/ktnef.dir/attachpropertydialogbase.cpp.o] Error 1 make[2]: Leaving directory `/home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build' make[1]: *** [ktnef/gui/CMakeFiles/ktnef.dir/all] Error 2 make[1]: Leaving directory `/home/albator/rpmbuild/BUILD/BUILD.el5.i386/kdepim/build' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.53807 (%build) ---------- When looking in "attachpropertydialogbase.cpp", I see that it lacks the line: "#include <klistview.h> . That's why it fails. In a working build environment, the same file contains the include, and it compiles correctly. It looks like the "attachpropertydialogbase.cpp" and "attachpropertydialogbase.h" are both autogenerated with "uic". I tried running "uic" manually in both build environment, and I confirm that in one case, I get the "#include <klistview.h>", and in another case, i do not get it, and then it FTBFS. What could cause a different behaviour in the uic utility ? (Note: both build environment have same QT, kdelibs, etc ... versions) Thanks François

12 years, 12 months

nm-applet kwallet problem

by Jay

While using nm-applet from network manager i have a problem. I am not sure if kwallet is to blame or NM is not calling gnome-keyring. Perhaps NM does not recognize TDE as a desktop due to some environment variable not exported or something? After restarting the nm-applet and trying to connect it spews out this: root@porteus:~# nm-applet ** Message: applet now removed from the notification area ** Message: applet now embedded in the notification area ** (nm-applet:2383): WARNING **: Failed to register as an agent: (32) No session found for uid 0 ** Message: Starting applet secret agent because GNOME Shell disappeared ** (nm-applet:2383): WARNING **: Failed to register as an agent: (32) No session found for uid 0 ** (nm-applet:2383): WARNING **: Could not initialize NMActiveConnection /org/freedesktop/NetworkManager/ActiveConnection/0: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (nm-applet:2383): CRITICAL **: applet_get_connection_for_active: assertion `path != NULL' failed ** (nm-applet:2383): WARNING **: Could not create object for /org/freedesktop/NetworkManager/ActiveConnection/0: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist So while it senses all networks when i try to connect i do not get the popup asking for passphrase. If i edit the config file for NM with a plain text password it connects without issue. Any ideas? Jay

12 years, 12 months

sftp-kio - still fails in R14 - Any progress? (log captured - may help?)

by David C. Rankin

All, Another critical issue that should be a priority for the R14 release is to finally have a working sftp. I just check and it is still broken: http://www.3111skyline.com/dl/dt/trinity/ss/sftp-kio-err.jpg However, I did capture a log from the command line that might help. It looks like there is a blank field '' that might be the culprit. http://www.3111skyline.com/dl/dt/tde/err/sftp-kio/sftp-output.txt Can someone give me a functional flow as to how the sftp-kio gets called? I doubt I'll be able to do anything, but at least I can look.... -- David C. Rankin, J.D.,P.E.

12 years, 12 months

BSD moves from kde4 -> kde3 in latest releases (on Qt4)

by David C. Rankin

All, I found this a very interesting tidbit posted by Felix Miata on the opensuse kde3 list this morning. According to distrowatch, BSD has gone from kde4 back to kde3 for both its release 9 and 10 due out this month. It has also gone back to FF 3.6: <quote> I was looking over distrowatch, opened the BSD page, and noticed some interesting data points: Version 8.1 8.2 9.0 9 10 Released 2010/07 2011/02 2012/01 2012/05 2012/05 Firefox 3.6.4 3.6.13 9.0.1 3.6.28 3.6.28 K3B 1.0.5 2.0.2 2.0.2 1.0.5 1.0.5 KDE 4.4.5 4.5.5 4.7.3 3.5.10 3.5.10 QT 4.6.3 4.7.1 4.7.4 4.7.4 4.7.4 Samba 3.4.8 3.5.6 3.6.1 3.6.4 3.6.4 T Bird 3.0.5 3.1.7 9.0 3.1.20 3.1.20 </quote> This caught my eye for a number of reasons. First, it is a major distro shifting back to kde3. This bodes well for TDE for a number of reasons (a) additional patch collaboration, (b) Qt3 -> Qt4 development experience. I do not know what the details are, but if BSD has ported the kde3 kwin widget set/styles/etc.. that should make it much easier for someone to build a prototype of TDE on the current kwin as Martin discussed. Next, the Mozilla downgrades were of interest as well. The current releases seem to take quite a bit of CPU and require manual maintenance to vacuum and reindex the sqlite databases to prevent them from growing wildly. (if you haven't checked your firefox and tbird profiles lately, then cd into you .mozilla/firefox/<blah349.default> and .thunderbird/<blah349.default> directories and then 'ls -al *.sqlite'). You will be surprised what you find. You can repair them with: for i in *.sqlite; do sqlite3 $i vacuum; sqlite3 $i reindex; done But I digress. The point being, between BSD, opensuse and others either returning to, or presently maintaining, kde3, the opportunities for advancing TDE become better and better each day. It might be a good idea to open up channels of communication between the developers so that everyone can benefit from the good work done by the kde/tde community as a whole. -- David C. Rankin, J.D.,P.E.

12 years, 12 months

TIME Frame 3/29 -> 4/10 kwrite crash introduced

by David C. Rankin

Tim, All, I have completed downgrading through the sets of binaries I have and from that I can summize that this bug was introduced sometime between 3/29 and 4/10. In my 3/29 build, kwrite is fine. In my 4/10 build, this bug effects kwrite, kate, all editors EXCEPT kedit. In kedit, I can continue to paste away without any crash (I'm sure it makes no use of katepart...) So that is the best I can do in narrowing it down rapidly from existing binaries I have. Darrell, do you have any binaries between 3/29 and 4/10 that could help narrow? There were a ton of changes that went into the GIT tree for tdelibs and tdebase during that two week period. It would be great if we could further narrow it by simply loading binaries rather going through all the commits... I've updated 979 with the info. -- David C. Rankin, J.D.,P.E.

12 years, 12 months

Narrowed Time Frame 3/29->4/3 kwrite crash -> Looks like Qt3 bug

by David C. Rankin

Tim, Darrell, All, I rebuilt all packages this morning with sources from 4/3 to help narrow down the kwrite crash issue. The files were built with full debug information. I don't know if this new backtrace is useful, but it is different from the prior backtraces in that it points straight at tqt3. (at least to me) I can't interpret exactly what it is saying, but I'll let the experts decide: Loaded symbols for /lib/libnss_files.so.2 0xb69ebb20 in __x86.get_pc_thunk.bx () from /opt/tqt3/lib/libtqt-mt.so.3 (gdb) bt #0 0xb69ebb20 in __x86.get_pc_thunk.bx () from /opt/tqt3/lib/libtqt-mt.so.3 #1 0xb6a12d77 in category (c=...) at ../include/private/qunicodetables_p.h:99 #2 0xb6d89361 in isSpace (ch=...) at tools/qunicodetables_p.h:218 #3 0xb6d7e96f in TQChar::isSpace (this=0x8d8d810) at tools/qstring.cpp:475 #4 0xb5270346 in KateRenderer::textWidth (this=0x8b4e400, textLine=..., startcol=0, maxwidth=751, needWrap=0xbfae53d8, endX=0xbfae53cc) at /build/src/tdelibs/kate/part/katerenderer.cpp:806 #5 0xb524dd97 in KateViewInternal::range (this=0x8bc5e20, realLine=0, previous=0x0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1331 #6 0xb524f1ae in KateViewInternal::range (this=0x8bc5e20, realLine=0, viewLine=1) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1418 #7 0x08bc5e20 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) A strace was also run and I've attached that to bug 979. http://bugs.pearsoncomputing.net/attachment.cgi?id=576 I also get a lot of undefined symbol messages when strace is running. I don't know if this will help, but maybe it provides a clue. IIRC, there was a name mangling patch that went it at some time around here. This is what gets dumped to konsole: 13:52 tdepv:~> strace -o vbh/tde/err/kwrite/strace0403.txt kwrite /opt/tqt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN14TQInputContext11sendIMEventEN7TQEvent4TypeERK8TQStringii /opt/tqt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN14TQInputContext14x11FilterEventEP8TQWidgetP7_XEvent /opt/tqt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN14TQInputContext11filterEventEPK7TQEvent /opt/tqt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN14TQInputContext11sendIMEventEN7TQEvent4TypeERK8TQStringii /opt/tqt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN14TQInputContext14x11FilterEventEP8TQWidgetP7_XEvent /opt/tqt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN14TQInputContext11filterEventEPK7TQEvent /opt/tqt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN14TQInputContext11sendIMEventEN7TQEvent4TypeERK8TQStringii /opt/tqt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN14TQInputContext14x11FilterEventEP8TQWidgetP7_XEvent /opt/tqt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN14TQInputContext11filterEventEPK7TQEvent /opt/tqt3/plugins/inputmethods/libqimsw-multi.so: undefined symbol: _ZN14TQInputContext11sendIMEventEN7TQEvent4TypeERK8TQStringii /opt/tqt3/plugins/inputmethods/libqsimple.so: undefined symbol: _ZN14TQInputContext14x11FilterEventEP8TQWidgetP7_XEvent /opt/tqt3/plugins/inputmethods/libqxim.so: undefined symbol: _ZN14TQInputContext11filterEventEPK7TQEvent <snip> (see attached file for remainder) I also tested kate - same crash! I don't know what Darrell is doing, he must be living right! I just pasted 'undefined symbol ' into line one until it would make it wrap and then on the next paste - wham! > crashed. This backtrace is a bit different, the qt3 error I saw in kwrite appears masked for some reason?? Here is the kate crash backtrace: Loaded symbols for /opt/tqt3/plugins/inputmethods/libqimsw-none.so 0xb620dd36 in TQChar::row (this=0x9f4c300) at ../include/ntqstring.h:221 221 ../include/ntqstring.h: No such file or directory. (gdb) bt #0 0xb620dd36 in TQChar::row (this=0x9f4c300) at ../include/ntqstring.h:221 #1 0xb620dd88 in category (c=...) at ../include/private/qunicodetables_p.h:104 #2 0xb6584361 in isSpace (ch=...) at tools/qunicodetables_p.h:218 #3 0xb657996f in TQChar::isSpace (this=0x9f4c300) at tools/qstring.cpp:475 #4 0xb5503346 in KateRenderer::textWidth (this=0x9fc6260, textLine=..., startcol=0, maxwidth=555, needWrap=0xbf887a08, endX=0xbf8879fc) at /build/src/tdelibs/kate/part/katerenderer.cpp:806 #5 0xb54e0d97 in KateViewInternal::range (this=0xa08e128, realLine=0, previous=0x0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1331 #6 0xb54e21ae in KateViewInternal::range (this=0xa08e128, realLine=0, viewLine=1) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1418 #7 0x0a08e128 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) What say the experts? Anything look like it points to anything specific? Worth running a strace on kate? I also found another bug in the setup wizard when choosing keramik style -- you get no window decorations. (this may be fixed since this was the 4/3 code). Plastik works fine. I had deleted ksycoca and my ~/.trinity profile for this test, so I was starting over from scratch. I thought I would pass that along as well. -- David C. Rankin, J.D.,P.E.

12 years, 12 months

TDE spring fundraiser success!

by Timothy Pearson

I know many of you are not subscribed to the trinity-announce list, so here is a link to the 2012 fundraiser completion announcement: http://trinity-announce.pearsoncomputing.net/?0::22 Tim

12 years, 12 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels