Used fedup F17 > F18. on a second vm
Only lightdm seems to have a problem.
Keeps appearing and disappearing.
Booted to telinit 3 logged in as user # lightdm --test-mode Failed to get D-Bus Connection.
all .rpmsave, .rpmnew have been sorted as necessary. full relabel has taken place.
How to get the light on the bus?
Regards, Frank
On 12/01/2012 11:43 AM, Frank Murphy wrote:
Used fedup F17 > F18. on a second vm
Only lightdm seems to have a problem.
Keeps appearing and disappearing.
Booted to telinit 3 logged in as user # lightdm --test-mode Failed to get D-Bus Connection.
all .rpmsave, .rpmnew have been sorted as necessary. full relabel has taken place.
How to get the light on the bus?
Regards, Frank
To use the test mode you have edit /etc/pam.d/lightdm and comment session required pam_loginuid.so
IIRC
On Sat, 01 Dec 2012 11:54:05 -0200 Sergio sergiocmailbox-users@yahoo.com.br wrote:
To use the test mode you have edit /etc/pam.d/lightdm and comment session required pam_loginuid.so
Done, just getting a black screen.
startx from level 3 works fine.
On Sat, 1 Dec 2012 14:01:09 +0000 Frank Murphy frankly3d@gmail.com wrote:
To use the test mode you have edit /etc/pam.d/lightdm and comment session required pam_loginuid.so
Done, just getting a black screen.
startx from level 3 works fine.
Spoke too fast back with the d-bus no connection bit.
--- Em sáb, 1/12/12, Frank Murphy frankly3d@gmail.com escreveu:
De: Frank Murphy frankly3d@gmail.com Assunto: Re: F18 Lightdm D-Bus Para: test@lists.fedoraproject.org Data: Sábado, 1 de Dezembro de 2012, 12:06 On Sat, 1 Dec 2012 14:01:09 +0000 Frank Murphy frankly3d@gmail.com wrote:
To use the test mode you have edit
/etc/pam.d/lightdm and comment
session required
pam_loginuid.so
Done, just getting a black screen.
startx from level 3 works fine.
Spoke too fast back with the d-bus no connection bit. --
I may have missed something but I thought the test mode was basically to test the greeters (like you can use it when you're already logged in and it will open lightdm in a window). I don't think it can be used 'for real'.
If you have issues with lightdm then the best thing is to look at its logs, I think.
On Sat, 1 Dec 2012 06:59:54 -0800 (PST) Sergio sergiocmailbox-users@yahoo.com.br wrote:
If you have issues with lightdm then the best thing is to look at its logs, I think.
Had a quick look at the logs. x-0.log empty lightdm-greeter.old words like cannot scale pixel buff?
lightdm.log, complains about greeter starting and stopping.
Maybe a bz?
Frank
--- Em sáb, 1/12/12, Frank Murphy frankly3d@gmail.com escreveu:
De: Frank Murphy frankly3d@gmail.com Assunto: Re: F18 Lightdm D-Bus Para: test@lists.fedoraproject.org Data: Sábado, 1 de Dezembro de 2012, 13:19 On Sat, 1 Dec 2012 06:59:54 -0800 (PST) Sergio sergiocmailbox-users@yahoo.com.br wrote:
If you have issues with lightdm then the best thing is
to look at
its logs, I think.
Had a quick look at the logs. x-0.log empty
Not normal, AFAIK.
lightdm-greeter.old words like cannot scale pixel buff?
lightdm.log is the main log for the DM itself, x-0.log is the X log and x-0-greeter.log is the log for the greeter. The latter usually just give the GTK3 warnings/errors.
lightdm.log, complains about greeter starting and stopping.
I think, not normal either.
Maybe a bz?
Frank
Not sure. Maybe for fedup. I upgraded my bare-metal system with yum and all went very well.
Make sure you have the lightdm files in integral states, check /etc/lightdm if you're using the old or the updated config files (if you have *.rpmnew files, these are the new ones so you might want to merge them. rpmconf is a tool made for that). Also make sure you reverted that comment on /etc/pam.d/lightdm.
Then boot to graphical.target and look at the logs in case it doesn't work.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/01/2012 04:53 PM, Sergio wrote:
Had a quick look at the logs. x-0.log empty
Not normal, AFAIK.
lightdm.log, complains about greeter starting and stopping.
I think, not normal either.
Maybe a bz?
Frank
I remember that one on a kvm virtual machine, filed as bug: https://bugzilla.redhat.com/show_bug.cgi?id=870007
It turned out, that had nothing to do with lightdm, but with xorg-x11-drv-qxl, which just crashes without writing xorg-log.
https://bugzilla.redhat.com/show_bug.cgi?id=879535
Downgrading xorg-x11-drv-qxl fixed my problem. Maybe, you're hit with the same?
Not sure. Maybe for fedup. I upgraded my bare-metal system with yum and all went very well.
Make sure you have the lightdm files in integral states, check /etc/lightdm if you're using the old or the updated config files (if you have *.rpmnew files, these are the new ones so you might want to merge them. rpmconf is a tool made for that). Also make sure you reverted that comment on /etc/pam.d/lightdm.
Then boot to graphical.target and look at the logs in case it doesn't work.
- -- Matthias Runge mrunge@matthias-runge.de mrunge@fedoraproject.org
On Sun, 02 Dec 2012 13:23:10 +0100 Matthias Runge mrunge@matthias-runge.de wrote:
I remember that one on a kvm virtual machine, filed as bug: https://bugzilla.redhat.com/show_bug.cgi?id=870007
It turned out, that had nothing to do with lightdm, but with xorg-x11-drv-qxl, which just crashes without writing xorg-log.
https://bugzilla.redhat.com/show_bug.cgi?id=879535
Downgrading xorg-x11-drv-qxl fixed my problem. Maybe, you're hit with the same?
Yes, not sure of the versions off hand, Downgrading *qxl has fixed the problem. LightDM now offers\and logs in.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/02/2012 01:41 PM, Frank Murphy wrote:
On Sun, 02 Dec 2012 13:23:10 +0100 Matthias Runge mrunge@matthias-runge.de wrote:
I remember that one on a kvm virtual machine, filed as bug: https://bugzilla.redhat.com/show_bug.cgi?id=870007
It turned out, that had nothing to do with lightdm, but with xorg-x11-drv-qxl, which just crashes without writing xorg-log.
https://bugzilla.redhat.com/show_bug.cgi?id=879535
Downgrading xorg-x11-drv-qxl fixed my problem. Maybe, you're hit with the same?
Yes, not sure of the versions off hand, Downgrading *qxl has fixed the problem. LightDM now offers\and logs in.
Great, that it worked for you!
Since there is no movement in that bug, could you please provide as much useful information as possible to https://bugzilla.redhat.com/show_bug.cgi?id=879535
Thanks. - -- Matthias Runge mrunge@matthias-runge.de mrunge@fedoraproject.org
-
Frank Murphy -
Matthias Runge -
Sergio