David,
I added a second patch to bug report 1063 --- for kmplayer.
Both patches work on my Slackware systems. The oldest release that I build Trinity has glib2-2.22.5 and the newest has glib2-2.28.6 (although that could change in the upcoming weeks).
I believe the cutoff for the "glib.h" failures is enforced starting with glib2-2.31.
In other words, my builds more or less prove backwards compatibility of the patches without needing any preprocessor checks.
I believe Arch is using glib2-2.32.3. Would you please test the kmplayer patch?
Thanks much!
Darrell
All,
I couldn't make the meeting today, but did read the logs. One note I have was
concerning the discussion regarding systemd and whether some distros will move
to it and some not. I want to make sure the issue isn't confused. Not everyone
will move to the systemd init systems, but everyone _will_ move to the systemd
package that provides udev. Arch separates systemd-tools to provide udev. My
guess is that most distros will do something similar to provide a udev package
from it's new upstream. Just know that udev from systemd isn't the same as
adopting systemd init structure. Arch has no plans to move to systemd. Init
scripts further the KISS philosophy, and systemd, while it provides a number of
new tools, it doesn't provide anything necessary to get your box going that your
current sysV or bsd style inits don't.
--
David C. Rankin, J.D.,P.E.
Tim,
While running branding updates, I ran across some problematic desktop files. I don't know how we want to update these files.
These files contain URLs to kde.org:
tdebase/konqueror/sidebar/trees/init/remote/ftp/kde_ftp.desktop
tdebase/konqueror/sidebar/trees/init/remote/web/kde_web.desktop
tdebase/konqueror/sidebar/trees/init/remote/web/apps_web.desktop
tdebase/konqueror/sidebar/trees/init/remote/web/look_web.desktop
tdebase/konqueror/sidebar/trees/init/remote/web/dot_web.desktop
tdebase/kcontrol/ebrowsing/plugins/ikws/searchproviders/kde_websvn.desktop
tdebase/kcontrol/ebrowsing/plugins/ikws/searchproviders/appsy.desktop
tdebase/kcontrol/ebrowsing/plugins/ikws/searchproviders/bugft.desktop
tdebase/kcontrol/ebrowsing/plugins/ikws/searchproviders/kde.desktop
These files use a group heading of [KDE Desktop Pattern], referenced in tdebase/kcontrol/background/bgsettings.cpp:
tdebase/kdesktop/patterns/triangles.desktop
tdebase/kdesktop/patterns/rattan.desktop
tdebase/kdesktop/patterns/fish.desktop
tdebase/kdesktop/patterns/pavement.desktop
tdebase/kdesktop/patterns/flowers.desktop
tdebase/kdesktop/patterns/night-rock.desktop
tdebase/kdesktop/patterns/stonewall2.desktop
These files use a group heading of [KDE Cards], referenced in tdegames/libtdegames/kcarddialog.cpp:
tdegames/libtdegames/carddecks/decks/deck19.desktop
tdegames/libtdegames/carddecks/decks/deck7.desktop
tdegames/libtdegames/carddecks/decks/deck2.desktop
tdegames/libtdegames/carddecks/decks/deck16.desktop
tdegames/libtdegames/carddecks/decks/deck3.desktop
tdegames/libtdegames/carddecks/decks/deck23.desktop
tdegames/libtdegames/carddecks/decks/deck0.desktop
tdegames/libtdegames/carddecks/decks/deck18.desktop
tdegames/libtdegames/carddecks/decks/deck8.desktop
tdegames/libtdegames/carddecks/decks/deck13.desktop
tdegames/libtdegames/carddecks/decks/deck6.desktop
tdegames/libtdegames/carddecks/decks/deck10.desktop
tdegames/libtdegames/carddecks/decks/deck12.desktop
tdegames/libtdegames/carddecks/decks/deck22.desktop
tdegames/libtdegames/carddecks/decks/deck24.desktop
tdegames/libtdegames/carddecks/decks/deck21.desktop
tdegames/libtdegames/carddecks/decks/deck15.desktop
tdegames/libtdegames/carddecks/decks/deck17.desktop
tdegames/libtdegames/carddecks/decks/deck20.desktop
tdegames/libtdegames/carddecks/decks/deck14.desktop
tdegames/libtdegames/carddecks/decks/deck5.desktop
tdegames/libtdegames/carddecks/decks/deck1.desktop
tdegames/libtdegames/carddecks/decks/deck4.desktop
tdegames/libtdegames/carddecks/decks/deck11.desktop
These files use a group heading of [KDE Backdeck], referenced in tdegames/libtdegames/kcarddialog.cpp:
tdegames/libtdegames/carddecks/cards-hard-a-port/index.desktop
tdegames/libtdegames/carddecks/cards-konqi-modern/index.desktop
tdegames/libtdegames/carddecks/cards-default/index.desktop
tdegames/libtdegames/carddecks/cards-warwick/index.desktop
tdegames/libtdegames/carddecks/cards-xskat-german/index.desktop
tdegames/libtdegames/carddecks/cards-penguins/index.desktop
tdegames/libtdegames/carddecks/cards-aisleriot/index.desktop
tdegames/libtdegames/carddecks/cards-spaced/index.desktop
tdegames/libtdegames/carddecks/cards-gdkcard-bonded/index.desktop
tdegames/libtdegames/carddecks/cards-xskat-french/index.desktop
tdegames/libtdegames/carddecks/cards-dondorf-whist-b/index.desktop
Darrell
This Trinity service is installed from tdesdk. Although configured not to start automatically, this service is started by various user actions.
For example, selecting Properties in the konqueror context popup menu will start this Trinity service.
Most users do not need this service running at any time for any reason. As we continually watch for ways to improve Trinity, should this service be started all the time for no apparent reason?
Darrell
Slackware Current 64-bit
The failure:
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: CMakeFiles/rosegardensequencer.dir/sequencer/main.cpp.o: undefined reference to symbol 'pthread_sigmask@@GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: note: 'pthread_sigmask@@GLIBC_2.2.5' is defined in DSO /lib64/libpthread.so.0 so try adding it to the linker command line
/lib64/libpthread.so.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
rosegarden builds without that error in 32-bit.
How to fix?
Darrell
I don't have a clue how to use QCAD in any meaningful way, but QCAD runs on my Trinity system. I built QCAD against Qt 3.3.8.b. I built QCAD in KDE3 and not in Trinity. Because Qt 3.3.8.d and TQt3 are built and installed separately, I have no problems launching QCAD from within Trinity.
The dialogs in QCAD suck, just like LibreOffice. Stupid generic Qt3 dialogs. :-)
I'm curious how much patching is required to build QCAD with TQt3. I hope to tinker with that eventually. I don't know how to force building QCAD (or any generic Qt3 app) to use the TDE Integration Module to use Trinity dialogs.
Darrell
Tim, Calvin,
Please add "Slackware 14" as a Platform/OS to the bug tracker pick lists.
That is the next release of Slackware. I am testing Trinity with that pre-release.
Thank you!
Darrell
I found the following article interesting:
http://www.ibm.com/developerworks/linux/library/l-admin-gnome/index.html?ca…
Trinity does most of this. I was thinking we could write a similar article for our community wiki.
Questions:
* How to set default file manager (konqueror) viewing preferences for all users? (Figure 4). The author did not imply setting such default options globally for all users was possible in GNOME, I'm just asking whether that is possible in Trinity.
* Does Trinity provide a GUI tool to manage system services (not Trinity services)?
Darrell
I reorganized the table of contents. Several documents now use dynamic release versions and dates, which means that information will alwasy be current.
There are too many handbooks needing a thorough review. We can't update all of them before R14.0.0. For R14.0.0 I am limiting my focus to a specific set of handbooks. Currently I am revising the following:
tdebase/doc/faq/index.docbook
tdebase/doc/khelpcenter/support.docbook
tdebase/doc/khelpcenter/welcome.docbook
tdebase/doc/khelpcenter/contact.docbook
tdebase/doc/khelpcenter/index.docbook
tdebase/doc/khelpcenter/whatistde.docbook
tdebase/doc/khelpcenter/help.docbook
tdebase/doc/quickstart/index.docbook
tdebase/doc/tdm/index.docbook
tdebase/doc/userguide/index.docbook
tdebase/doc/visualdict/index.docbook
To anybody interested in helping:
* Review all images (obsolete, branding, etc.)
* Missing images (this requires reading the text and noting where an image would help)
* Watch for any web link referencing KDE web sites
* Watch for any mail link referencing KDE addresses
* Technical correctness
* Stale information (for example, the FAQ)
To anybody who wants to help, you do not need to learn docbook. Use the actual (GIT, not 3.5.13 :-)) help handbooks to review. Contact me here in the mail list with your observations and notes. :-)
Darrell