Problem with network manager

English Network/Internet
1

I am having a problem with network manager, every time I clic over a connection to see the properties it hangs, this is the developer information output of the error.

Ejecutable:plasmashell PID: 1274 Señal:Illegal instrucion (4)

Application: Plasma (plasmashell), signal: Illegal instructionUsing host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8ba15c47c0 (LWP 1332))]


Thread 8 (Thread 0x7f8b8b0ae700 (LWP 1335)):
#0  0x00007f8b9ab2ec1d in poll () at /lib64/libc.so.6
#1  0x00007f8b9fa34422 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f8b9fa3600f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f8b8d1fec29 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#6  0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 7 (Thread 0x7f8b83fff700 (LWP 1355)):
#0  0x00007f8b97261cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x00007f8b9721fe16 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f8b9b456a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f8b9b22084a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f8b9e4f05f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 6 (Thread 0x7f8b7042a700 (LWP 1383)):
#0  0x00007f8b9ab2ec1d in poll () at /lib64/libc.so.6
#1  0x00007f8b9721fe64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f8b9b456a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f8b9b22084a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f8b9e4f05f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 5 (Thread 0x7f8b6e9d4700 (LWP 1387)):
#0  0x00007f8b9721f401 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0
#1  0x00007f8b9721fd80 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f8b9b456a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007f8b9b22084a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007f8b9e4f05f8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 4 (Thread 0x7f8b6d06b700 (LWP 1388)):
#0  0x00007f8b9a33c05f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f8ba0c987eb in  () at /usr/lib64/libQt5Script.so.5
#2  0x00007f8ba0c98819 in  () at /usr/lib64/libQt5Script.so.5
#3  0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#4  0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 3 (Thread 0x7f8b659ec700 (LWP 1389)):
#0  0x00007f8b9ab2aced in read () at /lib64/libc.so.6
#1  0x00007f8b97260b60 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f8b9721f999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f8b9721fdf8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f8b9b456a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#6  0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#7  0x00007f8b9b22084a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8b9f07cf82 in  () at /usr/lib64/libQt5Quick.so.5
#9  0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#10 0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#11 0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 2 (Thread 0x7f8ad913c700 (LWP 1392)):
#0  0x00007f8b9ab43682 in __libc_disable_asynccancel () at /lib64/libc.so.6
#1  0x00007f8b9ab2acf9 in read () at /lib64/libc.so.6
#2  0x00007f8b97260b60 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f8b9721f999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f8b9721fdf8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#6  0x00007f8b9b456a5b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#7  0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#8  0x00007f8b9b22084a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#9  0x00007f8ada788b77 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so
#10 0x00007f8b9b22555f in  () at /usr/lib64/libQt5Core.so.5
#11 0x00007f8b9a3380a4 in start_thread () at /lib64/libpthread.so.0
#12 0x00007f8b9ab3704d in clone () at /lib64/libc.so.6


Thread 1 (Thread 0x7f8ba15c47c0 (LWP 1332)):
[KCrash Handler]
#6  0x00007f8ac7b304fb in  ()
#7  0x00000000021e0b40 in  ()
#8  0x0000000000000007 in  ()
#9  0x0000000001f93f00 in  ()
#10 0x0000000000000044 in  ()
#11 0x00007ffcb4713ac0 in  ()
#12 0x00007ffcb4713ae0 in  ()
#13 0x00007f8b8120e418 in  () at /usr/lib64/dri/vmwgfx_dri.so
#14 0x00007f8b8120e6e4 in  () at /usr/lib64/dri/vmwgfx_dri.so
#15 0x00007f8b8114a9a1 in  () at /usr/lib64/dri/vmwgfx_dri.so
#16 0x00007f8b81143a35 in  () at /usr/lib64/dri/vmwgfx_dri.so
#17 0x00007f8b81143ee7 in  () at /usr/lib64/dri/vmwgfx_dri.so
#18 0x00007f8b813f66ed in  () at /usr/lib64/dri/vmwgfx_dri.so
#19 0x00007f8b8119e517 in  () at /usr/lib64/dri/vmwgfx_dri.so
#20 0x00007f8b81018d50 in  () at /usr/lib64/dri/vmwgfx_dri.so
#21 0x00007f8b80fea0ef in  () at /usr/lib64/dri/vmwgfx_dri.so
#22 0x00007f8b6668e4d8 in  () at /usr/lib64/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so
#23 0x00007f8b9b42f40f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#24 0x00007f8b9f118f2e in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /usr/lib64/libQt5Quick.so.5
#25 0x00007f8b9f0eacde in  () at /usr/lib64/libQt5Quick.so.5
#26 0x00007f8b9f0ebe35 in  () at /usr/lib64/libQt5Quick.so.5
#27 0x00007f8b9c778e8c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#28 0x00007f8b9c77dcd8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#29 0x00007f8b9b3ffba5 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#30 0x00007f8b9b45644d in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#31 0x00007f8b9b456771 in  () at /usr/lib64/libQt5Core.so.5
#32 0x00007f8b9721fc84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#33 0x00007f8b9721fed8 in  () at /usr/lib64/libglib-2.0.so.0
#34 0x00007f8b9721ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#35 0x00007f8b9b456a3c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#36 0x00007f8b9b3fda63 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#37 0x00007f8b9b4055d6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#38 0x000000000043467b in main ()

thanks

opensuse 42.1 kde 64 bits

2

I have made some more test and it seems to be a plasma KDE specific problem not network manager, I test it in xfce and it is working fine in that enviroment, not crash.

3

The crash is inside vmwgfx_dri, i.e. the vmware video driver. Are you running it inside vmware?
Try to disable compositing (“Configure Desktop”->“Display and Monitor”->Compositor, or press Shift+Alt+F12), does it crash then too?

Maybe try to disable 3D acceleration for the vmware guest if vmware has such an option. At least with VirtualBox this can cause problems when using Plasma5 in the guest.

Looks more like a vmware issue to me…

4

Try to disable compositing (“Configure Desktop”->“Display and Monitor”->Compositor, or press Shift+Alt+F12), does it crash then too?

Maybe try to disable 3D acceleration for the vmware guest if vmware has such an option. At least with VirtualBox this can cause problems when using Plasma5 in the guest.

I tried both with no success

5

Can you verify (show us) ‘Compositing’ status?

qdbus org.kde.KWin /KWin supportInformation|grep Compositing
6

A “workaround” would be to disable KDE’s network manager applet in the “System Tray Settings” and use nm-applet instead (package NetworkManager-gnome). You’d have to run it manually the first time though by typing “nm-applet”, it should be started automatically on login by the session management afterwards.

Strictly speaking, disabling KDE’s applet is not even necessary, you can use both at the same time.

7

Curious about this,
I ran some tests and cannot re-produce your described problem.

Therefor, I strongly recommend updating your system to see if that resolves your problem

zypper up

In any case,
There really isn’t any hard reason to run any kind of Network Manager (or similar) when your system is a virtualized Guest… It doesn’t matter what your virtualization is, whether you’re running VMware, KVM, Xen, VBox, etc. The main reason to use a NM is to manage multiple network configurations… But when your system is running as a virtualized Guest there is never any reason to use any more than one network connection, no matter what happens in the outside “physical” world… even switching from wired to wireless, to/from gigabit, dialup and more. At most you might change from/to being a DHCP client and that’s it.

This is because as you use only a single network connection in the Guest, the multitude of possible physical connections is configured in your Guest properties.

So, although you might have a preference to running a NM (ordinarily that should not be a problem) you can also switch to Wicked in YAST and you’ll do just fine.

That said, I switched over one of my LEAP/KDE to see if I could re-produce your problem and I can’t.
Everything continues to run just fine.

TSU

8

I am using a virtual machine to make some test before upgrading my primary pc to LEAP 42.1, can you confirm that this problem is exclusive to vmware virtual machines and will not be present in a physical machine?

thanks

9

Well, I haven’t heard of such a problem yet at least. If it were a general issue, the forum would be full of users complaining and there would be bug reports about it.

I cannot really “confirm” that it is exclusive to vmware, I can only confirm that I don’t have it on any of my two real systems here.
But both run openSUSE 13.2 with Plasma 5.5.3 from the additional KDE Frameworks5 repo, not Leap 42.1.
I didn’t have such a problem with Plasma 5.4.3 (the version included in Leap 42.1) either though, when that was the latest version (i.e. in November).

And as mentioned, the backtrace you posted points to the vmware video driver.

10

I don’t see it in a VMware Guest, and because virtual devices are very standard/supported, you’re seeing a unique anomaly.

Recommend you update your system.
If that doesn’t work, then maybe even re-install your system running the following with <only> the LEAP OSS repo enabled. If you are unsure of this, then post your repo list (zypper lr) and someone will post an appropriate command.

zypper dup

TSU

11

If it really is a vmware video driver,
Then the resolution should be to re-install the VMware Guest tools.

Although a working version should already be automatically installed by openSUSE (One of the nice things that separates openSUSE/SUSE is that the virt technology is detected and a Guest Tools is automatically installed), you can also manually update to the latest VMware release by following these instructions

https://forums.opensuse.org/showthread.php/509526-Verified-vmware-tools-patches?highlight=tsu+vmware+tools

TSU