Bug 547024

Summary:	Compiz segfaults if I "Use Previous Settings" in desktop-effects
Product:	[Fedora] Fedora	Reporter:	Rohan Dhruva <rohandhruva>
Component:	compiz	Assignee:	Adel Gadllah <adel.gadllah>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	12	CC:	adel.gadllah, hidoufr
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-18 19:50:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rohan Dhruva 2009-12-13 09:03:11 UTC

Description of problem:
I have a completely updated Fedora 12 system. Compiz was disabled by default on install. When I go to the desktop-effects in System - Preferences, and select "Compiz", it presents me with an option to either "Use Previous Settings", or "Keep Settings". If I select "Keep Settings", everything is fine and compiz works well and the effects are displayed.

If I instead select "Use Previous Settings", abrt reports that compiz has segfaulted. There is no visible indication of the segfault except for the abrt warning. I can still close desktop-effects, and use my system normally. Or I can instead choose to enable compiz again. This leads me to wonder abrt is reporting a false-positive segfault. abrt is also unable to generate a backtrace which I can use to report. I have the corresponding debug packages installed, yet abrt is not generating a backtrace (for which I will file a separate bug).

Can I somehow manually generate backtrace, or confirm whether compiz is actually segfaulting in the first place?

Version-Release number of selected component (if applicable):
compiz-0.8.2-19.fc12.x86_64

How reproducible:
Always

Steps to Reproduce:
1. System - Preferences - Desktop Effects
2. Select "Compiz"
3. Click on "Use Previous Settings"
  
Actual results:
abrt reports a segfault

Expected results:
No segfault

Additional info:
I have installed abrt from updates-testing in order to try and generate a backtrace, but even that isn't working out.

Comment 1 Adel Gadllah 2009-12-13 17:10:23 UTC

Some plugins do segfault when being unloaded, there is a fixed package in updates-testing, I will push it to stable once I fix the regression introduced in it (the wall plugin is broken).

Can you you confirm that it does not segfault with the updates-testing version?

Comment 2 Rohan Dhruva 2009-12-13 18:51:40 UTC

After installing the version from updates-testing, it does not get enabled at all. I don't see any segfaults, but I can't determine whether that is because the bug is fixed, or because compiz doesn't load at all. Using desktop-effects killed all window managers, I had to go to vt2 and use metacity --replace. 

Using compiz --replace from the terminal shows this output:

$ compiz --replace
compiz (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format
compiz: symbol lookup error: /usr/lib64/compiz/libwall.so: undefined symbol: getCompPluginInfo

I think it's the broken wall plugin that you mentioned.

Comment 3 Adel Gadllah 2009-12-14 11:59:59 UTC

(In reply to comment #2)
> After installing the version from updates-testing, it does not get enabled at
> all. I don't see any segfaults, but I can't determine whether that is because
> the bug is fixed, or because compiz doesn't load at all. Using desktop-effects
> killed all window managers, I had to go to vt2 and use metacity --replace. 
> 
> Using compiz --replace from the terminal shows this output:
> 
> $ compiz --replace
> compiz (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format
> compiz: symbol lookup error: /usr/lib64/compiz/libwall.so: undefined symbol:
> getCompPluginInfo
> 
> I think it's the broken wall plugin that you mentioned.  

Yes that is the wall plugin regression, thanks for testing though.

Comment 4 Hamidou Dia 2009-12-18 19:50:36 UTC

Hi All.

Adel, thanks for handling (had barely the time lastely to dedicate time triaging).
Continue doing a good job maintaining some folks´s preferred package :-)

Regards.

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

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