Bug 8954

Summary: Ardour 2 and Ardour 3 seg fault if oxygen-gtk is installed
Product: Mageia Reporter: Jim Dines <jdines>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: zen25000
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Jim Dines 2013-02-03 16:53:27 CET
Affects both versions of ardour including:
ardour3-3.0-0.13700.2.mga3
ardour-2.8.16-3.mga3

strace results:
....
open("/home/jdines/.kde4/share/config/oxygenrc", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/home/jdines/.kde4/share/config/oxygenrc", O_RDONLY) = -1 ENOENT (No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x50} ---
+++ killed by SIGSEGV +++
Segmentation fault

Removing oxygen-gtk fixes things, and reinstalling it breaks them again.
Comment 1 Barry Jackson 2013-02-03 22:43:58 CET
I cannot reproduce here with ardour3 and I have oxygen-gtk installed.
I don't have a ~/.kde4/share/config/oxygenrc either.

Did you test with a new user?

CC: (none) => zen25000

Comment 2 Jim Dines 2013-02-03 23:43:41 CET
This system is a Mageia 3 system recently upgraded from Mageia 2 via the Beta 2 DVD.

After copying /usr/share/themes/oxygen-gtk/gtk-3.0/oxygenrc to ~/ .kde4/share/config/ the problem went away.  Strangely, after removing it ardour2 and ardour3 no longer segfault.  I removed and re-installed oxygen-gtk multiple times to verify that it really was the presence and absence of this package that was the culprit originally.

I'm sorry I cannot be more help, but maybe the next guy will have the same issue, search for and find this bug, try what I did, and be able to use his system for ardour again.

Obviously, since neither of us can now reproduce the problem there is not much either of us can do to track it down.  I would guess that ardour doesn't look in  /usr/share/themes/oxygen-gtk/gtk-3.0/ and failing to find oxygenrc anywhere, goes ahead and does something that assumes it did.

Thanks, and sorry I couldn't be more help :-(
Comment 3 Barry Jackson 2013-02-04 11:34:16 CET
OK - so closing.

If anyone finds a way to reproduce this, then feel free to re-open with details.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME