[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use

2020-04-01 Thread Patrick McMunn
https://bugs.kde.org/show_bug.cgi?id=328987

--- Comment #24 from Patrick McMunn  ---
Since this is such a longstanding bug with apparently no easy solution, maybe a
possible workaround or alternative way of dealing with it could be adding a
sort of "Gsme Mode" to KDE. It could simply be a quick-access widget of some
kind that's configurable to do things like disable the screensaver, power
management and compositing. Maybe it would even be possible to add a list of
applications to it do that, whever an application on the list is launched, game
mode automatically activates. The widget could monitor whether the specified
applications are running, and then deactivate game mode automatically when the
application is either exited normally or crashes. Would something like that be
possible?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 419460] New: Kscreenlocker and power management activate even while playing a game with a joystick or gamepad

2020-03-31 Thread Patrick McMunn
https://bugs.kde.org/show_bug.cgi?id=419460

Bug ID: 419460
   Summary: Kscreenlocker and power management activate even while
playing a game with a joystick or gamepad
   Product: kscreenlocker
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: doctorwho...@gmail.com
CC: bhus...@gmail.com
  Target Milestone: ---

I'm not sure if kscreenlocker is the best place to file this bug because it
really involves potentially three components: the screen locker, power
management, and device I/O.

OBSERVED RESULT

I occasionally like to play games on my computer, and when I use a joystick or
gamepad (e.g. Logtech F310, Xbox One controller) to play a game, KDE apparently
does not consider joystick input to be a kind of activity which lets it know
that a user is still interacting with the system. Thus, if the screen locker is
enabled, the screen locker will activate even while playing a game unless I
occasionally move the mouse, touch my laptop's touchpad, or press a key on the
keyboard. Likewise, if the Power management is enabled for things like dimming
the screen, turning off the screen, or, presumably sleeping/powering down the
system, it will activate after the specified time period has elapsed even if
I'm playing a game.

EXPECTED RESULT

When playing a game with a joystick or gamepad, the system should register
gamepad I/O as activity which keeps the system awake and prevents power
management or the screen locker from activating.

SOFTWARE/OS VERSIONS
Linux: kernel 5.4.28 / Manjaro 19.0.2
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION

Although I'm reporting this bug on the versions specified above, this has been
a longstanding issue with KDE/Plasma 5, and I have observed it on other Linux
distros and FreeBSD, so it appears to be independent of the platform it's
running on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 419185] Amarok 2.9.70 crashes at startup with QSocketNotifier: Invalid socket on FreeBSD 12.1-RELEASE

2020-03-24 Thread Patrick McMunn
https://bugs.kde.org/show_bug.cgi?id=419185

--- Comment #1 from Patrick McMunn  ---
Created attachment 126985
  --> https://bugs.kde.org/attachment.cgi?id=126985=edit
output of amarok --debug

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 419185] New: Amarok 2.9.70 crashes at startup with QSocketNotifier: Invalid socket on FreeBSD 12.1-RELEASE

2020-03-24 Thread Patrick McMunn
https://bugs.kde.org/show_bug.cgi?id=419185

Bug ID: 419185
   Summary: Amarok 2.9.70 crashes at startup with QSocketNotifier:
Invalid socket on FreeBSD 12.1-RELEASE
   Product: amarok
   Version: unspecified
  Platform: FreeBSD Ports
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: doctorwho...@gmail.com
  Target Milestone: kf5

Created attachment 126984
  --> https://bugs.kde.org/attachment.cgi?id=126984=edit
Output of KDE crash reporter

Installed Amarok 2.9.70_1 from FreeBSD binary packages.

SOFTWARE/OS VERSIONS
FreeBSD: 12.1-RELEASE-p3
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.67.0
Qt Version: 5.13.2
OS Type: 64-bit

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 404920] New: Plasma 5.15.1 does not detect joystick or load joystick kcm module under FreeBSD

2019-02-28 Thread Patrick McMunn
https://bugs.kde.org/show_bug.cgi?id=404920

Bug ID: 404920
   Summary: Plasma 5.15.1 does not detect joystick or load
joystick kcm module under FreeBSD
   Product: systemsettings
   Version: 5.15.1
  Platform: Other
OS: FreeBSD
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_joystick
  Assignee: unassigned-b...@kde.org
  Reporter: doctorwho...@gmail.com
  Target Milestone: ---

SUMMARY

I have a Logitech Dual Action game pad plugged into a computer which dual boots
Funtoo Linux 1.2 and FreeBSD 12.0-STABLE r344470. My Linux installation is
running Plasma 5.12.3, and the gamepad is detected and works fine. The joystick
kcm module shows up in system settings and works as expected. But on my FreeBSD
installation, which runs Plasma 5.15.1, the kcm module for joystick doesn't
even appear in the system settings input tab. I do have a /dev/input/js0 device
node, and jstest-gtk correctly identifies the gamepad as a Logitech Dual
Action. So the gamepad works on the OS level under FreeBSD, but Plasma does not
detect it. I did ensure that xf86-input-joystick is installed.


SOFTWARE/OS VERSIONS
FreeBSD: 12.0-STABLE r344470
KDE Plasma Version: 5.15.1
KDE Frameworks Version: 5.55.0
Qt Version: 5.12.1

-- 
You are receiving this mail because:
You are watching all bug changes.