<?xml version="1.0" ?>
<rdf:RDF xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns="http://purl.org/rss/1.0/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel rdf:about="http://bugs.openpandora.org/">
    <title>OpenPandora - Hunting Timmy, the Bug.</title>
    <link>http://bugs.openpandora.org/</link>
    <description>OpenPandora - Hunting Timmy, the Bug.OpenPandora Main OS: Recently opened tasks</description>
    <dc:date>2014-12-10T01:48:55Z</dc:date>
    <items>
      <rdf:Seq>
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=337" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=336" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=335" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=334" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=332" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=331" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=330" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=329" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=328" />
                <rdf:li rdf:resource="http://bugs.openpandora.org/index.php?do=details&amp;task_id=327" />
              </rdf:Seq>
    </items>
    		
  </channel>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=337">
    <title>FS#337: SPAM</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=337</link>
    <dc:date>2014-12-10T01:48:55Z</dc:date>
    <dc:creator></dc:creator>
    <description>SPAM</description>
    <content:encoded><![CDATA[<p>SPAM</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=336">
    <title>FS#336: Touch screen sensitivity too low</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=336</link>
    <dc:date>2014-06-28T08:32:38Z</dc:date>
    <dc:creator>Kazimierz Król</dc:creator>
    <description>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).</description>
    <content:encoded><![CDATA[<p>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&#39;t react to my finger at all (even if pressed quite hard).</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=335">
    <title>FS#335: Evince 2.30 crashes when fullscreen</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=335</link>
    <dc:date>2014-06-08T20:11:37Z</dc:date>
    <dc:creator>Samuel VISCAPI</dc:creator>
    <description>Hi,

Evince 2.30 often crashes with the following error message:

(evince:2834): EvinceDocument-CRITICAL **: ev_image_save_tmp: assertion `GDK_IS_PIXBUF (pixbuf)&amp;#39; failed
Segmentation fault

How to reproduce: open Evince, &amp;nbsp;select a PDF file, go into fullscreen mode, then click into the body of the document.

Cheers, Magic Sam</description>
    <content:encoded><![CDATA[<p>Hi,</p>

<p>Evince 2.30 often crashes with the following error message:</p>

<p>(evince:2834): EvinceDocument-CRITICAL **: ev_image_save_tmp: assertion `GDK_IS_PIXBUF (pixbuf)&#39; failed<br />
Segmentation fault</p>

<p>How to reproduce: open Evince, &nbsp;select a PDF file, go into fullscreen mode, then click into the body of the document.</p>

<p>Cheers, Magic Sam</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=334">
    <title>FS#334: op_bright_down.sh: error when decreasing brightness</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=334</link>
    <dc:date>2014-04-07T21:49:19Z</dc:date>
    <dc:creator>Alec Moskvin</dc:creator>
    <description>The script does not handle brightness &amp;quot;0&amp;quot;.

If you try to decrease brightness if it&amp;#39;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&amp;#39;s a valid posix script.</description>
    <content:encoded><![CDATA[<p>The script does not handle brightness &quot;0&quot;.</p>

<p>If you try to decrease brightness if it&#39;s already at 0, it produces errors:</p>

<pre>
~ # /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</pre>

<p>Not sure how to attach a patch here, but you can get the change with:</p>

<pre>
git pull git://git.assembla.com/openpandora-oe.git bug-333</pre>

<p>I also changed the script to use /bin/sh since it&#39;s a valid posix script.</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=332">
    <title>FS#332: op_lidsettings.sh and op_power.sh scripts fail for some usernames</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=332</link>
    <dc:date>2014-03-22T17:02:22Z</dc:date>
    <dc:creator>russ</dc:creator>
    <description>/usr/pandora/scripts/op_lidsettings.sh and&amp;nbsp;/usr/pandora/scripts/op_power.sh fail for some usernames due to poor shell scripting

&amp;nbsp;

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:

&amp;nbsp;

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;

&amp;nbsp;

when a use called &amp;quot;me&amp;quot; is logged in, returns

&amp;nbsp;

/home/root

/usr/games

/var/run/dbus

/home/me

&amp;nbsp;

rather than just &amp;quot;/home/me&amp;quot;

&amp;nbsp;

all instances of that construct (reading and writing settings, in both&amp;nbsp;op_lidsettings.sh and op_power.sh) should be changed to

&amp;nbsp;

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;

&amp;nbsp;

to correctly match only the complete username field in /etc/passwd</description>
    <content:encoded><![CDATA[<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">/usr/pandora/scripts/op_lidsettings.sh and&nbsp;<span style="font-family: 'Source Code Pro'; font-size: 12px; line-height: normal;">/usr/pandora/scripts/</span>op_power.sh fail for some usernames due to poor shell scripting</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">these scripts find their config files by grepping /etc/passwd for the uer currently running&nbsp;xfce4-session, but the loose regexp matches too much. this shell fragment from op_lidsettings.sh:</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">grep /etc/passwd -e $(ps u -C xfce4-session | tail -n1 | awk &#39;{print $1}&#39;)| cut -f 6 -d &quot;:&quot;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">when a use called &quot;me&quot; is logged in, returns</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">/home/root</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">/usr/games</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">/var/run/dbus</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">/home/me</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">rather than just &quot;/home/me&quot;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">all instances of that construct (reading and writing settings, in both&nbsp;op_lidsettings.sh and op_power.sh) should be changed to</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';"><span style="font-family: 'Source Code Pro'; font-size: 12px; line-height: normal;">grep /etc/passwd -e ^$(ps u -C xfce4-session | tail -n1 | awk &#39;{print $1}&#39;): | cut -f 6 -d &quot;:&quot;</span></p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';">&nbsp;</p>

<p style="margin: 0px; font-size: 12px; line-height: normal; font-family: 'Source Code Pro';"><span style="font-family: 'Source Code Pro'; font-size: 12px; line-height: normal;">to correctly match only the complete username field in /etc/passwd</span></p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=331">
    <title>FS#331: Hold switch key continuously sends X11 KeyPress events to active application, increasing CPU usage</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=331</link>
    <dc:date>2014-02-23T22:12:35Z</dc:date>
    <dc:creator>Alec Moskvin</dc:creator>
    <description>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.

To reproduce:


	Install xev and open it in the terminal
	Put the power key in HOLD mode
	Notice the &amp;quot;time&amp;quot; value changing rapidly


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).</description>
    <content:encoded><![CDATA[<p>When put into Hold mode, X11 handles the power switch as if it&#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&#39;m guessing it&#39;s due to key repeat.</p>

<p>To reproduce:</p>

<ul>
	<li>Install xev and open it in the terminal</li>
	<li>Put the power key in HOLD mode</li>
	<li>Notice the &quot;time&quot; value changing rapidly</li>
</ul>

<p>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%.</p>

<p>In addition, the key-press events continue even after the switch is taken off HOLD until another key is pressed.</p>

<p>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).</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=330">
    <title>FS#330: NetworkManager crashes after suspend to RAM</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=330</link>
    <dc:date>2014-02-08T12:58:08Z</dc:date>
    <dc:creator>Daniel Schaaaf</dc:creator>
    <description>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.

This could be fixed with an update of&amp;nbsp;NetworkManager.</description>
    <content:encoded><![CDATA[<p>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.</p>

<p>This could be fixed with an update of&nbsp;NetworkManager.</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=329">
    <title>FS#329: Screen turns on when LCD closed</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=329</link>
    <dc:date>2013-08-12T04:11:33Z</dc:date>
    <dc:creator>David</dc:creator>
    <description>Issue: The screen accidentally turns on even when the lid is closed.

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.

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.</description>
    <content:encoded><![CDATA[<p>Issue: The screen accidentally turns on even when the lid is closed.</p>

<p>How to reproduce: &quot;Screen blanking&quot; must be enabled! Close the lid, wait more than 10 minutes, tap either shoulder button. &nbsp;This behaviour happens whether on charge or battery, at the desktop or running an application, provided that the &quot;screen blanking&quot; option is enabled.</p>

<p>Desired outcome: When the Pandora comes out of &quot;screen blanking&quot;, it should restore the brightness to the same value that it was before blanking.</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=328">
    <title>FS#328: XFCE desktop icons not displayed when logging on too quickly [including solution!]</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=328</link>
    <dc:date>2013-07-18T07:32:45Z</dc:date>
    <dc:creator>Daniel Schaaaf</dc:creator>
    <description>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.

&amp;nbsp;

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?</description>
    <content:encoded><![CDATA[<p>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.</p>

<p>&nbsp;</p>

<p>A simple workaround is adding the command &quot;xfdesktop --reload&quot; to autostart. Couls this be included in the next SuperZaxxon release or a hotfix?</p>]]></content:encoded>
  </item>
    <item rdf:about="http://bugs.openpandora.org/index.php?do=details&amp;task_id=327">
    <title>FS#327: Context menu for the XFCE menu</title>
    <link>http://bugs.openpandora.org/index.php?do=details&amp;task_id=327</link>
    <dc:date>2013-06-27T10:54:21Z</dc:date>
    <dc:creator>Daniel Schaaaf</dc:creator>
    <description>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.</description>
    <content:encoded><![CDATA[<p>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.</p>]]></content:encoded>
  </item>
  </rdf:RDF>
