Re: [kde-freebsd] run command
Schaich Alonso writes: > On Wed, 13 Nov 2013 15:29:10 +0100 > Bengt Ahlgren wrote: > >> Ajtim writes: >> >> > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 >> > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >> > KDE 4.11.3 from area51 >> > >> > ALT-F2 or Run Command from Application Launcher Menu open but when I >> > want to write a command it closed. It is not usable. >> > Is it related to almost everything built with clang, please? > > Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with > clang (that is, all of KDE that builds with clang), and the launcher works > fine - it also worked with all versions of KDE>=4.11.1 and FreeBSD-10 since > ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the past > though (thought it was fixed upstream). > >> >> A "me too" - I get the same with kde-4.10.5_1 built on 9.1 with default >> compiler (gcc?). When crashing it says: >> >> Null pointer in call to GeoDataTreeModel::addFeature (parent 0x82ccac048 - >> feature 0x0 ) >> >> Another observation: I often get one or two core files after exiting >> KDE. One kdeinit4.core, and often also an kactivitymanagerd.core. >> Things seem to work, however. >> >> Bengt > > GeoDataTreeModel is from marble, as was written by Adriaan de Groot in the > other reply. > > kactivitymanagerd needed to be built either with gcc>=4.6 (not the base one) > or clang-devel for some time, though that should be done by the port itself > in the meantime (it was back in the clang-3.2 times, 3.3 builds it fine). > > FreeBSD-9.1 ships with clang-3.1 IIRC, so the base clang won't build a working > kactivitymanagerd. Can you rebuild and retry it with WITH_GCC=any? I can certainly try another compiler, but I suspect that it already is built with gcc 4.6: $ strings /usr/local/kde4/bin/kactivitymanagerd | egrep -i "clang|gcc|glib|cxx|c\+\+" libstdc++.so.6 _ZTVN10__cxxabiv117__class_type_infoE _ZTVN10__cxxabiv120__si_class_type_infoE libgcc_s.so.1 /usr/local/lib/gcc46:/usr/local/kde4/lib:/usr/local/lib:/usr/local/lib/qt4 GLIBCXX_3.4 CXXABI_1.3 $ ldd /usr/local/kde4/bin/kactivitymanagerd | egrep -i "clang|gcc|glib|cxx|c\+\+" libstdc++.so.6 => /usr/local/lib/gcc46/libstdc++.so.6 (0x803fe5000) libgcc_s.so.1 => /usr/local/lib/gcc46/libgcc_s.so.1 (0x80450a000) libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x809811000) Bengt ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
Ajtim writes: > On Wednesday 13 November 2013 21:05:04 Bengt Ahlgren wrote: >> Adriaan de Groot writes: >> >> > On Wednesday 13 November 2013 07:21:21 Ajtim wrote: >> >> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 >> >> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 KDE >> > 4.11.3 from >> >> area51 >> >> >> >> ALT-F2 or Run Command from Application Launcher Menu open but >> > when I want to >> >> write a command it closed. It is not usable. Is it related to almost >> >> everything built with clang, please? >> >> >> >> Thank you. >> > >> > I had this behavior when I built Marble with gpsd support: the marble >> > runner crashes, taking krunner with it. After a few tries krunner seems >> > to give up. To see what's crashing, either look in your .xsession-errors >> > or check for core files after starting KDE (clean them up first, then try >> > alt-f2). >> >> Yes, marble seems to be involved. There is a workaround described in >> the FreeBSD forums. If you disable "OpenStreetMap with Marble" in the >> krunner config, it does not crash anymore. >> >> Bengt >> ___ >> kde-freebsd mailing list >> kde-freebsd@kde.org >> https://mail.kde.org/mailman/listinfo/kde-freebsd >> See also http://freebsd.kde.org/ for latest information > > I did disable but "marble" crashed anywhere: > > Application: Marble Virtual Globe (marble), signal: Segmentation fault > [Current thread is 1 (Thread 810014c00 (LWP 101104/marble))] > > Thread 5 (Thread 810006400 (LWP 100374/marble)): > #0 0x0008079aad2a in nanosleep () from /lib/libc.so.7 > #1 0x0008078f2efa in sleep () from /lib/libc.so.7 > #2 0x00080767cc33 in sleep () from /lib/libthr.so.3 > #3 0x00080234928a in KCrash::crashHandler () from > /usr/local/kde4/lib/libkdeui.so.7 > #4 0x000802348492 in KCrash::defaultCrashHandler () from > /usr/local/kde4/lib/libkdeui.so.7 > #5 0x00080767f3db in swapcontext () from /lib/libthr.so.3 > #6 0x00080767efc9 in sigaction () from /lib/libthr.so.3 > #7 0x7003 in ?? () > #8 0x00080767eeb0 in sigaction () from /lib/libthr.so.3 > #9 0x000800e7988d in Marble::GeoWriter::write () from > /usr/local/kde4/lib/libmarblewidget.so.16 > #10 0x00080105dc4c in Marble::BookmarkManager::updateBookmarkFile > () from /usr/local/kde4/lib/libmarblewidget.so.16 > #11 0x00080105d7a7 in Marble::BookmarkManager::loadFile () from > /usr/local/kde4/lib/libmarblewidget.so.16 > #12 0x00427203 in ?? () > #13 0x004254f4 in ?? () > #14 0x00424680 in ?? () > #15 0x0041948f in ?? () > #16 0x00080066b000 in ?? () > #17 0x in ?? () > > Thread 4 (Thread 810008800 (LWP 101101/marble)): > #0 0x0008079abc7a in kevent () from /lib/libc.so.7 > #1 0x000802d1857a in QKqueueFileSystemWatcherEngine::run () from > /usr/local/lib/qt4/libQtCore.so.4 > #2 0x000802c3cddc in QThreadPrivate::start () from > /usr/local/lib/qt4/libQtCore.so.4 > #3 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 > #4 0x in ?? () > > Thread 3 (Thread 810009800 (LWP 101102/marble)): > #0 0x0008079abc7a in kevent () from /lib/libc.so.7 > #1 0x000802d1857a in QKqueueFileSystemWatcherEngine::run () from > /usr/local/lib/qt4/libQtCore.so.4 > #2 0x000802c3cddc in QThreadPrivate::start () from > /usr/local/lib/qt4/libQtCore.so.4 > #3 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 > #4 0x in ?? () > > Thread 2 (Thread 810014400 (LWP 101103/marble)): > #0 0x00080768586c in __error () from /lib/libthr.so.3 > #1 0x000807683d2c in _pthread_cond_wait () from /lib/libthr.so.3 > #2 0x000805d6b3f2 in WTF::TCMalloc_PageHeap::scavengerThread () > from /usr/local/lib/qt4/libQtWebKit.so.4 > #3 0x000805d6b389 in WTF::TCMalloc_PageHeap::runScavengerThread () > from /usr/local/lib/qt4/libQtWebKit.so.4 > #4 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 > #5 0x in ?? () > > Thread 1 (Thread 810014c00 (LWP 101104/marble)): > #0 0x0008079630ca in poll () from /lib/libc.so.7 > #1 0x00080767c873 in poll () from /lib/libthr.so.3 > #2 0x00080b91ba0c in g_main_context_iterate () from > /usr/local/lib/libglib-2.0.so.0 > #3 0x00080b91baf4 in g_main_context_iteration () from > /usr/local/lib/libglib-2.0.so.0 > #4 0x000802d62a0f in QEventDispatcherGlib::processEvents () from > /usr/local/lib/qt4/libQtCore.so.4 > #5 0x000802d33ab7 in QEventLoop::exec () from > /usr/local/lib/qt4/libQtCore.so.4 > #6 0x000802c3ad05 in QThread::exec () from > /usr/local/lib/qt4/libQtCore.so.4 > #7 0x000802c3cddc in QThreadPrivate::start () from > /usr/local/lib/qt4/libQtCore.so.4 > #8 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 > #9 0x in ?? () To clarify: krunner does not crash for me when it is configured to not use marble. Fixing marble is another issu
Re: [kde-freebsd] run command
On Wednesday 13 November 2013 21:05:04 Bengt Ahlgren wrote: > Adriaan de Groot writes: > > > On Wednesday 13 November 2013 07:21:21 Ajtim wrote: > >> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > >> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 KDE > > 4.11.3 from > >> area51 > >> > >> ALT-F2 or Run Command from Application Launcher Menu open but > > when I want to > >> write a command it closed. It is not usable. Is it related to almost > >> everything built with clang, please? > >> > >> Thank you. > > > > I had this behavior when I built Marble with gpsd support: the marble > > runner crashes, taking krunner with it. After a few tries krunner seems > > to give up. To see what's crashing, either look in your .xsession-errors > > or check for core files after starting KDE (clean them up first, then try > > alt-f2). > > Yes, marble seems to be involved. There is a workaround described in > the FreeBSD forums. If you disable "OpenStreetMap with Marble" in the > krunner config, it does not crash anymore. > > Bengt > ___ > kde-freebsd mailing list > kde-freebsd@kde.org > https://mail.kde.org/mailman/listinfo/kde-freebsd > See also http://freebsd.kde.org/ for latest information I did disable but "marble" crashed anywhere: Application: Marble Virtual Globe (marble), signal: Segmentation fault [Current thread is 1 (Thread 810014c00 (LWP 101104/marble))] Thread 5 (Thread 810006400 (LWP 100374/marble)): #0 0x0008079aad2a in nanosleep () from /lib/libc.so.7 #1 0x0008078f2efa in sleep () from /lib/libc.so.7 #2 0x00080767cc33 in sleep () from /lib/libthr.so.3 #3 0x00080234928a in KCrash::crashHandler () from /usr/local/kde4/lib/libkdeui.so.7 #4 0x000802348492 in KCrash::defaultCrashHandler () from /usr/local/kde4/lib/libkdeui.so.7 #5 0x00080767f3db in swapcontext () from /lib/libthr.so.3 #6 0x00080767efc9 in sigaction () from /lib/libthr.so.3 #7 0x7003 in ?? () #8 0x00080767eeb0 in sigaction () from /lib/libthr.so.3 #9 0x000800e7988d in Marble::GeoWriter::write () from /usr/local/kde4/lib/libmarblewidget.so.16 #10 0x00080105dc4c in Marble::BookmarkManager::updateBookmarkFile () from /usr/local/kde4/lib/libmarblewidget.so.16 #11 0x00080105d7a7 in Marble::BookmarkManager::loadFile () from /usr/local/kde4/lib/libmarblewidget.so.16 #12 0x00427203 in ?? () #13 0x004254f4 in ?? () #14 0x00424680 in ?? () #15 0x0041948f in ?? () #16 0x00080066b000 in ?? () #17 0x in ?? () Thread 4 (Thread 810008800 (LWP 101101/marble)): #0 0x0008079abc7a in kevent () from /lib/libc.so.7 #1 0x000802d1857a in QKqueueFileSystemWatcherEngine::run () from /usr/local/lib/qt4/libQtCore.so.4 #2 0x000802c3cddc in QThreadPrivate::start () from /usr/local/lib/qt4/libQtCore.so.4 #3 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 #4 0x in ?? () Thread 3 (Thread 810009800 (LWP 101102/marble)): #0 0x0008079abc7a in kevent () from /lib/libc.so.7 #1 0x000802d1857a in QKqueueFileSystemWatcherEngine::run () from /usr/local/lib/qt4/libQtCore.so.4 #2 0x000802c3cddc in QThreadPrivate::start () from /usr/local/lib/qt4/libQtCore.so.4 #3 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 #4 0x in ?? () Thread 2 (Thread 810014400 (LWP 101103/marble)): #0 0x00080768586c in __error () from /lib/libthr.so.3 #1 0x000807683d2c in _pthread_cond_wait () from /lib/libthr.so.3 #2 0x000805d6b3f2 in WTF::TCMalloc_PageHeap::scavengerThread () from /usr/local/lib/qt4/libQtWebKit.so.4 #3 0x000805d6b389 in WTF::TCMalloc_PageHeap::runScavengerThread () from /usr/local/lib/qt4/libQtWebKit.so.4 #4 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 #5 0x in ?? () Thread 1 (Thread 810014c00 (LWP 101104/marble)): #0 0x0008079630ca in poll () from /lib/libc.so.7 #1 0x00080767c873 in poll () from /lib/libthr.so.3 #2 0x00080b91ba0c in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.0 #3 0x00080b91baf4 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0 #4 0x000802d62a0f in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4 #5 0x000802d33ab7 in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4 #6 0x000802c3ad05 in QThread::exec () from /usr/local/lib/qt4/libQtCore.so.4 #7 0x000802c3cddc in QThreadPrivate::start () from /usr/local/lib/qt4/libQtCore.so.4 #8 0x00080767a4a4 in pthread_create () from /lib/libthr.so.3 #9 0x in ?? () -- Mitja --- http://www.redbubble.com/people.lumiwa ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
Adriaan de Groot writes: > On Wednesday 13 November 2013 07:21:21 Ajtim wrote: >> OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 >> r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 KDE > 4.11.3 from >> area51 >> >> ALT-F2 or Run Command from Application Launcher Menu open but > when I want to >> write a command it closed. It is not usable. Is it related to almost >> everything built with clang, please? >> >> Thank you. > > I had this behavior when I built Marble with gpsd support: the marble > runner crashes, taking krunner with it. After a few tries krunner seems > to give up. To see what's crashing, either look in your .xsession-errors > or check for core files after starting KDE (clean them up first, then try > alt-f2). Yes, marble seems to be involved. There is a workaround described in the FreeBSD forums. If you disable "OpenStreetMap with Marble" in the krunner config, it does not crash anymore. Bengt ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
On Wednesday 13 November 2013 20:29:20 Schaich Alonso wrote: > On Wed, 13 Nov 2013 14:20:39 -0500 > Ajtim wrote: > > > On Wednesday 13 November 2013 18:48:08 Schaich Alonso wrote: > > > On Wed, 13 Nov 2013 15:29:10 +0100 > > > Bengt Ahlgren wrote: > > > > > > > Ajtim writes: > > > > > > > > > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > > > > > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > KDE 4.11.3 from area51 > > > > > > > > > > ALT-F2 or Run Command from Application Launcher Menu open but when I > > > > > want to write a command it closed. It is not usable. > > > > > Is it related to almost everything built with clang, please? > > > > > > Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with > > > clang (that is, all of KDE that builds with clang), and the launcher works > > > fine - it also worked with all versions of KDE>=4.11.1 and FreeBSD-10 > > > since ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the > > > past though (thought it was fixed upstream). > > > > > > > Yes, it is interesting because my installation was so smooth with clang > > except kalzium and avogadro. I am not sure if I had more problems. But now > > I have. > > > > avogadro was fixed earlier today, kalzium works fine since that. > > does klauncher work if you remove marble? I did change settings for klauncher and it works now :). -- Mitja --- http://www.redbubble.com/people.lumiwa ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
On Wed, 13 Nov 2013 14:20:39 -0500 Ajtim wrote: > On Wednesday 13 November 2013 18:48:08 Schaich Alonso wrote: > > On Wed, 13 Nov 2013 15:29:10 +0100 > > Bengt Ahlgren wrote: > > > > > Ajtim writes: > > > > > > > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > > > > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > > KDE 4.11.3 from area51 > > > > > > > > ALT-F2 or Run Command from Application Launcher Menu open but when I > > > > want to write a command it closed. It is not usable. > > > > Is it related to almost everything built with clang, please? > > > > Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with > > clang (that is, all of KDE that builds with clang), and the launcher works > > fine - it also worked with all versions of KDE>=4.11.1 and FreeBSD-10 > > since ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the > > past though (thought it was fixed upstream). > > > > Yes, it is interesting because my installation was so smooth with clang > except kalzium and avogadro. I am not sure if I had more problems. But now > I have. > avogadro was fixed earlier today, kalzium works fine since that. does klauncher work if you remove marble? ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
On Wednesday 13 November 2013 18:48:08 Schaich Alonso wrote: > On Wed, 13 Nov 2013 15:29:10 +0100 > Bengt Ahlgren wrote: > > > Ajtim writes: > > > > > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > > > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > > KDE 4.11.3 from area51 > > > > > > ALT-F2 or Run Command from Application Launcher Menu open but when I > > > want to write a command it closed. It is not usable. > > > Is it related to almost everything built with clang, please? > > Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with > clang (that is, all of KDE that builds with clang), and the launcher works > fine - it also worked with all versions of KDE>=4.11.1 and FreeBSD-10 since > ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the past > though (thought it was fixed upstream). > Yes, it is interesting because my installation was so smooth with clang except kalzium and avogadro. I am not sure if I had more problems. But now I have. -- Mitja --- http://www.redbubble.com/people.lumiwa ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
On Wed, 13 Nov 2013 15:29:10 +0100 Bengt Ahlgren wrote: > Ajtim writes: > > > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > > KDE 4.11.3 from area51 > > > > ALT-F2 or Run Command from Application Launcher Menu open but when I > > want to write a command it closed. It is not usable. > > Is it related to almost everything built with clang, please? Interesting, I have 10-BETA3 r257917 and kde-4.11.3 built completely with clang (that is, all of KDE that builds with clang), and the launcher works fine - it also worked with all versions of KDE>=4.11.1 and FreeBSD-10 since ALPHA1. I had that issue with FreeBSD9-STABLE and KDE-4.10.x in the past though (thought it was fixed upstream). > > A "me too" - I get the same with kde-4.10.5_1 built on 9.1 with default > compiler (gcc?). When crashing it says: > > Null pointer in call to GeoDataTreeModel::addFeature (parent 0x82ccac048 - > feature 0x0 ) > > Another observation: I often get one or two core files after exiting > KDE. One kdeinit4.core, and often also an kactivitymanagerd.core. > Things seem to work, however. > > Bengt GeoDataTreeModel is from marble, as was written by Adriaan de Groot in the other reply. kactivitymanagerd needed to be built either with gcc>=4.6 (not the base one) or clang-devel for some time, though that should be done by the port itself in the meantime (it was back in the clang-3.2 times, 3.3 builds it fine). FreeBSD-9.1 ships with clang-3.1 IIRC, so the base clang won't build a working kactivitymanagerd. Can you rebuild and retry it with WITH_GCC=any? Alonso ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
Ajtim writes: > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > KDE 4.11.3 from area51 > > ALT-F2 or Run Command from Application Launcher Menu open but when I > want to write a command it closed. It is not usable. > Is it related to almost everything built with clang, please? A "me too" - I get the same with kde-4.10.5_1 built on 9.1 with default compiler (gcc?). When crashing it says: Null pointer in call to GeoDataTreeModel::addFeature (parent 0x82ccac048 - feature 0x0 ) Another observation: I often get one or two core files after exiting KDE. One kdeinit4.core, and often also an kactivitymanagerd.core. Things seem to work, however. Bengt ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] run command
On Wednesday 13 November 2013 07:21:21 Ajtim wrote: > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 KDE 4.11.3 from > area51 > > ALT-F2 or Run Command from Application Launcher Menu open but when I want to > write a command it closed. It is not usable. Is it related to almost > everything built with clang, please? > > Thank you. I had this behavior when I built Marble with gpsd support: the marble runner crashes, taking krunner with it. After a few tries krunner seems to give up. To see what's crashing, either look in your .xsession-errors or check for core files after starting KDE (clean them up first, then try alt-f2). [ade] ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
[kde-freebsd] run command
OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 KDE 4.11.3 from area51 ALT-F2 or Run Command from Application Launcher Menu open but when I want to write a command it closed. It is not usable. Is it related to almost everything built with clang, please? Thank you. -- Mitja --- http://www.redbubble.com/people.lumiwa Ap ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
