Bug 914885 - Problems after failed upgrade 17 > 18
Summary: Problems after failed upgrade 17 > 18
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 18
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-23 07:06 UTC by Wolfram Wagner
Modified: 2014-02-05 19:25 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:25:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
xorg log with nvidia installed (20.73 KB, text/x-log)
2013-02-24 11:22 UTC, Wolfram Wagner
no flags Details
xorg log withOUT nvidia installed (20.78 KB, text/x-log)
2013-02-24 11:23 UTC, Wolfram Wagner
no flags Details

Description Wolfram Wagner 2013-02-23 07:06:01 UTC
Description of problem:
I need help after a failed fedup run to upgrade 17 to 18.
fedup did its work before installation, after reboot it did work for a long time rebooted and came back into 17 but without X. I managed to fix the issue by using yum distrosynch and fixing package conflicts manually.

Now I am back to an 90% running system. I miss only a few important features:
- Changing a user does not work sometimes (logoff current user => the login screen does not come, it seems as if X does not restart)
- Shutdown does hang sometimes and gives me dumps showing the CPU and the stack of which programs are running

Which packages contain these features? I guess, that these issues are caused by the failed update.
What can I do? What do you need to help me?

Comment 1 Wolfram Wagner 2013-02-23 09:25:27 UTC
I have made some checks. I can change the users several times, but finally it fails by sending me to the boot messages screen. (CTRL+ALT+F1). 

My messages file says frequently:
WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors

The x logs have two errors:
Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
This one comes up, when I try to start up a session with my plugable USB thin client. And 
Unable to open evdev device "/dev/input/event#" (# = [3-7])

Maybe I can change users as long as I have available "slots".

At the end I have to change to runlevel 1 and back to 5 to be able to login again.

This morning I have reinstalled all drivers, the x server and much more. This did not help.

Comment 2 Kamil Dudka 2013-02-23 10:07:50 UTC
The basesystem package is just a meta-package that has nothing to do with your issue.  I am switching the component to xorg-x11-server...

Comment 3 Wolfram Wagner 2013-02-24 11:12:07 UTC
I have digged more into the deep: although the thin client is using modesetting, fbdev,udev it is trying to use the nvidia driver. It fails to load the GLX extensions and displays the distortions (remainders of paint actions, mainly thin horizontal stripes about 30 dots long and traces of the mouse pointer).
When I remove the nvidia driver, the distorsions are gone, but the refresh rate is unacceptable slow. (beside, I need nvidia for my other applications)

In the case without nvidia rpms installed, I have no error messages in the xorg log file.

Comment 4 Wolfram Wagner 2013-02-24 11:22:05 UTC
Created attachment 701983 [details]
xorg log with nvidia installed

this is the case when the distortions appear

Comment 5 Wolfram Wagner 2013-02-24 11:23:19 UTC
Created attachment 701984 [details]
xorg log withOUT nvidia installed

This is the case without nvidia installed on the system. No distortions but SLOW

Comment 6 Wolfram Wagner 2013-03-23 16:03:02 UTC
The issue is still there...

Comment 7 Fedora End Of Life 2013-12-21 11:38:56 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2014-02-05 19:25:26 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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