|
57 | Core | Bug Report | High | New GLES driver not working yet (image from Feb 22nd) | Closed | |
Task Description
New GLES driver doesn't seem to load correctly right now.
Therefore, pmenu is also not working in this image. |
|
30 | Core | Bug Report | Medium | New issues in current image (pandora-20100102-new-kerne ... | Closed | |
Task Description
* It takes forever to startup.
It hangs while trying to initialize the new SDIO-WiFi:
[ 2363.922271] wl1251: WARNING WLAN not ready
[ 2363.927581] wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin
[ 2423.930328] wl1251: ERROR could not get firmware: -2
[ 2424.033447] wl1251: ERROR sdio write failed (-110)
[ 2425.786071] wl1251: ERROR sdio read failed (-110)
[ 2425.790893] wl1251: WARNING WLAN not ready
[ 2425.795776] wl1251_sdio mmc2:0001:1: firmware: requesting wl1251-fw.bin
* OpenPandora Start-Button is too small (has the same width as a normal icon) |
|
64 | Core | To Do (Reminder) | Low | New power-manager.xml-file (removes opening the logout ... | Closed | |
Task Description
As the powerswitch is used to go into low power mode or shutdown, it doesn't make sense showing the logout dialogue (which would appear when you come back from low-power mode).
Therefore, I disabled it with this file.
It should be placed in:
/etc/xdg/op/xfconf/xfce-perchannel-xml/
in the image. |
|
62 | Core | To Do (Reminder) | Low | New xmodmap to include into latest image | Closed | |
Task Description
This is just the latest xmodmap, based on the latest map notaz released.
Both maps (xmodmap and notaz' console map) are attached.
Path in the image:
/etc/skel/.pndXmodmap
/etc/keymap-extension-2.6.map |
|
7 | Core | Bug Report | Low | No help or tips and tricks yet | Closed | |
Task Description
Help is missing as are the tips and tricks on startup. |
|
177 | Core | Bug Report | Medium | no x or xfce after shutdown and reboot | Closed | |
Task Description
often but not always after shutting down the system (xfce logout, choose shutdown) there´s a problem when booting again.
i got the normal bootscreen but when x an xfce should start the screen remains black. i cannot say if the x or xfce didn´ start or if it is a problem with the backlight intensity.
rebooting with pandora key and power key leads to the same situation. the only thing that seems to help is to remove the battery shortly.
so, what is the difference beetween reboot after powerdown and reboot after replacing the battery? there could be the point to fix this problem. |
|
53 | Core | Bug Report | Low | Non-X Touchscreen: Inverted axis | Closed | |
Task Description
Running SDL-Apps in Non-X mode have inverted axis. |
|
16 | Core | Bug Report | Medium | normal user login fails over serial/ttys | Closed | |
Task Description
Only root can login over serial or ttys, and only if it has no password. Ssh login works fine.
After some debugging it seems to be PAM issue, possibly recipes/shadow/ misconfiguration in OE. Maybe we sould use IMAGE_LOGIN_MANAGER = "busybox" instead of IMAGE_LOGIN_MANAGER = "shadow" as we don't need super security? |
|
73 | Base OS | Feature Request | Medium | Nub: Change mouse speed, fix scrolling and add mouse bu ... | Closed | |
Task Description
Currently the nubs can be set to three different modes:
mouse, scroll and absolute
Mode 1 (mouse) works fine, but the speed is a bit slow.
Mode 2 (scroll) has inverted scrolling and it would be nice if scrolling speed would change according to how far you move it
Aditionally, I would suggest adding another mode: mbuttons (Mouse buttons).
At the moment, you can use the nubs as mouse but don't have any mouse buttons.
I think it would be very convenient if you could set the nubs as mouse buttons:
Move the nub left for left click, right for right click, up for double click and down for middle click.
That way, each user could use the left nub for mouse and the right nub for mouse buttons or vice versa. |
|
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. |
|
79 | Core | Bug Report | Low | On clean install, picking minimenu as a GUI hangs the p ... | Closed | |
Task Description
I had to reboot the pandora (look in the manual :)) to get back to the installer. I had to specify ANOTHER user, as the one I made was still there. Picking the XFCE one did work. |
|
135 | Application | Bug Report | Low | OOM Killer causes loss of items in xfce4-panel configur... | Unconfirmed | |
Task Description
When the Pandora runs out of memory and the Out-Of-Memory killer fires, the Applications/Settings/xfce4/panel/panels.xml loses the entries for the menu button and the power monitor. |
|
85 | Core | Feature Request | Low | open lid while in low power mode | Closed | |
Task Description
I'm replying in-forum:
An interesting point -- opening the lid turning the screen on, but you're still in lower power mode. The question then becomes --
Since you enabled low power mode (using the power switch), thats the logical way to un-low power mode.
Two outcomes come to mind ..
When opening the lid, one of:
i) wake up from low power mode, or
ii) Don't turn the screen on when in low power mode
(or a variation of (ii) -- flash a warning "hey, I'm in lower power, bugger off, and hit the power switch")
I can code something in; probably occured due to in my prototype, I broke the power switch, so I didn't use low power mode near the end ;) |
|
103 | Base OS | Feature Request | Low | OpenAL library in firmware? | Closed | |
Task Description
Is there any chance we can have OpenAL installed as a default library? I'm considering porting some software that requires it (and truth be told I manually compiled and installed it for my own use atm...) |
|
21 | Core | Bug Report | Low | op_bright.sh doesn't work correctly | Closed | |
Task Description
The file has to be changed to make it work.
The working script is:
#!/bin/bash
#get value range
minbright=3
maxbright=$(cat /sys/devices/platform/twl4030-pwm0-bl/backlight/twl4030-pwm0-bl/max_brightness)
curbright=$(cat /sys/devices/platform/twl4030-pwm0-bl/backlight/twl4030-pwm0-bl/brightness)
device=/sys/devices/platform/twl4030-pwm0-bl/backlight/twl4030-pwm0-bl/brightness
if [ ! $1 ]; then
newbright=$(DISPLAY=0:0 zenity --scale --text "set brightness" --min-value=$minbright --max-value=$maxbright --value=$curbright --step 1)
else
newbright=$1
fi
if [ $newbright -le $minbright ]; then newbright=$newbright; fi
echo $newbright > $device |
|
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. |
|
42 | Core | Bug Report | Low | op_defaultgui.sh: sed needs sudo access | Closed | |
Task Description
I (EvilDragon) created a small script where you can reselect the default GUI and enable / disable autologin.
Works fine so far, except for that the sed to /etc/slim.conf needs root access.
I have no idea how to make sudo in this script work without asking for a password.
If anyone could help me there, I'll be happy :) |
|
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 |
|
24 | Core | Bug Report | Low | op_menu.sh not working | Closed | |
Task Description
Reports:
xfce4-appfinder: Cannot open display: .
Fix might be (according to vimacs):
Change those two similar looking lines to:
sudo -u $xfceuser DISPLAY=:0.0 xfce4-appfinder
and:
pidlist=$(pstree -lpA | grep pnd_run.sh | sed -ne 's/.*-\(.*\)(\([0-9]\+\))/\2\n \1/p' | DISPLAY=:0.0 zenity --list --multiple --column "pid" --column "name" --title "kill" --text "which apps should be killed" | sed 's/|/\n/')
Needs to be checked. |
|
223 | Core | Bug Report | High | op_power.sh kills gles context | Unconfirmed | |
Task Description
opengles and op_power.sh don't like each other very much.
whenever returning from low power to full power mode again, opengles rendering is just dead.
the reason for this issue are following 2 lines within op_power.sh
18 echo 0 > /sys/devices/platform/omapfb/graphics/fb0/blank
...
66 echo 1 > /sys/devices/platform/omapfb/graphics/fb0/blank
if these lines are removed/commented, the gles rendering just resumes fine. |
|
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. |
|
176 | Core | Bug Report | Medium | op_power.sh: problematic display brightness restoring a ... | Closed | |
Task Description
Since hotfix4 it is possible to reduce the value for display brightness below '3'. Thus the script op_power.sh (the one used for low power mode) has to be adjusted accordingly. Currently line 25 in this script looks like this:
if [ $oldbright -ge 3 ] && [ $oldbright -le $maxbright ]; then
Please change the "-ge 3" part to "-ge 1" so that lower modes are possible, too. Otherwise the screen will be set to max brightness if you have selected a value of '1' when going into powersave mode.
Somehow it looks like what is possible to select via the hotkeys and what is possible via the "application" differs. In the script op_lcdsettings.sh in line 11 a minimum brightness of 3 seems to be defined, with the hotkeys it is even possible to go down to 0 (screen off) or values like 1 and 2. This is the relevant line:
minbright=3
Brightness restoring appears to be problematic in op_lid.sh, too. Just have a look at line 25 in this script:
if [ $oldbright -ge 3 ] && [ $oldbright -le $maxbright ]; then
Another issue is that the clockrate of 14MHz is simply too low to be reasonable. Please do adjust it to 125MHz instead, since this seems to be what TI recommends and what makes most sense since starting with hotfix4 this is where the lowest powermode (OPP0) is entered. When clocking down to 14MHz issues like the clock not working correctly come up.
Relevant lines in op_power.sh:
line 14, restoring old clockrate:
if [ $oldspeed -gt 14 ] && [ $oldspeed -le 900 ]; then
line 72, setting the clockrate for low power mode:
echo 14 > /proc/pandora/cpu_mhz_max |
|
214 | Core | Bug Report | High | op_wifi pnd not exiting cleanly, with fix (one characte ... | Closed | |
Task Description
The op_wifi pnd does not exit out cleanly once the encased script executes,
the pndrun_op_wifi.out reports
umount: /mnt/utmp/op_wifi: device is busy.
umount: /mnt/utmp/op_wifi: device is busy.
umount UNION failed, didn't clean up. Process still using this FS :
3197 ? S 0:00 /bin/sh /etc/init.d/wl1251-init start
This op_wifi.sh just calls
/usr/pandora/scripts/op_wifi.sh
for some reason, the init.d/w.... start causes it to hang, I executed all this locally, and it doesn't appear to keep running
Appending " &" to the line which calls this init script, solves the problem. |
|
115 | Base OS | Bug Report | Medium | OS is missing libvorbisidec.so | Closed | |
Task Description
Please add to next hotfix, srb2 needed this file. My temporary hack was to modify the LD_LIBRARY_PATH (didnt like having to so this, but I think the way srb2 is loading the library it wouldnt work without it) and include the library in the pnd.
Once this lib is added ill do an update on srb2 and remove the LD hack. |
|
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 |
|
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 |
|
61 | Core | Feature Request | Medium | Packages to remove and include | Closed | |
Task Description
The following packages can be removed:
embryo
gnome-games
gnome-games-blackjack
gnome-games-gnometris
gnome-games-iagno
gnome-games-gtali
gnome-games-gnobots2
xmms-mad
But we need the following ones:
xmms-plugin-input-mpg123
xmms-plugin-input-mikmod
mikmod
libxxf86dga1
epdfview
gnumeric (if possible, would be nice)
I do wonder though if we should remove all gnome-games (and ScummVM) completely.
Makes more sense if we wrap those games up as PND files.
Same goes for the community wallpapers. Should we include them? Or save that space for other things? |
|
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 |
|
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. |
|
58 | Core | Bug Report | Critical | Pandora has not been shipped yet. | Closed | |
Task Description
Pandora has not been shipped yet. |
|
102 | Base OS | Bug Report | Very Low | Pandora key does not close XFCE menu | Closed | |
Task Description
If the XFCE menu has been opened by a touchscreen command, it can also be closed by hitting the logo again. However, opening the menu this way and then hitting the Pandora key only spawns more instances of the menu. Least intrusive way to close those seems to be to select "Logout" and hit Cancel. |
|
81 | Core | Bug Report | High | pandora seems to hang during boot, turns out it didn't | Closed | |
Task Description
it seemed just now thay my pandora didnt complete its bootsequence. During booting, the screen turned black. I thought it had crashed, but I still saw lights flashing when I inserted an SDcard.
I then assumed that it WAS booting normally, but that the screen was turned down. So I pushed enter to confirm my username, as I suspected that I was at that prompt. Next I inputted my pwd, pushed enter, waited a bit, and then ised Fn+I to increase the brightness. It worked!
I think that during the bootprocess the screen should at most be set to the darkest setting, but never to off.
I think I know what happened. I told my pandora to shutdown and closed the lit before it was done. I guess that that swiittched off the screen, a setting which was then saved by the shutdown process, and restored during the bootsequence.
I would suggest fixing this in the startup process, rather than the shutdown process, because that way, no matter what ends up in the settings, a sensible valsue is set at startup. I'll see if I can reproduce this. |
|
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. |
|
44 | Core | Bug Report | Medium | Pandora-Start-Menu button too small | Closed | |
Task Description
Since about mid January, the Openpandora-Startmenu-Button doesn't resize when the "Show Title" is enabled.
Therefore, you only see parts of the "OpenPandora"-Title and no icon.
Disabling the title shows the icon. I have no idea how to resize it and why this happened (the theme hasn't been changed as far as I know) |
|
15 | Core | Bug Report | Medium | Permissions / automounted SD Card | Closed | |
Task Description
Only root has write access to automounted SD Cards. The normal user can only read. |
|
10 | Core | Bug Report | High | Permissions / sudoers isse in 12-21 image | Closed | |
Task Description
pndnotifyd will create .desktop files
Running those will fail; if you've just done a recent sudo, they'll run fine
Probably sudoers file needs fix |
|
3 | Core | Bug Report | High | Permissions for brightness and CPU Speed | Closed | |
Task Description
/sys/devices/platform/twl4030-pwm0-bl/backlight/twl4030-pwm0-bl/brightness
/proc/pandora/cpu_mhz_max
Those values cannot be changed by the user, only by root.
Should be changed. |
|
71 | Core | Bug Report | Low | Permissions of omapdss need to be fixed | Closed | |
Task Description
Only root can currently setup and change TV Out parameters :)
Should be set to make it user-changeable. |
|
98 | Application | Bug Report | Medium | Pidgin freezes (msn) | Closed | |
Task Description
Pidgin freezes when using the msn protocol. Sometimes it can last 25 minutes before doing so, sometimes it freezes instantly. Usually it's after only a few minutes. Once it freezes you are still able to close it using the built in crash manager (?!)
This happens both when running from XFCE and Minimenu. |
|
169 | Core | Bug Report | Low | pidgin freezes all the time | Closed | |
Task Description
pidgin freezes all the time |
|
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! |
|
134 | Core | Bug Report | Low | please add a working phonon backend | Closed | |
Task Description
Please see : http://www.gp32x.com/board/index.php?/topic/54831-minitube/page__view__findpost__p__883993
:) |
|
220 | Core | Feature Request | Low | Please include /usr/bin/xkbset | Closed | |
Task Description
One of the first things after installing HF5 was downloading xkbset, because it is necessary for proper L-R buttons mapping as mouse buttons. Could you please include that in the system?
I am using urjaman's executable from here:
http://www.gp32x.com/board/index.php?/topic/55124-remapping-the-mouse-buttons-etc/page__st__15__p__896576&#entry896576
Even better would be a GUI that allows mapping of L-R buttons for mouse, just like GUI for nubs :) But including xkbset will be already good. |
|
40 | Core | Bug Report | Low | pmenu doesn't show screenshots | Closed | |
Task Description
I did create some PXML files which have screenshots included.
pmenu seems to ignore them, it just shows a red X. |
|
9 | Core | Bug Report | High | pmenu doesn't work | Closed | |
Task Description
Running pmenu leads to:
ERROR: config_read_file() failed: skins/Platinum/skin.cfg (line 21 of config skin.c)
(config_skin.c:22)
ERROR: cfg_gui_read failed, exiting... ( main.c:1517) |
|
28 | Core | Bug Report | High | pmenu only shows preview pictures when selecting the PN ... | Closed | |
Task Description
When selecting a PND for the first time, it only shows a red X.
When selecting the PND for the second time, it shows the preview picture. |
|
50 | Core | To Do (Reminder) | Medium | pmenu: Add shutdown / logout | Closed | |
Task Description
There's no way yet to shutdown (poweroff) or logout from pmenu yet. |
|
46 | Core | Bug Report | Medium | pmenu: MediaPlayer only shows ~/ | Closed | |
Task Description
The mediaplayer only does show the ~/-Directory.
Ideally, it should present SD1 / SD2 / Users Home. |
|
201 | Core | Bug Report | High | PND apps still use memory after they've quit | Closed | |
Task Description
After running and quitting a PND app, not all of the used memory is being freed.
This eats more and more memory over time. Just run 5 or 6 apps and you only have half of the memory left.
Sounds like either aufs or unionfs don't free the memory after unmounting.
This has been reported with HF4 and still is the case with HF5 Beta 2
-- downgraded to 'Researching' and 'Normal' priority until confirmed and details found |
|
189 | Core | Bug Report | Medium | pnd-run.sh does not work correctly for very long <pathn ... | Closed | |
Task Description
When unmounting, the pnd-run-script greps the output of "losetup -a" at some point. But if you have a very long pathname and filename for the pnd (like "/media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd" then the endpart is cut off in the output, grep can't find the right part and the script get's confused.
Example:
mounting works:
/usr/pandora/scripts/pnd_run.sh -p /media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd -b scummvm -m
unounting does not work:
/usr/pandora/scripts/pnd_run.sh -p /media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_EN.pnd -b scummvm -u
(see /tmp/pndrun*-logs for output)
The problem is that the outut of losetup looks like this in such a case:
"/dev/loop7: [b309]:157081 (/media/trans8/gamedata/scummvm/Secret_of_Monkey_Islands_Amiga_*)"
And because the pnd-name is not fully shown, grepping the name does not work. After i renamed th pnd to a much shorter name (somi_amiga_en.pnd) it worked nicely. Still this should be fixed. |
