Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #204865
| From | Holger Herrlich <hohe72@arcor.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: logout kills X |
| Date | 2019-01-31 15:50 +0100 |
| Message-ID | <xmlPb-5Rm-11@gated-at.bofh.it> (permalink) |
| References | <xm209-28o-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
systemd is very aware the state:
loginctl list-sessions
SESSION UID USER SEAT TTY
1 1000 addams seat0 /dev/tty1
25 1000 addams seat0 /dev/tty2
2 sessions listed.
But it seems that drivers, used by X, will be canceled.
How can I check the udev state. I'm not that familiar with udev and the
way it is integrated into a debian system.
On Wed, 30 Jan 2019 18:38:26 +0100
hohe72@arcor.de wrote:
> I logged in (to tty1)
> started X (startx)
> switched to tty2
> logged in (using the same name)
> logged out
>
> -> X on tty1 crashes
>
>
> some info:
>
> .local/share/xorg/Xorg.0.log:
>
> [ 41948.035] (EE) modeset(0): failed to set mode: Permission denied
> [ 41948.035] (EE)
> Fatal server error:
> [ 41948.035] (EE) EnterVT failed for screen 0
> [ 41948.035] (EE)
> [ 41948.035] (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> [ 41948.035] (EE) Please also check the log file at
> "$HOME/.local/share/xorg/Xorg.0.log" for additional information.
> [ 41948.035] (EE)
>
> what modeset(0) usually goes:
>
> [ 41937.630] (II) modeset(0): EDID vendor "LEN", prod id 16401
> [ 41937.630] (II) modeset(0): Printing DDC gathered Modelines:
> [ 41937.630] (II) modeset(0): Modeline "1280x800"x0.0 68.94 1280
> 1296 1344 1408 800 801 804 816 -hsync -vsync (49.0 kHz eP)
> [ 41937.630] (II) modeset(0): Modeline "1280x800"x0.0 60.96 1280
> 1328 1360 1478 800 803 809 825 -hsync -vsync (41.2 kHz e)
>
> uname -a
> Linux bivalve 4.19.0-0.bpo.1-amd64 #1 SMP Debian 4.19.12-1~bpo9+1
> (2018-12-30) x86_64 GNU/Linux
>
>
> terminal output:
>
> X.Org X Server 1.19.2
> Release Date: 2017-03-02
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
> Current Operating System: Linux bivalve 4.19.0-0.bpo.1-amd64 #1 SMP
> Debian 4.19.12-1~bpo9+1 (2018-12-30) x86_64
> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-0.bpo.1-amd64
> root=UUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ro
> Build Date: 03 November 2018 03:09:11AM
> xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support)
> Current version of pixman: 0.34.0
> Before reporting problems, check http://wiki.x.org to make sure that
> you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational, (WW)
> warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/home/addams/.local/share/xorg/Xorg.0.log", Time: Wed
> Jan 30 15:24:19 2019
> (==) Using config directory: "/etc/X11/xorg.conf.d"
> (==) Using system config directory "/usr/share/X11/xorg.conf.d"
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> permitted) (II) AIGLX: Suspending AIGLX clients for VT switch
> [dix] couldn't enable device 7
> [dix] couldn't enable device 8
> [dix] couldn't enable device 9
> [dix] couldn't enable device 10
> [dix] couldn't enable device 12
> [dix] couldn't enable device 13
> [dix] couldn't enable device 14
> [dix] couldn't enable device 15
> [dix] couldn't enable device 17
> [dix] couldn't enable device 6
> [dix] couldn't enable device 11
> [dix] couldn't enable device 16
> (II) AIGLX: Suspending AIGLX clients for VT switch
> (EE)
> Fatal server error:
> (EE) EnterVT failed for screen 0
> (EE)
> (EE)
> Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
> (EE) Please also check the log file at
> "/home/addams/.local/share/xorg/Xorg.0.log" for additional
> information. (EE) (II) AIGLX: Suspending AIGLX clients for VT switch
> (EE) Server terminated with error (1). Closing log file.
> xinit: connection to X server lost
>
> waiting for X server to shut down
>
>
> ----
>
> loading an older kernel, X doesn't crash, instead all input devices
> have vanished from X.
>
> uname -a:
> Linux bivalve 4.17.0-0.bpo.3-amd64 #1 SMP Debian 4.17.17-1~bpo9+1
> (2018-08-27) x86_64 GNU/Linux
>
> Then I doesn't get control anymore.
>
> ----
> I finally want to know how to separate the sessions.
>
> /etc/systemd/logind.conf:
> KillUserProcesses=no
>
> allready done.
>
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
logout kills X hohe72@arcor.de - 2019-01-30 18:40 +0100
Re: logout kills X deloptes <deloptes@gmail.com> - 2019-01-30 19:30 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-30 19:40 +0100
Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-01-31 15:10 +0100
Re: logout kills X Felix Miata <mrmazda@earthlink.net> - 2019-01-30 19:50 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-30 20:20 +0100
Re: logout kills X Felix Miata <mrmazda@earthlink.net> - 2019-01-30 21:00 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-30 21:30 +0100
Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-01-31 15:30 +0100
Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-01-31 15:30 +0100
Re: logout kills X Felix Miata <mrmazda@earthlink.net> - 2019-01-31 19:00 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-31 19:40 +0100
Re: logout kills X David Wright <deblis@lionunicorn.co.uk> - 2019-01-31 20:00 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-31 21:00 +0100
Re: logout kills X Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-31 21:10 +0100
Re: logout kills X David Wright <deblis@lionunicorn.co.uk> - 2019-02-01 05:30 +0100
Re: logout kills X Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2019-02-02 22:50 +0100
Re: logout kills X Curt <curty@free.fr> - 2019-02-01 12:00 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-02-01 23:40 +0100
Re: logout kills X <tomas@tuxteam.de> - 2019-02-02 11:00 +0100
[solved] Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-02-01 17:20 +0100
[cause] Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-02-04 11:40 +0100
Re: logout kills X David Wright <deblis@lionunicorn.co.uk> - 2019-01-30 21:00 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-30 21:40 +0100
Re: logout kills X Brian <ad44@cityscape.co.uk> - 2019-01-31 00:40 +0100
Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-01-31 15:20 +0100
Re: Let's play "Where is X?" (was: logout kills X) Felix Miata <mrmazda@earthlink.net> - 2019-01-30 23:10 +0100
Re: Let's play "Where is X?" (was: logout kills X) Brian <ad44@cityscape.co.uk> - 2019-01-30 23:40 +0100
Re: Let's play "Where is X?" Felix Miata <mrmazda@earthlink.net> - 2019-01-31 00:00 +0100
Re: Let's play "Where is X?" Brian Potkin <brian@copernicus.org.uk> - 2019-01-31 00:10 +0100
Re: Let's play "Where is X?" Felix Miata <mrmazda@earthlink.net> - 2019-01-31 03:00 +0100
Let's play "Where is X?" (was: logout kills X) Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2019-02-02 23:30 +0100
Re: Let's play "Where is X?" (was: logout kills X) Felix Miata <mrmazda@earthlink.net> - 2019-02-03 00:40 +0100
Re: Let's play "Where is X?" (was: logout kills X) <tomas@tuxteam.de> - 2019-02-03 10:10 +0100
Re: Let's play "Where is X?" (was: logout kills X) Default User <hunguponcontent@gmail.com> - 2019-02-03 17:10 +0100
Re: Let's play "Where is X?" (was: logout kills X) Rusi Mody <rustompmody@gmail.com> - 2019-02-04 04:50 +0100
Re: Let's play "Where is X?" (was: logout kills X) Greg Wooledge <wooledg@eeg.ccf.org> - 2019-02-04 15:30 +0100
Re: logout kills X Holger Herrlich <hohe72@arcor.de> - 2019-01-31 15:50 +0100
csiph-web