When launching TOS under mageia 4 (Kde Desktop) with $ ./TOS_DI-linux-gtk-x86.sh We have the splash screen and the list of projects. When launching a project the result is a SIGSEV with that error message : Gtk-Message: Failed to load module "canberra-gtk-module" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ffaccab7528, pid=20601, tid=140715369928448 # # JRE version: OpenJDK Runtime Environment (7.0_71-b14) (build 1.7.0_71-iurt_2014_10_24_16_05-b00) # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea 2.5.3 # Distribution: Built on Mageia 4 (Fri Oct 24 16:05:23 UTC 2014) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-20601/hs_error.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # The error seems linked to Oxygen theme :-/ Tested on an up to date mageia4 x86_64 with TOS_DI-20141024_1545-V5.6.0 and TOS_DI-r104014-V5.3.1 (Download here : http://www.talend.com/download/data-integration )
Source RPM: (none) => oxygen-gtk-1.4.2-0.rc1.1.1.mga4
Source RPM: oxygen-gtk-1.4.2-0.rc1.1.1.mga4 => oxygen-gtk-1.4.6-1.mga5.src.rpm
From IRC: 2014:11:28:15:58 < marja> maat: maybe I misunderstand.... Talend Open Studio isn't in our repos, so we don't support it and the report will be closed as invalid, won't it? 2014:11:28:15:58 < maat> well 2014:11:28:15:58 < maat> the rpm in cause is not talend 2014:11:28:15:58 < maat> but oxygen 2014:11:28:15:59 < maat> as Talend is a very popular opensource ETL 2014:11:28:15:59 < maat> not solving the bug will drive people away from mageia 2014:11:28:15:59 < marja> maat: Hugo Pereira Da Costa knows most about oxygen 2014:11:28:16:00 < maat> the bug looks like a newer version of this issue : http://www.talendforge.org/forum/viewtopic.php?pid=150221 2014:11:28:16:00 < [mbot> [ [resolved] Talend crash on opensuse (Page 1) / Data Integration - Installation / Talend Community Forum ] 2014:11:28:16:01 < maat> well 2014:11:28:16:01 < maat> it was not really "solved" as the guy switched to gnome :P 2014:11:28:16:02 < marja> maat: I can paste the above in the report, and CC Hugo, is that OK with you? 2014:11:28:16:02 < maat> but i think investigating this and being the first to give a real solution would be anice move 2014:11:28:16:02 < maat> yep 2014:11:28:16:02 < maat> please do :) 2014:11:28:16:02 < marja> OK
CC: (none) => hugo.pereira, marja11
I use TOS_DI with oxygen-gtk. TOS_DI uses an old elipse platform (eclipse 3.6 Helios) which often crashes with GtkComboBox::appears-as-list = 1 used by some gtk theme: QtCurve, oxygen-gtk, ... Recent eclipse doesn't crash anymore with appears-as-list = 1. Some other apps crashes with appears-as-list = 1 too. It's difficult to say if the bug is in eclipse, or gtk 2 itself. To workaround this issue, I use this script to launch TOS_DI #!/usr/bin/bash # JAVA_HOME=/usr/lib/jvm/jre GDK_NATIVE_WINDOWS=1 GTK2_RC_FILES=~/.gtkrc-2.0-combobox-menu OXYGEN_APPLICATION_NAME_OVERRIDE=eclipse /usr/local/talend-DI/TOS_DI-linux-gtk-x86_64 & and for ~/.gtkrc-2.0-combobox-menu include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" gtk-theme-name="oxygen-gtk" # some apps crashes with appears-as-list = 1 style "oxygen-default" { GtkComboBox::appears-as-list = 0 }
CC: (none) => lmenut
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD