From: raphhawk <raphhawk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Cursor not working out of box, devices/android not showing in pcmanfm
Date: Wed, 10 Nov 2021 06:58:42 +0100 [thread overview]
Message-ID: <20211110055842.7AeocGWGNGjCYWZF-OF-zGIcQs3Z5zVWEfrRak3mRv4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33972@inbox.vuxu.org>
[-- 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
prev parent reply other threads:[~2021-11-10 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 6:40 [ISSUE] " raphhawk
2021-11-10 5:58 ` raphhawk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211110055842.7AeocGWGNGjCYWZF-OF-zGIcQs3Z5zVWEfrRak3mRv4@z \
--to=raphhawk@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).