** Changed in: eclipse
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade
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
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade
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
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
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.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
This also occurs here, with Ubuntu 14.04 x64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about
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
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade
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
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
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 pid
The problem is
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To
** Changed in: unity (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage
** No longer affects: unity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this bug go to:
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
@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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
When I opened the ticket, I also mentioned a workaround (set env. var.
UBUNTU_MENUPROXY to blank) before starting a java application. This
solves the problem for me for smartgit and eclipse.
This is clearly an indication of a problem with Unity menus.
--
You received this bug notification
** Project changed: java-common = eclipse
** Package changed: java-common (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after
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
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 d...@ptmx.org wrote:
Just so that this doesn't get overlooked: I have this problem with
Apache
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to
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
@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
Rolling back to the version of Unity from Raring updates
(7.0.0daily13.06.19~13.04-0ubuntu1) I cannot replicate this issue,
whereas with 7.1.2+13.10.20131014.1-0ubuntu1 I am able to produce a
crash. If someone could verify/disprove a connection between Unity and
this issue that would be very
Has anyone managed to track the package which is the source of this bug?
Here's my understanding so far:
It's not an Eclipse bug as the same version of Eclipse running on Ubuntu
13.04 does not suffer the problem
It doesn't appear to stem directly from oxygen-gtk as the QtCurve theme
suffers
We've been concentrating on gtk, which is a component. I'd like to
suggest taking a fresh look at Unity's global menu component. There
we're changes made to the global menu in 13.10, which may account for
this not showing up in 13.04. I'm going to mess around with that side of
things and see if I
That's a different bug. I can confirm that does fix several issues with
oxygen-gtk but not the g_object_get_qdata crash.
See https://bugs.kde.org/show_bug.cgi?id=329814 for the
g_object_get_qdata crash.
** Bug watch added: KDE Bug Tracking System #329814
Bug report in KDE: https://bugs.kde.org/show_bug.cgi?id=324438
** Bug watch added: KDE Bug Tracking System #324438
https://bugs.kde.org/show_bug.cgi?id=324438
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can reproduce it when using the Archi application. The Archi application is an
Enterprise Architecture modeling tool according the Archimate language.
Choosing the oxygen-gtk2 theme it crashes as soon as you do anything in the UI,
like:
- closing a tab
- dragging a object on the convas
- ...
** Package changed: gtk+2.0 (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about
Gtk+ 2.0 is definitely a component of this issue.
** Package changed: ubuntu = gtk+2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade
For KDE users:
Follow this: System Settings - Application View - GTK - GTK 2 Theme
Raleigh instead of oxygen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0
On Kubuntu 13.10 (64bit), the problem is easy to reproduce when using
Eclipse from the latest Android bundle and a JDK 1.7 (tested with
jdk1.7.0_25-x64).
Switching GTK2 theme from oxygen-gtk to Raleigh is working in my
configuration (glogal change or GTK2_RC_FILES variable).
On my box, the crash
https://bugs.launchpad.net/bugs/1234253 is a similar issue, but none of
the workarounds provided here work. The only workaround that does work
in that case is to lower the CPU affinity to 1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: gtk+2.0 (Suse)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
you can setup that directly for adt/eclipse, without changing the style
globally on KDE:
launch :
$ GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
/opt/adt-bundle-linux-x86_64-20130917/eclipse/eclipse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Can you confirm/nonconfirm that this issue is resolved if a desktop
environment other than Unity is used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0
At present, I could only speak for kubuntu/kde. The problem is gone when
using 'Radiance' as 'GTK2 Theme'. However, if I understand the KDE guys
right, this simply means that libglib is NOT used. Per consequence the
error cannot occur...
--
You received this bug notification because you are a
I believe that to be correct. If I get a bit of spare time today, i'll
mess around with different desktop environments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in
As I already mentioned on #1245468 I could not verify that changing
GTK_MODULES, UBUNTU_MENUPROXY, or GTK_IM_MODULE helps in any way.
However, I could verify that the problem GOES AWAYS IN KUBUNTU/KDE when
doing:
System Settings - Application Themes - GTK - Choose GTK2 Theme
Choose 'Radiance'
When changing UBUNTU_MENUPROXY this bug disappear to me. At least in
SmartSVN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to
Dear sirjoseca,
well I guess it is solved for SmartSVN. But I want to use eclipse...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04
Well, indeed i have to use UBUNTU_MENUPROXY= XXX in both, eclipse and
SmartSVN to get them working properly (SmartSVN closes unexpectedly, and
eclipse doesn't show menus any other way), and I have checked that in
both cases disabling ubuntu global menu solve this issue, at least in my
computer.
Dear sirjoseca,
I rechecked this carefully. For me (as a Kubuntu/KDE user) using
export UBUNTU_MENUPROXY=''
and afterwards starting eclipse makes things A LOT better but the
problem does NOT go away. I've still got spurious Java VM crashes, most
commonly with SWT 'cancel' buttons. But I have to
Removing the two environment variables Smart Svn don't crash anymore.
GTK_IM_MODULE=ibus
GTK_MODULES=overlay-scrollbar:unity-gtk-module
For me that solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's sufficient remove only the variable
GTK_MODULES=overlay-scrollbar:unity-gtk-module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from
** Also affects: gtk+2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to
** Changed in: gtk+2.0 (Ubuntu)
Status: New = Triaged
** Changed in: gtk+2.0 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash
** Attachment added: Jubula crash error log
https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1241101/+attachment/3900624/+files/hs_err_pid23823.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
True, as the twitter says changing the .desktop file exec line to:
Exec=env UBUNTU_MENUPROXY=0 [yoursmartgitbinpath]/smartgithg.sh %u
Works, and runs with menues not integrated into unity panel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
FWIW, eclipse started crashing after upgrade to 13.10, always # Problematic
frame: # C [libgobject-2.0.so.0+0x16bfe]
Upon reading #29 I changed GTK2 appearance a couple of times from oxygen-gtk
to ambiance etc. For me this seems to touch the problem. Oxygen crashes, others
do not.
Quinn, i've got the same scenario and changing GTK2 appearance did solve
the issue. I had 2 machines affected and both solved changing the GTK2
opt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I change GTK apperance using gtk-theme-switch2 command, I can see the
change on the othere applications (es. firefox) but smart svn crash with
the same error.
Stack: [0x7f275beb7000,0x7f275bfb8000], sp=0x7f275bfb3be8, free
space=1010k
Native frames: (J=compiled Java code,
in my case that's the stack
Stack: [0x7fa5c172b000,0x7fa5c182c000], sp=0x7fa5c18281f0, free
space=1012k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18
[error occurred during error reporting
** Attachment added: libgobject-2.0error.rtf
https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1241101/+attachment/3891219/+files/libgobject-2.0error.rtf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Posted here on behalf of Julien Aubin.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this
I have the same problem with Smartsvn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications about this
Strangely, something that has worked for people in a few other
situations has been to change GTK2 appearance to anything other than
oxygen-gtk. If someone wouldn't mind checking that out, I'd be
interested to see if that workaround works here, or if there are
multiple issues at hand here.
--
You
I've taken a look at this, and seemingly randomly*, java frames flipflop
between what we've seen here, and the
j org.eclipse.swt.internal.gtk.OS._g_object_get_qdata(JI)J+0
j org.eclipse.swt.internal.gtk.OS.g_object_get_qdata(JI)J+9
j
Also see bug #1208019
Not a crash per say, but some coordinated effort to fix global menus
that were working fine in 13.04. but must now be worked around setting
UBUNTU_MENUPROXY would be prudent.
Best regards,
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: java-common (Ubuntu)
Importance: Undecided = High
** Changed in: java-common (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Launchpad has imported 18 comments from the remote bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419729.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: java-common via
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419729
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Tracking this issue in eclipse-bugs.
Quinn Balazs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To manage notifications
I have the same bug using SmartSVN (same vendor, historically at least),
and their support narrowed it down to a problem with Native crash in
org.eclipse.swt.internal.gtk.OS._gtk_widget_show, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=419729
Dear: Java devs, please read thread above,
I found a workaround : if I start smartgit like this, it won't crash :
UBUNTU_MENUPROXY= ./smartgit.sh
So the issue seem related to appmenu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
There should be a file containing the full context of the OpenJDK issue.
All you added here is what the problematic frame, which is helpful in
context, but not particularly on its own. See if you can't upload the
error log, and once you have, set this back to new and someone will take
a look.
** Changed in: java-common (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: java-common (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241101
Title:
96 matches
Mail list logo
