Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
Nik
On Thu, 21 Jan 2021 17:48:31 +0100 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
If you're grabbing release versions (14.0.9, frex), the source is broken up into metapackages which can be downloaded and compiled individually. You probably want tdelibs and/or tdebase. Most of the metapackages also have CMake flags that will allow you to compile only one application at a time. tdelibs is not subdivided into applications, so it's the largest chunk you might have to build.
Hope that helps.
E. Liddell
Anno domini 2021 Thu, 21 Jan 12:08:28 -0500 E. Liddell scripsit:
On Thu, 21 Jan 2021 17:48:31 +0100 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
If you're grabbing release versions (14.0.9, frex), the source is broken up into metapackages which can be downloaded and compiled individually. You probably want tdelibs and/or tdebase. Most of the metapackages also have CMake flags that will allow you to compile only one application at a time. tdelibs is not subdivided into applications, so it's the largest chunk you might have to build.
Hope that helps.
Helps a lot. I have 14.0.10, "apt-get source tdebase-tdeio-plugins-trinity" created a directory "tdebase-trinity-14.0.10~pre25" with the sourcecode in it. Then "dpkg-checkbuilddeps" and installed all the missing stuff. Then "dpkg-buildpackage -rfakeroot -b -uc" .. and now I'm waiting ... :)
Thank you!
E. Liddell ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Anno domini 2021 Thu, 21 Jan 19:56:14 +0100 Dr. Nikolaus Klepp scripsit:
Anno domini 2021 Thu, 21 Jan 12:08:28 -0500 E. Liddell scripsit:
On Thu, 21 Jan 2021 17:48:31 +0100 "Dr. Nikolaus Klepp" office@klepp.biz wrote:
Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
If you're grabbing release versions (14.0.9, frex), the source is broken up into metapackages which can be downloaded and compiled individually. You probably want tdelibs and/or tdebase. Most of the metapackages also have CMake flags that will allow you to compile only one application at a time. tdelibs is not subdivided into applications, so it's the largest chunk you might have to build.
Hope that helps.
Helps a lot. I have 14.0.10, "apt-get source tdebase-tdeio-plugins-trinity" created a directory "tdebase-trinity-14.0.10~pre25" with the sourcecode in it. Then "dpkg-checkbuilddeps" and installed all the missing stuff. Then "dpkg-buildpackage -rfakeroot -b -uc" .. and now I'm waiting ... :)
Thank you!
Ok, as deloptes suggested, I built with "export DEB_BUILD_OPTIONS=debug". Now when I plug in a usb thumbdrive, I get lines like these in ~/.xsession-errors :
[FIXME] UNCLASSIFIED DEVICE name: msr type: (null) subsystem: class driver: (null) [Node Path: (null)] [Syspath: /sys/class/msr] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: uas type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/uas] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)]
Anybody knows what that means? Well, besides the obvious?
Nik
E. Liddell ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
On 2021/01/22 05:13 AM, Dr. Nikolaus Klepp wrote:
[FIXME] UNCLASSIFIED DEVICE name: msr type: (null) subsystem: class driver: (null) [Node Path: (null)] [Syspath: /sys/class/msr] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: uas type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/uas] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)]
This indicated devices detected by udev that tdehw lib is not able to classify. Cheers Michele
Anno domini 2021 Fri, 22 Jan 10:22:05 +0900 Michele Calgaro via tde-users scripsit:
On 2021/01/22 05:13 AM, Dr. Nikolaus Klepp wrote:
[FIXME] UNCLASSIFIED DEVICE name: msr type: (null) subsystem: class driver: (null) [Node Path: (null)] [Syspath: /sys/class/msr] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: uas type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/uas] [(null):(null)] [FIXME] UNCLASSIFIED DEVICE name: usb-storage type: (null) subsystem: drivers driver: (null) [Node Path: (null)] [Syspath: /sys/bus/usb/drivers/usb-storage] [(null):(null)]
This indicated devices detected by udev that tdehw lib is not able to classify. Cheers Michele
Ah, ok. That's a consequence from udev calling out many times when it sees a new device. The succeeding call is not shown in the output. Will have to fix that :)
Nik
On 2021/01/22 01:48 AM, Dr. Nikolaus Klepp wrote:
Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
Hi Nik, not sure what are your reasons to get rid of system:/media/ and media:/ protocols. In any case, those are deeply integrated in many places (tdelibs, tdebase, dolphin, k3b, krusader, soundkonverter, digikam, kaffeine, amarok and more) so it will take quite a bit of work. 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.
Cheers Michele
Hi Michele!
Anno domini 2021 Fri, 22 Jan 10:20:46 +0900 Michele Calgaro via tde-users scripsit:
On 2021/01/22 01:48 AM, Dr. Nikolaus Klepp wrote:
Hi all!
I'd like to get rid of system:/media/ and media:/ . My plan is to modify some tdeio libraries of my current TDE installation to do this, but this is where I hit a wall: Is there a way to get a minimal copy of code of the currently installed TDE - namely the tdeio part - build a modified version so that I can just copy the binaries over the current installed versions - without building and installing the whole TDE and installing it?
Maybe somebody can put me on the right track here.
Hi Nik, not sure what are your reasons to get rid of system:/media/ and media:/ protocols. In any case, those are deeply integrated in many places (tdelibs, tdebase, dolphin, k3b, krusader, soundkonverter, digikam, kaffeine, amarok and more) so it will take quite a bit of work.
I see media:/ and system:/media/ break these days. IMO the cause is not in TDE but in the GNOMEisch entanglement. e.g.: I use teminator as terminal. Version 0.97 (from jessie, GTK2) works perfect. pressing <F4> on a folder of a usb-thumbrive media:/sdb or system:/media/sdb brings up terminator in that specific real mountpoint /media/F37B-2EB9. Version 1.91 with GTK3 pops up in my home directory. Same thing happens for gimp, libreoffice ... you name it. Basicly for anything not GTK2 and not TDE, "open with ..." is broken due to this behaviour. So media:/ and system:/media start to really get in my way. Not to stress the fact that these urls are not intuitive to the user any more. "Where is my file that's on the thumbdrive?" is a regilar question, as drag&drop from konqueror to other applications is broken, too, and there is no media:/ outside konqueror.
My plan is to force a rewrite for urls from system:/media/XYZ and media:/XYZ to the real mountpoint and pass that back to the caller of tdeio_media.so or tde_system.so . There are some shell scripts that do stuff, too and then there is tdeio_media_mounthelper, that looks to me like a place to intercept.
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?
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
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
On 2021/01/22 04:24 PM, Dr. Nikolaus Klepp wrote:
I see media:/ and system:/media/ break these days. IMO the cause is not in TDE but in the GNOMEisch entanglement. e.g.: I use teminator as terminal. Version 0.97 (from jessie, GTK2) works perfect. pressing <F4> on a folder of a usb-thumbrive media:/sdb or system:/media/sdb brings up terminator in that specific real mountpoint /media/F37B-2EB9. Version 1.91 with GTK3 pops up in my home directory. Same thing happens for gimp, libreoffice ... you name it. Basicly for anything not GTK2 and not TDE, "open with ..." is broken due to this behaviour. So media:/ and system:/media start to really get in my way. Not to stress the fact that these urls are not intuitive to the user any more. "Where is my file that's on the thumbdrive?" is a regilar question, as drag&drop from konqueror to other applications is broken, too, and there is no media:/ outside konqueror.
My plan is to force a rewrite for urls from system:/media/XYZ and media:/XYZ to the real mountpoint and pass that back to the caller of tdeio_media.so or tde_system.so . There are some shell scripts that do stuff, too and then there is tdeio_media_mounthelper, that looks to me like a place to intercept.
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?
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.
Hi Nik, you open up a Pandora's box.
1. system:/media and media:/ are used in many places, not only in tdeio so you will have to do quite some work there, trust me.
2. system:/media and media:/ are definitely having some issues in R14.0.x. In R14.1.0 there are more changes that are not (and will not) be in R14.0.x, so you may want to test that out perhaps, just to see if you have the same problems or not. Also in R14.1.0 you can open the real folder of the drive instead of the media path and work from there.
3. interaction with other DE when copying from a TDE application: I have not tested that, I only run TDE, so I can't comment much.
4. kdDebug works only if you have compiled packages with Debug option. If you use standard packages from PSb/PTB/official releases, those kdDebug() statements won't do anything. Once you compile with debug, you need to use tdedebugdialog to enable/disable specific debug classes.
Cheers Michele
Anno domini 2021 Fri, 22 Jan 17:49:47 +0900 Michele Calgaro via tde-users scripsit:
On 2021/01/22 04:24 PM, Dr. Nikolaus Klepp wrote:
I see media:/ and system:/media/ break these days. IMO the cause is not in TDE but in the GNOMEisch entanglement. e.g.: I use teminator as terminal. Version 0.97 (from jessie, GTK2) works perfect. pressing <F4> on a folder of a usb-thumbrive media:/sdb or system:/media/sdb brings up terminator in that specific real mountpoint /media/F37B-2EB9. Version 1.91 with GTK3 pops up in my home directory. Same thing happens for gimp, libreoffice ... you name it. Basicly for anything not GTK2 and not TDE, "open with ..." is broken due to this behaviour. So media:/ and system:/media start to really get in my way. Not to stress the fact that these urls are not intuitive to the user any more. "Where is my file that's on the thumbdrive?" is a regilar question, as drag&drop from konqueror to other applications is broken, too, and there is no media:/ outside konqueror.
My plan is to force a rewrite for urls from system:/media/XYZ and media:/XYZ to the real mountpoint and pass that back to the caller of tdeio_media.so or tde_system.so . There are some shell scripts that do stuff, too and then there is tdeio_media_mounthelper, that looks to me like a place to intercept.
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?
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.
Hi Nik, you open up a Pandora's box.
- system:/media and media:/ are used in many places, not only in tdeio so you will have to do quite some work there,
trust me.
- system:/media and media:/ are definitely having some issues in R14.0.x. In R14.1.0 there are more changes that are
not (and will not) be in R14.0.x, so you may want to test that out perhaps, just to see if you have the same problems or not. Also in R14.1.0 you can open the real folder of the drive instead of the media path and work from there.
- interaction with other DE when copying from a TDE application: I have not tested that, I only run TDE, so I can't
comment much.
- kdDebug works only if you have compiled packages with Debug option. If you use standard packages from
PSb/PTB/official releases, those kdDebug() statements won't do anything. Once you compile with debug, you need to use tdedebugdialog to enable/disable specific debug classes.
Cheers Michele
Hi Michele!
Which repository should I use for 14.1.0?
Nik
On 2021/01/22 06:01 PM, Dr. Nikolaus Klepp wrote:
Hi Michele!
Which repository should I use for 14.1.0?
Nik
Hi Nik, you can use Slavek's PTB (Preliminary Testing Builds).
https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
Cheers Michele
Anno domini 2021 Fri, 22 Jan 19:42:56 +0900 Michele Calgaro via tde-users scripsit:
On 2021/01/22 06:01 PM, Dr. Nikolaus Klepp wrote:
Hi Michele!
Which repository should I use for 14.1.0?
Nik
Hi Nik, you can use Slavek's PTB (Preliminary Testing Builds).
https://wiki.trinitydesktop.org/Preliminary_Testing_Builds
Cheers Michele
Ok, got it. Behaviour is still the same, but I got a menu entry to permanently delete an item in the context menu - that's fine. Anyway, where's the fun in having a pandora box and not opening it - especially now siche we have masks and vaczine ? :)
Nik
-
Dr. Nikolaus Klepp -
E. Liddell -
Michele Calgaro