oxygen-gtk2 makes scilab crash

[Sergio Callegari]

On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gtk2-engines-oxygen 1.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Apr 17 19:38:52 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2009-11-12 (1617 days ago)
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MarkForUpload: True
SourcePackage: gtk2-engines-oxygen
UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago)

[Serge Steer (serge-steer-scilab)]

Created attachment 3854
trac

BUG DESCRIPTION:
----------------
The official 64 bits binary version of Scilab-5.5.0 fails to start on my laptop running SuSe12.3 (crash in glibc see the attched file)

ERROR LOG:
----------

HOW TO REPRODUCE THE BUG:
-------------------------

OTHER INFORMATION:
------------------
my glibc version is 2.17-4.7.1-x86_64

[Serge Steer (serge-steer-scilab)]

If I compile the source version, Scilab starts without any message.

[Clement-david-h (clement-david-h)]

It seems to be related to the JVM version embedded into scilab binaries. Can you try to copy you system JVM into /home/steer/scilab-5.5.0/thirdparty/java ?

[Serge Steer (serge-steer-scilab)]

I have replaced the lib and bin directories of thirdpaty/java by those located in my system; without any change.

[Sergio Callegari (callegar)]

Same happens on ubuntu 13.10 64bit. This was already reported through the scilab 5.5.0 beta.

[Sergio Callegari (callegar)]

I see two different origins for the crash.

1) Using oxygen-gtk as the gtk style (this is likely to happen when working with kde). This happens at the very startup of the application. Using another style for gtk2 apps should let scilab start.

2) Due to llvm. This happens when exiting the app and seems due to bad interaction with libLLVM-3.3.so.1

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

[Sergio Callegari (callegar)]

As a matter of fact, it may be the case that the specific version of the library shipped by (k)ubuntu is the issue. Ubuntu is lagging behind upstream on this.

[Sergio Callegari (callegar)]

As a side question:

For future bugs I may find in ubuntu, how should I behave? If the bugs look like issues with upstream source (i.e., not due to packaging) should I report them upstream only?

[Harald Sitter (apachelogger)]

That's the way to get them fixed anyway ;)

If there's an upstream fix available you may still choose to report a bug in launchpad though to possibly get the fix backported to stable releases.

[Ruslan (b7-10110111)]

@Sergio
I actually was able to reproduce this even with Ubuntu Precise 64 bit. Please do report this to bugs.kde.org: I currently don't have much time to debug this, while Hugo (another upstream developer) might be able look into this.
When reporting, please be sure to include terminal output of scilab when it crashes.

[Ruslan (b7-10110111)]

Ah, and newer scilab seems to use not gtk2, but gtk3.

[Clement-david-h (clement-david-h)]

(In reply to Serge STEER from comment #3)
> I have replaced the lib and bin directories of thirdpaty/java by those located in my system; without any change.

Ok, I'm able to reproduce and switching the GTK2 Theme from Oxygen to Adwaita fix the Scilab startup issue. To avoid switching all GTK application theme, you can use the approach reported on http://askubuntu.com/questions/78088/can-i-apply-a-different-gtk3-theme-from-the-main-one-to-an-individual-applicatio

I do not consider this issue as "Blocker" because OpenSuse 13.1 has been released and I'm unable to reproduce using it.

[Sergio Callegari (callegar)]

The bug seems to be present in precise, saucy and trusty. I cannot test previous kubuntu versions. I'll now report to kde. There is an open bug also on scilab (bug 13330).

[Sergio Callegari (callegar)]

The issue is also present in the just released kubuntu Trusty (14.04 that is a release with long term support). Also here, moving away from gtk2-oxygen theme fixes the crash. There is a bug open in ubuntu's launchpad, but is declared invalid as it should be fixed upstream by the kde developers.

[Sergio Callegari (callegar)]

On kubuntu precise, raring, saucy, trusty 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine.

The bug happens with all the oxygen-gtk2 versions used from ubuntu precise to trusty (1.4.5).

There is a bug open in ubuntu at https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1309132

Ubuntu's developer (Harald Sitter) recommended reporting upstream, to the attention of Hugo.

There is also a bug open at scilab http://bugzilla.scilab.org/show_bug.cgi?id=13330.

If needed I can attach the crash log, but probably the best is to setup scilab from www.scilab.org to see what happens, since the bug is 100% reproducible and evident not just in ubuntu, but also in other distros including suse.

Reproducible: Always

[Hugo Pereira Da Costa (hugo-pereira)]

Please do attach a crash report
Will have a look at it before installing anything on my machine, sorry.

[Hugo Pereira Da Costa (hugo-pereira)]

changed to gtk3 engine, as reported by Ruslan in upstream bug, it seems

[Hugo Pereira Da Costa (hugo-pereira)]

So ...
can't reproduce here. See:
http://wstaw.org/m/2014/04/28/plasma-desktopSF1843.png

though it seems the application is usign gtk2, not gtk3 here.

I'll need versions of
- oxygen-gtk2
- scylab (here is 5.5.0-0.beta1)
- gtk
- glib

and a crash report, please.
(no offense meant, but I'm getting tired of (k)ubuntu crash reports that I cannot reproduce)

[Hugo Pereira Da Costa (hugo-pereira)]

(ps:
I am using 64 bit linux
versions are:
oxygen-gtk: v1.4.5
gtk: 2.24.22
glib: 2.38.2

[Sergio Callegari (callegar)]

Sorry for the lack of the crash report, it is just that I am not on the right laptop to produce it now.
I'll provide the crash report as soon as I am on the right machine (in a few hours, hopefully).
In the meantime, I confirm that bug is with oxygen-gtk2, not oxygen-gtk3.

[Ruslan (b7-10110111)]

Created attachment 86317
Crash log

Indeed, it uses GTK2. I must have confused it with another app I tested. Here's the log printed at the moment of crash.
@Hugo if you need some more info, please ask. I can't find much time to do actual debugging these days.

[Ruslan (b7-10110111)]

In fact, although the bug reproduces in current version, this crash log was generated with oxygen-gtk2 1.4.3-xxx (current version gives the same output).

[Hugo Pereira Da Costa (hugo-pereira)]

ok. Crash seems to occur in our Qt configuration reading ... pretty low level. Why would it crash for this application only and not all.
I'll investigate in more details as soon as I'm on the right machine.

[Ruslan (b7-10110111)]

Created attachment 86318
Backtrace from gdb

Here's somewhat more verbose backtrace, taken from gdb.

[Sergio Callegari (callegar)]

Created attachment 86337
Output of scilab crashing

Here is the output of scilab crashing. I guess I am late and others have submitted much more useful logs by now, though.

[Clement-david-h (clement-david-h)]

*** Bug 13393 has been marked as a duplicate of this bug. ***

[Clement-david-h (clement-david-h)]

(In reply to Sergio Callegari from comment #7)
> The issue is also present in the just released kubuntu Trusty (14.04 that is a release with long term support). Also here, moving away from
> gtk2-oxygen theme fixes the crash. There is a bug open in ubuntu's launchpad, but is declared invalid as it should be fixed upstream by the kde
> developers.

Agreed with ubuntu's developers, this is a kde bug with a workaround. Not related to Scilab code at all.

[Sergio Callegari (callegar)]

Could be useful to list the issue and the workaround somewhere with the scilab release notes, though, to prevent this bug from being reopened multiple times and to help users who may encounter this issue

[Clement-david-h (clement-david-h)]

(In reply to Sergio Callegari from comment #10)
> Could be useful to list the issue and the workaround somewhere with the scilab release notes, though, to prevent this bug from being reopened
> multiple times and to help users who may encounter this issue

release notes added at https://codereview.scilab.org/14640

[Vincent-couvert-q (vincent-couvert-q)]

Merged @ http://gitweb.scilab.org/?p=scilab.git;a=commit;h=4ac93f63feae9d2f164f91c0907df5990f37a255

[Andrew-crouthamel (andrew-crouthamel)]

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

[Bug-janitor (bug-janitor)]

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

[Bug-janitor (bug-janitor)]

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!