tde-devels

devels@trinitydesktop.org

4 participants
3812 discussions

Re: [trinity-devel] kwrite crash - it is tdelibs! (tqt3-46, tdelibs-47, tdebase-46 => crash)
by Timothy Pearson 05 May '12

05 May '12

> Darn. I was running out the door when I wrote that; I'll try to get something better to you later. > All of these crashes appear to be the result of a TQString passed by reference from katerenderer.cpp that is disappearing before it is fully processed. > Tim Try the attached patch please. :-) Tim

2 1

kwrite crash - it is tdelibs! (tqt3-46, tdelibs-47, tdebase-46 => crash)
by David C. Rankin 04 May '12

04 May '12

Tim, Darrell, All, tdelibs is the package that causes the kwrite/kate/etc.. crash when built on gcc 47. The backtrace is good this time and points to: at (i=<optimized out>, this=<optimized out>) at /opt/tqt3/include/ntqstring.h:641 641 { return i < d->len ? d->unicode[i] : TQChar::null; } (full backtrace below) This last night/this morning I build gcc 4.6 and gcc 4.7 packages from 5/3 GIT sources. The test was as follows (removing ksycoca between each): (1) I installed the gcc 4.6 packages -- no crash occurred. (2) installed tqt3 built on gcc 4.7 -- no crash occurred. (3) uninstalled tqt3, reinstalled tqt3 built on gcc 4.6 (4) installed tdelibs built on gcc 4.7 -- kwrite CRASH ** Note: tdelibs built on gcc 4.7 is 9.64 MIB larger than when built on gcc 4.6 A summary of the test is in the following chart: tqt3-46 tdelibs-46 tdebase-46 tqt3-47 tdelibs-47 tdebase-47 tqt3-46 -- OK OK ++ CRASH no test tdelibs-46 OK -- OK OK ++ no test tdebase-46 OK OK -- OK CRASH ++ FULL BACKTRACE: at (i=<optimized out>, this=<optimized out>) at /opt/tqt3/include/ntqstring.h:641 641 { return i < d->len ? d->unicode[i] : TQChar::null; } (gdb) bt #0 at (i=<optimized out>, this=<optimized out>) at /opt/tqt3/include/ntqstring.h:641 #1 operator[] (this=<optimized out>, i=<optimized out>) at /opt/tqt3/include/ntqstring.h:642 #2 width (tabWidth=<optimized out>, italic=<optimized out>, bold=<optimized out>, col=<optimized out>, text=..., this=<optimized out>) at /build/src/tdelibs/kate/part/katefont.h:67 #3 width (tabWidth=<optimized out>, col=<optimized out>, text=..., fs=..., this=<optimized out>) at /build/src/tdelibs/kate/part/kateattribute.h:55 #4 KateRenderer::textWidth (this=0x22fc280, textLine=..., startcol=0, maxwidth=817, needWrap=0x7fff8df70e98, endX=0x7fff8df70e8c) at /build/src/tdelibs/kate/part/katerenderer.cpp:797 #5 0x00007fe5ae37f674 in KateViewInternal::range (this=this@entry=0x23fa0c0, realLine=realLine@entry=0, previous=previous@entry=0x0) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1331 #6 0x00007fe5ae380b32 in KateViewInternal::range (this=this@entry=0x23fa0c0, realLine=0, viewLine=viewLine@entry=1) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1418 #7 0x00007fe5ae3824c9 in KateViewInternal::viewLineOffset (this=this@entry=0x23fa0c0, virtualCursor=..., offset=0, keepX=keepX@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:1578 #8 0x00007fe5ae385d25 in KateViewInternal::makeVisible (this=this@entry=0x23fa0c0, c=..., endCol=117, force=force@entry=false, center=center@entry=false, calledExternally=calledExternally@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:781 #9 0x00007fe5ae386352 in KateViewInternal::updateCursor (this=this@entry=0x23fa0c0, newCursor=..., force=force@entry=true, center=center@entry=false, calledExternally=calledExternally@entry=false) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:2204 #10 0x00007fe5ae38a4c0 in KateViewInternal::editEnd (this=0x23fa0c0, editTagLineStart=0, editTagLineEnd=<optimized out>, tagFrom=<optimized out>) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:3385 #11 0x00007fe5ae326ef0 in KateDocument::editEnd (this=0x232f2c0) at /build/src/tdelibs/kate/part/katedocument.cpp:1032 #12 0x00007fe5ae320f5b in KateDocument::paste (this=0x232f2c0, view=0x24352e0) at /build/src/tdelibs/kate/part/katedocument.cpp:3249 #13 0x00007fe5ae358a53 in KateView::paste (this=0x24352e0) at /build/src/tdelibs/kate/part/kateview.cpp:1597 #14 0x00007fe5ae388102 in KateViewInternal::mouseReleaseEvent (this=0x23fa0c0, e=0x7fff8df71920) at /build/src/tdelibs/kate/part/kateviewinternal.cpp:2965 #15 0x00007fe5b424b0b3 in TQWidget::event (this=0x23fa0c0, e=0x7fff8df71920) at kernel/qwidget.cpp:4725 #16 0x00007fe5b41b5f9d in TQApplication::internalNotify (this=0x7fff8df71ff0, receiver=0x23fa0c0, e=0x7fff8df71920) at kernel/qapplication.cpp:2638 #17 0x00007fe5b41b5627 in TQApplication::notify (this=0x7fff8df71ff0, receiver=0x23fa0c0, e=0x7fff8df71920) at kernel/qapplication.cpp:2424 #18 0x00007fe5b5177894 in KApplication::notify (this=0x7fff8df71ff0, receiver=0x23fa0c0, event=0x7fff8df71920) at /build/src/tdelibs/tdecore/kapplication.cpp:583 #19 0x00007fe5b4148e59 in TQApplication::sendSpontaneousEvent (receiver=0x23fa0c0, event=0x7fff8df71920) at kernel/ntqapplication.h:526 #20 0x00007fe5b4142735 in TQETWidget::translateMouseEvent (this=0x23fa0c0, event=0x7fff8df71ce0) at kernel/qapplication_x11.cpp:4380 #21 0x00007fe5b414005d in TQApplication::x11ProcessEvent (this=0x7fff8df71ff0, event=0x7fff8df71ce0) at kernel/qapplication_x11.cpp:3557 #22 0x00007fe5b415b2c8 in TQEventLoop::processEvents (this=0x2272f90, flags=4) at kernel/qeventloop_x11.cpp:195 #23 0x00007fe5b41c9118 in TQEventLoop::enterLoop (this=0x2272f90) at kernel/qeventloop.cpp:201 #24 0x00007fe5b41c8fe9 in TQEventLoop::exec (this=0x2272f90) at kernel/qeventloop.cpp:148 #25 0x00007fe5b41b60cd in TQApplication::exec (this=0x7fff8df71ff0) at kernel/qapplication.cpp:2761 #26 0x00007fe5b84f1448 in kdemain (argc=1, argv=0x7fff8df72688) at /build/src/tdebase/kate/app/kwritemain.cpp:692 #27 0x00000000004007a4 in main (argc=1, argv=0x7fff8df72688) at /build/src/build/kate/app/kwrite_tdeinit_executable.cpp:2 (gdb) I think this should help isolate where the crash is coming from. I will need to punt to the experts. This backtrace seems to point to the crash in kate/part, but I don't understand why it is blowing up in tqt3. That's where you experts will have to figure it out. Let me know if you want additional tests. I have my box set up for it now, so all you have to do it tell me what to run. Let's get this bug squashed and R14 will be the best and most up-to-date release ever! -- David C. Rankin, J.D.,P.E.

2 3

No WILD GEESE gcc 4.7 => kwrite/kate crash, gcc 4.6 current code == All Good!
by David C. Rankin 04 May '12

04 May '12

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.

2 3

kwrite crash - it's gcc 4.7 - rebuilt 3/29 sources on gcc 4.7 - same crash
by David C. Rankin 03 May '12

03 May '12

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.

4 17

kwrite Crash - Now Down To 3/29 -> 4/1 (this may not be good -- gcc to blame?)
by David C. Rankin 03 May '12

03 May '12

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.

3 6

Odd FTBFS in kdepim 3.5.13
by Francois Andriot 03 May '12

03 May '12

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

1 0

nm-applet kwallet problem
by Jay 03 May '12

03 May '12

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

1 0

sftp-kio - still fails in R14 - Any progress? (log captured - may help?)
by David C. Rankin 02 May '12

02 May '12

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.

10 64

BSD moves from kde4 -> kde3 in latest releases (on Qt4)
by David C. Rankin 02 May '12

02 May '12

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.

3 3

TIME Frame 3/29 -> 4/10 kwrite crash introduced
by David C. Rankin 01 May '12

01 May '12

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.

4 19

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels