THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Alec Moskvin (Alec)
Attached to Project - OpenPandora Main OS
Summary - Hold switch key continuously sends X11 KeyPress events to active application, increasing CPU usage
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Release 1 (Zaxxon)
Severity - Medium
Priority - Very Low
Reported Version - SuperZaxxon Final 1.54
Due in Version - Undecided
Due Date - Undecided
Details - <p>When put into Hold mode, X11 handles the power switch as if it'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'm guessing it'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 "time" 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>
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=331
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Daniel Schaaaf (danielm)
Attached to Project - OpenPandora Main OS
Summary - NetworkManager crashes after suspend to RAM
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Release 1 (Zaxxon)
Severity - Low
Priority - Very Low
Reported Version - SuperZaxxon Final 1.54
Due in Version - Undecided
Due Date - Undecided
Details - <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 NetworkManager.</p>
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=330
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
It's difficult to contribute to OpenPandora development. First, there is
a bit of confusion with development separated all over the place.
Second, you guys depend on a underdocumented and outdated project like
OpenEmbedded (good thing we're moving away from it). Third, the
separation all over the place creates confusion/madness. I thought that
the development happened on the github (way easier to interact with) and
I've sent a few pull request there, just to be warned to move later.
Fourth, when I tried bugs.openpandora.org, the system seems broken (it
isn't accepting my bug-report/patch and even still, I had to upload the
patch to gist.github.com, because there was no attachment button). And
no we have this mailing list, with a broken web interface where I can
only request a new account through emails sent to
address-that-i-don't-remember-how-i-got.
Enough of my rant, let's do business...
I'm attaching the patch on this email. You can find more details about
it in the file contents. You can apply it with git apply (it was
generated with git format-patch), although I never really used it. The
patch is also hosted on gits:
https://gist.github.com/vinipsmaker/8795487
This change only affects automounting behaviour. The "manual" mounting
through the Thunar file-manager continues to get the argument wrong.
I'll study the hal architecture and see how I can tune the system even
further.
--
Vinícius dos Santos Oliveira
https://about.me/vinipsmaker
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#300 - SuperZaxxon interprets on-disk FAT32 filenames differently than desktop Linux
User who did this - Vinícius dos Santos Oliveira (vinipsmaker)
----------
<p>I'm working on that, but I'm not a core developer with commit access, then I need someone to review my patches.</p>
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=300#comment534
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.