Summary: | Follow xcb/xorg-server upgrade guide causes evdev to stop working | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | gef.kornflakes, SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
![]() ABI mismatch between xorg an drivers... You may have forgotten to rebuild all xf86 drivers, as advised at the end of xorg-server upgrade : echo ewarn "You must rebuild all drivers if upgrading from xorg-server 1.5" ewarn "or earlier, because the ABI changed. If you cannot start X because" ewarn "of module version mismatch errors, this is your problem." echo ewarn "You can generate a list of all installed packages in the x11-drivers" ewarn "category using this command:" ewarn "emerge portage-utils; qlist -I -C x11-drivers/" ebeep 5 epause 10 And comment 1 combined with this little gem: "I am not rebuilding the driver for getting it working again." can lead to only one resolution. (In reply to comment #1) > ABI mismatch between xorg an drivers... You may have forgotten to rebuild all > xf86 drivers, as advised at the end of xorg-server upgrade : > Yes, I know, but I think that should be noted in the guide that, if X are restarted (for example, if I logout from my X session when using gdm) after ending xcb "stage", X won't work, having to login vie SSH for fixing the problem (In reply to comment #2) > And comment 1 combined with this little gem: > "I am not rebuilding the driver for getting it working again." > can lead to only one resolution. > It was a typo: not -> now Well, libxcb upgrade and xorg-server upgrade are independent problems, you were simply misfortunate to have them happen at the same time. I'd still say it's INVALID, but waiting for a second opinion. It will depend in how they will be stabilized: if new X and xcb go to stable at the same time, the problem will appear It's not clear for me in which order you updated xcb and xorg-server. The xorg guide says to first update xcb. Did the xorg-server-1.5 stop working after the xcb update or did you first update xorg and then xcb? In either case you have to rebuild the drivers as mentioned above right after the xorg update. The problem appeared just after updating to new libxcb and while rebuilding broken packages. On that situation, X got restarted and, then, not working due to new xorg-server being rebuilt and evdev not still re-emerged. (In reply to comment #7) > On that situation, X got restarted and, then, not working due > to new xorg-server being rebuilt and evdev not still re-emerged. It should be clear that you shouldn't restart X without rebuild all it's drivers. As the post install message says: "If you cannot start X because of module version mismatch errors, this is your problem." I got the same problem,and now it is working fine. I check again the portage elog,notice the message for "media-libs/mesa",then I rebuild it and "xf86-input-evdev" later, the problem was fixed. |