Description of problem: With the new kernel I can't run "Startx", mount and some other commands give me a "bad address" error. Startx gives an error about missing screens? Xinit and StartXFCE work but then NetworkManager does not work. Version-Release number of selected component (if applicable): 4.17.3-100.fc27.x86_64 How reproducible: Allways Steps to Reproduce: 1. Start the new Kernal, try and "mount" a drive and you will get "bad address", also try and run StartX from a TTY(without X running automatically) 2. 3. Actual results: As I said above. Expected results: It works Additional info:
I've updated some of the dropdowns.
I've read somewhere that sometimes you have weird issues like that if you have a bad Busybox(which is part of Initframs, is that same package?)
Oops! Accidently changed the dropdowns again?
Can you share error logs for each of the problems you are reporting?
Created attachment 1457907 [details] Wrong log.
Would the others things: NetworkManager, mount be in the journal?
That was the wrong one. I can't find the Xorg log with the error in it, but I did see it at the time? I'll get it for you when you tell me where to find the others.
(In reply to jamie from comment #7) > That was the wrong one. I can't find the Xorg log with the error in it, but > I did see it at the time? I'll get it for you when you tell me where to find > the others. If I can, it's hard cause I don't have working internet when using that kernel.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
Still happens on newer kernels :(.
Fixed in 4.18.18-100.fc27.x86_64.