[ISSUE] Cursor not working out of box, devices/android not showing in pcmanfm

[ISSUE] Cursor not working out of box, devices/android not showing in pcmanfm

[raphhawk]

[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]

New issue by raphhawk on void-packages repository

https://github.com/void-linux/void-packages/issues/33972

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
   Void 5.13.19_1 x86_64 GenuineIntel uptodate rFFF
* package:  
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
  xf86-input-synaptics
  dbus
  android-udev-rules

### Expected behavior
    After a fresh install of void in a thinkpad, the mouse i.e, the tochpad and trackpoint both should work out of the box.
    Android and usb devices / partitions should be visible in any graphical file manager and should be able to manage those file 
    systems.
### Actual behavior
    no movement of mouse trackpad but it does with trackpoint
    no devices are visible in a graphical file manager and no mount options are working 
### Steps to reproduce the behavior
     Fresh install void base on any "thinkpad" which has both trackpoint and trackpad
     I am running bspwm without a dm on top of void base. 
### The solution
     Ofcourse I have found a "temporary" solution for this behaviour i believe but this keeps me from using void as a daily driver.
     1. for the cursors, I had to install xf86-input-synaptics and add a kernal parameter to grub i.e  psmouse.synaptics_intertouch=0  
     2. for the android devices to "just show up", i had to install android-udev-rules package. It still doesnot mount out of the box.
     3. for automounting the drives, the user should be in storage group and need to edit the Udisks2 policy and also need to start the xinit with dbus-session-start.
### The Problem and Conclusion
     It would be way better if void-base supported the android and devices situation out of the box and also the cursors situation.    
### Thankyou

Re: [ISSUE] [CLOSED] Cursor not working out of box, devices/android not showing in pcmanfm

[raphhawk]

[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]

Closed issue by raphhawk on void-packages repository

https://github.com/void-linux/void-packages/issues/33972

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  *output of ``xuname`` (part of xtools)*
   Void 5.13.19_1 x86_64 GenuineIntel uptodate rFFF
* package:  
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
  xf86-input-synaptics
  dbus
  android-udev-rules

### Expected behavior
    After a fresh install of void in a thinkpad, the mouse i.e, the tochpad and trackpoint both should work out of the box.
    Android and usb devices / partitions should be visible in any graphical file manager and should be able to manage those file 
    systems.
### Actual behavior
    no movement of mouse trackpad but it does with trackpoint
    no devices are visible in a graphical file manager and no mount options are working 
### Steps to reproduce the behavior
     Fresh install void base on any "thinkpad" which has both trackpoint and trackpad
     I am running bspwm without a dm on top of void base. 
### The solution
     Ofcourse I have found a "temporary" solution for this behaviour i believe but this keeps me from using void as a daily driver.
     1. for the cursors, I had to install xf86-input-synaptics and add a kernal parameter to grub i.e  psmouse.synaptics_intertouch=0  
     2. for the android devices to "just show up", i had to install android-udev-rules package. It still doesnot mount out of the box.
     3. for automounting the drives, the user should be in storage group and need to edit the Udisks2 policy and also need to start the xinit with dbus-session-start.
### The Problem and Conclusion
     It would be way better if void-base supported the android and devices situation out of the box and also the cursors situation.    
### Thankyou