Rox should open the file: tmp/dbxlTZUtV3.html#ceab1215aa5e6c51dd211cb2051ddbeea0a7021f9438e0c8e786bfc5ffdb2949f59e737c45862b87a65332 but cannot though it is duly present inside /tmp. Note that this temporary html file works perfectly when I click directly on..

@Argolance: Your setup is definitely good since you can launch that file by clicking it within Rox.

However, one thing that I've been trying to clarify (and has not been clarified) is - how and who actually triggers the viewing of "tmp/dbxlTZUtV3.html#ceab1215aa5e6c51dd211cb2051ddbeea0a7021f9438e0c8e786bfc5ffdb2949f59e737c45862b87a65332".

In jwm you have a menu file; that menu file contains the "exec" line which will be executed if you click on the menu. On other WMs or panels you have menus based on a .desktop file; if you click the menu, it will examine the associated .desktop file; find the Exec= line, and execute that line.

You say that the problem happens when you click a menu entry. What does that menu entry do? Does it run rox directly? Does it run another script/binary, which then later attempt to launch Rox? Etc.

All I know now, from what you've informed me so far, is that somehow, between the "click on the menu" and the "error", rox is involved. And I'm quite curious to see the original error message you posted is in the form of Rox RPC calls. So someone, something, must know enough about Rox to make RPC calls to start that temporary file "tmp/dbxlTZUtV3.html#ceab1215aa5e6c51dd211cb2051ddbeea0a7021f9438e0c8e786bfc5ffdb2949f59e737c45862b87a65332"

You are also saying things about 'dropbox'. So do you use some binary used to sync files with dropbox? Or something like that?_________________Fatdog64, Slacko and Puppeee user. Puppy user since 2.13.
Contributed Fatdog64 packages thread.

However, one thing that I've been trying to clarify (and has not been clarified) is - how and who actually triggers the viewing of "tmp/dbxlTZUtV3.html#ceab1215aa5e6c51dd211cb2051ddbeea0a7021f9438e0c8e786bfc5ffdb2949f59e737c45862b87a65332".

I don't know how Dropbox is build and what it does, but, it is while running it in terminal (or looking at xerrs.log) that I noticed error messages as I was clicking on menu entries. At startup, a menu entry "Sign in" was not working. After creating the "https" link inside /root/Choices, it worked (as I explained it above). Now I thought it could be possible to solve the second issue, that is to say the one that is on the picture below ("Run Dropbox web site") by creating an appropriate link.

NOTE: I temporarily replaced the /root/Choices/file link with a little script:

Code:

#!/bin/sh
echo blabla > /root/test

... to see if Dropbox was trying to use this link when clicking on the menu entry that sends the error message. Nothing happened! So it is not the link Dropbox is trying to find/use but another mysterious one...

Quote:

You are also saying things about 'dropbox'. So do you use some binary used to sync files with dropbox? Or something like that?

Yes indeed but I thought it was better not to speak so much of Dropbox because it is not the subject of this topic and this issue probably not specific to it but, more generally, encountered running many other applications.

Thanks for the info. I am now quite certain that this is dropbox (or other plumbing, such as xdg-open) issue.

Quote:

Yes indeed but I thought it was better not to speak so much of Dropbox because it is not the subject of this topic and this issue probably not specific to it but, more generally, encountered running many other applications.

Indeed, it won't be proper to discuss it in this thread; but please open a new thread and we'll follow it up there.

Finally NOT a Rox issue, only xdg-open that must be completed/modified/improved, though:

jamesbond wrote:

Instead of patching xdg-open, we can patch Rox and re-compile it so it recognises '#' when using the file:// URL. But I think this is impractical since deployment is difficult: it's difficult to ask everyone to upgrade to the patched Rox, especially if we're talking about old, unmaintained Puppies. And unlike xdg-open, which we can "override" with our own version, you can't easily do this with Rox.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum