Bug 1371407 - unable to cancel login anymore,after upgrade f24 to f25
Summary: unable to cancel login anymore,after upgrade f24 to f25
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf-plugin-system-upgrade
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-30 07:26 UTC by lnie
Modified: 2016-08-30 08:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-30 08:49:35 UTC
Type: Bug

Attachments (Terms of Use)
journalctl -b -1 (159.41 KB, text/x-vhdl)
2016-08-30 07:26 UTC, lnie 		no flags Details
dmesg (42.87 KB, text/plain)
2016-08-30 07:27 UTC, lnie 		no flags Details
video (559.07 KB, application/ogg)
2016-08-30 07:27 UTC, lnie 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description lnie 2016-08-30 07:26:48 UTC 
Created attachment 1195645 [details]
journalctl -b -1

Description of problem:
please see the video for more information.
I'm not sure if this is the right place to report this,if not,please feel free
to reassign,thanks.
 
Version-Release number of selected component (if applicable):
 

How reproducible:
always

Steps to Reproduce:
1. do a clean f24 installation  
2. do a full system update and reboot 
3. sudo dnf system-upgrade download --releasever=25 
4. sudo dnf system-upgrade reboot 
5. click the user name on the login page 
6. click on the "cancel" button
7. after do a dnf update,still don't work

Actual results:


Expected results:


Additional info:
Comment 1 lnie 2016-08-30 07:27:27 UTC 
Created attachment 1195646 [details]
dmesg
Comment 2 lnie 2016-08-30 07:27:54 UTC 
Created attachment 1195647 [details]
video
Comment 3 lnie 2016-08-30 08:49:35 UTC 
Turns out this is a mutter bug,and is fixed by the newly version (3.21.90-3)
Note You need to log in before you can comment on or make changes to this bug.