Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
startx borked
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
dufeu
l33t
l33t


Joined: 30 Aug 2002
Posts: 896
Location: US-FL-EST

PostPosted: Mon Jan 08, 2018 5:11 pm    Post subject: startx borked Reply with quote

I always start with a CLI login. Once I've logged on, I execute:
Code:
XSESSION=startkt{kde|lxqt|xfce4} startx
to bring up the desired desktop on any given account.

Recently, my main workstation has been failing with several different messages depending on the status of /dev/tty* and /dev/pts/.

I finished the migration from profile 13.0 to profile 17.0 for all three of my computers with weekend. I had hoped that recompilation of all packages witould magically fix the graphical startup on my workstation. Unfortunately - no joy.

The problem appears to be that whatever process it is that updates the ownership of /dev/tty* and creates the needed /dev/pts entries is not working properly on my workstation. I've compared these directories/files with my NAS where everything is working correctly.

What I've done so far:
  1. Compared /etc/group
    Code:
    pyrogyro ~ # grep -E 'input|video|tty' /etc/group | sort
    input:x:995:
    tty:x:5:
    video:x:27:root,guynonet,sddm
    Code:
    blaze ~ # grep -E 'input|video|tty' /etc/group | sort
    input:x:97:
    tty:x:5:
    video:x:27:root,guynonet,sddm

    Note: 'sddm' was missing from 'video' in pyrogyro. Adding it resulted in some /dev/pts entries being created.
  2. Compared /dev/pts
    Code:
    pyrogyro ~ # ls -l /dev/p*
    crw-r----- 1 root kmem   1, 4 Jan  7 22:22 /dev/port
    crw------- 1 root root 108, 0 Jan  7 17:22 /dev/ppp
    crw-rw-rw- 1 root tty    5, 2 Jan  8 11:25 /dev/ptmx

    /dev/pts:
    total 0
    crw------- 1 guynonet tty  136, 0 Jan  8 11:25 0                                   
    crw------- 1 guynonet tty  136, 1 Jan  8 11:24 1                                   
    c--------- 1 root     root   5, 2 Jan  7 17:22 ptmx
    Code:
    blaze ~ # ls -l /dev/p*
    crw-r----- 1 root kmem   1, 4 Jan  6 03:56 /dev/port
    crw-rw-rw- 1 root tty    5, 2 Jan  8 11:28 /dev/ptmx
    crw------- 1 root root 251, 0 Jan  6 03:56 /dev/ptp0
    crw------- 1 root root 251, 1 Jan  6 03:56 /dev/ptp1

    /dev/pts:
    total 0
    crw--w---- 1 root     tty  136, 0 Jan  6 05:21 0
    crw--w---- 1 guynonet tty  136, 1 Jan  8 06:36 1
    crw--w---- 1 root     tty  136, 2 Jan  8 06:35 2
    crw--w---- 1 root     tty  136, 3 Jan  8 06:35 3
    crw--w---- 1 root     tty  136, 4 Jan  8 06:35 4
    crw--w---- 1 guynonet tty  136, 5 Jan  8 11:28 5
    crw--w---- 1 guynonet tty  136, 6 Jan  8 07:19 6
    crw--w---- 1 guynonet tty  136, 7 Jan  8 07:19 7
    crw--w---- 1 guynonet tty  136, 8 Jan  8 07:19 8
    c--------- 1 root     root   5, 2 Jan  6 03:56 ptmx

    Note: pyrogyro and blaze both have CLI logins on F1, F2, F3 and F4. pyrogyro has graphical session running on F7. blaze has a graphical session for both 'root' and 'guynonet' running on F7an and F8 respectively. I would have expected entries in pyrogyro to look a lot more like entries in blaze.
  3. Compared /dev/tty*blaze ~ # ls -l /dev/tty*
    Code:
    pyrogyro ~ # ls -l /dev/tty*                                                                 
    crw-rw-rw- 1 root     tty      5,  0 Jan  7 23:20 /dev/tty                                           
    crw--w---- 1 root     tty      4,  0 Jan  7 22:22 /dev/tty0                                         
    crw------- 1 root     root     4,  1 Jan  8 07:23 /dev/tty1                                           
    crw--w---- 1 root     tty      4, 10 Jan  7 22:23 /dev/tty10                                         
    crw--w---- 1 root     tty      4, 11 Jan  7 22:23 /dev/tty11                                             
    crw--w---- 1 root     tty      4, 12 Jan  8 11:45 /dev/tty12
    crw------- 1 root     root     4,  2 Jan  8 07:24 /dev/tty2
    crw------- 1 guynonet guynonet 4,  3 Jan  8 06:32 /dev/tty3
    crw------- 1 root     root     4,  4 Jan  8 06:33 /dev/tty4
    crw------- 1 guynonet guynonet 4,  5 Jan  8 06:58 /dev/tty5
    crw--w---- 1 root     tty      4,  6 Jan  7 22:23 /dev/tty6
    crw--w---- 1 root     root     4,  7 Jan  7 22:23 /dev/tty7
    crw--w---- 1 root     tty      4,  8 Jan  7 22:23 /dev/tty8
    crw--w---- 1 root     tty      4,  9 Jan  7 22:23 /dev/tty9
    Code:
    crw-rw-rw- 1 root     tty 5,  0 Jan  6 08:55 /dev/tty
    crw--w---- 1 root     tty 4,  0 Jan  6 03:56 /dev/tty0
    crw------- 1 root     tty 4,  1 Jan  8 06:35 /dev/tty1
    crw--w---- 1 root     tty 4, 10 Jan  6 04:00 /dev/tty10
    crw--w---- 1 root     tty 4, 11 Jan  6 04:00 /dev/tty11
    crw--w---- 1 root     tty 4, 12 Jan  8 11:43 /dev/tty12
    crw------- 1 root     tty 4,  2 Jan  6 06:24 /dev/tty2
    crw------- 1 root     tty 4,  3 Jan  6 06:00 /dev/tty3
    crw------- 1 guynonet tty 4,  4 Jan  8 07:19 /dev/tty4
    crw--w---- 1 root     tty 4,  5 Jan  6 04:00 /dev/tty5
    crw--w---- 1 root     tty 4,  6 Jan  6 04:00 /dev/tty6
    crw--w---- 1 root     tty 4,  7 Jan  6 04:00 /dev/tty7
    crw--w---- 1 root     tty 4,  8 Jan  6 04:00 /dev/tty8
    crw--w---- 1 root     tty 4,  9 Jan  6 04:00 /dev/tty9

    Note: I manually changed ownership on some of the pyrogyro entries in an attempt to bypass initial permissions problems with X11.

The workstation is names 'pyrogyro' and the NAS is 'blaze'.

The current message of interest from the the x log is:
Code:
(EE) AddScreen/ScreenInit failed for driver 0


Adding 'sddm' to 'video' in /etc/group and manually changing the ownership of the /dev/tty7 and up permitted me to get to the above message. But I'd really like to fix this properly. Advice would be much appreciated.
_________________
People whom think M$ is mediocre, don't know the half of it.
Back to top
View user's profile Send private message
bec
Apprentice
Apprentice


Joined: 30 Sep 2004
Posts: 216
Location: Cali - Colombia

PostPosted: Fri Jan 19, 2018 4:42 pm    Post subject: Reply with quote

Code:
cat ~/.xinitrc

exec ck-launch-session dbus-launch --sh-syntax --exit-with-session openbox-session


I am using the above to start obenbox, assuming you are running the consolekit daemon
_________________
abe
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum