Note for anybody walking down that road:
Anno domini 2021 Fri, 22 Jan 08:24:07 +0100 Dr. Nikolaus Klepp scripsit:
[...] I might be wrong - and please korrect me if I am - but the system:/media and media:/ urls are handled by tdeio_media.so or tde_system.so from anywhere inside TDE. Or are there parallel implementations all over the place?
Both system:/media/ and media:/ end up in tdeio_media.so. Remame that file and the functionality for both protocols is gone in whole TDE. This includes automounting of thumbdrives. So this is the right place to start the hunt. Also watch out, that some debug info ends in ~/.xsession-errors and some ends on stdout.
Nik
Oh, debugging: Where goes the output from kdDebug() or kdDebug(1219) ? I think anything from "printf(...); fflush(stdout);" goes to ~/.xsession-errors, but I'm not sure about that, either.
Since you are using a deb based distro, a relatively easy way to test locally is to download the source code of the respective module (including the packaging info), put them together, then run "debian/rules binary" to build a first version of the packages. Then make changes, go to obj-x86.../tdeio folder, run "make && make install" and this will compile and install the new code to your system. Same for the other modules. Keep in mind you are actively changing your system, so if you do something very wrong you can end up with a broken system. If you don't want to do that, you can create deb packages with "debian/rules binary" each time and install them in a test box machine.
"debian/rules binary" ? OK, I used debhelper and it looks like it rebuilds the whole thing at each call.
Nik
Cheers Michele