Description of problem: Well I'm not exactly sure how it relates all together but recent xorg releases are quite problematic in use - one of the biggest problem seems to be - that suspend/resume is no longer usable since on resume - I start to get this error message: $ xhost + Invalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyInvalid MIT-MAGIC-COOKIE-1 keyxhost: unable to open display ":0" -- or whole Xsession directly fails with several gnome processes coredumping like this: Dec 5 11:21:25 linux kernel: [167545.092423] wnck-applet[30558]: segfault at 60 ip 00007fd02ec85b39 sp 00007fffa2b5ff30 error 4 Dec 5 11:21:25 linux kernel: [167545.095444] notification-da[30553]: segfault at 60 ip 00007fb6f7ef0b39 sp 00007fff0123c4f0 error 4 in libgdk-3.so.0.304.0[7fb6f7ed2000+8 2000] Dec 5 11:21:25 linux kernel: [167545.095643] gnome-screensav[30552]: segfault at 60 ip 00007fec3f3f9b39 sp 00007fff3fbc1db0 error 4 in libgdk-3.so.0.304.0[7fec3f3db000+8 2000] Dec 5 11:21:25 linux kernel: [167545.095836] gnome-panel[30542]: segfault at 60 ip 00007f3804d0cb39 sp 00007fff40bd8f70 error 4 in libgdk-3.so.0.304.0[7f3804cee000+82000 ] Dec 5 11:21:25 linux kernel: [167545.096973] clock-applet[30560]: segfault at 60 ip 00007f55c30e0b39 sp 00007fff4e780150 error 4 in libgdk-3.so.0.304.0[7f55c30c2000+8200 0] Dec 5 11:21:25 linux kernel: [167545.097168] notification-ar[30562]: segfault at 60 ip 00007f0d07e1cb39 sp 00007fffe608c3e0 error 4 in libgdk-3.so.0.304.0[7f0d07dfe000+8 2000] Dec 5 11:21:25 linux kernel: [167545.179971] in libgdk-3.so.0.304.0[7fd02ec67000+82000] Dec 5 11:21:25 linux kernel: [167545.204059] gnome-terminal[30589]: segfault at 60 ip 00007f1c131a7b39 sp 00007fffb053f5e0 error 4 in libgdk-3.so.0.304.0[7f1c13189000+82 000] Dec 5 11:21:25 linux kernel: [167545.226200] gnome-settings-[30505]: segfault at 60 ip 00007fb68e3f0b39 sp 00007fff4283e1e0 error 4 in libgdk-3.so.0.304.0[7fb68e3d2000+8 2000] Dec 5 11:21:25 linux gnome-session[30470]: ******************* START ******************************** Dec 5 11:21:25 linux gnome-session[30470]: Frame 0: gnome-session() [0x41ace7] Dec 5 11:21:25 linux gnome-session[30470]: Frame 1: gnome-session() [0x41b0ca] Dec 5 11:21:25 linux gnome-session[30470]: Frame 2: /lib64/libpthread.so.0(+0xf4f0) [0x7f4d875e24f0] Dec 5 11:21:25 linux gnome-session[30470]: Frame 3: /usr/lib64/libgdk-3.so.0(+0x1eb39) [0x7f4d890c7b39] Dec 5 11:21:25 linux gnome-session[30470]: Frame 4: /usr/lib64/libgdk-3.so.0(+0x418c5) [0x7f4d890ea8c5] Dec 5 11:21:25 linux gnome-session[30470]: Frame 5: /usr/lib64/libgdk-3.so.0(+0x4dda0) [0x7f4d890f6da0] Dec 5 11:21:25 linux gnome-session[30470]: Frame 6: /usr/lib64/libgdk-3.so.0(+0x4d8be) [0x7f4d890f68be] Dec 5 11:21:25 linux gnome-session[30470]: Frame 7: /usr/lib64/libgdk-3.so.0(gdk_display_get_event+0x71) [0x7f4d890c9381] Dec 5 11:21:25 linux gnome-session[30470]: Frame 8: /usr/lib64/libgdk-3.so.0(+0x4d3e2) [0x7f4d890f63e2] Dec 5 11:21:25 linux gnome-session[30470]: Frame 9: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x16a) [0x7f4d862f998a] Dec 5 11:21:25 linux gnome-session[30470]: Frame 10: /lib64/libglib-2.0.so.0(+0x46d50) [0x7f4d862f9d50] Dec 5 11:21:25 linux gnome-session[30470]: Frame 11: /lib64/libglib-2.0.so.0(g_main_loop_run+0x75) [0x7f4d862fa155] Dec 5 11:21:25 linux gnome-session[30470]: Frame 12: /usr/lib64/libgtk-3.so.0(gtk_main+0x8d) [0x7f4d894a80ad] Dec 5 11:21:25 linux gnome-session[30470]: Frame 13: gnome-session() [0x40c198] Dec 5 11:21:25 linux gnome-session[30470]: Frame 14: /lib64/libc.so.6(__libc_start_main+0xed) [0x7f4d85f1e69d] Dec 5 11:21:25 linux gnome-session[30470]: Frame 15: gnome-session() [0x40c405] Dec 5 11:21:25 linux gnome-session[30470]: ******************* END ********************************** I'm using Lenovo T61, with intel driver and kernel 3.1 or 3.2-rc3 Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.11.99.1-9.20111109.fc17.x86_64 the last usable version was: xorg-x11-server-1.11.1-2.fc17 however because of various ABI changes there is no easy way to revert back to such older package :(.... How reproducible: Steps to Reproduce: 1. pm-suspend 2. resume 3. Actual results: Expected results: Additional info:
So the issue with MIT-MAGIC-COOKIE is somehow related to switch to a different network where the machine get different network name. So when I list cookies I'm getting some cookie for old network and some new different cookie for new network. When I manually remove all old cookies via xauth remove - I get again usable display where I could open new windows - however doing this manually after each resume in different network isn't really practical. So anyone knows what has changed in X, that a different network name is now problem - I'm pretty sure I've not changed anything in my network setting for at least a year? How is the new different cookie getting into the xauth list ? linux/unix:0 MIT-MAGIC-COOKIE-1 c223f7790d4024d8651e939664763027 linux:0 MIT-MAGIC-COOKIE-1 c223f7790d4024d8651e939664763027 kabi/unix:0 MIT-MAGIC-COOKIE-1 9b99d3b71535084039eff094eee81cdc [fe80::21c:25ff:fe14:4ae2]:0 MIT-MAGIC-COOKIE-1 9b99d3b71535084039eff094eee81cdc [fe80::21c:bfff:fe03:287]:0 MIT-MAGIC-COOKIE-1 9b99d3b71535084039eff094eee81cdc [2620:52:0:221f:21c:25ff:fe14:4ae2]:0 MIT-MAGIC-COOKIE-1 9b99d3b71535084039eff094eee81cdc Why do I get cookies generated for IPV6 nework where my machine has IPV6 disabled via kernel drive so network interface can't get IPV6 address ?
Because xauth is terrible like that. Try checking out libXau from pkg-git (rawhide's branch is fine) and rebuilding it with the commented-out xau-1.0.4-local.patch applied. I've been trying to get someone to actually test that for ages now.
Well - for now I've disable the problem on my system differently - I've added small section into /etc/NetworkManager/NetworkManager.conf: [keyfile] hostname=linux So do you have some rpm I could install and test with some settings?
I had thought "try building this package with this patch enabled" was guidance enough, but it seems not. Try this: http://koji.fedoraproject.org/koji/taskinfo?taskID=3892684
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.