Thanks! Yes, I saw the complaints too. :) That makes me curious about the Debian/Ubuntu package for KDE3. Possibly one and the same, possibly not. I think the module would be a nice addition once we debugged the code. :) Ok --- I grabbed the sources. After I sanitize them for the TQt layer, how do I merge them with a parent package? Or would we host the module in the applications sources? Darrell

Ok. Thanks. Yet Another Side Project! Darrell

Test plan: * Installs correctly to TDE Components. Check! * If the user's Autostart directory is already populated, verify those items appear in the modules list. Check! * Can add new apps to the list. Check! * Those newly added apps actually start with the next new session. Check! * Previously populated apps still start with the next new session. Check! * Can remove apps from the list. Check! * Apps not removed still start with the next new session. Check! * Alleged Bug: When launching apart for kcontrol, clicking "Cancel" with a properties dialog open will generate a crash. Can't reproduce. * Alleged Bug: When launching inside kcontrol, option "Reset" does not work. Button does work --- sort of: read the next item. * Alleged Bug: Clicking "Reset" with a properties dialog open inserts a duplicate entry into the list of the entry which has the properties open. Reproduced. Checking the contents of the Autostart directory shows the items are not really duplicating. Toggling out of the Autostart manager module and returning immediately clears the list of duplicate entries. Not a blocker bug but not professional looking. I could not replicate this bug: https://bugs.kde.org/show_bug.cgi?id=150439. I discovered a new bug: I monitored my Autostart and shutdown directories in Konqueror while testing the module. When adding or removing items they are added or removed immediately --- before selecting the Apply button. Probably not good. Overall, we have a nice user-friendly addition with this module. As far as I can see, only two minor bugs. Reading the discussion at kde-look.org, one person suggested a "Disable" option, which seems handy. Another possible enhancement is mentioned here: http://lists.kde.org/?l=kde-devel&m=116924533130243&w=2 --- basically provide a portal to override anything in the global autostart locations. Yet even as is, this module provides a handy way of adding and removing items to the Autostart, shutdown and env directories. Yes, shutdown too. What next? Fixing the two bugs probably is beyond my noob C++ skills, although I'll take a gander. Does this new module sound like a good addition? If yes then do we want to keep this as a separate optional module or merge into tdebase/kcontrol or tdeadmin? Darrell

Looks good to me. Will this be pushed to tdebase GIT or did you build it as a standalone module? Tim

Darrell --- On Sun, 4/22/12, Darrell Anderson <humanreadable(a)yahoo.com> wrote:

git clone http://<username>@scm.trinitydesktop.org/scm/git/kcmautostart Tim

Can I still do this after I resetting my local repo to April 10? I reset my local repo to help debug the kate/kwrite problems. I have already started a fresh rebuild based on that date. Never mind. :-) Here is a tar.gz: http://humanreadable.nfshost.com/trinity/patches/autostart.tar.gz Here is the directory layout: http://humanreadable.nfshost.com/trinity/patches/autostart/ Of course, these files are updated and patched for Trinity and no longer are the same as the original Ubuntu sources. Nothing specific needed to build: CFLAGS=$CPUOPT \ CXXFLAGS=$CPUOPT \ ./configure \ --prefix=${PREFIX} \ --sysconfdir=${SYSCONFDIR} \ --libdir=${LIBDIR} \ --mandir=${MANDIR} \ --with-qt-dir=${QTDIR} \ --with-qt-includes=${QT_INCLUDE_DIR} \ --with-qt-libraries=${QT_LIB_DIR} \ $DEBUG_AUTOTOOL_OPT || exit 1 I have to review my previous list posts to start a bug report. There were two minor bugs, none fatal. Darrell

Too many things going on here today. Feeling stressed.... I don't understand. Permissions look fine. Can you see the contents of the parent directory? http://humanreadable.nfshost.com/trinity/patches/ Darrell

Got it that time; uploaded to GIT. Tim

Pushed to GIT in hash 035e48e. Thanks for the translations! Tim