Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Your problem is: the shell opens the file for writing *before* it invokes sudo.
Quoting the > is no solution either (sudo does not invoke another shell that handles the > )
A solution:
sudo runs a program that writes the file. And the shell can feed the sudo with a pipe.
Code:
echo '
...
' | sudo dd of=file
The shell opens the pipe to sudo, this does not need privileges.
Last edited by MadeInGermany; 08-23-2018 at 04:08 PM.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
First make sure the installation of libinput didn't already create the file by default in /usr/share/X11/xorg.conf.d ... (it does, for instance, in Arch Linux).
Then, just copy the file to the /etc/X11/xorg.conf.d/ directory and edit it to add the tapping option.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Quote:
Originally Posted by rlcosta14
It worked but another problem came up...
Once i restarted the DM:
systemctl restart gdm3
i can't seem to be able to enter, once i place my pw it does nothing... Did i screw up?
Hi rlcosta,
This is odd.
When you copied and edited 40-libinput.conf, did you simply add the tapping option to the touchpad block or did you make any other changes (ex. remove anything, change something else ...) ? I am reaching here - I wouldn't expect this type of mistake to negatively impact the functionality of your DM.
Did you make any other changes at the same time ?
If the above doesn't help, what I would do is disable the systemd service for gdm, boot into the console, completely remove gdm, reboot, reinstall gdm and retry manually starting it. Then try to log in via the DM and if it works again, re-enable the gdm service.
If this doesn't work, time to examine the logs for anything unusual ... If it comes to that, and you need guidance, let us know and either I or some of the other members should be able to help.
When you copied and edited 40-libinput.conf, did you simply add the tapping option to the touchpad block or did you make any other changes (ex. remove anything, change something else ...) ? I am reaching here - I wouldn't expect this type of mistake to negatively impact the functionality of your DM.
Did you make any other changes at the same time ?
If the above doesn't help, what I would do is disable the systemd service for gdm, boot into the console, completely remove gdm, reboot, reinstall gdm and retry manually starting it. Then try to log in via the DM and if it works again, re-enable the gdm service.
If this doesn't work, time to examine the logs for anything unusual ... If it comes to that, and you need guidance, let us know and either I or some of the other members should be able to help.
Let us know how you make out.
I really apreciate the help, what i've done is follow this tutorial:
when you remove gdm you will have no graphical display any more (just that console). So probably it is not what you want.
you can try to remove the file created (/etc/X11/xorg.conf.d/40-libinput.conf), probably that helps to restore the original configuration. But if you have modified other things ....
when you remove gdm you will have no graphical display any more (just that console). So probably it is not what you want.
you can try to remove the file created (/etc/X11/xorg.conf.d/40-libinput.conf), probably that helps to restore the original configuration. But if you have modified other things ....
So the systemctl restart gdm3 isn't the reason for it not be working, could be the file that i created?
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,364
Rep:
Hi again rlcosta14,
As mentioned in my above post, I would also suggest you begin by verifying that 40-libinput.conf file. What is important is that when you copied it into the /etc/X11/xorg.conf.d/ directory and edited it, you *added* the tapping option line but *did not change anything else*.
So first, compare the 2 files: /etc/X11/xorg.conf.d/40-libinput.conf and /usr/share/X11/xorg.conf.d/40-libinput.conf .... They should be identical except for that line you added. If not, as suggested above, delete the file you edited and start over.
You will only be able to create, edit or delete a file in the /etc directory tree with elevated privileges (it being a system directory). So use sudo. For example :
Code:
sudo rm /etc/X11/xorg.conf.d/40-libinput.conf
... See how your system behaves after rebooting. If you are still unable to login again with gdm, you can try the next level of troubleshooting (removing and reinstalling gdm).
As mentioned in my above post, I would also suggest you begin by verifying that 40-libinput.conf file. What is important is that when you copied it into the /etc/X11/xorg.conf.d/ directory and edited it, you *added* the tapping option line but *did not change anything else*.
So first, compare the 2 files: /etc/X11/xorg.conf.d/40-libinput.conf and /usr/share/X11/xorg.conf.d/40-libinput.conf .... They should be identical except for that line you added. If not, as suggested above, delete the file you edited and start over.
You will only be able to create, edit or delete a file in the /etc directory tree with elevated privileges (it being a system directory). So use sudo. For example :
Code:
sudo rm /etc/X11/xorg.conf.d/40-libinput.conf
... See how your system behaves after rebooting. If you are still unable to login again with gdm, you can try the next level of troubleshooting (removing and reinstalling gdm).
Let us know how things go !
Literally figured how what i was doing wrong...
Once i tried rm /etc/X11/xorg.conf.d/40-libinput.conf
and it didnt work i tried:
sudo rm/etc/X11/xorg.conf.d/40-libinput.conf
without the space between the rm and the file name -.-"
I'm now able to boot, its all good.
Still need to figure out how to enable tap-to-click though...
Excellent news - is your tapping option wirking as well ?
Just ran egrep -i 'synap|alps|etps|elan' /proc/bus/input/devices
found out i have a synaptics touchpad.
I'm using Gnome and was able to enable it.
It's all solved, i'll close the thread.
Thanks for all the help, from everyone.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.