Bug#720116: marked as done (xinit: startx should just start a plain X, not the whole desktop-environment)
Your message dated Sun, 18 Aug 2013 22:41:49 +0200
with message-id <20130818204149.GA15133@mraw.org>
and subject line Re: Bug#720116: xinit: startx should just start a plain X, not the whole desktop-environment
has caused the Debian Bug report #720116,
regarding xinit: startx should just start a plain X, not the whole desktop-environment
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
720116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720116
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xinit
Version: 1.3.2-1
Severity: wishlist
Hi.
IIRC, startx always used to do just that, "start X".
But nowadays, when I "startx" I get all kinds of further stuff, i.e.
GNOME tries to fully start up (WTF?).
This behaviour is IMHO quite problematic, since in case of disaster
recovery (see e.g. bug #720115) one cannot even start a plain X
anymore, without fiddling around with the X binary itself.
Not sure whether this is actually xinit's fault, or whether some other
package (gnome-whatever) just overrides any xsession or xinit config
file to cause this behaviour... I just didn't now where to start
searching ;)
Thanks,
Chris.
--- End Message ---
--- Begin Message ---
Hi,
Christoph Anton Mitterer <calestyo@scientia.net> (2013-08-18):
> Package: xinit
> Version: 1.3.2-1
> Severity: wishlist
>
> Hi.
>
> IIRC, startx always used to do just that, "start X".
startx(1) says:
| NAME
| startx - initialize an X session
[…]
| DESCRIPTION
[…]
| To determine the client to run, startx first looks for a file called
| .xinitrc in the user's home directory. If that is not found, it uses
| the file xinitrc in the xinit library directory. If command line
| client options are given, they override this behavior and revert to the
| xinit(1) behavior.
> But nowadays, when I "startx" I get all kinds of further stuff, i.e.
> GNOME tries to fully start up (WTF?).
>
> This behaviour is IMHO quite problematic, since in case of disaster
> recovery (see e.g. bug #720115) one cannot even start a plain X
> anymore, without fiddling around with the X binary itself.
>
> Not sure whether this is actually xinit's fault, or whether some other
> package (gnome-whatever) just overrides any xsession or xinit config
> file to cause this behaviour... I just didn't now where to start
> searching ;)
So either specify a client [1] or use a different session manager, e.g.
by using: update-alternatives --config x-session-manager
1. http://x.debian.net/faq/general.html
Closing accordingly.
Mraw,
KiBi.
--- End Message ---
Reply to: