The problem:
A right-click on a clear area of the desktop (under the default configuration) brings up the menu, as expected. After this is cleared (by a left-click), subsequent right-clicks on the desktop icons (including the drive icons) result in the desktop menu appearing, as if they were right-clicks on a clear area of the desktop (or as if the icons were not there, or simply not identified).
A subsequent left-click (or in some/many cases two spaced left-clicks) on one of the icons results in it working as expected. Following this, right-clicking on the icons also works as expected (as if the "problem trigger" had been reset).
Another right-click on a clear area of the desktop recreates the problem, and subsequent left-clicking on an icon clears it again.

ETP wrote:

Bug confirmed. (Also exists in 5.3.3.2.) It would seem that we have all been living with it!
Minor as you say, but very confusing for anyone new to Slacko.

Note that the .pet offered in that blog entry is no longer the latest ROX-Filer .pet. For the latest, see Barry's blog entry: ROX-Filer squashed log-window

But those .pets may not be best for use with Slacko, since 01micko reports that "For some reason rox needs to be compiled in Slacko or else Fido refuses to work." (See his comment under Barry's blog entry: ROX-Filer focus problem fixed) So it is probably best to compile on Slacko from the patched source, which can be found in the file rox-filer-20111022-patched3.tar.gz at http://bkhome.org/sources/alphabetical/r/.

EDIT: Also note that installing a .pet would have side-effects. For instance, your PuppyPin file would be overwritten with the PuppyPin used for Wary and Racy. So, again, it's best to compile your own from the patched source, or wait for someone to make a Slacko version of the .pet. (Even then, if you have customized your PuppyPin, you would want to back it up before installing the new .pet.)

The following lines in pkg_chooser.sh prevent the use of quirky and wary5 repositories in slacko, even though the database files for both are included in the distro, and so check boxes are available in the configuration dialog -- they just don't do anything:

1. In Slacko 5.3.3, run PPM and choose Configure package manager (or, in the Ziggy UI, the button with the screwdriver and spanner).

2. Click either of the check boxes for puppy-quirky-official or puppy-wary5-official. (If you already had 5 boxes checked, you will need to uncheck one so as not to exceed the limit of 5.)

3. Click OK.

4. Exit from the PPM.

5. Run PPM again and note that the newly selected repo is not listed under Repositories.

Perhaps this is intentional to discourage users from installing stuff in Slacko from these older repositories. If that is the case, their database files should probably be removed to prevent them from showing up in the configuration dialog. (Although I am guessing this isn't intentional since the even older Puppy-2, -3, -4, and -5 repositories are available, and don't have this issue.)

Thank you!!! I am a newbie to linux and thought I had broken my puppy or it's tail beyond all repair. 01micko's post fixed that. I installed the ziggy_patch_ppm-2.pet and that fixed the broken Puppy Package Manager. Tail wagging! Opps sorry-- I think I posted this in the wrong place.

My first post, so here goes the mandatory intro: hello to all around here doing a nice job of bringing the super-complicated linux system into puppy level .

And now to the point. Perhaps not a bug as such (although I did stumble upon a few along my 3-day long puppy linux career) but can anyone tell me how to make the download manager in ff/seamonkey open downloaded files according to shell settings (or whatever) and open containing folders (that's in the right-click menu) ?

Using slacky 5.3.3 windows installer (from this forum) clean install, seamonkey as included and namaruka post-installed from a .pet.

EDIT: allright, have managed to get "open containing folder" working by selecting /usr/local/bin/rox on the Open With dialog (and setting as default); should be pre-configured within the puppy, methinks

The /usr/local/jwmconfig2/panel-buttons script supplied with Slacko 5.3.3 adds one extra comment and deletes one line in /root/.jwmrc-tray every time a button is added to the tray.

The comment added is always a copy of this existing comment:

Code:

<!-- Additional TrayButton attribute: label -->

The line removed is the first non-blank line following the last button added.

If the original /root/.jwmrc-tray supplied with Slacko 5.3.3 is used as a starting point, adding buttons causes the following behavior:

The first time a button is added, the line deleted is just a comment, so the tray is created as expected. But when a second button is added, this line is deleted:

Code:

<Pager/>

So the pager buttons (for switching desktops) disappear.

Adding a third button just deletes another comment, but adding a fourth button deletes this line:

Code:

<TaskList maxwidth="25"/>

So the task list disappears.

Adding a fifth button deletes this line:

Code:

<Dock/>

And the dock is gone.

Adding a sixth button just deletes another comment, but adding a seventh deletes only the first line of a comment, which confuses JWM, and everything else vanishes -- in this case, the swallowed program (xload) and the clock.

Adding an eighth and ninth button deletes the last two lines of that same comment, so JWM is no longer confused, and the swallowed program and the clock reappear.

OK, I think I need not continue adding buttons. You get the idea.

The reason that lines are being deleted is that the number of lines remaining in .jwmrc-tray after the last line with a TrayButton definition is sometimes calculated incorrectly. And that happens because the total number of lines in .jwmrc-tray is sometimes calculated wrongly. The total is found using wc -l which counts newline characters, not lines. If the last line in the file has no newline character, the value returned by wc -l will be one shy of the actual number of lines.

The original .jwmrc-tray file supplied with Slacko 5.3.3 has no newline character in the last line.

While supplying a .jwmrc-tray file that ends with a newline character would make this problem go away at least initially, it wouldn't be the most robust solution. A user might manually edit the file and leave off the final newline -- something that is not ruled-out by the JWM documentation, and something that JWM itself is perfectly happy with. It would be better if the panel-buttons script could tolerate a configuration file that didn't end with a newline character.

As for the extra comment that gets added every time a button is added, that doesn't cause any problems (other than making the file grow unnecessarily), so could be ignored. But it could be fixed by filtering the comment out of CURRENTBTNSCODE by replacing line 24:

That way, if the user happened to add a single-line comment containing the word "TrayButton", it would not become part of CURRENTBTNS, even if it didn't also contain the word "Additional". This would also eliminate the need for line 26.

By the way, although I ran into this problem in Slacko 5.3.3, it looks like the same panel-buttons script is in jwmconfig2-121105.pet, which I think is used by Slacko 5.4.

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