Bug 702182 - [Calistoga] X login fails and returns to login screen
Summary: [Calistoga] X login fails and returns to login screen
Keywords:
Status: CLOSED DUPLICATE of bug 698237
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 01:12 UTC by Will Kemp
Modified: 2018-04-11 11:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-06 12:16:57 UTC
Type: ---


Attachments (Terms of Use)
Xorg.0.log (28.15 KB, text/plain)
2011-05-05 01:12 UTC, Will Kemp
no flags Details

Description Will Kemp 2011-05-05 01:12:24 UTC
Created attachment 496953 [details]
Xorg.0.log

Description of problem:

After a large update about 11.30pm UTC, 4th May, i'm unable to log in using X. I click on my username, enter my password, and after 20 seconds or so of blank screen, it returns to the login screen. I'm not entirely sure where to look in the logs for clues, but the following is the last line in .xsession-errors:

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

And i've attached the Xorg.0.log.

Comment 1 Will Kemp 2011-05-05 13:36:13 UTC
After a bit more investigation, i've discovered that somehow my system seems to have updated itself to F16. I suspect this was mainly due to operator malfunction and i may have changed something in the add/remove software app that i didn't mean to. So this probably really isn't an F15 bug after all.

For the first time in the 16 years i've been running Linux, i did a re-install to fix the problem. The system seemed to be a jumble of F15 and F16 packages and i couldn't see any easy way to untangle it without re-installing.

Comment 2 Matěj Cepl 2011-05-06 12:16:57 UTC
(In reply to comment #1)
> For the first time in the 16 years i've been running Linux, i did a re-install
> to fix the problem. The system seemed to be a jumble of F15 and F16 packages
> and i couldn't see any easy way to untangle it without re-installing.

It is probably too late, but if not then take a look at

yum distro-sync

in yum(8).

Anyway, concerning this bug, I close it as a duplicate of bug 698237.

*** This bug has been marked as a duplicate of bug 698237 ***


Note You need to log in before you can comment on or make changes to this bug.