...this time they killed TigerVNC

English Install/Boot/Login
#1

Two machines on TW 64 bit with KDE, TigerVNC doing fine for months, today updates killed the VNCservers, login works, but afterwards only a black window is shown on the client instead of the remote desktop.

On one machine I catched:

pplication: ksmserver (ksmserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff5a1393900 (LWP 1837))]

Thread 2 (Thread 0x7ff589400700 (LWP 1840)):
[KCrash Handler]
#6  0x00007ff5a0c17a60 in raise () from /lib64/libc.so.6
#7  0x00007ff5a0c190c6 in abort () from /lib64/libc.so.6
#8  0x00007ff595ba05c4 in ?? () from /lib64/libdbus-1.so.3
#9  0x00007ff595b9707c in _dbus_warn_check_failed () from /lib64/libdbus-1.so.3
#10 0x00007ff59dc5d631 in ?? () from /usr/lib64/libQt5DBus.so.5
#11 0x00007ff59dc5dbe5 in ?? () from /usr/lib64/libQt5DBus.so.5
#12 0x00007ff59dc5edf8 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x00007ff59bb79f62 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#14 0x00007ff59bb4c561 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#15 0x00007ff59bb4e8b5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#16 0x00007ff59bba1323 in ?? () from /usr/lib64/libQt5Core.so.5
#17 0x00007ff5940a8b57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007ff5940a8d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007ff5940a8e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007ff59bba173f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#21 0x00007ff59bb4ad0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#22 0x00007ff59b97d05a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#23 0x00007ff59dc4ba45 in ?? () from /usr/lib64/libQt5DBus.so.5
#24 0x00007ff59b98173e in ?? () from /usr/lib64/libQt5Core.so.5
#25 0x00007ff595dbf4e7 in start_thread () from /lib64/libpthread.so.0
#26 0x00007ff5a0cd0a2f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff5a1393900 (LWP 1837)):
#0  0x00007ff595dc55ed in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007ff59b982a5b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5
#2  0x00007ff59b97bd3b in QSemaphore::acquire(int) () from /usr/lib64/libQt5Core.so.5
#3  0x00007ff59bb7985a in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#4  0x00007ff59dca34c3 in ?? () from /usr/lib64/libQt5DBus.so.5
#5  0x00007ff59dc5463e in ?? () from /usr/lib64/libQt5DBus.so.5
#6  0x00007ff59dc4cfe9 in QDBusConnection::connect(QString const&, QString const&, QString const&, QString const&, QObject*, char const*) () from /usr/lib64/libQt5DBus.so.5
#7  0x00007ff5a09ccc93 in ?? () from /usr/lib64/libKScreenLocker.so.5
#8  0x00007ff59bb7967c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
#9  0x00007ff59dca1a32 in QDBusServiceWatcher::serviceRegistered(QString const&) () from /usr/lib64/libQt5DBus.so.5
#10 0x00007ff59dca21ef in ?? () from /usr/lib64/libQt5DBus.so.5
#11 0x00007ff59dca2515 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQt5DBus.so.5
#12 0x00007ff59dc55f48 in ?? () from /usr/lib64/libQt5DBus.so.5
#13 0x00007ff59bb79f62 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#14 0x00007ff59c8d593c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#15 0x00007ff59c8dccb4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#16 0x00007ff59bb4c578 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#17 0x00007ff59bb4e8b5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#18 0x00007ff59bba1323 in ?? () from /usr/lib64/libQt5Core.so.5
#19 0x00007ff5940a8b57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007ff5940a8d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007ff5940a8e1c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007ff59bba173f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#23 0x00007ff59bb4ad0a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#24 0x00007ff59bb53164 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#25 0x00007ff5a0f9aa9e in kdemain () from /usr/lib64/libkdeinit5_ksmserver.so
#26 0x00007ff5a0c0346a in __libc_start_main () from /lib64/libc.so.6
#27 0x00005585a24d085a in _start ()

Need that back soon! :\

#2

So VNC server works. If your session crashes, how is it related to TigerVNC?

#3

Because the client sees a black screen -> VNC dead.

Anything substantial? I myself am pretty good in splitting hairs… :wink:

#4

vncserver works here on current TW.

#5

TigerVNC?

So what is crashing on my two machines? How to resolve this? Again: Anything substantial?

#6

Please! Can anybody tell me how to roll back this update to make Tigervnc serve a functional graphics window on TW with KDE and EXT4 file system? I need this working urgently. How difficult can it be to have a stable graphics window in 2017?

#7

Output of

zypper lr -d

please. Seems a libQt5 issue.

#8

plain vanilla

zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.

# | Alias        | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                      | Service
--+--------------+-----------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------+--------
1 | repo-debug   | openSUSE-Tumbleweed-Debug   | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/  |        
2 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/non-oss/    |        
3 | repo-oss     | openSUSE-Tumbleweed-Oss     | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/tumbleweed/repo/oss/        |        
4 | repo-source  | openSUSE-Tumbleweed-Source  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/ |        
5 | repo-update  | openSUSE-Tumbleweed-Update  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/
#9

Updated 20 min ago, didn’t change anything…

#10

On Thu 06 Jul 2017 07:26:02 PM CDT, suse rasputin wrote:

Updated 20 min ago, didn’t change anything…

Hi
So, create a test user on the remote system and login as that
user, try a different WM eg iceWM, does that work with current
user or test user? Not a graphics card driver issue on the remote
system?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.73-18.17-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#11

Did you try other VNC clients? Since you can login, the server runs. But, you’re not providing too much info. And, we’re not some kind of company that you have an SLA with.

#12

Which kind of info do you need? Same thing I had in the very beginning with 42.2, with TW it worked till it broke 2 days ago.

#13

Update: Todays updates didnt resolve the issue.

#14

Did you report a bug?
Did you create a new remote user, other things as asked by Malcolm?
Can you show output by starting the client from a terminal?

Re. the title: please realize there is no “they”. The community is all of us. Without bugreports nothing is going to be done.

#15

How to reverse QT5 to a working version?`Graphics driver is totally OK, as display attached works fine.

#16

Is btrfs involved? If so, look for a snapshot from before the issue started.
No btrfs? TW does not keep previous versions. (at least not of those packages ).
Since others report their TW to be working properly I wouldn’t even consider downgrading, but rather look for some config. Creating a new user could help in such a case.

#17

On Fri 07 Jul 2017 04:16:02 PM CDT, suse rasputin wrote:

How to reverse QT5 to a working version?`Graphics driver is totally OK,
as display attached works fine.

Hi
Unless you rollback (via btrfs) or have a cached version, no chance the
Tumbleweed repos only move forward (as in replace)…

So, question is why the need to run a remote desktop? Use ssh -X?

Or raise a bug…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.73-18.17-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

#18

What is in the remote user’s ~/.vnc/xstartup ?

#19

A random combination of reboots, stop-restart tigervnc server brought me back the VNC connection with working desktop. Starting Firefox and waiting some minutes makes Firefox and all other windows on the desktop disappear.

Trying to restart Firefox gives a window saying:

“KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path: Not connected to D-Bus server”

Found this: https://forums.opensuse.org/showthread.php/434158-D-bus-error …in YasT d-bus is shown as “Disabled” and “Active”. So what’s the problem here?

#20

There is no way anybody can help you without answers to the questions raised. I.e. now way to support you in this matter. “Random reboots” are not a solution.