Bug 400479 - Crash on Export via Bluetooth
Summary: Crash on Export via Bluetooth
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-10-30 12:05 UTC by Greg Lepore
Modified: 2018-10-30 21:33 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Lepore 2018-10-30 12:05:41 UTC
Application: spectacle (18.08.2 - A Dearth of Dank Memes)

Qt Version: 5.11.2
Frameworks Version: 5.51.0
Operating System: Linux 4.15.0-38-generic x86_64
Distribution: KDE neon User Edition 5.14

-- Information about the crash:
- What I was doing when the application crashed: Doing basic bug checking after user on Reddit reported crash when exporting. Found additional crashes while attempting to export screenshot via Bluetooth and other functions.

- Unusual behavior I noticed: crash with bug report

- Custom settings of the application: None

-- Backtrace:
Application: Spectacle (spectacle), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e980a7140 (LWP 29472))]

Thread 4 (Thread 0x7f5e70563700 (LWP 29481)):
#0  0x00007f5e8b349d79 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f5e8b304538 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5e921bd53b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f5e921617fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e91f8cbba in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e939f04f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007f5e91f97adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f5e8e6676db in start_thread (arg=0x7f5e70563700) at pthread_create.c:463
#8  0x00007f5e9188188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f5e80de7700 (LWP 29474)):
#0  0x00007f5e91874bf9 in __GI___poll (fds=0x7f5e74007970, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f5e8b304439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5e8b30454c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f5e921bd53b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e921617fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e91f8cbba in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f5e932a5e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007f5e91f97adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f5e8e6676db in start_thread (arg=0x7f5e80de7700) at pthread_create.c:463
#9  0x00007f5e9188188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f5e83937700 (LWP 29473)):
#0  0x00007f5e91874bf9 in __GI___poll (fds=0x7f5e83936ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007f5e947f3747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f5e947f536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f5e85d03ed9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f5e91f97adb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e8e6676db in start_thread (arg=0x7f5e83937700) at pthread_create.c:463
#6  0x00007f5e9188188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f5e980a7140 (LWP 29472)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#7  0x00007f5e917a0801 in __GI_abort () at abort.c:79
#8  0x00007f5e91f685db in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f5e968df20d in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007f5e968dfffd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x00007f5e968e0d9a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x00007f5e92701745 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f5e9695a1a5 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x00007f5e93e9ae1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f5e93ea23ef in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007f5e921634d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f5e926f676f in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x00007f5e926f73bd in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007f5e926cff5b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x00007f5e85d8f76b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#21 0x00007f5e921617fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f5e9216a9c0 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00005576dcc29b22 in ?? ()
#24 0x00007f5e91781b97 in __libc_start_main (main=0x5576dcc284f0, argc=2, argv=0x7fff35d2b378, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff35d2b368) at ../csu/libc-start.c:310
#25 0x00005576dcc29f9a in _start ()

Possible duplicates by query: bug 395743, bug 392092, bug 389875, bug 389801, bug 388864.

Reported using DrKonqi
Comment 1 Kai Uwe Broulik 2018-10-30 15:18:46 UTC
Looks like your graphics driver is broken. Are you on nvidia or did you do a recent update without restarting?
Comment 2 Greg Lepore 2018-10-30 15:23:17 UTC
Not a recent update and reboot, as the problem persists through reboots. I am on Nvidia. Probably the same problem in bug 400478, also reported by me.

sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: GP108
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nvidia latency=0
       resources: irq:26 memory:fb000000-fbffffff memory:c0000000-cfffffff memory:de000000-dfffffff ioport:ef00(size=128) memory:c0000-dffff


$(modprobe --resolve-alias nvidia)
filename:       /lib/modules/4.15.0-38-generic/kernel/drivers/char/drm/nvidia.ko
alias:          char-major-195-*
version:        410.73
supported:      external
license:        NVIDIA
srcversion:     E6823ED882C76894D74F1C2
alias:          pci:v000010DEd00000E00sv*sd*bc04sc80i00*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        ipmi_msghandler
retpoline:      Y
name:           nvidia
vermagic:       4.15.0-38-generic SMP mod_unload 
parm:           NvSwitchRegDwords:NvSwitch regkey (charp)
parm:           NVreg_Mobile:int
parm:           NVreg_ResmanDebugLevel:int
parm:           NVreg_RmLogonRC:int
parm:           NVreg_ModifyDeviceFiles:int
parm:           NVreg_DeviceFileUID:int
parm:           NVreg_DeviceFileGID:int
parm:           NVreg_DeviceFileMode:int
parm:           NVreg_UpdateMemoryTypes:int
parm:           NVreg_InitializeSystemMemoryAllocations:int
parm:           NVreg_UsePageAttributeTable:int
parm:           NVreg_MapRegistersEarly:int
parm:           NVreg_RegisterForACPIEvents:int
parm:           NVreg_CheckPCIConfigSpace:int
parm:           NVreg_EnablePCIeGen3:int
parm:           NVreg_EnableMSI:int
parm:           NVreg_TCEBypassMode:int
parm:           NVreg_UseThreadedInterrupts:int
parm:           NVreg_EnableStreamMemOPs:int
parm:           NVreg_EnableBacklightHandler:int
parm:           NVreg_EnableUserNUMAManagement:int
parm:           NVreg_MemoryPoolSize:int
parm:           NVreg_KMallocHeapMaxSize:int
parm:           NVreg_VMallocHeapMaxSize:int
parm:           NVreg_IgnoreMMIOCheck:int
parm:           NVreg_RegistryDwords:charp
parm:           NVreg_RegistryDwordsPerDevice:charp
parm:           NVreg_RmMsg:charp
parm:           NVreg_GpuBlacklist:charp
parm:           NVreg_AssignGpus:charp
Comment 3 Kai Uwe Broulik 2018-10-30 15:25:11 UTC
Driver or configuration bug, it should print something on console when it quits. Please report this to your distribution or try up/downgrading your graphics driver.
Comment 4 Greg Lepore 2018-10-30 15:27:24 UTC
Nothing prints on the console when it crashes.

I am on KDE Neon, and they appear to say to report bugs on bugs.kde.org. Is there another location to report Neon bugs?

Thanks for your help on this.
Comment 5 Christoph Feck 2018-10-30 19:17:23 UTC
The Neon bug tracker is here on bugs.kde.org, but video drivers are not maintained by the Neon team, but downstream at the Ubuntu bug tracker at https://launchpad.net/bugs

To see the error message, please create a file "test.qml" then run it with "qmlscene test.qml" in Konsole.


import QtQuick 2

Rectangle {
        width: 400
        height: 300
        color: "green"
}
Comment 6 Greg Lepore 2018-10-30 19:22:58 UTC
qmlscene produces the green square, but apart from that, nothing else. Am I supposed to interact with it in some way?
Comment 7 Christoph Feck 2018-10-30 21:33:01 UTC
No, I was just hoping that you get the same fatal error message as in comment #0. Interesting to learn that a simple QtQuick test does not fail to create an OpenGL context, while Spectacle using QtQuick apparently does.