Re: startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

> my workstation's hostname is the same as my login
> username, which is (obviously) also the name of my home directory.
> And yet, I've never seen this problem before.
> So, there are definitely a few more variables involved in this one.

To reproduce, run xauth list $(hostname -f):0 from a directory that
has a file or directory with the name of the workstation.  Demo:

guest@redacted:~/empty$ ls
guest@redacted:~/empty$ xauth list $(hostname -f):0
redacted.localdomain:0  MIT-MAGIC-COOKIE-1  d41d8cd98f00b204e9800998ecf8427e
guest@redacted:~/empty$ touch $(hostname)
guest@redacted:~/empty$ xauth list $(hostname -f):0
Segmentation fault
guest@redacted:~/empty$ ls -li ~/.Xauthority-*
57941079 -rw--- 2 guest guest 0 Mar 31 13:09 /home/guest/.Xauthority-c
57941079 -rw--- 2 guest guest 0 Mar 31 13:09 /home/guest/.Xauthority-l
guest@redacted:~/empty$ 

The segfault has been addressed in upstream xauth-1.1.1, which is good!
Those changes are incomplete and it still gives a wrong/confusing answer
when faced with this accidental name collision.  I have a tested patch
that I'll write up and add to the 889720 report.

  - Larry

Re: startx xauth fails after upgrade to Bullseye 11.3

[David Wright]

On Thu 31 Mar 2022 at 07:30:14 (-0400), Greg Wooledge wrote:
> On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote:
> > I seem to have rediscovered Debian bug 889720
> > xauth crashes when directory name matches host name
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720
> > (Feb 2018)
> > 
> > So, nothing to do with the Bullseye upgrade.
> > I must have created that directory-matching-hostname in the
> > process of setting up for the upgrade.
> 
> Huh.  That is interesting, and confusing.  Because at work, I have the
> same setup as you -- my workstation's hostname is the same as my login
> username, which is (obviously) also the name of my home directory.
> And yet, I've never seen this problem before.
> 
> That bug report contains the clause "my .Xauthority file contains a line
> like this" which is also interesting.  Mine is not a text file.  When I
> view it in less, I'm warned that it's a binary file.  The file does not
> contain "lines" at all (looks like a mixture of text and binary data),
> and nothing that looks like "wooledg:0".  A few "wooledg", but none with
> the ":0" attached.

We can probably assume that the reporter listed it with xauth. Here's mine:

$ xauth -f .Xauthority list
HOST/unix:0  MIT-MAGIC-COOKIE-1  11223344556677889900aabbccddeeff
HOST.corp:0  MIT-MAGIC-COOKIE-1  11223344556677889900aabbccddeeff
HOST/unix:15  MIT-MAGIC-COOKIE-1  234567890abcdef1234567890abcdef1
HOST/unix:16  MIT-MAGIC-COOKIE-1  134567890abcdef1234567890abcdef2
HOST/unix:17  MIT-MAGIC-COOKIE-1  124567890abcdef1234567890abcdef3
HOST/unix:18  MIT-MAGIC-COOKIE-1  123567890abcdef1234567890abcdef4
HOST/unix:14  MIT-MAGIC-COOKIE-1  123467890abcdef1234567890abcdef5
HOST/unix:12  MIT-MAGIC-COOKIE-1  123457890abcdef1234567890abcdef6
HOST/unix:13  MIT-MAGIC-COOKIE-1  123456890abcdef1234567890abcdef7
HOST/unix:11  MIT-MAGIC-COOKIE-1  123456790abcdef1234567890abcdef8
HOST/unix:10  MIT-MAGIC-COOKIE-1  123456780abcdef1234567890abcdef9
$ ls -l .Xauthority
-rw--- 1 AUSER AUSER 548 Mar 29 10:57 .Xauthority
$ 

… where "corp" is my local domain name, and the rest is obfuscated.

I also own a file in /tmp:

$ xauth -f /tmp/serverauth.randmchars list
HOST/unix:0  MIT-MAGIC-COOKIE-1  123456789abcdef1234567890abcdef0
HOST/unix:1  MIT-MAGIC-COOKIE-1  11223344556677889900aabbccddeeff
HOST/unix:2  MIT-MAGIC-COOKIE-1  11223344556677889900aabbccddeeff
$ ls -l /tmp/serverauth.randmchars
-rw--- 1 AUSER AUSER 147 Mar 31 08:39 /tmp/serverauth.randmchars
$ 

… whose timestamp corresponds with when I booted this machine and
started X. (I can't match its first entry with anything else.)

> So, there are definitely a few more variables involved in this one.  I
> don't know why it works for some people (e.g. me) and not others.  I don't
> know the format of the ~/.Xauthority file, or why it varies across
> different Debian systems, or different login accounts.

I'm running a browser as a different local user, displayed on my X.
Their .Xauthority has an entry identical to the first entry above,
along with some different ones, and their file modification timestamp
is two hours later.

It'll be a couple of decades since I looked at what this all means.
I wrote a script that was designed to minimise retyping passwords
(pre- key authentication) when I connected and reconnected between
machines that were running Xservers.

I will say that I've never seen an entry as simple as HOST:0 …
>From the above, it might correspond to a host with no domain name.
Grasping at straws, I would check my /etc/hosts and /etc/hostname
were conformant, and that I had a domain name (like .corp).

Exim used to (does still?) complain about the lack of a domain name,
but it still performed. I don't know whether X has changed in this
regard. I wouldn't expect it to affect ordinary sockets. (I would
also have thought others would be complaining.)

Disclaimers: this particular machine is still running buster.
I don't run a DM (and I don't know what a DCOPserver is).

Cheers,
David.

Re: startx xauth fails after upgrade to Bullseye 11.3

[Greg Wooledge]

On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote:
> I seem to have rediscovered Debian bug 889720
> xauth crashes when directory name matches host name
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720
> (Feb 2018)
> 
> So, nothing to do with the Bullseye upgrade.
> I must have created that directory-matching-hostname in the
> process of setting up for the upgrade.

Huh.  That is interesting, and confusing.  Because at work, I have the
same setup as you -- my workstation's hostname is the same as my login
username, which is (obviously) also the name of my home directory.
And yet, I've never seen this problem before.

That bug report contains the clause "my .Xauthority file contains a line
like this" which is also interesting.  Mine is not a text file.  When I
view it in less, I'm warned that it's a binary file.  The file does not
contain "lines" at all (looks like a mixture of text and binary data),
and nothing that looks like "wooledg:0".  A few "wooledg", but none with
the ":0" attached.

So, there are definitely a few more variables involved in this one.  I
don't know why it works for some people (e.g. me) and not others.  I don't
know the format of the ~/.Xauthority file, or why it varies across
different Debian systems, or different login accounts.

Re: startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

I seem to have rediscovered Debian bug 889720
xauth crashes when directory name matches host name
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720
(Feb 2018)

So, nothing to do with the Bullseye upgrade.
I must have created that directory-matching-hostname in the
process of setting up for the upgrade.

  - Larry

Re: startx xauth fails after upgrade to Bullseye 11.3

[Felix Miata]

Larry Doolittle composed on 2022-03-30 19:31 (UTC-0700):

> Felix Miata wrote:

>> Is the problem avoided if you login via a display manager (gdm, sddm, 
>> lightdm,
>> etc.) instead of using startx?
 
> Beats me.  I don't have any software like that installed.

You could install one. Try LightDM. Uncompressed Size: 852 k, plus whatever 
deps.

> Would they run xauth before or after cd'ing to my home directory?

I don't know the middle of the chains of events that gets an X sessions
started, whether via DM, or startx, only some start and end points. I booted up 
a
Bullseye installation to multi-user.target, logged in, then ran startx, and got 
this:

# ls -alrtgG | tail -n9
drwxr-xr-x  3   4096 Feb  9 20:36 .mc
drwxr-xr-x 27   4096 Mar 16 21:23 ..
-rw---  1  33857 Mar 30 20:20 .bash_history
-rw---  1 99 Mar 30 20:23 .Xauthority
-rw-r--r--  1 52 Mar 30 20:23 .DCOPserver_ab560__0
lrwxrwxrwx  1 26 Mar 30 20:23 .DCOPserver_ab560_:0 -> 
/root/.DCOPserver_ab560__0
-rw---  1 31 Mar 30 20:23 .mcoprc
drwx-- 15   4096 Mar 30 20:23 .
-rw---  1 103873 Mar 30 20:23 .xsession-errors

Next I rebooted to graphical.target, logged in, and got this:
# ls -alrtgG | tail -n9
drwxr-xr-x  3   4096 Feb  9 20:36 .mc
drwxr-xr-x 27   4096 Mar 30 20:39 ..
-rw---  1 99 Mar 30 20:49 .Xauthority
-rw-r--r--  1 52 Mar 30 20:49 .DCOPserver_ab560__0
lrwxrwxrwx  1 26 Mar 30 20:49 .DCOPserver_ab560_:0 -> 
/root/.DCOPserver_ab560__0
-rw---  1 31 Mar 30 20:49 .mcoprc
-rw---  1  34072 Mar 30 20:49 .bash_history
drwx-- 15   4096 Mar 30 20:49 .
-rw---  1  48801 Mar 30 20:49 .xsession-errors
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

Felix -

Felix Miata  wrote:
> Is the problem avoided if you login via a display manager (gdm, sddm, lightdm,
> etc.) instead of using startx?

Beats me.  I don't have any software like that installed.
Would they run xauth before or after cd'ing to my home directory?

  - Larry

P.S.  Sorry about breaking threading; I can only read this list
via the web.

Re: startx xauth fails after upgrade to Bullseye 11.3

[Felix Miata]

Larry Doolittle composed on 2022-03-30 08:57 (UTC-0700):

> The xauth segfault is definitely real and
> a problem for me.

Is the problem avoided if you login via a display manager (gdm, sddm, lightdm,
etc.) instead of using startx?
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

Esteemed Debian experts and maintainers -

On Sun, Mar 27, 2022 at 11:26:37PM -0700, Larry Doolittle wrote:
> On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote:
> > I just upgraded my first machine from 11.2 to 11.3.
> > xauth fails in the context of startx.
> Workaround: create an empty directory, cd to that, and then startx.
> Something about running startx (and therefore xauth) in my home
> directory has it very confused.

The key command is
  xauth list $(hostname -f):0
When run in my home directory, it yields a Segmentation fault,
and leaves behind two zero-length lock files
  .Xauthority-l .Xauthority-c
that are hard-linked together.  I have to remove those files before
continuing.  When run in an empty subdirectory, that xauth command
(correctly) prints one line with an MIT-MAGIC-COOKIE-1, and
does not segfault.

In the context of /usr/bin/startx (xinit-1.4.0-1), this fault shows up
in line 199-200
authcookie=`xauth list "$displayname" \
| sed -n "s/.*$displayname[[:space:]*].*[[:space:]*]//p"` 2>/dev/null;
and the lock files left behind prevent the following xauth calls from
functioning.

I can run xauth (xauth-1:1.1-1) under gdb, but until and unless I recompile 
it with debugging symbols, the result is not so helpful:
Program received signal SIGSEGV, Segmentation fault.
__strncpy_avx2 () at ../sysdeps/x86_64/multiarch/strcpy-avx2.S:301
301 ../sysdeps/x86_64/multiarch/strcpy-avx2.S: No such file or directory.
(gdb) bt
#0  __strncpy_avx2 () at ../sysdeps/x86_64/multiarch/strcpy-avx2.S:301
#1  0x8cc3 in ?? ()
#2  0x9c8c in ?? ()
#3  0xa53d in ?? ()
#4  0xaa1e in ?? ()
#5  0x8634 in ?? ()
#6  0x77ca0d0a in __libc_start_main (main=0x8480, argc=3,
argv=0x7fffe378, init=, fini=,
rtld_fini=, stack_end=0x7fffe368)
at ../csu/libc-start.c:308
#7  0x870a in ?? ()
(gdb)

This behavior started when I upgraded to Bullseye 11.3 from 11.2.
Until I understand the fault and its trigger better, I can't guarantee 
that wasn't a coincidence.  The xauth segfault is definitely real and
a problem for me.

  - Larry

Re: startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

Esteemed Debian experts and maintainers -

On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote:
> I just upgraded my first machine from 11.2 to 11.3.
> xauth fails in the context of startx.
> Message is
>   xauth:  timeout in locking authority file /home/[redacted]/.Xauthority
> both in the startx console, and if I run "xauth list"
> in the resulting X session.

Workaround: create an empty directory, cd to that,
and then startx.  Something about running startx (and therefore xauth)
in my home directory has it very confused.  It leaves behind extra
files (hard-linked to each other): .Xauthority-c and .Xauthority-l.

  - Larry

startx xauth fails after upgrade to Bullseye 11.3

[Larry Doolittle]

Esteemed Debian experts and maintainers -

I just upgraded my first machine from 11.2 to 11.3.
xauth fails in the context of startx.
Message is
  xauth:  timeout in locking authority file /home/[redacted]/.Xauthority
both in the startx console, and if I run "xauth list"
in the resulting X session.  It's an annoyance that X takes longer to start.
I'm pretty sure my X security is broken, too.  E.g., "ssh -X foo" gives
a timeout and fallback.

I tried downgrading each of server-xorg-video-intel and linux-image-amd64,
and neither by itself fixed it.

Googling for the problem, the standard questions are what my home directory
and .Xauthority permissions are.  Sigh.  drwxr-xr-x and -rw---.
That's not it.

I was able to capture output of startx, running it as "sh -x /usr/bin/startx".
The relevant section seems to be
+ /usr/bin/mcookie
+ mcookie=31343d9e22148031aa3a7b27090d2090
+ test x31343d9e22148031aa3a7b27090d2090 = x
+ dummy=0
+ mktemp --tmpdir serverauth.XX
+ xserverauthfile=/tmp/serverauth.6wEy4jJlBy
+ trap rm -f '/tmp/serverauth.6wEy4jJlBy' HUP INT QUIT ILL TRAP KILL BUS TERM
+ xauth -q -f /tmp/serverauth.6wEy4jJlBy
+ serverargs= vt1 -keeptty -auth /tmp/serverauth.6wEy4jJlBy
+ authcookie=
+ [ z = z ]
+ xauth -q
xauth:  file /home/[redacted]/.Xauthority does not exist
+ removelist=:0 
+ authcookie=
+ [ z = z ]
+ xauth -q
xauth:  timeout in locking authority file /home/[redacted]/.Xauthority
+ removelist=menace.localdomain:0 :0 

(I've tried both removing and not removing .Xauthority* files)

Huh.  I just tried running startx as a different username.
Works fine!  WTF?

I've never seen anything like this in over a decade of Debian usage.

  - Larry

Re: Startx works, but sddm/lightdm/xdm doesn't

[Anssi Saari]

John Goerzen  writes:

> But sddm doesn't work.  In fact, when it starts, it causes my monitor to
> go "no signal".  Oddly, though, if I can log in blindly, then once I hit
> enter after putting in my password, KDE will come up and work like it
> should.
>
> I also tried lightdm and xdm.  Both of them also had "no signal" when
> starting.

That kind of points to a problem with a shared config file. I only know
sddm a little, its startup script /etc/sddm/Xsession ends with

. /etc/X11/Xsession

so it reads commands from there. Which in turn refers a whole bunch of
config files. I'd guess xdm and lightdm do the same. But good luck
figuring out what's wrong, especially if you have a new install where
you haven't tweaked anything? You didn't restore an old home directory
from backup for example?

What about installing the non-free nvidia-driver?

> It is using the nouveau driver.  There are no errors in Xorg.0.log,
> journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
> other graphics adapter.  xrandr on the sddm session shows it detected
> the appropriate output at the appropriate resolution.  Xorg.0.log looks
> completely appropriate; detecting devices, setting them up, etc.

Curious. I do seem to get quite a lot of messages in ~/.xsession-errors
on my laptop, although they don't all look like errors.

Re: Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

On Mon, Feb 28 2022, Felix Miata wrote:

>> However, removing modesetting_drv.so from
>> /usr/lib/xorg/modules/drivers did.  That solved the problem.
>
>> But it didn't switch to nouveau; it went to fbdev.
>
> You likely created a new problem. modesetting_drv.so is the default DIX for 
> AMD,
> Intel and NVidia GPUs. fbdev is unaccelerated, and won't support most common
> widescreen display modes. Some apps won't run on it. I don't think Gnome will 
> even
> start using it. Using fbdev you can expect your PC to feel like it's running a
> single core at 233MHz instead of 2000MHz or more on multiple cores.

I was afraid of this, yes.

> I don't know that I've ever migrated an installation using SDDM to another PC
> using a majorly different GPU. I use TDM or KDM3 on most installations, with a
> rare few on LightDM or SDDM, whose themes I always have extreme negative
> appreciation for.

Somehow the Live CDs must be doing something that works here.  I guess
it might be interesting to see what Debian Live KDE does on this box!

John

Re: Startx works, but sddm/lightdm/xdm doesn't

[Felix Miata]

John Goerzen composed on 2022-02-28 22:11 (UTC-0600):

> Interestingly, purging xserver-xorg-video-nouveau didn't change
> anything. 

That means you must have been /using/ the modesetting DIX driver.

> However, removing modesetting_drv.so from
> /usr/lib/xorg/modules/drivers did.  That solved the problem.

> But it didn't switch to nouveau; it went to fbdev.

You likely created a new problem. modesetting_drv.so is the default DIX for AMD,
Intel and NVidia GPUs. fbdev is unaccelerated, and won't support most common
widescreen display modes. Some apps won't run on it. I don't think Gnome will 
even
start using it. Using fbdev you can expect your PC to feel like it's running a
single core at 233MHz instead of 2000MHz or more on multiple cores.

I don't know that I've ever migrated an installation using SDDM to another PC
using a majorly different GPU. I use TDM or KDM3 on most installations, with a
rare few on LightDM or SDDM, whose themes I always have extreme negative
appreciation for.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

On Mon, Feb 28 2022, Felix Miata wrote:

> There are two nouveau drivers:
>
>   kernel device
>   display device
>   modesetting
>   nouveau
>
> Both possible full-function display device drivers depend on the nouveau 
> kernel
> driver (module). inxi -Gayz will show both. Try switching from the one in 
> current
> use to the other. Adding or purging xserver-xorg-video-nouveau is typically 
> the
> simplest way to switch between them. /etc/X11/xorg.conf.d/ can also be used to
> make the switch by explicitly declaring the chosen driver. The in-use display
> driver is announced in roughly half the lines in each Xorg.#.log.

Interestingly, purging xserver-xorg-video-nouveau didn't change
anything.  However, removing modesetting_drv.so from
/usr/lib/xorg/modules/drivers did.  That solved the problem.

But it didn't switch to nouveau; it went to fbdev.

But, since I also want to boot this drive on other machines that need
it, I can't just leave it that way.  It also leaves open the question of
why it worked fine in startx, or after logging in with sddm, which is
darn weird to me.

> Try disabling Plymouth, appending one of the following to the end of the linu 
> line
> after striking the E key at the Grub menu:

Thanks for the tip; no change there (I wasn't using the graphical stuff
anyhow).

> If none help, try appending your display's native mode & refresh instead, 
> e.g.:
>
>   video=1920x1080@60
>
> If this works, likely an edit to /etc/default/grub about graphics handling or
> theme, and regeneration of /boot/grub/grub.cfg, is indicated.

It's also already getting that right from EDID, so I'm pretty sure
that's not the issue.

Thanks again!

John

Re: Startx works, but sddm/lightdm/xdm doesn't

[Nicholas Geovanis]

On Mon, Feb 28, 2022, 3:43 PM John Goerzen  wrote:

> Hi,
>
> I have a system with a GeForce 1050 Ti on bullseye.
>
> On this system, if I log in as a regular user and run startx, everything
> works fine; KDE Plasma comes up and it's all good.
>
> But sddm doesn't work.  In fact, when it starts, it causes my monitor to
> go "no signal".  Oddly, though, if I can log in blindly, then once I hit
> enter after putting in my password, KDE will come up and work like it
> should.
>
> I also tried lightdm and xdm.  Both of them also had "no signal" when
> starting.
>
> It is using the nouveau driver.  There are no errors in Xorg.0.log,
> journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
> other graphics adapter.  xrandr on the sddm session shows it detected
> the appropriate output at the appropriate resolution.  Xorg.0.log looks
> completely appropriate; detecting devices, setting them up, etc.
>
> If I boot the same drive on a different box with Intel graphics, sddm
> works fine.
>
> This is a fresh bullseye install.
>
> A am utterly baffled; I'd think at least xdm should work!
>

I had something similar happen with Debian 8 a long time ago. It turned out
to be because the driver/firmware/grafx-chipset had the wrong idea about
the monitor's available resolutions and modes. It was using too high a
resolution.

Thanks,
>
> John
>
>

Re: Startx works, but sddm/lightdm/xdm doesn't

[Felix Miata]

John Goerzen composed on 2022-02-28 15:43 (UTC-0600):

> I have a system with a GeForce 1050 Ti on bullseye.

> On this system, if I log in as a regular user and run startx, everything
> works fine; KDE Plasma comes up and it's all good.

> But sddm doesn't work.  In fact, when it starts, it causes my monitor to
> go "no signal".  Oddly, though, if I can log in blindly, then once I hit
> enter after putting in my password, KDE will come up and work like it
> should.

> I also tried lightdm and xdm.  Both of them also had "no signal" when
> starting.

> It is using the nouveau driver. 

There are two nouveau drivers:

kernel device
display device
modesetting
nouveau

Both possible full-function display device drivers depend on the nouveau kernel
driver (module). inxi -Gayz will show both. Try switching from the one in 
current
use to the other. Adding or purging xserver-xorg-video-nouveau is typically the
simplest way to switch between them. /etc/X11/xorg.conf.d/ can also be used to
make the switch by explicitly declaring the chosen driver. The in-use display
driver is announced in roughly half the lines in each Xorg.#.log.

> There are no errors in Xorg.0.log,
> journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
> other graphics adapter.  xrandr on the sddm session shows it detected
> the appropriate output at the appropriate resolution.  Xorg.0.log looks
> completely appropriate; detecting devices, setting them up, etc.

> If I boot the same drive on a different box with Intel graphics, sddm
> works fine.

> This is a fresh bullseye install.

> A am utterly baffled; I'd think at least xdm should work!
Try disabling Plymouth, appending one of the following to the end of the linu 
line
after striking the E key at the Grub menu:

plymouth=0
noplymouth
plymouth.enable=0

If none help, try appending your display's native mode & refresh instead, e.g.:

video=1920x1080@60

If this works, likely an edit to /etc/default/grub about graphics handling or
theme, and regeneration of /boot/grub/grub.cfg, is indicated.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Startx works, but sddm/lightdm/xdm doesn't

[John Goerzen]

Hi,

I have a system with a GeForce 1050 Ti on bullseye.

On this system, if I log in as a regular user and run startx, everything
works fine; KDE Plasma comes up and it's all good.

But sddm doesn't work.  In fact, when it starts, it causes my monitor to
go "no signal".  Oddly, though, if I can log in blindly, then once I hit
enter after putting in my password, KDE will come up and work like it
should.

I also tried lightdm and xdm.  Both of them also had "no signal" when
starting.

It is using the nouveau driver.  There are no errors in Xorg.0.log,
journalctl, dmesg, syslog, or the xsession log.  lspci doesn't show any
other graphics adapter.  xrandr on the sddm session shows it detected
the appropriate output at the appropriate resolution.  Xorg.0.log looks
completely appropriate; detecting devices, setting them up, etc.

If I boot the same drive on a different box with Intel graphics, sddm
works fine.

This is a fresh bullseye install.

A am utterly baffled; I'd think at least xdm should work!

Thanks,

John

systemctl can not start X, but startx can.

[Chris Capon]

Hi.
During a recent update to xorg 1:7.7+19 my graphical environment stopped
initializing on reboot.

sudo systemctl isolate graphical.target
fails to initialize the graphics card with these messages:

[   340.372] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA GPU at
PCI:5:0:0.  Please
[   340.372] (EE) NVIDIA(GPU-0): check your system's kernel log for
additional error
[   340.372] (EE) NVIDIA(GPU-0): messages and refer to Chapter 8:
Common Problems in the
[   340.372] (EE) NVIDIA(GPU-0): README for additional information.
[   340.372] (EE) NVIDIA(GPU-0): Failed to initialize the NVIDIA graphics
device!
[   340.372] (EE) NVIDIA(0): Failing initialization of X screen 0


on the other hand:
startx
initializes it with no problems.

[   150.685] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:5:0:0
[   150.685] (--) NVIDIA(0): CRT-0
[   150.685] (--) NVIDIA(0): CRT-1
[   150.685] (--) NVIDIA(0): DFP-0 (boot)
[   150.685] (--) NVIDIA(0): DFP-1
[   150.685] (--) NVIDIA(0): DFP-2
[   150.687] (II) NVIDIA(0): NVIDIA GPU GeForce GT 430 (GF108) at PCI:5:0:0
(GPU-0)
[   150.687] (--) NVIDIA(0): Memory: 1048576 kBytes
[   150.687] (--) NVIDIA(0): VideoBIOS: 70.08.29.00.30
[   150.687] (II) NVIDIA(0): Detected PCI Express Link width: 16X


I haven't been able to find additional info on what the problem is.

Attached are the two complete Xorg.log files.

Can anyone help?
Thanks.


Xorg.0.log.isolate
Description: Binary data


Xorg.0.log.startx
Description: Binary data

Re: is this a bug of startx?

[Greg Wooledge]

On Sun, Feb 18, 2018 at 03:20:11AM +, Long Wind wrote:
> maybe few users still use startx?

Depends on where you draw your samples from.  If you consider "all
Debian users", then you are probably correct.  The vast majority of
users probably use one of the Display Managers.

If you consider "those who respond to help requests on debian-user",
I think the fraction of those who use startx is significantly higher.

I use startx.

> i can't run startxthen i create .xinitrc:
> xterm &
> twm
> and it solve the problem
> it seems that i must have a local .xinitrc

In the absence of a ~/.xsession or ~/.xinitrc file, startx should
default to running the system's default Xsession, which should try
to run /usr/bin/x-session-manager (if that exists), or else
/usr/bin/x-window-manager (if that exists).

Did installing twm set your /etc/alternatives/x-window-manager symlink
to point to /usr/bin/twm?  If not, then perhaps that's the reason it
failed.

Nevertheless, I think most startx users do end up creating their own
~/.xsession or ~/.xinitrc file, just because they tend to be the type
who like customizing things.

Re: is this a bug of startx?

[David Wright]

On Sun 18 Feb 2018 at 03:20:11 (+), Long Wind wrote:
> maybe few users still use startx?at first i found some strange problems with 
> stretchand unable to run X
> now i'm able to describe the problemafter i install twm , i can't run 
> startxthen i create .xinitrc:
> xterm &
> twm
> and it solve the problem
> it seems that i must have a local .xinitrc

As mentioned in another thread just now, I run X with startx.
I've always stuck to the Debian Way™ which means using ~/.xsession
rather than ~/.xinitrc.

Stripped down to the essentials, my ~/.xsession consists of:

#!/bin/sh
exec /usr/bin/fvwm >| $HOME/.fvwm-stdout 2>| $HOME/.fvwm-stderr & WMPID=$!
xterm …
xterm …
swisswatch -title local -noshape
xconsole -name console -file /dev/xconsole -exitOnFail
xclock -strftime "%a %d"
# and so on
# wait for the window manager in the background to die
wait $WMPID

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

Felix Miata composed on 2017-10-17 17:40 (UTC-0400):

> Brian composed on 2017-10-17 20:54 (UTC+0100):

>> On Tue 17 Oct 2017 at 15:30:36 -0400, Felix Miata wrote:

>>> Startx continues to work more or less as always in Mageia, just as in 
>>> Debian,
>>> though not necessarily perfectly:
>>> https://bugs.mageia.org/show_bug.cgi?id=15662

>> Not "more or less" in Debian". Just rock solid,

> You might be right, but you might not be. I don't suppose you looked at that
> bug, because the bug is actually upstream, about gfxchips installed in PCs on
> which I have no version of Debian installed to confirm or deny broader impact
> than on just Mageia and Fedora. Without any stronger reason to add Debian, 
> both
> the machines and the gfxchips are too old for me to bother trying.

Upstream bug just updated to include 9.2:
https://bugs.freedesktop.org/show_bug.cgi?id=90572
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

David Wright composed on 2017-10-21 11:34 (UTC-0500):

> On Fri 20 Oct 2017 at 04:42:53 (-0400), Felix Miata wrote:

>> It's not resolutions per se, but resolution increases have considerable 
>> tendency
>> to carry higher pixel density, notwithstanding the considerable average 
>> density
>> differences between laptop displays and desktop displays. The problem comes 
>> from
>> several sources:

> … which have to do with how X is configured, not whether you use a DE.
> Your point about the size of the "default" size of xterm (where "default"
> depends where you're coming from) is easily changed in any WM 

A point I was trying to make was that "easily" it is not, unless your eyes are
as good as, and your hardware matches that of, those who selected the defaults
provided by the applicable software. Shrinking the size can be many orders of
magnitude easier than bringing up to a legible size, because making a change
depends on discovering and utilizing the process of change being legible in the
first place.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[David Wright]

On Fri 20 Oct 2017 at 04:42:53 (-0400), Felix Miata wrote:
> David Wright composed on 2017-10-19 17:00 (UTC-0500):
> 
> > On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote:
> 
> >> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 
> >> or
> >> more applications is easier for most people than remembering the name and 
> >> any
> >> required startup options to type, both for those uncommonly used, and even 
> >> for
> >> the commonly used ones if there are more than a scant few such. 2 or 3 or 4
> >> clicks to start one up is typically easier than typing 4, 5, 6, 7 or more
> >> characters, or searching command history more than a few entries back.
> 
> > Do you need a DE to do that? What's the difference between that and
> > the Debian menus that I occasionally use? 
> 
> Don't I?

No.

> One of the few positive paradigms to come out of Redmond was the button
> at the lower left corner of the screen to open a tree-structured list of
> applications and utilities available to run. I've yet to see a materially 
> better
> one that that derived from it for KDE2 or 3 that added a search box.

Which is what the Debian menu gives you. If you want the tree to look like
the windows® one, just initiate it (for me it's a left click in the root
window, ie outside any application's window) near the lower left corner.

> >> It's a
> >> nice bonus in some DEs that automatically remember and reopen apps, their
> >> content states, and their window sizes and positions.
> 
> > That's more debatable. Some people like that, some like me prefer
> > a particular setup whenever I start X, some use Place with Mouseclick,
> > etc. But there appear to be separate packages to handle this, like
> > lxsession and devilspie. 
> 
> I need all the help I can get to pickup where I left off when interrupted and
> forced to end the session before the WIP can be completed.
> 
> >> For some, the microscopic default text size and fractional default 
> >> proportion of
> >> screen area (80x25, using as little as 1/16 or less of total screen space) 
> >> of
> >> xterm windows impedes their use for anything.
> 
> > I've seen reports of fonts getting tinier as resolutions increase,
> > and not just on linux. I don't know how hard or easy it is to provide
> > sensible defaults for every application on every system, and in any
> > case circumstances vary. People with poor sight want large characters,
> > others want more characters on the screen. In the specific case of
> > xterm, I want and have both, and different fonts too, just by setting
> > different commandline options and Xresources. 
> 
> It's not resolutions per se, but resolution increases have considerable 
> tendency
> to carry higher pixel density, notwithstanding the considerable average 
> density
> differences between laptop displays and desktop displays. The problem comes 
> from
> several sources:

… which have to do with how X is configured, not whether you use a DE.
Your point about the size of the "default" size of xterm (where "default"
depends where you're coming from) is easily changed in any WM, and the
ability to correct or circumvent it doesn't depend on running a DE.

In the earlier thread I alluded to, there was no need (with
installation of a couple of packages and a font change) for
the OP even to bother with running X to fix their original
problem.

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

David Wright composed on 2017-10-19 17:00 (UTC-0500):

> On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote:

>> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 or
>> more applications is easier for most people than remembering the name and any
>> required startup options to type, both for those uncommonly used, and even 
>> for
>> the commonly used ones if there are more than a scant few such. 2 or 3 or 4
>> clicks to start one up is typically easier than typing 4, 5, 6, 7 or more
>> characters, or searching command history more than a few entries back.

> Do you need a DE to do that? What's the difference between that and
> the Debian menus that I occasionally use? 

Don't I? One of the few positive paradigms to come out of Redmond was the button
at the lower left corner of the screen to open a tree-structured list of
applications and utilities available to run. I've yet to see a materially better
one that that derived from it for KDE2 or 3 that added a search box.

>> It's a
>> nice bonus in some DEs that automatically remember and reopen apps, their
>> content states, and their window sizes and positions.

> That's more debatable. Some people like that, some like me prefer
> a particular setup whenever I start X, some use Place with Mouseclick,
> etc. But there appear to be separate packages to handle this, like
> lxsession and devilspie. 

I need all the help I can get to pickup where I left off when interrupted and
forced to end the session before the WIP can be completed.

>> For some, the microscopic default text size and fractional default 
>> proportion of
>> screen area (80x25, using as little as 1/16 or less of total screen space) of
>> xterm windows impedes their use for anything.

> I've seen reports of fonts getting tinier as resolutions increase,
> and not just on linux. I don't know how hard or easy it is to provide
> sensible defaults for every application on every system, and in any
> case circumstances vary. People with poor sight want large characters,
> others want more characters on the screen. In the specific case of
> xterm, I want and have both, and different fonts too, just by setting
> different commandline options and Xresources. 

It's not resolutions per se, but resolution increases have considerable tendency
to carry higher pixel density, notwithstanding the considerable average density
differences between laptop displays and desktop displays. The problem comes from
several sources:

1-Inconsistency from developers, some who size in pixels, and some who size in
points. Points are resolution dependent, so are in principle unaffected by
density. Pixels are entirely independent, so the higher the density, the smaller
the container into which a fixed number of pixels fit.

2-As you imply, some want a bigger screen to provide for more stuff to fit,
while others want the same stuff to simply be bigger, and yet others want a
mixture of both.

3-Overall, computer developers are a youthful bunch, so their eyesight is better
than average, while their collective wisdom has a lot of growing yet to do. Try
to imagine anyone getting into computer development whose eyesight is materially
poorer than average. That can be lot of pain to suffer day-in, day-out working
on screens designed for use by people with better vision. There simply isn't
much of it happening.

4-Hardware manufacturers are caught in the middle. They don't stay in business
without making a profit. They know how to make higher quality product, but
they're stifled by returns from those who after getting the product home
determine their bigger screen makes things tinier and harder to use. So they
limit the selection of high quality product, producing mostly native resolutions
in physical sizes that produce densities near the arbitrary software standard of
96 DPI. 1366x768 in this day and age is hard to imagine, given that 1024x768
dates back over three decades, and 1080p dates back more than two decades. Yet,
this is the resolution of both a typical 32" TV screen and a laptop of 15".
Large PC screens ought to have an *average* density of at least 200 DPI by now,
and have the software automatically doing the computations necessary to allow
people to enjoy better quality and overall experience.

5-Much of development incorporates overwhelming perfectionism, a need to have
results look "just right", not necessarily with any wisdom of the perspective of
those with different eyes. Over-control is typical, limiting or even eliminating
the ability to accommodate differing capabilities and/or environments. Computers
are good at calculating, but developers routinely limit that utility. One of the
most blatant of such constraints can be seen in Xorg:

https://bugs.freedesktop.org/show_bug.cgi?id=41115
Please add option to avoid forcing of 96dpi

an offshoot from:
https://bugs.freedesktop.org/show_bug.cgi?id=23705
xserver forces 96 DPI on randr-1.2-capable drivers, overriding correct 
autodetection

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[David Wright]

On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote:
> Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200):
> 
> > I never understood the need for desktop managers. I use Debian since
> > hamm and Linux/Unix since 1995. My take is that desktop managers are
> > for people more used to microsoft OS'. Why do I need to click on
> > something when the xterm I type in can call any program I need?... 
> 
> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 or
> more applications is easier for most people than remembering the name and any
> required startup options to type, both for those uncommonly used, and even for
> the commonly used ones if there are more than a scant few such. 2 or 3 or 4
> clicks to start one up is typically easier than typing 4, 5, 6, 7 or more
> characters, or searching command history more than a few entries back.

Do you need a DE to do that? What's the difference between that and
the Debian menus that I occasionally use?

> It's a
> nice bonus in some DEs that automatically remember and reopen apps, their
> content states, and their window sizes and positions.

That's more debatable. Some people like that, some like me prefer
a particular setup whenever I start X, some use Place with Mouseclick,
etc. But there appear to be separate packages to handle this, like
lxsession and devilspie.

> For some, the microscopic default text size and fractional default proportion 
> of
> screen area (80x25, using as little as 1/16 or less of total screen space) of
> xterm windows impedes their use for anything.

I've seen reports of fonts getting tinier as resolutions increase,
and not just on linux. I don't know how hard or easy it is to provide
sensible defaults for every application on every system, and in any
case circumstances vary. People with poor sight want large characters,
others want more characters on the screen. In the specific case of
xterm, I want and have both, and different fonts too, just by setting
different commandline options and Xresources. I can change them on
the fly too, as I can also for VCs. I don't degrade the resolution
to make them bigger (as suggested earlier in the month). It's mainly
just a matter at looking at configurations.

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Oct 18, 2017 at 07:22:53PM -0400, Felix Miata wrote:
> Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200):
> 
> > I never understood the need for desktop managers. I use Debian since
> > hamm and Linux/Unix since 1995. My take is that desktop managers are
> > for people more used to microsoft OS'. Why do I need to click on
> > something when the xterm I type in can call any program I need?... 
> 
> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 or
> more applications is easier for most people than remembering the name and any
> required startup options to type, both for those uncommonly used, and even for
> the commonly used ones if there are more than a scant few such.

All generalizations suck.

My experience is that there's some tension between "easy to learn for a
newcomer" and "ergonomic for an experienced user". And my hunch is that,
in the last decennium, the "newcomer" part has been overemphasized to
a paradoxical level, where even the newcomers aren't treated very well
(an over-padded desktop environment which behaves erratically because
their creators don't master its exploding complexity[1] *is*
user-unfriendly, after all).

I think we should strive for a continuum which welcomes newcomers but
offers them a path towards experienced users they may follow if they
wish. Baroque complexity and arbitrary barriers (here users, there
sysadmins, yonder app programmers and far out, system programmers)
don't help.

The worst part is that nowadays there are strong financial incentives
in keeping users dumb. Watch the silos of Apple, Microsoft, Google,
Facebook et al. to see what I mean.

Cheers

[1] And no, I don't think Gnome's or KDE's creators are idiots, on
   the contrary. But I definitely believe they've fallen to one of
   the programmers "virtues" (Larry Wall): hubris.

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlnoRfkACgkQBcgs9XrR2kb9hgCcClRTCCRavUMeLvzRkFFRCz9X
GaUAn00so0+WlID82DN3ZNLAhjHHaoLp
=lEYB
-END PGP SIGNATURE-

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200):

> I never understood the need for desktop managers. I use Debian since
> hamm and Linux/Unix since 1995. My take is that desktop managers are
> for people more used to microsoft OS'. Why do I need to click on
> something when the xterm I type in can call any program I need?... 

Finding a wanted app to run from a classified tree list of 30 or 40 or 50 or
more applications is easier for most people than remembering the name and any
required startup options to type, both for those uncommonly used, and even for
the commonly used ones if there are more than a scant few such. 2 or 3 or 4
clicks to start one up is typically easier than typing 4, 5, 6, 7 or more
characters, or searching command history more than a few entries back. It's a
nice bonus in some DEs that automatically remember and reopen apps, their
content states, and their window sizes and positions.

For some, the microscopic default text size and fractional default proportion of
screen area (80x25, using as little as 1/16 or less of total screen space) of
xterm windows impedes their use for anything.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Jimmy Johnson]

On 10/17/2017 11:42 AM, Brian wrote:

On Tue 17 Oct 2017 at 13:56:37 -0400, Greg Wooledge wrote:


On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:

On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:

On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexan:der V. Makartsev wrote:

Deprecated doesn't mean it doesn't exist or work anymore at all, it
means it isn't supported anymore and should not be used.
Look it up, it was deprecated for quite some time.



  https://forums.mageia.org/en/viewtopic.php?f=8=8737


So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
had ever heard of it before today) that might carry some weight with me.

Just curious, what are Mageia users expected to use instead of startx if
they want to start a traditional X session from a console?  Or is that
no longer a supported configuration at all?  (By traditional, I mean
a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
window manager you prefer.)

Did they simply throw every window manager under the bus and say "Nope,
sorry, you gotta run a desktop environment now"?


That is possible, but I'm not going to invest the time in finding out.
The purpose of my post was to point out Alexan:der V. Makartsev's use
of a post from elsewhere without acknowledgement and indicate Debian's
attitude towards startx (without going into detail).

I use startx. My users get xdm because they have poor memories for the
names of commands and like pretty pictures.


I use startx a lot because I install a lot of systems from a base 
install and after installing drivers, firmware and desktop I can startx 
and do my desktop setup before rebooting or logging out.  I'm sure there 
are other ways like starting sddm or start plasma or? But I know and use 
startx.

--
Jimmy Johnson

Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Ionel Mugurel Ciobîcă]

> 
> [ It might be clearer to write "Desktop Environment" (or DE) instead
> of "desktop manager" because of the latter's having the same initials
> as Display Manager (or DM). ]

You are right.

> That said, what are the advantages of running a DM in your case,
> compared with using startx? One big disadvantage has already been
> mentioned (that Linux Consoles rely on particular drivers far less
> than X does).
> 

I use more than one X session. startx would work just as good but then
I will not know how to commute between sessions. The Ctrl-Alt-Fx or
Shift-Fx would not work since startx starts the X on a higher
terminal... If I press Ctrl-Alt-F1 I do not have a way to return to X.
I have to kill the X and type startx again. I never studied startx
carefully, I just rely on xdm that I fully configured. 

Ionel

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[David Wright]

On Wed 18 Oct 2017 at 20:47:08 (+0200), Ionel Mugurel Ciobîcă wrote:
> On 18-10-2017, at 22h 17'14", Richard Hector wrote about "Re: removing of 
> sddm (debian 9 -kde5) to start in console mode then startx to start kde5"
> > > 
> > > Did they simply throw every window manager under the bus and say "Nope,
> > > sorry, you gotta run a desktop environment now"?
> > 
> > Now I'm curious - assuming Mageia has deprecated startx, how does that
> > impact using a plain window manager? It's perfectly possible to run twm
> > or whatever when logging in to a display manager, no? I'm sure I used to
> > do that with xdm and icewm.
> > 
> 
> I never ran an desktop manager, nor I used startx. I always used a
> dm (xdm, kdm, etc.) and fvwm. In my ~/.xsession file the last line
> is "fvwm2" (no quotes). Before that I set the background, set the
> keyboard (with xmodmap), start the ssh agent, start rclock, etc.
> 
> I think kdm has an option to overlook ~/.xsession and start another
> wm. Set it to default, which means "read the config files".
> 
> I never understood the need for desktop managers. I use Debian since
> hamm and Linux/Unix since 1995. My take is that desktop managers are
> for people more used to microsoft OS'. Why do I need to click on
> something when the xterm I type in can call any program I need?...

[ It might be clearer to write "Desktop Environment" (or DE) instead
of "desktop manager" because of the latter's having the same initials
as Display Manager (or DM). ]

That said, what are the advantages of running a DM in your case,
compared with using startx? One big disadvantage has already been
mentioned (that Linux Consoles rely on particular drivers far less
than X does).

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Ionel Mugurel Ciobîcă]

On 18-10-2017, at 22h 17'14", Richard Hector wrote about "Re: removing of sddm 
(debian 9 -kde5) to start in console mode then startx to start kde5"
> > 
> > Did they simply throw every window manager under the bus and say "Nope,
> > sorry, you gotta run a desktop environment now"?
> 
> Now I'm curious - assuming Mageia has deprecated startx, how does that
> impact using a plain window manager? It's perfectly possible to run twm
> or whatever when logging in to a display manager, no? I'm sure I used to
> do that with xdm and icewm.
> 

I never ran an desktop manager, nor I used startx. I always used a
dm (xdm, kdm, etc.) and fvwm. In my ~/.xsession file the last line
is "fvwm2" (no quotes). Before that I set the background, set the
keyboard (with xmodmap), start the ssh agent, start rclock, etc.

I think kdm has an option to overlook ~/.xsession and start another
wm. Set it to default, which means "read the config files".

I never understood the need for desktop managers. I use Debian since
hamm and Linux/Unix since 1995. My take is that desktop managers are
for people more used to microsoft OS'. Why do I need to click on
something when the xterm I type in can call any program I need?...

Ionel

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Richard Hector]

On 18/10/17 06:56, Greg Wooledge wrote:
> On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:
>> On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:
>>> On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:
>>>> Deprecated doesn't mean it doesn't exist or work anymore at all, it
>>>> means it isn't supported anymore and should not be used.
>>>> Look it up, it was deprecated for quite some time.
> 
>>  https://forums.mageia.org/en/viewtopic.php?f=8=8737 
> 
> So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
> had ever heard of it before today) that might carry some weight with me.
> 
> Just curious, what are Mageia users expected to use instead of startx if
> they want to start a traditional X session from a console?  Or is that
> no longer a supported configuration at all?  (By traditional, I mean
> a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
> window manager you prefer.)
> 
> Did they simply throw every window manager under the bus and say "Nope,
> sorry, you gotta run a desktop environment now"?

Now I'm curious - assuming Mageia has deprecated startx, how does that
impact using a plain window manager? It's perfectly possible to run twm
or whatever when logging in to a display manager, no? I'm sure I used to
do that with xdm and icewm.

Richard



signature.asc
Description: OpenPGP digital signature

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

Brian composed on 2017-10-17 20:54 (UTC+0100):

> On Tue 17 Oct 2017 at 15:30:36 -0400, Felix Miata wrote:

>> Mageia is among those installed on most of my multiboot PCs.

>> Mageia's contributor base is among the more limited among top 20 distros. It
>> provides limited deviation from upstream. Thus, if upstream says something is
>> deprecated, Mageia either claims it's deprecated, or is silent on the 
>> subject.

>> Startx continues to work more or less as always in Mageia, just as in Debian,
>> though not necessarily perfectly:
>> https://bugs.mageia.org/show_bug.cgi?id=15662

> Not "more or less" in Debian". Just rock solid,
You might be right, but you might not be. I don't suppose you looked at that
bug, because the bug is actually upstream, about gfxchips installed in PCs on
which I have no version of Debian installed to confirm or deny broader impact
than on just Mageia and Fedora. Without any stronger reason to add Debian, both
the machines and the gfxchips are too old for me to bother trying.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

Thank you very much Alexander for your help,because I had switched to debian 8 
again for three months because I didn't know how to boot in console mode debian 
9.so I have just installed again debian 9 and with  it boots in multi user mode(console) so I am happy :-)my 
problem is solved...
best regards
Stéphane 

Le Mardi 17 octobre 2017 21h07, Alexander V. Makartsev <avbe...@gmail.com> 
a écrit :
 

  Stephane asked for a help and got it. I also given him the best advice based 
on my experience with "startx" shell script.
 "$ sudo systemctl start display-manager.service" is most fail-safe command to 
start desktop environment from console session on any systemd-adopted distro.
 
 Here is some example disadvantages of using "startx":
 * "startx" often requires user to go extra mile and configure or keep track of 
changes in ~/.xinitrc ~/.xsessionrc scripts.
 * If you use Xfce and will start it by "startx" you will pass on display 
manager and greeter, and if you manually lock your session at some point with 
xflock4 you will get black screen without any way of unlocking it other than 
logging into another tty and doing it from console. This is understandable, 
because by using "startx" with Xfce you passed on session and seat management.
 * Some users could fire "sudo startx" at some point and give themselves a good 
chance to ruin their system.
 You can use whatever you want, as I already said it doesn't mean "startx" 
doesn't exist or work anymore, and you have to understand there is many ways to 
do something in Linux, but just any way doesn't always means it is the right 
way. To all respectable people, go ahead and grab pitchforks and torches there 
is somebody with different\wrong opinion on The Internets.
  
  
 On 17.10.2017 19:39, Greg Wooledge wrote:
  
 On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote:
 
 Deprecated doesn't mean it doesn't exist or work anymore at all, it
means it isn't supported anymore and should not be used.
Look it up, it [startx] was deprecated for quite some time.
 
 Quoting from
https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html

==
* Only the gdm3 display manager supports running X as a non-privileged
  user in stretch. Other display managers will always run X as
  root. Alternatively, you can also start X manually as a non-root user
  on a virtual terminal via startx.

When run as a regular user, the Xorg log will be available from
~/.local/share/xorg/.
==

Looks supported to me.
 
 
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 
 

   

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Brian]

On Tue 17 Oct 2017 at 15:30:36 -0400, Felix Miata wrote:

> Mageia is among those installed on most of my multiboot PCs.
> 
> Mageia's contributor base is among the more limited among top 20 distros. It
> provides limited deviation from upstream. Thus, if upstream says something is
> deprecated, Mageia either claims it's deprecated, or is silent on the subject.
> 
> Startx continues to work more or less as always in Mageia, just as in Debian,
> though not necessarily perfectly:
> https://bugs.mageia.org/show_bug.cgi?id=15662

Not "more or less" in Debian". Just rock solid,

> Since KDM has been removed from both Mageia and Stretch, killing KDM features
> not supported by GDM, LightDM or SDDM, I more often start X sessions in those
> installations using startx than otherwise (which usually means TDM).
> 
> One of my use cases for startx is need for simultaneously run X sessions
> *initialized* with unique and/or arbitrary configurations, e.g.:
> 
>   1920x1200@120DPI on :0 (default, via login greeter)
>   1440x900@108DPI on :1 (non-default, via vtty3 login)
>   1920x1200@132DPI on :2 with panning (virtual desktop) 1920x2400
> 
> If such is supported entirely from running Xorg, I have yet to find how. Such
> settings from within any running DE don't count, due to key requirements
> "initialized" and "arbitrary" that obviate starting a session, configuring via
> GUI, then restarting session with the just applied (user-specific) 
> modifications.

Am I on the wrong mailing list?

-- 
Brian.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Felix Miata]

David Wright composed on 2017-10-17 13:36 (UTC-0500):

> On Tue 17 Oct 2017 at 13:56:37 (-0400), Greg Wooledge wrote:

>> On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:

>> > On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:

>> > > On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:

>> > > > Deprecated doesn't mean it doesn't exist or work anymore at all, it
>> > > > means it isn't supported anymore and should not be used.
>> > > > Look it up, it was deprecated for quite some time.

>> >  https://forums.mageia.org/en/viewtopic.php?f=8=8737 

>> So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
>> had ever heard of it before today) that might carry some weight with me.

>> Just curious, what are Mageia users expected to use instead of startx if
>> they want to start a traditional X session from a console?  Or is that
>> no longer a supported configuration at all?  (By traditional, I mean
>> a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
>> window manager you prefer.)

> I see no evidence from a quick look at their website and the wiki
> that they support (or ever supported) X without a DE. I may be wrong;
> it's difficult to prove a negative. I'd be interested in a reference
> to a counter-example.

>> Did they simply throw every window manager under the bus and say "Nope,
>> sorry, you gotta run a desktop environment now"?

> Did they ever support WMs? If not, then they wouldn't have any reason
> to get rid of them, and what would they have used startx for. Why
> would they have any reason to deprecate it rather than just ignore it? 

Mageia is among those installed on most of my multiboot PCs.

Mageia's contributor base is among the more limited among top 20 distros. It
provides limited deviation from upstream. Thus, if upstream says something is
deprecated, Mageia either claims it's deprecated, or is silent on the subject.

Startx continues to work more or less as always in Mageia, just as in Debian,
though not necessarily perfectly:
https://bugs.mageia.org/show_bug.cgi?id=15662

Since KDM has been removed from both Mageia and Stretch, killing KDM features
not supported by GDM, LightDM or SDDM, I more often start X sessions in those
installations using startx than otherwise (which usually means TDM).

One of my use cases for startx is need for simultaneously run X sessions
*initialized* with unique and/or arbitrary configurations, e.g.:

1920x1200@120DPI on :0 (default, via login greeter)
1440x900@108DPI on :1 (non-default, via vtty3 login)
1920x1200@132DPI on :2 with panning (virtual desktop) 1920x2400

If such is supported entirely from running Xorg, I have yet to find how. Such
settings from within any running DE don't count, due to key requirements
"initialized" and "arbitrary" that obviate starting a session, configuring via
GUI, then restarting session with the just applied (user-specific) 
modifications.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Alexander V. Makartsev]

Stephane asked for a help and got it. I also given him the best advice
based on my experience with "startx" shell script.
"$ sudo systemctl start display-manager.service" is most fail-safe
command to start desktop environment from console session on any
systemd-adopted distro.

Here is some example disadvantages of using "startx":
* "startx" often requires user to go extra mile and configure or keep
track of changes in ~/.xinitrc ~/.xsessionrc scripts.
* If you use Xfce and will start it by "startx" you will pass on display
manager and greeter, and if you manually lock your session at some point
with xflock4 you will get black screen without any way of unlocking it
other than logging into another tty and doing it from console. This is
understandable, because by using "startx" with Xfce you passed on
session and seat management.
* Some users could fire "sudo startx" at some point and give themselves
a good chance to ruin their system.

You can use whatever you want, as I already said it doesn't mean
"startx" doesn't exist or work anymore, and you have to understand there
is many ways to do something in Linux, but just any way doesn't always
means it is the right way.

To all respectable people, go ahead and grab pitchforks and torches
there is somebody with different\wrong opinion on The Internets.



On 17.10.2017 19:39, Greg Wooledge wrote:
> On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote:
>> Deprecated doesn't mean it doesn't exist or work anymore at all, it
>> means it isn't supported anymore and should not be used.
>> Look it up, it [startx] was deprecated for quite some time.
> Quoting from
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html
>
> ==
> * Only the gdm3 display manager supports running X as a non-privileged
>   user in stretch. Other display managers will always run X as
>   root. Alternatively, you can also start X manually as a non-root user
>   on a virtual terminal via startx.
>
> When run as a regular user, the Xorg log will be available from
> ~/.local/share/xorg/.
> ==
>
> Looks supported to me.

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Brian]

On Tue 17 Oct 2017 at 13:56:37 -0400, Greg Wooledge wrote:

> On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:
> > On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:
> > > On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexan:der V. Makartsev wrote:
> > > > Deprecated doesn't mean it doesn't exist or work anymore at all, it
> > > > means it isn't supported anymore and should not be used.
> > > > Look it up, it was deprecated for quite some time.
> 
> >  https://forums.mageia.org/en/viewtopic.php?f=8=8737 
> 
> So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
> had ever heard of it before today) that might carry some weight with me.
> 
> Just curious, what are Mageia users expected to use instead of startx if
> they want to start a traditional X session from a console?  Or is that
> no longer a supported configuration at all?  (By traditional, I mean
> a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
> window manager you prefer.)
> 
> Did they simply throw every window manager under the bus and say "Nope,
> sorry, you gotta run a desktop environment now"?

That is possible, but I'm not going to invest the time in finding out.
The purpose of my post was to point out Alexan:der V. Makartsev's use
of a post from elsewhere without acknowledgement and indicate Debian's
attitude towards startx (without going into detail).

I use startx. My users get xdm because they have poor memories for the
names of commands and like pretty pictures.

-- 
Brian.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[David Wright]

On Tue 17 Oct 2017 at 13:56:37 (-0400), Greg Wooledge wrote:
> On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:
> > On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:
> > > On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:
> > > > Deprecated doesn't mean it doesn't exist or work anymore at all, it
> > > > means it isn't supported anymore and should not be used.
> > > > Look it up, it was deprecated for quite some time.
> 
> >  https://forums.mageia.org/en/viewtopic.php?f=8=8737 
> 
> So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
> had ever heard of it before today) that might carry some weight with me.
> 
> Just curious, what are Mageia users expected to use instead of startx if
> they want to start a traditional X session from a console?  Or is that
> no longer a supported configuration at all?  (By traditional, I mean
> a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
> window manager you prefer.)

I see no evidence from a quick look at their website and the wiki
that they support (or ever supported) X without a DE. I may be wrong;
it's difficult to prove a negative. I'd be interested in a reference
to a counter-example.

> Did they simply throw every window manager under the bus and say "Nope,
> sorry, you gotta run a desktop environment now"?

Did they ever support WMs? If not, then they wouldn't have any reason
to get rid of them, and what would they have used startx for. Why
would they have any reason to deprecate it rather than just ignore it?

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Greg Wooledge]

On Tue, Oct 17, 2017 at 06:42:04PM +0100, Brian wrote:
> On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:
> > On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:
> > > Deprecated doesn't mean it doesn't exist or work anymore at all, it
> > > means it isn't supported anymore and should not be used.
> > > Look it up, it was deprecated for quite some time.

>  https://forums.mageia.org/en/viewtopic.php?f=8=8737 

So it's deprecated in Mageia GNU/Linux?  OK.  If I were a Mageia user (or
had ever heard of it before today) that might carry some weight with me.

Just curious, what are Mageia users expected to use instead of startx if
they want to start a traditional X session from a console?  Or is that
no longer a supported configuration at all?  (By traditional, I mean
a ~/.xsession or ~/.xinitrc file that contains "exec twm" or whatever
window manager you prefer.)

Did they simply throw every window manager under the bus and say "Nope,
sorry, you gotta run a desktop environment now"?

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Brian]

On Tue 17 Oct 2017 at 11:38:40 -0500, David Wright wrote:

> On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:
> > Deprecated doesn't mean it doesn't exist or work anymore at all, it
> > means it isn't supported anymore and should not be used.
> > Look it up, it was deprecated for quite some time.
> 
> Please get a grip and provide a reference.

For what is quoted?

 https://forums.mageia.org/en/viewtopic.php?f=8=8737 

Debian has gone to quite some trouble to fit startx into all the changes
which have taken place in xorg and the init system. Kudos.

-- 
Brian.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[David Wright]

On Tue 17 Oct 2017 at 19:32:11 (+0500), Alexander V. Makartsev wrote:
> Deprecated doesn't mean it doesn't exist or work anymore at all, it
> means it isn't supported anymore and should not be used.
> Look it up, it was deprecated for quite some time.

Please get a grip and provide a reference.

> On 17.10.2017 19:16, Greg Wooledge wrote:
> > On Tue, Oct 17, 2017 at 07:05:13PM +0500, Alexander V. Makartsev wrote:
> >> I think "startx" command is deprecated now and you shouldn't use it
> >> anymore.
> > Nonsense.  Many people (including me) use it all the time.  Granted,
> > I don't use KDE.

Cheers,
David.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Jimmy Johnson]

On 10/17/2017 07:39 AM, Greg Wooledge wrote:

On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote:

Deprecated doesn't mean it doesn't exist or work anymore at all, it
means it isn't supported anymore and should not be used.
Look it up, it [startx] was deprecated for quite some time.


Quoting from
https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html

==
* Only the gdm3 display manager supports running X as a non-privileged
   user in stretch. Other display managers will always run X as
   root. Alternatively, you can also start X manually as a non-root user
   on a virtual terminal via startx.

When run as a regular user, the Xorg log will be available from
~/.local/share/xorg/.
==

Looks supported to me.


+1
--
Jimmy Johnson

Debian Buster - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Greg Wooledge]

On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote:
> Deprecated doesn't mean it doesn't exist or work anymore at all, it
> means it isn't supported anymore and should not be used.
> Look it up, it [startx] was deprecated for quite some time.

Quoting from
https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html

==
* Only the gdm3 display manager supports running X as a non-privileged
  user in stretch. Other display managers will always run X as
  root. Alternatively, you can also start X manually as a non-root user
  on a virtual terminal via startx.

When run as a regular user, the Xorg log will be available from
~/.local/share/xorg/.
==

Looks supported to me.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Alexander V. Makartsev]

Deprecated doesn't mean it doesn't exist or work anymore at all, it
means it isn't supported anymore and should not be used.
Look it up, it was deprecated for quite some time.


On 17.10.2017 19:16, Greg Wooledge wrote:
> On Tue, Oct 17, 2017 at 07:05:13PM +0500, Alexander V. Makartsev wrote:
>> I think "startx" command is deprecated now and you shouldn't use it
>> anymore.
> Nonsense.  Many people (including me) use it all the time.  Granted,
> I don't use KDE.
>

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Greg Wooledge]

On Tue, Oct 17, 2017 at 07:05:13PM +0500, Alexander V. Makartsev wrote:
> I think "startx" command is deprecated now and you shouldn't use it
> anymore.

Nonsense.  Many people (including me) use it all the time.  Granted,
I don't use KDE.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

OK thank you AlexanderI will try this...
bests regards
stephane
 

Le Mardi 17 octobre 2017 16h05, Alexander V. Makartsev <avbe...@gmail.com> 
a écrit :
 

  I think "startx" command is deprecated now and you shouldn't use it anymore. 
Right way to start DE is by starting display manager service.
 This command should work in your case:
     $ sudo systemctl start sddm.service
 
 
 
 On 17.10.2017 18:55, Stephane L wrote:
  
  Hi, Alexander I Want to boot debian 9 in multi user mode (console),then do 
something then and then to startx kde5/xorg with startx as I do with 
debian8/kde4
   
 
  Le Mardi 17 octobre 2017 14h46, Alexander V. Makartsev 
<avbe...@gmail.com> a écrit :
  
 
What are you trying to archieve? If you want to start DE you better launch 
it by starting your display manager (gdm in my case):
     $ sudo systemctl start gdm.service
 
 
  On 17.10.2017 17:24, Stephane L wrote:
  
 do I need too to make a .xinitrc with something like /usr/bin/startkde ? 
  
 
  Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev 
<avbe...@gmail.com> a écrit :
  
 
Assuming you have systemd, you have to change final target from  graphical 
to multi-user.
 This shows possible targets:
     $ sudo systemctl list-units --type=target 
 
 This will show what target is default:
     $ sudo systemctl get-default
 
 This will set default target to "console mode" you want:
     $ sudo systemctl set-default multi-user.target
 
 This will redo the changes if you ever will want to start DE  by default:
     $ sudo systemctl set-default graphical.target
 
 You have to reboot to apply changes.
 
 
 
  On 17.10.2017 16:59, Stephane L wrote:
  
  Hi I have tried to remove sddm from /etc/init.d but  it starts always with 
sddm.I want to boot my debian 9 in console mode  and do startx to launch kde5 
as I do with debian 8  and kde4.does anyone know exactly how to do that ?  
  
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

   
 
  
  
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

   
 
  
 
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

 

   

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Alexander V. Makartsev]

I think "startx" command is deprecated now and you shouldn't use it
anymore. Right way to start DE is by starting display manager service.
This command should work in your case:
    $ sudo systemctl start sddm.service



On 17.10.2017 18:55, Stephane L wrote:
> Hi, Alexander
> I Want to boot debian 9 in multi user mode (console),then do something
> then and then to startx kde5/xorg with startx as I do with debian8/kde4
>
>
> Le Mardi 17 octobre 2017 14h46, Alexander V. Makartsev
> <avbe...@gmail.com> a écrit :
>
>
> What are you trying to archieve? If you want to start DE you better
> launch it by starting your display manager (gdm in my case):
>     $ sudo systemctl start gdm.service
>
>
> On 17.10.2017 17:24, Stephane L wrote:
>> do I need too to make a .xinitrc with something like /usr/bin/startkde ?
>>
>>
>> Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev
>> <avbe...@gmail.com> <mailto:avbe...@gmail.com> a écrit :
>>
>>
>> Assuming you have systemd, you have to change final target from
>> graphical to multi-user.
>> This shows possible targets:
>>     $ sudo systemctl list-units --type=target
>>
>> This will show what target is default:
>>     $ sudo systemctl get-default
>>
>> This will set default target to "console mode" you want:
>>     $ sudo systemctl set-default multi-user.target
>>
>> This will redo the changes if you ever will want to start DE by default:
>>     $ sudo systemctl set-default graphical.target
>>
>> You have to reboot to apply changes.
>>
>>
>>
>> On 17.10.2017 16:59, Stephane L wrote:
>>> Hi I have tried to remove sddm from /etc/init.d but it starts always
>>> with sddm.I want to boot my debian 9 in console mode and do startx
>>> to launch kde5 as I do with debian 8 and kde4.does anyone know
>>> exactly how to do that ?
>>
>> -- 
>> With kindest regards, Alexander.
>>
>> ⢀⣴⠾⠻⢶⣦⠀ 
>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org <https://www.debian.org/>
>> ⠈⠳⣄ 
>>
>>
>>
>
> -- 
> With kindest regards, Alexander.
>
> ⢀⣴⠾⠻⢶⣦⠀ 
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org <https://www.debian.org/>
> ⠈⠳⣄ 
>
>
>

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

Hi, AlexanderI Want to boot debian 9 in multi user mode (console),then do 
something then and then to startx kde5/xorg with startx as I do with 
debian8/kde4
 

Le Mardi 17 octobre 2017 14h46, Alexander V. Makartsev <avbe...@gmail.com> 
a écrit :
 

  What are you trying to archieve? If you want to start DE you better launch it 
by starting your display manager (gdm in my case):
     $ sudo systemctl start gdm.service
 
 
 On 17.10.2017 17:24, Stephane L wrote:
  
 do I need too to make a .xinitrc with something like /usr/bin/startkde ? 
  
 
  Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev 
<avbe...@gmail.com> a écrit :
  
 
Assuming you have systemd, you have to change final target from graphical 
to multi-user.
 This shows possible targets:
     $ sudo systemctl list-units --type=target 
 
 This will show what target is default:
     $ sudo systemctl get-default
 
 This will set default target to "console mode" you want:
     $ sudo systemctl set-default multi-user.target
 
 This will redo the changes if you ever will want to start DE by default:
     $ sudo systemctl set-default graphical.target
 
 You have to reboot to apply changes.
 
 
 
  On 17.10.2017 16:59, Stephane L wrote:
  
  Hi I have tried to remove sddm from /etc/init.d but it starts always with 
sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as 
I do with debian 8 and kde4.does anyone know exactly how to do  that ?  
  
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

   
 
  
 
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

 

   

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Alexander V. Makartsev]

What are you trying to archieve? If you want to start DE you better
launch it by starting your display manager (gdm in my case):
    $ sudo systemctl start gdm.service


On 17.10.2017 17:24, Stephane L wrote:
> do I need too to make a .xinitrc with something like /usr/bin/startkde ?
>
>
> Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev
> <avbe...@gmail.com> a écrit :
>
>
> Assuming you have systemd, you have to change final target from
> graphical to multi-user.
> This shows possible targets:
>     $ sudo systemctl list-units --type=target
>
> This will show what target is default:
>     $ sudo systemctl get-default
>
> This will set default target to "console mode" you want:
>     $ sudo systemctl set-default multi-user.target
>
> This will redo the changes if you ever will want to start DE by default:
>     $ sudo systemctl set-default graphical.target
>
> You have to reboot to apply changes.
>
>
>
> On 17.10.2017 16:59, Stephane L wrote:
>> Hi I have tried to remove sddm from /etc/init.d but it starts always
>> with sddm.I want to boot my debian 9 in console mode and do startx to
>> launch kde5 as I do with debian 8 and kde4.does anyone know exactly
>> how to do that ?
>
> -- 
> With kindest regards, Alexander.
>
> ⢀⣴⠾⠻⢶⣦⠀ 
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org <https://www.debian.org/>
> ⠈⠳⣄ 
>
>
>

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

do I need too to make a .xinitrc with something like /usr/bin/startkde ? 
 

Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev <avbe...@gmail.com> 
a écrit :
 

  Assuming you have systemd, you have to change final target from graphical to 
multi-user.
 This shows possible targets:
     $ sudo systemctl list-units --type=target 
 
 This will show what target is default:
     $ sudo systemctl get-default
 
 This will set default target to "console mode" you want:
     $ sudo systemctl set-default multi-user.target
 
 This will redo the changes if you ever will want to start DE by default:
     $ sudo systemctl set-default graphical.target
 
 You have to reboot to apply changes.
 
 
 
 On 17.10.2017 16:59, Stephane L wrote:
  
  Hi I have tried to remove sddm from /etc/init.d but it starts always with 
sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as 
I do with debian 8 and kde4.does anyone know exactly how to do that ?  
 
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

 

   

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

thank you very much alexander I will try this. 

Le Mardi 17 octobre 2017 14h11, Alexander V. Makartsev <avbe...@gmail.com> 
a écrit :
 

  Assuming you have systemd, you have to change final target from graphical to 
multi-user.
 This shows possible targets:
     $ sudo systemctl list-units --type=target 
 
 This will show what target is default:
     $ sudo systemctl get-default
 
 This will set default target to "console mode" you want:
     $ sudo systemctl set-default multi-user.target
 
 This will redo the changes if you ever will want to start DE by default:
     $ sudo systemctl set-default graphical.target
 
 You have to reboot to apply changes.
 
 
 
 On 17.10.2017 16:59, Stephane L wrote:
  
  Hi I have tried to remove sddm from /etc/init.d but it starts always with 
sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as 
I do with debian 8 and kde4.does anyone know exactly how to do that ?  
 
 -- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

 

   

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Alexander V. Makartsev]

Assuming you have systemd, you have to change final target from
graphical to multi-user.
This shows possible targets:
    $ sudo systemctl list-units --type=target

This will show what target is default:
    $ sudo systemctl get-default

This will set default target to "console mode" you want:
    $ sudo systemctl set-default multi-user.target

This will redo the changes if you ever will want to start DE by default:
    $ sudo systemctl set-default graphical.target

You have to reboot to apply changes.



On 17.10.2017 16:59, Stephane L wrote:
> Hi I have tried to remove sddm from /etc/init.d but it starts always
> with sddm.I want to boot my debian 9 in console mode and do startx to
> launch kde5 as I do with debian 8 and kde4.does anyone know exactly
> how to do that ?

-- 
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄ 

removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

[Stephane L]

Hi I have tried to remove sddm from /etc/init.d but it starts always with 
sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as 
I do with debian 8 and kde4.does anyone know exactly how to do that ?

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Brian]

On Mon 19 Jun 2017 at 14:43:08 -0400, Felix Miata wrote:

> Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400):
> 
> > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
> .
> >> I have a dozen machines with Stretch installed, most with Jessie and/or 
> >> Sid as
> >> well. Only Stretch on host big41 produces the subject problem.
> .
> > According to a previous message in this thread, it could be triggered
> > by a specific kernel boot parameter.  Can you show us "cat /proc/cmdline"
> > from big41?
> .
> Current boot, not exactly the same as the default Grub stanza, but virtually 
> the
> same as my other Stretch installations that work as expected:
> ro root=LABEL=debian9sv5 net.ifnames=0 ipv6.disable=1 noresume 
> plymouth.enable=0
> vga=791 video=1440x900@60 3

There doesn't appear to be anything there which could cause a problem,
but me being me I'd try without the fluff.

Jessie working is not a good comparison because it doesn't run X for a
user without X having root privileges. DMs working are likewise not a
good guide to a solution because they often interact gracefully with 
logind.

How about the logs? They should be in ~/.local/share/xorg. Are they?
Do they help?

-- 
Brian.

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Felix Miata]

Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400):

> On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
.
>> I have a dozen machines with Stretch installed, most with Jessie and/or Sid 
>> as
>> well. Only Stretch on host big41 produces the subject problem.
.
> According to a previous message in this thread, it could be triggered
> by a specific kernel boot parameter.  Can you show us "cat /proc/cmdline"
> from big41?
.
Current boot, not exactly the same as the default Grub stanza, but virtually the
same as my other Stretch installations that work as expected:
ro root=LABEL=debian9sv5 net.ifnames=0 ipv6.disable=1 noresume plymouth.enable=0
vga=791 video=1440x900@60 3
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Henrique de Moraes Holschuh]

On Mon, 19 Jun 2017, Brian wrote:
> The same experience as yours on tty1 to tty6. Except a couple of days
> ago when I used nouveau.modeset=0 on GRUB's linux line and got what is
> in the subject header.

Kernel modeset must be enabled non-root X to work, as you found out...

-- 
  Henrique Holschuh

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Greg Wooledge]

On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
> I have a dozen machines with Stretch installed, most with Jessie and/or Sid as
> well. Only Stretch on host big41 produces the subject problem.

According to a previous message in this thread, it could be triggered
by a specific kernel boot parameter.  Can you show us "cat /proc/cmdline"
from big41?

> # inxi -c0 -v4
> System:Host: big41 Kernel: 4.9.0-3-amd64 x86_64 (64 bit gcc: 6.3.0) 
> Console:
> tty 3
>Distro: Debian GNU/Linux 9
> Machine:   Mobo: TAR model: T41 HD v: ' ' Bios: American Megatrends v: 080015
> date: 09/22/2009
> CPU:   Dual core Intel Core2 Duo E7600 (-MCP-) cache: 3072 KB
>flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 12237
>clock speeds: max: 3066 MHz 1: 1603 MHz 2: 1603 MHz
> Graphics:  Card: Intel 4 Series Integrated Graphics Controller bus-ID: 00:02.0
>Display Server: X.org 1.19.2 drivers: (unloaded: fbdev,vesa)
>tty size: 180x56 Advanced Data: N/A for root out of X
[snip]

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Felix Miata]

Greg Wooledge composed on 2017-06-19 09:29 (UTC-0400):
.
> On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
.
>> When I try as ordinary user (on host big41), I get the subject message. 
>> Anyone
>> know how to get startx to work in Stretch, either on :0, :1 or :2, with or
>> without a greeter running (multi-user.targer vs. graphical.target)?
.
> I've been using startx on stretch for a couple months, with no problems.
> I login as my non-root user on tty1, and run 'startx', and it just works.
.
> This is on two different machines, both using Intel graphics.  Here's one
> of them:
.
I have a dozen machines with Stretch installed, most with Jessie and/or Sid as
well. Only Stretch on host big41 produces the subject problem. It has Intel
Eagle Lake X4500 video attached via HDMI. It's Jessie works as expected, while
its Sid halts at an initramfs prompt. Big41 with kernel 4.9.0-3-amd64 works as
expected for root only. Ordinary users produce subject errors only by attempting
startx. Login from TDM greeter works as expected for all users.
.
> wooledg:~$ uname -a
> Linux wooledg 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 
> GNU/Linux
> 
> wooledg:~$ lspci -nn | grep VGA
> 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
> [8086:1912] (rev 06)
> 
> wooledg:~$ sudo dmesg | grep firmware
> [3.796473] [drm] GuC firmware load skipped
> [3.802454] i915 :00:02.0: firmware: direct-loading firmware 
> i915/skl_dmc_ver1_26.bin
.
# inxi -c0 -v4
System:Host: big41 Kernel: 4.9.0-3-amd64 x86_64 (64 bit gcc: 6.3.0) Console:
tty 3
   Distro: Debian GNU/Linux 9
Machine:   Mobo: TAR model: T41 HD v: ' ' Bios: American Megatrends v: 080015
date: 09/22/2009
CPU:   Dual core Intel Core2 Duo E7600 (-MCP-) cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 12237
   clock speeds: max: 3066 MHz 1: 1603 MHz 2: 1603 MHz
Graphics:  Card: Intel 4 Series Integrated Graphics Controller bus-ID: 00:02.0
   Display Server: X.org 1.19.2 drivers: (unloaded: fbdev,vesa)
   tty size: 180x56 Advanced Data: N/A for root out of X
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   driver: r8169 v: 2.3LK-NAPI port: d800 bus-ID: 01:00.0
   IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 
00:30:67:3a:a0:06
Drives:HDD Total Size: 500.1GB (7.4% used) ID-1: /dev/sda model: ST3500411SV
size: 500.1GB
Partition: ID-1: / size: 5.4G used: 3.5G (67%) fs: ext3 dev: /dev/sda27
   ID-2: /home size: 4.3G used: 810M (19%) fs: ext3 dev: /dev/sda9
   ID-3: swap-1 size: 1.57GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Info:  Processes: 139 Uptime: 28 min Memory: 161.8/3731.4MB Init: systemd
runlevel: 5 Gcc sys: 6.3.0
   Client: Shell (bash 4.4.121) inxi: 2.2.28
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Brian]

On Mon 19 Jun 2017 at 09:29:40 -0400, Greg Wooledge wrote:

> On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
> > When I try as ordinary user (on host big41), I get the subject message. 
> > Anyone
> > know how to get startx to work in Stretch, either on :0, :1 or :2, with or
> > without a greeter running (multi-user.targer vs. graphical.target)?
> 
> I've been using startx on stretch for a couple months, with no problems.
> I login as my non-root user on tty1, and run 'startx', and it just works.

The same experience as yours on tty1 to tty6. Except a couple of days
ago when I used nouveau.modeset=0 on GRUB's linux line and got what is
in the subject header.

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Greg Wooledge]

On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
> When I try as ordinary user (on host big41), I get the subject message. Anyone
> know how to get startx to work in Stretch, either on :0, :1 or :2, with or
> without a greeter running (multi-user.targer vs. graphical.target)?

I've been using startx on stretch for a couple months, with no problems.
I login as my non-root user on tty1, and run 'startx', and it just works.

This is on two different machines, both using Intel graphics.  Here's one
of them:

wooledg:~$ uname -a
Linux wooledg 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux

wooledg:~$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:1912] (rev 06)

wooledg:~$ sudo dmesg | grep firmware
[3.796473] [drm] GuC firmware load skipped
[3.802454] i915 :00:02.0: firmware: direct-loading firmware 
i915/skl_dmc_ver1_26.bin

[Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

[Felix Miata]

>From the release notes:
2.2.10. The Xorg server no longer requires root

In the stretch version of Xorg, it is possible to run the Xorg
server as a regular user rather than as root. This reduces the
risk of privilege escalation via bugs in the X server. However,
it has some requirements for working:

  * It needs logind and libpam-systemd.

  * The system needs to support Kernel Mode Setting (KMS).
Therefore, it may not work in some virtualization
environments (e.g. virtualbox) or if the kernel has no driver
that supports your graphics card.

  * It needs to run on the virtual console it was started from.

  * Only the gdm3 display manager supports running X as a
non-privileged user in stretch. Other display managers will
always run X as root. Alternatively, you can also start X
manually as a non-root user on a virtual terminal via startx.

When I try as ordinary user (on host big41), I get the subject message. Anyone
know how to get startx to work in Stretch, either on :0, :1 or :2, with or
without a greeter running (multi-user.targer vs. graphical.target)?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: stretch, startx impossible

[JF Straeten]

Re,

On Sun, Feb 19, 2017 at 10:11:46PM +0100, David Pinson wrote:

> Est-ce que ce lien pourrait vous aider ?
> https://github.com/dnschneid/crouton/issues/2926

Tkx, déjà vu, mais pas exploitable :-/


-- 

JFS.

Re: stretch, startx impossible

[David Pinson]

Le 19/02/2017 à 21:42, JF Straeten a écrit :
> Lo,
>
>
> On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote:
>
> [...]
>>> il m'est impossible de lancer startx. [...] 
>>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
>>> permitted)
> [...]
>> As tu installé xinit? /usr/bin/startx fait partie du paquet xinit
> Oui, ce message apparaît en exécutant startx, justement...
>
> J'ai le même problème sur une stretch aussi.
>
> Apparemment, ça semble lié au fait que X n'est plus lancé avec les
> droits root, ni même suid root, mais en utilisateur, sous stretch,
> mais je n'ai pas encore eu le temps d'aller plus loin :-/
>
> A+
>

Bonsoir,

Est-ce que ce lien pourrait vous aider ?
https://github.com/dnschneid/crouton/issues/2926

-- 
Librement vôtre,
David P. 

Re: stretch, startx impossible

[JF Straeten]

Lo,


On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote:

[...]
> >il m'est impossible de lancer startx. [...] 
> >xf86EnableIOPorts: failed to set IOPL for I/O (Operation not
> >permitted)

[...]
> As tu installé xinit? /usr/bin/startx fait partie du paquet xinit

Oui, ce message apparaît en exécutant startx, justement...

J'ai le même problème sur une stretch aussi.

Apparemment, ça semble lié au fait que X n'est plus lancé avec les
droits root, ni même suid root, mais en utilisateur, sous stretch,
mais je n'ai pas encore eu le temps d'aller plus loin :-/

A+

-- 

JFS.

Re: stretch, startx impossible

[jérémy prego]

Le 19/02/2017 à 21:20, maderios a écrit :

Bonjour
As tu installé xinit?
/usr/bin/startx fait partie du paquet xinit


oui, du moins il l'ait par défaut
jerem.

Re: stretch, startx impossible

[maderios]

On 02/19/2017 01:58 PM, jérémy prego wrote:

bonjour à tous,

après avoir installé Stretch sur une machine avec le bureau mate, il
m'est impossible de lancer startx. Google me donne plein de résultat
mais c'est trop vieux et les commande ne fonctionnent plus sur ma
stretch. L'erreur que j'ai est la suivante:
[82.260] xf86EnableIOPorts: failed to set IOPL for I/O (Operation
not permitted)

avec lightdm, ça fonctionne très bien par contre, mais je préférerai
utiliser startx.

je précise que le système vient d'être installé et que rien n'a été touché.


Bonjour
As tu installé xinit?
/usr/bin/startx fait partie du paquet xinit

--
Maderios

stretch, startx impossible

[jérémy prego]

bonjour à tous,

après avoir installé Stretch sur une machine avec le bureau mate, il 
m'est impossible de lancer startx. Google me donne plein de résultat 
mais c'est trop vieux et les commande ne fonctionnent plus sur ma 
stretch. L'erreur que j'ai est la suivante:
[82.260] xf86EnableIOPorts: failed to set IOPL for I/O (Operation 
not permitted)


avec lightdm, ça fonctionne très bien par contre, mais je préférerai 
utiliser startx.


je précise que le système vient d'être installé et que rien n'a été touché.

je vous remercie pour votre réponse

jerem

Re: veeger is infected ...startx again

[Ric Moore]

On 10/17/2016 06:48 PM, Felix Miata wrote:

Ric Moore composed on 2016-10-17 17:47 (UTC-0400):


Felix Miata wrote:



Did you consider trying with both NVidia and Nouveau purged? Apparently,
development focus has been migrating into the server-integrated
modesetting driver:
http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX




Thanks! But it seems to be fore Intel based GPU's.


I guess it's not particularly obvious that the focus of the _article_ is
on Intel, while the _development_ focus is on all three of the
mainstream gpu drivers.

I've been using the modesetting driver on all hardware that it supports
in all distros that include server 1.17.0 or newer since before that
article was written in July. Jessie's server is 1.16.4, but it does
offer the pre-incorporation version as a separate
xserver-xorg-video-modesetting .deb that seems to work just as well, as
long as it's supported by the gfxchip.



ric@iam:~$ lsmod |grep nvidia
nvidia_drm 45056  5
drm_kms_helper147456  1 nvidia_drm
drm   364544  8 drm_kms_helper,nvidia_drm
nvidia_modeset765952  5 nvidia_drm
nvidia  11472896  165 nvidia_modeset
ric@iam:~$

There appears to be some sort of modeset support for nvidia. How to use 
AND keep my nvidia goodies. ??




--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: veeger is infected ...startx again

[Felix Miata]

Ric Moore composed on 2016-10-17 17:47 (UTC-0400):


Felix Miata wrote:



Did you consider trying with both NVidia and Nouveau purged? Apparently,
development focus has been migrating into the server-integrated
modesetting driver:
http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX



Thanks! But it seems to be fore Intel based GPU's.


I guess it's not particularly obvious that the focus of the _article_ is on 
Intel, while the _development_ focus is on all three of the mainstream gpu 
drivers.


I've been using the modesetting driver on all hardware that it supports in 
all distros that include server 1.17.0 or newer since before that article was 
written in July. Jessie's server is 1.16.4, but it does offer the 
pre-incorporation version as a separate xserver-xorg-video-modesetting .deb 
that seems to work just as well, as long as it's supported by the gfxchip.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Fwd: Re: veeger is infected ...startx again

[Frank McCormick]

On 17/10/16 05:48 PM, Ric Moore wrote:


On 10/17/2016 02:43 PM, Felix Miata wrote:

Ric Moore composed on 2016-10-17 14:25 (UTC-0400):


I finally went ape and re-installed from the latest stretch build.
Initially, with the nouveau driver, XFCE$  synaptic (and others) drop
down menus worked. I installed nvidia-driver and it installed everything
related to nvidia. Rebooted and with the nvidia driver running, synaptic
still worked. THEN I created an /etc/X11/xorg.conf file, rebooted, and
it all went to h-e-double hockey sticks with the black screen and active
mouse pointer. Synaptic borken again.



And yes, I have a 4 monitor setup via two video cards. It has worked
well for several years. I rebooted into Xubuntu 16.04 on another drive,
it works just fine. I copied that xorg.conf file to my Debian drive
/etc/X11, rebooted, no go. I removed xorg.conf, rebooted and no problems
other than using one monitor out of four.  Xubuntu works, Stretch not. I
would love to know where the difference is so I could make a sane bug
report.


Did you consider trying with both NVidia and Nouveau purged? Apparently,
development focus has been migrating into the server-integrated
modesetting driver:
http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX



Thanks! But it seems to be fore Intel based GPU's. What I just
discovered is a BUNCH of gtk errors in ~/.xsession-errors

(nm-applet:2704): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underal locate toplevel GtkTrayIcon 0x14a44a0. Allocation is 22x22, but
minimum required size is 24x24.

...and there must be hundreds of errors just like it. all ranting about
a shortfall in allocated "size".  Every so often I see this:




  They may or may not be connected Ric. I am running Sid and regularly 
my .xsession-errors file grow to several hundred k filled with those 
errors and other. Now Google-chrome is also dumping hundreds of errors
into the same file. But everything seems to work my my system under 
IceWm, Mate and Cinnamon.





process 3303: arguments to dbus_message_new_method_call() were
incorrect, assertion "path != NULL" failed in file
../../../dbus/dbus-message.c line 1363. This is normally a bug in some
application using the D-Bus library.

This is a mindblower. :) Ric



  Those I don't see.

Frank

Fwd: Re: veeger is infected ...startx again

[Ric Moore]

On 10/17/2016 02:43 PM, Felix Miata wrote:

Ric Moore composed on 2016-10-17 14:25 (UTC-0400):


I finally went ape and re-installed from the latest stretch build.
Initially, with the nouveau driver, XFCE$  synaptic (and others) drop
down menus worked. I installed nvidia-driver and it installed everything
related to nvidia. Rebooted and with the nvidia driver running, synaptic
still worked. THEN I created an /etc/X11/xorg.conf file, rebooted, and
it all went to h-e-double hockey sticks with the black screen and active
mouse pointer. Synaptic borken again.



And yes, I have a 4 monitor setup via two video cards. It has worked
well for several years. I rebooted into Xubuntu 16.04 on another drive,
it works just fine. I copied that xorg.conf file to my Debian drive
/etc/X11, rebooted, no go. I removed xorg.conf, rebooted and no problems
other than using one monitor out of four.  Xubuntu works, Stretch not. I
would love to know where the difference is so I could make a sane bug
report.


Did you consider trying with both NVidia and Nouveau purged? Apparently,
development focus has been migrating into the server-integrated
modesetting driver:
http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX


Thanks! But it seems to be fore Intel based GPU's. What I just 
discovered is a BUNCH of gtk errors in ~/.xsession-errors


(nm-applet:2704): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to
underal locate toplevel GtkTrayIcon 0x14a44a0. Allocation is 22x22, but 
minimum required size is 24x24.


...and there must be hundreds of errors just like it. all ranting about 
a shortfall in allocated "size".  Every so often I see this:


process 3303: arguments to dbus_message_new_method_call() were 
incorrect, assertion "path != NULL" failed in file 
../../../dbus/dbus-message.c line 1363. This is normally a bug in some 
application using the D-Bus library.


This is a mindblower. :) Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: veeger is infected ...startx again

[Felix Miata]

Ric Moore composed on 2016-10-17 14:25 (UTC-0400):


I finally went ape and re-installed from the latest stretch build.
Initially, with the nouveau driver, XFCE$  synaptic (and others) drop
down menus worked. I installed nvidia-driver and it installed everything
related to nvidia. Rebooted and with the nvidia driver running, synaptic
still worked. THEN I created an /etc/X11/xorg.conf file, rebooted, and
it all went to h-e-double hockey sticks with the black screen and active
mouse pointer. Synaptic borken again.



And yes, I have a 4 monitor setup via two video cards. It has worked
well for several years. I rebooted into Xubuntu 16.04 on another drive,
it works just fine. I copied that xorg.conf file to my Debian drive
/etc/X11, rebooted, no go. I removed xorg.conf, rebooted and no problems
other than using one monitor out of four.  Xubuntu works, Stretch not. I
would love to know where the difference is so I could make a sane bug
report.


Did you consider trying with both NVidia and Nouveau purged? Apparently, 
development focus has been migrating into the server-integrated modesetting 
driver:

http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: veeger is infected ...startx again

[Ric Moore]

On 10/10/2016 08:49 AM, Charlie Kravetz wrote:


It sounds like GTK3 themes is taking over. I had a similar situation


I finally went ape and re-installed from the latest stretch build. 
Initially, with the nouveau driver, XFCE$  synaptic (and others) drop 
down menus worked. I installed nvidia-driver and it installed everything 
related to nvidia. Rebooted and with the nvidia driver running, synaptic 
still worked. THEN I created an /etc/X11/xorg.conf file, rebooted, and 
it all went to h-e-double hockey sticks with the black screen and active 
mouse pointer. Synaptic borken again.


And yes, I have a 4 monitor setup via two video cards. It has worked 
well for several years. I rebooted into Xubuntu 16.04 on another drive, 
it works just fine. I copied that xorg.conf file to my Debian drive 
/etc/X11, rebooted, no go. I removed xorg.conf, rebooted and no problems 
other than using one monitor out of four.  Xubuntu works, Stretch not. I 
would love to know where the difference is so I could make a sane bug 
report. Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: veeger is infected ...startx again

[Charlie Kravetz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 10 Oct 2016 05:08:44 -0400
Ric Moore <wayward4...@gmail.com> wrote:

>On 10/01/2016 09:40 PM, Jimmy Johnson wrote:
>> On 10/01/2016 12:49 PM, Ric Moore wrote:  
>>> ... humans are infecting Veeger. I figured I'd fix the display manager
>>> problem with a clean install.  Here's the fun part that gives me the
>>> giggles: I downloaded the testing DVD to install clean from, whilst
>>> thinking it would be stretch or sid. Best laid plans of mice.
>>>
>>> I rebooted upon completion and it went smoothly. I installed my Nvidia
>>> drivers and that went smooth. It was all s stupidly smooth that I
>>> suspected something was wrong. Surprise, my sources list reflected
>>> Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
>>> steps I'd go for Stretch. Long story short. I'm back to the black screen
>>> with itty bitty mouse cursor where I should be logging in.  Synaptic is
>>> also acting up again  with the drop down menus refusing to drop down.  
>>
>> Add the Sid/unstable sources and 'aptitude update' and 'aptitude
>> safe-upgrade' and you'll be okay ;). Maybe when the Stretch freeze
>> starts that will be the time to remove Sid to get the next stable system.
>>  
>>> I'm fulla pain killers (legitimately prescribed!) so I figure a much
>>> younger, and more agile, mind with figure this out. I'll even buy my
>>> newly found favorite cube-monkey a pizza, as long as the order doesn't
>>> require truffles.  
>>
>> Good luck!  
>
>No luck so far and I just updated sid. On initial boot, the video driver 
>kicks in, as all the monitors come to life, the harddrive is checked and 
>then I get the black screen and mouse cursor which is active and moves 
>with movement of the mouse. Buggers. What package should I file a 
>bugreport against?? If I log into a terminal and issue "startx", 
>everything comes up normally into XFCE4 desktop. Synaptic menus still 
>refuse to drop down. Thanks all, Ric

It sounds like GTK3 themes is taking over. I had a similar situation,
by removing all GTK3 themes, I was able to get GTK2 theme installed. It
gave me back those menus and the proper spacing. I am now using
Orangine in Appearance and Kindaker in Window Manager. It works here.

- -- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]
-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJX+45XAAoJEIqui46mydCACfoH/2VfONKeF/TrTRcMzg3J2i5Z
shB9O2GE0/GXsXqDEqlC6LUXDrELsvmfre1g7mdhSG4xc+XGm1YYjV44EPri9Ant
dQaxOitFWLzELeeDj3Q13GGxRqIEvs+w0h1dGs+PLdf0rDA8RgmE05Z6roas/BJo
K02vDG5T053THNLMO8bp0ZeK8JQH0vawStyXa6YyDIMR93OScNUabIFs558pILNr
4gM2EpX2rpdJ9uLCaef+UFFrG4aaXJQF8UTKXBh4xoelXuQTmSxjOMnaxSVSgD4v
UmTm4ww38noqTOiINU7VNp0iRlmUjbmJex+ABqFIIj+bzhNKnDSNuhpIbCnG2nU=
=8vYi
-END PGP SIGNATURE-

Re: veeger is infected ...startx again

[Ric Moore]

On 10/01/2016 09:40 PM, Jimmy Johnson wrote:

On 10/01/2016 12:49 PM, Ric Moore wrote:

... humans are infecting Veeger. I figured I'd fix the display manager
problem with a clean install.  Here's the fun part that gives me the
giggles: I downloaded the testing DVD to install clean from, whilst
thinking it would be stretch or sid. Best laid plans of mice.

I rebooted upon completion and it went smoothly. I installed my Nvidia
drivers and that went smooth. It was all s stupidly smooth that I
suspected something was wrong. Surprise, my sources list reflected
Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
steps I'd go for Stretch. Long story short. I'm back to the black screen
with itty bitty mouse cursor where I should be logging in.  Synaptic is
also acting up again  with the drop down menus refusing to drop down.


Add the Sid/unstable sources and 'aptitude update' and 'aptitude
safe-upgrade' and you'll be okay ;). Maybe when the Stretch freeze
starts that will be the time to remove Sid to get the next stable system.


I'm fulla pain killers (legitimately prescribed!) so I figure a much
younger, and more agile, mind with figure this out. I'll even buy my
newly found favorite cube-monkey a pizza, as long as the order doesn't
require truffles.


Good luck!


No luck so far and I just updated sid. On initial boot, the video driver 
kicks in, as all the monitors come to life, the harddrive is checked and 
then I get the black screen and mouse cursor which is active and moves 
with movement of the mouse. Buggers. What package should I file a 
bugreport against?? If I log into a terminal and issue "startx", 
everything comes up normally into XFCE4 desktop. Synaptic menus still 
refuse to drop down. Thanks all, Ric

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: veeger is infected ...startx again

[Ric Moore]

On 10/01/2016 08:02 PM, Bob Bernstein wrote:

On Sat, 1 Oct 2016, Ric Moore wrote:


Surprise, my sources list reflected Jessie, not Stretch or Sid. I
 FIXED that.


Did you run an 'apt-get dist-upgrade' after making changes to sources.list?

Hang in there.


OK. I gave that a digital whirl.
Login / greeter is~ still~ broken. Maybe I need an ASCII greeter with 
blinking X's for the outline?? startx works for now. :)

Synaptic drop down menus are broke again.
Office drop down menus thankfully DO work.
A new one is that background selection greys out source directory 
selection, while Thunar file selection works. Go figure. I dinked with 
it some more, and using Thunar to select a graphic file, selecting it to 
be used as background, something clicked and I have my backgrounds back. 
Strange. Verrry strange.

xfce4 sound mixer no longer exists. No biggie, I just use pavucontrol.
Everything else appears nOrMaL. :) Ric

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: veeger is infected ...startx again

[Jimmy Johnson]

On 10/01/2016 12:49 PM, Ric Moore wrote:

... humans are infecting Veeger. I figured I'd fix the display manager
problem with a clean install.  Here's the fun part that gives me the
giggles: I downloaded the testing DVD to install clean from, whilst
thinking it would be stretch or sid. Best laid plans of mice.

I rebooted upon completion and it went smoothly. I installed my Nvidia
drivers and that went smooth. It was all s stupidly smooth that I
suspected something was wrong. Surprise, my sources list reflected
Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
steps I'd go for Stretch. Long story short. I'm back to the black screen
with itty bitty mouse cursor where I should be logging in.  Synaptic is
also acting up again  with the drop down menus refusing to drop down.


Add the Sid/unstable sources and 'aptitude update' and 'aptitude 
safe-upgrade' and you'll be okay ;). Maybe when the Stretch freeze 
starts that will be the time to remove Sid to get the next stable system.



I'm fulla pain killers (legitimately prescribed!) so I figure a much
younger, and more agile, mind with figure this out. I'll even buy my
newly found favorite cube-monkey a pizza, as long as the order doesn't
require truffles.


Good luck!
--
Jimmy Johnson

Kali GNU/Linux Rolling  - EXT4 - AMD64 at sda17
Registered Linux User #380263

Re: veeger is infected ...startx again

[Bob Bernstein]

On Sun, 2 Oct 2016, Liam O'Toole wrote:

At the risk of stating the obvious ... an 'apt-get update' is 
required first.


Stating the obvious is a dirty job, but someone has to do it. 
I'm trying to make a Pat 'n Mike joke out of this, but the thing 
eludes me.


--
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive
persons with low self-esteem, no sense of humour or irrational
metaphysical beliefs.

Re: veeger is infected ...startx again

[Liam O'Toole]

On 2016-10-02, Bob Bernstein  wrote:
> On Sat, 1 Oct 2016, Ric Moore wrote:
>
>> Surprise, my sources list reflected Jessie, not Stretch or 
>> Sid. I  FIXED that.
>
> Did you run an 'apt-get dist-upgrade' after making changes to 
> sources.list?
>
> Hang in there.
>

At the risk of stating the obvious ... an 'apt-get update' is required
first.

-- 

Liam

Re: veeger is infected ...startx again

[Bob Bernstein]

On Sat, 1 Oct 2016, Ric Moore wrote:

Surprise, my sources list reflected Jessie, not Stretch or 
Sid. I  FIXED that.


Did you run an 'apt-get dist-upgrade' after making changes to 
sources.list?


Hang in there.

--
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive
persons with low self-esteem, no sense of humour or irrational
metaphysical beliefs.

Re: veeger is infected ...startx again

[Sven Hartge]

Erwan David  wrote:

> You'd better explain what you call "veeger" nobody will understand
> your problem.

I think he means "V'ger", which would be a reference to the first Star
Trek Movie.

S!

-- 
Sigmentation fault. Core dumped.

Re: veeger is infected ...startx again

[Erwan David]

Le 01/10/2016 à 21:49, Ric Moore a écrit :
> ... humans are infecting Veeger. I figured I'd fix the display manager
> problem with a clean install.  Here's the fun part that gives me the
> giggles: I downloaded the testing DVD to install clean from, whilst
> thinking it would be stretch or sid. Best laid plans of mice.
>
> I rebooted upon completion and it went smoothly. I installed my Nvidia
> drivers and that went smooth. It was all s stupidly smooth that I
> suspected something was wrong. Surprise, my sources list reflected
> Jessie, not Stretch or Sid. I  FIXED that. Figuring baby
> steps I'd go for Stretch. Long story short. I'm back to the black
> screen with itty bitty mouse cursor where I should be logging in. 
> Synaptic is also acting up again  with the drop down menus refusing to
> drop down.
>
> I'm fulla pain killers (legitimately prescribed!) so I figure a much
> younger, and more agile, mind with figure this out. I'll even buy my
> newly found favorite cube-monkey a pizza, as long as the order doesn't
> require truffles.
>
>

You'd better explain what you call "veeger" nobody will understand your
problem.

veeger is infected ...startx again

[Ric Moore]

... humans are infecting Veeger. I figured I'd fix the display manager 
problem with a clean install.  Here's the fun part that gives me the 
giggles: I downloaded the testing DVD to install clean from, whilst 
thinking it would be stretch or sid. Best laid plans of mice.


I rebooted upon completion and it went smoothly. I installed my Nvidia 
drivers and that went smooth. It was all s stupidly smooth that I 
suspected something was wrong. Surprise, my sources list reflected 
Jessie, not Stretch or Sid. I  FIXED that. Figuring baby 
steps I'd go for Stretch. Long story short. I'm back to the black screen 
with itty bitty mouse cursor where I should be logging in.  Synaptic is 
also acting up again  with the drop down menus refusing to drop down.


I'm fulla pain killers (legitimately prescribed!) so I figure a much 
younger, and more agile, mind with figure this out. I'll even buy my 
newly found favorite cube-monkey a pizza, as long as the order doesn't 
require truffles.



--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

veeger is infected ...startx again

[Ric Moore]

--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Login impossible/ startx ne demarre pas/Xauth timeout

[Denis Fertin]

Bonjour,

Je ne suis pas sur de savoir quelle action a resolu le probleme.
J 'ai cree le fichier .Xauthority dans mon repertoire home en tant que
root. Puis j'ai changé le propritaire et le group, je me suis rendu compte
que mon répertoire home appartenait a nobody/nogroup, j'ai changé cela
aussi.
Startx ne fonctionnait toujours pas mais avec un message different: user
not authorized to start X... ( ou qqchose du genre) du coup j'ai reessaye
le login et cela a marché.

Cordialement
Le 14 févr. 2016 12:04, "Jean-Michel OLTRA" <jm.oltra.antis...@espinasse.net>
a écrit :

>
> Bonjour,
>
>
> Le samedi 13 février 2016, dfertin a écrit...
>
>
> > Résolu
>
> Mais encore…?
>
>
> --
> jm
>
>

Re: Login impossible/ startx ne demarre pas/Xauth timeout

[Jean-Michel OLTRA]

Bonjour,


Le samedi 13 février 2016, dfertin a écrit...


> Résolu

Mais encore…?


-- 
jm

Login impossible/ startx ne demarre pas/Xauth timeout

[Denis Fertin]

Bonjour,

Je viens d'installer debian sur un pc lap top neuf.
Tout fonctionnaitnickel mais j'ai laisser le Pcen veille la nuit.
Depuis je ne peux plus me logger normalement.
En mode recovery, root peut executer startx.
Lorsque l'utilisateur dfertin essaye de lancer startx, j'obtiens le message
suivant:
Xauth : time out inlocking authority file /home/dfertin/.Xauthority
X: user not authorized to run Xserver, aborting ...

Le fichier /home/dfertin/.Xauthority n
'existe pas et je ne peux pas le creer en utilisant touch.
Ma conclusion: xauthotity n'arrive pas a creer ce fichier parce qu'il a ete
mal fermé lors de l'extinction du système.
Que faire?
Merci d'avance.

Re: Login impossible/ startx ne demarre pas/Xauth timeout

[dfertin]

Résolu

Re: Can't startx as normal user

[Sven Arvidsson]

On Tue, 2015-12-01 at 22:23 -0300, Draco Metallium(Rodrigo S. Cañibano)
> > The NEWS entry should have been picked up by apt-listchanges:
> 
> I must have missed it. Thanks!

Looks like it was added after the change was made, so it's possible
that you made the upgrade before it was added.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





signature.asc
Description: This is a digitally signed message part

Re: Can't startx as normal user

[Rodrigo S. Cañibano]

On 1 December 2015 at 16:47, Sven Arvidsson  wrote:
> The NEWS entry should have been picked up by apt-listchanges:

I must have missed it. Thanks!

Re: Can't startx as normal user

[Sven Arvidsson]

On Mon, 2015-11-30 at 19:20 -0300, Draco Metallium(Rodrigo S. Cañibano)
wrote:
> It could be that, since I don't have systemd, nor systemd-shim
> installed (I just checked again).
> 
> I had to install xserver-xorg-legacy, just as Harald Dunkel
> suggested.
> 
> Should't apt-get have warned me that there were unmet dependencies?

The NEWS entry should have been picked up by apt-listchanges:
https://sources.debian.net/src/xorg-server/2:1.17.3-2/debian/xserver-xorg-core.NEWS/

(And will probably also be mentioned in the release docs)

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





signature.asc
Description: This is a digitally signed message part

Re: Can't startx as normal user

[Rodrigo S. Cañibano]

On 30 November 2015 at 06:10, Ansgar Burchardt <"Ansgar
Burchardt"@43-1.org> wrote:
> which looks like some DBus policy forbids Xorg to talk to logind. Xorg
> does so in order to get access to devices w/o being setuid root since
> recently.

It could be that, since I don't have systemd, nor systemd-shim
installed (I just checked again).

I had to install xserver-xorg-legacy, just as Harald Dunkel suggested.

Should't apt-get have warned me that there were unmet dependencies?

Wasn't systemd just an init?

Thanks to all of you!

Re: Can't startx as normal user

[Harald Dunkel]

If you are using startx/xinit: Try installing xserver-xorg-legacy.
I had the same problem.

Good luck
Harri

Re: Can't startx as normal user

[Ansgar Burchardt]

"Draco Metallium(Rodrigo S. Cañibano)" <draco@gmail.com> writes:
> No only root can run startx. If a user tries the following error appears:
>
> "(EE) AddScreen/ScreenInit failed for driver 0"

The first error in the log you attached is:

> [  4203.010] (EE) systemd-logind: failed to get session: Rejected send 
> message, 1 matched rules; type="method_call", sender=":1.34" (uid=1000 
> pid=18022 comm="/usr/lib/xorg/Xorg -nolisten tcp :1 vt2 -keeptty -") 
> interface="org.freedesktop.login1.Manager" member="GetSessionByPID" error 
> name="(unset)" requested_reply="0" destination="org.freedesktop.login1" 
> (uid=0 pid=5989 comm="/lib/systemd/systemd-logind ")

which looks like some DBus policy forbids Xorg to talk to logind. Xorg
does so in order to get access to devices w/o being setuid root since
recently.

I remember users having problems with DBus policies when old version of
systemd-shim were installed (it has been fixed some time ago),
cf. https://bugs.debian.org/746242

Please make sure that either systemd-shim is purged (not only removed),
e.g. by running "apt-get purge systemd-shim", or that at least version
6-3 of systemd-shim is installed (if you don't use systemd as init).

Ansgar

Can't startx as normal user

[Rodrigo S. Cañibano]

Hi!

Today I made a dist-upgrade and everything worked fine until I rebooted.

No only root can run startx. If a user tries the following error appears:

"(EE) AddScreen/ScreenInit failed for driver 0"

(I will attach the full log).

Does anyone have any idea what might be the source of this problem?

Thanks and sorry for the bad English!

--
Draco Metallium
[  4203.003] 
X.Org X Server 1.17.3
Release Date: 2015-10-26
[  4203.004] X Protocol Version 11, Revision 0
[  4203.004] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[  4203.004] Current Operating System: Linux ruri 4.2.0-1-amd64 #1 SMP Debian 4.2.6-1 (2015-11-10) x86_64
[  4203.004] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 root=UUID=88c4cde7-3244-453d-bf2a-d28d836b2527 ro quiet
[  4203.005] Build Date: 27 October 2015  11:41:02PM
[  4203.005] xorg-server 2:1.17.3-2 (http://www.debian.org/support) 
[  4203.005] Current version of pixman: 0.33.4
[  4203.006] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[  4203.006] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  4203.007] (==) Log file: "/home/draco/.local/share/xorg/Xorg.1.log", Time: Mon Nov 30 01:41:43 2015
[  4203.008] (==) Using config file: "/etc/X11/xorg.conf"
[  4203.008] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  4203.009] (==) ServerLayout "X.org Configured"
[  4203.009] (**) |-->Screen "Screen0" (0)
[  4203.009] (**) |   |-->Monitor "DVI-1"
[  4203.009] (**) |   |-->Device "Card1"
[  4203.009] (**) |-->Input Device "Mouse0"
[  4203.009] (**) |-->Input Device "Keyboard0"
[  4203.009] (==) Automatically adding devices
[  4203.009] (==) Automatically enabling devices
[  4203.009] (==) Automatically adding GPU devices
[  4203.009] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  4203.009] 	Entry deleted from font path.
[  4203.009] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  4203.009] 	Entry deleted from font path.
[  4203.009] (**) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins,
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[  4203.009] (**) ModulePath set to "/usr/lib/xorg/modules"
[  4203.009] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[  4203.009] (WW) Disabling Mouse0
[  4203.009] (WW) Disabling Keyboard0
[  4203.009] (II) Loader magic: 0x562a849f7de0
[  4203.009] (II) Module ABI versions:
[  4203.009] 	X.Org ANSI C Emulation: 0.4
[  4203.009] 	X.Org Video Driver: 19.0
[  4203.009] 	X.Org XInput driver : 21.0
[  4203.009] 	X.Org Server Extension : 9.0
[  4203.010] (EE) systemd-logind: failed to get session: Rejected send message, 1 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=18022 comm="/usr/lib/xorg/Xorg -nolisten tcp :1 vt2 -keeptty -") interface="org.freedesktop.login1.Manager" member="GetSessionByPID" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=5989 comm="/lib/systemd/systemd-logind ")
[  4203.010] (II) xfree86: Adding drm device (/dev/dri/card0)
[  4203.012] (--) PCI: (0:1:5:0) 1002:9616:1849:9616 rev 0, Mem @ 0xc000/268435456, 0xfe8f/65536, 0xfe70/1048576, I/O @ 0xa000/256
[  4203.012] (--) PCI:*(0:2:0:0) 1002:679a:174b:a003 rev 0, Mem @ 0xd000/268435456, 0xfe9c/262144, I/O @ 0xb000/256, BIOS @ 0x/131072
[  4203.012] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[  4203.012] (II) LoadModule: "ddc"
[  4203.012] (II) Module "ddc" already built-in
[  4203.012] (II) LoadModule: "dri"
[  4203.012] (II) Module "dri" already built-in
[  4203.012] (II) LoadModule: "dri2"
[  4203.012] (II) Module "dri2" already built-in
[  4203.012] (II) LoadModule: "extmod"
[  4203.012] (II) Module "extmod" already built-in
[  4203.012] (II) LoadModule: "glx"
[  4203.012] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  4203.013] (II) Module glx: vendor="X.Org Foundation"
[  4203.013] 	compiled for 1.17.3, module version = 1.0.0
[  4203.013] 	ABI class: X.Org Server Extension, version 9.0
[  4203.013] (==) AIGLX enabled
[  4203.013] (II) Lo

Re: Can't startx as normal user

[Charlie]

On Mon, 30 Nov 2015 01:48:40 -0300 Draco Metallium(Rodrigo S. Cañibano)
sent:

> Today I made a dist-upgrade and everything worked fine until I
> rebooted.
> 
> No only root can run startx. If a user tries the following error
> appears:
> 
> "(EE) AddScreen/ScreenInit failed for driver 0"
> 
> (I will attach the full log).
> 
> Does anyone have any idea what might be the source of this problem?

Could this be of help?

https://bbs.archlinux.org/viewtopic.php?id=170860

Charlie

-- 
Registered Linux User:- 329524
***

If I shall sell both my forenoons and afternoons to society, as
most appear to do, I'm sure that, for me, there would be
nothing left worth living
for. .Henry David Thoreau

***

Debian GNU/Linux - Magic indeed.

-

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

[Andrei POPESCU]

On Vi, 21 mar 14, 10:34:03, Darac Marjal wrote:
 On Fri, Mar 21, 2014 at 11:46:38AM +0200, Andrei POPESCU wrote:
  On Vi, 21 mar 14, 09:52:09, Gian Uberto Lauri wrote:
   
   You can access the console X was started from even when the machine is
   locked.
  
  Seriously? I'd find that to be a severe bug in the said locking 
  application.

I have to correct myself here, apparently the application tries to do 
everything right, but...
http://www.jwz.org/xscreensaver/faq.html#no-ctl-alt-bs

 It's a feature of linux being multi-user. You come up to a machine
 that's running Xscreensaver (et al.) change to another VT, login there
 and start another X server. GDM can facilitate this with the Switch User
 functionality, but it's perfectly normal behaviour even without.
 
 If you don't want people terminating your X session from the console, I
 think the best solution is to use a display manager, which re-uses the
 VT, and to turn on DontZap.

With a display manager one doesn't need DontZap and DontVTSwitch, as 
long as one is not logged in on one of the consoles.

Alt-SysRq-F is disabled on sid:
mar 25 12:03:28 sid kernel: SysRq : This sysrq operation is disabled.

AllowClosedownGrabs doesn't exist in xorg.conf(5) and 
Ctrl-Alt-KP_Multiply doesn't do anything on sid.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

[Vincent Lefevre]

On 2014-03-25 12:08:12 +0200, Andrei POPESCU wrote:
 Alt-SysRq-F is disabled on sid:
 mar 25 12:03:28 sid kernel: SysRq : This sysrq operation is disabled.

But what if someone logs in, uses all the memory left (possibly not
even in a malicious way) so that this triggers the OOM killer, and
the OOM killer chooses the screen saver as the application to kill?

The right thing is that the screen saver should protect itself
against the OOM killer.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140325130315.ga26...@ypig.lip.ens-lyon.fr

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

[Vincent Lefevre]

On 2014-03-23 21:06:55 +0100, Jörg-Volker Peetz wrote:
 Seems I'm a little bit old-fashioned ;-)
 According to the man-page Xsession(5) the system scripts take care of using a
 log-file, given that you indeed don't have ~/.xinitrc .
 So maybe the man-page of startx(1) has to be updated, since it only talks 
 about
 ~/.xinitrc .

Because startx runs the xinitrc (either the user's one or the system
one) and doesn't know anything about the .xsession file. Xsession files
(including the user's .xsession) are sourced via the system xinitrc.
Perhaps a section about Debian recommendations and default configuration
should be added.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/
100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140324113736.ga22...@ypig.lip.ens-lyon.fr