Bug 1274025 - gnome-shell-wayland killed by signal 5
gnome-shell-wayland killed by signal 5
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: wayland (Show other bugs)
22
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-21 14:17 EDT by Rubén Lledó
Modified: 2015-10-29 18:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-29 18:02:22 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
boot-journalctl.log (557.09 KB, text/x-vhdl)
2015-10-21 14:17 EDT, Rubén Lledó
no flags Details
boot-dmesg.log (63.37 KB, text/plain)
2015-10-21 14:20 EDT, Rubén Lledó
no flags Details
screenshot (176.23 KB, image/jpeg)
2015-10-21 14:25 EDT, Rubén Lledó
no flags Details

  None (edit)
Description Rubén Lledó 2015-10-21 14:17:32 EDT
Created attachment 1085263 [details]
boot-journalctl.log

Description of problem:
gnome-shell and wayland crashes after a system upgrade to kernel-4.2.3-200


Version-Release number of selected component (if applicable):
kernel-4.2.3-200.fc22
gnome-shell-3.16.3-1.fc22
wayland-1.7.0-1.fc22

How reproducible:


Steps to Reproduce:
1. upgrade to kernel-4.2.3-200
2. reboot

Actual results:
System displays an error that reports the impossibility to recover and suggests to log out and retry, but this is also impossible (see screenshot attached).

Expected results:
System working.

Additional info:
Comment 1 Rubén Lledó 2015-10-21 14:20 EDT
Created attachment 1085264 [details]
boot-dmesg.log
Comment 2 Rubén Lledó 2015-10-21 14:25 EDT
Created attachment 1085265 [details]
screenshot
Comment 3 Rubén Lledó 2015-10-29 18:02:22 EDT
Hello.

I upgraded to kernel 4.2.3 again and it didn't happened any more.

Sorry.

Note You need to log in before you can comment on or make changes to this bug.