Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14201 - xorg-server-1.6.0-3 cannot be installed
Attached to Project:
Arch Linux
Opened by Maurel (guy-kde) - Sunday, 12 April 2009, 16:11 GMT
Last edited by Jan de Groot (JGC) - Thursday, 16 April 2009, 21:10 GMT
Opened by Maurel (guy-kde) - Sunday, 12 April 2009, 16:11 GMT
Last edited by Jan de Groot (JGC) - Thursday, 16 April 2009, 21:10 GMT
|
DetailsDescription:
I got the xorg-server-1.6.0-3 (and somme more) with the command pacman -Syu but this cannot be installed: error: could not prepare transaction error: failed to commit transaction (conflicting files) xorg-server: /usr/lib/xorg/modules/extensions/libdri.so exists in filesystem xorg-server: /usr/lib/xorg/modules/libwfb.so exists in filesystem what is to do? |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 16 April 2009, 21:10 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix, because I can't fix this. This has been announced when xorg-server 1.6.0 was released to testing, but was forgotten when the move to extra was announced.
Thursday, 16 April 2009, 21:10 GMT
Reason for closing: Won't fix
Additional comments about closing: Won't fix, because I can't fix this. This has been announced when xorg-server 1.6.0 was released to testing, but was forgotten when the move to extra was announced.
But I get a new error in the
/var/log/Xorg.0.log
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(EE) config/hal: couldn't initialise context: (null) ((null))
I don't anderstand why.
But I have red, a few days ago, that the hal was automatically started by dbus, and before I got the xorg-server-1.6, I havn't this problem.
The error above is no more there, but the next ones:
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) config/hal: Adding input device Macintosh mouse button emulation
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device ImPS/2 Logitech Wheel Mouse
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(EE) config/hal: NewInputDeviceRequest failed (8)
Not correct: dbus is automatically started by hal.
But who can help me with the (EE) in the file Xorg.0.log ?
There are also some dependency problems with xorg-server 1.6.0. For example, xf86-input-evdev depends on xorg-server-1.6.0, and vice versa. xorg-server depends on xf86-input-mouse-1.4.0, newer xf86-input-keyboard (1.3.2?) and others. Also, xf86-video-intel-newest from AUR does not work, xf86-video-intel (from community?) is required.
This issue can be solved by removing xorg-server, installing xf86-input-evdev (which will also fetch xorg-server 1.6.0) and all the driver packages that are put out with "(EE)".
Bottom line: this is purely a package dependency issue.
Bottomer line: Linux jane 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 09:47:26 UTC 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux
I first got a "triple echo" of each character within the kdm-login-window.
I red it could be a problem with evdev. A solution could be to add the Option "AutoAddDevices" "off" to the Section "ServerFlags".
I try this and got the correct "single echo" and so I was able to login.
Now I try without the "AutoAddDevices"-Option.
The (EE)-errors have disappeared, a new one is coming (see later) but the "triple echo" is there again.
I have to choose betwenn the two problems!
The new problem is:
(**) Option "xkb_layout" "us"
unless I specify
"XkbLayout" "de"
in the /etc/X11/xorg.conf
Note that if you have AutoAddDevices set to false your input devices aren't managed by hal. Don't care about its moans.
And please, don't change the topic of a bug report. Here only the first comment is relevant and can be useful for people upgrading xorg-server, otherwise this task could be closed.
I first got a "triple echo" of each character within the kdm-login-window.
I red it could be a problem with evdev. A solution could be to add the Option "AutoAddDevices" "off" to the Section "ServerFlags".
I try this and got the correct "single echo" and so I was able to login.
Now I try without the "AutoAddDevices"-Option.
The (EE)-errors have disappeared, a new one is coming (see later) but the "triple echo" is there again.
I have to choose betwenn the two problems!
The new problem is:
(**) Option "xkb_layout" "us"
unless I specify
"XkbLayout" "de"
in the /etc/X11/xorg.conf
If I commented out, in the file /etc/X11/xorg.conf in the Section "ServerFlags" the Options "AllowEmptyInput" and "AutoAddDevices" AND the complete Sections
#Section "InputDevice"
# Identifier "Keyboard0"
# Driver "kbd"
# Option "XkbLayout" "de"
#EndSection
#Section "InputDevice"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "auto"
# Option "Device" "/dev/input/mice"
# Option "ZAxisMapping" "4 5 6 7"
#EndSection
the problem with the "triple echo" (last comment) is no more present.
The only problem remaining ist the definition of the keyboard-layout I wanted to have "de"
At which place is it possible to define this?
FS#14012and are not relevant to this task's topic.If you set "AutoAddDevices" to true you have: Option "xkb_layout" "us". This is not a problem; it's the way new xorg works (http://archlinux.org/news/424/). There were tons of bug reports, forum and mailing list discussions about this "issues". So I pointed to the wiki page where there is also a section "When I press a key, X thinks I pressed it multiple times".
In that section is also described how to setup the keyboard layout inside hal fdi files.
I didn't intend to be rude; the fact is that keeping the bug reports clean is better for everyone.
And I think that reading http://wiki.archlinux.org/index.php/Xorg_input_hotplugging tooks less time than writing our last three comments, including this.
Hope this helps.
The problem of a beginner (such I), is to find out what is happening.
The section "When I press..." is exactly what I was looking for... but I have overseen it.
And I don't made the association with the "...hotplugging".
I beg your pardon. And thank for your (and other persons) help.