|
193 | Core | Bug Report | Low | Cannot reach button well in ubuntu x64 | Closed | |
Task Description
Window can also not be resized |
|
194 | Core | Bug Report | Low | python ctypes broken (and fix) | Closed | |
Task Description
run python and type import ctypes
cant find _ctypes it says....
for further details and a fix see
http://www.gp32x.com/board/index.php?/topic/57102-python-ctypes-stopped-working/ |
|
197 | Core | Bug Report | High | [PATCH] Fix opp if booting with wrong settings in hw | Closed | |
Task Description
Hi,
This should help with cases like this
http://www.gp32x.com/board/index.php?/topic/57303-overclocking-broke-my-pandora/
Patch attached. |
|
198 | Application | Bug Report | Low | Mousepad: 'Find' works only once | Closed | |
Task Description
Mousepad 0.2.16
Find (Ctrl+F) works once, the next time it is used the button 'Find' is and stays grayed out. |
|
200 | Core | Bug Report | Low | After opening the lid, the backlight is not reset to th ... | Closed | |
Task Description
Using the hotkeys to set the backlite, after closing and then opening the lid, the backlight is not reset to the same level it was before closing it.
It seems to set it to a fixed value. |
|
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 |
|
202 | Core | Bug Report | Low | Set Date and Time won't let you cancel or close | Closed | |
Task Description
The Date and Time application in MiniMenu by won't let you use the cross or the cancel button to close the application without changing anything.
If you use one of those buttons then a new window opens that says: "Error: Please select a timezone" and equally so for the date and time. |
|
203 | Core | Bug Report | Low | Video-out setting window does not exit on OK | Closed | |
Task Description
The "video-out" window opens again if you choose OK button. |
|
205 | Core | Bug Report | Medium | libpnd functions and dynamic libs missing | Closed | |
Task Description
tried to compile a simple test application that uses functions from libpnd, namely
pnd_evdev_open(pnd_evdev_e)
pnd_evdev_dpad_state(pnd_evdev_e)
pnd_evdev_closeall()
but all 3 seem to be missing.
yes, i'm linking to libpnd ... but no chance to get it running.
i'm using ivanovic's latest toolchain, which in turn installs "pandora-libpnd-dev_1.0-r40.5_armv7a.ipk" ...
also, there's only the static library available inside, no dynamic libraries. |
|
207 | Core | Bug Report | Medium | Touchscreen calibration / use of nubs conflict | Closed | |
Task Description
When using certain apps like Basilisk 2 / Dosbox / Enigma the analogue stick and touchscreen are both available to use as a mouse cursor.
All is well with the touch until you decide to touch the analogue stick when then affects touchscreen alignment by about 2 - 3 CM.
This has been going on since first release. |
|
208 | Core | Bug Report | Critical | HOTFIX 4 and 5 Slow WIFI | Closed | |
Task Description
I'm getting 5kb/s with bursts up to 10kb/s if I am lucky.
I have attempted every channel on my router.
Tried every encryption even no encryption.
Tested with the router's wifi speed: 300Mbps 154Mbps and 45Mbps
I'm running Hotfix 5 RC2.
Wifi works fine with my android smartphone, and other wireless devices such as a laptop. |
|
211 | Core | Bug Report | Low | x11vnc server (in xfce menu - > network) does not work! | Closed | |
Task Description
x11vnc launcher in xfce menu -> network does not work.
can this be fixed please. |
|
213 | Application | Bug Report | Low | Gigolo does not perform it's task | Closed | |
Task Description
In it's current state, Gigolo is flat out broken and (almost) useless. It pretends to to it's job, but can't because it's missing critical pieces of anatomy.
It can mount local filesystems correctly, but then so can thunar, so this is a redundant and useless function. The main reason to use Gigolo is to mount remote filesystems easily, and without having to use the terminal, and to save passwords in your keychain.
The solution to the problem is to perform the following tasks:
sudo opkg install gvfsd-sftp sshfs-fuse
sudo mousepad /etc/modutils/fuse
type "fuse" save and quit
sudo update-modules |
|
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. |
|
215 | Core | Bug Report | Medium | Kingston 32GB Class6G2 SDHC card not working in pandora | Closed | |
Task Description
I have noticed errors like this, but not every time
[ 1455.612792] mmc2: card claims to support voltages below the defined range. These will be ignored.
[ 1455.621795] mmc2: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
[ 1455.665985] mmc2: new SDIO card at address 0001
This is me plugging in my 32GB SD6G2 Kingston SDHC card.
at [ 1114.484252] is when the file copy started
Errors continue from there until it bombs and remounts the filesystem readonly.
I have tried this with ext3 vfat in various configurations and all fail the same I/O errors
Let me know if I can do anything to help
-------------------------------------
[ 989.496459] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 989.504638] mmc1: new high speed SDHC card at address 0003
[ 989.510620] mmcblk1: mmc1:0003 SD32G 31514112KiB
[ 989.515625] mmcblk1: p1 p2 p3 p4 < p5 p6 >
[ 989.940490] FAT: invalid media value (0x00)
[ 989.944702] VFS: Can't find a valid FAT filesystem on dev mmcblk1.
[ 990.083190] FAT: invalid media value (0x00)
[ 990.087402] VFS: Can't find a valid FAT filesystem on dev mmcblk1.
[ 991.907562] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 991.922943] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.002563] mmci-omap mmci-omap.0: MMC IRQ 0x208002 : TC ERRI DCRC
[ 992.003143] mmcblk0: retrying using single block read
[ 992.028411] kjournald starting. Commit interval 5 seconds
[ 992.048553] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.092346] kjournald starting. Commit interval 5 seconds
[ 992.237091] kjournald starting. Commit interval 5 seconds
[ 992.259185] EXT3-fs: Unrecognized mount option "umask=0" or missing value
[ 992.361999] FAT: bogus number of reserved sectors
[ 992.366760] VFS: Can't find a valid FAT filesystem on dev mmcblk1p4.
[ 992.400909] kjournald starting. Commit interval 5 seconds
[ 992.612945] EXT3 FS on mmcblk1p2, internal journal
[ 992.617797] EXT3-fs: mounted filesystem with ordered data mode.
[ 992.787475] EXT3 FS on mmcblk1p3, internal journal
[ 992.792449] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.038940] EXT3 FS on mmcblk1p1, internal journal
[ 993.043884] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.205749] EXT3 FS on mmcblk1p5, internal journal
[ 993.210632] EXT3-fs: mounted filesystem with ordered data mode.
[ 993.510253] FAT: bogus number of reserved sectors
[ 993.515045] VFS: Can't find a valid FAT filesystem on dev mmcblk1p4.
[ 1114.484252] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1114.484802] mmcblk0: retrying using single block read
[ 1115.763946] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1115.765594] mmcblk0: retrying using single block read
[ 1115.984649] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1115.984985] mmcblk0: retrying using single block read
[ 1116.039489] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.039916] mmcblk0: retrying using single block read
[ 1116.094329] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.094757] mmcblk0: retrying using single block read
[ 1116.150146] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.152343] mmcblk0: retrying using single block read
[ 1116.212127] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.212615] mmcblk0: retrying using single block read
[ 1116.267791] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.268280] mmcblk0: retrying using single block read
[ 1116.335723] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.337738] mmcblk0: retrying using single block read
[ 1116.410766] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.413360] mmcblk0: retrying using single block read
[ 1116.488250] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.490234] mmcblk0: retrying using single block read
[ 1116.581390] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.581939] mmcblk0: retrying using single block read
[ 1116.645721] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.646331] mmcblk0: retrying using single block read
[ 1116.933288] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1116.933715] mmcblk0: retrying using single block read
[ 1117.000518] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.002899] mmcblk0: retrying using single block read
[ 1117.068328] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.070526] mmcblk0: retrying using single block read
[ 1117.128326] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.128753] mmcblk0: retrying using single block read
[ 1117.194183] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.194488] mmcblk0: retrying using single block read
[ 1117.261566] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.262084] mmcblk0: retrying using single block read
[ 1117.328674] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.329956] mmcblk0: retrying using single block read
[ 1117.388061] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.390380] mmcblk0: retrying using single block read
[ 1117.451629] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.452087] mmcblk0: retrying using single block read
[ 1117.510467] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.512725] mmcblk0: retrying using single block read
[ 1117.714874] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.715301] mmcblk0: retrying using single block read
[ 1117.776550] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.778930] mmcblk0: retrying using single block read
[ 1117.841247] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1117.841674] mmcblk0: retrying using single block read
[ 1122.718658] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1122.719055] mmcblk0: retrying using single block read
[ 1123.265136] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1123.265441] mmcblk0: retrying using single block read
[ 1123.442230] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1123.442413] mmcblk0: retrying using single block read
[ 1126.759338] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1126.759399] mmcblk1: error -110 transferring data, sector 32669824, nr 8, card status 0xc00
[ 1126.807830] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1126.807891] end_request: I/O error, dev mmcblk1, sector 32669824
[ 1126.813934] Buffer I/O error on device mmcblk1p1, logical block 4083726
[ 1126.820556] lost page write due to I/O error on mmcblk1p1
[ 1127.630950] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1127.631011] mmcblk1: error -110 transferring data, sector 32686232, nr 8, card status 0xc00
[ 1127.715179] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1127.715240] end_request: I/O error, dev mmcblk1, sector 32686232
[ 1127.721282] Buffer I/O error on device mmcblk1p1, logical block 4085777
[ 1127.727935] lost page write due to I/O error on mmcblk1p1
[ 1133.399963] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.400024] Spurious DMA IRQ
[ 1133.403411] mmcblk0: retrying using single block read
[ 1133.504821] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.504943] mmcblk0: retrying using single block read
[ 1133.599304] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.599548] mmcblk0: retrying using single block read
[ 1133.767486] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1133.767578] mmcblk0: retrying using single block read
[ 1134.222564] mmci-omap mmci-omap.0: MMC IRQ 0x208000 : ERRI DCRC
[ 1137.074981] mmcblk0: retrying using single block read
[ 1137.465576] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1137.465667] mmcblk1: error -110 transferring data, sector 17316672, nr 72, card status 0xc00
[ 1137.509582] mmci-omap mmci-omap.1: MMC IRQ 0x108000 : ERRI DTO
[ 1137.509643] end_request: I/O error, dev mmcblk1, sector 17316672
[ 1137.515686] end_request: I/O error, dev mmcblk1, sector 17316680
[ 1137.521728] end_request: I/O error, dev mmcblk1, sector 17316688
[ 1137.527770] end_request: I/O error, dev mmcblk1, sector 17316696
[ 1137.533813] end_request: I/O error, dev mmcblk1, sector 17316704
[ 1137.539855] end_request: I/O error, dev mmcblk1, sector 17316712
[ 1137.545867] end_request: I/O error, dev mmcblk1, sector 17316720
[ 1137.551910] end_request: I/O error, dev mmcblk1, sector 17316728
[ 1137.557952] end_request: I/O error, dev mmcblk1, sector 17316736
[ 1137.766906] Aborting journal on device mmcblk1p1.
[ 1137.997436] journal commit I/O error
[ 1138.001037] EXT3-fs error (device mmcblk1p1) in ext3_create: IO failure
[ 1138.225067] ext3_abort called.
[ 1138.228149] EXT3-fs error (device mmcblk1p1): ext3_journal_start_sb: Detected aborted journal
[ 1138.236785] Remounting filesystem read-only |
|
219 | Core | Bug Report | Medium | wrong owner of /home/user/Desktop | Closed | |
Task Description
I just reflashed with HF5, and it turns out that I cannot make shortcuts on the desktop. It is very simple to fix:
sudo chown janek.janek Desktop/
I remember that this bug was also present in HF4, I fixed it so quickly that I didn't even remember to report it. |
|
221 | Core | Bug Report | Medium | 32MB worth of qt4 examples in /usr/bin/qt4 ? | Closed | |
Task Description
Hi, after upgrading to HF5, I accidentally discovered that there are 32MB of qt4 examples & demos in directory /usr/bin/qt4, those examples do work. For instance the /usr/bin/qt4/examples/webkit/fancybrowser/fancybrowser is a working WWW browser.
It is, without any dispute a very useful qt4 development help, but are you sure that you want to include all that in NAND ? |
|
224 | Core | Bug Report | Low | Unresponsive start menu since HF5 | Closed | |
Task Description
Since hotfix 5, the start menu often pauses for a few seconds, not letting me select anything or move the mouse.
Other people have reported the issue as well:
http://boards.openpandora.org/index.php?/topic/2295-is-the-xfce-menu-trolling-anyone-else/page__gopid__42559#entry42559 |
|
228 | Core | Bug Report | Low | libpnd must be linked to libstdc++ | Closed | |
Task Description
Run "ldd -r /usr/lib/libpnd.so.1", and a number of undefined symbols are listed. These become a problem when attempting to load libpnd in Python. I imagine it could be a problem when attempting to load libpnd in other languages as well.
This can be worked around with "LD_PRELOAD=/usr/lib/libstdc++.so" before running a Python program that loads libpnd.
But it can be worked around more easily by linking libstdc++ during compile. Adding "-lstdc++" to line 41 of libpnd's Makefile does it. I'd add a patch, but the attach file button isn't working for me. Still, a simple fix, right? |
|
230 | Core | Bug Report | Low | Second SD slot not working in future kernel version 2.6 ... | Closed | |
Task Description
Sorry, not sure where to log this bug. I have confirmed with aTc on freenode, that SD slot #2 does not work on kernel version 2.6.37 from the openpandora git.
Happy to test anything and reports results. |
|
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. |
|
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 |
|
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. |
|
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? |
|
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. |
|
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. |
|
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. |
|
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. |
