, 4 Jun 2010 15:33:08
To: Владимир Новосельцев
Cc:
Subject: Re: [osol-discuss] Problem: Very long delay before login prompt
(GDM splash)
On 2010-06-02 21:37, Владимир Новосельцев wrote:
> 02.06.2010 14:02, Robin Axelsson пишет:
>> On 2010-05-12 23:48, Mark Martin wrote:
>>> On
On 2010-06-02 21:37, Владимир Новосельцев wrote:
02.06.2010 14:02, Robin Axelsson пишет:
On 2010-05-12 23:48, Mark Martin wrote:
On Tue, May 11, 2010 at 5:20 PM, Robin Axelsson
wrote:
I'm not using any particular locale (I use the default system
language) and
I use a Swedish keyboard layout.
On 2010-06-02 21:20, Brian Cameron wrote:
Robin:
Here's the output of the "top" command while it's frozen at the login
splash:
Unfortunately the top output does not show any particular processes
consuming a lot of memory, so this indicates that the delay is not CPU
bound.
Note there is a bu
On 2010-06-02 21:20, Brian Cameron wrote:
Robin:
Here's the output of the "top" command while it's frozen at the login
splash:
Unfortunately the top output does not show any particular processes
consuming a lot of memory, so this indicates that the delay is not CPU
bound.
Note there is a bu
Can you post your /etc/hosts?
I was seeing the same delay in startx. What I did was to add an entry for my
hostname in there.
BEFORE:
::1 oso-vbox oso-vbox.local localhost loghost
127.0.0.1 oso-vbox.local localhost loghost
AFTER:
::1 oso-vbox oso-vbox.local localhost loghost oso-vbox
127.0.0.1
02.06.2010 14:02, Robin Axelsson пишет:
On 2010-05-12 23:48, Mark Martin wrote:
On Tue, May 11, 2010 at 5:20 PM, Robin Axelsson
wrote:
I'm not using any particular locale (I use the default system
language) and
I use a Swedish keyboard layout. The keyboard is a Logitech keyboard
connected vi
Robin:
Here's the output of the "top" command while it's frozen at the login
splash:
Unfortunately the top output does not show any particular processes
consuming a lot of memory, so this indicates that the delay is not CPU
bound.
Note there is a bug about a very similar problem here:
htt
On 2010-05-12 22:56, Brian Cameron wrote:
Robin:
Just to report what I did last night. I did a relogin with truss on
gnome-session-real (since the /usr/bin/gnome-session was renamed to
gnome-session-real). The system froze and was stuck as I described in my
previous post. After waiting for abo
On 2010-05-12 23:48, Mark Martin wrote:
On Tue, May 11, 2010 at 5:20 PM, Robin Axelsson
wrote:
I'm not using any particular locale (I use the default system language) and
I use a Swedish keyboard layout. The keyboard is a Logitech keyboard
connected via the PS/2 port and the mouse is a Log
On 2010-05-12 23:48, Mark Martin wrote:
On Tue, May 11, 2010 at 5:20 PM, Robin Axelsson
wrote:
I'm not using any particular locale (I use the default system language) and
I use a Swedish keyboard layout. The keyboard is a Logitech keyboard
connected via the PS/2 port and the mouse is a Log
You shouldn't truss anymore that 3 min for login.
-Ghee
On 05/12/10 11:41 AM, Robin Axelsson wrote:
Just to report what I did last night. I did a relogin with truss on
gnome-session-real (since the /usr/bin/gnome-session was renamed to
gnome-session-real). The system froze and was stuck as I d
On Tue, May 11, 2010 at 5:20 PM, Robin Axelsson
wrote:
> I'm not using any particular locale (I use the default system language) and
> I use a Swedish keyboard layout. The keyboard is a Logitech keyboard
> connected via the PS/2 port and the mouse is a Logitech USB mouse. Also note
> that this del
Robin:
Just to report what I did last night. I did a relogin with truss on
gnome-session-real (since the /usr/bin/gnome-session was renamed to
gnome-session-real). The system froze and was stuck as I described in my
previous post. After waiting for about 2 hours I interrupted my attempt.
The tr
Just to report what I did last night. I did a relogin with truss on
gnome-session-real (since the /usr/bin/gnome-session was renamed to
gnome-session-real). The system froze and was stuck as I described in my
previous post. After waiting for about 2 hours I interrupted my attempt.
The truss fil
I'm not using any particular locale (I use the default system language)
and I use a Swedish keyboard layout. The keyboard is a Logitech keyboard
connected via the PS/2 port and the mouse is a Logitech USB mouse. Also
note that this delay has not been there all the time. Even after I
upgraded to
I forgot to say: I don't know what "face browser" means. If it is the
feature that enables the possibility of "choosing" users at the login
and/or poweroff/restart the the answer to this question is no.
- Robin.
On 2010-05-07 18:34, Brian Cameron wrote:
Robin:
According to the GDM debug outpu
Robin:
On 05/ 8/10 02:14 PM, Robin Axelsson wrote:
The delay is 3 minutes long (~180 seconds) and not 2 or 30 seconds. This
is delay easy to measure since there's a clock in the bottom right
corner of the login splash that is frozen which "jumps" 3 minutes
forward when the input text field for
Here's the log file. The clock in the bottom right of the login splash
screen is frozen at 10:46 and when the user prompt comes up the clock
"jumps" to 10:49. I've tried to analyze this log but it is difficult for
me to understand it and link the messages to this delay.
- Robin.
On 2010-05-06 1
Robin:
According to the GDM debug output from /var/adm/messages that you
provided the login program is taking 13 seconds to start up. This
does not seem an unusually long time for GDM to start up.
Also I do not see anything in the log which indicates that anything in
particular which is very s
Maby totally unrelated, but anyway:
>From first install, I wasn't very pleased with gnome startup (about 90 sec).
>I found out later that this was known "issue" caused by "wrong" setup in my
>bios. After disabling my "non-existing" floppy drive in the bios, this 90
>sec. delay vanished.
htt
To debug this, I would recommend editing the /etc/gdm/custom.conf file
and add the line "Enable=true" after the line that says "[debug]" so
it looks like this:
[debug]
Enable=true
Then reboot. After reboot, the syslog file (/var/adm/messages) should
have GDM related debug messages near the bot
I see one error message complaining about failure to start service:
"svc:/network/sendmail-client:default"
When looking at the list of running services ("~$ svcs") this service is
the only one in maintenance mode, all other services are online except
for the "legacy-run" services. When checking
What can you see on the screen, once you hit the key after the first
moving splash part shows? That'll finish the splash,and you'll see the
console...
Matthias
You (Robin Axelsson) wrote:
> Quite recently the system have picked up a new behaviour that occurs every
> time I boot and ever
Quite recently the system have picked up a new behaviour that occurs every time
I boot and every time I log out and back in again; when the splash login screen
appears it takes about 3 minutes before it prompts for username. In the
meantime it responds to CIFS and ssh. What's wrong and how can I
24 matches
Mail list logo
