There are also crashes in system settings - try to change icon set - the program exits when you switch to, e.g., monochrome icons.

Unless some C++ experts take a look or back port certain patches from Trinity, I decided I cannot do anything more with 3.5.10. I lack the skills to do anything meaningful. I have that version running on 13.1. My workaround for the KMail bug is to copy /usr/bin/kmail and /usr/lib/libkmailprivate.so from 12.2. That stops the crashing. Based upon a Gentoo discussion I discovered, I suspect the KMail crash is related to the newer version of glibc.

Whether or not I rebuild 3.5.10 on 13.37, I decided to wait until the full Trinity package set conversion to cmake is complete. I'll focus on other projects and enjoy the summer. Hopefully by then the Trinity conversion is finished.

This one fixes the kmail bug.
http://git.overlays.gentoo.org/gitwe...b25b130ba5848e

Hey! Relax! Your backtrace helped to find the patch :-)

I searched for that patch after I stumbled across the gentoo discussion. Good find! I have no need for dcop with the composer window, so I'll test that patch. Hopefully a better long-term solution appears in Trinity for those who want dcop support with the composer.

All I meant was I can't help with patching because of a lack of C++ skills.

I wonder whether the default for these packages should be with debugging enabled. The number of users is much smaller than with the mainstream. Takes longer to build and builds larger packages, but being able to backtrace would help everybody trying to support and use these packages. I have enabled debugging as the default in my build scripts.

Also problems with icon settings is now solved, thanks to patch found on opensuse site:
https://build.opensuse.org/package/v...45397b5b735ca4

I changed .txt arquive extension to .torrent and I'm trying to use ktorrent to download kde_3_5_10_for_slackware_13_1-(Demonoid.me)_6274531.0026 but nothing. What's the problem? And first arquive link is updating with new patch?

No, there is no updated version yet. There will be one, but compiled on 13.37.

That's all, alekow!!!

1)But, about dowloading... I don't get yours 3.5.10! Is there another direct link to use?
2)Are you a Trinity writer too? In case of being, can I use 3.5.12 in 13.1 system unless slackware/l ( qca, arts, qt3, dbus.. ) install, so it isn't there , is it?

1. Just released a torrent for new packages for 13.37 - it's here:
http://www.linuxquestions.org/questi...ml#post4350180
2. I didn't try using any trinity packages on 13.xx

[QUOTE=alekow;4350181]1. Just released a torrent for new packages for 13.37 - it's here:
http://www.linuxquestions.org/questi...ml#post4350180

I need a 13.1 packages! I did'nt understand this reply, so kde3.5.10_13.37 is using a different glibc?

Can you seed it?
kde_3_5_10_for_slackware_13_1-(Demonoid.me)_6274531.0026.txt

I need a 13.1 packages! I did'nt understand this reply, so kde3.5.10_13.37 is using a different glibc?

Can you seed it?
kde_3_5_10_for_slackware_13_1-(Demonoid.me)_6274531.0026.txt

I reseeded it. Have in mind it wasn't compiled with the above-mentioned patches.

Thanks a lot. I downloaded it! It will be pacthed too?

I don't have plans to rebuild packages for 13.1. You can try using the source code from here:
ftp://ftp.darkstarlinux.ro/pub/peopl...slackware/kde/
You'd need to rebuild kdelibs and kdepim only. To patch the source just:
1. add this patch:
ftp://ftp.darkstarlinux.ro/pub/peopl...ash_patch.diff
to kdelibs source directory and the following line:
to apply-patches.sh in kdelibs source directory;
2. Run as root kdelibs.SlackBuild like this:
(after finished compilation upgrade kdelibs with the output package)
3. add another patch:
ftp://ftp.darkstarlinux.ro/pub/peopl...rash-fix.patch
to kdepim source directory and the following line:
to apply-patches.sh in kdepim source directory;
4. Run as root kdepim.SlackBuild like this:
(after finished compilation upgrade kdepim with the output package)

Have fun.

It's not difficult, but the compilation process is time-consuming.

I did something to help me and now I have a kde 3.5.10 running. Unfortunately, there is small bug yet so login manager starts using a Xfce appearance. Someone can pinpoint me a local to correct it?