FS#25886 - [gcin] 1.6.5-1 causes other applications seg-fault.

Attached to Project: Arch Linux
Opened by Henry Lee (bsdson) - Sunday, 04 September 2011, 10:51 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 05 September 2011, 01:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Description:after upgrade to gcin 1.6.5-1, I can no longer launch Nautilus and Empathy and some other applications.

Additional info:
* package version(s): 1.6.5-1
* config and/or log files etc.

Steps to reproduce:
just upgrade to 1.6.5-1 on 64bit platform.
and on launch nautilus and/or empathy, you may see something like this:

[henry@henry_u59 ~]$ empathy

(empathy:1539): Gdk-CRITICAL **: gdk_window_get_screen: assertion `GDK_IS_WINDOW (window)' failed
Segmentation fault

after restore to earlier version,
both of them are okay...
This task depends upon

Closed by  Gaetan Bisson (vesath)
Monday, 05 September 2011, 01:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  gcin-1.6.5-2 in [extra]
Comment by b4283 (b4283) - Sunday, 04 September 2011, 16:13 GMT
Confirmation on this bug. The affected applications on my box is the list: '(brasero evince).

After researching with the developers upstream, this bug has been worked around and seems to be a bug from gtk3 instead of gcin's.

This patch should "fix" the bug: http://paste.pocoo.org/show/469992/
Comment by Gaetan Bisson (vesath) - Sunday, 04 September 2011, 20:48 GMT
I cannot reproduce this bug, so thanks a lot for handling it with upstream.
Please test gcin-1.6.5-2 from [testing] (it contains your patch) and let me know if it solves your issue.
Comment by b4283 (b4283) - Monday, 05 September 2011, 00:25 GMT
It indeed fixes my problem starting evince. But I think we need the original poster to confirm as well.
Comment by Gaetan Bisson (vesath) - Monday, 05 September 2011, 01:18 GMT
No, we don't: your bug is fixed; if Henry's bug is different (which I don't think is very likely), then he should open another bug report and provide more info. (We should avoid discussing different bugs in the same bug report; it makes it a nightmare to understand the issue(s).)