But this here on the console looks like an error:
*** glibc detected *** /usr/bin/Xair: double free or corruption (!prev): 0x09071e40 *** ======= Backtrace: ========= /lib/libc.so.6[0x164de8] /lib/libc.so.6(__libc_free+0x79)[0x1682ed] /usr/bin/Xair(Xfree+0x23)[0x8205576] /usr/lib/xair/modules/extensions/libdri.so(DRIDestroyInfoRec+0x2a)[0xe269b7] /usr/lib/xair/modules/drivers/radeon_drv.so(RADEONDRICloseScreen+0x1c3)[0x91f063] /usr/lib/xair/modules/drivers/radeon_drv.so[0x90f1b1] /usr/bin/Xair[0x818f072] /usr/bin/Xair[0x80f84b7] /usr/bin/Xair[0x80d79be] /usr/bin/Xair[0x8156e40] /usr/bin/Xair[0x818c0a3] /usr/bin/Xair[0x81f6a92] /usr/bin/Xair(main+0x7b9)[0x806e3ad] /lib/libc.so.6(__libc_start_main+0xdc)[0x1167a4] /usr/bin/Xair(FontFileCompleteXLFD+0xad)[0x806db3]
Hi,
yes this is a real bad real bug in Xair...
you can improve the quality of this bugreport by 1) installing the respective -debuginfo rpms (in this case of Xair and the driver) 2) running the app from inside gdb and then when the crash hits, 3) type "bt"
that gives a similar backtrace, but with a LOT more useful information (such as function names and filenames + line numbers) for the developers to figure this one out...