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 UBUNTU
(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 de
(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 u
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() r
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.
-
You can also reproduce this in Eclipse by clicking Run... > Breakpoint
Types
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in l
** 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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Titl
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
f
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
Created attachment 254676
crash log
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
Created attachment 253846
Short SWT snippet that reproduces the problem
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libgli
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-package
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
(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 /thepathToEclipse
(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 /usr/share/ap
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
(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 /thepathToEclipse
(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
> > Project>Build Working Set Eclipse crashes
(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 ma
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
(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
> Project>Build Working Set Eclipse crashes with the following
Have you tried UBUNTU_MENUPROXY=0 ?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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
Project>Build Working Set Eclipse crashes with the following
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
*** Bug 466326 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 aft
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 rece
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 DX
Packages, which is subscribed to unity in U
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 mod
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Ti
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 Environm
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 SWT_GT
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
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
S
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 fr
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.
*
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 anything).
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 pc
Created attachment 246108
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 pc=0x7fe3b0b716b8, pid=6629, tid=140615974131456
#
# JRE version: Java(TM)
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
#
# JRE
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 bec
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 bu
** Bug watch added: Eclipse bugs #430736
https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Titl
Can confirm the issue with:
- Kubuntu 14.04 amd64
- Eclipse 3.8.1
- java -version = java version "1.7.0_55" OpenJDK Runtime Environment (IcedTea
2.4.7, (7u55-2.4.7-1ubuntu1), OpenJDK 64-Bit Server VM (build 24.51-b03, mixed
mode)
Tried the following workarounds, all did not help
- Opening the se
Tried the following workarounds on Kubuntu 14.04 amd64 with Eclipse from
package management, all did not help
- Opening the search menu (CTRL+F) and closing it with ESC only takes 2-3
attempts to crash Eclipse:
- Setting affinity (taskset -c 1 eclipse)
- Setting theme to Raleigh in systemsetting
Can confirm the issue with Kubuntu 14.04 amd64, Eclipse crashes when
closing the search window:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7f487db99718, pid=13246, tid=139949693536000
#
# JRE version: OpenJDK Runtime Environment (7.0_55-b14)
NetBeans 8 also crashes the first time you launch it and works ok the
second time. Problem is in
C [libgobject-2.0.so.0+0x125be0] _fini+0xecb18
** Attachment added: "JDK 8 crash report."
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/+attachment/4131045/+files/hs_err_pid2825.l
Created attachment 244042
crash log
(In reply to David Matějček from comment #22)
> Problematic frames occurs in two variants:
> 1) # C [libgobject-2.0.so.0+0x31b3c] g_type_check_instance_is_a+0x3c
> 2) # C [libgtk-x11-2.0.so.0+0x24492a] gtk_widget_queue_draw+0x1a
>
I've a third variant in t
Dear kecsap,
well, the only problem is that this bug was never limited to eclipse
from ubuntu repos. It has also stroked me with an eclipse from
eclipse.org...
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscrip
Guys, I am on 13.10 and nothing fixed this issue except downloading
Eclipse Kepler from eclipse.org instead of the non-working Eclipse in
the Ubuntu repos
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions:
I've been using the Raleigh override, and I have experienced no crashes.
I also tried David's suggestions, though the libgtk-3-0 version in the
Trusty repos seems to be the same as the one in the gnome3 ppa (Package
libgtk3 is already the newest version etc.). I compiled oxygen-gtk
locally, but th
This also occurs here, with Ubuntu 14.04 x64.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 1
same issue here with ubuntu 13.10 x64
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to
I did have to upgrade oxygen as specified by David, too, as even with
the Raleigh theme I was getting failures (much less frequent or
reproducible than before upgrading libgtk, though). After upgrading
oxygen, I didn't experience any further failures.
Of course, now I'm in the process of upgradin
Fingers crossed, David! Simply installing libgtk-3-0 worked for the
trivial case I described above, where I could always make it fail (I
haven't upgraded oxygen, yet, and probably won't if this works without
it—I'm still using the override
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc).
It seems it is fixed in newer GTK, but after my recent experiences I am
not so optimistic. But after upgrade to 1.3.5 and also GTK 3.10 and
restarting the system Eclipse still did not crash (10 hours yesterday, 5
hours today, switching git branches on massive project, debugging,
refactoring).
Can
EDIT: workaround does not help. And one more note: Eclipse crashes
earlier when showing variables in debug mode.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bu
Yes, today Eclipse crashes again, taskset does not help. :(
This is really very bad, hardly reproducible bug. It seems the faster machine
and newer JDK and Linux, the more occurences I have ...
Maybe the fastest method to fix it is to dig into the code of GTK ...?
--
You received this bug notifi
I've also tested this using Juno (the version included in Zend Studio
10) and unfortunately share auspex's experience, it doesn't solve the
issue for me.
I also tried explicitly launching the application with an affinity:
taskset 0x0001 zend-studio
with the same reslult.
--
You received th
I'll add that my test was not using Kepler, but David's suggesting
Kepler doesn't change things.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Titl
Nice idea, David but no luck for me.
I start Eclipse with:
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and do Ctrl-F, and click on Find, Find, Close. Eclipse aborts at
g_object_get_qdata+0x18
I restart Eclipse, find the PID
Workaround:
1) Start the Eclipse
2) find pid of the process
3) taskset -p 0x0001
The problem is something like with volatile and synchronized; with this I used
two Eclipse instances for 12 hours without a crash!
After restart I forgot to set it again and Eclipse crashed after 5 minutes ...
I use Eclipse Kepler 4.3.2 and this bug occurs more often then ever before!
Eclipse also is not the only application crashing with this bug - today I have
seen bugreport also for Gimp.
Workaround:
1) Start the Eclipse
2) find pid of the process
3) taskset -p 0x0001
The problem is something
The problem is fixed with the latest trusty build (at least the menus
behavior) in Kepler 4.3.2 : it was present in previous versions of
Kepler.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packag
It's probably worth mentioning that with the latest Eclipse (Kepler)
this bug does not occur. Perhaps looking at the differences between
what happens on "close" in the find dialog in Kepler and Juno will shed
some light on what is causing the crash.
--
You received this bug notification because
Reproduced also with the JDK6, OpenJDK7, and finally JDK8:
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
Problematic frames occurs in two variants:
1) # C [libgobject-2.0.so.0+0x31b3c] g_type_check_instance_is_a+0x3c
2) # C [li
I have an idea, theoretical scenario: isn't it somehow similar problem as with
the volatile and synchronization in Java?
GTK makes many updates and redrawing at the same time.
Even Eclipse have parallel threads for redrawing.
I got 2core/4thread CPU Intel i5.
What if the GTK tries to redraw somet
Reproduced also with the JDK6, OpenJDK7, and finally JDK8:
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)
Problematic frames occurs in two variants:
1) # C [libgobject-2.0.so.0+0x31b3c] g_type_check_instance_is_a+0x3c
2) # C [li
** No longer affects: unity
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Sta
** Changed in: unity (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 af
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0
This may also be relevant: It doesn't seem to be an Ubuntu/Debian based
distro specific bug. I also have an Arch Linux installation and it
happens on that as well.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subsc
Unfortunately running Eclipse via sudo does not fix the issue for me and
I get the exact same crash:
Stack: [0x7f252c76,0x7f252c861000], sp=0x7f252c85d040, free
space=1012k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libgobject-2.0.so.0+0x
I have my own RCP application, built with Eclipse Helios, for multiple
platforms. The problem happens for me when I test the application build
for Linux x86-gtk. Platform: Kubuntu 13.10 (virtualbox machine), JRE:
1.6u45. I get the crash while I use the preference pages and hit the OK
button. No .lo
Same issue in Ubuntu 14.04 (Unity).
Tested with eclipse 3.8.2 and 4.3.1 with oracle-java7 and openjdk-7.
After install and first time start, eclipse freeze and crash, second start
works fine, but when download a project from git, or download a maven project
or starting tomcat, eclipse crash.
--
@daff Why would you assume a different bug? I have tried it with both forms
UBUNTU_MENUPROXY='' GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and setting the theme in System Settings, and I _can_ use Eclipse for a while,
but s
Just wanted to comment that this bug is also present in the KDE
environment, but not Gnome, on a 64-bit Fedora 20 system. I encountered
it when using an SDK leveraged from Eclipse. The SDK crashes frequently
when I click the "OK" button on a window. The problematic frame is:
C [libgobject-2.0.
Just a quick note : I ran a test on Trusty (30-jan build) and the bug
is still present.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Jav
As Mr. Adam says above, i use the same environment, and the same error
occurs at certain operations when i use the oxygen-gtk theme.
The workaround with the
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc works for me also,
but looks not very good :(
--
You received this bug notification b
Using GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc worked also
for me using Kubuntu 13.10 64bit with oxygen-gtk theme.
It's an annoying bug because evertying seems to work and at certain
operations the application (based on Eclipse) crashes.
--
You received this bug notification because
@auspex: the GTK2_RC_FILES workaround should work for this bug, how are
you calling it? Should look like this:
$ GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
/path/to/eclipse/or/whatever
Alternatively you can set the GTK2 theme to Raleigh globally and try
starting your crashing applicati
I'm not sure this is helpful or not but:
I don't have Unity installed. I'm running Linux Mint which is built from
Ubuntu and I'm running KDE. Whether that rules out a unity bug or not I
don't know.
Setting UBUNTU_MENUPROXY has no effect at all.
Using GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2
The GTK2_RC_FILES theme workaround doesn't help me, nor does
UBUNTU_MENUPROXY.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash i
Totally agree with Andreas.
I've got the same persistent issue using KDE and oxygen theme.
Gotta be some shared library
Alessio Nobile
mail sent from Android
On 28 Jan 2014 16:31, "Andreas Ntaflos" wrote:
> Just so that this doesn't get overlooked: I have this problem with
> Apache Directory Stu
Just so that this doesn't get overlooked: I have this problem with
Apache Directory Studio (an Eclipse RCP application) running on Kubuntu
13.10 using KDE 4.12 and the oxygen-gtk engine. It is definitely not
related to Unity directly, though I don't know how many libraries or how
much code oxygen-g
** Project changed: java-common => eclipse
** Package changed: java-common (Ubuntu) => unity (Ubuntu)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
You have been subscribed to a public bug:
Running smartgit 4.6.4 on 13.10 64 bits. After registering the product,
smartgit crash when trying to open a new repository. Java error log :
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x7fa59061f9c0, p
98 matches
Mail list logo
