THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#297 - pandora button and taskbar autohide
User who did this - bukkit (bukkit)
----------
Alright. The command should supposedly be xfce4-popup-menu (not xfdesktop --menu). The downside seems to be that you cannot quit the menu by pressing a second time, instead it opens a second menu instance. Well, I can live with that, better than with a non-working button in autohide.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=297#comment456
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Stephan Sokolow (ssokolow)
Attached to Project - OpenPandora Main OS
Summary - SuperZaxxon interprets on-disk FAT32 filenames differently than desktop Linux
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Release 1 (Zaxxon)
Severity - Low
Priority - Normal
Reported Version - SuperZaxxon Final
Due in Version - Undecided
Due Date - Undecided
Details - With SuperZaxxon Final, I've noticed that stuff running on the Pandora like Thunar and bash are seeing a different interpretation of filenames on disk than when I remove the SD card and insert it into my desktop PC.
Specifically, the following two mismatches appear to be present when using a FAT32-formatted SD card:
First, the Pandora's VFAT support seems to be be operating with different case-handling settings than desktop Linux distros.
Filenames set in all uppercase are forced to all-lowercase on the Pandora (whether they're set on the desktop or the Pandora) but inserting the card into a PC reveals that the. All-lowercase filenames set by software on the Pandora risk appearing in all uppercase when the card is inserted into a PC. (I think the grsync PND is what created the files in question)
Among other things, this forces me to use EITHER the PND-based copy of grsync over the network OR a desktop-based copy of rsync with an SD card reader but not both because the kernel will preserve case differences like ALBION.BAT vs. albion.bat but rsync think they are separate files. (resulting in Flash-killing, time-wasting deletion and re-creation)
It also makes for irritating entries like "zzt" in DOSBox or "ddr" in PyDance where I can't capitalize the filename properly without employing Department of Redundancy Department with "DDR Songs" or "ZZT.The.Game" as an excuse for mixed case.
Second, SuperZaxxon Final seems to be using a different (though still Unicode-capable) filename encoding than all the desktop distros I've tried.
Filenames are preserved properly and all-ASCII filenames are displayed properly in all cases, but any non-ASCII characters appear as gibberish on whichever system was not used to set them.
I've confirmed this problem with these two filenames:
- 03 - The Foggy Dew with Sinéad O'Connor.flac
- Lucky Star - Native Misao (Touhou - Native Faith) ネイティブみさお 【ネイティブフェイス×らき☆すた】.mp4
As a Canadian user, my desktops use the "en_CA.utf8" locale and the only other distros I've found which have this problem are Slax and the 1.0 release of its successor, Porteus, both of which use ISO-8859-1 (latin1) for filenames.
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=300
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - bukkit (bukkit)
----------
What have I done to deserve this. :) Thank you. I'll try.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment455
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - Jeff (skeezix)
----------
Very good :) I hereby put you in charge of reviewing the wikis to audit for usability :)
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment454
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - bukkit (bukkit)
----------
I changed the wording at http://pandorawiki.org/Pnd_run.sh#Creating_a_launch_script_for_PND. I'd like you to have a look and amend, if necessary.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment453
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - Sébastien Huss (set3)
----------
wording for the help would be welcome.
And as it sound like you forgot, the -d option was a request from the case designer you forwarded to me.
As I have eard anything from him since a while, I guess nobody use that anyway
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment452
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - bukkit (bukkit)
----------
I actually did consult the PXML specification there, and that contributed to my errors, I'm afraid. Yes, it mentions the unique ID (as a placeholder in package id *and* application id), but in fact first the appdata entry gets extracted and fed as pndid to pnd_run.sh via -b, the unique id only being used if appdata was absent. According to the c source above, this seems to correctly describe the behaviour.
I should be able to amend the wiki (about pnd_run.sh) a bit, too. If I do, maybe one of you guys should check if that comes out acceptable.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment451
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - Jeff (skeezix)
----------
I agree; the pnd_run.sh command line help isn't as ... helpful as it could be.
The unique-id and such is more described here:
http://pandorawiki.org/Libpnd_hub
which leads to
http://pandorawiki.org/PXML_specification
A user shouldn't generally have to consult such levels of documentation however :)
This is all due to history and changes over time, but yeah, the command line args coudl be much better explained.
-b is the appdata or unique-id name
-d is an override IIRC; without it, -d is implied to be /pandora/appdata/THING (as specified by -b)
with -d, you could specify -b as 'foo', but then override it and say -d /pandora/appdata/something-else if you really wanted to.
sebt3 -- you want to updat ethe command line docs to be more usable, or you want me to maybe recommend some wording?
Is there actually a -d bug, then maybe you can look into it (or we can remove -d, since I imagine few if anyone use it :O)
jeff
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment450
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - bukkit (bukkit)
----------
Alright, I think I see. Maybe. But I'd claim this confusion is not my fault. I'll summarize:
You say: -b is used to specify the desired directory in /pandora/appdata
pnd_run.sh says: -d is used to specify the directory in /pandora/appdata
(You say: -d isn't evaluated)
pnd_run.sh says: -b pndid : name of the (unison) directory mount-point, default is name of the pnd file
you say: -b should specify the preferred appdata name, or failing that, the unique-id, and *not* the file name
But no other doc, wiki or text states -b should specify the appdata name... and hardly anything says what this unique id is (it's faulty to use the application id, like I did, you say, which is named the uniqueID in the PXML.xml doc and which the wiki (http://pandorawiki.org/Pnd_run.sh) refers to as PND ID, and states should be passed as -b param... just like pnd_run.sh, like so: "-b pndid")
....
So maybe this ended up being a very wrong and confusing documentation inside and outside of pnd_run.sh. Possible. I'll give it a try. Tomorrow.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment449
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#299 - run_pnd.sh does not follow PXML.xml or "-d"-Parameter
User who did this - Jeff (skeezix)
----------
also note.. "package id" is 'new'; the whole package layer is relatively new in PXML terms (added to help with the repo); libpnd's app execution _does not_ care about package at all in fact.. its used outside of the system for the most part. The package-id is not used for appdata naming or the like.
Take a look at the .desktop files to get an idea what happens, they will show you exactly what the pnd_run.sh command line looks like for a normal invocation. Also note there are other tricks, like the auto-generated 'info/help' .desktops and such.
A pnd_run.sh invocation will look like:
......pnd_run.sh -p "/meda/foo/pandora/menu/Dosbox.pnd" -e "rundosbox.sh" -b "dosbox"
-- something like that
The -e part will change to select a different subapp; the -b stays the same, since you want it to run _in the same place_.
If you wanted 2 subapps to run in different data spaces, they could each have their own appdata which would change the -b, but thats not typical.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=299#comment448
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.