Bug 538698 - [abrt] crash detected in compiz-0.8.2-19.fc12 compiz-0.8.2-21.fc12#0 in doPoll at display.c:1209
Summary: [abrt] crash detected in compiz-0.8.2-19.fc12 compiz-0.8.2-21.fc12#0 in doPo...
Keywords:
Status: CLOSED DUPLICATE of bug 538679
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2078e000aeffab271d56458df13...
: 537003 552716 553209 553476 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-19 05:42 UTC by qianhan1986
Modified: 2010-12-02 21:03 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-08 03:39:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
xorg.conf (2.17 KB, text/plain)
2009-11-23 01:05 UTC, qianhan1986
no flags Details
command dmesg output (41.90 KB, text/plain)
2009-11-23 01:18 UTC, qianhan1986
no flags Details
Xorg.0.log.old (68.97 KB, text/plain)
2009-11-23 01:20 UTC, qianhan1986
no flags Details
/var/cache/abrt/ccpp-1258442865-1676/coredump (940.00 KB, application/octet-stream)
2009-11-27 08:44 UTC, qianhan1986
no flags Details

Description qianhan1986 2009-11-19 05:42:24 UTC
abrt detected a crash.

backtrace
-----
Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  doPoll (timeout=<value optimized out>) at display.c:1209
	in display.c

Thread 1 (Thread 1676):

cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat
component: compiz
executable: /usr/bin/compiz
kernel: 2.6.31.5-127.fc12.i686.PAE
package: compiz-0.8.2-19.fc12
rating: 0
reason: Process was terminated by signal 11

Comment 1 Hamidou Dia 2009-11-22 03:40:58 UTC
Hi Qian.

Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Regards

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 qianhan1986 2009-11-23 01:05:55 UTC
Created attachment 372993 [details]
xorg.conf

Hi ,This is my xorg.conf file.

Comment 3 qianhan1986 2009-11-23 01:18:53 UTC
Created attachment 372994 [details]
command  dmesg output

and here's the information from command dmesg.

Comment 4 qianhan1986 2009-11-23 01:20:07 UTC
Created attachment 372995 [details]
Xorg.0.log.old

Comment 5 Hamidou Dia 2009-11-24 00:10:48 UTC
Hi Qian.

Many thanks.

Regards.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Hamidou Dia 2009-11-27 06:42:38 UTC
Hi Qian.

I just paid attention to the fact that the the backtrace file that should have been generated with report and automatically uploaded as an uncompressed attachment is missing (unless you unchecked the "backtrace" checkbox before submitting the report).

Please could you kindly go for it?

You can find the backtrace file into /var/cache/abrt/ccpp* directory corresponding to the day that the crash occurred.
In case you had several in the same day, look for the one containing.

--------------------------------------

backtrace
-----
Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  doPoll (timeout=<value optimized out>) at display.c:1209
 in display.c

Thread 1 (Thread 1676):
--------------------------------------

Again, thanks in advance.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 7 qianhan1986 2009-11-27 08:44:04 UTC
Created attachment 374163 [details]
/var/cache/abrt/ccpp-1258442865-1676/coredump

Hi, Hamidou:
I found a file named coredump in the dir. I think that's the file you need.
because there's another file named backtrace in the dir but containing  few information,I'll show it below:

Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  doPoll (timeout=<value optimized out>) at display.c:1209
	in display.c

Thread 1 (Thread 1676):


btw,I didn't uncheck the  "coredump" checkbox before committing, maybe because of my poor network environment. well,anyway I'll upload the coredump for you.

Comment 8 Hamidou Dia 2009-11-27 16:29:02 UTC
Ok.

So I have the BT file. But it looks like truncated.

-------------------------------------------------------------------------
BFD: Warning: /home/liveuser/Downloads/core is truncated: expected core file size >= 28692480, found: 962560.
Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  doPoll (timeout=<value optimized out>) at display.c:1209
1209		for (i = core.nWatchFds - 1, w = core.watchFds; w; i--, w = w->next)
(gdb) bt
Cannot access memory at address 0xbfcc7adc
(gdb) print i
$1 = <value optimized out>
(gdb) print w
$2 = (CompWatchFd *) 0x10
(gdb) print (w->next)
Cannot access memory at address 0x10
--------------------------------------------------------------------------

So not sure it is going to be exploitable.

Qian, could you check the file size on your computer ?

If you have

[liveuser@localhost ~]$ ll Downloads/core 
-rw-rw-r--. 1 liveuser liveuser 962560 2009-11-27 15:55 Downloads/core

It means that it is incomplete. And in this case we will leave this up to the maintainer (Adel) to decide whether or not this can be pushed forward anyway or not.

In the case that your file in local is complete, I really invite you to try upload the file again, and check the size as reported by the bugzilla ticket to know if you succeeded.

Thanks in advance.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 9 Hamidou Dia 2009-11-27 16:30:45 UTC
As well, do you remember if a special action triggered this issue or if it occured -randomly-?

Thanks

Comment 10 qianhan1986 2009-11-30 02:07:44 UTC
Hi,Hamidou:
the file I uploaded is the same size as my local file.

-rw-r--r-- 1 root root 962560 11月 27 16:37 coredump

I think you're right,I checked backtrace and coredump files in other dirs, this coredump is much  smaller than other coredump files. 
  I don't remember how this bug was triggered.the OS Fedora12 on my machine is upgraded from Fedora11.

Comment 11 Hamidou Dia 2009-12-04 08:06:52 UTC
Hi Qian.

Sorry to come late.
Many thanks for the upload attempt and the information.
This issue does looks like a 100% compiz related. I hope that the maintainer
would have enough information in order to fix this issue (not sure).

@Adel: Assigning to you (from NEW to ASSIGNED).

Regards.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 12 Hamidou Dia 2009-12-12 08:59:58 UTC
Ticket 537003 provided the same BT: 

Core was generated by `compiz --ignore-desktop-hints glib gconf gnomecompat'.
Program terminated with signal 11, Segmentation fault.
#0  doPoll (timeout=<value optimized out>) at display.c:1209
	in display.c

Thread 1 (Thread 1744):
#0  doPoll (timeout=<value optimized out>) at display.c:1209
        w = 0x28
        i = <value optimized out>
        rv = 4
#1  0x0805755b in eventLoop () at display.c:1655
        event = {type = 123, xany = {type = 123, serial = 43099, send_event = 
    0, display = 0x9bb0820, window = 14680068}, xkey = {type = 123, serial = 
    43099, send_event = 0, display = 0x9bb0820, window = 14680068, root = 
    44040553, subwindow = 0, time = 0, x = 444728, y = 0, x_root = 7537674, 
            y_root = 59572347, state = 7537674, keycode = 15, same_screen = 
    0}, xbutton = {type = 123, serial = 43099, send_event = 0, display = 
    0x9bb0820, window = 14680068, root = 44040553, subwindow = 0, time = 0, 
            x = 444728, y = 0, x_root = 7537674, y_root = 59572347, state = 
    7537674, button = 15, same_screen = 0}, xmotion = {type = 123, serial = 
    43099, send_event = 0, display = 0x9bb0820, window = 14680068, root = 
    44040553, subwindow = 0, time = 0, x = 444728, y = 0, x_root = 7537674, 
            y_root = 59572347, state = 7537674, is_hint = 15 '\017', 
            same_screen = 0}, xcrossing = {type = 123, serial = 43099, 
            send_event = 0, display = 0x9bb0820, window = 14680068, root = 
    44040553, subwindow = 0, time = 0, x = 444728, y = 0, x_root = 7537674, 
            y_root = 59572347, mode = 7537674, detail = 15, same_screen = 0, 
            focus = 16, state = 16}, xfocus = {type = 123, serial = 43099, 
            send_event = 0, display = 0x9bb0820, window = 14680068, mode = 
    44040553, detail = 0}, xexpose = {type = 123, serial = 43099, 
            send_event = 0, display = 0x9bb0820, window = 14680068, x = 

--------------------------------------------

Comment 13 Hamidou Dia 2009-12-12 09:00:28 UTC
*** Bug 537003 has been marked as a duplicate of this bug. ***

Comment 14 Chris Campbell 2010-01-06 00:17:30 UTC
*** Bug 552668 has been marked as a duplicate of this bug. ***

Comment 15 Chris Campbell 2010-01-06 00:20:17 UTC
*** Bug 552716 has been marked as a duplicate of this bug. ***

Comment 16 Hamidou Dia 2010-01-07 14:24:23 UTC
*** Bug 553209 has been marked as a duplicate of this bug. ***

Comment 17 Hamidou Dia 2010-01-07 14:30:26 UTC
Updating title: crasher reported up to compiz 0.8.2-21 so far

Comment 18 Chris Campbell 2010-01-08 04:07:04 UTC
*** Bug 553476 has been marked as a duplicate of this bug. ***

Comment 19 Jeff Raber 2010-06-08 03:39:56 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 538679 ***


Note You need to log in before you can comment on or make changes to this bug.