45:respawn:/sbin/agetty 38400 tty3 linux
c4:2345:respawn:/sbin/agetty 38400 tty4 linux
c5:2345:respawn:/sbin/agetty 38400 tty5 linux
c6:2345:respawn:/sbin/agetty 38400 tty6 linux
--
edes
27;t change anything. As far as
I can see, it's not different from running startx -- vtN, and I get the
same error.
--
edes
el Tue, 27 Oct 2020 09:35:25 -0300
edes escribió:
> Just to be sure: I should enable the -suid USE flag in
> x11-base/xorg-server?
Just for the record, I rebuilt x11-base/xorg-server with +suid, and the
problem persists:
$ startx -- vt7
Fatal server error:
(EE) xf86OpenConsole: Canno
(and others), but
I thought it addressed the problem of not being able to start Xorg as
regular user, which is not my case.
Just to be sure: I should enable the -suid USE flag in
x11-base/xorg-server?
--
edes
x27;t replicate the old behaviour. I tried "startx -- vt7", but I get
this error message:
Fatal server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
I don't know if this is relevant, but under /dev I see:
crw--w 1 root tty 4, 0 oct 27 07:54 /dev/t
el 2020-05-04 a las 21:56 antlists escribió:
> Another app that's 2.7 only is the current version of lilypond. The new
> dev version I think can run without python2, but certainly building the
> stable version demands it. I *think* if you get the pre-compiled binary
> the current version can
el 2020-01-23 a las 13:59 Mick escribió:
> The way I went about it was to comment out the offending lines in these
> files and recompile the kernel. It is a bit of pain, since I have to
> perform this manual editing with each kernel so far.
>
> You could try to comment out the lines which brea
el 2020-01-19 a las 16:49 Mick escribió:
> You could compare the dmesg output of working and non-working kernels
> and see what differences are present, then google for bugs/solutions on
> that basis.
[...]
> You could also diff the two different kernel tree versions and see what
> drivers h
el 2020-01-18 a las 12:58 edes escribió:
> But now for some reason it works as playback device, but is not
> recognized as capture device.
I kept investigating, and all the evidence points to a kernel problem
(gentoo-sources).
I tried several versions, everything works fine with kernels
Hello list,
I have a Sound Devices that always worked perfectly fine out of the box as
a generic USB device, without need of asoundrc or anything.
But now for some reason it works as playback device, but is not recognized
as capture device.
Below I pasted the output of the alsa_info script, w
10 matches
Mail list logo
