OpenPandora Main OS

This project it to track issues relating to the current shipping OS only as found here http://goo.gl/S5JCy. Please state what Hotfix you are running with any issue report. Please ONLY use this to record issues for the main OS and its default included applications - any other application issue reports should go into the Additional Applications project. Issue reports with 'in development OS images' or feature requests for the next MAJOR version (not Hotfix release) should be placed into the OpenPandora Development OS project and reported on the mailing list http://openpandora.org/cgi-bin/mailman/listinfo/firmware-dev. Please read this page to find out how to properly report bugs: http://pandorawiki.org/Reporting_bugs

IDCategoryTask TypeSeveritySummaryStatus  ascProgress
 170 CoreBug ReportMedium Executable directories broken Closed
100%
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 CoreFeature RequestMedium Update clock from hardware when restoring from low powe ...Closed
100%
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 CoreBug ReportMedium op_power.sh: problematic display brightness restoring a ...Closed
100%
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
 219 CoreBug ReportMedium wrong owner of /home/user/Desktop Closed
100%
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.
 234 CoreFeature RequestMedium Changeable behaviour when closing the lid Closed
100%
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)
 237 CoreBug ReportCritical /dev/mmcblkN - N sometimes points to left, sometimes to ...Closed
100%
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.
 279 CoreFeature RequestMedium pidgin requires (more) locales to work correctly Closed
100%
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!
 321 CoreFeature RequestLow Support overriding all category fields with .ovr Closed
100%
Task Description

Currently only the main category and the first sub category of the main category can be overridden using a .ovr file while libpnd uses additional PXML supplied category date to construct the desktop file. This makes it difficult to work with PNDs that supply unwanted data in these additional fields.

 322 CoreBug ReportLow Allow removal of categories using the libpnd category c ...Closed
100%
Task Description

Since some PNDs provide nonstandard categories like GTK or GNOME, it is desirable to extend the libpnd category mapping with the ability to suppress individual categories completely.

 82 Base OSBug ReportCritical Network Manager - Wifi Can't Reconnect Closed
100%
Task Description When wifi drops out, or you have disconnected from it and wish to reconnect, you cant reconnect using network-manager. The connecting icon spins for a while, then it pops up the 'Password' Dialog. If you enter your password, the cycle begins again.
 201 CoreBug ReportHigh PND apps still use memory after they've quit Closed
100%
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
Showing tasks 301 - 311 of 311 Page 7 of 7<<First - 3 - 4 - 5 - 6 - 7

Available keyboard shortcuts

Tasklist

Task Details

Task Editing