On Wed, 2008-11-26 at 07:42 +, Matthew Gadd wrote:
> I'm not sure which processes these PIDs belong to, I tried doing a 'sudo ps
> -ef
> | grep {pid}' on them to see, but I didn't find any processes with PIDs
> matching
> those in the logs.
>
> The problem I had is that when I turn on the co
> Sorry, I don't remember reading your original message so I'm not
> familiar with the exact problem you're experiencing. Those messages are
> generic messages that the X server prints when it stops a client from
> connecting to it (for example, it might not be authorised to connect).
> "6826" is t
On Tue, 2008-11-25 at 23:12 +, Matthew Gadd wrote:
> Dunno if anyone got my previous post about a strange problem with GDM, or if
> it's just that no-one has any idea how to fix it. Anyway, I've tried a few
> things to see if they make a difference.
>
> I tried changing the theme of GDM (you n
Dunno if anyone got my previous post about a strange problem with GDM, or if
it's just that no-one has any idea how to fix it. Anyway, I've tried a few
things to see if they make a difference.
I tried changing the theme of GDM (you never know) and disabling and reenabling
automatic login (I use it
I'm curently having a strange problem with GDM (although fortunately it's
relatively minor).
The problem occurs like this, most of the startup goes normally, GDM begins to
start. Then presumably some kind of error occurs, because GDM restarts. The
second time it starts, it works absolutely fine.
I'm curently having a strange problem with GDM (although fortunately it's
relatively minor).
The problem occurs like this, most of the startup goes normally, GDM begins to
start. Then presumably some kind of error occurs, because GDM restarts. The
second time it starts, it works absolutely fine.
