Bug 680814 - F15 Create User screen hangs when hitting backspace on purple password on Dell 340
Summary: F15 Create User screen hangs when hitting backspace on purple password on Del...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 15
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Gracik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 22:03 UTC by Larry Vaden
Modified: 2013-07-04 12:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-14 08:35:34 UTC
Type: ---


Attachments (Terms of Use)

Description Larry Vaden 2011-02-27 22:03:14 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0b12) Gecko/20110226 Firefox/4.0b12

When a purple password has been entered and the backspace key is hit to change the last couple of characters of the password, that session becomes unresponsive, although ctrl-alt-f2 and ctrl-alt-f3 are functional;  however, logins take approximately 25 seconds.

Reproducible: Always

Steps to Reproduce:
1.boot
2.select install
3.enter purple password
Actual Results:  
The system became non responsive to everything but ctrl-alt-f2 and ctrl-alt-f3;  furthermore, logins from there took 25 seconds after the password for root was entered.

Expected Results:  
Backspace key in field having purple password should act nominally.

The following may be helpful, it may not be helpful.

[root@ping vaden]# cat fc15-bug-firstboot
Sun Feb 27 13:49:27 CST 2011
root       636  0.0  0.1   5416  1548 tty1     Ss+  13:38   0:00 /bin/bash /etc/init.d/firstboot start
root       664  0.3  3.0  60380 31596 tty1     S+   13:38   0:02 /usr/bin/python2 /usr/sbin/firstboot --reconfig
root       746  0.0  1.3  36304 14144 tty1     S+   13:38   0:00 /usr/bin/python2 /usr/sbin/firstboot --reconfig
root      1474  0.0  0.0   4456   760 tty2     S+   13:49   0:00 grep --color=auto -i firstboot
Feb 26 19:00:06 ping kernel: [   37.893266] type=1400 audit(1298768404.837:10): avc:  denied  { write } for  pid=348 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 19:04:06 ping systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 26 19:04:06 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 26 19:18:13 ping kernel: [   37.842977] type=1400 audit(1298769491.788:10): avc:  denied  { write } for  pid=345 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 19:56:10 ping kernel: [   38.641776] type=1400 audit(1298771768.586:10): avc:  denied  { write } for  pid=350 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 19:57:16 ping systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 26 19:57:16 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 26 20:03:09 ping kernel: [   37.824721] type=1400 audit(1298772187.768:10): avc:  denied  { write } for  pid=347 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 22:32:50 ping kernel: [   38.298300] type=1400 audit(1298781168.241:10): avc:  denied  { write } for  pid=352 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 23:09:55 ping kernel: [   38.507079] type=1400 audit(1298783393.451:10): avc:  denied  { write } for  pid=345 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 23:14:36 ping kernel: [   38.072275] type=1400 audit(1298783674.019:10): avc:  denied  { write } for  pid=349 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 26 23:25:43 ping kernel: [   38.224777] type=1400 audit(1298784341.169:10): avc:  denied  { write } for  pid=346 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 02:12:44 ping kernel: [   38.226147] type=1400 audit(1298794362.170:10): avc:  denied  { write } for  pid=346 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 02:46:43 ping kernel: [   39.374051] type=1400 audit(1298796401.318:10): avc:  denied  { write } for  pid=347 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 03:19:39 ping kernel: [   38.036349] type=1400 audit(1298798376.981:10): avc:  denied  { write } for  pid=348 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 03:41:32 ping kernel: [   38.741373] type=1400 audit(1298799684.687:12): avc:  denied  { write } for  pid=349 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 03:48:10 ping systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 27 03:48:10 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 04:02:07 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 04:02:07 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 04:02:07 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 04:06:32 ping kernel: [   38.870973] type=1400 audit(1298801061.816:11): avc:  denied  { write } for  pid=347 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 04:06:32 ping kernel: [   44.538253] type=1400 audit(1298801067.483:35): avc:  denied  { write } for  pid=347 comm="systemd-readahe" path="/usr/share/firstboot/modules" dev=dm-1 ino=1312823 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 04:06:32 ping kernel: [  168.461645] systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 27 04:06:32 ping kernel: [  168.678103] systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:05:35 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:05:58 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:10:30 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:33 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:35 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:35 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:35 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:40 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:49 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:49 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:53 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:56 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:56 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:14:58 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:15:08 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:15:12 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:17:01 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:17:21 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:17:34 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:17:50 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:18:05 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:18:42 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:18:45 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
Feb 27 13:40:50 ping kernel: [   42.117481] type=1400 audit(1298835522.061:11): avc:  denied  { write } for  pid=345 comm="systemd-readahe" path="/usr/share/firstboot/themes" dev=dm-1 ino=1310735 scontext=system_u:system_r:readahead_t:s0 tcontext=system_u:object_r:usr_t:s0 tclass=dir
Feb 27 13:54:01 ping systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 27 13:54:01 ping systemd[1]: Unit firstboot-graphical.service entered failed state.
[root@ping vaden]#

Comment 1 Martin Gracik 2011-02-28 11:42:33 UTC
What do you mean with "purple password" ?

Comment 2 Larry Vaden 2011-02-28 15:46:36 UTC
I am referring to the feature documented at <http://blogs.fedoraproject.org/wp/mclasen/page/2/>, save the color purple occurs in the case of a strong password rather than the documented green.

This is idle speculation (a SWAG), but I may not have waited long enough for the hang to clear.  e.g., last evening, I started the installation again from scratch after installing 4 other distros without a problem.

This time, I did not encounter a problem when backspacing on a 13 character password, but the system hung awaiting a start of NTP on the next screen (just as it had done before).  It was late, so I left it waiting (after observing it for several minutes) and when I checked this AM, 6 hours later, the NTP had proceeded.

This probably should be a separate bug report because of the difference in the symptoms, but I suspect the code which is causing the "apparent hangs" is the same in both cases.


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