|
109 | Core | Bug Report | Medium | Wifi looses connection after 20-30 minutes | Closed | |
Task Description
While logged into XFCE and browsing for an extended period the wireless will loose its connection. It will not reconnect until the Wifi is toggled off and back on again using the ToggleWifi application.
I have not tested this on an unsecured network. My wireless is WPA2 encrypted. |
|
111 | Core | Feature Request | Medium | Minimal Boot to X_Term / Pico | Closed | |
Task Description
Can we add an option to the boot menu for a minimal boot to X-term, and include Pico in the base OS?
This would allow us to fix problems we've caused by messing around with starup scripts etc.. |
|
112 | Core | Bug Report | Medium | .pnd files with spaces in filename won't work | Closed | |
Task Description
pnd_run.sh barfs when given a file with space in it's name.
Also pnd_run bin doesnt enclose the .pnd name, it should.
/usr/pandora/scripts/pnd_run.sh -p "PicoDrive_180beta2 .pnd" -e PicoDrive.run
pnd set to `PicoDrive_180beta2 .pnd'
exec set to `PicoDrive.run'
/usr/pandora/scripts/pnd_run.sh: line 50: [: PicoDrive_180beta2: unary operator expected
when run from menu:
in fork!
df: /media/mmcblk1p1/pandora/desktop//PicoDrive_180beta2: can't find mount point
mountpoint:
/usr/pandora/scripts/pnd_run.sh: line 120: [: !: integer expression expected
not mounted on loop yet, doing so
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
error determining fs, output was cannot |
|
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. |
|
120 | Base OS | Bug Report | Medium | Python is missing some modules | Closed | |
Task Description
It seems like Python is missing some modules (like cgi) which should be included in the base installation. |
|
122 | Base OS | Feature Request | Medium | SDL 1.2 optimizations | Closed | |
Task Description
At the moment, SDL is a bit slow and has vsync problems (tearing, etc.).
It could need optimizations to use the hardware. |
|
128 | Core | Bug Report | Medium | pndnotifyd Segfault | Closed | |
Task Description
pndnotifyd Segfault when the PXML.xml attached with th pnd contain non-ascii characters (for translation) |
|
129 | Base OS | Bug Report | Medium | [PATCH] bluetooth script fails to store/restore bluetoo ... | Closed | |
Task Description
Patch to op_bluetooth.sh attached. |
|
131 | Core | Bug Report | Medium | bluetooth drivers read timeout too trigger-happy/logic ... | Closed | |
Task Description
Shamelessly plugged from the forums, to get proper bug tracking and notifications on this. My post:
@notaz:
+ /* there hould be no rx in progress at this point */
+ if (info->rx_skb != NULL) {
+ dev_err(info->dev, "Receive timed out, %i done, %li left, "
+ "LSR=%02x, IER=%02x\n", info->rx_skb->len + 1,
+ info->rx_count, hci_h4p_inb(info, UART_LSR),
+ hci_h4p_inb(info, UART_IER));
+ info->rx_timed_out = 1;
+ }
Could you share your rationale for that comment in drivers/bluetooth/hci_h4p/core.c? (Oh and there's a typo, too :P )
EDIT: Asking this because commenting that block out changed status of bluetooth (for me) from unusable (can receive ~20-500kB of data before ppp connection halting) to fully working - used to have big problems playing 32kbps AAC stream (max 2 min), now already 4 mins of 96kbps, but i still think we need some receive timeout mechanism, but this one (as it currently stands) doesnt work.
Notaz's reply:
I don't really remember, it was more than 1.5 years ago. That driver is a hack, will need to review it, does it work stable with that code removed?
My reply:
For the non-IRC people:
urjaman on IRC said:
(22:47:45) urjaman: notaz: about stability: i'm on irc atm with that driver, its been playing internet radio for a few hours without problems now, but i don know for sure.
(22:48:00) urjaman: *dont know
(22:50:11) urjaman: my logic: if the serial port _never_ misses a byte it should be ok - IMO scary without some receive timeout, but works for me |
|
132 | Base OS | Bug Report | Medium | Deleting big files doesn't work | Closed | |
Task Description
When deleting a file on the SD card, the Pandora OS moves it into the thrash folder in the internal memory. That itself isn't very nice (shouldn't there be a trash folder on the SD card as well, to reduce unnecessary copying?), but if the file is too big for the internal memory, a error message appears, and the file cannot be deleted on the Pandora directly. |
|
142 | Core | Feature Request | Medium | Visible Sleep Indicator | Closed | |
Task Description
Could we please get a visual indication that the Pandora is in sleep/low-power mode? I would suggest one of the case LEDs either turn on or blink to indicate the sleep mode. |
|
151 | Base OS | Feature Request | Medium | [PATCH] Turn Off LCD when closing the lid | Closed | |
Task Description
Just added a few lines to op_lid.sh, will power off the LCD when you close the LID. Patch attached. |
|
162 | Core | Bug Report | Medium | XFCE Setting date | Closed | |
Task Description
The tool to setup the date/time in XFCE doesn't work properly :
- Menu -> Settings -> Date and Time
- The tool show up
- Select the time zone
Now an error window spam every seconds... |
|
170 | Core | Bug Report | Medium | Executable directories broken | Closed | |
Task Description
Directory type packages fail to run. i.e. dropping a directory containing PXML.xml and a bunch of files onto the SD card rather than a .pnd package.
The application is detected and menu entries created correctly, however pnd_run.sh fails to bind mount the directory due to bogus double quoting. Looks like a failed attempt to handle spaces in the path. Patch below removes these incorrect quotes.
--- pnd_run.sh
+++ pnd_run.sh.old
@@ -161,2 +161,2 @@
elif [ $DFS = directory ]; then
- mntline="sudo mount --bind -o ro ${PND} "
+ mntline="sudo mount --bind -o ro \"${PND}\" " |
|
171 | Core | Feature Request | Medium | Update clock from hardware when restoring from low powe ... | Closed | |
Task Description
The clock occasionally does weird things during low power mode, sometimes gaining time, sometimes losing. This is most likely a result of the CPU being reduced to 14Mhz and the system clock being unable to keep up.
A convenient work around is to make a call to "/sbin/hwclock --hctosys" during wake-up to load the hardware clock back into the system clock. This may add an extra second or two to the wake-up time but will prevent confusion caused by clock being very incorrect. |
|
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 |
|
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. |
|
180 | Core | Bug Report | Medium | LCD Brightness Lower = Flashing, Dies. | Closed | |
Task Description
Just try and lower with the Fn+Br- until it starts to flashing and just dies if you go lower. It does go back if you raise it again. Feels wrong. Also no real feel in the brightness getting lower. |
|
182 | Core | Bug Report | Medium | Ctrl + F5 (Fn Lock) Fail | Closed | |
Task Description
So I've tried this a while now with no success. I'm assuming its when Fn is triggered and then pressing Ctrl or Alt it goes away. |
|
184 | Core | Feature Request | Medium | libpnd: Add a function to get all mounted PNDs | Closed | |
Task Description
Add a function to get all mounted PNDs. Because it's very annoying to check all the menu/desktop folders on all of the SD-Cards. |
|
186 | Application | Bug Report | Medium | unusable "Manage LCD Gamma" tool | Closed | |
Task Description
Pandora Menu -> Settings -> LCD-Settings -> Manage LCD Gamma
Removing all the profiles listed there will make the user unable to even create a new one. The tool becomes unusable. I hope a re-flash would fix the problem.
The last profile in the list, or the Default one, shouldn't be deletable at all. |
|
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. |
|
192 | Core | Bug Report | Medium | [U-Boot] ext2fs_devread() read error - block (boot from ... | Closed | |
Task Description
[U-Boot] ext2fs_devread() read error - block
Description:
Formatted two different Transcend 8GB SD cards as EXT2 using both GParted and also with Mkfs.ext2, extracted pandora-rootfs.tar.bz2 to the root of the SD and added 'autoboot.txt' as described here: http://openpandora.org/firmware/README.txt
This issue appears to be same as mentioned here, looks like a patch maybe required in drivers/mmc/omap3_mmc.c):
http://lists.denx.de/pipermail/u-boot/2010-June/072198.html
Output on boot :
mmc1 is available
reading autoboot.txt
** Unable to read "autoboot.txt" from mc1 0:1 **
Loading file "autoboot.txt" from mmc1 device 0:! (xxa1)
184 bytes read
** Executing plain script at 82000000
Loading file "/boot/uImage-2.6.27.46-omap1" from mmc device 0:1 (xxa1)
** ext2fs_devread() read error - block
** Unable to read "/boot/uImage-2.6.27.46-omap1" from mmc 0:1 **
## Booting kernel from Legacy Image at 8030000 ...
Image Name: Angstrom/2.6.27-pandora+r21+git4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2325740 Bytes = 2.2 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
syntax error |
|
196 | Core | Feature Request | Medium | [PATCH] Add tablet support into kernel | Closed | |
Task Description
Hi,
This should be a quite simple thing, but my first time touching
the OE repo and i cant test it, so be careful. |
|
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. |
|
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 ? |
|
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) |
|
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). |
|
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 |
|
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 |
|
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! |
|
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). |
|
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 |
|
317 | Core | Bug Report | Medium | After disabling USB-host current still flows into USB d ... | Closed | |
Task Description
On my Pandora, due to bad internal WiFi, I use an Edimax EW-7811Un USB WiFi adapter, which has a status-LED, flickering according to the network activity.
After disabling USB-host through the settings menu, the WiFi functionality is gone, but the device's LED is still on. So some current must still flow into the USB device.
The LED now has a permanent light, no flickering! This lack of "device intelligence" indicates that the device was indeed turned off, just current flowing directly to the LED circuit unaltered).
I can repeat the aforementioned steps many times, the behavior is the same.
As soon as I then first physically unplug and reinsert the device, the LED remains off eventually.
From then on, every further issuing of "Disable USB-host" through the settings menu turns the device LED completely off.
Smells like a kernel bug to me! As it requires one real un/re-plugging, from then on works ok. |
|
323 | Core | Bug Report | Medium | OS Selector bug | Closed | |
Task Description
When selecting no OS in the OS Selector you're returned to the login screen where you have to reauthenicate. (Pressing Enter without selecting an OS does this)
I happen to do this a lot and it drives me mad :P |
|
332 | Core | Bug Report | Medium | op_lidsettings.sh and op_power.sh scripts fail for some ... | Closed | |
Task Description
/usr/pandora/scripts/op_lidsettings.sh and /usr/pandora/scripts/op_power.sh fail for some usernames due to poor shell scripting
these scripts find their config files by grepping /etc/passwd for the uer currently running xfce4-session, but the loose regexp matches too much. this shell fragment from op_lidsettings.sh:
grep /etc/passwd -e $(ps u -C xfce4-session | tail -n1 | awk '{print $1}')| cut -f 6 -d ":"
when a use called "me" is logged in, returns
/home/root
/usr/games
/var/run/dbus
/home/me
rather than just "/home/me"
all instances of that construct (reading and writing settings, in both op_lidsettings.sh and op_power.sh) should be changed to
grep /etc/passwd -e ^$(ps u -C xfce4-session | tail -n1 | awk '{print $1}'): | cut -f 6 -d ":"
to correctly match only the complete username field in /etc/passwd |
|
12 | Core | To Do (Reminder) | Low | file association for .pnd | New | |
Task Description
Build the xml file and defaults.list so that pnd_run is file-assocated to .pnd |
|
94 | Core | Bug Report | Low | Backlight control by lid sensor not detected after boot | New | |
Task Description
If you boot the system with the lid closed, the backlight will still be on when you get to the desktop. You have to lift the lid for an instant and then close again to shut it off. Perhaps this is because of the lack of trigger for an interrupt since the sensor is already activated. Can there be one extra check of the lid sensor after boot to cover this static position? |
|
104 | Base OS | Bug Report | Low | AAC decoder libfaad doesn't appear to be compiled as fi... | Unconfirmed | |
Task Description
FAAD2 appears to not be compiled with fixed point decoding. My version of libfaad compiled with fixed point used 2-3x less cpu than the provided one. It's not enough to provide the switch to the configure script. the file libfaad/common.h has to be edited and a define uncommented. Line 68 in the v2.7 source.
/* COMPILE TIME DEFINITIONS */
/* use double precision */
/* #define USE_DOUBLE_PRECISION */
/* use fixed point reals */
//#define FIXED_POINT |
|
118 | Base OS | Feature Request | Low | add sdl-perl to the base OS | Unconfirmed | |
Task Description
Hi there,
Many games depend on sdl-perl. Perl and sdl are part of the base OS, but not not the connection between the two.
Cheers,
sebt3 |
|
123 | Base OS | Feature Request | Low | Suggestions for the Pandora-Button | New | |
Task Description
My suggestion instead of a full menu, would be to have a tiny overlay over the current running application which allows you to:
- relogin (to close all running applications)
- quit (stop the active application)
- shows the last notifications / toaster messages which you missed while being in a fullscreen app.
- possibly even something like plugin support or icons to check out the wifi-strength etc. from fullscreen apps.
Implementation wise this could possibly be done using
- a topmost window and the same content rendered in screenspace in a GLES hook (which should draw over most applications)
or
- one of the DSS2 overlays maybe
It's definitely something to consider as it was requested on the forums a few times (~"xbox like menu in games"). |
|
124 | Base OS | Bug Report | Low | ifup doesn't like dhclient | Unconfirmed | |
Task Description
I added:
iface usb0 inet dhcp
And ran:
ifup usb0
But dhclient simply prints usage. |
|
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. |
|
138 | Core | Bug Report | Low | 'del' key (shift+backspace) not working | New | |
Task Description
The title says everything: The 'del' key does not work. In theory you should have a del "event" when hitting shift+backspace. This is not the case in all progs I tested so far (terminal and default text editor with gui). |
|
148 | Core | Bug Report | Low | add standard library path to ldconfig.so.conf to help l... | Unconfirmed | |
Task Description
cat >/etc/ld.so.conf |
|
178 | Core | Bug Report | Low | Mount-loop when booting from SD-card | Unconfirmed | |
Task Description
When booting the pandora-OS from sd-card by using the official tar, you will end up with your sd-card being mounted twice: once as / and once as /media/. I solved this by adding "/dev/mmcblk0" to "/etc/udev/mount.blacklist". Maybe this should be added to the default tarball? I'm not sure as it might be used in other ways maybe (beside SD-card-installation)?
Background: I ran "updatedb" as root and have been notified by a message that there was a mount-loop. After adding the above modification the system still booted fine and "updatedb" ran nicely without a warning. |
