tde-devels April 2012

devels@trinitydesktop.org

25 participants
142 discussions

by Darrell Anderson

I updated the bug tracker. Anything related to building/compiling is now marked with the prefix 'Build issue: '. I modified the priority of a few. Most build issues are now tagged with Blocker, Critical, or Major, although there are other build issues rated lower. Possibly I missed a few. Please check your own reports and add the 'Build issue: ' prefix as necessary. With these updates, we now know which bug reports are build issues. Just search for 'Build issue: '. No need for an etherpad. :) A check box would be nice. Does bugzilla support that? http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/buglist.cgi?qui… How many? 72 reports of build issues. Yet remember that many reports are similar --- resolve one report and resolve several. Not necessarily related to build issues, there are 30 bug reports with attached patches. If we seek a way to triage the bug tracker, I recommend first focusing on Blocker reports, then Critical, then Major, etc., but within each priority, first address those with patches. http://bugs.pearsoncomputing.net/bugzilla/bugzilla/bugzilla/bugzilla/buglis… I will push patches to GIT but often I need technical review and approval. Sometimes one person is sufficient but other times more when I believe a "root cause analysis" is required, such as reverting patches. As project leader, Tim is an exception and when he says push I'll push. Tim, Unless I can do this on my own, would you please add my email address to the bug tracker notification list? That way I'll know about new bug reports and can quickly tag any new report as a build issue if needed. I then can post to this list any such new reports. Darrell

12 years, 1 month

Qt:: or TQt:: ?

by Darrell Anderson

When reviewing the source code, sometimes I see Qt:: prefixed and sometimes TQt::. Which is correct? If both are correct then how does one determine appropriate context for each? Thanks. Darrell

12 years, 1 month

kpowersave now working without HAL

by Timothy Pearson

All, I have recently finished a initial conversion of kpowersave to work without HAL, instead relying on the brand-new TDE hardware library, which in turn works straight off of the raw device nodes in /sysfs. As this is the last remaining large HAL dependency in TDE, I would encourage the TDE developers to compile and test on their hardware, reporting bugs to this mailing list. The source code is available here: http://git.trinitydesktop.org/cgit/kpowersave-nohal/ and can be obtained via: git clone http://scm.trinitydesktop.org/scm/git/kpowersave-nohal If this works reliably, along with the udev-based media kioslave:/, I will seriously consider removing the TDE HAL dependency completely for R14.0. Tim

12 years, 1 month

Editing MNG files

by Darrell Anderson

In tdebase/kicker/data/kickoff, are image files that need branding updates: kmenu_active.png kmenu_basic.mng kmenu_flipped.mng kmenu_vertical.mng I updated kmenu_active.png (GIT hash d4e6607ad6a9bfc49f4dfeced379c136704714b1), but the other three are animated (MNG) files that I can't perform mere touch up with kolourpaint. To my knowledge no TDE apps support MNG editing (viewing yes, editing no). The only app I find for that is GIMP and I won't go there. Would somebody with some MNG skills look at updating those three MNG images? To update the logo, you should be able to grab the same from the kmenu_active.png I uploaded to GIT. Thank you ! Darrell

12 years, 1 month

Extensive patching of inadvertent "TQ" conversions

by Darrell Anderson

Yesterday I patched many modules with various amounts of inadvertent "TQ" conversions. Most of them were harmless because the compiler doesn't know how to spell and the inadvertent changes were consistently mispelled. Thus the packages compiled normally. The sources merely looked weird when reading the code. For example, ETQUAL vs. EQUAL, RETQUIRED vs. REQUIRED, UNITQUE vs. UNIQUE, etc. The main reason for this cleanup effort is to restore the correct "human readability" of the source code. However, a handful of the inadvertent conversions might have played a role in various bug reports. Might have. If you have a favorite pet peeve bug then please rebuild from scratch in GIT and test again. No promises. I suspect very few bugs will be resolved by this effort, but who knows? I now can see SVG images in the file preview tooltip in Konqueror as well as through the embedded viewer. I would appreciate confirmation from others with this bug (bug report 615). Darrell

12 years, 1 month

SUCCESS gcc47 - tdelibs/tdebase - NO modules fail

by David C. Rankin

Tim, Darrell, All, After a successful gcc46 build last night, I decided to try building tdelibs and tdebase on gcc47 with the exact same patch setup. SUCCESS. After installing the gcc47 patches, deleting ksycoca and starting TDE, everything was working, knemo appeared and all kcontrol modules were in place. The patches included in this build were: tdelibs: tdelibs-kdirwatch.diff tdebase: 01-kicker-lockout-applet-button-order.patc 03-kcontrol_advbg_step.patch 06-nspluginscan-xdgcompliance.patch 08-kip_kdesktop_rounded_icon_text_corners.patch tdebase-kicker-easyvector.patch tdebase-docbook-refix.diff All patches are available here for review: http://www.3111skyline.com/dl/dt/tde/pbpkg/tde-tdelibs/ http://www.3111skyline.com/dl/dt/tde/pbpkg/tde-tdebase/ Now there is a CAVEAT that everyone should be very clear on. The remainder of the install was built on gcc46. ONLY tdelibs and tdebase were built with gcc47 and tdebase required '-fpermissive'. So unknown failures may still occur when the remaining dependencies are built on gcc47. However, I have a set of gcc47 packages for TDE that I will test with the new tdelibs/tdebase to determine if the current dependency builds on gcc47 are solid. If we still have issues, I will have to strip all patches from the dependencies and attempt another build on gcc47 through tdebase to confirm. -- David C. Rankin, J.D.,P.E.

12 years, 1 month

All tde modules FAIL when built on gcc47 (kdesktop, knemo, kcontrol, etc...)

by David C. Rankin

Tim, Darrell, All, I rebuilt TDE yesterday on gcc47. Nothing else changed. Now, after updating my install and removing all /var/tmp/ ksyscoca files, I get module failure when trying to access kcm modules like kcontrol, knemo, kdesktop, etc.. I grabbed a couple of screenshots: http://www.3111skyline.com/dl/dt/trinity/ss/kcontrol-module-failure.jpg http://www.3111skyline.com/dl/dt/trinity/ss/kdesktop-module-failure.jpg http://www.3111skyline.com/dl/dt/trinity/ss/knemo-error-window.jpg Checking the command line with knemo, I get the following: kio (KSycoca): Trying to open ksycoca from /var/tmp/tdecache-david/ksycoca kutils (KCModuleInfo): Could not find the service. kcontrol: Module '' not found. kutils (KCMultiDialog): KCMultiDialog::addModule Network Monitor kutils (KCModuleProxy): [void KCModuleProxy::init(const KCModuleInfo&)] kutils (KCMultiDialog): [void KCMultiDialog::slotAboutToShow(TQWidget*)] kutils (KCModuleProxy): [KCModule* KCModuleProxy::realModule() const] kutils (KCModuleProxy): Module not already loaded, loading module kutils (KCModuleProxy): [KCModule* KCModuleProxy::realModule() const] kutils (KCModuleProxy): [KCModule* KCModuleProxy::realModule() const] kutils (KCModuleProxy): [KCModule* KCModuleProxy::realModule() const] kutils (KCModuleProxy): [virtual void KCModuleProxy::showEvent(TQShowEvent*)] kutils (KCModuleProxy): [KCModule* KCModuleProxy::realModule() const] kutils (KCMultiDialog): [void KCMultiDialog::dialogClosed()] I don't know where to look next. What gives? -- David C. Rankin, J.D.,P.E.

12 years, 1 month

R14 Issues

by Darrell Anderson

There are a handful of issues I'd like to see resolved before R14. If we are discussing a 3 month window then I believe we can resolve these issues. * Bug report 892: Update XDG keys I have the patches ready for all modules but I don't know how to update user profile files. I don't want to push the patches without providing that remedy. (Refer to the recent discussion in this list.) I am unable to figure out how to change $PREFIX/applications/kde -> $PREFIX/applications/tde without causing weird problems with usability. Read the bug report comments for details. * libkipi, kipi-plugins, mlt need updating * tqca needs to be added to the source tree (I have TQ converted sources ready to go and tested.) * Branding issues: References of KDE in What's This text strings References of KDE in Tooltip text strings Visible references of "KDE [Aa]pplications" Visible references of "KDesktop" Visible references of "KDE3" Command line "--help:" reference to KDE Darrell

12 years, 1 month

tdepim FTBFS on Slackware 13.37

by Darrell Anderson

Failure: ================================================== In file included from /dev/shm/tdepim/libkcal/icalformat.cpp:35:0: /usr/include/libical/icalss.h:38:27: fatal error: icalcomponent.h: No such file or directory compilation terminated. ================================================== /usr/include/libical/icalcomponent.h does exist. I reinstalled libical anyway. I just built tdepim on Slackware 13.1 with no such failure. Slackware 13.1: libical 0.43, gcc 4.4.4, cmake 2.8.4 Slackware 13.37: libical 0.4.4, gcc 4.5.2, cmake 2.8.4 I appreciate any help. Darrell

12 years, 1 month

error: tde-style-qtcurve - in /common dir

by David C. Rankin

Darrell, There may have been a problem introduced in the tde-style-qtcurve 'common' dir. This is on gcc46, so it's not a 47 problem: [ 25%] Building CXX object style/CMakeFiles/qtcurve-module.dir/qtcurve.cpp.o cd /build/src/build/style && /usr/bin/c++ -Dqtcurve_module_EXPORTS -DHAVE_CONFIG_H -DQT_PLUGIN -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -fPIC -I/opt/tqt3/include -I/usr/include/tqt -I/opt/trinity/include -I/build/src/build -I/build/src/tde-style-qtcurve/common -I/build/src/build/style -o CMakeFiles/qtcurve-module.dir/qtcurve.cpp.o -c /build/src/tde-style-qtcurve/style/qtcurve.cpp In file included from /build/src/tde-style-qtcurve/style/qtcurve.h:66:0, from /build/src/tde-style-qtcurve/style/qtcurve.cpp:112: /build/src/tde-style-qtcurve/common/common.h:555:5: error: expected identifier before numeric constant /build/src/tde-style-qtcurve/common/common.h:555:5: error: expected '}' before numeric constant /build/src/tde-style-qtcurve/common/common.h:555:5: error: expected unqualified-id before numeric constant /build/src/tde-style-qtcurve/common/common.h:564:1: error: expected declaration before '}' token make[2]: *** [style/CMakeFiles/qtcurve-module.dir/qtcurve.cpp.o] Error 1 make[2]: Leaving directory `/build/src/build' make[1]: *** [style/CMakeFiles/qtcurve-module.dir/all] Error 2 make[1]: Leaving directory `/build/src/build' make: *** [all] Error 2 -- David C. Rankin, J.D.,P.E.

12 years, 1 month

← Newer
1
...
4
5
6
7
8
9
10
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels April 2012