Bug 24769

Summary:

Cairo-dock with OpenGL causes crashes

Product:

xorg

Reporter:

tkitsos

Component:

Driver/intel

Assignee:

Ian Romanick <idr>

Status:

RESOLVED WORKSFORME

QA Contact:

Xorg Project Team <xorg-team>

Severity:

critical

Priority:

high

Keywords:

NEEDINFO

Version:

unspecified

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
part of xorg.log	none

Description tkitsos 2009-10-27 18:13:35 UTC

Created attachment 30760 [details]
part of xorg.log

Very basic Fedora 11 system with Firefox and Flash.

Cairo-dock
Start normal way with drop down menu.
Cairo default dock with firefox launcher. OpenGL
Using Firefox when a Fedora system automatic update showed up. Click on icon to 
view update. Shows 1 update started to check for dependencies. It them froze up. 
May have had a text file open also not sure. Everything froze. Crtl Alt Del or 
Crtl Alt Esc did nothing. Had to shut off pc.

Start normal way with drop down menu.  OpenGL
Using Firefox minimized. Click on SD mounted card on desktop, it opens, click on 
one folder it opens but shows nothing because it froze up. Everything froze. 
Crtl Alt Del or Crtl Alt Esc did nothing. Had to shut off pc.

Start by using cairo-dock -l debug > debug.txt  OpenGL
Using Firefox minimized. Click on my Home folder on desk top it opens, click on 
one folder it opens, but shows nothing because it froze up. Terminal window 
froze also. Everything froze. Crtl Alt Del or Crtl Alt Esc did nothing. Had to 
shut off pc. Can't find any debug.txt file.

Cairo-dock-team says it's an Intel card problem. I should report it. ...Tell them you are experiencing crashes with Cairo-Dock 2.1.1 and your card,
they could then reproduce the problem and fix it.

https://bugs.launchpad.net/bugs/460850

using: cairo-dock-2.1.0-1.fc11(i586)
from:
RPM Fusion for Fedora 11 -Free
RPM Fusion for Fedora 11 -Free -Updates

cairo-dock -v =2.1.0-1  with OpenGL
Firefox 3.5.3.
Gnome 2.26.3
Fedora 11 2.6.30.8-64.fc11.i686.PAE  32bit
Memory 2.0 GiB
Intel Core 2 Duo T5250 1.50Ghz
Avail Disk space 19.8 GiB
File System ext4
metacity
HP DV2617US Centrino Core 2 Duo T5250
.
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (rev 0c)
.
Intel 8201H
.
i915                  154304  2 
drm                   168304  2 i915
i2c_algo_bit            4804  1 i915
video                  18708  1 i915
output                  2440  1 video
i2c_core               24984  4 i2c_i801,i915,drm,i2c_algo_bit

xorg-x11-drv-intel-2.7.0-7.fc11(i586)
Cairo team: Also affects: xserver-xorg-video-intel

Comment 1 Carl Worth 2009-11-06 11:53:30 UTC

Hi tkitsos,

From what I can gather from the linked-to bug report, you're getting crashes
when you run "cairo-dock" (which uses OpenGL) but not when running
"cairo-dock -c" (which uses some cairo-based code within cairo-dock).

I also see that you're using version 2.7.0 of the Intel driver.

The first thing for you to do is to test with version 2.9.1 of the driver and
to report back here if the problem still exists, (and remove the NEEDINFO
keyword when you do).

Meanwhile, I'll assign this bug to Ian Romanick for when you report back.

-Carl

Comment 2 Ian Romanick 2009-11-23 11:07:10 UTC

Closing due to more than two weeks with no reply from the submitter.

Comment 3 tkitsos 2009-11-23 14:18:39 UTC

I just got the New Fedora 12 disk in the mail today. It has the new Intel drivers. I'm installing it now and will report back results later today.

Comment 4 tkitsos 2009-11-23 21:04:19 UTC

I installed new Fedora 12.  Cairo-Dock seems to work o.k. now.  Opening folders in Nautilus is no longer crashing the whole OS.  Programs launch o.k.   Thanks for your help.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.