Adam Jackson wrote : > David Nielsen wrote: > > > Okay before I open a bug on this, what information do you want and how > > do I pry it out of my machine.. it's afterall a bit hard to read any > > output on a black screen. > > Presumably it still responds to the network, so scp /var/log/Xorg.0.log > to another machine. Alternatively, once it hangs, reboot to runlevel 3 > with rhgb disabled so you can see the server startup log. I know I've been seeing stuff like this lately : Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x71) [0x4a0c01] 1: /lib64/libc.so.6 [0x39e1230210] 2: /usr/lib64/xorg/modules/libfb.so(fbCopyAreammx+0x20b) [0x2aaaadf1eeab] 3: /usr/lib64/xorg/modules/libfb.so(fbComposite+0x5db) [0x2aaaadf0f76b] 4: /usr/lib64/xorg/modules/libxaa.so(XAAComposite+0x2ac) [0x2aaaae1609ec] 5: /usr/bin/Xorg [0x512ddd] 6: /usr/bin/Xorg [0x50f1f8] 7: /usr/bin/Xorg [0x502caf] 8: /usr/bin/Xorg(Dispatch+0x1ca) [0x449c4a] 9: /usr/bin/Xorg(main+0x455) [0x432585] 10: /lib64/libc.so.6(__libc_start_main+0xf4) [0x39e121da44] 11: /usr/bin/Xorg(FontFileCompleteXLFD+0x229) [0x431879] Fatal server error: Caught signal 11. Server aborting And various other issues that could be related to the removal of all legacy x86 packages on my system. I don't dare reboot or file a bug, though, since X is now working and I can't easily reproduce without loosing my work environment :-/ Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 5.92 (FC6 Test3) - Linux kernel 2.6.18-1.2699.fc6 Load : 1.55 1.14 1.04 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
