plasmashell crashed with SIGSEGV in QWindow::screen()

Bug #1674693 reported by Ovidiu-Florin BOGDAN
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
plasma-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I get random crashes. I hope the stacktrace get's added automatically, like I'm told it will happen.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: plasma-workspace 4:5.9.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Tue Mar 21 13:13:12 2017
ExecutablePath: /usr/bin/plasmashell
InstallationDate: Installed on 2017-02-23 (26 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/bin/plasmashell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ro_RO.UTF-8
 SHELL=/usr/bin/zsh
 LANGUAGE=
Signal: 11
SourcePackage: plasma-workspace
StacktraceTop:
 QWindow::screen() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? ()
 QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QGuiApplication::primaryScreenChanged(QScreen*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 QXcbConnection::updateScreens(xcb_randr_notify_event_t const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
Title: plasmashell crashed with SIGSEGV in QWindow::screen()
UpgradeStatus: Upgraded to zesty on 2017-02-27 (22 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo
XsessionErrors:
 (firefox:5258): Gtk-WARNING **: Error loading theme icon 'network-idle' for stock: Icon 'network-idle' not present in theme breeze
 (firefox:31478): Gtk-WARNING **: Error loading theme icon 'network-idle' for stock: Icon 'network-idle' not present in theme breeze

Revision history for this message
Ovidiu-Florin BOGDAN (ovidiu-florin) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in plasma-workspace (Ubuntu):
status: New → Invalid
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.