<?xml version="1.0" ?>
<rss version="2.0">
  <channel>
    <title>OpenPandora - Hunting Timmy, the Bug.</title>
    <lastBuildDate>Wed, 10 Dec 2014 01:48:55 +0000</lastBuildDate>
    <description>OpenPandora - Hunting Timmy, the Bug.OpenPandora Main OS: Recently opened tasks</description>
    <link>http://bugs.openpandora.org/</link>
        <item>
      <title>FS#337: SPAM</title>
      <author></author>
      <pubDate>Tue, 09 Dec 2014 23:42:25 +0000</pubDate>
      <description><![CDATA[SPAM<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=337</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=337</guid>
    </item>
        <item>
      <title>FS#336: Touch screen sensitivity too low</title>
      <author>Kazimierz Król</author>
      <pubDate>Sat, 28 Jun 2014 08:32:38 +0000</pubDate>
      <description><![CDATA[The touch screen requires to be used with the stylus or another sharp object. Even if I need to click a desktop icon, and could as well use my finger, the touch screen won&amp;#39;t react to my finger at all (even if pressed quite hard).<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=336</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=336</guid>
    </item>
        <item>
      <title>FS#335: Evince 2.30 crashes when fullscreen</title>
      <author>Samuel VISCAPI</author>
      <pubDate>Sun, 08 Jun 2014 20:11:37 +0000</pubDate>
      <description><![CDATA[Hi,<br />
<br />
Evince 2.30 often crashes with the following error message:<br />
<br />
(evince:2834): EvinceDocument-CRITICAL **: ev_image_save_tmp: assertion `GDK_IS_PIXBUF (pixbuf)&amp;#39; failed<br />
Segmentation fault<br />
<br />
How to reproduce: open Evince, &amp;nbsp;select a PDF file, go into fullscreen mode, then click into the body of the document.<br />
<br />
Cheers, Magic Sam<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=335</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=335</guid>
    </item>
        <item>
      <title>FS#334: op_bright_down.sh: error when decreasing brightness</title>
      <author>Alec Moskvin</author>
      <pubDate>Sun, 06 Apr 2014 19:16:15 +0000</pubDate>
      <description><![CDATA[The script does not handle brightness &amp;quot;0&amp;quot;.<br />
<br />
If you try to decrease brightness if it&amp;#39;s already at 0, it produces errors:<br />
<br />
<br />
~ # /usr/pandora/scripts/op_bright_down.sh<br />
/usr/pandora/scripts/op_bright_down.sh: line 18: [: : integer expression expected<br />
/usr/pandora/scripts/op_bright_down.sh: line 22: echo: write error: Invalid argument<br />
<br />
Not sure how to attach a patch here, but you can get the change with:<br />
<br />
<br />
git pull git://git.assembla.com/openpandora-oe.git bug-333<br />
<br />
I also changed the script to use /bin/sh since it&amp;#39;s a valid posix script.<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=334</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=334</guid>
    </item>
        <item>
      <title>FS#332: op_lidsettings.sh and op_power.sh scripts fail for some usernames</title>
      <author>russ</author>
      <pubDate>Mon, 03 Mar 2014 01:44:35 +0000</pubDate>
      <description><![CDATA[/usr/pandora/scripts/op_lidsettings.sh and&amp;nbsp;/usr/pandora/scripts/op_power.sh fail for some usernames due to poor shell scripting<br />
<br />
&amp;nbsp;<br />
<br />
these scripts find their config files by grepping /etc/passwd for the uer currently running&amp;nbsp;xfce4-session, but the loose regexp matches too much. this shell fragment from op_lidsettings.sh:<br />
<br />
&amp;nbsp;<br />
<br />
grep /etc/passwd -e $(ps u -C xfce4-session | tail -n1 | awk &amp;#39;{print $1}&amp;#39;)| cut -f 6 -d &amp;quot;:&amp;quot;<br />
<br />
&amp;nbsp;<br />
<br />
when a use called &amp;quot;me&amp;quot; is logged in, returns<br />
<br />
&amp;nbsp;<br />
<br />
/home/root<br />
<br />
/usr/games<br />
<br />
/var/run/dbus<br />
<br />
/home/me<br />
<br />
&amp;nbsp;<br />
<br />
rather than just &amp;quot;/home/me&amp;quot;<br />
<br />
&amp;nbsp;<br />
<br />
all instances of that construct (reading and writing settings, in both&amp;nbsp;op_lidsettings.sh and op_power.sh) should be changed to<br />
<br />
&amp;nbsp;<br />
<br />
grep /etc/passwd -e ^$(ps u -C xfce4-session | tail -n1 | awk &amp;#39;{print $1}&amp;#39;): | cut -f 6 -d &amp;quot;:&amp;quot;<br />
<br />
&amp;nbsp;<br />
<br />
to correctly match only the complete username field in /etc/passwd<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=332</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=332</guid>
    </item>
        <item>
      <title>FS#331: Hold switch key continuously sends X11 KeyPress events to active application, increasing CPU usage</title>
      <author>Alec Moskvin</author>
      <pubDate>Sun, 23 Feb 2014 22:12:35 +0000</pubDate>
      <description><![CDATA[When put into Hold mode, X11 handles the power switch as if it&amp;#39;s being pressed, and it generates lots of keypress events, passing them to the foreground application. Since /dev/input/eventX does not seem to continuously trigger, I&amp;#39;m guessing it&amp;#39;s due to key repeat.<br />
<br />
To reproduce:<br />
<br />
<br />
	Install xev and open it in the terminal<br />
	Put the power key in HOLD mode<br />
	Notice the &amp;quot;time&amp;quot; value changing rapidly<br />
<br />
<br />
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%.<br />
<br />
In addition, the key-press events continue even after the switch is taken off HOLD until another key is pressed.<br />
<br />
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).<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=331</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=331</guid>
    </item>
        <item>
      <title>FS#330: NetworkManager crashes after suspend to RAM</title>
      <author>Daniel Schaaaf</author>
      <pubDate>Sat, 08 Feb 2014 12:58:08 +0000</pubDate>
      <description><![CDATA[Suspend to RAM uses less power than the low power mode, but the NetworkManager crashes often after the Pandora woke up from suspend to RAM.<br />
<br />
This could be fixed with an update of&amp;nbsp;NetworkManager.<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=330</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=330</guid>
    </item>
        <item>
      <title>FS#329: Screen turns on when LCD closed</title>
      <author>David</author>
      <pubDate>Mon, 12 Aug 2013 04:11:33 +0000</pubDate>
      <description><![CDATA[Issue: The screen accidentally turns on even when the lid is closed.<br />
<br />
How to reproduce: &amp;quot;Screen blanking&amp;quot; must be enabled! Close the lid, wait more than 10 minutes, tap either shoulder button. &amp;nbsp;This behaviour happens whether on charge or battery, at the desktop or running an application, provided that the &amp;quot;screen blanking&amp;quot; option is enabled.<br />
<br />
Desired outcome: When the Pandora comes out of &amp;quot;screen blanking&amp;quot;, it should restore the brightness to the same value that it was before blanking.<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=329</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=329</guid>
    </item>
        <item>
      <title>FS#328: XFCE desktop icons not displayed when logging on too quickly [including solution!]</title>
      <author>Daniel Schaaaf</author>
      <pubDate>Thu, 18 Jul 2013 07:31:32 +0000</pubDate>
      <description><![CDATA[It looks like XFCE cannot find the icons for links/launchers on the desktop, when the user logs on too quickly. This happens either when the session chooser at start-up is disabled, or when the session is being chosen quickly after the session chooser is being displayed (e.g. by pressing enter as soon as the chooser window pops up). The icons are probably not generated yet at that time point.<br />
<br />
&amp;nbsp;<br />
<br />
A simple workaround is adding the command &amp;quot;xfdesktop --reload&amp;quot; to autostart. Couls this be included in the next SuperZaxxon release or a hotfix?<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=328</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=328</guid>
    </item>
        <item>
      <title>FS#327: Context menu for the XFCE menu</title>
      <author>Daniel Schaaaf</author>
      <pubDate>Thu, 27 Jun 2013 10:54:21 +0000</pubDate>
      <description><![CDATA[Right now. the XFCE menu handles right clicks like left clicks. It would be more logical to either not do anything on a right click, or open a context menu that e.g. lets the user generate a link to an application on the desktop.<br />
]]></description>
      <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=327</link>
      <guid>http://bugs.openpandora.org/index.php?do=details&amp;task_id=327</guid>
    </item>
      </channel>
</rss>
