Hide Forgot
Description of problem: While installing several packages and groups on Fedora 16beta X (or I assume more precise GDM) crashed several times reuslting in broken yum transactions. Version-Release number of selected component (if applicable): [m8ram@localhost ~]$ rpm -qa|grep gdm pulseaudio-gdm-hooks-0.9.23-1.fc16.x86_64 gdm-3.2.1.1-1.fc16.x86_64 [m8ram@localhost ~]$ sudo yum check-update [m8ram@localhost ~]$ sudo yum repolist repo id repo name status fedora Fedora 16 - x86_64 25,046 squeezecenter-release SqueezeCenter Release Repository 22 updates-testing Fedora 16 - x86_64 - Test Updates 7,297 repolist: 32,365 How reproducible: I encountered this at least 4 times today while installing the Xfce group (using the default Gnome 3 session) and later while installing several eclipse packages. Steps to Reproduce: 1. sudo yum install or sudo yum groupinstall 2. several packages are installed Actual results: screen goes blank and the login screen is displayed, the yum transaction is incomplete and the next yum run suggest running yum-complete-transaction Expected results: installation zithout crash Additional info: I'll attach the entire messages log for today. I apologize if it contains too much information but the majority of the logs are related to my attempts to install these packages and I do not know which sections of the GDM DEBUG output are relevant and which arent't.
Created attachment 530165 [details] /var/log/messages with today's log messgaes upload failed twice
Today I encountered more of these unexpected gdm crashes. I believe to have traced it down to the addition of user accounts. I can reproduce this issue by adding a user account: sudo /usr/sbin/useradd -r -g squeezeboxserver -d /tmp/squeezeboxserver -s /sbin/nologin -c "SqueezeBox Server2" -u 487 squeezeboxserver2 As soon as the command completes my X session (gnome 3) is killed and I'm presented with the login screen and all my open work is lost. From the secure log: Nov 5 15:38:47 lieve-pc sudo: m8ram : TTY=pts/0 ; PWD=/home/m8ram ; USER=root ; COMMAND=/usr/sbin/useradd -r -g squeezeboxserver -d /tmp/squeezeboxserver -s /sbin/nologin -c SqueezeBox Server2 -u 487 squeezeboxserver2 Nov 5 15:38:47 lieve-pc useradd[3045]: new user: name=squeezeboxserver2, UID=487, GID=474, home=/tmp/squeezeboxserver, shell=/sbin/nologin Nov 5 15:38:49 lieve-pc polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session4 (system bus name :1.123, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 5 15:38:50 lieve-pc gdm-welcome][3084]: pam_unix(gdm-welcome:session): session opened for user gdm by (uid=0) Nov 5 15:38:52 lieve-pc polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session5 (system bus name :1.144 [gnome-shell --gdm-mode], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 5 15:38:59 lieve-pc gdm-password][3136]: pam_unix(gdm-password:session): session opened for user m8ram by (uid=0) Nov 5 15:39:00 lieve-pc polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session5 (system bus name :1.144, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 5 15:39:02 lieve-pc polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.162 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
bug 702937 appears to describe similar crashes
reproduced it again by installing abrt which also creates a new user: [m8ram@lieve-pc ~]$ rpm -q --scripts abrt preinstall scriptlet (using /bin/sh): #uidgid pair 173:173 reserved in setup rhbz#670231 getent group abrt >/dev/null || groupadd -f -g 173 --system abrt getent passwd abrt >/dev/null || useradd --system -g abrt -u 173 -d /etc/abrt -s /sbin/nologin abrt exit 0
what does rpm -q accountsservice say ? Can you determine what is actually crashing, and maybe get a stacktrace ?
Created attachment 549836 [details] log messages
Today, I installed Fedora 16 x86_64 on my Dell OptiPlex 980 PC. After the installation, I mounted my old /home partition and added back my old user in /etc/passwd and /etc/group with uid/gid 500, as I did not want to do a mass chown today. When doing "yum install" on various software I missed, I started being logged out at random(?) times. Googling on the symptoms, I found this ticket, and I can now reproduce the crashes by running a simple "useradd testuser". Attachment 549836 [details] contains messages from /var/log/{messages,secure} during a crash triggered by that simple method. Turning of SELinux with "setenforce 0" does not make a difference. I do not see the same crashes on my laptop, that I have upgraded from Fedora 15 to Fedora 16 (keeping my user with uid 500).
same problem today, while installing xorg-x11-xfs-1.1.1-3.fc16.x86_64, on a fully updated F16 x86_64, with rpmfusion NVidia driver.
maybe related to bug on fc17 alpha https://bugzilla.redhat.com/show_bug.cgi?id=804361
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.