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#28926 - Xorg crashes with xf86-video-intel-2.18.0-1 when two monitors are connected
Attached to Project:
Arch Linux
Opened by Michael Helmling (supermihi) - Thursday, 15 March 2012, 14:49 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 15 March 2012, 21:40 GMT
Opened by Michael Helmling (supermihi) - Thursday, 15 March 2012, 14:49 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 15 March 2012, 21:40 GMT
|
DetailsDescription:
Since the latest updates of xf86-video-intel and intel-dri, the X server does not start when two monitors are connected. In my case, I don't even get to see the GDM login manager; others seem to have similar problems as soon as gnome-session starts: https://bbs.archlinux.org/viewtopic.php?id=137593 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/921236 Installing xf86-input-evdev-git from AUR does not help (the launchpad report suggests that evdev causes the problem). I also noticed a line [ 4.065215] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work in dmesg. However, * this also appears with the working 2.7 version * it does not disappear when I set the allow_duplicates=1 option, neither does that help Additional info: * package version(s): xf86-video-intel 2.18.0-1, intel-dri-8.0.1-2 * Xorg.0.log attached 
Xorg.0.log
(54.9 KiB)
|
This task depends upon
Comment by Andreas Radke (AndyRTR) -
Thursday, 15 March 2012, 21:40 GMT
Please report this upstream. It's not a packaging bug.