Thanks Markus!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Fix
*** Bug 465485 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
There's no point in delaying a workaround in SWT for this crash.
Attachment 253846 still reproduces on Ubuntu 14.04.
AFAICS, this is the place where the fix in Ubuntu could eventually show up:
** Changed in: eclipse
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
*** Bug 462002 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
*** Bug 457512 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
The issue is fixed in Ubuntu >= 14.10. I proposed a patch to back-port
the fix to 14.04, see https://bugs.launchpad.net/ubuntu/+source/unity-
gtk-module/+bug/1427866/comments/5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I'll assign to myself for now to investigate a fix in Ubuntu. Otherwise
we can try to apply the patch in SWT.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
*** Bug 449031 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
Many thanks for the analysis so far, the explanation with "empty radio
label" makes a lot of sense! - Does anyone know if a ticket already
exists with Ubuntu for getting this fixed ?
We also do see the crash occasionally with Mars on Ubuntu 14.04 64-bit.
The suggested workarounds SWT_GTK3=0
Created attachment 256390
Patch
Hi. I have looked into this problem and came up with the following
workaround patch that still uses Unity and avoids the crash.
I found that the crash occurs because a new Radio menu is created with *empty
label*
for which unity_gtk_action_group_get_state_name()
(In reply to Taehoon Kwak from comment #53)
> I found that the crash occurs because a new Radio menu is created with
> *empty label*
> for which unity_gtk_action_group_get_state_name() returns null and this ends
> up with a null-pointer dereference at g_str_hash().
Would it be a good idea to fix
(In reply to Marc-Andre Laperle from comment #54)
> (In reply to Taehoon Kwak from comment #53)
> > I found that the crash occurs because a new Radio menu is created with
> > *empty label*
> > for which unity_gtk_action_group_get_state_name() returns null and this ends
> > up with a null-pointer
A user reported this problem for the latest SmartGit, too, though we
already set a couple of environment variables in the launcher script to
prevent it. He runs Linux Mint 17.2 Cinnamon and had the Global
Application Menu applet installed. After disabling that, SmartGit did
not crash any more.
--
Note that there was some further discussion of this bug here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461311
In addition to causing crashes when opening the Window menu, it also can
cause reset perspective to crash.
This only occurs under Ubuntu, and seems related to Ubuntu's menuproxy
** Bug watch added: Eclipse bugs #461311
https://bugs.eclipse.org/bugs/show_bug.cgi?id=461311
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in
You can also reproduce this in Eclipse by clicking Run... Breakpoint
Types
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after
Created attachment 254676
crash log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
Created attachment 253846
Short SWT snippet that reproduces the problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
Don't know if it can be useful, but often after the crash the bash shell
from which I've launched Eclipse doesn't respond to keyboard commands.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
(In reply to Cristiano Gaviao from comment #45)
(In reply to Simone Perriello from comment #43)
Do you mean creating a .desktop file? If so, where I have to put the
commands in the exec, right? Can you provide a template of a .desktop file?
I've always launched Eclipse from terminal.
(In reply to Cristiano Gaviao from comment #42)
(In reply to Simone Perriello from comment #41)
Tried, and it always crash every single time.
Have you tried this? to create a desktop configuration file and set its
command as:
env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0
(In reply to Cristiano Gaviao from comment #42)
(In reply to Simone Perriello from comment #41)
Tried, and it always crash every single time.
Have you tried this? to create a desktop configuration file and set its
command as:
env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0
(In reply to Simone Perriello from comment #43)
Do you mean creating a .desktop file? If so, where I have to put the
commands in the exec, right? Can you provide a template of a .desktop file?
I've always launched Eclipse from terminal.
Yep, its a .desktop file that I've put in
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
(In reply to Simone Perriello from comment #39)
For me, no one of the suggested workarounds work. I tried with export
SWT_GTK3=0 or export SWT_GTK3=1, but every time I move the mouse pointer on
ProjectBuild Working Set Eclipse crashes with the following
Have you tried UBUNTU_MENUPROXY=0 ?
--
(In reply to Simone Perriello from comment #41)
Tried, and it always crash every single time.
Have you tried this? to create a desktop configuration file and set its
command as:
env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 /thepathToEclipse/eclipse
I've being using this for months with many ubuntu
(In reply to Marc-Andre Laperle from comment #40)
(In reply to Simone Perriello from comment #39)
For me, no one of the suggested workarounds work. I tried with export
SWT_GTK3=0 or export SWT_GTK3=1, but every time I move the mouse pointer on
ProjectBuild Working Set Eclipse crashes with
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
For me, no one of the suggested workarounds work. I tried with export
SWT_GTK3=0 or export SWT_GTK3=1, but every time I move the mouse pointer on
ProjectBuild Working Set Eclipse crashes with the following
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at
*** Bug 466326 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
I can reproduce the crash using Thomas Singer's example code (comment
9), on Ubuntu 13.10 and 14.04 when UBUNTU_MENUPROXY is enabled. If I
disable UBUNTU_MENUPROXY it works. I think it's the same issue as bug
461311: radio button in the menu. Can we mark one as duplicate of the
other?
--
You
I can confirm this in Comsol Multiphysics, and various versions of
eclipse and liclipse, on Kubuntu 14.04 64-bit. Really serious bug. The
Eclipses tend to crash during debugging but it seems random. Comsol used
to run for a while before crashing but now crashes as soon as you create
a new blank
Ok, changing the combobox appearance as detailed at
http://askubuntu.com/questions/513471/kubuntu-14-04eclipse-adt-crashes-
at-button-ok-from-project-properties/530468 fixed it for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
it's still happened on rhel/centos-7.0 with:
- eclipse-swt-4.4.0
- glib2-2.36.3
is there any solution to this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
same problem for an old Eclipse 3.6.2. the workaround worked for me:
http://askubuntu.com/a/530468
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
I'm still getting segmentation faults out of libglib-2.0 with Java
1.8.0_25-b17, Ubuntu 14.10, and Eclipse. However, after upgrading to
Java 8, the seg faults I'm seeing have moved to from g_str_hash() to
g_type_check_instance_is_a()
#
# A fatal error has been detected by the Java Runtime
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
Hi,
I simply don't understand why nobody fixes this bug.
This was already discussed a thousand times.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736
The problem occurs in any eclipse versions I tried (beginning with
eclipse-3.8 from Ubuntu repo).
workarounds are either:
export
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in gtk+2.0
Hi Simeone,
Your problem with Modelio and removing non-existent sources:
(Modelio 3:10699): GLib-CRITICAL **: Source ID 20104 was not found when
attempting to remove it
is connected with some changes in GLib library. GLib 2.40.0 introduced
the following change:
[..] g_source_remove() will now
Created attachment 247831
Additional crash log
Eclipse 4.3.2 crashes *constantly* (several times per day) with this
problem on Ubuntu 14.04. The UI goes grey and unresponsive, and after
force-quitting the application I get an error log with a stack trace
about a seg fault in native code invoked
This bug in GTK causes Eclipse to crash *constantly* (several times per
day) on Ubuntu 14.04. I've attached an error log that gets left behind
after the crash. The incriminating frame is:
C [libglib-2.0.so.0+0x38fe0] g_str_hash+0x0
I really hope this gets fixed! Stability bugs are the worst.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in “gtk+2.0”
Don't know if it is strongly related, but I think so.
I'm using Modelio 3.1 on Ubuntu 64 bit. Sometimes, apparently without a
specific sequence pattern, Modelio closes; other times, it doesn't allow to
make any type of operations (i.e. when I right click on an element, it doesn't
show
Concerning switching the oxygen theme please consider
https://bugs.launchpad.net/ubuntu/+source/java-
common/+bug/1205452/comments/20.
IMHO there are multiple reasons at the moment causing java applications
to SIGSEGV the reported way. This link shows AFAIS one of them.
--
You received this bug
(In reply to Kamil Khamitov from comment #31)
Created attachment 246108 [details]
full log
Hello, with Eclipse 4.2.2 with ADT get this bug.
Core dump https://yadi.sk/d/UTGqkxJmZz6e7
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at
I'm also seeing instability with SIGSEVs in the native code when running
eclipse.
I tried the SWT_GTK3=0 workaround, but got the following crash:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f5f9d789d6c, pid=7849, tid=140048942749440
#
#
Same problem here with IBM Sametime using the embedded IBM JRE and
Eclipse Expeditor. So if it's an Eclipse bug, it's one you'll find in
commercial closed-source products.
Workaround of setting
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc works.
--
You received this bug notification
So, after few tries in Virtual Machines to test different Debian/gtk
versions, and other researches on the net, I found a workaround to make
Luna work on my Debian laptop :
export SWT_GTK3=0
That aims to fallback to the GTK2 SWT implementation and bring my
Eclipse back!
I was not on the right
60 matches
Mail list logo
