Evince 2.30 often crashes with the following error message:
(evince:2834): EvinceDocument-CRITICAL **: ev_image_save_tmp: assertion `GDK_IS_PIXBUF (pixbuf)' failed
Segmentation fault
How to reproduce: open Evince, select a PDF file, go into fullscreen mode, then click into the body of the document.
Cheers, Magic Sam
]]>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.
]]>
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
]]>To reproduce:
In addition to causing more work to X, it also floods the active application with key presses, resulting in increased CPU usage. In my test, switching to HOLD while Firefox is in the foreground causes it to use 6% CPU and X an additional 2.5%.
In addition, the key-press events continue even after the switch is taken off HOLD until another key is pressed.
A possible solution to this is to blacklist the power-button event device, to prevent evdev from listening to it (the key is handled by pndevmapperd).
]]>This could be fixed with an update of NetworkManager.
]]>How to reproduce: "Screen blanking" must be enabled! Close the lid, wait more than 10 minutes, tap either shoulder button. This behaviour happens whether on charge or battery, at the desktop or running an application, provided that the "screen blanking" option is enabled.
Desired outcome: When the Pandora comes out of "screen blanking", it should restore the brightness to the same value that it was before blanking.
]]>
A simple workaround is adding the command "xfdesktop --reload" to autostart. Couls this be included in the next SuperZaxxon release or a hotfix?
]]>