ksplashqml crashed with SIGABRT in QMessageLogger::fatal()

Bug #1640451 reported by Oleksandr Pikozh
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-304 (Ubuntu)
Confirmed
Critical
Unassigned
plasma-workspace (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

I'm unable to start plasma after nvidia nvidia-304 package upgrade (and reboot).

The related KDE bug report is (at least, KDE crash handler (DrKonqi) considered my report a duplicate): https://bugs.kde.org/show_bug.cgi?id=372229.
However, I discovered that the crash is caused by upgrade to nvidia-304=304.132-0ubuntu0.16.04.2 (with nvidia-304=304.131-0ubuntu3 it worked).

Current version of packages make my system unusable at all:
- With nvidia-304, nvidia-opencl-icd-304, nvidia-settings packages installed (and xserver-xorg-video-nouveau purged) I perceive the currently described bug.
- With xserver-xorg-video-nouveau package installed (and nvidia-304, nvidia-opencl-icd-304, nvidia-settings purged) the video isn't working at all (colorful screen and system hang).
- With all them purged session starts and seems to work fine, but them crashes every 5-20mins (probably, I'll fill a separate report for that).

1) lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04

2) apt-cache policy plasma-workspace nvidia-304 nvidia-opencl-icd-304 nvidia-settings
plasma-workspace:
  Installed: 4:5.5.5.2-0ubuntu1
  Candidate: 4:5.5.5.2-0ubuntu1
  Version table:
 *** 4:5.5.5.2-0ubuntu1 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status
nvidia-304:
  Installed: 304.132-0ubuntu0.16.04.2
  Candidate: 304.132-0ubuntu0.16.04.2
  Version table:
 *** 304.132-0ubuntu0.16.04.2 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages
     304.131-0ubuntu3 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages
nvidia-opencl-icd-304:
  Installed: 304.132-0ubuntu0.16.04.2
  Candidate: 304.132-0ubuntu0.16.04.2
  Version table:
 *** 304.132-0ubuntu0.16.04.2 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages
     304.131-0ubuntu3 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages
nvidia-settings:
  Installed: 361.42-0ubuntu1
  Candidate: 361.42-0ubuntu1
  Version table:
 *** 361.42-0ubuntu1 500
        500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

3) I expected plasma to start normally on system start-up (I use autologin) and/or on manual execution of 'sudo service sddm start' in first console (assuming sddm was previously shut down).

4) Black screen for a second, then 5 or more cascaded windows of KDE crash handler.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: plasma-workspace 4:5.5.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Nov 9 12:17:49 2016
ExecutablePath: /usr/bin/ksplashqml
ExecutableTimestamp: 1460701605
InstallationDate: Installed on 2015-11-10 (364 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
ProcCmdline: ksplashqml Breeze --pid
ProcCwd: /home/user
Signal: 6
SourcePackage: plasma-workspace
StacktraceTop:
 qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1578
 QMessageLogger::fatal (this=this@entry=0x7fffdc604b30, msg=msg@entry=0x7f92c2e932c5 "%s") at global/qlogging.cpp:781
 QSGRenderLoop::handleContextCreationFailure (this=this@entry=0xec5920, window=0xec8f40, isEs=isEs@entry=false) at scenegraph/qsgrenderloop.cpp:244
 QSGThreadedRenderLoop::handleExposure (this=this@entry=0xec5920, window=window@entry=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:919
 QSGThreadedRenderLoop::exposureChanged (this=0xec5920, window=0xec8f40) at scenegraph/qsgthreadedrenderloop.cpp:857
Title: ksplashqml crashed with SIGABRT in qt_message_fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Oleksandr Pikozh (o-pikozh) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /tmp/apport_sandbox_xTMfPP/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /tmp/apport_sandbox_xTMfPP/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 QSGThreadedRenderLoop::handleExposure(QQuickWindow*) () from /tmp/apport_sandbox_xTMfPP/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 QSGThreadedRenderLoop::exposureChanged(QQuickWindow*) () from /tmp/apport_sandbox_xTMfPP/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 QWindow::event(QEvent*) () from /tmp/apport_sandbox_xTMfPP/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in plasma-workspace (Ubuntu):
importance: Undecided → Medium
summary: - ksplashqml crashed with SIGABRT in qt_message_fatal()
+ ksplashqml crashed with SIGABRT in QMessageLogger::fatal()
tags: removed: need-amd64-retrace
Revision history for this message
Oleksandr Pikozh (o-pikozh) wrote :

This seems to be nvidia-304-, not plasma-workspace-related bug. At least, KDE maintainers closed the corresponding bug.

Revision history for this message
Oleksandr Pikozh (o-pikozh) wrote :

This seems to be "nvidia-304"-, not "plasma-workspace"-related bug. At least, KDE maintainers closed the corresponding bug.

information type: Private → Public
Revision history for this message
Veress Krisztián (krirz) wrote :

1. Fekete nvidia-304.
sudo apt remove --purge nvidia-304

2. Download nvidia-304.131.0ubuntu3.deb
3. Install nvidia driver
sudo dpkg -i nvidia-304.131.0ubuntu3
deb
4. Reboot

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-304 (Ubuntu):
status: New → Confirmed
Changed in plasma-workspace (Ubuntu):
status: New → Confirmed
Revision history for this message
lothar4ever (lothar4ever) wrote :

Steps i did to solve this:

1. sudo apt-get install nvidia-304=304.131-0ubuntu3
(it will downgrade to 131)
2. sudo apt-mark hold nvidia-304
(it will prevent future automatic updates)

I don't know if in the future it will be a problem not having it updated, but for now i can work like this.

Changed in nvidia-graphics-drivers-304 (Ubuntu):
importance: Undecided → Critical
Changed in plasma-workspace (Ubuntu):
importance: Medium → Critical
description: updated
Revision history for this message
Frau Tukka (frautukka) wrote :

I experienced the same issue. The instructions in comment #11 helped to resolve it for now. Not quite sure what to do for the future of this package?

Revision history for this message
Oleksandr Pikozh (o-pikozh) wrote :

@frautukka, I'm not experienced in this...

Propositions:
(a) Report upstream? (I reported upstream to KDE, but they say it's not their issue; IMHO, they're right. We should report upstream to nvidia.)
(b) Publish 304.131 version until fixed 304.133 will be released upstream.

Revision history for this message
Oleksandr Pikozh (o-pikozh) wrote :

I discovered this is duplicate of #1639180.

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.