Bug 334025 - Oxygen-gtk2 makes scilab 5.5.0 crash at startup on linux 64 bit
Summary: Oxygen-gtk2 makes scilab 5.5.0 crash at startup on linux 64 bit
Status: RESOLVED WORKSFORME
Alias: None
Product: Oxygen
Classification: Plasma
Component: gtk2-engine (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-28 15:05 UTC by Sergio
Modified: 2018-11-30 03:59 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Crash log (38.51 KB, text/plain)
2014-04-28 19:09 UTC, Ruslan Kabatsayev
Details
Backtrace from gdb (5.41 KB, text/plain)
2014-04-28 19:36 UTC, Ruslan Kabatsayev
Details
Output of scilab crashing (27.34 KB, text/plain)
2014-04-29 09:27 UTC, Sergio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio 2014-04-28 15:05:40 UTC
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
Comment 1 Hugo Pereira Da Costa 2014-04-28 15:14:02 UTC
Please do attach a crash report
Will have a look at it before installing anything on my machine, sorry.
Comment 2 Hugo Pereira Da Costa 2014-04-28 15:19:06 UTC
changed to gtk3 engine, as reported by Ruslan in upstream bug, it seems
Comment 3 Hugo Pereira Da Costa 2014-04-28 15:36:36 UTC
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)
Comment 4 Hugo Pereira Da Costa 2014-04-28 15:37:42 UTC
(ps:
I am using 64 bit linux
versions are:
oxygen-gtk: v1.4.5
gtk: 2.24.22
glib: 2.38.2
Comment 5 Sergio 2014-04-28 15:40:10 UTC
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.
Comment 6 Ruslan Kabatsayev 2014-04-28 19:09:42 UTC
Created attachment 86317 [details]
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.
Comment 7 Ruslan Kabatsayev 2014-04-28 19:16:03 UTC
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).
Comment 8 Hugo Pereira Da Costa 2014-04-28 19:19:36 UTC
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.
Comment 9 Ruslan Kabatsayev 2014-04-28 19:36:30 UTC
Created attachment 86318 [details]
Backtrace from gdb

Here's somewhat more verbose backtrace, taken from gdb.
Comment 10 Sergio 2014-04-29 09:27:11 UTC
Created attachment 86337 [details]
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.
Comment 11 Andrew Crouthamel 2018-10-31 03:52:20 UTC
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!
Comment 12 Bug Janitor Service 2018-11-15 10:46:28 UTC
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!
Comment 13 Bug Janitor Service 2018-11-30 03:59:36 UTC
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!