[kde-testing] and [kde-crazy] KDE4 overlays thread (part 5)

[wrc1944]

OK- the new patch worked for kdelibs, and my usual kde-live package list went OK, now at 4.5.75 (4.6 >= 20101105), except for three packages. (Finally realized I had to unmask upower-0.9.6, otherwise 0.9.5 wanted to downgrade polkit, and was causing a kdelibs confict).

Code: Select all

>>> Emerging (1 of 1) kde-base/activitymanager-9999 from kde
 * Package:    kde-base/activitymanager-9999
 * Repository: kde
 * Maintainer: kde@gentoo.org
 * USE:  amd64 elibc_glibc kernel_linux userland_GNU
>>> Unpacking source...
 * Fetching disabled since 1 hours has not passed since last update.
 * Using existing repository copy at revision 1193996.
 *    working copy: /usr/portage/distfiles/svn-src/kdebase-runtime/runtime

 * Exporting parts of working copy to /var/tmp/portage/kde-base/activitymanager-9999/work/activitymanager-9999
rsync: change_dir "/usr/portage/distfiles/svn-src/kdebase-runtime/runtime/nepomuk/services/activities" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1042) [sender=3.0.7]
 * ERROR: kde-base/activitymanager-9999 failed:
 *   subversion: can't export subdirectory 'nepomuk/services/activities/org.kde.nepomuk.ActivitiesService.xml' to '/var/tmp/portage/kde-base/activitymanager-9999/work/activitymanager-9999/nepomuk/services/activities'.
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_unpack
 *   environment, line 4298:  Called kde4-meta_src_unpack
 *   environment, line 3466:  Called kde4-meta_src_extract
 *   environment, line 3375:  Called die
 * The specific snippet of code:
 *               rsync --recursive ${rsync_options} "${ESVN_WC_PATH}/${kmnamedir}${subdir%/}" "${S}/${targetdir}" || die "${ESVN}: can't export subdirectory '${subdir}' to '${S}/${targetdir}'.";
 * 
 * If you need support, post the output of 'emerge --info =kde-base/activitymanager-9999',
 * the complete build log and the output of 'emerge -pqv =kde-base/activitymanager-9999'.
 * This ebuild used the following eclasses from overlays:
 *   /var/lib/layman/kde/eclass/kde4-meta.eclass
 *   /var/lib/layman/kde/eclass/kde4-base.eclass
 *   /var/lib/layman/kde/eclass/kde4-functions.eclass
 * This ebuild is from an overlay named 'kde': '/var/lib/layman/kde/'
 * The complete build log is located at '/var/log/portage/kde-base:activitymanager-9999:20101107-205257.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/activitymanager-9999/temp/environment'.
 * S: '/var/tmp/portage/kde-base/activitymanager-9999/work/activitymanager-9999'

>>> Failed to emerge kde-base/activitymanager-9999, Log file: 

AND KSYSTEMLOG:

Code: Select all

 [  9%] Building CXX object ksystemlog/src/lib/CMakeFiles/ksystemlog_lib.dir/view.o                                 
/usr/include/qt4/QtCore/qstring.h: In member function 'virtual QString LogModeItemBuilder::createFormattedText(LogLine*) const':
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:66:25: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:74:26: error: within this context
/usr/include/qt4/QtCore/qstring.h: In member function 'virtual QString LogModeItemBuilder::createToolTipText(LogLine*) const':
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:83:25: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:89:26: error: within this context
/usr/include/qt4/QtCore/qstring.h: In member function 'QString LogModeItemBuilder::labelMessageFormat(const QString&, const QString&) const':
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:96:46: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:96:54: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:96:102: error: within this context
/usr/include/qt4/QtCore/qstring.h: In member function 'QString LogModeItemBuilder::messageFormat(const QString&) const':
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:101:36: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:101:46: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:102:36: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:102:45: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:103:36: error: within this context
/usr/include/qt4/QtCore/qstring.h:601:5: error: 'QString::QString(const char*)' is private
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logModeItemBuilder.cpp:103:45: error: within this context
make[2]: *** [ksystemlog/src/lib/CMakeFiles/ksystemlog_lib.dir/logModeItemBuilder.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from /var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/view.cpp:42:0:
/usr/include/ktreewidgetsearchline.h:211:18: warning: 'virtual void KTreeWidgetSearchLine::updateSearch(QTreeWidget*)' was hidden
/var/tmp/portage/kde-base/ksystemlog-9999/work/ksystemlog-9999/ksystemlog/src/lib/logViewFilterWidget.h:80:7: warning:   by 'virtual void LogViewWidgetSearchLine::updateSearch(const QString&)'
make[1]: *** [ksystemlog/src/lib/CMakeFiles/ksystemlog_lib.dir/all] Error 2
make: *** [all] Error 2
emake failed
 * ERROR: kde-base/ksystemlog-9999 failed:
 *   Make failed!
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 4293:  Called kde4-meta_src_compile
 *   environment, line 3347:  Called kde4-base_src_compile
 *   environment, line 2994:  Called cmake-utils_src_compile
 *   environment, line 1197:  Called _execute_optionaly 'src_compile'
 *   environment, line  584:  Called enable_cmake-utils_src_compile
 *   environment, line 1566:  Called cmake-utils_src_make
 *   environment, line 1216:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!"; 

AND MARBLE:

Code: Select all

 Scanning dependencies of target python_module_PyKDE4_marble
[ 99%] [ 99%] [100%] Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o                                                                                                   
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart0.o     
Building CXX object marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o     
In file included from /usr/include/python2.6/Python.h:8:0,                                                         
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart1.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart0.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
In file included from /usr/include/python2.6/Python.h:8:0,
                 from /usr/include/python2.6/sip.h:32,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipAPImarble.h:11,
                 from /var/tmp/portage/kde-base/marble-9999/work/marble-9999_build/marble/src/bindings/python/sip/sipmarblepart2.cpp:7:
/usr/include/python2.6/pyconfig.h:1079:0: warning: "_XOPEN_SOURCE" redefined
<command-line>:0:0: note: this is the location of the previous definition
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewportParams_focusPointIsCenter(PyObject*, PyObject*)':
sipmarblepart1.cpp:3269:30: error: 'class Marble::ViewportParams' has no member named 'focusPointIsCenter'
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewParams_radiusUpdated(PyObject*, PyObject*)':
sipmarblepart1.cpp:4048:30: error: 'class Marble::ViewParams' has no member named 'radiusUpdated'
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewParams_setRadiusUpdated(PyObject*, PyObject*)':
sipmarblepart1.cpp:4074:21: error: 'class Marble::ViewParams' has no member named 'setRadiusUpdated'
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewParams_planetAxisUpdated(PyObject*, PyObject*)':
sipmarblepart1.cpp:4102:53: error: 'class Marble::ViewParams' has no member named 'planetAxisUpdated'
sipmarblepart1.cpp: In function 'PyObject* meth_Marble_ViewParams_setPlanetAxisUpdated(PyObject*, PyObject*)':
sipmarblepart1.cpp:4128:21: error: 'class Marble::ViewParams' has no member named 'setPlanetAxisUpdated'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_RenderPluginInterface_pluginInstance(PyObject*, PyObject*)':
sipmarblepart2.cpp:2171:30: error: 'class Marble::RenderPluginInterface' has no member named 'pluginInstance'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_needsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14310:30: error: 'class Marble::MarbleWidget' has no member named 'needsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setNeedsUpdate(PyObject*, PyObject*)':
sipmarblepart2.cpp:14335:21: error: 'class Marble::MarbleWidget' has no member named 'setNeedsUpdate'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_northPoleY(PyObject*, PyObject*)':
sipmarblepart2.cpp:14363:30: error: 'class Marble::MarbleWidget' has no member named 'northPoleY'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_addPlacemarkFile(PyObject*, PyObject*)':
sipmarblepart2.cpp:14557:41: warning: 'void Marble::MarbleWidget::addPlacemarkFile(const QString&)' is deprecated (declared at /var/tmp/portage/kde-base/marble-9999/work/marble-9999/marble/src/lib/MarbleWidget.h:309)
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_addPlacemarkData(PyObject*, PyObject*)':
sipmarblepart2.cpp:14589:45: warning: 'void Marble::MarbleWidget::addPlacemarkData(const QString&, const QString&)' is deprecated (declared at /var/tmp/portage/kde-base/marble-9999/work/marble-9999/marble/src/lib/MarbleWidget.h:317)
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_removePlacemarkKey(PyObject*, PyObject*)':
sipmarblepart2.cpp:14619:43: warning: 'void Marble::MarbleWidget::removePlacemarkKey(const QString&)' is deprecated (declared at /var/tmp/portage/kde-base/marble-9999/work/marble-9999/marble/src/lib/MarbleWidget.h:324)
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_setProxy(PyObject*, PyObject*)':
sipmarblepart2.cpp:15301:21: error: 'class Marble::MarbleWidget' has no member named 'setProxy'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyHost(PyObject*, PyObject*)':
sipmarblepart2.cpp:15332:42: error: 'class Marble::MarbleWidget' has no member named 'proxyHost'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_proxyPort(PyObject*, PyObject*)':
sipmarblepart2.cpp:15359:30: error: 'class Marble::MarbleWidget' has no member named 'proxyPort'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_user(PyObject*, PyObject*)':
sipmarblepart2.cpp:15386:42: error: 'class Marble::MarbleWidget' has no member named 'user'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_password(PyObject*, PyObject*)':
sipmarblepart2.cpp:15413:42: error: 'class Marble::MarbleWidget' has no member named 'password'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_changeCurrentPosition(PyObject*, PyObject*)':
sipmarblepart2.cpp:16914:21: error: 'class Marble::MarbleWidget' has no member named 'changeCurrentPosition'
sipmarblepart2.cpp: In function 'PyObject* meth_Marble_MarbleWidget_updateGps(PyObject*, PyObject*)':
sipmarblepart2.cpp:16968:21: error: 'class Marble::MarbleWidget' has no member named 'updateGps'
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart1.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/sip/sipmarblepart2.o] Error 1
make[1]: *** [marble/src/bindings/python/CMakeFiles/python_module_PyKDE4_marble.dir/all] Error 2
make: *** [all] Error 2
emake failed
 * ERROR: kde-base/marble-9999 failed:
 *   Make failed!
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 6389:  Called kde4-meta_src_compile
 *   environment, line 3886:  Called kde4-base_src_compile
 *   environment, line 3533:  Called cmake-utils_src_compile
 *   environment, line 1736:  Called _execute_optionaly 'src_compile'
 *   environment, line  738:  Called enable_cmake-utils_src_compile
 *   environment, line 2105:  Called cmake-utils_src_make
 *   environment, line 1755:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!";

Marble is really frustrating to get down to 99-100% finished, and have this happen.

[ComaWhite]

You could just disable python for marble unless you really really need it?

[Shining Arcanine]

I have had this problem in the past too. Have you guys tried recompiling? Usually when this happens to me with KDE, the cause is either a bad ebuild or a bug in portage. In the case of portage, compiling it again and then filing a bug report for zmedico describing the issue in as much detail as possible usually works. In the case of a bad ebuild, fixing it and then filing a bug report with information on how you fixed it usually works for me.

[wrc1944]

Thanks ComaWhite,
USE="-python" emerge marble worked fine. I'm wondering what Marble is losing by disabling python, or more specifically, what features are added or enhanced by having python support?

Shining Arcanine,
I did look on gentoo and kde bugzilla, but found no references to these errors. Seeing as how this is from the kde overlay, I'm unsure if these bugzillas are the correct places to file kde-live bugs. Did I just miss something in the overlay Documentation saying where to report problems other than this forum thread?

[Shining Arcanine]

Thanks ComaWhite,
USE="-python" emerge marble worked fine. I'm wondering what Marble is losing by disabling python, or more specifically, what features are added or enhanced by having python support?

Shining Arcanine,
I did look on gentoo and kde bugzilla, but found no references to these errors. Seeing as how this is from the kde overlay, I'm unsure if these bugzillas are the correct places to file kde-live bugs. Did I just miss something in the overlay Documentation saying where to report problems other than this forum thread?

Gentoo's developers do not patrol the forums for reports regarding issues. The best way to notify them is to file a bug report at bugs.gentoo.org. Be sure to specify in the title that it is regarding the kde overlay and they will be happy to have your report.

[wrc1944]

Update: kde-base/activitymanager-9999 was fixed in svn.

Hmm. Just noticed Dolphin now takes 10 seconds to open, every time, with or without any desktop effects enabled. On closing dolphin, once (not every time) it crashed with:

Code: Select all

 Executable: kdeinit4 PID: 2714 Signal: Aborted (6)

Application: Dolphin (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0x00007fbffa6e67c5 in raise () from /lib/libc.so.6
#7  0x00007fbffa6e7c46 in abort () from /lib/libc.so.6
#8  0x00007fbffa721473 in ?? () from /lib/libc.so.6
#9  0x00007fbffa726906 in ?? () from /lib/libc.so.6
#10 0x00007fbffaabf959 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.1/libstdc++.so.6
#11 0x00007fbffa6e93b1 in ?? () from /lib/libc.so.6
#12 0x00007fbffa6e9405 in exit () from /lib/libc.so.6
#13 0x000000000040703d in _start () 

EDIT: This crash now appears randomly when closing dolphin. Sometimes it closes normally, and i can't tie it to any specific action as of yet. Same thing happens with a completely new user and new ~/.kde4 directory.

Things generally seem more sluggish, but dolphin is the most serious example so far. Kde version 4.5.73 wasn't like this.
EDIT2: More info. When I open dolphin as user from CLI, it still takes 10 seconds, but gives no info output at all. When i close it, it gives this output:

Code: Select all

wrc@amd64 ~ $ dolphin
wrc@amd64 ~ $ QPixmap::scaled: Pixmap is a null pixmap
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(3078)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:

Forgot to mention, same thing happens with Gwenview.

[wrc1944]

Having a tough time with plasma-workspace making sense out of this output. Tried new sources, resync overlay, bugzillas, google, forums, still no luck.

Code: Select all

[ 15%] Generating ui_clockConfig.h
[ 15%] Built target krunner_plasma-desktop
Scanning dependencies of target plasma_applet_clock
Scanning dependencies of target plasma_applet_activitybar
[ 16%] Building CXX object plasma/generic/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/plasma_applet_clock_automoc.o
[ 16%] Building CXX object plasma/generic/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/plasma_applet_activitybar_automoc.o
[ 16%] Building CXX object plasma/generic/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/clock.o
[ 16%] Building CXX object plasma/generic/applets/activitybar/CMakeFiles/plasma_applet_activitybar.dir/activitybar.o
[ 16%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/dashboardview.o
Linking CXX shared module ../../../../lib/plasma_applet_clock.so
Linking CXX shared module ../../../../lib/plasma_applet_activitybar.so
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.1/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lKDEPIMLibs__kholidays
collect2: ld returned 1 exit status
make[2]: *** [lib/plasma_applet_clock.so] Error 1
make[1]: *** [plasma/generic/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 16%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/desktopcorona.o
[ 16%] Built target plasma_applet_activitybar
[ 17%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/desktopview.o
[ 17%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/interactiveconsole.o
[ 17%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/main.o
[ 17%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/panelcontroller.o
[ 17%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/panelview.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/panelapplethandle.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/panelappletoverlay.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/plasmaapp.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/positioningruler.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/activitycontrols.o
[ 18%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/activitymanager.o
[ 19%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/activityicon.o
[ 19%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/activitylist.o
[ 19%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/filterbar.o
[ 19%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/activitymanager/kidenticongenerator.o
[ 19%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/plasma-shell-desktop.o
[ 20%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/appadaptor.o
[ 20%] Building CXX object plasma/desktop/shell/CMakeFiles/kdeinit_plasma-desktop.dir/ksmserver_interface.o
Linking CXX shared library ../../../lib/libkdeinit4_plasma-desktop.so
[ 20%] Built target kdeinit_plasma-desktop
make: *** [all] Error 2
emake failed
 * ERROR: kde-base/plasma-workspace-9999 failed:
 *   Make failed!
 * 
 * Call stack:
 *     ebuild.sh, line   56:  Called src_compile
 *   environment, line 6501:  Called kde4-meta_src_compile
 *   environment, line 3992:  Called kde4-base_src_compile
 *   environment, line 3639:  Called cmake-utils_src_compile
 *   environment, line 1842:  Called _execute_optionaly 'src_compile'
 *   environment, line  844:  Called enable_cmake-utils_src_compile
 *   environment, line 2211:  Called cmake-utils_src_make
 *   environment, line 1861:  Called die
 * The specific snippet of code:
 *           emake "$@" || die "Make failed!"; 

Anyone else seeing this? Happens building against either qt-4.7.9999 or portage qt-4.7.1.

[Stefano Crocco]

Today I decided to switch from Kde 4.5.3 to the live version. Mostly things went well, but I couldn't compile plasma-workspace. The error I keep getting is this:

Code: Select all

/usr/lib/gcc/i686-pc-linux-gnu/4.4.5/../../../../i686-pc-linux-gnu/bin/ld: cannot find -lKDEPIMLibs__kholidays                                                                                            
collect2: ld returned 1 exit status                                                                                                                                                                       
make[2]: *** [lib/plasma_applet_clock.so] Error 1                                                                                                                                                         
make[1]: *** [plasma/generic/applets/analog-clock/CMakeFiles/plasma_applet_clock.dir/all] Error 2

I tried looking around, both in the plasma-workspace sources and in the various cmake modules installed by kdelibs, to find instances of kholidays, but changing what I found to point to the actual path of the file didn't change anything. It seems as if in some cmake file they forgot to enclose KDEPIMLibs__kholidays in braces, so that the makefile contains the name of the variable rather than the value it contains. Unfortunately, I have no idea of where to look for something like that.

Does anyone have any suggestion?

Thanks in advance

[wrc1944]

@Stefano Crocco,
Yeah- I have the same error in my post above at 16%, except mine is an amd64 box.

I too looked around like you did, and tried commenting out the analog clock applet in a CMakeList.txt file, but it didn't help. As you tried a PATH adjustment and that too didn't help, I think you're right and it's got something to do with KDEPIMLibs__kholidays.

I don't really know much (if any) c++, so I'm pretty much limited in hacking on this stuff to editing in what somebody else has figured out . Strangely, my kde-live install seems to function OK even without updating plasma-workspace- guess it's still using the previous 9999 version. I still have the slow 10+ second Dolphin opening problem.

Guess I'll just have to wait until it's fixed in svn.

[laughinggnome]

Stefano and wrc1944, I ran into the same problem and you'll be pleased to hear I've fixed it! I'm not sure it's the "correct" solution, but it works... After a lot of trial and error I worked out that plasma-workspace needs libplasmaclock to be built at the same time. And thanks to our wonderful ebuilds that's very easy to achieve: I removed the libplasmaclock references from the COMMONDEPEND and KMLOADLIBS sections of the plasma-workspace ebuild, and added the plasmaclock directory to the KMEXTRA section.

Code: Select all

KMEXTRA="
        statusnotifierwatcher/
        libs/plasmaclock/
"

I then unmerged liblpasmaclock (and removed it from kdebase-meta and whichever set it was in) and emerged plasma-workspace. Happy days.

[wrc1944]

laughinggnome,
Thanks for posting.
Next time I'll check to see if it's fixed in either svn or the overlay, but if not I'll definitely give this a try.

Seems like it's probably an overlay problem, but if we edit the overlay ebuild I guess it will be over-written on the next sync. In fact, IIRC editing an overlay ebuild causes the layman -s kde command not to work.

However, I don't think I want to get into putting kde-live stuff in another "local" overlay.

[asturm]

However, I don't think I want to get into putting kde-live stuff in another "local" overlay.

For such cases I've always got my bugfix overlay ready. Someone should report this btw via bugzilla [kde]

[Stefano Crocco]

Thanks for the suggestion, it works. I'll try syncing the overlay later today. If nothing changes, I'll post a bug report

[wrc1944]

Yep- plasma-workspace (4.5.80) seems fixed in svn, so no need for the ebuild edit.

However, Ksystemlog still fails with same error oposted above.

EDIT: Just rebooted into kde, Version 4.5.80 (4.6 Beta1), and the 10 second slow Dolphin & Gwenview launch time is still there, on both initial and subsequent tries.

[Earthwings]

USE="-python" emerge marble worked fine. I'm wondering what Marble is losing by disabling python, or more specifically, what features are added or enhanced by having python support?

The python bindings are needed to use the Marble widget (~ the Marble library) from python programs. In examples/python there's a sample python program where you can see that in action.

The python bindings are synced around the beta / release candidates with the Marble API. Before that, compilation errors are to be expected. Simon Edwards (the maintainer of the bindings) recently synced them, so chances are good Marble compiles fine now.

From a user's point of view, the python bindings are very likely not needed since they do not affect the Marble application in any way. Therefore I'd recommend to compile Marble with a deactivated python use flag unless you plan to write or execute python programs embedding a Marble widget.

[wrc1944]

Thanks for the info, Earthwings.
I was wondering why Marble needed a python USE flag. Guess I'll put -python for Marble in /etc/portage/package.use on my kde-live partition, if it still fails with python. Python/Marble works OK in kde-4.5.3 portage.

[NaiL]

Code: Select all

Calculating dependencies \ * A file is not listed in the Manifest: '/var/lib/layman/kde/kde-base/kde-l10n/kde-l10n-4.5.80.ebuild'
 * Missing digest for '/var/lib/layman/kde/kde-base/kde-l10n/kde-l10n-4.5.80.ebuild'
... done!

!!! All ebuilds that could satisfy "kde-base/kde-l10n:4.6" have been masked.
!!! One of the following masked packages is required to complete your request:
- kde-base/kde-l10n-9999::kde (masked by: corruption)
- kde-base/kde-l10n-4.5.9999::kde (masked by: corruption)
- kde-base/kde-l10n-4.5.80::kde (masked by: corruption)
- kde-base/kde-l10n-4.4.9999::kde (masked by: corruption)

(dependency required by "@kde-4.6")

I'm missing something?

[asturm]

No, simply the repo currently broken at that package. Either re-sync and see if it's been solved (could have been you syncing in the middle of an update before or indeed overlooked by the overlay guys), or do the following:

Code: Select all

cd /var/lib/layman/kde/kde-base/kde-l10n/
ebuild kde-l10n-4.5.80.ebuild manifest

[crafty_guy]

kdelibs-4.5.80 ebuild fails to find kdelibs-4.5.80.tar.bz2 in any of the distfile locations. Is this file being hosted someplace??

[asturm]

Ah, I've seen it now. It's nothing unusual that kde beta ebuilds arrive in kde overlay days before actual source tarball availability.

[Finswimmer]

kdelibs-4.5.80 ebuild fails to find kdelibs-4.5.80.tar.bz2 in any of the distfile locations. Is this file being hosted someplace??

http://techbase.kde.org/Schedules/KDE4/ ... _1_Release

--> 24. November

[Stefano Crocco]

Does anyone know what's the current status of KMail 2? Is it supposed to be usable? Will it be included in KDE 4.6?

The reason I'm asking is that since I switched from KDE 4.5 to the svn version little more than one week ago, I've spent large amounts of my free time fighting against KMail 2 to have it work like KMail it used to. However, I found out some issues I couldn't solve. Here they are:

• KMail has huge trouble in dealing with folders containing thousands of e-mails. Every time I selected one such folder, it took a very long time "syncing" the folder, whatever that means. "Very long time" means something from half a minute for folders with about two thousand e-mails to five or ten minutes for folders with thirty thousands e-mails to some hours for a folder with something like 100,000 messages in it. Besides, while doing so, it eats a large amount of resources, sometimes completely freezing the system.
• It treats ignored messages as unread. I'm subscribed to several mailing lists, and it often happens that I see from the beginning that a particular thread doesn't interest me. With KMail 1, in this situation, I marked the whole thread as Ignored and it wouldn't appear anymore either in the list of unread messages or while cycling among unread e-mails using the + key. Now, instead, they still appear in the list of unread messages, and there's no way to make them disappear from there. Even selecting them in the message list marks them as read only temporarily: the next time the foder is synced, they're again marked as unread. At least, they're not taken into account when using the + key to go to the next unread message.
• In my attempts to migrate my old mail folders to KMail 2, I tried removing the old KMail configuration so that KMail 2 would start with default settings. I then manually added a resource pointing to the old mail directory, which was correctly imported. Then, I tried moving the old messages from the original folders to the new ones. And here, things become strange: if I tried to move a single message, it worked. As soon as I tried to move more than one message, nothing happened. Sometimes, after waiting for about a hour, the messages were finally moved. The problem is that all the time KMail stated it was "ready".
• KMail doesn't always keep up to date with itself. For example, I had a folder containing two messages, both unread. I selected one, read it then deleted it. Yet, KMail still showed two unread messages in that folder
  [item] KMail 2 doesn't show the number of unread messages in the system tray icon like KMail 1 did.

I'm not sure whether the issues above are true bugs, known problems which will be resolved before KDE 4.6 is released or are caused by an incorrect configuration. Does anyone has any advice?

Thanks in advance

[Biert]

KDE SC 4.5.80 distfiles are available now, but all manifests are wrong.

[D-Bug]

Code: Select all

[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimporttodoc.dir/excelimporttodoc_automoc.o
[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimporttodoc.dir/ExcelImport.o
[ 78%] Building CXX object filters/kspread/excel/import/CMakeFiles/excelimport.dir/excelimport_automoc.o
In file included from /home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/../sidewinder/swinder.h:25:0,
                 from /home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/ExcelImport.cpp:78:
/home/portage/portage/app-office/koffice-libs-9999/work/koffice-libs-9999/filters/kspread/excel/import/../sidewinder/cell.h:30:36: error fatal: generated/simpleParser.h: Do no exist file or directory

I've edited koffice-libs-9999.ebuild and it's solved build problem for me.

Code: Select all

--- koffice-libs-9999.ebuild    2010-11-25 20:25:47.000000000 +0000
+++ koffice-libs-9999.ebuild    2010-11-25 20:02:14.000000000 +0000
@@ -32,10 +32,12 @@
        doc/thesaurus/
        filters/generic_wrapper/
        filters/libkowmf/
+       filters/libmso/
        filters/libmsooxml/
        filters/xsltfilter/
        filters/kspread/
        kspread/
+       kword/
        interfaces/
        kounavail/
        plugins/

But i've got some file collisions with koffice-data and kchart. Need more examination.

[aminalshmu]

thanks for the tip on building marble with USE="-python" for successful compile. what loss of functionality does that entail, i wonder?