Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-04 Thread pete nikolic
On Tue, 05 Aug 2014 05:52:15 +0200
sinclair  wrote:

> Did you try logging in as another user?
> 
> Sent from Samsung Mobile
> 
>  Original message 
> From: Peter Nikolic  
> Date: 04/08/2014  23:59  (GMT+02:00) 
> To: kde@mail.kde.org 
> Subject: Re: [kde] keyboard and mouse not working after upadte to latest
  xorg  server 
>  
> On Sun, 3 Aug 2014 07:48:29 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
> 
> > Peter Nikolic posted on Sat, 02 Aug 2014 21:25:03 +0100 as excerpted:
> > 
> > > Thanks for the reply i think it may be as you suggest a permissions
> > > problem but it is proving to be hell to sort out   every thing was
> > > fine untill i accepted the update to the latest Xorg server  then
> > > well
> > 
> > FWIW, latest xorg-server 1.16.0 here, recently upgraded (as it'd have
> > to be, because it only recently came out).  No problems to report,
> > but as I said, I do the text login, startx with a kde xsession
> > setting, thing here, and don't even have a *dm installed, so if there
> > were issues with it and *dm, I'd never know it.
> > 
> > But it does seem to me that your issue is likely related to logind 
> > console session dynamic permissions.  Obviously those logging into a
> > text login session and running startx from there have a login session
> > already going when they run startx, with console perms already set
> > for the existing login.  That contrasts significantly with the *dm
> > login case, where X is already running and at least basic input perms
> > would be necessary in ordered to be even to login graphically at all,
> > which seems to be your problem.  I just don't know how to fix it
> > since the little *dm experience I have is over a decade outdated now,
> > well before systemd's logind solution and indeed, before hal and the
> > like as well, so literally, generations of solutions have come and
> > gone since then. =:^\
> > 
> > 
> > > Ok  well i am going to be out all day tomorrow fishing
> > 
> > =:^)
> > 
> > > so will try to solve it monday evening and get back to you then .
> > 
> > 
> 
> Hi Duncan 
> 
> 
> Right had time to fiddle for a while now  ..
> 
> I can get KDE up using "xinit startkde"   all fine but still no
> keyboard or mouse  , so this seems it may be a kde based problem  have
> to install and try another desktop to test this out .
> 
> 
> 
> 
> PS if anyone else has any suggestions please pipe up  i am now getting
> desperate to get this machine back up and running  have neither the
> space or software on here to do what i need ..
> 
> 
> Pete  
> 

Hi .


Well some success now back on the afflicted machine but having to log in and 
start
KDE  using  "startx" and it seems to be behaving .

It would seem to be either KDM  or a systemd KDM  problem   and to be honest i 
cant
get my head round systemd yet  , Main thing is the machine is useable again  
and i
can get on and reduce the amount of GVH  (grievous verbal hassle) i am getting 
from
the club about an out of date web site ..


thanksPete ..
 

-- 
Please note: No trees were killed in the sending of this message. 
However a large number of electrons were terribly inconvenienced.
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-04 Thread sinclair
Did you try logging in as another user?

Sent from Samsung Mobile

 Original message 
From: Peter Nikolic  
Date: 04/08/2014  23:59  (GMT+02:00) 
To: kde@mail.kde.org 
Subject: Re: [kde] keyboard and mouse not working after upadte to latest
  xorg  server 
 
On Sun, 3 Aug 2014 07:48:29 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:

> Peter Nikolic posted on Sat, 02 Aug 2014 21:25:03 +0100 as excerpted:
> 
> > Thanks for the reply i think it may be as you suggest a permissions
> > problem but it is proving to be hell to sort out   every thing was
> > fine untill i accepted the update to the latest Xorg server  then
> > well
> 
> FWIW, latest xorg-server 1.16.0 here, recently upgraded (as it'd have
> to be, because it only recently came out).  No problems to report,
> but as I said, I do the text login, startx with a kde xsession
> setting, thing here, and don't even have a *dm installed, so if there
> were issues with it and *dm, I'd never know it.
> 
> But it does seem to me that your issue is likely related to logind 
> console session dynamic permissions.  Obviously those logging into a
> text login session and running startx from there have a login session
> already going when they run startx, with console perms already set
> for the existing login.  That contrasts significantly with the *dm
> login case, where X is already running and at least basic input perms
> would be necessary in ordered to be even to login graphically at all,
> which seems to be your problem.  I just don't know how to fix it
> since the little *dm experience I have is over a decade outdated now,
> well before systemd's logind solution and indeed, before hal and the
> like as well, so literally, generations of solutions have come and
> gone since then. =:^\
> 
> 
> > Ok  well i am going to be out all day tomorrow fishing
> 
> =:^)
> 
> > so will try to solve it monday evening and get back to you then .
> 
> 

Hi Duncan 


Right had time to fiddle for a while now  ..

I can get KDE up using "xinit startkde"   all fine but still no
keyboard or mouse  , so this seems it may be a kde based problem  have
to install and try another desktop to test this out .




PS if anyone else has any suggestions please pipe up  i am now getting
desperate to get this machine back up and running  have neither the
space or software on here to do what i need ..


Pete  

-- 
Linux voyager 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012
x86_64 GNU/Linux
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-04 Thread Peter Nikolic
On Sun, 3 Aug 2014 07:48:29 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:

> Peter Nikolic posted on Sat, 02 Aug 2014 21:25:03 +0100 as excerpted:
> 
> > Thanks for the reply i think it may be as you suggest a permissions
> > problem but it is proving to be hell to sort out   every thing was
> > fine untill i accepted the update to the latest Xorg server  then
> > well
> 
> FWIW, latest xorg-server 1.16.0 here, recently upgraded (as it'd have
> to be, because it only recently came out).  No problems to report,
> but as I said, I do the text login, startx with a kde xsession
> setting, thing here, and don't even have a *dm installed, so if there
> were issues with it and *dm, I'd never know it.
> 
> But it does seem to me that your issue is likely related to logind 
> console session dynamic permissions.  Obviously those logging into a
> text login session and running startx from there have a login session
> already going when they run startx, with console perms already set
> for the existing login.  That contrasts significantly with the *dm
> login case, where X is already running and at least basic input perms
> would be necessary in ordered to be even to login graphically at all,
> which seems to be your problem.  I just don't know how to fix it
> since the little *dm experience I have is over a decade outdated now,
> well before systemd's logind solution and indeed, before hal and the
> like as well, so literally, generations of solutions have come and
> gone since then. =:^\
> 
> 
> > Ok  well i am going to be out all day tomorrow fishing
> 
> =:^)
> 
> > so will try to solve it monday evening and get back to you then .
> 
> 

Hi Duncan 


Right had time to fiddle for a while now  ..

I can get KDE up using "xinit startkde"   all fine but still no
keyboard or mouse  , so this seems it may be a kde based problem  have
to install and try another desktop to test this out .




PS if anyone else has any suggestions please pipe up  i am now getting
desperate to get this machine back up and running  have neither the
space or software on here to do what i need ..


Pete  

-- 
Linux voyager 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012
x86_64 GNU/Linux
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-03 Thread Duncan
Peter Nikolic posted on Sat, 02 Aug 2014 21:25:03 +0100 as excerpted:

> Thanks for the reply i think it may be as you suggest a permissions
> problem but it is proving to be hell to sort out   every thing was fine
> untill i accepted the update to the latest Xorg server  then  well

FWIW, latest xorg-server 1.16.0 here, recently upgraded (as it'd have to 
be, because it only recently came out).  No problems to report, but as I 
said, I do the text login, startx with a kde xsession setting, thing 
here, and don't even have a *dm installed, so if there were issues with 
it and *dm, I'd never know it.

But it does seem to me that your issue is likely related to logind 
console session dynamic permissions.  Obviously those logging into a text 
login session and running startx from there have a login session already 
going when they run startx, with console perms already set for the 
existing login.  That contrasts significantly with the *dm login case, 
where X is already running and at least basic input perms would be 
necessary in ordered to be even to login graphically at all, which seems 
to be your problem.  I just don't know how to fix it since the little *dm 
experience I have is over a decade outdated now, well before systemd's 
logind solution and indeed, before hal and the like as well, so 
literally, generations of solutions have come and gone since then. =:^\


> Ok  well i am going to be out all day tomorrow fishing

=:^)

> so will try to solve it monday evening and get back to you then .


-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-02 Thread Peter Nikolic
On Sat, 2 Aug 2014 06:47:22 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:

> Peter Nikolic posted on Fri, 01 Aug 2014 23:05:58 +0100 as excerpted:
> 
> > Iam running Arch Linux on my main PC fully updated including the
> > latest xorg server  stuff  , If i run startx i can use the terminal
> > windows start programes  as root.
> > 
> > If i run kdm to use kde i get the login screen /greeter but have no
> > mouse or keyboard .
> > I have so far tried every thing i can find to attempt to solve this
> > without sucess .
> > 
> > Could use a little help and or suggestions as to where to look next
> 
> FWIW, here I use startx to start kde directly from a text login, no
> *dm installed at all, nor have I used a *dm graphical login since
> before I switched to gentoo in 2004, so there's a definite limit to
> my knowledge in that area.  In fact, I quit using *dm logins back on
> Mandrake in probably 2002 or so, precisely because the one I was
> using broke, while a text login and simply running startx from there
> "just worked".  My impression then and now is thus that a *dm login
> requires that more software machinery be configured and in working
> order, and that it's consequently more delicate and prone to breakage
> than the relatively more robust simple text login and startx as a
> normal user, with an xsession set as appropriate (to kde in this
> context).
> 
> Anyway, some questions/observations can be made:
> 
> You tried kdm, and you tried startx as root, but there's no
> indication you tried startx as a normal user (which is the way I
> launch X, with kde set as the xsession, here).  What happens if you
> do that?
> 
> That kdm isn't giving you mouse/keyboard in X while logging in as
> root and running startx gives you working mouse/keyboard points at a 
> permissions issue, possibly related to systemd's logind configuration
> -- nobody logged in so it's not setting permissions appropriately to
> allow X- based input activation, to /get/ that login.  While what
> little *dm stuff I know is long outdated (long /long/ before
> systemd's logind, for instance, which certainly changed the rules in
> that area quite a bit), checking whether a text login as a normal
> user and startx from there gives you working input, would test
> another variant on the problem, giving people more information to
> troubleshoot with.
> 
> You can also try a text login, and then switch back to kdm and see if
> it is suddenly working.  If that works, it's definitely
> dynamic-permissions related based on login.
> 
> 
> Meanwhile, if you'd like startx to run kde instead of a generic
> session (as I do here on gentoo, but with a slightly different
> technique than suggested in the link below), since you're on arch,
> I'll refer you to the arch wiki:
> 
> https://wiki.archlinux.org/index.php/Xinitrc
> 
> With that you may find, as I did, that ultimately you don't need a
> *dm graphical login any longer.  Simply do a normal text login, and
> if you want to startx, just run startx as you would a normal
> command.  If not, don't. =:^)
> 
> ...  Tho even if you don't use kdm for graphical login, if you need a 
> screen-locker you'll still need to keep it installed as it provides
> the greeter for kde's screenlocker, without which you won't get a
> login prompt after locking the screen, and you'll have to kill X
> (using magic- srq K or from a different VT) and run startx again if
> you activate the screenlocker.  FWIW, I don't need that screenlocker
> functionality as I'm the only user on my home computer and I
> deliberately keep private info off my netbook, so I just disable the
> screenlocker and use startx to start kde, and don't need to have kdm
> installed at all.
> 

Hi Duncan   

Thanks for the reply i think it may be as you suggest a permissions
problem but it is proving to be hell to sort out   every thing was fine
untill i accepted the update to the latest Xorg server  then  well 


Ok  well i am going to be out all day tomorrow fishing so will try to
solve it monday evening and get back to you then .


Thanks Pete ..


-- 
Linux voyager 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012
x86_64 GNU/Linux
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


Re: [kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-01 Thread Duncan
Peter Nikolic posted on Fri, 01 Aug 2014 23:05:58 +0100 as excerpted:

> Iam running Arch Linux on my main PC fully updated including the latest
> xorg server  stuff  , If i run startx i can use the terminal windows
> start programes  as root.
> 
> If i run kdm to use kde i get the login screen /greeter but have no
> mouse or keyboard .
> I have so far tried every thing i can find to attempt to solve this
> without sucess .
> 
> Could use a little help and or suggestions as to where to look next

FWIW, here I use startx to start kde directly from a text login, no *dm 
installed at all, nor have I used a *dm graphical login since before I 
switched to gentoo in 2004, so there's a definite limit to my knowledge 
in that area.  In fact, I quit using *dm logins back on Mandrake in 
probably 2002 or so, precisely because the one I was using broke, while a 
text login and simply running startx from there "just worked".  My 
impression then and now is thus that a *dm login requires that more 
software machinery be configured and in working order, and that it's 
consequently more delicate and prone to breakage than the relatively more 
robust simple text login and startx as a normal user, with an xsession 
set as appropriate (to kde in this context).

Anyway, some questions/observations can be made:

You tried kdm, and you tried startx as root, but there's no indication 
you tried startx as a normal user (which is the way I launch X, with kde 
set as the xsession, here).  What happens if you do that?

That kdm isn't giving you mouse/keyboard in X while logging in as root 
and running startx gives you working mouse/keyboard points at a 
permissions issue, possibly related to systemd's logind configuration -- 
nobody logged in so it's not setting permissions appropriately to allow X-
based input activation, to /get/ that login.  While what little *dm stuff 
I know is long outdated (long /long/ before systemd's logind, for 
instance, which certainly changed the rules in that area quite a bit), 
checking whether a text login as a normal user and startx from there 
gives you working input, would test another variant on the problem, 
giving people more information to troubleshoot with.

You can also try a text login, and then switch back to kdm and see if it 
is suddenly working.  If that works, it's definitely dynamic-permissions 
related based on login.


Meanwhile, if you'd like startx to run kde instead of a generic session 
(as I do here on gentoo, but with a slightly different technique than 
suggested in the link below), since you're on arch, I'll refer you to the 
arch wiki:

https://wiki.archlinux.org/index.php/Xinitrc

With that you may find, as I did, that ultimately you don't need a *dm 
graphical login any longer.  Simply do a normal text login, and if you 
want to startx, just run startx as you would a normal command.  If not, 
don't. =:^)

...  Tho even if you don't use kdm for graphical login, if you need a 
screen-locker you'll still need to keep it installed as it provides the 
greeter for kde's screenlocker, without which you won't get a login 
prompt after locking the screen, and you'll have to kill X (using magic-
srq K or from a different VT) and run startx again if you activate the 
screenlocker.  FWIW, I don't need that screenlocker functionality as I'm 
the only user on my home computer and I deliberately keep private info 
off my netbook, so I just disable the screenlocker and use startx to 
start kde, and don't need to have kdm installed at all.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


[kde] keyboard and mouse not working after upadte to latest xorg server

2014-08-01 Thread Peter Nikolic

Hi 
Iam running Arch Linux on my main PC fully updated including the latest
xorg server  stuff  , If i run startx i can use the terminal windows
start programes  as root.

If i run kdm to use kde i get the login screen /greeter but have no
mouse or keyboard . 
I have so far tried every thing i can find to attempt to solve this
without sucess .

Could use a little help and or suggestions as to where to look next  


Thanks Pete ..

-- 
Linux voyager 3.6.2-1-ARCH #1 SMP PREEMPT Fri Oct 12 23:58:58 CEST 2012
x86_64 GNU/Linux
___
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.