[systemsettings] [Bug 396269] Touchpad settings are changed when another mouse is connected

2018-07-07 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=396269

Alex Mason  changed:

   What|Removed |Added

 CC||alexmason...@outlook.com

--- Comment #1 from Alex Mason  ---
Also having this issue. Same issue occurs when entering kcm_mouse and hitting
'Apply' - mouse settings get applied to the touchpad.

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

[Touchpad-KCM] [Bug 395722] touchpad settings are wrong after resuming from suspend

2018-07-07 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=395722

Alex Mason  changed:

   What|Removed |Added

 CC||alexmason...@outlook.com

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

[systemsettings] [Bug 396269] Touchpad settings are changed when another mouse is connected

2018-07-14 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=396269

--- Comment #4 from Alex Mason  ---
Related: https://bugs.kde.org/show_bug.cgi?id=395722

Running kcminit kcm_touchpad as suggested in the above bug report returns the
correct touchpad settings. Also, this bug occurs when "Disable touchpad when
mouse is plugged in" setting is active. Uupon unplugging mouse and touchpad is
re-enabled, touchpad settings are not applied until running kcminit
kcm_touchpad.

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

[systemsettings] [Bug 400229] Flat and Adaptive acceleration profiles both do the same thing

2018-12-11 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=400229

Alex Mason  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||alexmason...@outlook.com
 Status|REPORTED|CONFIRMED

--- Comment #11 from Alex Mason  ---
Mouse KCM does indeed not change the acceleration profile on X11 libinput
pointers.
Simple way to see: xinput list-props on your mouse device. libinput Accel
Profile Enabled is default 1,0. Changing to 'Flat' profile on GNOME changes
this to 0,1. Change it to 0,1 through xinput and you'll no longer have mouse
acceleration. I believe the mouse KCM is changing it to 1,1, which still
results in mouse acceleration.

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

[systemsettings] [Bug 400229] Flat and Adaptive acceleration profiles both do the same thing

2018-12-11 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=400229

--- Comment #12 from Alex Mason  ---
I have no experience with the KDE codebase, but I took a look around out of
curiosity.
At line 150 of
plasma-desktop/kcms/mouse/backends/x11/x11_libinput_dummydevice.cpp,
LIBINPUT_PROP_ACCEL_PROFILE_ENABLED is defined as a boolean. However, xinput
list-props shows two booleans for "libinput Accel Profile Enabled". 1 0
corresponds to Adaptive profile while 0 1 corresponds to Flat profile.
Might be a lead.

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

[dolphin] [Bug 405837] New: Dolphin crashes opening icon changer

2019-03-24 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=405837

Bug ID: 405837
   Summary: Dolphin crashes opening icon changer
   Product: dolphin
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: alexmason...@outlook.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

SUMMARY
Dolphin 19.03.80 segfaults when opening the custom icon picker from a file's
properties.

STEPS TO REPRODUCE
1. Select a file
2. Open the file's properties
3. Click the icon button to the left of the file's name

OBSERVED RESULT
Dolphin crashes

EXPECTED RESULT
Icon picker view should appear.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux wth kde-unstable packages
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.13.0

ADDITIONAL INFORMATION

Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8e11610800 (LWP 2410))]

Thread 6 (Thread 0x7f8dff0e3700 (LWP 2526)):
#0  0x7f8e19559c21 in poll () from /usr/lib/libc.so.6
#1  0x7f8e14cc0690 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f8e14cc077e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f8e17600644 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f8e175a905c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f8e173e2da9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f8e173e41ac in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f8e15caca9d in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f8e19564b23 in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f8dffd19700 (LWP 2415)):
#0  0x7f8e19559c21 in poll () from /usr/lib/libc.so.6
#1  0x7f8e14cc0690 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f8e14cc077e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f8e17600644 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f8e175a905c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f8e173e2da9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f8e173e41ac in ?? () from /usr/lib/libQt5Core.so.5
#7  0x7f8e15caca9d in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f8e19564b23 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f8e0cffb700 (LWP 2414)):
#0  0x7f8e15cb2afc in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f8e0d5eb214 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x7f8e0d5eaf38 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x7f8e15caca9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x7f8e19564b23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f8e0f576700 (LWP 2413)):
#0  0x7f8e19559c21 in poll () from /usr/lib/libc.so.6
#1  0x7f8e14cc0690 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f8e14cc077e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f8e17600644 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f8e175a905c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f8e173e2da9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7f8e1786aba6 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x7f8e173e41ac in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7f8e15caca9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x7f8e19564b23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f8e10323700 (LWP 2412)):
#0  0x7f8e19559c21 in poll () from /usr/lib/libc.so.6
#1  0x7f8e14773630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f8e147752db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f8e10ef4a09 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7f8e173e41ac in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7f8e15caca9d in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f8e19564b23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f8e11610800 (LWP 2410)):
[KCrash Handler]
#6  0x7f8e187b9fd9 in ?? () from /usr/lib/libKF5ItemViews.so.5
#7  0x7f8e187ba394 in ?? () from /usr/lib/libKF5ItemViews.so.5
#8  0x7f8e187ba496 in ?? () from /usr/lib/libKF5ItemViews.so.5
#9  0x7f8e175d53a4 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/libQt5Core.so.5
#10 0x7f8e1755161e in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) () from /usr/lib/libQt5Core.so.5
#11 0x7f8e182da3c1 in ?? () from /usr/lib/libQt5Widgets.so.5
#12 0x7f8e182dc9e2 in QListWidgetItem::setData(int, QVariant const&) ()
from /usr/lib/libQt5Widgets.so.5
#13 0x7f8e182dcff7 in QListWidgetItem::QListWidgetIte

[dolphin] [Bug 405837] Dolphin crashes opening icon changer

2019-03-25 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=405837

Alex Mason  changed:

   What|Removed |Added

 Resolution|--- |DOWNSTREAM
 Status|REPORTED|RESOLVED

--- Comment #3 from Alex Mason  ---
Looks like this is just a packaging issue then! As Julian says, it's likely the
mismatch in frameworks versions. If the issue still occurs when pushed to
stable repos I will report the bug downstream in the Arch bug trackers.
Thank you

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

[kdeconnect] [Bug 401726] remote keyboard don't work since android update to 9

2018-12-06 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=401726

Alex Mason  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||alexmason...@outlook.com
 Ever confirmed|0   |1

--- Comment #1 from Alex Mason  ---
Same issue on Nokia 6.1, which updated to Android 9 recently. Keyboard and
presentation remote stopped working but virtual mouse still works.

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

[kwin] [Bug 400171] New: QuickTiled Windows Should Not be Shadowed

2018-10-22 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=400171

Bug ID: 400171
   Summary: QuickTiled Windows Should Not be Shadowed
   Product: kwin
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: alexmason...@outlook.com
  Target Milestone: ---

SUMMARY
Windows that have been QuickTiled (snapped to the side of the screen) draw
shadows, which is inconsistent with how other platforms manage tiling (GNOME,
macOS SplitView). Suggest removing property _KDE_NET_WM_SHADOW from QuickTiled
windows.

STEPS TO REPRODUCE
1. Enable window decoration shadows in Breeze.
2. QuickTile two windows side by side.
3. Observe shadow overlapping the unfocused window.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.1 and below
KDE Frameworks Version: 5.51 and below
Qt Version: 5.11 and below

ADDITIONAL INFORMATION
Ideally the two tiled windows would still have shadows but be on an equal
'z-index', but it seems easier to just remove the shadows to fix the issue.

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

[systemsettings] [Bug 396269] Touchpad settings are changed when another mouse is connected

2018-07-07 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=396269

Alex Mason  changed:

   What|Removed |Added

 CC||alexmason...@outlook.com

--- Comment #1 from Alex Mason  ---
Also having this issue. Same issue occurs when entering kcm_mouse and hitting
'Apply' - mouse settings get applied to the touchpad.

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

[Touchpad-KCM] [Bug 395722] touchpad settings are wrong after resuming from suspend

2018-07-07 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=395722

Alex Mason  changed:

   What|Removed |Added

 CC||alexmason...@outlook.com

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

[systemsettings] [Bug 396269] Touchpad settings are changed when another mouse is connected

2018-07-14 Thread Alex Mason
https://bugs.kde.org/show_bug.cgi?id=396269

--- Comment #4 from Alex Mason  ---
Related: https://bugs.kde.org/show_bug.cgi?id=395722

Running kcminit kcm_touchpad as suggested in the above bug report returns the
correct touchpad settings. Also, this bug occurs when "Disable touchpad when
mouse is plugged in" setting is active. Uupon unplugging mouse and touchpad is
re-enabled, touchpad settings are not applied until running kcminit
kcm_touchpad.

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