[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #10 from Rajeesh K V --- (In reply to Luca Weiss from comment #9) Thanks. > signal time=1477047039.599343 sender=:1.13 -> destination=(null destination) > serial=1100 path=/component/kcm_touchpad; > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed >string "kcm_touchpad" >string "Toggle Touchpad" >int64 5992314 > signal time=1477047041.263323 sender=:1.13 -> destination=(null destination) > serial=1101 path=/component/kcm_touchpad; > interface=org.kde.kglobalaccel.Component; member=globalShortcutPressed >string "kcm_touchpad" >string "Toggle Touchpad" >int64 5993987 Shortcut triggered twice in succession. Did you press the toggle shortcut twice, or just once? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #8 from Rajeesh K V --- Is this issue always reproducible? The problem I experience is when waking from sleep, touchpad is disabled (likely a kernel issue). Other than that, touchpad toggle is working as expected. Run the below command before you press touchpad toggle short cut and report the output: dbus-monitor "type='signal',interface='org.kde.kglobalaccel.Component'" If possible, can you revert commit cf0bf81ccd4c7f8afacda7084978af719340a138 (you may need to revert ca23c39229d607fa45a2d862b44233163853739b first) and check if the issue persists? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371276] Only black screen with breeze plymouth theme in plasma 5.8.2
https://bugs.kde.org/show_bug.cgi?id=371276 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #3 from Rajeesh K V --- Same case (black boot screen) with Fedora 24. On shutdown, though, the plasma icon within spinner is visible. Plymouth version 0.8.9. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 --- Comment #4 from Rajeesh K V --- Can you also confirm the hardware? Is it by chance a Lenovo Yoga laptop? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370643] KCMInit crash
https://bugs.kde.org/show_bug.cgi?id=370643 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Can you enable debuginfo details and provide the crash report? Also confirm whether kded_touchpad.so is installed in correct location (e.g: /usr/lib64/qt5/plugins/). -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 370588] Global keyboard shortcut for KDE Daemon:Toggle Touchpad actually maps to Disable Touchpad
https://bugs.kde.org/show_bug.cgi?id=370588 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Can you confirm the input driver? $xlsatoms | grep -i tap I have observed this behaviour in 5.8 as well, but there was no code change in touchpad daemon affecting this. Will take a closer look. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 369355] Touchpad configuration applet crashes
https://bugs.kde.org/show_bug.cgi?id=369355 Rajeesh K V changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #3 from Rajeesh K V --- *** This bug has been marked as a duplicate of bug 363109 *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session
https://bugs.kde.org/show_bug.cgi?id=363109 Rajeesh K V changed: What|Removed |Added CC||e...@theunixman.com --- Comment #5 from Rajeesh K V --- *** Bug 369355 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 369355] Touchpad configuration applet crashes
https://bugs.kde.org/show_bug.cgi?id=369355 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Are you running wayland? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 368156] No touchpad found
https://bugs.kde.org/show_bug.cgi?id=368156 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Please confirm the plasma-desktop version, and the input drivers installed ($xlsatoms | grep -i tap) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 353463] RFE: Make use of iio-sensor-proxy
https://bugs.kde.org/show_bug.cgi?id=353463 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 346900] floating point exception if folder in testing area is dropped onto itself twice
https://bugs.kde.org/show_bug.cgi?id=346900 Rajeesh K V changed: What|Removed |Added CC||victor.tr...@live.com --- Comment #6 from Rajeesh K V --- *** Bug 366113 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 366113] systemsettings crashes testing touchpad settings
https://bugs.kde.org/show_bug.cgi?id=366113 Rajeesh K V changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- *** This bug has been marked as a duplicate of bug 346900 *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 364934] How to disable touchpad after Login
https://bugs.kde.org/show_bug.cgi?id=364934 Rajeesh K V changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 364934] How to disable touchpad after Login
https://bugs.kde.org/show_bug.cgi?id=364934 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- There is the touchpad applet - you can add/enable them in system tray or in the desktop as regular applets. In addition, touchpad can be enabled/disabled using global short cut key. You can configure it in "System Settings → Input Devices → Touchpad → Enable/Disable Touchpad → Keyboard shortcuts". -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored
https://bugs.kde.org/show_bug.cgi?id=362800 Rajeesh K V changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Rajeesh K V --- You're welcome, Mark. I think libinput is declared as feature complete. Libinput aims to simplify input handling and a side-effect of it is providing good defaults instead of making many configuration options available, which previous drivers like synaptics did. You could try to contact libinput upstream if you'd like to pursue further. Closing this report. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored
https://bugs.kde.org/show_bug.cgi?id=362800 --- Comment #3 from Rajeesh K V --- Okay, thanks for confirmation. You could indeed switch to synaptics driver - simply uninstall xorg-x11-drv-libinput and install xorg-x11-drv-synaptics and see if that helps. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362800] Touchpad setting "Disable taps and scrolling only" ignored
https://bugs.kde.org/show_bug.cgi?id=362800 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Can you confirm the input driver used? Try: $ xlsatoms | grep -i tap FWIW, libinput does not support the 'disable tapping and scrolling only' option. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session
https://bugs.kde.org/show_bug.cgi?id=363109 Rajeesh K V changed: What|Removed |Added CC||mgraess...@kde.org Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Rajeesh K V --- Adding Martin Gräßlin to cc; to check how best to handle this for Wayland platform. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 363109] systemsettings crash when selecting touchpad when run in a wayland session
https://bugs.kde.org/show_bug.cgi?id=363109 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Can you provide the crash trace? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 351920] Touchpad Three Fingers setting not working
https://bugs.kde.org/show_bug.cgi?id=351920 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #2 from Rajeesh K V --- Can you confirm the input driver used? Use `xlsatoms|grep -i tap`. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362547] Could not start ksmserver. Check your installation
https://bugs.kde.org/show_bug.cgi?id=362547 --- Comment #3 from Rajeesh K V --- I really think this is a packaging issue. But I'll keep looking. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362547] Could not start ksmserver. Check your installation
https://bugs.kde.org/show_bug.cgi?id=362547 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Is this crash reproducible in plasma 5.6.3? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362473] Expanded Media Controller widget causes Next song to start from Slider value of current song
https://bugs.kde.org/show_bug.cgi?id=362473 Rajeesh K V changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-workspace/0e2af335dcd112 ||a7acefcf226cc56f5df518adad --- Comment #6 from Rajeesh K V --- Git commit 0e2af335dcd112a7acefcf226cc56f5df518adad by Rajeesh K V. Committed on 29/04/2016 at 13:20. Pushed by knambiar into branch 'master'. [Media Controller[: Fix playing next/previous song seeking Seems the Slider value is not reset when Next/Previous buttons are pressed in Media Controller widget. This causes next/previous song to seek the slider position instead of starting from beginning. REVIEW: 127789 M +8-2applets/mediacontroller/contents/ui/ExpandedRepresentation.qml http://commits.kde.org/plasma-workspace/0e2af335dcd112a7acefcf226cc56f5df518adad -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362473] Expanded Media Controller widget causes Next song to start from Slider value of current song
https://bugs.kde.org/show_bug.cgi?id=362473 --- Comment #5 from Rajeesh K V --- https://git.reviewboard.kde.org/r/127789/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362473] Expanded Media Controller widget causes Next song to start from Slider value of current song
https://bugs.kde.org/show_bug.cgi?id=362473 --- Comment #3 from Rajeesh K V --- Created attachment 98687 --> https://bugs.kde.org/attachment.cgi?id=98687&action=edit Fix playing next/previous song seeking That didn't quite work, but the attached patch to reset Slider value seems to work. Does this look okay? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362473] Expanded Media Controller widget causes Next song to start from Slider value of current song
https://bugs.kde.org/show_bug.cgi?id=362473 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Created attachment 98686 --> https://bugs.kde.org/attachment.cgi?id=98686&action=edit D-Bus monitor output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362473] New: Expanded Media Controller widget causes Next song to start from Slider value of current song
https://bugs.kde.org/show_bug.cgi?id=362473 Bug ID: 362473 Summary: Expanded Media Controller widget causes Next song to start from Slider value of current song Product: plasmashell Version: 5.6.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: rajeeshknamb...@gmail.com CC: mklape...@kde.org, plasma-b...@kde.org Using VLC to play songs. While a song is in progress (say 50%) open Media Controller widget and press 'Next'. The next song often starts from the middle instead of start. Same issue with 'Previous' button as well. Probably something to do with Slider value and delayed timer setting it. Possibly related to bugs #35815 and #341446. Reproducible: Sometimes Steps to Reproduce: 1. Add a bunch of songs to VLC playlist and start play. 2. When the first song is into playing few seconds, open Media Controller and press 'Next' 3. Observe that next song doesn't start from beginning, but skipped to the position of previously playing song. Actual Results: Next song doesn't start from beginning, but skipped to the position of previously playing song. Expected Results: Next song doesn't start from beginning. Not always reproducible. Possibly a race condition with the timer enabled slider seeking code? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 362370] kcm_touchpad: Enabling "Mouse click emulation" does not enable the associated drop downs
https://bugs.kde.org/show_bug.cgi?id=362370 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Rajeesh K V --- *** This bug has been marked as a duplicate of bug 348328 *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 348328] cannot edit touchpad tap settings beyond enabling/disabling Mouse Click Emulation
https://bugs.kde.org/show_bug.cgi?id=348328 Rajeesh K V changed: What|Removed |Added CC||arjunak...@gmail.com --- Comment #9 from Rajeesh K V --- *** Bug 362370 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361566] Panel auto-hide is completely broken
https://bugs.kde.org/show_bug.cgi?id=361566 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #10 from Rajeesh K V --- Same issue in Fedora 23 after upgrade to 5.6.2 - autohide does not work, panel is always visible. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 360943] Can't customize touchpad's configuration
https://bugs.kde.org/show_bug.cgi?id=360943 Rajeesh K V changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from Rajeesh K V --- If both drivers are installed, libinput gets the preference. Either you can change the priority similar to comment#3 or simply uninstall the driver you're not using. Touchpad KCM cannot do anything on its own, so closing the bug. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 360943] Can't customize touchpad's configuration
https://bugs.kde.org/show_bug.cgi?id=360943 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #1 from Rajeesh K V --- Hi, The reason these options greyed out is you (or the distribution) is using/installed the 'new' libinput touchpad driver. The package name is usually xorg-x11-drv-libinput. Libinput is the unified touchpad driver for X.org and Wayland; but it exposes only few configurable options compared to the 'old'/previous synaptics driver (package xorg-x11-drv-synaptics). If you want all the options to be individually configured, simply remove libinput driver and install synaptics driver. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 360372] Unplugging a mouse does not re-enable touchpad
https://bugs.kde.org/show_bug.cgi?id=360372 Rajeesh K V changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.6 CC||rajeeshknamb...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Rajeesh K V --- *** This bug has been marked as a duplicate of bug 349545 *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 349545] Disable touchpad when mouse is plugged in, never re-enables when mouse is unplugged
https://bugs.kde.org/show_bug.cgi?id=349545 Rajeesh K V changed: What|Removed |Added CC||l.bonn...@laposte.net --- Comment #4 from Rajeesh K V --- *** Bug 360372 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 358189] kdeinit5 and kded5 crash in XlibBackend::setTouchpadOff
https://bugs.kde.org/show_bug.cgi?id=358189 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #3 from Rajeesh K V --- This should be fixed in master/5.6 branch - do you still face this issue? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/plas ||ma-desktop/86b59198f1c60236 ||034567dc804b578376f8d06c Resolution|--- |FIXED --- Comment #19 from Rajeesh K V --- Git commit 86b59198f1c60236034567dc804b578376f8d06c by Rajeesh K V. Committed on 09/03/2016 at 19:29. Pushed by knambiar into branch 'Plasma/5.6'. Touchpad KCM: Fix synaptics driver issues Fixes couple of issues: 1. Remove spurious members of SynapticsTouchpad class from parent class XlibTouchpad; fixing wrong scroll delta values. 2. Enlarge vertical,horizontal&circular scroll delta and maxtapmove allowing value more than 100. The max value supported by driver is 1000 REVIEW: 127306 M +15 -0kcms/touchpad/src/backends/x11/synapticstouchpad.cpp M +3-1kcms/touchpad/src/backends/x11/synapticstouchpad.h M +1-10 kcms/touchpad/src/backends/x11/xlibtouchpad.cpp M +2-4kcms/touchpad/src/backends/x11/xlibtouchpad.h M +3-3kcms/touchpad/src/kcm/touchpad.kcfg M +13 -1kcms/touchpad/src/kcm/ui/scroll.ui M +3-0kcms/touchpad/src/kcm/ui/tap.ui http://commits.kde.org/plasma-desktop/86b59198f1c60236034567dc804b578376f8d06c -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added Attachment #97749|0 |1 is obsolete|| --- Comment #18 from Rajeesh K V --- Created attachment 97799 --> https://bugs.kde.org/attachment.cgi?id=97799&action=edit Synaptic driver fix and max scroll delta change Hello, here is another patch with slightly different technical approach. Could you test this one instead and report if it works? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added Attachment #97719|0 |1 is obsolete|| Attachment #97739|0 |1 is obsolete|| --- Comment #16 from Rajeesh K V --- Created attachment 97749 --> https://bugs.kde.org/attachment.cgi?id=97749&action=edit Synaptic driver fix and max scroll delta change Here's the new patch. Please test and share feedback? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 --- Comment #15 from Rajeesh K V --- (In reply to Mykola Krachkovsky from comment #14) > (In reply to Rajeesh K V from comment #13) > > (In reply to Mykola Krachkovsky from comment #11) > > > > > In file kcms/touchpad/src/backends/x11/synapticstouchpad.h class > > > SynapticsTouchpad redefines (line 34) fields: > > > QStringList m_scaleByResX, m_scaleByResY, m_toRadians; > > > from parent class XlibTouchpad (file > > > kcms/touchpad/src/backends/x11/xlibtouchpad.h, line 79). > > > So usage that fields in files synapticstouchpad.cpp (adding data) and > > > xlibtouchpad.cpp (reading data) works with different variables. And > > > XlibTouchpad::getPropertyScale returns default 1.0 instead of correct > > > value. > > > > Indeed, that would explain the problem. There was a similar bug but that was > > fixed. Can you raise a review request for this patch or shall I do it for > > you? > > > > I don't know what I should do. Okay, I'll take care of it. > > > > (In reply to Mykola Krachkovsky from comment #11) > > > But KCM works not ok > > What do you mean by KCM doesn't work? > > It looks like VertScrollDelta and HorizScrollDelta are written to > ~/.config/touchpadrc but aren't actually set to device. But MaxTapMove, > CircScrollDelta works "ok". > There is also "Active settings don't match saved settings. You currently see > saved settings." message when I press "Show active settings" I got 10mm for > vertical and 0.1mm for horizontal. This requires my patch to work as well. Scroll delta maximum is hard coded to 10 in the kcfg file. I'll fold both into single patch and upstream. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 --- Comment #13 from Rajeesh K V --- (In reply to Mykola Krachkovsky from comment #11) > In file kcms/touchpad/src/backends/x11/synapticstouchpad.h class > SynapticsTouchpad redefines (line 34) fields: > QStringList m_scaleByResX, m_scaleByResY, m_toRadians; > from parent class XlibTouchpad (file > kcms/touchpad/src/backends/x11/xlibtouchpad.h, line 79). > So usage that fields in files synapticstouchpad.cpp (adding data) and > xlibtouchpad.cpp (reading data) works with different variables. And > XlibTouchpad::getPropertyScale returns default 1.0 instead of correct value. Indeed, that would explain the problem. There was a similar bug but that was fixed. Can you raise a review request for this patch or shall I do it for you? (In reply to Mykola Krachkovsky from comment #11) > But KCM works not ok What do you mean by KCM doesn't work? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added Attachment #97717|0 |1 is obsolete|| --- Comment #9 from Rajeesh K V --- Created attachment 97719 --> https://bugs.kde.org/attachment.cgi?id=97719&action=edit Allow large scroll delta Please use this version which has fix for maximum finger movement also. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 --- Comment #8 from Rajeesh K V --- Created attachment 97717 --> https://bugs.kde.org/attachment.cgi?id=97717&action=edit Allow large scroll delta Disclaimer: I don't fully understand why the issue manifested recently (it could be the recent refactoring for hotplug support but not sure). Could you try the attached patch and see if it helps? It should let you configure the scroll delta values - I chose upper limit of 500, which is arbitrary. I'm quite vary of including this patch in 5.6 as it is quite late in the release cycle. Please test and report if it helps. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 --- Comment #6 from Rajeesh K V --- (In reply to Mykola Krachkovsky from comment #0) > Actual Results: > UI units (mm) are just written to touchpad settings. Default touchpad values > coudn't be set using UI. Are you unable to set the scrolling distance parameters in UI? Do you also have libinput driver (xorg-x11-drv-libinput or equivalent) installed? -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 360099] GUI caps values too low.
https://bugs.kde.org/show_bug.cgi?id=360099 Rajeesh K V changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||rajeeshknamb...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from Rajeesh K V --- *** This bug has been marked as a duplicate of bug 359460 *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added CC||p...@muddygoat.org --- Comment #3 from Rajeesh K V --- *** Bug 360099 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits
https://bugs.kde.org/show_bug.cgi?id=359460 Rajeesh K V changed: What|Removed |Added CC||rajeeshknamb...@gmail.com --- Comment #2 from Rajeesh K V --- Can you post the output of 'xinput list-props '? touchpad id can be found by running just 'xinput'. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load
https://bugs.kde.org/show_bug.cgi?id=357907 --- Comment #10 from Rajeesh K V --- Uninstalled xorg-x11-drv-libinput, running on synaptics driver; still no crash for me. So, yes - it would be great to get some debug output. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 357907] Crash eventual crash, often on load
https://bugs.kde.org/show_bug.cgi?id=357907 --- Comment #5 from Rajeesh K V --- I cannot reproduce this crash. I have both xorg-x11-drv-libinput and xorg-x11-drv-synaptics installed. Is it possible to provide some debug input? Please check if "xcb_connection_t *c" is valid in XcbAtom::XcbAtom, XcbAtom::intern and check "m_connection" is valid in XcbAtom::atom(). All call sites are in kcms/touchpad/src/backend/x11/xcbatom.cpp. -- You are receiving this mail because: You are watching all bug changes.