Bug 377038 - Spectacle crashes when the option "Rectangular Region" is selected.
Summary: Spectacle crashes when the option "Rectangular Region" is selected.
Status: RESOLVED WORKSFORME
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
: 378204 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-02-28 23:12 UTC by Dylan Socolobsky
Modified: 2018-04-12 09:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dylan Socolobsky 2017-02-28 23:12:31 UTC
Hello.

Spectacle crashes for me when the option "Rectangular Region" under "Area" is selected; once you click "Take a New Screenshot" the window will close and no screenshot is taken.

If you uncheck the option "On Click" then you'll see the '+' marker that lets you select the desired rectangular area, however once you click nothing happens and Spectacle crashes with the same error.

Reproducible: Every time apparently.

Steps to Reproduce:
1. Open Spectacle.
2. Select "Rectangular Region" under "Area".
3. Press "Take a New Screenshot".

Actual Results: The program crashes and no screenshot is taken.

Expected Results: A screenshot of the desired area should be taken.

Package Version: 16.12.2-1

Error message:
/* This can be seen at the start of the program */
QGLXContext: Failed to create dummy context
qrc:/JobDialog.qml:67: TypeError: Cannot read property 'Layout' of null
qrc:/JobDialog.qml:66: TypeError: Cannot read property 'Layout' of null
/* This is the actual error message once you click "Take a New Screenshot */
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile)) 
Aborted (core dumped) 

I'm using the propietary NVidia drivers under Arch Linux in case it's relevant.
Comment 1 Nate Graham 2017-10-18 17:20:27 UTC
*** Bug 378204 has been marked as a duplicate of this bug. ***
Comment 2 null 2018-01-31 14:29:02 UTC
Cannot reproduce with Spectacle 17.12.1 and Qt 5.10.1. Please retest with a recent version and possibly switch to a non-proprietary driver, so we can narrow down the issue.
Comment 3 Nate Graham 2018-02-10 15:04:55 UTC
If you can add the requested information, please do so.
Comment 4 Christoph Feck 2018-02-28 23:16:51 UTC
To further investigate this issue, KDE developers need the information requested in comment #2. If you can provide it, or need help with finding that information, please add a comment.
Comment 5 Christoph Feck 2018-03-21 23:38:57 UTC
No response, changing status. If you have new information, please add a comment.
Comment 6 Ole Christensen 2018-04-12 09:16:19 UTC
Same behavior here on Gentoo. It used to work until I upgraded from 17.08.3 to 17.12.3. Qt version is 5.9.4.

Error message is:
QGLXContext: Failed to create dummy context
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile  QSurfaceFormat::OpenGLContextProfile(NoProfile)) 
Aborted

The X driver is the proprietary nVidia driver as well.
Comment 7 null 2018-04-12 09:26:12 UTC
Thanks for commenting. It's difficult for me to reproduce, because I cannot run this proprietary driver. Nevertheless, we can try do debug this further with your help:

1. Provide a backtrace (see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB)

2. Bisect which commit caused the issue, in particular if your assumption that this was introduced between 17.08.3 and 17.12.3 holds. Let us know if you need help compiling from the upstream Git repo and using "git bisect".

3. Determine if the problem is somewhere else in the stack, e.g. in Qt or with NVidia.
Comment 8 Ole Christensen 2018-04-12 09:34:30 UTC
Hmm, just tried to reproduce the issue again. Works...

The only thing I just changed some minutes ago is the nVidia driver. I upgraded from 390.48 to 396.18.

Sorry for the noise. Highly probable the nVidia stuff is the causer.

Maybe Dylan could also give the latest driver a try.