| 2016-11-15 17:16:30 |
Oleksandr Pikozh |
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 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 |
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 |
|
