tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

TDE Task Bar Icons
by Darrell Anderson 10 Dec '11

10 Dec '11

In KDE3 the task bar icons stretch from the top of the task bar to the bottom. There is no space above or below the icons. That is, the icons fully fill the task bar from top to bottom. In TDE the icons do not fully fill the task bar. There is a thin space above and below the task bar icons. Are the icon heights configurable in TDE? I'm referring to the task bar only and not the quick launch or system tray icons. Darrell

6 11

Trinity, Gentoo, and packaging
by E. Liddell 09 Dec '11

09 Dec '11

Or: "Lions and tigers and ebuilds, oh my!" Yes, I know there are no official packages for Gentoo yet. I decided to see if I could do something useful by installing what unofficial ones were available and probing for bugs, and possibly rolling a few ebuilds of my own for the packages that haven't gotten any love yet. I used non7top's GitHub fork of Serghei's ebuild repository (at the time I started, the contents of the two were identical, actually) and did manage to get kdebase installed after two ebuild- related hiccups. After that, things started to get complicated, and I ran into a variety of problems. Unfortunately, I haven't been able to decide whether some of them are Trinity bugs, ebuild bugs, or just Gentoo quirks, so I don't know where to file them and need help with the triage. __________________ Problem #1: Unset environment variables When I first booted Trinity, the desktop *appeared* to come up exactly as it should, but most applications would not start, the main menu was nearly empty, and kcontrol had no settings available. After some mucking around, I discovered that there was no mention of the Trinity bin directory in my PATH, and then found that Gentoo set PATH, ROOTPATH, LDPATH, and XDG_DATA_DIRS inside a distro-specific part of starkde (for KDE 3.5.10, that is), so I copy-and-pasted those into the startup file provided. (I know there are some setters in the Trinity startup script. They didn't work, possibly because of Problem #4.) Unfortunately, that didn't fix things--I also needed to set LD_LIBRARY_PATH for programs (including konsole) to start properly, and XDG_DATA_HOME, XDG_CONFIG_HOME, and/or XDG_CONFIG_DIRS (I never tried setting them individually, so I can't narrow it down) to get a working menu and kcontrol. I don't know what changed between KDE 3.5.10 and Trinity 3.5.13 to make the setting of those additional environment variables necessary, so I'm not sure who owns the second half of the bug. __________________ Problem #2: Autotools packages and ebuilds I did manage to write some successful ebuilds (I have most of kdegraphics and kdeartwork working, if anyone wants ebuilds for those, plus kdebase-meta and a variant ksmserver ebuild with a hal useflag), but only for packages that have been ported to CMake. The autotools packages Will Not Work, no matter how I mangle the KDE 3.5.10 ebuilds (rewriting from scratch is not an option, IMAO--the old kde-meta eclass contains several hundred lines of bash script, and spending more than minimal time on a build system that's going away is wasted effort). After a lot of playing around with kdetoys, I was able to figure out that I was running into two problems: a minor change in the tarball structure (not a bug, solved by a 1-line fix), and a set of missing build/config files. The kdetoys-3.5.10 tarball contains a bunch of files at the top level that are missing from its 3.5.13 equivalent: configure.in, acinclude.m4, aclocal.m4, and several other config* and Makefile* files. When I copied these files from the old to the new package, the ebuild got as far as actually configuring/building the package (and, naturally, failed, because the old buildscripts didn't know about TQT, but it was the first iteration that didn't bail out while trying to find the build directory or run eautoreconf/aclocal). I know next to nothing about autotools, so I don't know if those files were removed for a reason. Maybe someone who knows more about autotools and ebuilds could do something without them; I just know that *I* can't. Another thing is that I couldn't seem to get the --without-arts switch to work, but with the ebuilds so messed up to begin with it's difficult to tell whether that's meaningful. __________________ Problem #3: CMake failures Ebuilds for two subapplications of kdeutils that were included in the stuff I took from GitHub failed to build, complaining that they weren't able to find tqt.h (one of them would have been Ark). I don't know whether this is an ebuild or a CMake bug. __________________ Problem #4: startkde/starttrinity and minimal or unusual builds While I was wrestling with Problem #1 above, I had occasion to examine both the new and the old startup scripts in detail, and there were some things in the new one that drew my attention. However, I'm not sure they really qualify as bugs: if [ -d /opt/trinity/games ]; then That, and the lines that follow it, might work fine if Trinity is installed into /opt/trinity/, but Gentoo's practice is to install most software into /usr/. Something like: if [ -d ${KDEDIR}/games ]; then might be more portable. # Make sure a default wallpaper is set. if [ ! -e $kdehome/share/config/kdesktoprc ]; then # With Trinity this file should exist, but test first. if [ -r /usr/share/wallpapers/isadora.png.desktop ]; then cat >$kdehome/share/config/kdesktoprc <<EOF [Desktop0] Wallpaper=isadora.png WallpaperMode=Scaled EOF fi fi Not having a wallpaper set is harmless--these lines seem to add complexity to the script for no good reason (and I don't have a /usr/share/wallpapers, either-- isadora.png is in /usr/kde/3.5/share/wallpapers--so this code isn't portable). Perhaps it belongs in a distro-specific patch? # Configuration of the gtk_qt_engine if not already set. [...] Trinity will run quite happily without gtk-qt-engine installed, so a test needs to be made for that (at minimum--I'd relegate this to "distro-specific" too). # Remove moodin cache if we have a new wallpaper installed, jriddell. Distro-specific. if [ -d $kdehome/share/apps/ksplash/cache/Moodin/kubuntu ]; then if [ /usr/share/wallpapers/kubuntu-wallpaper.png -nt $kdehome/share/apps/ksplash/cache/Moodin/kubuntu/ ]; then rm -rf $kdehome/share/apps/ksplash/cache/Moodin/kubuntu/ fi fi This says right out that it's a Kubuntu patch. It doesn't belong in vanilla Trinity. $KDEDIR/bin/artsshell -q terminate Arts is another optional component that Trinity can operate without, so it shouldn't be shut down without testing to see if it's there. Maybe: if test -e $KDEDIR/bin/artsshell ; then artsshell -q terminate ; fi (The prelinking stuff isn't in my old startup script either, but I suspect that Gentoo may have removed it.) __________________ I think that's everything. The other (minor) bugs I ran into I'm fairly sure I know where to file.

2 7

Porting to cmake.
by L0ner sh4dou 09 Dec '11

09 Dec '11

While searching some info on the net about porting projects from autotools to cmake i have found this: http://techbase.kde.org/Development/Tutorials/KDE4_Porting_Guide#CMake Apparentely they have script that converts automatically .am files to cmake files. I've run it on several not-yet-ported-to-cmake trinity components, and it generated nearly whole CMake files structure. Yet it doesn't generate config.h.cmake file which is needed (without it compilation simply don't happen). I've asked for help on kde-devel irc channel, but without any success (maybe I'll ask later). Whole point is, maybe we could adapt this to generate our cmake files, thus speeding whole porting to cmake?

3 4

Need help with patch
by Darrell Anderson 08 Dec '11

08 Dec '11

Several days ago when I started my koffice nightmare, I submitted bug report 721 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=721). For the poppler warning messages I ran across a patch from Francois. I updated the bug report with a link to the patch already in GIT. Today I ran across the likely cause to the ruby messages: the configure scripts do not support ruby 1.9.x (https://gist.github.com/1414497). I started a patch but still receive the warning message. I'm missing something else but don't know what. Here is the patch: ======================================= diff -urN koffice/configure.in koffice.new/configure.in --- koffice/configure.in 2011-08-21 18:30:53.000000000 -0500 +++ koffice.new/configure.in 2011-12-08 12:56:01.215427952 -0600 @@ -1539,14 +1539,20 @@ # Check for Ruby if test "x$compile_kross" = "xyes" ; then - AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18], ruby) + AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18 ruby1.9 ruby19], ruby) if test -n "$RUBY"; then AC_MSG_CHECKING(for Ruby dirs) RUBY_ARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"archdir"@:>@)'` RUBY_SITEARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitearchdir"@:>@)'` RUBY_SITEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitelibdir"@:>@)'` - RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'` + if test -n "$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'"; then + # Ruby 1.9 + RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'` + else + # not Ruby 1.9 + RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'` + fi RUBY_LIBDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"libdir"@:>@)'` RUBY_LIBRUBYARG=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"LIBRUBYARG_SHARED"@:>@)'` RUBY_ENABLESHARED=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"ENABLE_SHARED"@:>@)'` @@ -1602,7 +1608,7 @@ #include <version.h> ],[ -#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR == 8 && RUBY_VERSION_TEENY <= 1) +#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR >= 8 && RUBY_VERSION_TEENY <= 1) #error "need at least ruby 1.8.2\n" #endif diff -urN koffice/lib/kross/configure.in.in koffice.new/lib/kross/configure.in.in --- koffice/lib/kross/configure.in.in 2010-08-11 22:16:27.000000000 -0500 +++ koffice.new/lib/kross/configure.in.in 2011-12-08 12:56:45.787428312 -0600 @@ -21,14 +21,20 @@ # Check for Ruby if test "x$compile_kross" = "xyes" ; then - AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18], ruby) + AC_CHECK_PROGS([RUBY], [ruby ruby1.8 ruby18 ruby1.9 ruby19], ruby) if test -n "$RUBY"; then AC_MSG_CHECKING(for Ruby dirs) RUBY_ARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"archdir"@:>@)'` RUBY_SITEARCHDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitearchdir"@:>@)'` RUBY_SITEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"sitelibdir"@:>@)'` - RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'` + if test -n "$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'"; then + # Ruby 1.9 + RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyhdrdir"@:>@)'` + else + # not Ruby 1.9 + RUBY_INCLUDEDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"rubyincludedir"@:>@)'` + fi RUBY_LIBDIR=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"libdir"@:>@)'` RUBY_LIBRUBYARG=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"LIBRUBYARG_SHARED"@:>@)'` RUBY_ENABLESHARED=`$RUBY -r rbconfig -e 'printf("%s",Config::CONFIG@<:@"ENABLE_SHARED"@:>@)'` @@ -84,7 +90,7 @@ #include <version.h> ],[ -#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR == 8 && RUBY_VERSION_TEENY <= 1) +#if(RUBY_VERSION_MAJOR==1 && RUBY_VERSION_MINOR >= 8 && RUBY_VERSION_TEENY <= 1) #error "need at least ruby 1.8.2\n" #endif ======================================= If we get this resolved the patch will be available to close the bug report. :) Thanks for any help. Darrell

2 3

Qt4 needed for building using autotools? && Wonders.
by L0ner sh4dou 08 Dec '11

08 Dec '11

I'm trying to build some trinity components manually, since no binaries, nor build scrips (PKGBUILD) are available for my distro (arch), and I wonder, why when I try to compile something using autotools (because obviously it hasn't been ported to cmake yet) it keeps me asking for Qt >=4.3 and <5.0. Besides I looked a little at files present in the admin dir and I found that some of the paths for libraries are hardcoded and point to (example) /usr/share/kde3 or /usr/share/qt. Another thing, shouldn't automake files be removed form components that have been ported to CMake. Since autotools-based compiling aren't really supported for those... And I'd be grateful of someone could write a little about how to port trinity components to cmake. I'd like to help, I get the main idea, but I don't know where too look for dependencies and stuff like that.

3 3

KOffice 3.5.13 FTBFS
by Darrell Anderson 08 Dec '11

08 Dec '11

Slackware 13.1 Building KOffice 3.5.13 from tarballs. * FTBFS with ImageMagick 6.5.9_6 and GraphicsMagick not installed. * FTBFS with GraphicsMagick 1.3.12 (built with libpng14) installed and ImageMagick not installed. * FTBFS with GraphicsMagick 1.3.12 (built with libpng12) installed and ImageMagick not installed. * FTBFS with GraphicsMagick 1.2.10 (built with libpng12) installed and ImageMagick not installed. * FTBFS with both installed. KOffice will build with neither installed but only chalk, karbon, and krossrunner build. I am unable to build GraphicsMagick 1.1.15 on Slackware 13.1 with either libpng12 or libpng14. I can build 1.2.10 with libpng12 but not libpng14. I can build 1.3.12 with either libpng12 or libpng14. Fiddling with libpng12 does not really help because the default in Slackware 13.1 is libpng14. ========================================================== With ImageMagick installed the build fails with these errors: /usr/lib/libMagickCore.so: undefined reference to `DestroyPixelWand' /usr/lib/libMagickCore.so: undefined reference to `DrawPushPattern' /usr/lib/libMagickCore.so: undefined reference to `DrawPathLineToAbsolute' /usr/lib/libMagickCore.so: undefined reference to `DrawSetClipPath' /usr/lib/libMagickCore.so: undefined reference to `DrawPathClose' /usr/lib/libMagickCore.so: undefined reference to `PixelSetRedQuantum' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeAntialias' /usr/lib/libMagickCore.so: undefined reference to `DestroyMagickWand' /usr/lib/libMagickCore.so: undefined reference to `DestroyDrawingWand' /usr/lib/libMagickCore.so: undefined reference to `NewMagickWandFromImage' /usr/lib/libMagickCore.so: undefined reference to `DrawRender' /usr/lib/libMagickCore.so: undefined reference to `PixelSetOpacityQuantum' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokePatternURL' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeDashArray' /usr/lib/libMagickCore.so: undefined reference to `DrawPathMoveToAbsolute' /usr/lib/libMagickCore.so: undefined reference to `DrawPopPattern' /usr/lib/libMagickCore.so: undefined reference to `DrawPathFinish' /usr/lib/libMagickCore.so: undefined reference to `DrawSetFont' /usr/lib/libMagickCore.so: undefined reference to `DrawSetFillColor' /usr/lib/libMagickCore.so: undefined reference to `PixelSetGreenQuantum' /usr/lib/libMagickCore.so: undefined reference to `DrawTranslate' /usr/lib/libMagickCore.so: undefined reference to `PixelSetQuantumColor' /usr/lib/libMagickCore.so: undefined reference to `PushDrawingWand' /usr/lib/libMagickCore.so: undefined reference to `PixelSetColor' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeWidth' /usr/lib/libMagickCore.so: undefined reference to `DrawRectangle' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeColor' /usr/lib/libMagickCore.so: undefined reference to `DrawRoundRectangle' /usr/lib/libMagickCore.so: undefined reference to `DrawAnnotation' /usr/lib/libMagickCore.so: undefined reference to `DrawPathStart' /usr/lib/libMagickCore.so: undefined reference to `DrawSetViewbox' /usr/lib/libMagickCore.so: undefined reference to `DrawPopClipPath' /usr/lib/libMagickCore.so: undefined reference to `DrawColor' /usr/lib/libMagickCore.so: undefined reference to `DrawScale' /usr/lib/libMagickCore.so: undefined reference to `DrawLine' /usr/lib/libMagickCore.so: undefined reference to `DrawSetFillPatternURL' /usr/lib/libMagickCore.so: undefined reference to `DrawPushDefs' /usr/lib/libMagickCore.so: undefined reference to `DrawComment' /usr/lib/libMagickCore.so: undefined reference to `DrawAllocateWand' /usr/lib/libMagickCore.so: undefined reference to `PixelSetBlueQuantum' /usr/lib/libMagickCore.so: undefined reference to `DrawSetFontSize' /usr/lib/libMagickCore.so: undefined reference to `DrawPushClipPath' /usr/lib/libMagickCore.so: undefined reference to `DrawSetTextUnderColor' /usr/lib/libMagickCore.so: undefined reference to `DrawArc' /usr/lib/libMagickCore.so: undefined reference to `NewPixelWand' /usr/lib/libMagickCore.so: undefined reference to `DrawRotate' /usr/lib/libMagickCore.so: undefined reference to `PopDrawingWand' /usr/lib/libMagickCore.so: undefined reference to `DrawSetClipRule' /usr/lib/libMagickCore.so: undefined reference to `DrawComposite' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeLineJoin' /usr/lib/libMagickCore.so: undefined reference to `DrawPathEllipticArcAbsolute' /usr/lib/libMagickCore.so: undefined reference to `DrawPopDefs' /usr/lib/libMagickCore.so: undefined reference to `DrawSetStrokeLineCap' /usr/lib/libMagickCore.so: undefined reference to `DrawEllipse' collect2: ld returned 1 exit status make[3]: *** [karbon] Error 1 make[3]: Leaving directory `/dev/shm/applications/koffice/karbon' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/dev/shm/applications/koffice/karbon' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/dev/shm/applications/koffice' make: *** [all] Error 2 ========================================================== With GraphicsMagick installed the build fails with these errors: In file included from kis_image_magick_converter.cc:44: ../../../chalk/core/kis_layer.h:170: warning: type qualifiers ignored on function return type kis_image_magick_converter.cc: In function 'void<unnamed>::setAnnotationsForImage(const Image*, KisImageSP)': kis_image_magick_converter.cc:185: error: 'const struct _Image' has no member named 'generic_profiles' kis_image_magick_converter.cc:189: error: 'const struct _Image' has no member named 'generic_profile' kis_image_magick_converter.cc:189: error: 'const struct _Image' has no member named 'generic_profile' kis_image_magick_converter.cc:191: error: 'const struct _Image' has no member named 'generic_profile' kis_image_magick_converter.cc: In member function 'KisImageBuilder_Result KisImageMagickConverter::decode(const KURL&, bool)': kis_image_magick_converter.cc:483: error: 'Downscale' was not declared in this scope kis_image_magick_converter.cc:537: error: 'Downscale' was not declared in this scope kis_image_magick_converter.cc:581: error: 'Downscale' was not declared in this scope kis_image_magick_converter.cc:611: error: 'Downscale' was not declared in this scope kis_image_magick_converter.cc: In member function 'KisImageBuilder_Result KisImageMagickConverter::buildFile(const KURL&, KisPaintLayerSP, KSharedPtr<KisAnnotation>*, KSharedPtr<KisAnnotation>*)': kis_image_magick_converter.cc:815: error: 'Upscale' was not declared in this scope kis_image_magick_converter.cc:851: error: 'Upscale' was not declared in this scope kis_image_magick_converter.cc:882: error: 'Upscale' was not declared in this scope kis_image_magick_converter.cc: In static member function 'static QString KisImageMagickConverter::readFilters()': kis_image_magick_converter.cc:993: warning: unused variable 'matches' kis_image_magick_converter.cc: In static member function 'static QString KisImageMagickConverter::writeFilters()': kis_image_magick_converter.cc:1067: warning: unused variable 'matches' make[4]: *** [kis_image_magick_converter.lo] Error 1 make[4]: Leaving directory `/dev/shm/applications/koffice/filters/chalk/gmagick' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/dev/shm/applications/koffice/filters/chalk' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/dev/shm/applications/koffice/filters' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/dev/shm/applications/koffice' make: *** [all] Error 2 ========================================================== I've searched the web to no avail. Any ideas where to start the triage? Darrell

6 16

ideas for new power management system
by Serghei Amelian 08 Dec '11

08 Dec '11

Hello, I need some opinions about features provided by Power Management System. So far I implemented a battery monitor and backlight control. Now, I want to debate about: 1) Governors. KPowersave come with governor controller, but a guy from #udev irc channel adviced me that is actually is not necessary to implement it in a gui interface, because actually we don't want to change governors but we need to burn less energy. Check this "good practices" guide: http://www.codon.org.uk/~mjg59/power/good_practices.html 2) DPMS and screensavers. In my opinion, DPMS control should be passed to screensaver, not to be controlled by power manager. Why? I think that Power Manager should react only to events related to power supplies (like AC adapter plugged in, AC unplugged, battery low, etc) or ACPI events like "lid closed", "power button pressed", etc. Shutting down the monitor when the user is away from keyboard is not exactly related to power management, seem natural to be a part of screensaver. Opinions? Ideas? -- Serghei

4 3

Building tde 3.5.13
by Baho Utot 08 Dec '11

08 Dec '11

I am having mucho trouble compiling TDE-3.5.13 non cmake packages I am getting things like the following (from kdemultimedia for example) I think I have a path incorrect or something so.... How do you "lookup" where these references are found (like which library file etc) ? .libs/kmixapplet.o: In function `KMixApplet::reportBug()': kmixapplet.cpp:(.text+0x21c): undefined reference to `QDialog::exec()' .libs/kmixapplet.o: In function `KMixApplet::resizeEvent(QResizeEvent*)': kmixapplet.cpp:(.text+0x312): undefined reference to `QWidget::updateGeometry()' .libs/kmixapplet.o: In function `KMixApplet::staticMetaObject()': kmixapplet.cpp:(.text+0x465): undefined reference to `QMetaObject::new_metaobject(char const*, QMetaObject*, QMetaData const*, int, QMetaData const*, int, QMetaProperty const*, int, QMetaEnum const*, int, QClassInfo const*, int)' kmixapplet.cpp:(.text+0x479): undefined reference to `QMetaObjectCleanUp::setMetaObject(QMetaObject*&)' .libs/kmixapplet.o: In function `AppletConfigDialog::staticMetaObject()': kmixapplet.cpp:(.text+0x527): undefined reference to `QMetaObject::new_metaobject(char const*, QMetaObject*, QMetaData const*, int, QMetaData const*, int, QMetaProperty const*, int, QMetaEnum const*, int, QClassInfo const*, int)' kmixapplet.cpp:(.text+0x53b): undefined reference to `QMetaObjectCleanUp::setMetaObject(QMetaObject*&)' .libs/kmixapplet.o: In function `KMixApplet::about()': kmixapplet.cpp:(.text+0x647): undefined reference to `QDialog::exec()' .libs/kmixapplet.o: In function `AppletConfigDialog::activeColors(QColor&, QColor&, QColor&) const': kmixapplet.cpp:(.text+0x81b): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x82f): undefined reference to `QColor::operator=(QColor const&)' kmixapplet.cpp:(.text+0x84c): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x85c): undefined reference to `QColor::operator=(QColor const&)' kmixapplet.cpp:(.text+0x87a): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x88a): undefined reference to `QColor::operator=(QColor const&)' .libs/kmixapplet.o: In function `AppletConfigDialog::mutedColors(QColor&, QColor&, QColor&) const': kmixapplet.cpp:(.text+0x95b): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x96f): undefined reference to `QColor::operator=(QColor const&)' kmixapplet.cpp:(.text+0x98c): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x99c): undefined reference to `QColor::operator=(QColor const&)' kmixapplet.cpp:(.text+0x9bd): undefined reference to `QColor::QColor(QColor const&)' kmixapplet.cpp:(.text+0x9cd): undefined reference to `QColor::operator=(QColor const&)' .libs/kmixapplet.o: In function `AppletConfigDialog::AppletConfigDialog(QWidget*, char const*)': kmixapplet.cpp:(.text+0xa9f): undefined reference to `QString::shared_null' kmixapplet.cpp:(.text+0xb23): undefined reference to `QString::shared_null' kmixapplet.cpp:(.text+0xb2f): undefined reference to `QStringData::deleteSelf()' kmixapplet.cpp:(.text+0xb74): undefined reference to `i18n(char const*)' Thanks

3 2

tdelibs compilation stuck on KBetterThanKDialogBase
by Aleksey Midenkov 08 Dec '11

08 Dec '11

Hello! I have trouble compiling tdelibs: [ 42%] Building CXX object kio/misc/kwalletd/CMakeFiles/kded_kwalletd-module.dir/kwalletd.cpp.o /home/midenok/src/kde/tdelibs/kio/misc/kwalletd/kwalletd.cpp: In member function ‘bool KWalletD::isAuthorizedApp(const QCString&, const QString&, WId)’: /home/midenok/src/kde/tdelibs/kio/misc/kwalletd/kwalletd.cpp:556:12: error: ‘class KBetterThanKDialogBase’ has no member named ‘setLabel’ /home/midenok/src/kde/tdelibs/kio/misc/kwalletd/kwalletd.cpp:558:12: error: ‘class KBetterThanKDialogBase’ has no member named ‘setLabel’ I looked at KBetterThanKDialogBase. It is descendant of QDialog. And there is no method setLabel(). Tried to compile from master branch and from tag v3.5.13 -- same result. I compile with tqtinterface and qt3 modules from git.

1 0

Running Trinity, KDE 4, and KDE 3 Concurrently
by Darrell Anderson 07 Dec '11

07 Dec '11

Just my observations with Slackware 13.1. YMMV. Please feel free to add, edit, qualify, add a workaround, etc. Should we fine tune this information and post to our wiki? =================================== Whereas the Trinity developers have worked hard to support KDE 4 compatibility, there are several challenges with running Trinity, KDE 4, and KDE 3 installed on the same multiple user system. 1. Many of the apps use the same file name. The scripts in /etc/profile.d produce conflicting file search paths. Without the appropriate file search path, the file search path highest in the path hierarchy will launch the app, which might not be the correct app. 2. On multiple user systems, the profile.d scripts can’t be arbitrarily disabled because any of the desktop environments might be used. 3. The profile.d scripts cause conflicts with XDG paths, which create the desktop menus. Normally this is not a problem with other desktops such as Xfce, but that is not the case with these three desktops because many apps have the same name. With each profile.d script being sourced, each desktop system menu will show every app from all other desktops. The Trinity developers have hacked a neat trick to tag the KDE 4 apps in the menu, but there is no such support for KDE 3 apps. The hack does not exist for KDE 4 or KDE 3. 4. User-defined menu changes are stored in $HOME/.config/menus and $HOME/.local/applications. As those directories are global to anything the user does, menu changes in one desktop affects the other desktops if a user wants to change desktops. That means conflicts with starting apps. 5. The KDE 3 and Trinity KDM login manager will conflict unless one or the other is disabled (chmod -x). Neither can be used to support the other desktops because of the underlying dependency on each desktop’s respective kdelibs package. 6. The file search path conflicts will introduce multiple autostart directories. Apps in those directories will start for the other desktops too. A possible work-around to most of these conflicts is to disable all affected profile.d scripts and then modify the xinitrc scripts to source the appropriate profile.d scripts. That might suffice for run level 3, but not run level 4. Run level 4 would require some detailed scripting in the KDM Xsession script to look at the user’s dmrc config file and then source the appropriate profile.d scripts. Yet these work-around won’t resolve any user-defined menu changes. On single user systems or systems where all users want to use the same desktop, all of this can be avoided by uninstalling the other desktop environments. =================================== Darrell

5 22

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels