Where did you see that message? We have been trying to purge the Trinity source files of any KDE and Kubuntu branding. Please post where that Kubuntu branding is found and I'll get the source files updated.

I saw the same thing happen to me when I started testing Trinity. The older ~/.kde profile has a Trash.desktop file in ~/Desktop. Trinity supports its own Trash widget and the two both appear on the desktop. The solution is to delete the older KDE Trash.desktop file from ~/Desktop.

I don't use wireless here and might not be able to help much with that one. What do you mean by being loaded twice? Are there two processes running or two desktop icons? How is wicd usually started in Slackware?

I confirm. I just checked my pre-built package and there are no /usr/bin files. I'll try to solve that problem as soon as possible.

That sounds like a bug. Possibly some Debian/Ubuntu contamination. I would appreciate more info to help quash that problem.

Theoretically , you should not have to rebuild any Trinity packages. Just install the additional third party packages and the hooks in Trinity should then work with the new packages.

Yes, that is the idea. Libical is a required package for Trinity but libcaldav is not. Also, there is a libcarddav package that I never have been able to build. I would appreciate any help with that. I do not use those online apps, so some courageous Slackers will need to help test those packages in Slackware. The Trinity users list group would be a good place to help explore those options.

Hmm. I notice in my build scripts that the patch is not applied when building arts for KDE 3.5.10. I just now added an apply-patches.sh script to the arts directory and uploaded the new files to my web site. Therefore using my build scripts to build arts in KDE 3.5.10 should now work as expected. That patch slipped through the cracks during my testing. The patch has been applied to Trinity SVN and 3.5.12 --- I simply forgot to test the same when building KDE 3.5.10.

THAT is good news.

There is no binary file in /usr/bin. I checked the stock 12.2 knemo package too. Knemo runs as a daemon and not as a traditional binary executable.

3.5.10, no KDE4. I used slightly modified slackware 12.2 slackbuilds and quite a lot of patches. Needed to rebuild qt3 too.

What info do you need for the root shell problem?

I guess my question wasn't clear. If something like libdvdcss, for example, is already installed with KDE 3.5.10 and I replace KDE 3.5.10 with 3.5.12, but not the package (libdvdcss), will the hooks find the already installed package or would I need to rebuild said package under 3.5.12?

I'm unsure why the sudoer list was necessary. All I do here is add a user to the wheel group. I then can start a root shell or su to root.

They should.

I've never used the wheel group for this type of thing before. The behaviour of the root shell option in Konsole is clearly different from 3.5.10 to 3.5.12.

I just tried it on my virtual machine. I commented myself out of the sudoers file and added my user to the wheel group. Entering the root password when starting a root shell in Konsole still failed. Switched things back and entered my user password to get the root shell.

Everyone is free to scratch their own itch. For anyone wanting to help with this project, please consider joining the Trinity list groups.

I would like to see further testing with 12.2, but anyone who has 13.0 and 13.1 installed is welcome to start tinkering with the build scripts in those environments. Please set up a chroot or virtual machine to ensure a stock Slackware system. That means no third party packages and no proprietary video drivers.

For 13.x, remember that several foundation packages must be rebuilt and installed, such as qt3, dbus-qt3, etc. I'm unsure about 13.0, but poppler needs to be rebuilt in 13.1 to provide qt3 support.

For those wanting to help test the build process, please join the Trinity developer's list group. I am unable to check the forum here during the week and the Trinity developers are far more qualified to help than me. I just provide grunt work to find the kinks in the build process.

Folks with C++ skills are welcome to tackle the bugzilla to help quash bugs and enhancement requests. During my last conversations on the developer's list we had decided that a primary focus for 3.5.13 was the bugzilla. Anyone helping in that area will need to setup SVN support on their system.

Please do not fear helping. I never used SVN or tried to build packages for others until I joined this project. I've learned a lot and have much more to learn. Overall the project has been rewarding.

Hmm. Works fine here. I just added a test user to the wheel group and nothing in the sudoers list for that user. I was able to open a root shell and su to root from the user's konsole shell.

Woodsman,

The "Welcome to Ubuntu" was on the default KDM. I couldn't find any mention of Ubuntu in any of the SlackBuilds. I think it is probably set somewhere in the kdebase source files.

The Wicd problem is that two wicd gui's show up on the taskbar. Not sure why it's doing that. I'm not using wireless at the moment, but the box itself has a wireless card. I'm still investigating that one. Do you know what file controls the taskbar?

As for knemo, this is a system tray application. How can this be loaded as a daemon? Well, at least that's not the way it behaves in the kde 4 series. I'm almost certain that the latest version of knemo requires qt4 and will not work on qt3.

I will sign up for Trinity's list servers. However, thank you already for the work that you have put into this project.

I'll raise the topic about KDM in the developer's list and if necessary file a bug report to focus attention. In the mean time I'll make a note to check that and apply a build patch if necessary.

I'll need help with wicd. I don't use wireless here. I think there is a section in kcontrol, internet, that controls wireless configurations. Try looking for something obvious there.

KNemo runs as a KDE daemon, not as a system process daemon. Perhaps KDE service is a better description. Autostarting knemo is controlled by kdedrc. Look in kcontrol, internet, network monitor.

Wicd issue is probably caused by wicd.desktop files in two different places that are both looked at by Trinity.
I did the code for that in wicd, and if I remember correctly, it was done during the transition from kde3 to kde4 (and the assumption was that only one of them would ever be installed). Check in /etc/xdg/autostart/ and /usr/share/autostart/ and /opt/kde/share/autostart/ and $HOME/.config/autostart/ and see what shows up

Yeap, that's it! There were desktop files on both /etc/xdg/autostart and /usr/share/autostart. Learned something new today!

Now that I think about it, I had notice the "Ubuntu" problem when I had upgraded kde to trinity instead of doing a clean install. KDM in Trinity is "themed" and thus is not showing any "Welcome to...". I hope I'm making sense!! lol It's been a long day with all the Halloween festivities!

As for the wicd, rworkman might have solved the problem on the previous post.

Lastly, knemo, I'll play around with that tomorrow to see if I can get it to work.

I just aquired a spare machine to play with, so I did a brand spanking new install of Slackware 12.2, I did the full install but I delselected KDE because I have read about Trinity and wanted to give it a try, I took it for a spin doing various things at the CLI and then with XFCE and everything was fine, as it always is with Slackware

So I went to the Trinity site and downloaded all the .tgz packages for Trinity for SW 12.2 iirc it's version 3.5.12 released in 2010 and installed with installpkg *.tgz and then ran xwmconfig to choose the new desktop - it was listed as kdeinit.new I think, or whatever.

Well, startx gave me errors so I scratched my head for a minute and went to /usr/bin and then just cp kdeinit.new to kdeinit (I think that was the file name), startx and the Trinity desktop fired right up.

I thought, okay, this is cool, so far so good, but then as reported here, there were none of the usual things I would expect to see in the K-menu, or rather, the T-menu

So, did I miss something? Is Trinity for sw 12.2 designed to be installed OVER the existing KDE 3.5.10 that ships with SW 12.2 and then use it's config files ???

So, I'm guessing at this point, I'm considering installing KDE 3.5.10 and making sure that is stable and then installing Trinity 3.5.12 unless I am missing something and maybe 'launching' it wrong ?

Any help appreciated.

Been a long time since I thought about those 12.2 packages....

The Trinity packages for 12.2 were intended to replace KDE3 completely. That is, KDE3 needs to be fully removed because all of the Trinity packages install to /usr, the same place as the KDE3 packages.

I suspect your reference of kdeinit.new was to xinitrc.tde.new.

I don't know about the incorrectly populated menu. I have a 12.2 virtual machine I could clone to test the 3.5.12 packages. If I find the time....

With that said, there was not a lot of difference between 3.5.12 and 3.5.10. Bug fixes. You will not miss a lot if you use KDE3 that came with 12.2. My HTPC still has 12.2/KDE3 installed.