Arch Linux

jameh0

Member

Registered: 2013-04-06

Posts: 40

Broken logind session after X has started

When I boot to tty1 and log in, my session is active:

loginctl show-session $XDG_SESSION_ID --property=Active
Active=Yes

When I startx, my window manager is started and I have some systemd user services start, but once I am in my window manager, the session is broken:

loginctl show-session $XDG_SESSION_ID

EnableWallMessages=no
NAutoVTs=6
KillUserProcesses=no
RebootToFirmwareSetup=no
RebootToBootLoaderMenu=18446744073709551615
IdleHint=no
IdleSinceHint=1589314688265786
IdleSinceHintMonotonic=31121357
DelayInhibited=sleep
InhibitDelayMaxUSec=5s
UserStopDelayUSec=10s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=ignore
HoldoffTimeoutUSec=30s
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no
Docked=yes
LidClosed=no
OnExternalPower=yes
RemoveIPC=yes
RuntimeDirectorySize=1667846144
InhibitorsMax=8192
NCurrentInhibitors=2
SessionsMax=8192
NCurrentSessions=1

and I can't reboot, shutdown, suspend as my user.

journalctl --user -b 0:

-- Logs begin at Sun 2020-02-02 21:09:18 PST, end at Tue 2020-05-12 13:18:25 PDT. --
May 12 13:18:04 viper systemd[5758]: Reached target Paths.
May 12 13:18:04 viper systemd[5758]: Reached target Timers.
May 12 13:18:04 viper systemd[5758]: Starting D-Bus User Message Bus Socket.
May 12 13:18:04 viper systemd[5758]: Listening on GnuPG network certificate management daemon.
May 12 13:18:04 viper systemd[5758]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
May 12 13:18:04 viper systemd[5758]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
May 12 13:18:04 viper systemd[5758]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
May 12 13:18:04 viper systemd[5758]: Listening on GnuPG cryptographic agent and passphrase cache.
May 12 13:18:04 viper systemd[5758]: Listening on p11-kit server.
May 12 13:18:04 viper systemd[5758]: Listening on Multimedia System.
May 12 13:18:04 viper systemd[5758]: Listening on Sound System.
May 12 13:18:04 viper systemd[5758]: Listening on D-Bus User Message Bus Socket.
May 12 13:18:04 viper systemd[5758]: Reached target Sockets.
May 12 13:18:04 viper systemd[5758]: Reached target Basic System.
May 12 13:18:04 viper systemd[5758]: Started Syncthing - Open Source Continuous File Synchronization.
May 12 13:18:04 viper systemd[5758]: Starting tmux default session (detached)...
May 12 13:18:04 viper systemd[5758]: Starting Update XDG user dir configuration...
May 12 13:18:04 viper systemd[5758]: xdg-user-dirs-update.service: Succeeded.
May 12 13:18:04 viper systemd[5758]: Finished Update XDG user dir configuration.
May 12 13:18:04 viper systemd[5758]: Started tmux default session (detached).
May 12 13:18:04 viper systemd[5758]: Reached target Main User Target.
May 12 13:18:04 viper systemd[5758]: Startup finished in 185ms.
May 12 13:18:04 viper syncthing[5767]: [start] INFO: syncthing v1.5.0 "Fermium Flea" (go1.14.2 linux-amd64) builduser@svetlemodry 2020-05-09 10:38:56 UTC
May 12 13:18:04 viper syncthing[5767]: [GQOTN] INFO: My ID: GQOTNYO-A3FGW7B-HFCN7KL-4BNWIIT-G42T6VR-OU4ZA5H-QEOMW74-JLO42QX
May 12 13:18:05 viper systemd[5758]: Reloading.
May 12 13:18:05 viper syncthing[5767]: [GQOTN] INFO: Single thread SHA256 performance is 429 MB/s using minio/sha256-simd (362 MB/s using crypto/sha256).
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Hashing performance is 360.59 MB/s
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Overall send rate is unlimited, receive rate is unlimited
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "music" (hojfp-ekkjt) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: TCP listener ([::]:22000) starting
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: QUIC listener ([::]:22000) starting
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "camera-pixel3a" (o57yd-kowm1) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "code" (oqj6s-xmcie) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "org" (q3zkt-xv7iq) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "ideas" (tfems-uurgr) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "courses" (wltos-qwavz) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "docs" (xqiom-srwli) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Ready to synchronize "pics" (z3rqi-xl6nm) (sendreceive)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "ideas" (tfems-uurgr)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "courses" (wltos-qwavz)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "org" (q3zkt-xv7iq)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: GUI and API listening on 127.0.0.1:8384
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: My name is "viper"
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Device DVU3I23-NOSHMTQ-XUOHXNE-KKD5JGW-TGED5VU-JYSQ6B6-D2P5O3B-7SWX4AK is "pixel3a" at [dynamic]
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "code" (oqj6s-xmcie)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "docs" (xqiom-srwli)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "pics" (z3rqi-xl6nm)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "camera-pixel3a" (o57yd-kowm1)
May 12 13:18:06 viper syncthing[5767]: [GQOTN] INFO: Completed initial scan of sendreceive folder "music" (hojfp-ekkjt)
May 12 13:18:07 viper syncthing[5767]: [GQOTN] INFO: Established secure connection to DVU3I23-NOSHMTQ-XUOHXNE-KKD5JGW-TGED5VU-JYSQ6B6-D2P5O3B-7SWX4AK at 192.168.1.19:52206-192.168.1.48:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
May 12 13:18:07 viper syncthing[5767]: [GQOTN] INFO: Device DVU3I23-NOSHMTQ-XUOHXNE-KKD5JGW-TGED5VU-JYSQ6B6-D2P5O3B-7SWX4AK client is "syncthing v1.3.4" named "Pixel 3a" at 192.168.1.19:52206-192.168.1.48:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256
May 12 13:18:15 viper systemd[5758]: Started D-Bus User Message Bus.
May 12 13:18:16 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=1000 pid=7294 comm="/usr/bin/python /usr/bin/udiskie ")
May 12 13:18:16 viper systemd[5758]: Starting Virtual filesystem service...
May 12 13:18:16 viper systemd[5758]: Created slice polybar.slice.
May 12 13:18:16 viper systemd[5758]: Started Xorg compositor.
May 12 13:18:16 viper systemd[5758]: Started Automatic desktop naming for bspwm.
May 12 13:18:16 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Successfully activated service 'org.gtk.vfs.Daemon'
May 12 13:18:16 viper systemd[5758]: Starting XDG autostart...
May 12 13:18:16 viper systemd[5758]: Started Restore background.
May 12 13:18:16 viper systemd[5758]: Started Keep KRK monitors live.
May 12 13:18:16 viper systemd[5758]: Started X11 status bar on monitor HDMI1.
May 12 13:18:16 viper systemd[5758]: Started Simple X Hotkey Daemon.
May 12 13:18:16 viper systemd[5758]: Started Hide cursor when key is pressed.
May 12 13:18:16 viper systemd[5758]: Started Virtual filesystem service.
May 12 13:18:16 viper systemd[5758]: Started X11 status bar on monitor eDP1.
May 12 13:18:16 viper krk-stay-awake.sh[7354]: Cannot connect to server socket err = No such file or directory
May 12 13:18:16 viper krk-stay-awake.sh[7354]: Cannot connect to server request channel
May 12 13:18:16 viper krk-stay-awake.sh[7354]: jack server is not running or cannot be started
May 12 13:18:16 viper krk-stay-awake.sh[7354]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 12 13:18:16 viper krk-stay-awake.sh[7354]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
May 12 13:18:16 viper krk-stay-awake.sh[7354]: aplay: main:830: audio open error: No such file or directory
May 12 13:18:16 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.5' (uid=1000 pid=7294 comm="/usr/bin/python /usr/bin/udiskie ")
May 12 13:18:16 viper systemd[5758]: Starting Accessibility services bus...
May 12 13:18:16 viper systemd[5758]: Finished XDG autostart.
May 12 13:18:16 viper systemd[5758]: Reached target Window manager has started.
May 12 13:18:16 viper systemd[5758]: Starting Sound Service...
May 12 13:18:16 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Successfully activated service 'org.a11y.Bus'
May 12 13:18:16 viper systemd[5758]: Started Accessibility services bus.
May 12 13:18:16 viper at-spi-bus-launcher[7397]: dbus-daemon[7397]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=7294 comm="/usr/bin/python /usr/bin/udiskie ")
May 12 13:18:16 viper at-spi-bus-launcher[7397]: dbus-daemon[7397]: Successfully activated service 'org.a11y.atspi.Registry'
May 12 13:18:16 viper at-spi-bus-launcher[7415]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
May 12 13:18:16 viper dex[7378]: Config already loaded
May 12 13:18:16 viper dex[7378]: mobile
May 12 13:18:16 viper dex[7378]: docked (detected) (current)
May 12 13:18:16 viper systemd[5758]: fehbg.service: Succeeded.
May 12 13:18:16 viper dex[7379]: blueman-applet 13.18.16 WARNING  PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
May 12 13:18:16 viper dex[7379]: blueman-applet 13.18.16 WARNING  PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority
May 12 13:18:16 viper pulseaudio[7393]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
May 12 13:18:16 viper pulseaudio[7393]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="3" name="usb-M-Audio_USB_Keystation_88es-00" card_name="alsa_card.usb-M-Audio_USB_Keystation_88es-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
May 12 13:18:16 viper pulseaudio[7393]: E: [pulseaudio] module-alsa-card.c: Failed to find a working profile.
May 12 13:18:16 viper pulseaudio[7393]: E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="2" name="usb-Akai_MPD218_NO_SERIAL_NUMBER-00" card_name="alsa_card.usb-Akai_MPD218_NO_SERIAL_NUMBER-00" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed.
May 12 13:18:16 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Activating via systemd: service name='org.blueman.Applet' unit='blueman-applet.service' requested by ':1.11' (uid=1000 pid=7441 comm="/usr/bin/python /usr/bin/blueman-tray ")
May 12 13:18:16 viper systemd[5758]: Starting Bluetooth management applet...
May 12 13:18:17 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Successfully activated service 'org.blueman.Applet'
May 12 13:18:17 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.9' (uid=1000 pid=7379 comm="/usr/bin/python /usr/bin/blueman-applet ")
May 12 13:18:17 viper systemd[5758]: Started Bluetooth management applet.
May 12 13:18:17 viper systemd[5758]: Starting Bluetooth OBEX service...
May 12 13:18:17 viper obexd[7454]: OBEX daemon 5.54
May 12 13:18:17 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Successfully activated service 'org.bluez.obex'
May 12 13:18:17 viper systemd[5758]: Started Bluetooth OBEX service.
May 12 13:18:17 viper blueman-applet[7448]: blueman-applet version 2.1.2 starting
May 12 13:18:17 viper blueman-applet[7448]: There is an instance already running
May 12 13:18:17 viper systemd[5758]: blueman-applet.service: Succeeded.
May 12 13:18:17 viper systemd[5758]: Started Sound Service.
May 12 13:18:17 viper polybar[7359]: polybar|warn:  pulseaudio: using default sink alsa_output.usb-Focusrite_Scarlett_2i2_USB-00.analog-stereo
May 12 13:18:17 viper polybar[7349]: polybar|warn:  pulseaudio: using default sink alsa_output.usb-Focusrite_Scarlett_2i2_USB-00.analog-stereo
May 12 13:18:17 viper polybar[7349]: polybar|warn:  Systray selection already managed (window=0x1600005)
May 12 13:18:17 viper polybar[7359]: polybar|error: Failed to reconfigure tray client, removing... (XCB_WINDOW (3))
May 12 13:18:17 viper syncthing[5767]: [GQOTN] INFO: New NAT port mapping: external TCP address 107.190.20.106:57318 to local address 0.0.0.0:22000.
May 12 13:18:17 viper syncthing[5767]: [GQOTN] INFO: Detected 1 NAT service
May 12 13:18:17 viper blueman-tray[7453]: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
May 12 13:18:19 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Activating via systemd: service name='org.freedesktop.Notifications' unit='dunst.service' requested by ':1.2' (uid=1000 pid=7294 comm="/usr/bin/python /usr/bin/udiskie ")
May 12 13:18:19 viper systemd[5758]: Starting Dunst notification daemon...
May 12 13:18:19 viper systemd[5758]: Started Restore background.
May 12 13:18:19 viper dbus-daemon[7291]: [session uid=1000 pid=7291] Successfully activated service 'org.freedesktop.Notifications'
May 12 13:18:19 viper systemd[5758]: Started Dunst notification daemon.
May 12 13:18:19 viper dunst[7586]: WARNING: No icon found in path: 'drive-removable-media'
May 12 13:18:19 viper dunst[7586]: WARNING: No icon found in path: 'drive-removable-media'
May 12 13:18:19 viper systemd[5758]: fehbg.service: Succeeded.
May 12 13:18:19 viper desknamer[7361]: trigger: node_add 0x00800002 0x00800007 0x00000000 0x02000002
May 12 13:18:19 viper desknamer[7361]:  ├ Renaming Desktop ID: 0x00800007
May 12 13:18:19 viper desknamer[7361]:  ├─ Current Desktop Name: 1 
May 12 13:18:19 viper desknamer[7361]:  ├─ Desktop Index: 1
May 12 13:18:19 viper desknamer[7361]:  ├─ Unique Process Names: Alacritty alacritty client tmux:
May 12 13:18:19 viper desknamer[7361]:  ├─ Unique Categories: System TerminalEmulator
May 12 13:18:19 viper desknamer[7361]:  └─ New Name:  
May 12 13:18:25 viper syncthing[5767]: [GQOTN] INFO: quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
May 12 13:18:25 viper syncthing[5767]: [GQOTN] INFO: quic://0.0.0.0:22000 resolved external address quic://107.190.20.106:1024 (via stun.syncthing.net:3478)

loginctl show-user jamie

UID=1000
GID=998
Name=jamie
Timestamp=Tue 2020-05-12 13:18:04 PDT
TimestampMonotonic=27431923
RuntimePath=/run/user/1000
Service=user@1000.service
Slice=user-1000.slice
Display=1
State=active
Sessions=1
IdleHint=no
IdleSinceHint=1589314688265786
IdleSinceHintMonotonic=31121358
Linger=no

xinitrc:

#!/bin/sh

userresources="$XDG_CONFIG_HOME/X11/Xresources"
usermodmap="$XDG_CONFIG_HOME/X11/Xmodmap"
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

xcape -e "Hyper_R=Tab"

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

xset s off
xset -dpms

udiskie &
/usr/bin/bspwm -c "$XDG_CONFIG_HOME/bspwm/bspwmrc"
systemctl --user stop wm.target

bspwmrc:

#!/bin/sh

bspc config remove_unplugged_monitors true
bspc config remove_disabled_monitors true

$XDG_CONFIG_HOME/bspwm/monitor.sh
$XDG_CONFIG_HOME/bspwm/keyboard.sh

bspc config pointer_modifier mod1
bspc config focus_follows_pointer true

bspc config border_width         3
bspc config window_gap          20

bspc config split_ratio          0.50
bspc config borderless_monocle   true
bspc config gapless_monocle      true

bspc rule -a "Chromium" desktop='focused:^2'
bspc rule -a "mpv" state=floating
bspc rule -a "Show-splash-gtk" desktop='focused:^7' state=floating
bspc rule -a "Bitwig Studio" desktop='focused:^7'
bspc rule -a "Spotify" desktop='focused:^5'
bspc rule -a "Steam" desktop='focused:^4'
bspc rule -a '*' center=true
#bspc rule -a "*:scratchpad" state=floating

xsetroot -cursor_name left_ptr &

if ! systemctl --user status wm.target; then
    systemctl --user restart wm.target
fi

https://wiki.archlinux.org/index.php/Ge … ermissions

The Arch wiki says to make sure that X runs on the same tty that login occurs at, which I do.

Any ideas would be appreciated.

---

Life is very short, and there's no time for fussing and fighting, my friends.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,697

Re: Broken logind session after X has started

The Arch wiki says to make sure that X runs on the same tty that login occurs at, which I do.

Do you?
See https://wiki.archlinux.org/index.php/Xinit#xserverrc and check "loginctl session-status"

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jameh0

Member

Registered: 2013-04-06

Posts: 40

Re: Broken logind session after X has started

loginctl session-status

loginctl session-status
1 - jamie (1000)
           Since: Tue 2020-05-12 13:18:04 PDT; 1h 20min ago
          Leader: 5015 (login)
            Seat: seat0; vc1
             TTY: tty1
         Service: login; type tty; class user
           State: active
            Unit: session-1.scope
                  ├─ 5015 login -- jamie
                  ├─ 5770 -zsh
                  ├─ 6345 -zsh
                  ├─20264 /bin/sh /usr/bin/startx /home/jamie/.config/X11/xinitrc
                  ├─20286 xinit /home/jamie/.config/X11/xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -keeptty -auth /tmp/serverauth.5DK0SUbnf2
                  ├─20287 /usr/lib/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.5DK0SUbnf2
                  ├─20313 /bin/sh /home/jamie/.config/X11/xinitrc
                  ├─20319 /usr/bin/bspwm -c /home/jamie/.config/bspwm/bspwmrc
                  └─20441 xcape -e Hyper_R Tab

May 12 13:18:04 viper login[5015]: LOGIN ON tty1 BY jamie
May 12 13:18:04 viper systemd[1]: Started Session 1 of user jamie.

I think so, I'm using the default xserverrc in /etc/X11/xinit/xserverrc though

Last edited by jameh0 (2020-05-12 21:50:22)

---

Life is very short, and there's no time for fussing and fighting, my friends.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,697

Re: Broken logind session after X has started

The default xserverrc doesn't re-use the TTY, compare yours to the one in the previous link.
Since your session status shows an active ("unbroken") session on tty1, I assume you went to TTY1 (away from your X11 session) to obtain it?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

jameh0

Member

Registered: 2013-04-06

Posts: 40

Re: Broken logind session after X has started

To be clear, I boot to tty1, and login to the tty, the session reports as unbroken there, then I type `startx` and within X the session is broken.

Using the suggested xserverrc, the session is still broken inside of X

loginctl session-status

loginctl session-status
1 - jamie (1000)
           Since: Tue 2020-05-12 14:56:06 PDT; 56s ago
          Leader: 3852 (login)
            Seat: seat0; vc1
             TTY: tty1
         Service: login; type tty; class user
           State: active
            Unit: session-1.scope
                  ├─3852 login -- jamie
                  ├─4615 -zsh
                  ├─5154 -zsh
                  ├─6152 /bin/sh /usr/bin/startx /home/jamie/.config/X11/xinitrc
                  ├─6174 xinit /home/jamie/.config/X11/xinitrc -- /home/jamie/.xserverrc :0 vt1 -keeptty -auth /tmp/serverauth.wRoJns4Ptn
                  ├─6175 /usr/lib/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.wRoJns4Ptn vt1
                  ├─6202 /bin/sh /home/jamie/.config/X11/xinitrc
                  ├─6209 /usr/bin/bspwm -c /home/jamie/.config/bspwm/bspwmrc
                  └─6252 xcape -e Hyper_R Tab

May 12 14:56:06 viper login[3852]: LOGIN ON tty1 BY jamie
May 12 14:56:06 viper systemd[1]: Started Session 1 of user jamie.

that is, `loginctl show-session $XDG_SESSION_ID --property=Active` reports nothing

---

Life is very short, and there's no time for fussing and fighting, my friends.

jameh0

Member

Registered: 2013-04-06

Posts: 40

Re: Broken logind session after X has started

Sorry, I just realized that I'm able to suspend now as my user and that XDG_SESSION_ID is not set when I'm inside X, but it is '1' when at the tty. So my session is not broken - let me see if it's because of the xserverrc.

Last edited by jameh0 (2020-05-12 22:08:29)

---

Life is very short, and there's no time for fussing and fighting, my friends.

jameh0

Member

Registered: 2013-04-06

Posts: 40

Re: Broken logind session after X has started

I've figured out that my session breakage is actually related to using ly display manager, and specifically when I log out and back in quickly using ly as my display manager, and when I was stripping down my system to a startx config, I misdiagnosed the session as still being broken because for some reason inside X, XDG_SESSION_ID and XDG_VTNR are unset.

Do you know why those variables would be unset inside X, but not in the tty? Should I export them in my xinitrc?

Last edited by jameh0 (2020-05-13 03:26:30)

---

Life is very short, and there's no time for fussing and fighting, my friends.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,697

Re: Broken logind session after X has started

https://github.com/cylgom/ly/issues/165 ?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc