Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.0 detected a crash. How to reproduce ----- 1.just logged in and the error popped up after comiz crashed 2. 3. Attached file: backtrace cmdline: compiz component: compiz executable: /usr/bin/compiz kernel: 2.6.31.9-174.fc12.i686 package: compiz-0.8.2-19.fc12 rating: 3 reason: Process was terminated by signal 3
Created attachment 380997 [details] File: backtrace
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Program terminated with signal 3, Quit. #0 0x00a1d416 in __kernel_vsyscall () Thread 1 (Thread 1799): #0 0x00a1d416 in __kernel_vsyscall () No symbol table info available. #1 0x00485e0b in __poll (fds=0x9a72e48, nfds=8, timeout=1499) at ../sysdeps/unix/sysv/linux/poll.c:83 resultvar = <value optimized out> resultvar = <value optimized out> oldtype = 32767 result = <value optimized out> #2 0x080547b4 in doPoll (timeout=<value optimized out>) at display.c:1203 rv = <value optimized out> #3 0x0805755b in eventLoop () at display.c:1655 ---------------------------------- Hi Phil, Just a question: did this crash occurred only once? Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers ---------------------------------- PS: this is a F12 ticket, switching to ASSIGNED status as well (Triaged keyword was already set).
yes it only happens once each boot, when i restarted compiz after the crash everything was ok till the next reboot. i no longer have the machine here as it was setuip for a friend but i can get a hold of it for debugging if needs be.
See also bug 538679. I am fairly certain that these bugs are related, if not the same. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 538679 ***