|
8 | Core | Bug Report | High | WiFi doesn't work | Closed | |
Task Description
Error inserting /lib/modules/2.6.27-omap1/kernel/drivers/net/wireless/wl12xx/wl1251_sdio.ko: -1 Unknown symbol in module |
|
5 | Core | Bug Report | High | Touchscreen Calibration stops the First-Boot-Wizard | Closed | |
Task Description
When selecting the touchscreen calibration within the first-boot-wizard, the script stops after the calibration and the Pandora continues to boot. |
|
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. |
|
2 | Core | Bug Report | High | pndnotifyd | Closed | |
Task Description
pndnotifyd needs to be restarted before it works (tested in image 2009-12-21)
This can manually be fixed by installing two packages:
http://www.angstrom-distribution.org/unstable/feed/armv7a/base/sessreg_1.0.4-r0.2_armv7a.ipk
http://djwillis.openpandora.org/pandora/packages/pandora-libpnd_1.0-r12.5_armv7a.ipk
And adding to lines to slim.conf:
sessionstart_cmd /usr/bin/sessreg -a -l $DISPLAY %user
sessionstop_cmd /usr/bin/sessreg -d -l $DISPLAY %user |
|
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. |
|
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. |
|
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. |
|
108 | Base OS | Feature Request | Critical | TUN/TAN-Driver | Closed | |
Task Description
There is no TUN/TAN Driver installed. This is recommanded for some encrypted wireless lan connections, especially for eduroam, a world wide access point for the education community. Also, a tun-driver is also recommended for vpnc. |
|
82 | Base OS | Bug Report | Critical | Network Manager - Wifi Can't Reconnect | Closed | |
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. |
|
58 | Core | Bug Report | Critical | Pandora has not been shipped yet. | Closed | |
Task Description
Pandora has not been shipped yet. |
|
55 | Core | Bug Report | Critical | .xinitrc problems (image from Feb 22nd) | Closed | |
Task Description
Loading a GUI from slim fails, as .xinitrc is broken.
Seems to have been edited using a windows editor? From line 50 on, there are newline characters that shouldn't be there.
Removing them makes XFCE4 loading fine. |