Bug 320061 - If I open a vncserver session the kde daemon will crash, OK with the main console - pointer does not work, it shows a double horizontal arrow.
Summary: If I open a vncserver session the kde daemon will crash, OK with the main con...
Status: RESOLVED WORKSFORME
Alias: None
Product: wacomtablet
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Ehrichs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-20 17:48 UTC by danielsender
Modified: 2018-03-16 19:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kded4 crash report with debuginfo (13.67 KB, text/plain)
2013-08-13 23:30 UTC, fischer-michael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description danielsender 2013-05-20 17:48:03 UTC
If I open a vncserver session, e.g. 'vncserver :1" there will be a window appearing saying that the kde daemon crashed. I tried using the automated bug reporting system but it said that it could find appropriate debug packages for the task. At the same time, the buttons of the mouse do not work, the pointer is a double horizontal (or 45 degrees) arrow. I disabled desktop effects but it didn't make any difference. If from a konsole I enter 'metacity --replace' then the mouse button works. This problem occurs exactly the same in two different machines after upgrading to kubuntu 13.04, problem that didn't occur in its past version.

Reproducible: Always

Steps to Reproduce:
1. open a vncserver application
2.
3.
Actual Results:  
a window appears notifying that the kde daemon crashed.

Expected Results:  
just open the session on instance :1 (or other)

Application: kded4 ($Id$)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.9.0-030900rc6-generic i686
Distribution: Ubuntu 13.04

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

-- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0xae6c0d96 in Wacom::TabletDaemon::findTabletDevice() () from /usr/lib/kde4/kded_wacomtablet.so
#7  0xae6c0103 in Wacom::TabletDaemon::TabletDaemon(QObject*, QList<QVariant> const&) () from /usr/lib/kde4/kded_wacomtablet.so
#8  0xae6c1cd3 in ?? () from /usr/lib/kde4/kded_wacomtablet.so
#9  0xb70b249e in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () from /usr/lib/libkdecore.so.5
#10 0xb541b356 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#11 0xb541c422 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#12 0xb541e656 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#13 0xb74945d7 in ?? () from /usr/lib/libkdeui.so.5
#14 0xb7494686 in ?? () from /usr/lib/libkdeui.so.5
#15 0xb749480c in ?? () from /usr/lib/libkdeui.so.5
#16 0xb5aff7be in QDBusConnectionPrivate::deliverCall (this=0x8a002b0, object=0x8b384b8, msg=..., metaTypes=..., slotIdx=0) at qdbusintegrator.cpp:951
#17 0xb5b0003a in QDBusConnectionPrivate::activateCall (this=0x8a002b0, object=0x8b384b8, flags=337, msg=...) at qdbusintegrator.cpp:856
#18 0xb5b007e2 in QDBusConnectionPrivate::activateObject (this=0x8a002b0, node=..., msg=..., pathStartPos=145977345) at qdbusintegrator.cpp:1427
#19 0xb5b00bd8 in QDBusActivateObjectEvent::placeMetaCall (this=0x8b37198) at qdbusintegrator.cpp:1541
#20 0xb6d5a48b in QObject::event (this=this@entry=0xbfe01f7c, e=e@entry=0x8b37198) at kernel/qobject.cpp:1194
#21 0xb6d436da in QCoreApplication::event (this=this@entry=0xbfe01f7c, e=e@entry=0x8b37198) at kernel/qcoreapplication.cpp:1758
#22 0xb62363cd in QApplication::event (this=0xbfe01f7c, e=0x8b37198) at kernel/qapplication.cpp:2549
#23 0xb622dc7c in QApplicationPrivate::notify_helper (this=0x8a1ca08, receiver=0xbfe01f7c, e=0x8b37198) at kernel/qapplication.cpp:4567
#24 0xb6230b94 in QApplication::notify (this=0x8b37198, receiver=0xbfe01f7c, e=0x8b37198) at kernel/qapplication.cpp:3949
#25 0xb7490d01 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#26 0xb6d3e90e in QCoreApplication::notifyInternal (this=0xbfe01f7c, receiver=0xbfe01f7c, event=0x8b37198) at kernel/qcoreapplication.cpp:946
#27 0xb6d42721 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#28 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x89acf88) at kernel/qcoreapplication.cpp:1570
#29 0xb6d42a8c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463
#30 0xb6d70aa4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#31 postEventSourceDispatch (s=0x8a1cd40) at kernel/qeventdispatcher_glib.cpp:279
#32 0xb592c3b3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0xb592c750 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#34 0xb592c831 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#35 0xb6d70c21 in QEventDispatcherGlib::processEvents (this=this@entry=0x89ae2e8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#36 0xb62e4a5a in QGuiEventDispatcherGlib::processEvents (this=0x89ae2e8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0xb6d3d3ec in QEventLoop::processEvents (this=this@entry=0xbfe01de8, flags=...) at kernel/qeventloop.cpp:149
#38 0xb6d3d6e1 in QEventLoop::exec (this=this@entry=0xbfe01de8, flags=...) at kernel/qeventloop.cpp:204
#39 0xb6d433fa in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#40 0xb622bfc4 in QApplication::exec () at kernel/qapplication.cpp:3828
#41 0xb541ad40 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kded4.so
#42 0x0804f6df in _start ()

Report to https://bugs.kde.org/
Comment 1 fischer-michael 2013-08-13 23:29:02 UTC
Similar problem with tigervnc-server and Fedora 19.  Can't use automatic bug reporting tool because it needs kded4 to be running.  I saved the crash report and am adding it to this bug report as an attachment.
Comment 2 fischer-michael 2013-08-13 23:30:10 UTC
Created attachment 81696 [details]
kded4 crash report with debuginfo
Comment 3 Valerii Malov 2018-03-16 19:35:03 UTC
I'm just going to close this bug because it's very old and I can't reproduce it, neither these stack traces are relevant anymore (there's no TabletDaemon::findTabletDevice anymore, second stack trace is unrelated to wacom module)