|
241 | Application | Feature Request | Low | MiniMenu shall remember state for next start | Closed | |
Task Description
With the setting "Live (not exit) on app run?" set to "NO" the currently selected tab and item shall be remembered, so that you return to the same state, in which you left MiniMenu. |
|
247 | Core | Bug Report | Low | pnd_make.sh can't handle PND with spaces in the path | Closed | |
Task Description
pnd_make.sh can't handle PND with spaces in the path. For example, if the label of the volume where the PND is saved, has spacebars.
The Problem is line 655:
655: PND=$(readlink -f $PND)
Bash handles a path with spacebars as two seperate arguments for the readlink command.
The problem is, that i don't know a solution for this problem. |
|
248 | Core | Feature Request | Medium | Support for hibernation by caching to SD card | Closed | |
Task Description
It would be very desirable that the PandoraOS could hibernate, and that this action can easily be accessed/triggered with either a hotkey or as an action for the max-idle-time-event or lid-close-event.
That would be the battery friendly universal action to quickly pause/resume any arbitrary application/task.
The current standby mode is far to power consuming for breaks longer than ~ 1 hour. Improving standby mode to be more battery-friendly would of course be too highly appreciated and practical.
If hibernation is triggered, RAM content gets written to a special file or partition on a SD card. The boot-manager of course needs to recognize such a RAM-file on SD-cards. In case it finds more than 1, i.e.: multiple cards/partitions, the one with the newest timestamp gets priority.
256MB RAM with about 10-20 MB/s read/write time to SD, would result in 25-12 seconds for going into or out of hibernation, which would be acceptable for me. In practice it would mean, that if I quickly have to pause me OpenPandora operation (i.e. train stop), I just close my lid, and put the Pandora into my pocket (2-4 seconds), and I am then trusting that the rest reliable happens in my pocket (10-20 seconds). |
|
249 | Application | Bug Report | High | File Browser Thunar - After 2 nub double-clicks unreact ... | Closed | |
Task Description
If I navigate via keyboard (KEY UP/DOWN to move in lists, ENTER level down, BACKSPACE level up) I experience no problems at all. I can go many levels up/down, change to other folders, etc. No problems.
But if I navigate with the nubs, and using the right-nub-up-direction to trigger a double click, this only works 1-2 times, and from then on, the files/folders in Thunar cannot be clicked any further. I am stuck then.
A look into dmesg reveals this:
keyboard.c Can't emulate rawcode for keycode 139
The timestamp of that specific keyboard.c error messages exactly correlates with the bug occurrence times. (uptime timestamps matched with dmesg timestamps)
I tried alternative filebrowsers such as emelFM2, and there the problem does not exist, meaning I can trigger as many double clicks I want!
I am using HotFix 5 Alpha 4 on an SD card. The bug already annoyed me on a HF5 on the NAND. |
|
254 | Core | Bug Report | High | Several apps leave graphical artefact overlay (ghost) a ... | Closed | |
Task Description
After quitting some apps, their last graphical output remains on the screen, which covers a large area of the Pandora, and therefore makes it quite unusable, so that only a full restart resolves this issue.
As this happens in many apps (Mednafen-GB, Dark Light Battles, etc) this must be a problem within a shared library (driver, graphics lib, window manager framework, or similar). |
|
255 | Core | Bug Report | Medium | Waking Pandora with closed lid nevertheless turns scree ... | Closed | |
Task Description
Steps to reproduce the undesired behavior:
1) Close the lid. The screen goes off.
2) Slide the power switch to the right. The device goes into low power mode. The screen remains off.
3) Slide the power switch to the right. The device goes into normal power mode and turns on the screen although the lid is still closed!
Desired behavior:
Ad 3) If the system catches the event "wake from low power mode" it should first wake the system, then check the "lid open/close state", and set the screen on/off state accordingly. By this you could use the Pandora as a power-efficient sleep/wake-able closed-lid-device, practical for i.e. audio applications.
I am using: Pandora OS R1.HF6.A4 |
|
259 | Core | Bug Report | High | Hold switch does NOT lock keyboard! Especially crucial ... | Closed | |
Task Description
Apps, which operate with the Pandora in closed lid mode, such as audio players, server processes, etc, in a button-press-probably environment (as i.e. your pocket) still CAN receive the shoulder button L + R key presses, and if they have a meaning in these programs, they could trigger undesired actions.
And also in the current implementation of the Low Power Mode (See: FS#260) key presses may still be received.
Therefore I strongly propose to implement the HOLD switch to en/dis-able a keyboard lock.
IN DETAIL: This shall be global, meaning that the input processing software (however this is implemented on the Pandora: kernel, driver, … ) keeps the lock state (on/off), and if the keyboard state is off,
a) discards all input, or
b) if it makes sense for some reason/applications (any ideas?) just writes them into a queue/buffer, which gets (partially) executed or made accessible to certain software after the keyboard gets unlocked again.
FYI: I have tested the hold switch with the Pandora Input-Tester, and it is recognized. So my report is definitely a software (and not an hardware) issue. |
|
263 | Application | Bug Report | Critical | MiniMenu with "Auto discover pnd apps?" set to NO hangs ... | Closed | |
Task Description
BUG DESCRIPTION:
On my SD card with Pandora OS 1.6.4 I changed MiniMenu's setting "Auto discover pnd apps?" to NO, and then the program remained in an endless loop showing "Setting up menu...", crashing, "Setting up menu...", crashing, and so on.
BUG REPRODUCTION:
The variable filesystem.do_pnd_disco set to the value 0 definetely causes the crash, but maybe only in conjunction with some of my other settings?!
Therefore see my attached config file mmpref.conf.
Maybe related to FS#79 , hard to tell, as this is a very minimal report.
Definitely not related to my previously reported MiniMenu bug FS#262
WORKAROUND:
1) If your default GUI is:
a) MiniMenu: Then after rebooting, MiniMenu will still be caught in an endless loop! Therefore boot up from an auxilary/temporary volume rather than your volume with the damaged MiniMenu! If your ruined system is on the NAND boot from an SD card, if the ruined system is on SD card, boot from NAND or another SD card. In doubt read: http://pandorawiki.org/Running_Linux_from_an_SD_card
b) Other than MiniMenu such as XFCE: Then you are lucky. Simply start into XFCE, and continue with the next step.
2) Open ~/.mmpref.conf with a text editor and set the variable filesystem.do_pnd_disco to the value 1.
3) Reboot into your healed volume. |
|
264 | Core | Bug Report | Low | Issues with HOTFIX 6 R1 Beta | Closed | |
Task Description
I started with hotfix 5 and when I used the Left Nub for mouse movement it performed well.
I installed HOTFIX 6 R1 Beta and the Nub works fine except pushing up. It moves the cursor very slow and all other directions just fine. The other nub works just fine as well.
This only began after I installed HF6R1B.
I also had to install the Hotfix twice due to sustained system freeze upon start up on the first attempt.
I enabled gui choice but minimenu does not function it just cycles back to GUI choice. |
|
266 | Application | Bug Report | Low | hf6rc: Unable to enter Low Power Mode with lid shut: | Closed | |
Task Description
Since hf6rc was installed I am unable to enter low power mode.
I did pull up the new lid config settings script and selected switch off screen.
Reproducable.
Nothing happens when the power switch is moved fully to the right for a short time.
I expect it to entry low power mode. quirky for it not too.
workaround: easy - enter LPM before closing lid.
btw: unable to select hf6 in reported version. |
|
267 | Core | Bug Report | High | HF6-Updater.pnd loses pnd_run.sh | Closed | |
Task Description
Several users have reported that running HF6-Updater.pnd leads to a missing /usr/pandora/scripts/pnd_run.sh
Possibly the file is locked by the Updater itself when installing pandora-libpnd_1.0-r56.5_armv7a.ipk
Forum thread:
http://boards.openpandora.org/index.php?/topic/5652-hotfix-6-final-released/page__view__findpost__p__99313 |
|
268 | Core | Bug Report | Low | HF6: error in op_power.sh | Closed | |
Task Description
When powering the system off after it has been in low power state once, an error is reported by op_power.sh, line 173.
Unfortunately I don't have the full message as it's visible on the console only for a short time before the screen turns off.
From looking at the script, the "fi" in the last line might be superfluous. |
|
275 | Core | Feature Request | Low | User should be a member of the cdrom group | Closed | |
Task Description
These permissions are needed for CD/DVD burning/player apps.
From bdc88595d8af726b3bf4745ece310f92299d8759 Mon Sep 17 00:00:00 2001
From: Paul Dersey
Date: Sun, 19 Feb 2012 17:22:41 -0500
Subject: [PATCH] pandora-first-run-wizard: add user to cdrom group
---
recipes/pandora-system/pandora-first-run-wizard.bb | 2 +-
.../pandora-first-run-wizard/first-run-wizard.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes/pandora-system/pandora-first-run-wizard.bb b/recipes/pandora-system/pandora-first-run-wizard.bb
index 904dc4a..a63dc0c 100755
--- a/recipes/pandora-system/pandora-first-run-wizard.bb
+++ b/recipes/pandora-system/pandora-first-run-wizard.bb
@@ -6,7 +6,7 @@ RDEPENDS = "hsetroot zenity dbus pandora-wallpaper-official tslib tslib-calibrat
COMPATIBLE_MACHINE = "omap3-pandora"
-PR = "r28"
+PR = "r29"
SRC_URI = " \
file://first-run-wizard.sh \
diff --git a/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh b/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
index a801e3f..f30b80e 100755
--- a/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
+++ b/recipes/pandora-system/pandora-first-run-wizard/first-run-wizard.sh
@@ -88,7 +88,7 @@ while ! username=$(zenity --title="Enter your username" --entry --text "Please c
zenity --title="Error" --error --text="Please try again." --timeout 6
done
-while ! useradd -c "$name,,," -G adm,audio,video,netdev,wheel,plugdev,users "$username" ; do
+while ! useradd -c "$name,,," -G adm,audio,cdrom,netdev,plugdev,users,video,wheel "$username" ; do
username=$(zenity --title="Please check username" --entry --text "Please ensure that your username consists of only\nletters and numbers and is not already in use on the system." --entry-text "$username")
done
--
1.7.8.3 |
|
276 | Core | Feature Request | Low | Kernel 3.2.x: add script to activate zram | Closed | |
Task Description
Please add a script to activate zram (RAM compression) when using the new kernel. More info about how to do this is available in this post:
http://boards.openpandora.org/index.php?/topic/7844-superzaxxon-beta-3-released/#entry138834
http://boards.openpandora.org/index.php?/topic/7226-superzaxxon-beta-11-released/page__st__20#entry128665
Please be aware though that Linux-SWAT had to explicitly set a value in "/sys/block/zram0/disksize" to get it work with Slackware. Over here the following is automatically set:
pandora:~$ cat /sys/block/zram0/disksize
61648896
Sadly I can *not* change this value, even using sudo:
pandora:~$ ls -l /sys/block/zram0/disksize
-rw-r--r-- 1 root root 4096 Apr 9 12:51 /sys/block/zram0/disksize
pandora:~$ cat /sys/block/zram0/disksize
61648896
pandora:~$ sudo echo 61648888 > /sys/block/zram0/disksize
-bash: /sys/block/zram0/disksize: Permission denied
Basically the following commands are required in a startup script to automatically create the "compressed swap inside RAM" aka zram (possibly a check if the modprobe was successful makes sense as well as checking for the size of the created ramdisk):
modprobe zram
mkswap /dev/zram0
swapon -p 5 /dev/zram0 |
|
277 | Core | Bug Report | Medium | SuperZaxxon B3: minimenu does not scan all folders | Closed | |
Task Description
Using SuperZaxxon beta3 (already observed it with beta2) it seems as if minimenu is not scanning all folders (and subfolders) correctly. Please have a look at this post for more information:
http://boards.openpandora.org/index.php?/topic/7558-superzaxxon-beta-2-released/page__st__140#entry138597 |
|
278 | Core | Bug Report | Low | Kernel 3.2.x: broken middle click on right nub | Closed | |
Task Description
Using kernel 3.2.x middle click with the right nub is no longer working. With the "old" kernel you get a middle click when pushing the right nub down, this is no longer the case when eg using SuperZaxxon Beta3 (was already the case in SuperZaxxon Beta1 with kernel 3.2.1). As long as you are using kernel 2.6.27.x middle click is working as expected. |
|
289 | Application | Bug Report | Medium | "sudo find /" produces assertion | Closed | |
Task Description
$ sudo find /
find: ftsfind.c:477: consider_visiting: Assertion `ent->fts_info == 11 || state.type != 0' failed.
Aborted
This is fixed by updating findutils to latest version using
sudo opkg upgrade findutils
Release SuperZaxxon 1.5
(not Beta 3, as given in "Reported Version" field, but there the release cannot be chosen). |
|
294 | Core | Bug Report | Low | Left nub not working with kernel 3.2 | Closed | |
Task Description
Left nub doesnt work when powering on into SuperZaxxon Final with kernel 3.2.
Rebooting into kernel 2.6 fixes it until sleeping or powering off. After which rebooting into 2.6 is once again necessary to get the left nub working. |
|
298 | Application | Bug Report | Low | Mousepad only searches once | Closed | |
Task Description
Whenever I search text in an open Mouspad document, it works fine the first time. As soon as I close the search dialogue and re-open it, the "find" (resp "find and replace" in replace dialogue) button is greyed out and unclickable. (This is the state the dialogue is in before typing anything, but this time, typing doesn't help.) "return" also doesn't work. Only help is closing and reopening Mousepad. |
|
302 | Core | Bug Report | Low | Correct keymap not available during login process | Closed | |
Task Description
The correct keymap, as matching the characters printed on the keys, is available when running the First Boot Wizard, but not during login.
This means that special characters like ! ( ) and so on, which you enter via Fn-[2nd key] cannot currently be used in a username nor password.
My first experience with my Pandora was therefore that I had to reflash the OS due to this as I had locked myself out because I used a special character in my first chosen password.
Also reported here:
http://boards.openpandora.org/index.php?/topic/10112-question-mark/#entry188179 |
|
303 | Core | Bug Report | Low | pppd 2.4.3 has a bug, recommend upgrade to ppp 2.4.5 | Closed | |
Task Description
pppd 2.4.3 doesnt auto reconnect (in my setup) even if configured to do so (persist). Found a ppp bug report confirming this ( http://ppp.samba.org/cgi-bin/ppp-bugs/resolved?id=1110;user=guest - "ppp-2.4.3 / pppoe not reconnecting") and that it has been fixed. I compiled pppd 2.4.5 and that reconnects just fine. |
|
304 | Core | Bug Report | Low | bluetooth serial port sleep causes lost / frozen connec ... | Closed | |
Task Description
I experienced (reliably) 3 times that if I had an idle ppp/rfcomm connection to my phone, it would eventually freeze so that the phone reported no active bluetooth connection and the pandora ppp would still think that the connection is active, but no data would flow. Killing pppd and re-trying would fail opening of the rfcomm link with "Host is down".
Disabling & enabling bluetooth "fixed" this so that pppd worked again (so it is not the phone that was "down").
Adding these lines to op_bluetooth_work.sh (apparently atleast) fixed it for me:
add between lines 14-15:
echo 0 > /sys/devices/platform/omap_uart.0/sleep_timeout
(or at any place during enable for that matter)
And to disable (before exit 0, line 30) to save power when bluetooth is off and restore normal settings:
echo 10 > /sys/devices/platform/omap_uart.0/sleep_timeout
I remember mentioning this way back when I last tested bluetooth, but got a reply that this should not be needed because we have flow control between the bt chip and pandora. But if a sleeping serial port loses a character when somebody sends a burst to it, what could flow control do? If it reported not ready to receive, the character would never be sent (and things would freeze...). If it reports ready to receive (what I think it does) the character will be lost. One would need to periodically disable the serial port sleep (and enable ready to receive) for a moment to check for pending data, but I think this would use more power than keeping the serial port active and/or possibly cause way too big delays.
I'm not really certain of this thing (whether this is a workaround, hack or a real fix... and whether my interpretation of what is happening is correct - i have no real proof), but I think that reporting what I've found is better than not. (And am I the only user of bluetooth with an old phone for internet (ppp+rfcomm, not pan)? ...) |
|
305 | Core | Bug Report | Low | [PATCH] bluetooth startup doesnt restore enabled state | Closed | |
Task Description
op_bluetooth.sh doesnt remember to call op_bluetooth_work.sh in the startup case. Patch inlined here (maybe broken, but for fast reading) and behind link: http://urjaman.dyndns.info/bluetooth-startup-fix.patch
--- op_bluetooth.sh.org 2012-11-24 01:54:53.000000000 +0000
+++ op_bluetooth.sh 2012-11-24 02:06:51.000000000 +0000
@@ -7,8 +7,13 @@
cd "$HOME"
if [ "$1" = "startup" ]; then
- [ -f "$LOCK" ] && sudo /usr/sbin/hciconfig "$INTERFACE" up pscan 1>/dev/null && sudo /usr/sbin/bluetoothd || echo "Bluetooth: User has not enabled Bluetooth."
-
+ if [ -f "$LOCK" ]; then
+ sudo /usr/pandora/scripts/op_bluetooth_work.sh 1
+ INTERFACE="`hciconfig | grep "^hci" | cut -d ':' -f 1`"
+ sudo /usr/sbin/hciconfig "$INTERFACE" up pscan 1>/dev/null && sudo /usr/sbin/bluetoothd
+ else
+ echo "Bluetooth: User has not enabled Bluetooth."
+ fi
else
# Figure out if Bluetooth is running or not |
|
306 | Core | Bug Report | Low | Issue with Network Notification pop-ups | Closed | |
Task Description
Clicking on the button in a notification used when WiFi is enabled (such as the one stating that Wireless Networks were found), doesn't close the notification. In order to close it, I have to click the X button that's in the top-left. |
|
310 | Core | Bug Report | Medium | mkdosfs is broken - creates 1GiB filesystems | Closed | |
Task Description
When a partition is bigger than 2 or 4 GiB (can't recall now) it makes a "default" 1GiB filesystem. Propably missing large file support in the build. Also, the pandora sd card formatter is missing -F 32 so it makes (i think, it is some time from when I noticed this) FAT16 partitions... |
|
311 | Core | Bug Report | Medium | [PATCH] Thunar configurable trash | Closed | |
Task Description
Not my work, but since I think my reply to ED on the forums will get buried I made this report.
The post with patch: http://boards.openpandora.org/index.php/topic/11189-its-arrived-questions/?p=210363 |
|
312 | Core | Bug Report | Low | Special character in password | Closed | |
Task Description
problem:
setting a username and password using first setup wizzard it's possible to set special character like @#*%/ ect...
the login manager don't support this characters, so you need to reset the device.
possible solution:
1. disable the possibility of setting special characters.
2. implement special characters in login manager. |
|
313 | Core | Bug Report | Low | WiFi LED Not Triggered on First Activation | Closed | |
Task Description
The first time WiFi is enabled after boot, using either the the config button menu or the Toggle WiFi menu option the WiFi LED does not light up. (though the WiFi itself does work)
Once it has been enabled and disabled for the first time, it will work normally for subsequent uses of the WiFi toggle.
If the Toggle WiFi script is launched for the first time from the terminal the LED does light up.
This is the case in SuperZaxxon 1.53 with all current upgrades applied, and reportedly since the introduction of SuperZaxxon.
checking /sys/class/leds/pandora::wifi/trigger while the WiFi is enabled but the LED off shows that the trigger has been successfully set to phy0radio
Also noted while investigating this:
If Wifi is enabled for the first time from the terminal the following errors are generated by /etc/init.d/wl1251-init
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
Usage: insmod filename [args]
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
find: /lib/modules/3.2.30/updates: No such file or directory
Usage: insmod filename [args]
The commands that generate these errors are only executed if the mac80211 module is not already loaded - and that module is not unloaded when wifi is disabled. This seems to be unrelated to the issue being reported, however I can't see any cause for the issue at all, so I figured it was worth including it in the report anyway. |
|
314 | Core | Bug Report | Low | Pandora-Button doesn't open XFCE menu | Closed | |
Task Description
If you enable the "disapear automaticaly" feature in the XFCE panel, the Pandora button doesn't open the main menu anymore and you need to open it manually with the cursor. |
|
323 | Core | Bug Report | Medium | OS Selector bug | Closed | |
Task Description
When selecting no OS in the OS Selector you're returned to the login screen where you have to reauthenicate. (Pressing Enter without selecting an OS does this)
I happen to do this a lot and it drives me mad :P |
|
332 | Core | Bug Report | Medium | op_lidsettings.sh and op_power.sh scripts fail for some ... | Closed | |
Task Description
/usr/pandora/scripts/op_lidsettings.sh and /usr/pandora/scripts/op_power.sh fail for some usernames due to poor shell scripting
these scripts find their config files by grepping /etc/passwd for the uer currently running xfce4-session, but the loose regexp matches too much. this shell fragment from op_lidsettings.sh:
grep /etc/passwd -e $(ps u -C xfce4-session | tail -n1 | awk '{print $1}')| cut -f 6 -d ":"
when a use called "me" is logged in, returns
/home/root
/usr/games
/var/run/dbus
/home/me
rather than just "/home/me"
all instances of that construct (reading and writing settings, in both op_lidsettings.sh and op_power.sh) should be changed to
grep /etc/passwd -e ^$(ps u -C xfce4-session | tail -n1 | awk '{print $1}'): | cut -f 6 -d ":"
to correctly match only the complete username field in /etc/passwd |
|
334 | Core | Bug Report | Low | op_bright_down.sh: error when decreasing brightness | Closed | |
Task Description
The script does not handle brightness "0".
If you try to decrease brightness if it's already at 0, it produces errors:
~ # /usr/pandora/scripts/op_bright_down.sh
/usr/pandora/scripts/op_bright_down.sh: line 18: [: : integer expression expected
/usr/pandora/scripts/op_bright_down.sh: line 22: echo: write error: Invalid argument
Not sure how to attach a patch here, but you can get the change with:
git pull git://git.assembla.com/openpandora-oe.git bug-333
I also changed the script to use /bin/sh since it's a valid posix script. |
|
337 | Core | Bug Report | Low | SPAM | Closed | |
Task Description
SPAM |
|
227 | Core | Bug Report | Low | Delete button won't delete, and function lock doesn't w... | Unconfirmed | |
Task Description
If you hit the function button, then hit it again to lock the function keys, it doesn't lock the function key.
The delete key, hold shift and hit the back space button, it won't delete, meaning it won't remove the character to the right of the cursor. I saw this on the forum, and confirmed it on my pandora also. |
|
250 | Application | Feature Request | Medium | File Browser Thunar - Trashing file crosses filesystem ... | Researching | |
Task Description
Trashing a file/folder seems to MOVE it to a certain trash directory on the MAIN VOLUME, rather then the ORIGINATING VOLUME, hence this can result in a COPY RATHER THAN A MOVE operation, if the trashed file originates from a filesystem other than the main filesystem!
This is very inefficient and faulty as it is:
a) Very time consuming
b) And in case of large files this operation can even fail due to not enough free space on the main volume. |
|
216 | Application | To Do (Reminder) | Low | ToDo - SD manager tool (backup homedir/restore, prepare... | New | |
Task Description
Should make up a simple zenity script tool ..
- backup -> pick SD -> backs up current user's homedor to SD. (tar.gz format so permissions can be kept; not cpio/etc, too annoying for user.) -> keep rolling, or just one copy?
- restore -> pick SD -> pick user -> confirm -> wipe home and restore with version from tarball? (or just unpack in-place, so existing new files are kept)
-> prepare SD -> pick SD -> mkdir /pandora/menu and /pandora/desktop |
|
328 | Core | Bug Report | Low | XFCE desktop icons not displayed when logging on too qu... | Requires testing | |
Task Description
It looks like XFCE cannot find the icons for links/launchers on the desktop, when the user logs on too quickly. This happens either when the session chooser at start-up is disabled, or when the session is being chosen quickly after the session chooser is being displayed (e.g. by pressing enter as soon as the chooser window pops up). The icons are probably not generated yet at that time point.
A simple workaround is adding the command "xfdesktop --reload" to autostart. Couls this be included in the next SuperZaxxon release or a hotfix? |
|
291 | Core | Bug Report | Medium | root-owned pndrun_...out file makes PND refuse starting | Assigned | |
Task Description
If a PND has been run as root before (using pnd_run.sh from a root shell) and afterwards it is invoked the normal way, the PND doesn't start, because the .out file cannt be overwritten:
/usr/pandora/scripts/pnd_run.sh: line 26: /tmp/pndrun_firefox.out: Permission denied
Desired solution:
.out file is silently overwitten.
Maybe, if that's not possible, create another .out file with a different name (added counter, for example).
Seen in SuperZaxxon relese 1.5, not in Beta3 as this task is flagged, but there is no choice besides Beta3. |
|
299 | Core | Bug Report | Low | run_pnd.sh does not follow PXML.xml or "-d"-Parameter | Assigned | |
Task Description
I call pnd_run.sh with a pnd. The application directory will invariably be /media/SD/pandora/appdata/, no matter if the PXML.xml specifies a different appdata path. Also, the parameter -d for run_pnd.sh is not followed, either.
I tried with vlc.pnd from the app store and with Dosbox74.pnd.
UPDATE: Original submission contained a wrong filename reference. Corrected that typo to the filename intended by the submitter. Admin: porg. |
|
12 | Core | To Do (Reminder) | Low | file association for .pnd | New | |
Task Description
Build the xml file and defaults.list so that pnd_run is file-assocated to .pnd |
|
65 | Core | Feature Request | Very Low | .desktop files, be nice if they included the non-englis... | New | |
Task Description
.desktop files only include the English stuff right now (using the .desktop default tags.)
Be nice if in addition to 'title', we also include 'title[de]' type extras, whatever is in the PXML.xml
pnd_pxml_t includes all the goods, but pnd_disco_t has only the summarized english stuff. |
|
94 | Core | Bug Report | Low | Backlight control by lid sensor not detected after boot | New | |
Task Description
If you boot the system with the lid closed, the backlight will still be on when you get to the desktop. You have to lift the lid for an instant and then close again to shut it off. Perhaps this is because of the lack of trigger for an interrupt since the sensor is already activated. Can there be one extra check of the lid sensor after boot to cover this static position? |
|
105 | Application | Feature Request | Very Low | Nubs feature request | New | |
Task Description
The 'Nubs' application needs a setting for deadzone. Using the nubs in First person shooters the nubs trigger in directions when not even touched. An adjustment for deadzone would eliminate accidental movement caused by vibration.
Also, application profiles for the nubs would be very useful. Different apps use the nubs in different ways and it would be great to not have to go and change settings before launching each application. |
|
121 | Base OS | Bug Report | Medium | PyGame Hardware support | New | |
Task Description
PyGame is damn slow (games with scrolling are not at all playable).
Would be nice if Hardware surface could be used :) |
|
123 | Base OS | Feature Request | Low | Suggestions for the Pandora-Button | New | |
Task Description
My suggestion instead of a full menu, would be to have a tiny overlay over the current running application which allows you to:
- relogin (to close all running applications)
- quit (stop the active application)
- shows the last notifications / toaster messages which you missed while being in a fullscreen app.
- possibly even something like plugin support or icons to check out the wifi-strength etc. from fullscreen apps.
Implementation wise this could possibly be done using
- a topmost window and the same content rendered in screenspace in a GLES hook (which should draw over most applications)
or
- one of the DSS2 overlays maybe
It's definitely something to consider as it was requested on the forums a few times (~"xbox like menu in games"). |
|
138 | Core | Bug Report | Low | 'del' key (shift+backspace) not working | New | |
Task Description
The title says everything: The 'del' key does not work. In theory you should have a del "event" when hitting shift+backspace. This is not the case in all progs I tested so far (terminal and default text editor with gui). |
|
252 | Core | Feature Request | Low | Power management: If power cable is plugged ignore "Shu... | New | |
Task Description
If the power cable is plugged and the user chooses "Shutdown Pandora" from a menu, there should be a warning that this is without purpose, as the device will automatically restart.
The resulting user choices should be "Cancel shutdown" and "Shutdown nevertheless". |
|
270 | Core | Bug Report | Very Low | Power-slider & lid-close events: XFCE observes user set... | New | |
Task Description
STATUS QUO:
If you are in XFCE and hold the power slider for 3 seconds, you thereby trigger the shutdown command.
For 3 more seconds a dialogue box gives you the chance to abort the shutdown ("Shutting down in 3…2…").
Now in MiniMenu no direct shutdown key is available. You first have to quit the running app (via PANDORA key), then call up the menu (via SELECT key), and then navigate to "Shutdown" and confirm it (by B or ENTER).
INQUIRED BEHAVIOR:
1) Thanks to the very recent MiniMenu speedups, these 4 consecutive user interaction steps can now at least be be executed a lot faster.
Nevertheless, offering a 1-button-interaction (via power slider) too, would be nice. Could you please make that available to MiniMenu?
And in general: Make this power-slide-event available to any possible GUI, so that not each GUI has to implement this by itself, but rather the OS catches this event and handles it uniformly, except if a certain GUI WANTS to establish an exception to the rule.
2) Also the "Lid-Close-Settings" seem to be ignored by MiniMenu. MiniMenu seems to have the action "Turn off screen" hardcoded to that event. Please make MiniMenu observe the user settings from "Lid-Close-Settings".
RELATED SOURCE CODE FILES (to my knowledge):
op_lid.sh
op_power.sh
op_bright_up.sh
op_bright_down.sh |
|
104 | Base OS | Bug Report | Low | AAC decoder libfaad doesn't appear to be compiled as fi... | Unconfirmed | |
Task Description
FAAD2 appears to not be compiled with fixed point decoding. My version of libfaad compiled with fixed point used 2-3x less cpu than the provided one. It's not enough to provide the switch to the configure script. the file libfaad/common.h has to be edited and a define uncommented. Line 68 in the v2.7 source.
/* COMPILE TIME DEFINITIONS */
/* use double precision */
/* #define USE_DOUBLE_PRECISION */
/* use fixed point reals */
//#define FIXED_POINT |
|
106 | Application | Feature Request | Very Low | AppData corruption | Unconfirmed | |
Task Description
The appdata folder was corrupted on my SD card from an unclean eject this made the folder read only until i ran a repaired it. MiniMenu still displayed all my PND files.
When clicking to launch the app would try to load crash and then return to MiniMenu without any visible error. This was pretty confusing and i thought it might be a good fix for a troubleshooting guide. |
