Bug 1382576

Summary: gnuplot qt term crashes on "Export as PDF"
Product: [Fedora] Fedora Reporter: Dmitri A. Sergatskov <dasergatskov>
Component: qt5Assignee: Helio Chissini de Castro <helio>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: dasergatskov, fkluknav, helio, orion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 11:05:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dmitri A. Sergatskov 2016-10-07 05:01:29 UTC
Description of problem:
When I try to save a (Qt-terminal) plot using gui menu "Export to PDF"
(or "Export to SVG") plot windows crashes.

Version-Release number of selected component (if applicable):
4.0.3-3
Qt5-5.7.0

How reproducible:
100%

Steps to Reproduce:
1.run gnuplot
2. set term qt 
3. plot sin(x)
4. On plot windows gui select "File" --> "Save as PDF"

Actual results:
crash

Expected results:
pop-up a file-select dialogue window

Additional info:

If I recompile srs.rpm against Qt-4.8.7 the problem goes away.

Comment 1 Dmitri A. Sergatskov 2016-10-07 05:05:22 UTC
Forgot to mention -- the crash only occurs on Gnome/Wayland desktop.
Works as expected on (e.g.) Plasma.

Dmitri.
--

Comment 2 Frantisek Kluknavsky 2016-10-07 22:40:14 UTC
It does not seem like a gnuplot problem, but I will look a bit more before reassigning component.

Comment 3 Frantisek Kluknavsky 2016-10-10 14:38:23 UTC
Works for me in a virtual machine with freshly installed Fedora 25 alpha. Tried straight after installation from iso and then after `dnf update` and reboot. Both work. Are you sure your system is not messed up?

Maybe someone with knowledge of qt and/or wayland will have some insight. Reassigning to qt5.

Comment 4 Dmitri A. Sergatskov 2016-10-10 22:13:51 UTC
Well, i have two computers with FC25 installed: one is amd FX8350/Radeon6450 
and another is old-ish laptop (core duo/radeon 4650) -- both of them show
the same problem. 
I tried on two other computers (i7/intel graphics and Nehalem/nvidia) with
Fedora 24 and they do not have the problem (even on Wayland). 
So it could be an AMD graphics hardware driver issue.

I also tried to compile the most recent gnuplot (5.0.5) from the tarball
and it has the same problems as the one from Fedora distribution
(crash on F25/weiland, fine on FC24). 

I also have octave-gui (4.2.0) compiled on FC25 against Qt5 and it runs just fine
(with file selection windows popping up e.g. in its qscintilla component).

gnuplot compiled against Qt4 works fine on all computers as well.

Dmitri.

Comment 5 Dmitri A. Sergatskov 2016-10-11 12:10:12 UTC
I also try to run gnuplot on FC25 (that crashes on local amd machine) through ssh 
from FC24 machine (i.e. display is on FC24). And it works as expected, no crash.

Dmitri.

Comment 6 Dmitri A. Sergatskov 2016-10-11 12:28:37 UTC
Going backwards, i.e. running self-compiled gnuplot 5.0.5

ldd /usr/local/bin/gnuplot | grep Qt
	libQt5Network.so.5 => /lib64/libQt5Network.so.5 (0x00007f6e4df1f000)
	libQt5Svg.so.5 => /lib64/libQt5Svg.so.5 (0x00007f6e4dec7000)
	libQt5PrintSupport.so.5 => /lib64/libQt5PrintSupport.so.5 (0x00007f6e4de53000)
	libQt5Widgets.so.5 => /lib64/libQt5Widgets.so.5 (0x00007f6e4d7ca000)
	libQt5Gui.so.5 => /lib64/libQt5Gui.so.5 (0x00007f6e4d2d3000)
	libQt5Core.so.5 => /lib64/libQt5Core.so.5 (0x00007f6e4ce4f000)

and displaying on amd/FC25 works fine, no crash.

(on un-related note, remote evince from FC25 --> display on FC24 does not
work (I was trying to look at the file I saved from gnuplot):

evince t1.pdf 
xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Control, ignoring Lock

(evince:5075): Gtk-WARNING **: Allocating size to EvSidebar 0x55c29c24c6c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

)

Dmitri.

Comment 7 Dmitri A. Sergatskov 2016-12-13 17:07:30 UTC
Here is some update
I still see the crash on multiple computers that were *updated* to FC25.

I do not see this bug on which I *reinstalled* the OS (preserving /home
directory). 

At this moment I really tempted to reinstall OS on all affected 
computers.

Dmitri.

Comment 8 Fedora End Of Life 2017-11-16 19:00:44 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2017-12-12 11:05:43 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.