Hello, crash means, in running level 3: startx (with a new user) The graphics mode (if there is not xorg.conf.d directory) starts asking about language and keyboard and return to text mode (before, it says, Oh no! etc..) In running level 6. it there is a xorg.conf.d directory the machine need to be unplugged after starting Plymouth Now journalctl -b _COMM=gdm-x-session provides anything when it fails in the archive I put 5 files The *.OK are files when I run Live the other 2 ones are the ones which fail the machine Thank for your help. =========================================================================== Patrick DUPRÉ | | email: pdupre@xxxxxxx Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France =========================================================================== > Sent: Tuesday, July 28, 2015 at 9:01 PM > From: "Michael Schwendt" <mschwendt@xxxxxxxxx> > To: users@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: Update 20 -> 22, failure > > On Tue, 28 Jul 2015 17:27:01 +0200, Patrick Dupre wrote: > > > > It _should_ just work. Did you need to configure anything when > > > running the Live version? No. Why would you want to configure > > > anything for your installation then? > > > > Starx would like to configure, but crashes. > > The verb "to crash" is not well-defined. Do you mean the system > freezes? It locks up? Can you still reach it via SSH? > > > Just tell me exactly which files a should compare? > > Live does not seems to create much files in /etc/X11 > > Log files, not configuration files. > > https://fedoraproject.org/wiki/How_to_debug_Xorg_problems > https://fedoraproject.org/wiki/Common_F22_bugs > > > > The X server logs are still missing. No sign of booting with > > > SELinux set to permissive mode either to work around the errors > > > you get. > > Just tell me exactly which files a should check? > > Should I run restorecon? > > No, "permissive mode" refers to booting with "enforcing=0" option > appended to the kernel boot parameters. It's a very basic (and less > of a big hammer than selinux=0) to check whether SELinux might cause > problems. It doesn't tell much more. For example, it doesn't tell > whether you've had errors in F20, too. > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org >
Attachment:
log.tgz
Description: application/compressed
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
