On 2023-06-12, pa...@quillandmouse.com wrote:
> Typically, when Debian installs a GUI environment (GNOME, XFCE4, etc.),
> it also installs lightdm or some other X session manager. This takes up
> memory, and isn't something I really need (as far as I know). Instead,
> I'm p
On Mon, Jun 12, 2023 at 03:59:40PM -0400, pa...@quillandmouse.com wrote:
> Folks:
>
> Typically, when Debian installs a GUI environment (GNOME, XFCE4, etc.),
> it also installs lightdm or some other X session manager.
Nitpick: xdm is the X display manager. The X session is somethin
On Mon, Jun 12, 2023 at 03:59:40PM -0400, pa...@quillandmouse.com wrote:
> I'm perfectly happy to have Debian give me a console login prompt, and
> then I issue startx.
That's what I use too. As well as several other people who post regularly
on this mailing list.
Folks:
Typically, when Debian installs a GUI environment (GNOME, XFCE4, etc.),
it also installs lightdm or some other X session manager. This takes up
memory, and isn't something I really need (as far as I know). Instead,
I'm perfectly happy to have Debian give me a console login prompt
On 2023-05-10 09:28:51 -0400, Greg Wooledge wrote:
> On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> > On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > > Note: if you play with .ssh/rc, be careful as there is a risk
> > > that you may not log in any more with ssh in case
On Wed, May 10, 2023 at 03:19:31PM +0200, Vincent Lefevre wrote:
> On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> > Note: if you play with .ssh/rc, be careful as there is a risk
> > that you may not log in any more with ssh in case of mistake
> > (I'm wondering whether there is an undocumen
On 2023-05-10 15:07:17 +0200, Vincent Lefevre wrote:
> Note: if you play with .ssh/rc, be careful as there is a risk
> that you may not log in any more with ssh in case of mistake
> (I'm wondering whether there is an undocumented way to skip it).
For this point, there are solutions there:
https
On 2023-05-10 14:36:25 +0200, Vincent Lefevre wrote:
[...]
> zira:~> ssh cventin xterm
> Connected to cventin (from 140.77.51.8)
> OS: Debian GNU/Linux 12 (bookworm) [x86_64]
> DISPLAY: localhost:11.0
>
> and xterm is started as expected. FYI, some data, like DISPLAY, are
> output by my .ssh/rc sc
On 2023-05-09 20:07:26 +0200, zithro wrote:
> On 09 May 2023 18:06, Vincent Lefevre wrote:
> > On 2023-05-05 15:04:27 +0200, zithro wrote:
> > >
> > > journalctl after GUI LOGOFF
> > > -
On 2023-05-09 14:17:14 -0400, Dan Ritter wrote:
> zithro wrote:
> > On 09 May 2023 17:47, Vincent Lefevre wrote:
> > > BTW, you should also try GNU Screen to see if you have the same issue
> > > with it (this could help debugging).
> >
> > Do you mean trying "ssh u@h screen" ?
> > Never tried scr
On 2023-05-09 19:44:48 +0200, zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > Hi,
> >
> > On 2023-05-04 21:07:17 +0200, zithro wrote:
> > > Here is what happens chronologically :
> > >
> > > 1. I start various SSH connections to a host, some normal, some with X
> > > forwarding,
zithro wrote:
> On 09 May 2023 17:47, Vincent Lefevre wrote:
> > BTW, you should also try GNU Screen to see if you have the same issue
> > with it (this could help debugging).
>
> Do you mean trying "ssh u@h screen" ?
> Never tried screen with GUI apps, does that work ?
Not in a useful way. For
On Tue, May 09, 2023 at 08:07:26PM +0200, zithro wrote:
> I use Ctrl-D to close ssh sessions, "~." does not work, I get "bash: command
> not found".
To use the tilde commands in the ssh client, they have to be at the
"beginning of a line", which means you have to press Enter first. Or
at least ha
On 09 May 2023 18:06, Vincent Lefevre wrote:
On 2023-05-05 15:04:27 +0200, zithro wrote:
journalctl after GUI LOGOFF
[...]
May 05 14:09:14 debzit sshd[14246
es: one at home and one at my lab.
At home, I have an almost persistent X session (I log out only
when I need), and from it I ssh to my machine at my lab and keep
this ssh session open also almost persistently.
At my lab, I log in when I arrive and always log out when I leave,
but this never affects
On 2023-05-05 15:04:27 +0200, zithro wrote:
>
> journalctl after GUI LOGOFF
>
[...]
> May 05 14:09:14 debzit sshd[14246]: Received disconnect from IP.IP.IP.IP
>
e
with it (this could help debugging).
More precisely, I have 2 machines: one at home and one at my lab.
At home, I have an almost persistent X session (I log out only
when I need), and from it I ssh to my machine at my lab and keep
this ssh session open also almost persistently.
At my lab, I log in
On 06 May 2023 07:07, to...@tuxteam.de wrote:
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
Thanks both for the pointers, will report back with results
On 05 May 2023 19:14, Max Nikulin wrote:
Does it happen for newly created user with no customization?
Never tried !
I recommended to do it just for a case that you added something to init
files for the "zithro" user.
AFAIK I didn't customize a lot, as I'm rarely logging to X.
But it won't
On 06 May 2023 06:45, David Wright wrote:
*I login to VC1 and startx for an Xserver*
I think that's why you don't have my problem, your user is always logged
in, even when you close X.
Is the greeter just deferring the ssh command until you login?
Nope, they work without X "direct" login.
On 05/05/2023 12:33, David wrote:
That sounds like what is documented here, with the solution at the end:
$ apt show dbus-user-session
I have tried quite similar steps, it seems the cause is not
dbus-user-session per se.
I have a laptop with Debian 11 bullseye and "minimalistic" KDE
(origi
On Sat, May 06, 2023 at 10:24:52AM +0700, Max Nikulin wrote:
> On 05/05/2023 20:04, zithro wrote:
> > journalctl after GUI LOGOFF
>
> I do not see obvious problems. What might be inspected more closely:
>
> > May 05 14:09:14 debzit systemd[711]: Stopping D-Bus User Message Bus...
>
On Fri 05 May 2023 at 13:59:37 (+0200), zithro wrote:
> On 05 May 2023 07:33, David wrote:
> > On Thu, 4 May 2023 at 19:07, zithro wrote:
> >
> > > this is a rather strange problem, I hope the title is explicit enough.
> >
> > Subject: Logging off an X s
On Sat 06 May 2023 at 09:57:30 (+0700), Max Nikulin wrote:
> On 05/05/2023 10:30, David Wright wrote:
> > On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
> > > On 05/05/2023 02:07, zithro wrote:
> > > > 2. using VNC or rdesktop, I then log on to X on the machine, do
> > > > some stuff, t
On 05/05/2023 20:04, zithro wrote:
journalctl after GUI LOGOFF
I do not see obvious problems. What might be inspected more closely:
May 05 14:09:14 debzit systemd[711]: Stopping D-Bus User Message Bus...
^^^
If it is the bus
On 05/05/2023 10:30, David Wright wrote:
On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do
some stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connecti
On 05/05/2023 18:58, zithro wrote:
# loginctl list-sessions
SESSION UID USER SEAT TTY
111 1000 zithro
112 1000 zithro
141 1000 zithro pts/0
I do not see anything suspicious. I suppose, dbus-user-session
hypothesis by David may be more productive. Perhaps you may prev
On 05 May 2023 16:10, to...@tuxteam.de wrote:
I have now full logs of before/after GUI logon/logoff, I posted them in the
other post.
Will try to make sense of it with this lead ... after a needed break ^^
I saved that for a look during weekend, now I'm supposed to fix
an update of... forget it
On Fri, May 05, 2023 at 03:26:12PM +0200, zithro wrote:
> On 05 May 2023 14:11, to...@tuxteam.de wrote:
[...]
> > No DE, just a window manager (fvwm2).
>
> Isn't that fluxbox ? That's the GUI I used on Slackware.
> Simple, lean, efficient !
No, quite a bit older. Fluxbox 2000-ish, fvwm 199-smal
On 05 May 2023 14:11, to...@tuxteam.de wrote:
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to sw
uid=1000 pid=13960]
Activating service name='org.freedesktop.secrets' requested by ':1.33'
(uid=1000 pid=23408 comm="/usr/libexec/xdg-desktop-portal ")
May 05 14:04:46 debzit dbus-daemon[13960]: [session uid=1000 pid=13960]
Successfully activated service 'org.freedes
On Fri, May 05, 2023 at 01:58:55PM +0200, zithro wrote:
> On 05 May 2023 06:32, to...@tuxteam.de wrote:
> > dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
> > no dbus (still, Debian buster, and X).
>
> I'm on bullseye, I know how to switch back to old init, but have no cl
On 05 May 2023 07:33, David wrote:
On Thu, 4 May 2023 at 19:07, zithro wrote:
this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
Yeah, I meant title==subject, I was hoping
On 05 May 2023 06:32, to...@tuxteam.de wrote:
dbus is a candidate. Let me explain: I have a funny setup -- no systemd,
no dbus (still, Debian buster, and X).
I'm on bullseye, I know how to switch back to old init, but have no clue
about Dbus (kinda a Linux-GUI-with-systemd noob).
Which DE/DM y
On 05 May 2023 05:30, David Wright wrote:
Isn't it this issue?
https://news.ycombinator.com/item?id=19023885
Looks like it, yes !
I'm afraid I can't replicate the problem, though, as I don't have
a "log off" button or menu entry. That might suggest that the
problem is in something I don't r
On 05 May 2023 04:13, Max Nikulin wrote:
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do some
stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get
closed, hence all the shells and
On Thu, 4 May 2023 at 19:07, zithro wrote:
> this is a rather strange problem, I hope the title is explicit enough.
Subject: Logging off an X session closes all ssh -X connections
started previously from outside X
> Here is what happens chronologically :
>
> 1. I start various SSH
On Fri, May 05, 2023 at 09:13:04AM +0700, Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do some
> > stuff, then hit "log off" from the desktop menu.
[...]
> Perhaps it may be related to user D-Bus sessions, however I would
On Fri 05 May 2023 at 09:13:04 (+0700), Max Nikulin wrote:
> On 05/05/2023 02:07, zithro wrote:
> > 2. using VNC or rdesktop, I then log on to X on the machine, do
> > some stuff, then hit "log off" from the desktop menu.
> > Immediately, ALL the previous SSH connections started in step 1
> > get c
On 05/05/2023 02:07, zithro wrote:
2. using VNC or rdesktop, I then log on to X on the machine, do some
stuff, then hit "log off" from the desktop menu.
Immediately, ALL the previous SSH connections started in step 1 get
closed, hence all the shells and the GUI apps (firefox, etc) !
Have you i
ed in step 1 get
closed, hence all the shells and the GUI apps (firefox, etc) !
Everything is done using the same local and remote users (same UID but
different names). sshd is the parent process of all my remote SSH sessions.
I don't get how apps and shells NOT started via the X sessi
On Lu, 22 nov 21, 11:39:46, Greg Wooledge wrote:
>
> That's as far as I got. If the OP wants to try writing a systemd --user
> unit file for their unison thingy, and see if that starts and stops in
> a way that they find acceptable, that would be a cool experiment.
It's a good way to run backgr
On Ma, 23 nov 21, 09:28:39, David Wright wrote:
> On Tue 23 Nov 2021 at 07:51:32 (-0500), Greg Wooledge wrote:
> > On Tue, Nov 23, 2021 at 12:05:37PM +, Jonathan Dowland wrote:
> > > On Mon, Nov 22, 2021 at 11:39:46AM -0500, Greg Wooledge wrote:
> > > > I don't know the exact time that I closed
On Tue 23 Nov 2021 at 07:51:32 (-0500), Greg Wooledge wrote:
> On Tue, Nov 23, 2021 at 12:05:37PM +, Jonathan Dowland wrote:
> > On Mon, Nov 22, 2021 at 11:39:46AM -0500, Greg Wooledge wrote:
> > > I don't know the exact time that I closed the login shell on tty2. It
> > > *could* have been at
set -e will trigger
> and kill the shell.
>
> I suspect you've run across one of the above cases, without realizing it.
Well, that would be a welcome correction—and one less thing to worry about.
> On Mon, Nov 22, 2021 at 02:45:43PM -0600, David Wright wrote:
> > I haven&#x
On Tue, Nov 23, 2021 at 12:05:37PM +, Jonathan Dowland wrote:
> On Mon, Nov 22, 2021 at 11:39:46AM -0500, Greg Wooledge wrote:
> > I don't know the exact time that I closed the login shell on tty2. It
> > *could* have been at exactly 11:19:00 but that seems like a suspiciously
> > round number
On Mon, Nov 22, 2021 at 11:39:46AM -0500, Greg Wooledge wrote:
I don't know the exact time that I closed the login shell on tty2. It
*could* have been at exactly 11:19:00 but that seems like a suspiciously
round number (and a suspiciously long time after I started the service).
You don't, but
#x27;ve run across one of the above cases, without realizing it.
On Mon, Nov 22, 2021 at 02:45:43PM -0600, David Wright wrote:
> I haven't looked for differences that might have arisen since systemd
> entered upon the scene (and I've yet to work my way through your
> addition to th
less someone can figure out how to make systemd do this.)
I haven't looked for differences that might have arisen since systemd
entered upon the scene (and I've yet to work my way through your
addition to this subthread), but in looking through /etc/X11/ to see
what x-session-manager m
n pressing
> a magic key combination like Ctrl-Alt-Backspace, with an appropriate
> option set in the xorg.conf file to cause that to terminate the X server)
> rather than exiting from MATE in the normal manner?
When I wrote the post that ¶B refers to, the only evidence that the OP
was using
gged out of the tty2 shell, and pressed Ctrl-Alt-F1 to get back to
my X session running as greg. Then I checked the processes running as
user tester:
unicorn:~$ ps -fu tester
UID PIDPPID C STIME TTY TIME CMD
tes
On Mon, Nov 22, 2021 at 03:25:02PM +, Musbur wrote:
> Am 20.11.2021 22:19 schrieb Greg Wooledge:
> > On Sat, Nov 20, 2021 at 09:46:24PM +0100, Arkadiusz Dabrowski wrote:
> > > Started with "exec" according to Debian documentation:
> > > https://wiki.debian.org/Xsession
> >
> > You're cargo-cul
Am 20.11.2021 22:19 schrieb Greg Wooledge:
On Sat, Nov 20, 2021 at 09:46:24PM +0100, Arkadiusz Dabrowski wrote:
Started with "exec" according to Debian documentation:
https://wiki.debian.org/Xsession
You're cargo-culting stuff with zero understanding. That's not going
to help.
If you don't k
On Sun, Nov 21, 2021 at 11:39:53PM -0600, David Wright wrote:
> On Sun 21 Nov 2021 at 14:16:26 (-0500), Greg Wooledge wrote:
> > So then, it would look something like this:
> >
> > your unison thing &
> > unisonPID=$!
> > other things you want to run
> > magic MATE start command
> > kill "$unisonP
I see that ~/.xsession is invoked from
> > etc/X11/Xsession (indirectly by calling
> > /etc/X11/Xsession.d/50x11-common_determine-startup)
> > and after .xsessionrc (called prior from
> > /etc/X11/Xsession.d/40x11-common_xsessionrc) so I ended-up with hundreds of
> > u
es (not scripts) in
> /etc/X11/Xsession.d/.
>
> So, if you want to be able to kill a process while logging out of
> your X session, apparently you need to create a whole .xsession file.
> Congratulations: you're graduating out of novice mode whether you like
> it or not.
>
> The
common_determine-startup)
> and after .xsessionrc (called prior from
> /etc/X11/Xsession.d/40x11-common_xsessionrc) so I ended-up with hundreds of
> unison instances instead of new X session.
>
> But it is not so bad: I learned about X11 starting process so will be able
> to analyze i
ith hundreds of
unison instances instead of new X session.
But it is not so bad: I learned about X11 starting process so will be able
to analyze it and invent something. So thanks a lot :)
> > Started with "exec" according to Debian documentation:
> > https://wiki.debian
On Sat, Nov 20, 2021 at 09:46:24PM +0100, Arkadiusz Dabrowski wrote:
> Unfortunately, the solution with .xsession file doesn't work.
> I resorted to something very simplistic:
>
>
> exec /usr/bin/marco
>
>
> Note: I use mate desktop with marco wm.
I doubt very much that this is the correct com
d and ssh-agent is the only process under it.
I have no idea why my .xsession file name appears in the command line where
ssh-agent is started but it looks suspicious. Another x-session is started?
root 17474 0.0 0.1 165776 9604 ?Sl 21:23 0:00 \_
lightdm --session-child 12 2
d from
> > > .xsessionrc.
> > > It works flawlessly but when I log out it is orphaned and not terminated.
> > > I start it like this:
> > > nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> > > Once started the parent is x-session
Thank You all guys for help!
If systemd feature is not an option I'll try a .xession solution. Looks
promising.
On Thu, Nov 18, 2021 at 09:21:34PM +, Jonathan Dowland wrote:
> On Thu, Nov 18, 2021 at 03:46:48PM -0500, Greg Wooledge wrote:
> > (I still wonder whether systemd offers anything relevant here. And if
> > not, what the hell *is* the point of systemctl --user? I've never used
> > it, nor found
I'd echo Greg in that the simplest answer might lie with using systemd's
facility for this, but,
On Thu, Nov 18, 2021 at 02:34:52PM -0600, David Wright wrote:
# ~/.xsession contents
…
# now start your clients and programs, all backgrounded with &
^^
This would be the point at which OP would
On Thu, Nov 18, 2021 at 03:46:48PM -0500, Greg Wooledge wrote:
(I still wonder whether systemd offers anything relevant here. And if
not, what the hell *is* the point of systemctl --user? I've never used
it, nor found any reason to use it. Yet.)
systemd certainly does offer something here. I
son unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
> group.
> What can I do to terminate the process with x-session?
>
/etc/X11/Xreset.d is a directory which holds scripts to be executed
upon termination of a display mana
t it is orphaned and not terminated.
> > I start it like this:
> > nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> > Once started the parent is x-session-manager and they the same process
> > group.
>
> I think this is because you're star
-c2 -n7 unison unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
> group.
I think this is because you're starting it in the wrong file.
Everything in .xsessionrc should complete immediately. Use it
to set parameters and things like th
p;
> > Once started the parent is x-session-manager and they the same process
> > group.
> > What can I do to terminate the process with x-session?
>
> does it work if you don't put it in the background?
That would prevent the rest of the X session from running, until the
unison process terminates.
Arkadiusz Dabrowski wrote:
...
> It works flawlessly but when I log out it is orphaned and not terminated.
> I start it like this:
> nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
> Once started the parent is x-session-manager and they the same process
>
On Wed 17 Nov 2021 at 22:39:21 +0100, Arkadiusz Dabrowski wrote:
> Hi all
> I have a problem with unison sync termination when it is started from
> .xsessionrc.
.xsessionrc is for stting environment variables for an X session. This
your intentio?
--
Brian.
On Wed, Nov 17, 2021 at 10:39:21PM +0100, Arkadiusz Dabrowski wrote:
> I have a problem with unison sync termination when it is started from
> .xsessionrc.
> It works flawlessly but when I log out it is orphaned and not terminated.
> I start it like this:
> nice -n18 ionice -c2 -n7 unison unison_pr
Hi all
I have a problem with unison sync termination when it is started from
.xsessionrc.
It works flawlessly but when I log out it is orphaned and not terminated.
I start it like this:
nice -n18 ionice -c2 -n7 unison unison_profile &>/dev/null &
Once started the parent is x-session-
Roger Price wrote Mon, 29 Jan 2018 23:13:05 +0100 (CET):
I rebooted stretch and now my journald is being swamped with the following
message:
/usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context
unloaded: Message manager disconnected
It's the Ghostery addon to Firefox 5
Roger Price wrote Mon, 29 Jan 2018 23:13:05 +0100 (CET):
I rebooted stretch and now my journald is being swamped with the following
message:
/usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context unloaded:
Message manager disconnected
I managed to get rid of this flood of
I rebooted stretch and now my journald is being swamped with the following
message:
/usr/lib/gdm3/gdm-x-session[2684]: Promise rejected after context unloaded:
Message manager disconnected
A new message appears every few seconds. What is causing this?
What have I done wrong? Any hint would
On Sun, 8/23/15, Jimmy Johnson wrote:
// While kdm still works in upstream stretch/testing, I've been told it is
// no longer being supported by systemd and has been replaced with sddm,
// but if you want to see your desktop currently you need to follow the
// instructions I gave you. For plasma
On 08/23/2015 01:19 PM, Ldten K wrote:
On Sun, 8/23/15, Jimmy Johnson wrote:
It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098
It may be the same issue though I'm not sure why I was getting the error about
missing /home/luser/.Xsession file. I manually copied /etc/kde4/kd
On Sun, 8/23/15, Jimmy Johnson wrote:
> It's a bug, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796098
It may be the same issue though I'm not sure why I was getting the error about
missing /home/luser/.Xsession file. I manually copied /etc/kde4/kdm/Xsession
file as /home/luser/.Xsession
On 08/23/2015 02:16 AM, Ldten K wrote:
Hi,
Tried upgrading from wheezy to stretch, just to see how it would go. It mostly
went OK though there is an issue: when trying to log in from kdm the system now
complains that it's unable to start X session --- no /home/luser/.xsession
file, no
Hi,
Tried upgrading from wheezy to stretch, just to see how it would go. It mostly
went OK though there is an issue: when trying to log in from kdm the system now
complains that it's unable to start X session --- no /home/luser/.xsession
file, no /home/luser/.Xsession file, no session man
On Mon, 8 Jun 2015 17:48:11 +0200
Siard wrote:
> Teemu Likonen:
> > Nicolas George:
> > > Someone recently suggested to use "nodm"; a quick test a few days
> > > ago seems to indicate it still works.
> >
> > It works, indeed. Thanks.
>
> But how to log out with nodm?? After logging out, I get
Le decadi 20 prairial, an CCXXIII, Siard a écrit :
> Ah, I use Fluxbox, so I can only log out, then shut down from the
> console. Looks like nodm is no option here.
Why do you need to log out? Just open a terminal emulator to shutdown.
Regards,
--
Nicolas George
signature.asc
Description:
Lisi Reisz:
> Siard:
> > But how to log out with nodm?? After logging out, I get immediately
> > logged back in.
>
> You have to shut down.
Ah, I use Fluxbox, so I can only log out, then shut down from the
console. Looks like nodm is no option here.
--
To UNSUBSCRIBE, email to debian-user-re
On Monday 08 June 2015 16:48:11 Siard wrote:
> Teemu Likonen:
> > Nicolas George:
> > > Someone recently suggested to use "nodm"; a quick test a few days
> > > ago seems to indicate it still works.
> >
> > It works, indeed. Thanks.
>
> But how to log out with nodm?? After logging out, I get immedi
Teemu Likonen:
> Nicolas George:
> > Someone recently suggested to use "nodm"; a quick test a few days
> > ago seems to indicate it still works.
>
> It works, indeed. Thanks.
But how to log out with nodm?? After logging out, I get immediately
logged back in.
--
To UNSUBSCRIBE, email to debian
On Monday 08 June 2015 10:53:40 Juha Heinanen wrote:
> Teemu Likonen writes:
> > > It seems that it has no effect anymore in Debian 8 (Jessie), probably
> > > because of the new init system (systemd). So how do I get similar
> > > functionality with the new systemd init system?
> >
> > One option i
Le decadi 20 prairial, an CCXXIII, Teemu Likonen a écrit :
> Fortunately I haven't noticed anything in years. I've been using i3
> window manager so maybe I'm unaware of some services that modern
> desktops might use or depend on.
The issues are discreet, but if you end up falling on one, you will
Nicolas George [2015-06-08 11:55:17+02] wrote:
> Rule of thumb: if you are using rc.local, then you are doing something
> quick-and-dirty and preparing no end of problems for later.
>
> In this particular instance, you are not registering the X11 session
> with the various session-management daemo
Le decadi 20 prairial, an CCXXIII, Teemu Likonen a écrit :
> One option is /etc/rc.local:
>
> /bin/su -l USER -c /usr/bin/startx /dev/tty8 2>&1 &
> exit 0
Rule of thumb: if you are using rc.local, then you are doing something
quick-and-dirty and preparing no end of problems for later.
In
Teemu Likonen writes:
> > It seems that it has no effect anymore in Debian 8 (Jessie), probably
> > because of the new init system (systemd). So how do I get similar
> > functionality with the new systemd init system?
>
> One option is /etc/rc.local:
>
> /bin/su -l USER -c /usr/bin/startx /d
Teemu Likonen [2015-06-04 12:26:08+03] wrote:
> When my machine boots it logs in to X session automatically without
> user login and password prompt.
> Upto Debian 7 I have had this line in my [/etc/inittab] file:
>
> oma:2:once:/bin/su -l dtw -c /usr/bin/startx /dev/tty8 2&
Nicolas George [2015-06-04 11:35:47+02] wrote:
> Le sextidi 16 prairial, an CCXXIII, Teemu Likonen a écrit :
>> oma:2:once:/bin/su -l dtw -c /usr/bin/startx /dev/tty8 2>&1
>> So how do I get similar functionality with the new systemd init
>> system?
>
> Someone recently suggested to use "nodm
Teemu Likonen [2015-06-04 12:26:08+03] wrote:
> Upto Debian 7 I have had this line in my /etc/fstab file:
>
> oma:2:once:/bin/su -l dtw -c /usr/bin/startx /dev/tty8 2>&1
Obviously I meant /etc/inittab file.
signature.asc
Description: PGP signature
Le sextidi 16 prairial, an CCXXIII, Teemu Likonen a écrit :
> Upto Debian 7 I have had this line in my /etc/fstab file:
>
> oma:2:once:/bin/su -l dtw -c /usr/bin/startx /dev/tty8 2>&1
>
> It seems that it has no effect anymore in Debian 8 (Jessie), probably
> because of the new init system (s
Hi!
When my machine boots it logs in to X session automatically without user
login and password prompt. (This is a single-user system with encrypted
Luks partitions and I always enter Luks password when the machine boots.
I'm the only person in the world who knows the Luks password so this i
Am Dienstag, 10. Dezember 2013, 19:24:14 schrieb Zenaan Harkness:
> On 12/10/13, Zenaan Harkness wrote:
> > After my recent sid upgrade, when I test boot with systemd, startx
> > ends with an error saying something (I think it is X) is lacking
> > permissions.
>
> Just rebooted (to test other cha
On 12/10/13, Zenaan Harkness wrote:
> After my recent sid upgrade, when I test boot with systemd, startx
> ends with an error saying something (I think it is X) is lacking
> permissions.
Just rebooted (to test other changes), and my laptop is now
auto-booting with systemd (looks like some grub cu
After my recent sid upgrade, when I test boot with systemd, startx
ends with an error saying something (I think it is X) is lacking
permissions.
Any systemd users knowledgeable on how to user startx manually after
booting with systemd?
I tested systemd a few times after my upgrade, and have rever
On 2013-05-20 10:45 +0200, Andrei POPESCU wrote:
> On Du, 19 mai 13, 22:35:03, Celejar wrote:
>>
>> The release notes are actually somewhat unclear, and I was considering
>> filing a bug report against them. The implication is that there's no
>> recommendation aga
1 - 100 of 264 matches
Mail list logo
