Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31776 - [eclipse] Crashing Very Often

Attached to Project: Arch Linux
Opened by Jimmie Butler (jimmiebtlr) - Tuesday, 02 October 2012, 23:23 GMT
Last edited by Allan McRae (Allan) - Monday, 29 April 2013, 05:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
The following error appears when trying to start a project or change the layout of the workspace.
<code>
**
Gtk:ERROR:gtkwidget.c:8854:gtk_widget_real_map: assertion failed: (gtk_widget_get_realized (widget))
</code>

Additional info:
* package version(s)
Version 4.2.1-1

A quick google search turns up another person with the same issue
http://mateusz.loskot.net/2012/09/14/eclipse-4-2-throwing-gtk_widget_real_map-assertion-failed/
Though I havn't heard back to see if he's found a solution.

Steps to reproduce:
Open Eclipse -> try to manipulate the workspace or start a project.
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 29 April 2013, 05:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in 4.2.2
Comment by Jimmie Butler (jimmiebtlr) - Tuesday, 02 October 2012, 23:26 GMT
Sorry about the critical status, should probably be high.
Comment by Denis R. (lezter) - Thursday, 04 October 2012, 14:49 GMT
I had the same issue with Eclipse 4.2. And nothing changed after update to 4.2.1.
Oracle JDK 1.7.0_05
Comment by Denis R. (lezter) - Thursday, 04 October 2012, 15:56 GMT
Official build from eclipse.org also has the same bug.
Comment by Ionut Biru (wonder) - Thursday, 04 October 2012, 15:59 GMT
we use the clasic version and we don't build anything, we just repackage it.
Comment by Jimmie Butler (jimmiebtlr) - Thursday, 04 October 2012, 19:09 GMT
If I change gnome gtk theme to the default theme, the error stops. I believe this is due to my install currently missing a murrine engine dependency. It would seem either gtk or eclipse is not gracefully handling a missing theme dependency.

EDIT: Installing murrine doesn't seem to fix the issue.
Comment by Denis R. (lezter) - Sunday, 14 October 2012, 19:49 GMT
Hm, strange - Eclipse works fine in XFCE, but crashes in KDE. I've removed ~/.gtkrc-2.0-kde and gtk-kde4 but nothing changed. What does KDE that XFCE doesn't?..
Comment by Andrew Gaydenko (student975) - Sunday, 14 October 2012, 19:58 GMT
Denis, you can use own gtkrc for any app by adding to start script this environment var:

export GTK2_RC_FILES="/home/user/.gtkrc-2.0.eclipse"

I'm afraid KDE can create gtk-related configs on the fly.
Comment by Ivan Koryabkin (apathism) - Wednesday, 31 October 2012, 22:50 GMT
Looks like it's fixed in upstream in the integration builds: https://bugs.eclipse.org/bugs/show_bug.cgi?id=382812
Comment by Jimmie Butler (jimmiebtlr) - Thursday, 01 November 2012, 01:08 GMT
Seems fixed to me as well
Comment by Mateusz Loskot (mloskot) - Thursday, 15 November 2012, 00:00 GMT
  • Field changed: Percent Complete (100% → 0%)
The bug report has been closed without clear conclusion on how Arch users should get the fix. Last update of eclipse package is 2012-09-29, so it pre-dates the fix. Is the package going to be updated? IMHO, it should be clarified on the bug closure, or the bug should be left opened, as Arch users are still affected.
Comment by Mateusz Loskot (mloskot) - Thursday, 15 November 2012, 10:46 GMT
Meanwhile, to allow early access to the fixed build of Eclipse, I've proposed package for Eclipse stable build based on the stable integration builds (it's different to eclipse-integration):
https://mailman.archlinux.org/pipermail/aur-general/2012-November/020942.html
Comment by Greg (dolby) - Saturday, 17 November 2012, 09:07 GMT
This is not an Archlinux packaging bug & has been fixed upstream so it has no reason to stay open here, its served its purpose. Arch users can either upgrade to newer unreleased versions or use your aur package.
Comment by Mateusz Loskot (mloskot) - Saturday, 17 November 2012, 14:31 GMT
@Greg This is clear and understand it. The reason I requested to open it is that closing a bug without providing a minimal comment on when Arch users will get the fix is not the right way to close a bug. At least, it should be explained in closing comment that Arch package will get the fix as soon as Eclipse releases version 4.3. Otherwise, users read the bug report has been closed as fixed, but are left confused on how they can obtain the fixed version. OK, they can dig through the lengthy bug report at Eclipse and apply some deduction, but that is not the user-friendly approach, is it.
Comment by Greg (dolby) - Saturday, 17 November 2012, 14:33 GMT
Yes of course. Thanks for writing the aur script btw.

Loading...