|
315 | Core | Bug Report | Medium | Pairing bluetooth SPP devices doesn't work with XFCE | Unconfirmed | |
Task Description
Hi, sadly the XFCE bluetooth manager seems to have problems with pairing simple SPP devices (an BT GPS mouse here).
1. Enable BT
2. BT Manager -> Add new device
3. Confirm Dialog and wait for scanning
4. Pick device
5. Select PIN options -> "0000" (here for me)
In next step the dialog still asks you to enter a random PIN at your BT device (which is impossible here).
Thus it seems, that the XFCE dialog makes troubles, I tried it with 2 different GPS. Pairing the GPS manually works fine:
sudo rfcomm connect rfcomm0 00:18:E4:26:5F:14 |
|
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. |
|
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. |
|
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. |
|
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 |
|
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... |
|
308 | Core | Bug Report | Low | Wireless Network being dropped asks for password | Unconfirmed | |
Task Description
When a Wireless Network that is dropped because its signal strength isn't that good gets reconnected to, I am being asked to re-input the password for that network. It would be nice if it just used the password I gave to it when it was able to connect without popping up that dialog box. |
|
307 | Core | Feature Request | Medium | Change how Automatic Shutdown works | Unconfirmed | |
Task Description
When thee Pandora is shutting down because its almost out of power, it should check to make sure that the nub inputs are set to the default mode (which is mouse movement for the left nub and mouse buttons for the right nub). If not, it should change them to be like that. |
|
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. |
|
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 |
|
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)? ...) |
|
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. |
|
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 |
|
301 | Core | Bug Report | Medium | Missing X keybinding for colon symbol | Unconfirmed | |
Task Description
As verified with xev, an attached bluetooth keyboard can not generate colon (shift semicolon). xmodmap shows that (unlike a standard Linux system) shift-semicolon is mapped to NoSymbol. While it's find that there's a special symbol to get semicolon on the built-in keyboard, the other binding really should be there in support of attached keyboards. |
|
300 | Core | Bug Report | Low | SuperZaxxon interprets on-disk FAT32 filenames differen... | Unconfirmed | |
Task Description
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. |
|
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. |
|
297 | Core | Bug Report | Low | pandora button and taskbar autohide | Unconfirmed | |
Task Description
When the taskbar is set to autohide, the Pandora button does not bring up the menu anymore. |
|
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. |
|
292 | Core | Bug Report | Low | Can't seek in ogg files using pygame / SDL | Unconfirmed | |
Task Description
Using pygame I try to play a music file starting from some position in the middle::
import pygame
pygame.init()
pygame.mixer.init()
pygame.mixer.music.load('some_file.ogg')
pygame.mixer.music.play(0,60)
This should start playing the file from the firs minute, instead on the pandora the file plays from the start.
I've tried the same code in a debian (sid) chroot (from extend utils) and it works correctly, as it does on my pc (debian wheezy).
I suspect that the issue may be present also in .next (I've done a very quick test on a friend's pandora).
Some relevant version numbers:
* libogg.so.0.6.0 (on debian libogg.so.0.8.0)
* libSDL_mixer-1.2.so.0.10.1 (on debian libSDL_mixer-1.2.so.0.12.0) |
|
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. |
|
290 | Core | Bug Report | Medium | gnome-mount not available | Unconfirmed | |
Task Description
In GTK applications, such as Truecrypt, NoteCase Pro or Mousepad, the file open / file save dialogs have shortcuts to mounted file systems on the left side.
If clicking such a shortcut entry, the corresponding file system's contents are shown in the right dialog pane.
This works for file systems, which were available at boot time.
For file systems mounted after booting, e.g. by inserting an SD card or connecting a USB drive, when clicking such an entry, an error message appears saying
"Could not mount [volumen name]
Failed to execute child process 'gnome-mount' (No such file or directory)"
This is healed by
sudo opkg install gnome-mount
(which instals gnome-mount, nautilus, gvfsd-ftp, gvfs (upgrade), and a lot of libs (upgrades)..
This has been seen in SuperZaxxon release 1.5, not in Beta3 (but Beta3 is the only choice in Flyspray's dropdown currently).
I reported that error for HF6 I think, and it seemed to be fixed in SuperZaxxon Beta5. A regression? |
|
288 | Core | Feature Request | Low | add functionality to inputrc | Unconfirmed | |
Task Description
Since the default inputrc doesn't contain any functionality (simple cli movements like ctrl-left or crtrl-right to skip words don't work) this diff may be useful to add to the cli-experience. I've also been trying to get the delete-key to work, but this is apparently already a known issue (see FS#227). I can remove this from the diff if you want. (I couldn't attach a file to the task somehow)
31,32c31,33
< # "\e[3~": delete-char
< # "\e[2~": quoted-insert
---
> #"\e[3~": delete-char
> "\e[^?": delete-char
> "\e[2~": quoted-insert
44,47c45,50
< # "\e[5C": forward-word
< # "\e[5D": backward-word
< # "\e\e[C": forward-word
< # "\e\e[D": backward-word
---
> "\e[1;5C": forward-word
> "\e[1;5D": backward-word
> "\e[5C": forward-word
> "\e[5D": backward-word
> "\e\e[C": forward-word
> "\e\e[D": backward-word |
|
279 | Core | Feature Request | Medium | pidgin requires (more) locales to work correctly | Closed | |
Task Description
Please add the following package to allow umlauts working in pidgin:
glibc-gconv-utf-16
After installing this package I no longer have a problem receiving umlauts in pidgin. Besides it might also make sense to add "glibc-gconv-cp1250" which might be required for western europe and koi8-r which seems to be missing for xchat and conversion of chars there.
At the moment the following locale related packages are installed (as of SuperZaxxon Beta3):
glibc-charmap-utf-8 - 2.9-r35.3.5
glibc-gconv - 2.9-r35.3.5
glibc-gconv-cp1252 - 2.9-r35.3.5
glibc-gconv-ibm850 - 2.9-r35.3.5
glibc-gconv-iso8859-1 - 2.9-r35.3.5
glibc-gconv-iso8859-15 - 2.9-r35.3.5
Please add:
glibc-gconv-cp1250
glibc-gconv-koi8-r
glibc-gconv-unicode
glibc-gconv-utf-16
Thanks! |
|
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. |
|
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 |
|
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 |
|
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 |
|
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 |
|
269 | Core | Bug Report | Low | Thunar Slow Exit | Unconfirmed | |
Task Description
Thunar takes a long time going back to minimenu on exit. You don't notice this when in XFCE but then you are always in the GUI not returning to it.
This started in Hotfix 6 Alpha4 I believe |
|
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. |
|
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 |
|
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. |
|
261 | Core | To Do (Reminder) | High | Overview of all current KEYBOARD INPUT related issues | Unconfirmed | |
Task Description
Built-in keyboard input is a central thing on the Pandora, as it concerns almost all user interfaced apps!
I realized that I myself and also others submitted quite many reports concerning this issue.
Hence this meta issue is intended as an overview/accumulation/aid for those devs who are willing to overwork the whole issue.
If you realize new related issues, feel free to add them here.
If this my effort is contradicting the OpenPandora workflow, then pardon me, and instruct me, how else to handle issues of that kind. Thanks!
Keyboard low level: Driver, keyboard layout, post processing (hotkeys, input support, etc)
FS#138 FS#227 FS#242 FS#259
Keyboard mid level: Application interfacing
FS#102 FS#123 FS#238
Keyboard application internal level
FS#157 (dupe: FS#249 ) FS#243 FS#256 |
|
260 | Core | Bug Report | Medium | Low Power Mode: Input (keyboard, nub) still taken. Appl... | Unconfirmed | |
Task Description
This is the related documentation:
http://pandorawiki.org/Power_modes#Low_Power
(Please update accordingly as part of the issue resolution)
FROM MY USER EXPERIENCE:
If you put the Pandora into Low Power Mode, then press some keys, and then wake the Pandora back into Normal Mode, your input (both keys and nubs, haven't tried with USB input yet) seem to have triggered something while the device was in Low Power Mode!
What does really happen in Low Power Mode concerning execution and input?
a) Input is received AND triggers as application execution continues
or
b) Kernel/driver queues the input signals into a buffer, and executes them on wake?
If supposition a) or b) is true, then this would be one more reason to properly implement: FS#259
OBSERVANCE EXAMPLE 1:
1) Start MiniMenu. Mentally note down your active tab.
2) Put Pandora to Low Power Mode.
3) Press shoulder button R once.
4) Wake Pandora to Normal Mode. You are now one tab to the right of where you left. Input must have been caught in Low Power Mode, but wether execution of it happened while Low Power Mode or later after wake in Normal power Mode is unclear.
OBSERVANCE EXAMPLE 2:
1) Start gedit (a text editor). Insert the digit "1".
2) Put Pandora to Low Power Mode.
3) Press: CTRL-N 2 CTRL-N 3 CTRL-N 4. (Without the spaces)
4) Wake Pandora to Normal Mode.
5) For a fraction of a second you see the tabs building up. Either the input was really received AND executed while Low Power Mode and what you see is just a delayed window manager refreshment, or the input was queued in Low Power Mode, and only executed on wake. |
|
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. |
|
257 | Core | Bug Report | Medium | TV Out script breaks XV/SDL Video playback | Unconfirmed | |
Task Description
This seems to be the case with Hot-fix 5 and 6 alpha 4.
I've been able to repeat this bug by re-flashing..
On a fresh re-flash.. installed community codec pack.. Videos will play fine on Panplayer, VLC and Gnome-Mplayer with default settings, which I believe is XV or SDL out in the case of VLC.
Run the TV-out script it will cause a blank black screen during playback.. Disabling TV-out, switching modes, rebooting.. battery out, nothing seems to allows it to work with XV/SDL out again.. I know If I switch to X11 it will make it "work" again, but I notice a bit of lag during playback using X11 compared to XV/SDL out. |
|
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 |
|
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). |
|
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". |
|
251 | Core | Feature Request | Low | SD Mass Storage: Possibility to host multiple volumes | Unconfirmed | |
Task Description
a) Host multiple volumes at once.
b) Select one for hosting first, later host additional ones. (I guess this scenario is more complicated) |
|
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). |
|
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. |
|
245 | Core | Feature Request | Low | BugTracker: Submitter shall be able to edit bug after p ... | Closed | |
Task Description
I accidentally posted a "feature request" as a "bug report" within the FlySpray BugTracker.
I wanted to correct my mistake.
It was not possible to edit it.
I assigned the bug to myself.
Then I could edit it.
But now I cannot un-assign it from me.
I merely wanted to suggest a feature but not take development responsibility (yet).
For original submitters, who later realize a mistake in their post, there should be a possibility to correct their mistake.
Please un-assign me from #237 #241 #243 and this one #245. Thanks. |
|
237 | Core | Bug Report | Critical | /dev/mmcblkN - N sometimes points to left, sometimes to ... | Closed | |
Task Description
SPECIFICATION:
According to http://pandorawiki.org/SD_compatibility_list
/dev/mmcblk0 is the left SD card slot (the one being closer to the headphone check)
/dev/mmcblk1 is the right SD card slot
I trusted that device path specification.
And it was correct MOST of the time.
But sadly only most of the time, NOT ALWAYS!!!
This bug is severely dangerous, as a (possibly critical) command could unexpectedly affect a device other than the one you intended it for!
BUG INCIDENT:
Sadly, I realized this bug at the worst possible moment!
I issued the command: shred -fvz /dev/mmcblk0
but it erased the card in the RIGHT slot.
I realized that because the card inserted on the left has 16GB, and the one on the right 128MB.
I checked both the card positions and my entered command, to exclude my own mistake. Sadly it was not a clumsy mistake: This severe bug really exists!
BUG REPRODUCIBILITY:
I already slightly witnessed this bug during the last days, but thought it was just a coincidence.
I.e. in GParted the larger card showed up at the wrong device path.
I did a refresh and/or ejected/re-inserted the card, and the expected device path was back again, and I did not think further about this incident.
Only today with this fatal shred incident, I eventually realized this behavior is a bug.
Luckily I had my data backed up. |
|
236 | Core | Bug Report | Low | Cannot unmount SD-Card | Unconfirmed | |
Task Description
SD-Card in Pandora can only be unmounted by guest (uid=1000) but not by jgeiss (uid=1001).
Steps To Reproduce:
Insert SD-Card (or boot with SD-Card inserted),
Login as jgeiss (uid=1001),
Try to unmount SD-Card via XFCE-Popup-Menu (right mouse click on SD-Card-Icon and select unmount). |
|
235 | Core | Bug Report | Low | File /tmp/currentuser cannot be deleted by other users | Closed | |
Task Description
The system creates a file /tmp/currentuser at the first login of a user. After logging out and in as another user the file still contains the previous user name. An cannot be deleted/overwritten by the new user.
Steps To Reproduce:
At least two users are available and have XFCE GUI enabled.
1. Login as user (eg. guest), a file /tmp/currentuser is created (containing guest)
2. Log out
3. Log in as another user (eg. jgeiss), the file still contains the old name
4. Change GUI to PMenu
5. Log out
6. Log in as first user (guest)
Now the first user (guest) has PMenu as GUI which was set by the second user (jgeiss).
Maybe the permission should be 0666 for this file? |
|
234 | Core | Feature Request | Medium | Changeable behaviour when closing the lid | Closed | |
Task Description
As it was requested on forum.gp2x.de and I think it's a good idea I've written some scripts to allow the user to change what happens when the lid is opened/closed.
There are 3 Settings:
-The old behaviour (turning off the screen)
-Go into low power mode
-Shutdown
Default behaviour is still the same: Turn the screen off. Maybe we could change this to low power mode? I don't know.
I made a lot of changes to op_lid.sh: http://pastebin.com/GT3qxWSx (diff: http://pastebin.com/Z8GwpDj8 )
I changed line 11 in op_power.sh to: if [ $powerstate -ne 0 ]; then
And wrote a gui for changing the setting using zenity: http://pastebin.com/9JvSTqfQ
(I still can't upload any files, don't know if it's the fault of my browser, that's why I use this paste service) |
|
233 | Core | Bug Report | Very Low | op_power.sh: errors | Closed | |
Task Description
op_power.sh gives some errors to me... it works anyway, but it's not nice to see them all the time.
/usr/pandora/scripts/op_power.sh: line 60: [: 5380: binary operator expected
or
/usr/pandora/scripts/op_power.sh: line 60: [: too many arguments
I guess line 60 of op_power.sh
if [ ! $wlstate ]; then
should rather be
if [ -z "$wlstate" ]; then
shouldn't it?
The same thing is in line
Then sometimes also
rm: cannot remove `/tmp/wlstate': No such file or directory
or
cat: /tmp/wlstate: No such file or directory
which could easily be fixed by adding a test -f /tmp/wlstate && or something like that before the respective command. I just added a lot of test, I'm not sure if every single one of them is really needed, but better too much than not enough, I would say. :-)
I can't attach a file (I click the button and nothing happens), so I just paste it there: http://nopaste.info/2256365eba.html
It's a bit longer because some indentations were wrong (and I corrected them) and I changed all indentations to tabs = 8 spaces instead of 2. |
|
232 | Core | Bug Report | Low | HF6 - charged completed with lid closed causing keyboar ... | Closed | |
Task Description
HF6 - It seems as when charging finishes with pandora on then charge light goes out (charge completed assuming) keyboard not functioning just gamepad. Can't use letters to cycle through in mini minimenu or use space to pull up ovr settings.
Will test further |
|
231 | Core | Bug Report | Low | Touchscreen not accurate on the edges - Calibration doe ... | Closed | |
Task Description
The touchscreen is accurate in the middle of the screen but precision is off by one or more mm near the edges of the screen. Recalibrating and rebooting does not help.
Seems like this is just a permission problem - tslib saves calibration data to /etc/pointercal which is noch writeable for the regular user.
Changing permission on that file to 666 solves this, but i guess starting the calibration tool with root permission (gksu?) would be a better solution. |
