Bug 334827

Summary: crash at startup in KWindowInfo
Product: [Frameworks and Libraries] kdelibs Reporter: Filipe Azevedo <pasnox>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: grave CC: mgraesslin, mk-lists
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: macOS   
Latest Commit: Version Fixed In:
Attachments: mac os x crash backtrace

Description Filipe Azevedo 2014-05-15 17:56:48 UTC
I self built the sources as it's not packaged.
Once installed, if I start it, it crash during initialization in KWindowInfo.

Reproducible: Always

Steps to Reproduce:
1. Start yakuake
2.
3.
Actual Results:  
Crash

Expected Results:  
Run ;)
Comment 1 Christoph Feck 2014-05-15 18:26:10 UTC
Is it possible to show the backtrace of the crash?
Comment 2 Filipe Azevedo 2014-05-15 18:31:46 UTC
Created attachment 86653 [details]
mac os x crash backtrace
Comment 3 Filipe Azevedo 2014-05-15 18:32:20 UTC
(In reply to comment #1)
> Is it possible to show the backtrace of the crash?
done.
Comment 4 Eike Hein 2014-05-16 16:21:59 UTC
Reassigning.

Martin: I'm CC'ing you here because you know more about KWindowSystem in Frameworks and might want to reassign to frameworks-kwindowsystem.
Comment 5 Martin Flöser 2014-05-17 06:24:38 UTC
(In reply to comment #4)
> Martin: I'm CC'ing you here because you know more about KWindowSystem in
> Frameworks and might want to reassign to frameworks-kwindowsystem.

sorry cannot help here. I don't know anything about the Mac OS implementation in kdelibs4 time and in frameworks it's currently disabled.
Comment 6 Filipe Azevedo 2014-05-24 09:06:03 UTC
If you guide me on how produce a dev environment on mac os x, I could have a look at it.
Comment 7 Marko Käning 2014-05-24 09:12:13 UTC
(In reply to comment #6)
> If you guide me on how produce a dev environment on mac os x, I could have a
> look at it.

Great. Let's get into touch.
Comment 8 Marko Käning 2014-07-11 06:14:50 UTC
There is a solution to this in https://bugs.kde.org/show_bug.cgi?id=337154

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