-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Fri, May 20, 2005 at 08:42:33AM -0500, Jay Kline wrote:
|
|>Steve Langasek wrote:
|>| On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
|>|
|>|>Steve Langasek wrote:
|>|>| On Wed, May 18, 2005 at 07:51:05AM -0500, J
On Fri, May 20, 2005 at 08:42:33AM -0500, Jay Kline wrote:
> Steve Langasek wrote:
> | On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
> |
> |>Steve Langasek wrote:
> |>| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
> |>|
> |>|>| Jay, taking care to run rm -f /usr/lib/libld
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
|
|>Steve Langasek wrote:
|>| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
|>|
|>|>| Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before
|>doing
On Wed, May 18, 2005 at 08:31:51AM -0500, Jay Kline wrote:
> Steve Langasek wrote:
> | On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
> |
> |>| Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before
> doing so,
> |>| would you mind upgrading to the libldap2 from unstable to see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
|
|>| Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before
doing so,
|>| would you mind upgrading to the libldap2 from unstable to see if it
fixes
|>| your pro
On Wed, May 18, 2005 at 07:51:05AM -0500, Jay Kline wrote:
> | Jay, taking care to run rm -f /usr/lib/libldap.so.2.0.15 before doing so,
> | would you mind upgrading to the libldap2 from unstable to see if it fixes
> | your problem?
> That did not change anything. libldap.so.2.0.15 did not exist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve Langasek wrote:
| On Tue, May 17, 2005 at 11:41:01AM -0700, Ryan Murray wrote:
|
|>On Tue, May 17, 2005 at 12:49:30PM -0500, Jay Kline wrote:
|>
|>>Alexander Sack wrote:
|>>| I did not found any hints on this in the bug report, so maybe it's
|>>wo
On Tue, May 17, 2005 at 11:41:01AM -0700, Ryan Murray wrote:
> On Tue, May 17, 2005 at 12:49:30PM -0500, Jay Kline wrote:
> > Alexander Sack wrote:
> > | I did not found any hints on this in the bug report, so maybe it's
> > worth asking:
> > |
> > | You see any unexpected messages in dmesg or any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
|>No, nothing of the sort. However, I am starting to lean towrads
|>libnss-ldap being the issue. Bug #302296
|
|
| Ahh, you didn't mention this! There is/was an ABI conflict between
the two,
| which would cause this. I can't find
On Tue, May 17, 2005 at 12:49:30PM -0500, Jay Kline wrote:
> Alexander Sack wrote:
> | I did not found any hints on this in the bug report, so maybe it's
> worth asking:
> |
> | You see any unexpected messages in dmesg or any system logs? Are there any
> | errors in /var/log/XFree86.0.log?
>
> No,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexander Sack wrote:
| I did not found any hints on this in the bug report, so maybe it's
worth asking:
|
| You see any unexpected messages in dmesg or any system logs? Are there any
| errors in /var/log/XFree86.0.log?
No, nothing of the sort. However
Hi,
I did not found any hints on this in the bug report, so maybe it's worth asking:
You see any unexpected messages in dmesg or any system logs? Are there any
errors in /var/log/XFree86.0.log?
Thanks,
--
GPG messages preferred. | .''`. ** Debian GNU/Linux **
Alexander Sack| :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeroen van Wolffelaar wrote:
| You don't happen to have a full disk or ran out of quota, right? I do
| have experiences with failed logins when stuff can't write to disk (temp
| files, log files, ...)
Disks have plenty of space (~80G free) and every use
On Thu, May 12, 2005 at 12:11:17PM -0500, Jay Kline wrote:
> Ryan Murray wrote:
> |>| And in /var/log/gdm/:0.log ? (It'll rotate to .1 when restarting)
> |>|
> |>It seems truncated, but here it is:
Truncated...
(...)
> Yes. It appears the X server is dieing. after authentication.
You don't ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
|>| And in /var/log/gdm/:0.log ? (It'll rotate to .1 when restarting)
|>|
|>It seems truncated, but here it is:
|>
|>XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-12.0.1 20050223080930
|>[EMAIL PROTECTED]
|>elix.org)
|>Release Date: 1
On Thu, May 12, 2005 at 11:30:31AM -0500, Jay Kline wrote:
> |>| And what is in the user's ~/.xsession-errors ? I have a feeling your
> |>| problem is in the session startup, and nothing to do with gdm.
> |>|
> |>
> |>The file is blank. Note that the sesision type did not change, and this
> |>beh
On Thu, May 12, 2005 at 11:02:19AM -0500, Jay Kline wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ryan Murray wrote:
> | On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
> |
> |>After a recent upgrade of gdm, logins "fail". A user inputs
> |>username/password/securID logi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
| On Thu, May 12, 2005 at 11:02:19AM -0500, Jay Kline wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>Ryan Murray wrote:
|>| On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
|>|
|>|>After a recent upgrade of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Murray wrote:
| On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
|
|>After a recent upgrade of gdm, logins "fail". A user inputs
|>username/password/securID login, it succeeds, goes to a black screen,
|>then back to login. Here is the o
On Wed, May 11, 2005 at 08:48:20AM -0500, Jay Kline wrote:
> After a recent upgrade of gdm, logins "fail". A user inputs
> username/password/securID login, it succeeds, goes to a black screen,
> then back to login. Here is the output to daemon.log:
>
> gdm[23126]: gdm_slave_xioerror_handler: Fat
Package: gdm
Version: 2.6.0.8-1
Severity: grave
Justification: renders package unusable
After a recent upgrade of gdm, logins "fail". A user inputs
username/password/securID login, it succeeds, goes to a black screen,
then back to login. Here is the output to daemon.log:
gdm[23126]: gdm_slave_
21 matches
Mail list logo
