Reason: libthread_db.so.1 problem
KDE message:
“The appropriate fix has been submitted to openSUSE Tumbleweed and Leap: it’s not a KDE software bug, but a PulseAudio one. See http://bugzilla.opensuse.org/show_bug.cgi?id=950487 for details.”
If I delete pulseaudio I can not get login screen… >:)
Any idea?
Developer message:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library “/lib64/libthread_db.so.1”.
[Current thread is 1 (Thread 0x7fd3f655d900 (LWP 5633))]
Thread 6 (Thread 0x7fd3d3916700 (LWP 5648)):
#0 0x00007fd3ef286cfc in __lll_lock_wait () at /lib64/libpthread.so.0
#1 0x00007fd3ef280bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2 0x00007fd3eb532fcc in () at /usr/lib64/libGL.so.1
#3 0x00007fd3eb537b11 in () at /usr/lib64/libGL.so.1
#4 0x00007fd3eb537fbb in () at /usr/lib64/libGL.so.1
#5 0x00007fd3e7160ff0 in () at /usr/lib64/tls/libnvidia-tls.so.352.63
#6 0x00007fd3ec155210 in () at /usr/lib64/libglib-2.0.so.0
#7 0x00007fd3ec112d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#8 0x00007fd3ec113208 in () at /usr/lib64/libglib-2.0.so.0
#9 0x00007fd3ec11336c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#10 0x00007fd3f039d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#11 0x00007fd3f034763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#12 0x00007fd3f0173b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#13 0x00007fd3f34749a5 in () at /usr/lib64/libQt5Qml.so.5
#14 0x00007fd3f017894f in () at /usr/lib64/libQt5Core.so.5
#15 0x00007fd3ef27e4a4 in start_thread () at /lib64/libpthread.so.0
#16 0x00007fd3efa88bdd in clone () at /lib64/libc.so.6
Thread 5 (Thread 0x7fd3c7cae700 (LWP 5649)):
#0 0x00007fd3ef286d9a in __lll_unlock_wake () at /lib64/libpthread.so.0
#1 0x00007fd3ef282121 in __pthread_mutex_unlock_usercnt () at /lib64/libpthread.so.0
#2 0x00007fd3eb532ce5 in () at /usr/lib64/libGL.so.1
#3 0x00007fd3eb538018 in () at /usr/lib64/libGL.so.1
#4 0x00007fd3e7161001 in () at /usr/lib64/tls/libnvidia-tls.so.352.63
#5 0x00007fd3ec155210 in () at /usr/lib64/libglib-2.0.so.0
#6 0x00007fd3ec112d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#7 0x00007fd3ec113208 in () at /usr/lib64/libglib-2.0.so.0
#8 0x00007fd3ec11336c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#9 0x00007fd3f039d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#10 0x00007fd3f034763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#11 0x00007fd3f0173b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#12 0x00007fd3f34749a5 in () at /usr/lib64/libQt5Qml.so.5
#13 0x00007fd3f017894f in () at /usr/lib64/libQt5Core.so.5
#14 0x00007fd3ef27e4a4 in start_thread () at /lib64/libpthread.so.0
#15 0x00007fd3efa88bdd in clone () at /lib64/libc.so.6
Thread 4 (Thread 0x7fd3c641e700 (LWP 5650)):
#0 0x00007fd3ef286cfc in __lll_lock_wait () at /lib64/libpthread.so.0
#1 0x00007fd3ef280bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0
#2 0x00007fd3eb532fcc in () at /usr/lib64/libGL.so.1
#3 0x00007fd3eb537b11 in () at /usr/lib64/libGL.so.1
#4 0x00007fd3eb537fbb in () at /usr/lib64/libGL.so.1
#5 0x00007fd3e7160ff0 in () at /usr/lib64/tls/libnvidia-tls.so.352.63
#6 0x00007fd3ec155210 in () at /usr/lib64/libglib-2.0.so.0
#7 0x00007fd3ec112d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#8 0x00007fd3ec113208 in () at /usr/lib64/libglib-2.0.so.0
#9 0x00007fd3ec11336c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#10 0x00007fd3f039d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#11 0x00007fd3f034763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#12 0x00007fd3f0173b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#13 0x00007fd3f34749a5 in () at /usr/lib64/libQt5Qml.so.5
#14 0x00007fd3f017894f in () at /usr/lib64/libQt5Core.so.5
#15 0x00007fd3ef27e4a4 in start_thread () at /lib64/libpthread.so.0
#16 0x00007fd3efa88bdd in clone () at /lib64/libc.so.6
Thread 3 (Thread 0x7fd3c4a4e700 (LWP 5658)):
#0 0x00007fd3ef28407f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1 0x00007fd3f5c4ea84 in () at /usr/lib64/libQt5Script.so.5
#2 0x00007fd3f5c4eac9 in () at /usr/lib64/libQt5Script.so.5
#3 0x00007fd3ef27e4a4 in start_thread () at /lib64/libpthread.so.0
#4 0x00007fd3efa88bdd in clone () at /lib64/libc.so.6
Thread 2 (Thread 0x7fd335d76700 (LWP 5659)):
#0 0x00007fd3ec1564d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1 0x00007fd3ec113376 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#2 0x00007fd3f039d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#3 0x00007fd3f034763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007fd3f0173b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5 0x00007fd3f4009e42 in () at /usr/lib64/libQt5Quick.so.5
#6 0x00007fd3f017894f in () at /usr/lib64/libQt5Core.so.5
#7 0x00007fd3ef27e4a4 in start_thread () at /lib64/libpthread.so.0
#8 0x00007fd3efa88bdd in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7fd3f655d900 (LWP 5633)):
[KCrash Handler]
#6 0x00007fd3ef9d3d38 in raise () at /lib64/libc.so.6
#7 0x00007fd3ef9d518a in abort () at /lib64/libc.so.6
#8 0x00007fd3f016682e in () at /usr/lib64/libQt5Core.so.5
#9 0x00007fd3f40735c4 in () at /usr/lib64/libQt5Quick.so.5
#10 0x00007fd3f4074545 in () at /usr/lib64/libQt5Quick.so.5
#11 0x00007fd3f407544e in () at /usr/lib64/libQt5Quick.so.5
#12 0x00007fd3f0898c3b in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5
#13 0x00007fd3f40ac621 in QQuickWindow::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5
#14 0x0000000000442316 in DesktopView::event(QEvent*) ()
#15 0x00007fd3f16d08cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#16 0x00007fd3f16d59d6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#17 0x00007fd3f0349cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fd3f08916e4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib64/libQt5Gui.so.5
#19 0x00007fd3f089237d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5
#20 0x00007fd3f08779f8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Gui.so.5
#21 0x00007fd3e07d9ed0 in () at /usr/lib64/libQt5XcbQpa.so.5
#22 0x00007fd3ec113097 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fd3ec1132c8 in () at /usr/lib64/libglib-2.0.so.0
#24 0x00007fd3ec11336c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#25 0x00007fd3f039d50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007fd3f034763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007fd3f034f2fd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#28 0x0000000000436571 in main ()
Additional information:
I had a working 13.2 with a working KDE desktop environment.
I made zypper dup (to Tumbleweed), the system let me to do that by repository change.
The result: I have a Tumbleweed with non-working KDE environment (neither KDE4 and nor Plasma5), but there are several other working desktops.
I sent a bug report to the KDE, they said that they sent a fix message to Leap and Tumbleweed developers before.
I made a sign about this problem in an another opensuse thread also.
I performed all Tumbleweed upgrades.
Any idea?
Wait for the fix and don’t perform further Tumbleweed upgrades ? 
Yes… rotfl!
But I will like Tumbleweed, I think. Just the errors at the beginning… :O, and some skeletons in the cupboard.
And the developer guys re-invented minimum half of the system, as I see… (system flows and security).
No.
libpthread_db is some low-level system library and definitely not the problem.
KDE message:
“The appropriate fix has been submitted to openSUSE Tumbleweed and Leap: it’s not a KDE software bug, but a PulseAudio one. See 950487 – kded5, kdeinit and kmix segfault when I log in for details.”
This is fixed since months. It was a problem after a pulseaudio update during the Leap Beta phase in October and got fixed shortly afterwards as you can see in that bug report.
Your problem is something else.
If I delete pulseaudio I can not get login screen… >:)
And how did you do that?
The login screen should not need pulseaudio. Which one are you actually using?
As a side-note, I don’t have pulseaudio installed here and everything works fine including all login screens I have installed (kdm, gdm, xdm, and sddm). I’m on 13.2 though.
This is a crash in QtQuick and likely a graphics driver problem.
Is your nvidia installation actually working?
Please install “Mesa-demo-x” and post the output of “glxinfo | grep render”.
There is a known bug in the nvidia driver at the moment:
https://bugzilla.opensuse.org/show_bug.cgi?id=957061
Maybe try to install the latest beta version (361.18) that should have a fix.
PS: you could also try to disable PulseAudio in YaST->Hardware->Audio->Other->PulseAudio Configuration if you cannot uninstall it to rule out that that’s causing the problem.
It is a REMOTE machine.
Xlib: extension “GLX” missing on display “xxxxxx.xxx.xx:2.0”
repeated
Could not find RGB GLX Visual or fbconfig
I do not know that the X server has +iglx feature… I would try the KDE with a home script “LIBGL_ALWAYS_ENABLED=1” but crashing already at the start… and I do not know other solution in other desktops to visualize the feature from remote.
A will try the beta version.
I would not disturb the Pulseaudio if it does not contain the problem…
I will try the newest beta. 352.63 is the latest driver on Official Drivers | NVIDIA; for Geforce GT610
Klick on “Beta and Older Drivers” and you will get the whole list.
Remote in what regard?
Do you connect via VNC?
Then Plasma5 cannot work with the nvidia driver is installed. nvidia replaces some system libraries with their own incompatible versions, this breaks Mesa completely and expecially its software OpenGL renderer. NVidia’s hardware OpenGL support obviously doesn’t work over VNC…
- I can not decide CLEARLY what driver is loaded AND working. The Xorg.0.log is error-free. All desktops are working except from the KDE-related others.
I installed nvidia driver on hard way from 352.63. I will try the newest beta. 352.63 is the latest driver on Official Drivers | NVIDIA; for Geforce GT610
Mesa demo already installed, the result:
Xlib: extension “GLX” missing on display “xxxxxx.xxx.xx:2.0”
repeated
Could not find RGB GLX Visual or fbconfig
So, there you have your problem.
OpenGL/GLX is not working, but Plasma5 requires it.
Other desktops don’t need OpenGL, so they do work. GNOME e.g. won’t work either though.
The only way I know of to get Plasma5 (or other OpenGL applications) working, would be to uninstall the nvidia driver and use nouveau.
It might help to force Plasma5 (or Qt5 rather) to use software rendering:
http://lists.opensuse.org/opensuse-kde/2015-11/msg00037.htmlBut I fear the nvidia driver will still be in the way…
With the newest beta driver the result is the same.
I use passworded VNC.
I MUST use GLX enabled nividia driver, because some applications demand it.
Why could I use nouveau driver? It is not a videocard… two drivers are less than one…
If an operating system can not manage seamlessly a key device which owns the half of the videocard market, it is a big problem for the system…
I use passworded VNC.
I MUST use GLX enabled nividia driver, because some applications demand it.
Why could I use nouveau driver? It is not a videocard… two drivers are less than one…
If an operating system can not manage seamlessly a key device which owns the half of the videocard market, it is a big problem for the system…
“Then Plasma5 cannot work with the nvidia driver is installed. nvidia replaces some system libraries with their own incompatible versions, this breaks Mesa completely and expecially its software OpenGL renderer.”
Why? It is YOUR problem, YOU DID IT. If you make a standalone driver and library for nvidia, it will work. DO NOT MIX the libraries with same functions. The old golden times has gone, the programs are more secure and error free with their standalone independent libraries… there are eligible disk spaces. Who is the Mesa, why can I get it at all?
Then I can throw out my videocard?
Well, then forget about Plasma5, over VNC at least.
Why could I use nouveau driver? It is not a videocard… two drivers are less than one…
???
What is it then if not a “videocard”?
And what do you mean with “two drivers are less than one”?
If you uninstall nvidia (which you have to do to use nouveau), you only have one (actually you probably still have a dozen installed though… 
)
If an operating system can not manage seamlessly a key device which owns the half of the videocard market, it is a big problem for the system…
The system can manage your nvidia card.
But the nvidia driver breaks the system.
Why? It is YOUR problem, YOU DID IT.
Sorry, but what did I do?
If you make a standalone driver and library for nvidia, it will work.
DO NOT MIX the libraries with same functions. The old golden times has gone, the programs are more secure and error free with their standalone independent libraries… there are eligible disk spaces.
???
It’s the proprietary nvidia driver (created by nvidia themselves) that replaces Mesa’s and Xorg’s libraries, not the other way round.
Who is the Mesa, why can I get it at all?
Mesa is an open source OpenGL implementation, and installed by default.
Then I can throw out my videocard?
No, use nouveau, or use a different desktop over VNC. Probably a good idea anyway, although Plasma5 did work acceptable when I last tried it over VNC a few months ago (host: an old intel system, client: an even older one with an NVidida Riva TNT2 card, using nouveau).
Or switch to AMD or intel. They at least actively support the open source driver development.
“???
What is it then if not a “videocard”?
And what do you mean with “two drivers are less than one”?
If you uninstall nvidia (which you have to do to use nouveau), you only have one (actually you probably still have a dozen installed though… 
)”
Nouveau is a synthetic driver, not the hardware vendors make it.
FORGET nouveau as I said before. Nvidia a MUST in this case.
If you buy a videocard usually uses the vendor’s driver.
Xorg mixing the noveau and nvidia features. The result untrustable. Lots of complaints during years: no solution.
“The system can manage your nvidia card.
But the nvidia driver breaks the system.”
NO. System can not enable to use nvidia card’s features. NEVER, NEVER, NEVER the hardware (if works well) responsible if the system cannot manage it.
“Sorry, but what did I do?”
The SuSE developers. It is unbelievable for me that they can not solve for years so problem as two indifferent programs write to same directory and confuse it.
“???
It’s the proprietary nvidia driver (created by nvidia themselves) that replaces Mesa’s and Xorg’s libraries, not the other way round.”
IT is the problem, really.
“Mesa is an open source OpenGL implementation, and installed by default.”
First come, first shot?
“No, use nouveau, or use a different desktop over VNC. Probably a good idea anyway, although Plasma5 did work acceptable when I last tried it over VNC a few months ago (host: an old intel system, client: an even older one with an NVidida Riva TNT2 card, using nouveau).
Or switch to AMD or intel. They at least actively support the open source driver development.”
It should work with KDE by a shell script as the KDE developers said, if the X server can manage it (not sure).
Nouveau NOT an option, do you understand? I can not rewrite the applications…
THEN at all:
The aim: using WHATEVER desktop remotely with OpenGL nvidia support.
The problem: a hardware vendor built a software component into their product. This occurrence can be repeated in other areas in the future…
What is your proposal: desktop, script, setup?
Then blame the “hardware vendors” for not providing an open source driver, not supporting nouveau’s development, or breaking the system when installing their driver.
And nouveau is not “synthetic”. It’s a “real” driver for nvidia cards with OpenGL/3D support, it even supports a lot of older cards that are not supported at all by the “official” driver any more.
But, it has been (had to be) created by reverse-engineering the closed-source proprietary driver, and therefore does still have its problems.
But again, you should blame NVidia for that.
FORGET nouveau as I said before. Nvidia a MUST in this case.
I know that you did. But again, you won’t be able to run Plasma 5 over VNC in this case.
The only two options I see is uninstall nvidia or use a different desktop.
If you buy a videocard usually uses the vendor’s driver.
Not necessary with AMD, the open source radeon driver is on par with the proprietary one, and sometimes even better.
It is actively supported by AMD since years.
And intel only has an open source driver anyway.
Xorg mixing the noveau and nvidia features.
Xorg?
You are just talking non-sense.
Again, nvidia replaces parts of Xorg and Mesa, and breaks the system.
The result untrustable. Lots of complaints during years: no solution.
Again, blame NVidia.
The solution is to only use open source drivers, this is trustable and works since years (if your hardware is supported).
NO. System can not enable to use nvidia card’s features. NEVER, NEVER, NEVER the hardware (if works well) responsible if the system cannot manage it.
No, but the driver is responsible.
And your nvidia driver breaks the system’s OpenGL support by replacing the system’s files. How is this the fault of the system?
And don’t forget that you are talking about VNC here. You just cannot use your nvidia card’s features over VNC, that’s one part of the problem, inherent to what VNC is and how it works.
The SuSE developers. It is unbelievable for me that they can not solve for years so problem as two indifferent programs write to same directory and confuse it.
The SuSE developers didn’t do this either. Except trying to improve the situation, and the open source drivers.
Again, it’s nvidia that create a closed-source, proprietary, binary driver blob, which forces you to break your open source system when installing it.
IT is the problem, really.
Yes, the nvidia driver is the problem, really.
First come, first shot?
What do you mean with that?
Mesa exists since 1993.
And it’s the only working software OpenGL solution (for Linux) that I know. And it also provides the hardware 3D part for other (open source) drivers like intel, nouveau and radeon, so it is vital to have in a Linux distribution.
See here e.g. for more information: Mesa (computer graphics) - Wikipedia
Ask nvidia to provide a software renderer too for their proprietary solution, and it might fix your problem.
It should work with KDE by a shell script as the KDE developers said, if the X server can manage it (not sure).
Well, the main problem here is that installing the driver overwrites those system files, no script can work around that.
It should be possible to switch to nouveau via a script with some heavy trickery (installing either Mesa’s and Xorg’s libs or the nvidia one’s to a different directory, and making them available to the system via LD_LIBRARY_PATH, something that openSUSE’s nvidia packages do btw).
Nothing that can be done on a distribution level though.
A side-note: you keep mentioning “messages from KDE”, and what “KDE developers said”, could you please provide links as well?
The “KDE message” in your first post was clearly not applicable to your problem.
Nouveau NOT an option, do you understand? I can not rewrite the applications…
I do understand you, but I cannot help you.
Using Plasma5 over VNC is no option, if nvidia is in use or installed. Period.
Anyway, you are barking up the wrong tree here. This is a community forum, where users try to help other users in their spare time.
This is not a professional support forum run by the nvidia developers, or any other developers either.
Dear wolft323,
thank you for your support.
Concentrate only for the working plasma5 and KDE environment WITHOUT nouveau, none of them working now. Forget the ultimate aim.
…
It is is working, I will make the next steps (indirect script and X server +iglx).
And looking for a working other desktop solution also.
Best regards
venember
So it is not even working locally now, without VNC in the game?
Then there’s likely something wrong with your nvidia installation, i.e. the driver not fully working.
Can you please post the /var/log/Xorg.0.log?
Btw, I see you opened a thread in the KDE forums as well:
https://forum.kde.org/viewtopic.php?f=225&t=130439
Do you actually have this script that sets LIBGL_ALWAYS_INDIRECT=1 on your system now? Or the “+iglx” X server parameter in kdmrc?
Then try to remove it again, I’d say.
Plasma5 should definitely work and run stable with the propietary nvidia driver locally.
And a side-note: luebking is one of the main kwin developers. If he cannot help you, nobody else can probably.
The log:
35346.148]
X.Org X Server 1.18.0
Release Date: 2015-11-09
35346.148] X Protocol Version 11, Revision 0
35346.148] Build Operating System: openSUSE SUSE LINUX
35346.148] Current Operating System: Linux paradigm 4.3.3-6-default #1 SMP PREEMPT Fri Jan 8 18:34:17 UTC 2016 (da39cbd) x86_64
35346.148] Kernel command line: root=/dev/sdb2 splash=silent audit=0 nomodeset
35346.148] Build Date: 12 January 2016 04:20:57PM
35346.148]
35346.148] Current version of pixman: 0.33.6
35346.148] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
35346.148] Markers: (–) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
35346.148] (==) Log file: “/var/log/Xorg.0.log”, Time: Thu Jan 14 21:33:34 2016
35346.148] (==) Using config file: “/etc/X11/xorg.conf”
35346.148] (==) Using config directory: “/etc/X11/xorg.conf.d”
35346.148] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
35346.249] (==) No Layout section. Using the first Screen section.
35346.249] (==) No screen section available. Using defaults.
35346.249] () |–>Screen “Default Screen Section” (0)
35346.249] () | |–>Monitor “<default monitor>”
35346.250] (==) No device specified for screen “Default Screen Section”.
Using the first device section listed.
35346.250] () | |–>Device “nvidia”
35346.250] (==) No monitor specified for screen “Default Screen Section”.
Using a default monitor configuration.
35346.250] (==) Automatically adding devices
35346.250] (==) Automatically enabling devices
35346.250] (==) Automatically adding GPU devices
35346.250] (==) Max clients allowed: 256, resource mask: 0x1fffff
35346.250] (WW) The directory “/usr/share/fonts/misc/sgi” does not exist.
35346.250] Entry deleted from font path.
35346.250] (==) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/ghostscript/,
/usr/share/fonts/cyrillic:unscaled,
/usr/share/fonts/truetype/,
built-ins
35346.250] (==) ModulePath set to “/usr/lib64/xorg/modules”
35346.250] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
35346.250] (II) Loader magic: 0x813d00
35346.250] (II) Module ABI versions:
35346.250] X.Org ANSI C Emulation: 0.4
35346.250] X.Org Video Driver: 20.0
35346.250] X.Org XInput driver : 22.1
35346.250] X.Org Server Extension : 9.0
35346.251] (++) using VT number 7
35346.251] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
35346.252] (II) xfree86: Adding drm device (/dev/dri/card0)
35346.254] (–) PCI:*(0:1:0:0) 10de:104a:1458:3545 rev 161, Mem @ 0xfd000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x???/524288
35346.254] (II) LoadModule: “glx”
35346.255] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
35346.272] (II) Module glx: vendor=“X.Org Foundation”
35346.272] compiled for 1.18.0, module version = 1.0.0
35346.272] ABI class: X.Org Server Extension, version 9.0
35346.272] (==) AIGLX enabled
35346.272] (II) LoadModule: “nvidia”
35346.272] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
35346.279] (II) Module nvidia: vendor=“NVIDIA Corporation”
35346.279] compiled for 4.0.2, module version = 1.0.0
35346.279] Module class: X.Org Video Driver
35346.279] (II) NVIDIA dlloader X Driver 361.18 Sat Jan 9 20:20:22 PST 2016
35346.279] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
35346.286] (II) Loading sub module “fb”
35346.286] (II) LoadModule: “fb”
35346.286] (II) Loading /usr/lib64/xorg/modules/libfb.so
35346.294] (II) Module fb: vendor=“X.Org Foundation”
35346.294] compiled for 1.18.0, module version = 1.0.0
35346.294] ABI class: X.Org ANSI C Emulation, version 0.4
35346.294] (II) Loading sub module “wfb”
35346.294] (II) LoadModule: “wfb”
35346.294] (II) Loading /usr/lib64/xorg/modules/libwfb.so
35346.306] (II) Module wfb: vendor=“X.Org Foundation”
35346.306] compiled for 1.18.0, module version = 1.0.0
35346.306] ABI class: X.Org ANSI C Emulation, version 0.4
35346.306] (II) Loading sub module “ramdac”
35346.306] (II) LoadModule: “ramdac”
35346.306] (II) Module “ramdac” already built-in
35346.307] (II) NVIDIA(0): Creating default Display subsection in Screen section
“Default Screen Section” for depth/fbbpp 24/32
35346.307] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
35346.307] (==) NVIDIA(0): RGB weight 888
35346.307] (==) NVIDIA(0): Default visual is TrueColor
35346.307] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
35346.307] () NVIDIA(0): Option “RenderAccel” “true”
35346.307] () NVIDIA(0): Option “AllowIndirectGLXProtocol” “true”
35346.307] () NVIDIA(0): Option “AllowEmptyInitialConfiguration” “true”
35346.307] () NVIDIA(0): Enabling RENDER acceleration
35346.307] () NVIDIA(0): Enabling 2D acceleration
35346.308] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
35346.308] (EE) NVIDIA(0): log file that the GLX module has been loaded in your X
35346.308] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
35346.308] (EE) NVIDIA(0): you continue to encounter problems, Please try
35346.308] (EE) NVIDIA(0): reinstalling the NVIDIA driver.
35346.826] (–) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
35346.826] (–) NVIDIA(0): CRT-0 (boot)
35346.826] (–) NVIDIA(0): CRT-1
35346.826] (–) NVIDIA(0): DFP-0
35346.826] (–) NVIDIA(0): DFP-1
35346.839] (–) NVIDIA(0): CRT-0: disconnected
35346.839] (–) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
35346.839] (–) NVIDIA(0):
35346.840] (–) NVIDIA(0): CRT-1: disconnected
35346.840] (–) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock
35346.840] (–) NVIDIA(0):
35346.853] (–) NVIDIA(0): DFP-0: disconnected
35346.853] (–) NVIDIA(0): DFP-0: Internal TMDS
35346.853] (–) NVIDIA(0): DFP-0: 330.0 MHz maximum pixel clock
35346.853] (–) NVIDIA(0):
35346.853] (–) NVIDIA(0): DFP-1: disconnected
35346.853] (–) NVIDIA(0): DFP-1: Internal TMDS
35346.853] (–) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
35346.853] (–) NVIDIA(0):
35346.853] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20150116)
35346.854] (II) NVIDIA(0): NVIDIA GPU GeForce GT 610 (GF119) at PCI:1:0:0 (GPU-0)
35346.854] (–) NVIDIA(0): Memory: 1048576 kBytes
35346.854] (–) NVIDIA(0): VideoBIOS: 75.19.55.00.02
35346.854] (II) NVIDIA(0): Detected PCI Express Link width: 16X
35346.854] (==) NVIDIA(0):
35346.854] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
35346.854] (==) NVIDIA(0): will be used as the requested mode.
35346.854] (==) NVIDIA(0):
35346.854] (–) NVIDIA(0): No enabled display devices found; starting anyway because
35346.854] (–) NVIDIA(0): AllowEmptyInitialConfiguration is enabled
35346.854] (II) NVIDIA(0): Validated MetaModes:
35346.854] (II) NVIDIA(0): “NULL”
35346.854] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
35346.854] (WW) NVIDIA(0): Unable to get display device for DPI computation.
35346.854] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
35346.854] (–) Depth 24 pixmap format is 32 bpp
35346.855] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
35346.855] (II) NVIDIA: access.
35346.861] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
35346.861] (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
35346.861] (II) NVIDIA(0): configuration option may not be set correctly. When the
35346.861] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
35346.861] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
35346.861] (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
35346.861] (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
35346.861] (II) NVIDIA(0): Config Options in the README.
35346.882] (II) NVIDIA(0): Built-in logo is bigger than the screen.
35346.882] (II) NVIDIA(0): Setting mode “NULL”
35346.915] (==) NVIDIA(0): Disabling shared memory pixmaps
35346.915] (==) NVIDIA(0): Backing store enabled
35346.915] (==) NVIDIA(0): Silken mouse enabled
35346.916] (II) Loading sub module “x11glvnd”
35346.916] (II) LoadModule: “x11glvnd”
35346.917] (WW) Warning, couldn’t open module x11glvnd
35346.917] (II) UnloadModule: “x11glvnd”
35346.917] (II) Unloading x11glvnd
35346.917] (II) x11glvnd Loading
35346.917] (II) Loading sub module “dri2”
35346.917] (II) LoadModule: “dri2”
35346.917] (II) Module “dri2” already built-in
35346.917] (II) NVIDIA(0): [DRI2] Setup complete
35346.917] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
35346.917] (–) RandR disabled
35346.922] (II) AIGLX: Screen 0 is not DRI2 capable
35346.922] (EE) AIGLX: reverting to software rendering
35346.942] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
35346.942] (EE) GLX: could not load software renderer
35346.942] (II) GLX: no usable GL providers found for screen 0
35347.069] (II) config/udev: Adding input device Power Button (/dev/input/event1)
35347.069] () Power Button: Applying InputClass “evdev keyboard catchall”
35347.069] () Power Button: Applying InputClass “system-keyboard”
35347.069] () Power Button: Applying InputClass “evdev keyboard catchall”
35347.069] (II) LoadModule: “evdev”
35347.069] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
35347.069] (II) Module evdev: vendor=“X.Org Foundation”
35347.069] compiled for 1.18.0, module version = 2.10.1
35347.069] Module class: X.Org XInput Driver
35347.069] ABI class: X.Org XInput driver, version 22.1
35347.069] (II) Using input driver ‘evdev’ for ‘Power Button’
35347.069] () Power Button: always reports core events
35347.069] () evdev: Power Button: Device: “/dev/input/event1”
35347.069] (–) evdev: Power Button: Vendor 0 Product 0x1
35347.069] (–) evdev: Power Button: Found keys
35347.069] (II) evdev: Power Button: Configuring as keyboard
35347.069] () Option “config_info” “udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event1”
35347.069] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD, id 6)
35347.069] () Option “xkb_rules” “evdev”
35347.069] () Option “xkb_model” “microsoftpro”
35347.069] () Option “xkb_layout” “gb”
35347.069] () Option “xkb_variant” “basic”
35347.132] (II) config/udev: Adding input device Power Button (/dev/input/event0)
35347.132] () Power Button: Applying InputClass “evdev keyboard catchall”
35347.132] () Power Button: Applying InputClass “system-keyboard”
35347.132] () Power Button: Applying InputClass “evdev keyboard catchall”
35347.132] (II) Using input driver ‘evdev’ for ‘Power Button’
35347.132] () Power Button: always reports core events
35347.132] () evdev: Power Button: Device: “/dev/input/event0”
35347.132] (–) evdev: Power Button: Vendor 0 Product 0x1
35347.132] (–) evdev: Power Button: Found keys
35347.132] (II) evdev: Power Button: Configuring as keyboard
35347.132] () Option “config_info” “udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event0”
35347.132] (II) XINPUT: Adding extended input device “Power Button” (type: KEYBOARD, id 7)
35347.132] () Option “xkb_rules” “evdev”
35347.132] () Option “xkb_model” “microsoftpro”
35347.132] () Option “xkb_layout” “gb”
35347.132] (**) Option “xkb_variant” “basic”
35347.134] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event12)
35347.134] (II) No input driver specified, ignoring this device.
35347.134] (II) This device may have been added with another device file.
35347.134] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
35347.134] (II) No input driver specified, ignoring this device.
35347.135] (II) This device may have been added with another device file.
35347.135] (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event7)
35347.135] (II) No input driver specified, ignoring this device.
35347.135] (II) This device may have been added with another device file.
35347.136] (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event8)
35347.136] (II) No input driver specified, ignoring this device.
35347.136] (II) This device may have been added with another device file.
35347.136] (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event9)
35347.136] (II) No input driver specified, ignoring this device.
35347.136] (II) This device may have been added with another device file.
35347.136] (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event10)
35347.136] (II) No input driver specified, ignoring this device.
35347.136] (II) This device may have been added with another device file.
35347.137] (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event11)
35347.137] (II) No input driver specified, ignoring this device.
35347.137] (II) This device may have been added with another device file.
35347.137] (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event4)