error loading /etc/profile (xinput property doesn't exist)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












After upgrading from Xenial to Bionic, I now receive errors when logging into my desktop:



Error found when loading /etc/profile
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format


I believe the culprit are the following lines I put both in .profile and .xinputrc to configure my touchpad:



xinput set-prop 11 298 1
xinput set-prop 11 299 1, 100
xinput set-prop 11 300 20.0 50000.0


However, if I do source .profile, then there's absolutely no problem, and my xinput settings are set correctly. It seems to only occur when these scripts are executed by /etc/profile. Has xinput not initialised my touchpad yet at that stage? And how can I prevent this?







share|improve this question




















  • Did you put the same lines in /etc/profile too ?
    – Soren A
    May 15 at 14:09











  • no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
    – bluppfisk
    May 15 at 14:11














up vote
0
down vote

favorite












After upgrading from Xenial to Bionic, I now receive errors when logging into my desktop:



Error found when loading /etc/profile
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format


I believe the culprit are the following lines I put both in .profile and .xinputrc to configure my touchpad:



xinput set-prop 11 298 1
xinput set-prop 11 299 1, 100
xinput set-prop 11 300 20.0 50000.0


However, if I do source .profile, then there's absolutely no problem, and my xinput settings are set correctly. It seems to only occur when these scripts are executed by /etc/profile. Has xinput not initialised my touchpad yet at that stage? And how can I prevent this?







share|improve this question




















  • Did you put the same lines in /etc/profile too ?
    – Soren A
    May 15 at 14:09











  • no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
    – bluppfisk
    May 15 at 14:11












up vote
0
down vote

favorite









up vote
0
down vote

favorite











After upgrading from Xenial to Bionic, I now receive errors when logging into my desktop:



Error found when loading /etc/profile
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format


I believe the culprit are the following lines I put both in .profile and .xinputrc to configure my touchpad:



xinput set-prop 11 298 1
xinput set-prop 11 299 1, 100
xinput set-prop 11 300 20.0 50000.0


However, if I do source .profile, then there's absolutely no problem, and my xinput settings are set correctly. It seems to only occur when these scripts are executed by /etc/profile. Has xinput not initialised my touchpad yet at that stage? And how can I prevent this?







share|improve this question












After upgrading from Xenial to Bionic, I now receive errors when logging into my desktop:



Error found when loading /etc/profile
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format
Property 300 doesn't exist, you must specify its type and format
Property 299 doesn't exist, you must specify its type and format
Property 298 doesn't exist, you must specify its type and format


I believe the culprit are the following lines I put both in .profile and .xinputrc to configure my touchpad:



xinput set-prop 11 298 1
xinput set-prop 11 299 1, 100
xinput set-prop 11 300 20.0 50000.0


However, if I do source .profile, then there's absolutely no problem, and my xinput settings are set correctly. It seems to only occur when these scripts are executed by /etc/profile. Has xinput not initialised my touchpad yet at that stage? And how can I prevent this?









share|improve this question











share|improve this question




share|improve this question










asked May 15 at 13:38









bluppfisk

1268




1268











  • Did you put the same lines in /etc/profile too ?
    – Soren A
    May 15 at 14:09











  • no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
    – bluppfisk
    May 15 at 14:11
















  • Did you put the same lines in /etc/profile too ?
    – Soren A
    May 15 at 14:09











  • no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
    – bluppfisk
    May 15 at 14:11















Did you put the same lines in /etc/profile too ?
– Soren A
May 15 at 14:09





Did you put the same lines in /etc/profile too ?
– Soren A
May 15 at 14:09













no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
– bluppfisk
May 15 at 14:11




no; only in ~/.profile and ~/.xinputrc - I assume those are in turn loaded by /etc/profile ?
– bluppfisk
May 15 at 14:11















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036539%2ferror-loading-etc-profile-xinput-property-doesnt-exist%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036539%2ferror-loading-etc-profile-xinput-property-doesnt-exist%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491