blob: 39a3336d323587dbe8265e07109ee77732c474d3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
[[!meta copyright="Copyright © 2012, 2015 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]
[[!tag open_issue_glibc open_issue_hurd]]
# console switching and DMs
Something like VT_ACTIVATE would need to be implemented to allow console
switching. In the meanwhile xorg refuses the vtx option, thus making lightdm &
such fail with an Xserver error:
(EE) Fatal server error:
(EE) Unrecognized option: vt7
In the meanwhile DMs could be taught not to use the vtx option.
# IRC, freenode, #hurd, 2012-08-30
<gean> braunr: I have some errors about keyboard in the xorg log, but
keyboard is working on the X
<braunr> gean: paste the log somewhere please
<gean> braunr: http://justpaste.it/19jb
[...]
[1987693.272] Fatal server error:
[1987693.272] Cannot set event mode on keyboard (Inappropriate ioctl for device)
[...]
[1987693.292] FatalError re-entered, aborting
[1987693.302] can't reset keyboard mode (Inappropriate ioctl for device)
[...]
<braunr> hum
<braunr> it looks like the xorg keyboard driver evolved and now uses ioctls
our drivers don't implement
<braunr> thanks for the report, we'll have to work on this
<braunr> i'm not sure the problem is new actually
|
