Since I made the switch to a 64 bit machine (still using 32 bit Fedora
19) there is a long delay just before lightdm comes up with the login
screen.
Can someone take a look at this output and perhaps point out why and
where it's occurring ? By the way I don't use LVM or raid...can I disable
thes
On 13.08.2013 18:49, Frank wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> 19) there is a long delay just before lightdm comes up with the login
> screen.
> Can someone take a look at this output and perhaps point out why and
> where it's occurring ? By the way I d
On Tue, 13 Aug 2013 12:49:13 -0400
Frank wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit
> Fedora 19) there is a long delay just before lightdm comes up with
> the login screen.
> Can someone take a look at this output and perhaps point out why and
> where it's occurring
On 08/13/2013 01:24 PM, poma wrote:
On 13.08.2013 18:49, Frank wrote:
Since I made the switch to a 64 bit machine (still using 32 bit Fedora
19) there is a long delay just before lightdm comes up with the login
screen.
///snip///
[frank@localhost ~]$ sudo systemd-analyze blame
19.
On Tue, Aug 13, 2013 at 02:00:33PM -0400, Frank wrote:
> On 08/13/2013 01:24 PM, poma wrote:
> >On 13.08.2013 18:49, Frank wrote:
> >>Since I made the switch to a 64 bit machine (still using 32 bit Fedora
> >>19) there is a long delay just before lightdm comes up with the login
> >>screen.
>
> ///
On 08/13/2013 02:50 PM, Fred Smith wrote:
On Tue, Aug 13, 2013 at 02:00:33PM -0400, Frank wrote:
On 08/13/2013 01:24 PM, poma wrote:
On 13.08.2013 18:49, Frank wrote:
Since I made the switch to a 64 bit machine (still using 32 bit Fedora
19) there is a long delay just before lightdm comes up w
Dana 13.08.2013 20:00, Frank je napisao:
> On 08/13/2013 01:24 PM, poma wrote:
>> On 13.08.2013 18:49, Frank wrote:
>>> Since I made the switch to a 64 bit machine (still using 32 bit Fedora
>>> 19) there is a long delay just before lightdm comes up with the login
>>> screen.
>
…
>>> [frank@local
On 08/13/2013 05:28 PM, poma wrote:
Dana 13.08.2013 20:00, Frank je napisao:
On 08/13/2013 01:24 PM, poma wrote:
On 13.08.2013 18:49, Frank wrote:
Since I made the switch to a 64 bit machine (still using 32 bit Fedora
19) there is a long delay just before lightdm comes up with the login
screen
So32-bit software on a 64-bit CPU sometimes may not be all it's
cracked up to be :)
Boy, Poma, if you can't figure it outI doubt anyone here can -
I've been following your various and sundry suggestions to users
closely and you are usually close to, if not on the mark.
Is this wor
On 13/08/13 08:40 PM, Roger wrote:
So32-bit software on a 64-bit CPU sometimes may not be all it's
cracked up to be :)
Boy, Poma, if you can't figure it outI doubt anyone here can -
I've been following your various and sundry suggestions to users
closely and you are usually close to,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/14/2013 12:49 AM, Frank wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit Fedora 19)
> there is a long delay just before lightdm comes up with the login screen.
> Can someone take a look at this output and perhaps point ou
On 08/13/2013 10:07 PM, Frank wrote:
On 13/08/13 08:40 PM, Roger wrote:
So32-bit software on a 64-bit CPU sometimes may not be all it's
cracked up to be :)
Boy, Poma, if you can't figure it outI doubt anyone here can -
I've been following your various and sundry suggestions to users
On 14.08.2013 01:13, Frank wrote:
…
> Is this worth submitting a bug ??
First check whether it's a 'lightdm-gtk-greeter' issue,
yum install lightdm-razorqt
alternatives --config lightdm-greeter
systemctl restart lightdm
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe
On 08/14/2013 05:02 AM, poma wrote:
On 14.08.2013 01:13, Frank wrote:
…
Is this worth submitting a bug ??
First check whether it's a 'lightdm-gtk-greeter' issue,
yum install lightdm-razorqt
alternatives --config lightdm-greeter
systemctl restart lightdm
No...it's some other problem. The
On 14.08.2013 15:11, Frank wrote:
> On 08/14/2013 05:02 AM, poma wrote:
>> On 14.08.2013 01:13, Frank wrote:
>> …
>>> Is this worth submitting a bug ??
>>
>> First check whether it's a 'lightdm-gtk-greeter' issue,
>>
>> yum install lightdm-razorqt
>> alternatives --config lightdm-greeter
>> systemc
On Tue, Aug 13, 2013 at 10:51 AM, আনন্দ কুমার সমাদ্দার
wrote:
> Can you not use bootchart to visualise this and find the culprit?
To expand upon this, just add the following to your kernel command
line before booting:
init=/usr/lib/systemd/systemd-bootchart
Then, after you system has booted, ch
On 08/14/2013 10:14 AM, poma wrote:
lspci -nnk | grep VGA -A2
[frank@localhost ~]$ lspci -nnk | grep VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q963/Q965
Integrated Graphics Controller [8086:2992] (rev 02)
Subsystem: Dell Device [1028:01da]
Kernel dr
On 13 August 2013 18:49, Frank wrote:
> Since I made the switch to a 64 bit machine (still using 32 bit Fedora 19)
> there is a long delay just before lightdm comes up with the login screen.
> Can someone take a look at this output and perhaps point out why and
> where it's occurring ? By the way
On 08/14/2013 10:14 AM, poma wrote:
On 14.08.2013 15:11, Frank wrote:
On 08/14/2013 05:02 AM, poma wrote:
On 14.08.2013 01:13, Frank wrote:
…
Is this worth submitting a bug ??
First check whether it's a 'lightdm-gtk-greeter' issue,
yum install lightdm-razorqt
alternatives --config lightdm-g
On 08/14/2013 11:33 AM, Ahmad Samir wrote:
On 13 August 2013 18:49, Frank mailto:bea...@videotron.ca>> wrote:
Since I made the switch to a 64 bit machine (still using 32 bit
Fedora 19) there is a long delay just before lightdm comes up with
the login screen.
Can someone take a lo
On 08/14/2013 11:51 AM, Frank wrote:
On 08/14/2013 11:33 AM, Ahmad Samir wrote:
On 13 August 2013 18:49, Frank mailto:bea...@videotron.ca>> wrote:
Since I made the switch to a 64 bit machine (still using 32 bit
Fedora 19) there is a long delay just before lightdm comes up with
the l
On 14.08.2013 17:35, Frank wrote:
> On 08/14/2013 10:14 AM, poma wrote:
>> On 14.08.2013 15:11, Frank wrote:
>>> On 08/14/2013 05:02 AM, poma wrote:
On 14.08.2013 01:13, Frank wrote:
…
> Is this worth submitting a bug ??
First check whether it's a 'lightdm-gtk-greeter' issue
On 08/14/2013 02:15 PM, poma wrote:
On 14.08.2013 17:35, Frank wrote:
On 08/14/2013 10:14 AM, poma wrote:
On 14.08.2013 15:11, Frank wrote:
On 08/14/2013 05:02 AM, poma wrote:
On 14.08.2013 01:13, Frank wrote:
…
Is this worth submitting a bug ??
First check whether it's a 'lightdm-gtk-gree
On 08/14/2013 09:07 AM, Frank wrote:
Re-enabled lightdm, and we are back to a 25 sec delay before it comes
up.
I really don't know what to do next.I can "solve" my problem by going
back to lxdm, but I really prefer the lightdm interface.
I had a similar issue on my laptop after upgrading to
On 14.08.2013 20:49, Frank wrote:
…
> No change at all - still a long delay. Either I will
> just put up with it (I like the interface) or I'll go back to
> lxdm. If I am still curious in a day or two, I'll run bootchart.
> Right now I am just frustrated.
>
>
>
> Thanks Poma
>
>
> Regards
>
> To opt out of the equation an Xorg driver for Intel integrated graphics
> chipsets - man 4 intel, you can try the following:
>
> /boot/grub2/grub.cfg
> linux … nomodeset
>
For further testing, you can also try the following:
systemctl mask accounts-daemon.service
'lightdm' can work wi
On 08/14/2013 07:02 PM, poma wrote:
To opt out of the equation an Xorg driver for Intel integrated graphics
chipsets - man 4 intel, you can try the following:
/boot/grub2/grub.cfg
linux … nomodeset
Didn't work - put me into Vesa mode I guess but the delay remains
For further testin
On 08/14/2013 03:24 PM, Joe Zeff wrote:
On 08/14/2013 09:07 AM, Frank wrote:
Re-enabled lightdm, and we are back to a 25 sec delay before it comes
up.
I really don't know what to do next.I can "solve" my problem by going
back to lxdm, but I really prefer the lightdm interface.
I had a simi
On 08/14/2013 04:55 PM, Frank wrote:
Only took a minute..but it didn't solve the problem.
Even cutting down the delay is better than nothing. After moving from
F17 to F19 lightdm had a long delay, both in coming up and in getting to
a responsive desktop after login. (Only on my laptop, howe
On 08/14/2013 08:27 PM, Joe Zeff wrote:
On 08/14/2013 04:55 PM, Frank wrote:
Only took a minute..but it didn't solve the problem.
Even cutting down the delay is better than nothing. After moving from
F17 to F19 lightdm had a long delay, both in coming up and in getting to
a responsive desktop
On 15.08.2013 01:53, Frank wrote:
> On 08/14/2013 07:02 PM, poma wrote:
>>
>>> To opt out of the equation an Xorg driver for Intel integrated graphics
>>> chipsets - man 4 intel, you can try the following:
>>>
>>> /boot/grub2/grub.cfg
>>> linux …nomodeset
>
>
> Didn't work - put me into V
…
>
> 5th:
> cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
> - add 10s delay in
> /etc/systemd/system/lightdm.service
> i.e.
> …
> [Service]
> ExecStartPre=/usr/bin/sleep 10
> ExecStart=/usr/sbin/lightdm
> …
>
> - enable it
> i.e.
> systemctl enable lightdm.service --force
>
>
On 08/15/2013 04:19 AM, poma wrote:
On 15.08.2013 01:53, Frank wrote:
On 08/14/2013 07:02 PM, poma wrote:
To opt out of the equation an Xorg driver for Intel integrated graphics
chipsets - man 4 intel, you can try the following:
/boot/grub2/grub.cfg
linux …nomodeset
Didn't work -
On 08/15/2013 01:58 PM, poma wrote:
…
5th:
cp /usr/lib/systemd/system/lightdm.service /etc/systemd/system
- add 10s delay in
/etc/systemd/system/lightdm.service
i.e.
…
[Service]
ExecStartPre=/usr/bin/sleep 10
ExecStart=/usr/sbin/lightdm
…
- enable it
i.e.
systemctl enable lightdm.service --for
On 15.08.2013 20:10, Frank wrote:
>With all due respect, I don't understand what's going on here---my
> network manager is not disabled. What effect does adding sleep to
> lightdm.service produce ?? I think I am missing the point :)
>
> Regards
>
>
> Frank
It is a famous the dodge by braki
On 08/15/2013 08:46 PM, poma wrote:
On 15.08.2013 20:10, Frank wrote:
With all due respect, I don't understand what's going on here---my
network manager is not disabled. What effect does adding sleep to
lightdm.service produce ?? I think I am missing the point :)
Regards
Frank
It is a
On 16.08.2013 02:55, Frank wrote:
> On 08/15/2013 08:46 PM, poma wrote:
>> On 15.08.2013 20:10, Frank wrote:
>>
>>> With all due respect, I don't understand what's going on here---my
>>> network manager is not disabled. What effect does adding sleep to
>>> lightdm.service produce ?? I think I a
>
> Looks like you're not as skilled as Maverick. ;)
>
Neither am I. :)
Bummer!
poma
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/cod
Didn't work - put me into Vesa mode I guess but the delay remains
None of those worked for me either
Roger
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http:/
On 16.08.2013 06:36, Roger wrote:
>
> Didn't work - put me into Vesa mode I guess but the delay remains
>
> None of those worked for me either
> Roger
Now you have more than enough informations for a solid bug report.
- upstream:
https://bugs.launchpad.net/lightdm
- downstream:
https://
On 08/14/2013 10:33 AM, T.C. Hollingsworth wrote:
On Tue, Aug 13, 2013 at 10:51 AM, আনন্দ কুমার সমাদ্দার
wrote:
Can you not use bootchart to visualise this and find the culprit?
To expand upon this, just add the following to your kernel command
line before booting:
init=/usr/lib/systemd/syst
41 matches
Mail list logo
