Puppy Linux Discussion Forum

[Mike Walsh]

Afternoon, all.

Well, this is embarrassing.

After the success I had with my PepperFlash .pets,

http://www.murga-linux.com/puppy/viewtopic.php?t=106409

....I've decided to turn my hand to the 64-bit version of SlimJet; a browser which, for me, has pretty well replaced Chrome (and I've been a Chrome user since it was in beta, back in 2008).

After making the release announcement here, I've had to withdraw them temporarily, upon discovery that they won't actually start from the MenuEntry..!

32-bit SlimJet normally resides in /usr/lib; I've located these in /opt (a nice 'catch-all' directory), which quite neatly sidesteps the problem with the rather non-standard implementation of the way the lib32 & lib64 directories are linked in 64-bit Pups. Some link in one direction, some the other, and some don't link at all. Plus, Tahr64 has 32-bit compatability libraries, whereas others, such as Slacko64 and Lighthouse64, don't appear to have anything resembling these.

I've been using trio's 'Pet-Maker' package, which is a really useful .pet. Initially, I used it for the SFS packages as well as the .pet ones, although recently I've been experimenting with the 'mksquashfs' command, which seems to work just as successfully.....I suspect the dir2pet script within trio's package probably makes use of this, as well as others. Remember, I'm still quite a 'noob' when it comes to this side of things, so be gentle with me..!

They will all start quite happily from

a) The SlimJet wrapper-script itself
b) The symbolic link to the above, in /usr/bin, and
c) The .desktop file. BUT:

I cannot, for some reason, get them to start from the Menu entry. What I'm wondering is this:-

Does the .pet/SFS need to include an entry for /root/.jwmrc? (Since this appears to be where the Menu entries are generated, although I'm not at all certain of the mechanism...)

I understood that the .desktop file would somehow generate the Menu entry during the installation process; if I'm wrong here (and I suspect I am), I'm more than willing to learn the correct way of doing this.

My .desktop file for these SlimJet packages is as follows:-

[nic007]

Have you run fixmenus yet?

[Mike Walsh]

Hi, Nic.

No, I'll be honest with you; I'd forgotten about that. I mean, the entry shows up in the Menu.....but it doesn't actually do anything, despite showing the correct application path in /root/.jwmrc.

As I understand it, fixmenus is used to make 'reluctant' menu entries show up in the first place.....or have I got the wrong end of the stick? I mean, it's annoying to not have every part of an application working as it should.....but aside from that, it's unprofessional to release something for general consumption in that condition. It gives the impression that you couldn't care about doing the job properly.....and it doesn't give Puppy very good publicity, either.

Hence why I've withdrawn them until I can get them fixed. Every part functions as it should.....apart from the Menu entry. Despite the fact that those of us familiar with Puppy know there's lots of different ways to launch something, that's the one method the majority of people will wish to use.

I'll give 'fixmenus' a try, but I'm not hopeful..... I'll let you know what happens.


Mike.

[Mike Walsh]

Hi again, Nic.

Nope. Didn't do a thing. It's not that the menu entry isn't showing up ( it does).....the entry, as far as I can tell, is correct in /root/.jwmrc. too (application path and everything); but it simply won't execute.

My usual method, since I prefer to work from desktop icons, is to drag an app's .desktop entry onto the desktop, edit and tart-up as necessary, and to use that.....but for some people, even that's too much like hard work!

But the point is, the Menu entry should work. That's the primary method employed by most people to launch something.....and it isn't doing its job. So; where have I gone wrong with it?

Anyway, thanks for the suggestion; it was appreciated, even if it wasn't the 'magic bullet'!


Mike.

[Mike Walsh]

A question.

In my .desktop file above, does the 'Exec' entry refer to the /usr/bin executable? Do I have that part correct?

Edit:- Y'know, thinking about it, I wonder if some of the problem might be down to my spelling & syntax (once again!) I.e., 'Slimjet' instead of 'SlimJet'.....or maybe all lower case, right the way through..?

I know how fussy Linux is about dotting the i's, and crossing the t's...


Mike.

[Moat]

Weird one! Opening from the .desktop file directly, but not the menu entry (which should reflect that same, exact .desktop file).

I'm no expert, but wonder if there's a conflicting .desktop file floating around the system somewhere (/usr/local/** ??) with an older, improper "Exec=" entry, that's taking menu priority over the /usr/share/applications .desktop file... Pfind would likely uncover it's location, if so.

FWIW,

Bob

[Mike Walsh]

Hallo, Bob.

Actually, now you mention it.....

There's a SlimJet /usr/lib/entry keeps popping up, every time I install a SlimJet package for testing purposes. I made up a version of 10.0.0.0., a little while back, which was located in /usr/lib/slimjet. Now, although every trace of it has been wiped from the system (there's definitely nowt in /usr/lib any longer).....and I've edited /root/.jwmrc, and /root/.jwmrc-previous, and done a re-boot to ensure the alterations got saved.....it keeps on popping up from somewhere. And I can't for the life of me figure out where it's coming from.....

Are there any other .jwmrc-related files, elsewhere in the system, that I'm not aware of? 'Cos it's the only thing I can think of that's interfering with the normal launch process.....

Any ideas, mate?

Edit:- Screenie below of what pFind has thrown up.



There's not one item there that I haven't put there myself.....so where the hell is usr/lib/slimjet coming from?

Here's the extraneous internet entry:-



Wait a minute...!. I've just discovered another 'dead' entry , under 'Networking'...



.....and pFind doesn't throw this up at all. Here's the /root/.jwmrc entry for it, highlighted (if you can read it):-



So where's it coming from? (*scratches head*) Is there by any chance some kind of log in the system that hangs onto stuff, long after it's been deleted?


Mike.

[Sailor Enceladus]

[Mike Walsh]

Hi again, Bob.

Just had a thought. You take a gander at both of the extraneous 'FlashPeak SlimJet' entries in .jwmrc; both of them have a '%U' at the very end of the exec phrase. Nothing else in .jwmrc is showing this.....yet pFind doesn't 'find' them.

I was just considering what you meant by improper 'Exec' entries... What d'you think?

(This is in Slacko64 6.3.0 at the moment, BTW.)


Mike.

[Mike Walsh]

[Moat]

Mike -

1) Click the "eye" on Rox's toolbar, to uncover any hidden files and make sure your not missing anything in /usr/share/applications and /usr/local/share/applications.

2) Hmmm... I believe the text displayed in the menu entry (as "FlashPeak Slimjet" in your screenshot) is defined in the .desktop file's "Name=" line... since your screenshot's menu entry displays differently from what you posted earlier as the actual .desktop file's "Name=SlimJet" entry (and there is no "FlashPeak Slimjet" entry to be found in said above .desktop file) - this still makes me suspect there's a stray, old .desktop file being used by JWM to build the menu, instead. Maybe look further up the .desktop directory list (after making sure Rox is showing all/hidden files), for something alphabetically beginning earlier with, say, "Flashpeak" instead of "Slimjet" - or whatnot.

3) I also believe the "%U" has something to do with allowing a browser to open an external link directly (from, say, your email client) - so it will open the browser directly to the link, and not just open as usual to your default home page. I think that's what that's for, anyway...!?!

4) Remember, you can test any of the (questionable) exec lines by running 'em in a terminal, and see what happens (errors, nothing opens, etc.).

In the past I've noticed that some updated application's binaries require a different/updated exec command to fire - and therefore a new/updated .desktop file to go with it (possibly even with a different name). And sometimes the old, now-broken ones get left behind - muckin' things up a bit.

Hopefully some of that might be of help, but like I said - I'm no expert at these things! (Where's Semme when ya' need him?! )

Bob

[perdido]

Look in the file /opt/slimjet/flashpeak-slimjet

Seems to generate its own desktop file when run.

[nic007]

The U% in the name of the executable is definitely incorrect. This is what I would do: delete that entry in .jwmrc > specify the full path of the correct executable in the desktop entry > do fixmenus > restart JMW

[Mike Walsh]

[B.K. Johnson]

Mike
Just a thought from one who knows nothing!
/opt is not in your path. You may need to link to /usr/bin which is.