When I login a text screen. Instead of the graphic one
Nvidia- or ATI-Driver installed?
Install it new.
And why did you start a new thread now instead of continuing in yesterday’s one? https://forums.opensuse.org/showthread.php/517968-I-don-t-have-xdm-file
It’s nvidia but I don’t know how to install it new without install my Linux again.
I started a new thread because I’m not really sure if the xdm file has something to do with this
Well, how did you install the nvidia driver in the first place? Do the same again.
You can do that in text mode, or you can also uninstall the driver (“nvidia-installer --uninstall” I think) and you should get a login screen.
But AFAIK, the current version doesn’t work with the latest kernel 4.6. You’d need an older one, or patch it.
Though as you have this problem a few days already, you probably didn’t update the kernel to 4.6 yet anyway…
Anyway, there are reasons why using Tumbleweed is not recommended if you rely on 3rd party drivers, unless you know what you are doing.
You definitely should at least know how to reinstall the driver (or recompile the kernel module) in that case, if you don’t, Tumbleweed is not for you.
I started a new thread because I’m not really sure if the xdm file has something to do with this
Yes, it is unrelated to /etc/init.d/xdm missing, as already explained this file doesn’t exist at all any more since 13.2.
But discussing the same problem (i.e. your graphical login not working) in two different threads only created chaos and wastes everybody’s time.
As we already started to analyze the problem in the other thread, it would have been better to just continue there IMHO.
But ok…
I’m very sorry to create this thread into 2 threads and some people wasting time. Anyway, I don’t know how to install the graphic mode. I mean it’s not clear for me.
You cannot and don’t have to “install the graphic mode”.
You should provide answers to the questions I asked you in the other thread so that we can find out why it is not starting.
I.e:
What’s the output of “sudo systemctl status display-manager” exactly?
Does “systemctl restart display-manager” bring up a graphical session?
Does “startx” (as root) work? If not, what errors do you get?
And maybe uninstalling or reinstalling the nvidia driver would help.
startx didn’t works.
Start with:
xauth file /root/.perversity.1779 does not exist. And then another text that I can’t copy and paste here because I’m writing from kindle fire.
Once again I’m sorry to open 2 threads at once. Won’t happen again. I promise.
I meant that in root login and type
startx
Returns
xauth: file /root/.serverauth.1779 does not exist
Anybody knows how I can use yahoo or gmail to attach whole text output of startx using lynx or some another way to do it
Hi
Install susepaste, as long as you have internet you can upload and post the link.
eg, for tumbleweed;
zypper in susepaste
exit
cat ~/.local/share/xorg/Xorg.0.log | susepaste -t "Zorg.log" -n "username" -e "0"
Pasted as:
http://susepaste.org/25258172
http://paste.opensuse.org/25258172
There are quite some problems in there, and not even related to the graphics driver…
Current Operating System: Linux agunet 4.2.1-1-desktop #1 SMP PREEMPT Fri Sep 25 08:21:54 UTC 2015 (6996a42) x86_64
Why are you still using Kernel 4.2.1?
The current one in Tumbleweed is 4.6.0…
splashqml: relocation error: /usr/lib64/libQt5Svg.so.5: symbol _ZTIN4QCss13StyleSelectorE, version Qt_5 not defined in file libQt5Gui.so.5 with link time reference
…
klauncher: relocation error: /usr/lib64/libQt5Svg.so.5: symbol _ZTIN4QCss13StyleSelectorE, version Qt_5 not defined in file libQt5Gui.so.5 with link time reference
…
/usr/bin/ksmserver: relocation error: /usr/lib64/libQt5PrintSupport.so.5: symbol _ZTI10QPdfEngine, version Qt_5 not defined in file libQt5Gui.so.5 with link time reference
You have a mixture of Qt5 packages in different versions installed.
X: symbol lookup error: /usr/lib64/libLLVMAMDGPUCodeGen.so.3.8: undefined symbol: _ZN4llvm19MachinePassRegistry6RemoveEPNS_23MachinePassRegistryNodeE
Another incompatible package mix.
I would suggest to run “zypper dup”, maybe that will bring your system in a consistent state again.
And please post your repo list:
zypper lr -d
>The current one in Tumbleweed is 4.6.0…
And as someone said earlier in the thread, the nvidia binary drivers WILL NOT install onto this kernel, but I can confirm that Nouveau works great (better than previously ever worked for me with my GEFORCE). I can’t find where the OP lists his video card, but if it’s nvidia, then Nouveau should handle it.
If the OP had previously had the binary nvidia drivers, they will have to clean them off, and remove the /etc/X11/xorg.conf file, and make sure nothing is sitting in their /etc/modeprobe.d/* files that would block (blacklist) nouveau kernel module.
W
Hi
There is a patch available for older cards that need the 340.96 driver to use the 4.6 kernel. See [opensuse-factory] Patch for NVIDIA driver on kernel 4.6 - openSUSE Factory - openSUSE Mailing Lists
This problem brings me lot of head ache and because of that I decided to install linux again
I just did a fresh install of the x64/Network installation, chose KDE during installation on a virtual machine inside VirtualBox and get the same issue. Once I boot into the system, I get a single-user:ish login prompt.
Sysctl status display-manager yields the following output:
http://s33.postimg.org/x6bw5791b/Tumbleweed_Display_Mgr.png
Trying to startx yields the error entry AddScreen/ScreenInit failed for driver 0 (VBoxVideo).
I very much doubt that it really is the same issue… 
Trying to startx yields the error entry AddScreen/ScreenInit failed for driver 0 (VBoxVideo).
You can only run startx as root.
I would suggest these things:
- try to disable 3D acceleration in VirtualBox’s guest settings, there were problems with this in the past and you don’t specify which VirtualBox version you are using anyway…
- sddm is crashing in your case. Try to set “xdm” as DISPLAYMANAGER in /etc/sysconfig/displaymanager, and you should get a login screen at least. Would be interesting to see whether Plasma 5 starts or not…
Also, which snapshot did you install?
cat /etc/os-release
There were severe problems (which also could cause the graphical session not to start because of insufficient permissions) in 20160605, running this should fix them:
sudo pam-config -a --systemd
I wanted to post a separate thread about this issue but then I saw several threads that appears to be discussing a similar issue. If my issue is something else then I apologize for hijacking it.
I use VirtualBox 4.3.36 as I don’t believe VBox 5 is mature enough. All 3D acceleration was disabled during testing and I was running ‘startx’ as root. The output of ‘/etc/os-release’ shows that it’s “openSUSE Tumbleweed (20160609) (x86_64)”.
The pam-config command solved the issue and everything works. But the keymap is wrong even though I did set the locale during installation.
The recent several threads about Xorg not starting were about problems with the nvidia driver packages in the nvidia repo.
A VirtualBox guest does of course not use the nvidia driver (if you install it in the guest, it may break the guest system though), and the repo does not even exist for Tumbleweed.
The problem of the OP was something different anyway.
It apparently was a completely messed up system, he had at least a mix of Qt5 packages in different versions, as you can see in my previous reply here.
There were a few threads about the pam-config problem too, this was a general problem in Tumbleweed 20160605.
It normally did not cause the GUI failing to start completely (unless you use gdm), the situation might be different in VirtualBox though.
I use VirtualBox 4.3.36 as I don’t believe VBox 5 is mature enough. All 3D acceleration was disabled during testing and I was running ‘startx’ as root.
Well, the 3D acceleration problems were in fact present in 4.3.
I could even reproduce them by just installing Tumbleweed…
Though they did not cause a problem with sddm (i.e. the GUI not starting at all), they manifest themselves via graphical problems in Plasma5 (e.g. panels missing and the application menu not appearing)
I think that’s even fixed in v5 though, and v5 should actually be mature enough.
We’re at 5.0.20 already, and I didn’t have any problems with earlier 5.0.x versions either.
Though if you’re more confident with 4.3, it’s fine to stick with that too I suppose.
The output of ‘/etc/os-release’ shows that it’s “openSUSE Tumbleweed (20160609) (x86_64)”.
Ok, the pam problem should be fixed there, but if you did have the faulty pam-config package installed, an update will not solve the problems.
The pam-config command solved the issue and everything works.
But the keymap is wrong even though I did set the locale during installation.
Please open a new thread for this.
Although I think this should work in general.
It might be dependent on the actual keyboard layout though.
And just to be clear: setting the locale has no influence on the keyboard layout, you need to set the keyboard layout appropriately.
You could try to set it to something else in YaST->System->System Keyboard Layout, press on OK, and set it back again.
And also note that the desktop settings might override the system keyboard layout, so have a look there as well.