Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDE Plasma 5 upgrade: ksmserver crashes
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
dnm
n00b
n00b


Joined: 07 Oct 2002
Posts: 58
Location: Stockholm/Sweden

PostPosted: Tue Apr 19, 2016 10:55 am    Post subject: KDE Plasma 5 upgrade: ksmserver crashes Reply with quote

For some reason ksmserver does not survive to another day. Just turning the monitor off and on again does not trigger the segmentation fault. The day after I login to a plasma session, ksmserver will have crashed, and pressing ok will take the plasma session down (basically a logout killing every app).

The stacktrace below is similar to https://bugs.kde.org/show_bug.cgi?id=354934 in that mapToNative is called with a nullptr as this. However I have only have one Dell Display connected via DisplayPort.

Code:
Application: ksmserver (ksmserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  QXcbScreen::mapToNative (this=this@entry=0x0, rect=...) at qxcbscreen.cpp:267
#7  0x00007f43d667f7d3 in QXcbWindow::mapToNative (this=<optimized out>, rect=..., screen=0x0) at qxcbwindow.cpp:199
#8  0x00007f43d6680f8b in QXcbWindow::propagateSizeHints (this=0x121e550) at qxcbwindow.cpp:1606
#9  0x00007f43d668608d in QXcbWindow::setGeometry (this=0x121e550, rect=...) at qxcbwindow.cpp:709
#10 0x00007f43e9c9231a in ScreenLocker::X11Locker::updateGeo (this=0x1162040) at /var/tmp/portage/kde-plasma/kscreenlocker-5.5.5/work/kscreenlocker-5.5.5/x11locker.cpp:492
#11 0x00007f43e59d1a53 in QtPrivate::QSlotObjectBase::call (a=0x7fffa07fd7d0, r=0x1162040, this=0x1220c60) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#12 QMetaObject::activate (sender=sender@entry=0x11565e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffa07fd7d0) at kernel/qobject.cpp:3698
#13 0x00007f43e59d26c7 in QMetaObject::activate (sender=sender@entry=0x11565e0, m=m@entry=0x7f43e66fb4c0 <QDesktopWidget::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fffa07fd7d0) at kernel/qobject.cpp:3578
#14 0x00007f43e6256511 in QDesktopWidget::screenCountChanged (this=this@entry=0x11565e0, _t1=_t1@entry=0) at .moc/moc_qdesktopwidget.cpp:218
#15 0x00007f43e6257a24 in QDesktopWidgetPrivate::_q_updateScreens (this=<optimized out>) at kernel/qdesktopwidget.cpp:117
#16 0x00007f43e59d308a in QObject::event (this=this@entry=0x11565e0, e=e@entry=0x1150040) at kernel/qobject.cpp:1239
#17 0x00007f43e623f127 in QWidget::event (this=0x11565e0, event=0x1150040) at kernel/qwidget.cpp:9105
#18 0x00007f43e61fb69c in QApplicationPrivate::notify_helper (this=this@entry=0x1135860, receiver=receiver@entry=0x11565e0, e=e@entry=0x1150040) at kernel/qapplication.cpp:3716
#19 0x00007f43e6200b10 in QApplication::notify (this=0x112abf0, receiver=0x11565e0, e=0x1150040) at kernel/qapplication.cpp:3499
#20 0x00007f43e59a9d8d in QCoreApplication::notifyInternal (this=0x112abf0, receiver=0x11565e0, event=event@entry=0x1150040) at kernel/qcoreapplication.cpp:965
#21 0x00007f43e59acb63 in QCoreApplication::sendEvent (event=0x1150040, receiver=<optimized out>) at kernel/qcoreapplication.h:224
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1127a00) at kernel/qcoreapplication.cpp:1593
#23 0x00007f43e59ad128 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451
#24 0x00007f43e59f7713 in postEventSourceDispatch (s=0x116bc00) at kernel/qeventdispatcher_glib.cpp:271
#25 0x00007f43dec22cad in g_main_dispatch (context=0x7f43d00016f0) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3154
#26 g_main_context_dispatch (context=context@entry=0x7f43d00016f0) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3769
#27 0x00007f43dec22f90 in g_main_context_iterate (context=context@entry=0x7f43d00016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3840
#28 0x00007f43dec2303c in g_main_context_iteration (context=0x7f43d00016f0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmain.c:3901
#29 0x00007f43e59f7787 in QEventDispatcherGlib::processEvents (this=0x1179790, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#30 0x00007f43e59a89aa in QEventLoop::exec (this=this@entry=0x7fffa07fdea0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#31 0x00007f43e59afd8c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229
#32 0x00007f43e5cce32c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1527
#33 0x00007f43e61f72d5 in QApplication::exec () at kernel/qapplication.cpp:2976
#34 0x00007f43ea25a0fe in kdemain (argc=1, argv=<optimized out>) at /var/tmp/portage/kde-plasma/plasma-workspace-5.5.5-r2/work/plasma-workspace-5.5.5/ksmserver/main.cpp:349
#35 0x00007f43e9ec76e0 in __libc_start_main (main=0x400810 <main(int, char**)>, argc=1, argv=0x7fffa07fe158, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa07fe148) at libc-start.c:289
#36 0x0000000000400849 in _start ()
Back to top
View user's profile Send private message
FoZo
n00b
n00b


Joined: 14 Sep 2013
Posts: 5
Location: Stockholm/Sweden

PostPosted: Thu Apr 28, 2016 8:43 am    Post subject: Reply with quote

Same problem here...
Back to top
View user's profile Send private message
dnm
n00b
n00b


Joined: 07 Oct 2002
Posts: 58
Location: Stockholm/Sweden

PostPosted: Thu Apr 28, 2016 8:46 am    Post subject: Reply with quote

FoZo wrote:
Same problem here...

Still crashing for me as well, very irritating.
Back to top
View user's profile Send private message
zebbedi
Tux's lil' helper
Tux's lil' helper


Joined: 05 Sep 2003
Posts: 118

PostPosted: Thu Apr 28, 2016 8:51 am    Post subject: Reply with quote

I've go the same problem too. I think it's to do with power saving. I've disabled turning off the monitors when my laptop is on DC power and i think it's working better now.
Back to top
View user's profile Send private message
FoZo
n00b
n00b


Joined: 14 Sep 2013
Posts: 5
Location: Stockholm/Sweden

PostPosted: Mon May 09, 2016 7:58 am    Post subject: Reply with quote

zebbedi wrote:
I've go the same problem too. I think it's to do with power saving. I've disabled turning off the monitors when my laptop is on DC power and i think it's working better now.

That is not solution for me. I'm using a laptop.

I tried
Code:
Option      "AccelMethod"  "uxa"

in xorg.conf and it did not work.
I'm using kernel version 4.5.2 , and x11-drivers/xf86-video-intel-2.99.917-r2


Last edited by FoZo on Tue May 10, 2016 7:07 pm; edited 1 time in total
Back to top
View user's profile Send private message
zebbedi
Tux's lil' helper
Tux's lil' helper


Joined: 05 Sep 2003
Posts: 118

PostPosted: Mon May 09, 2016 8:04 am    Post subject: Reply with quote

I've got an nvidia card, with intel built in, and it's use modesetting to switch them. kernel 4.1.16-r1 and same intel driver as you. Mine has been much much better since disabling the monitor power saving, but has crashed once.
Back to top
View user's profile Send private message
870Fragmaster
Tux's lil' helper
Tux's lil' helper


Joined: 01 Jul 2002
Posts: 92
Location: Gulfport, Ms

PostPosted: Wed Jun 15, 2016 2:16 am    Post subject: Reply with quote

I have a nvidia card using the nvidia driver on a desktop machine. Kcmserver and plama are crashing often. I am however using a kvm switch to change computers. I havent noticed any pattern in the crashes...
Back to top
View user's profile Send private message
FoZo
n00b
n00b


Joined: 14 Sep 2013
Posts: 5
Location: Stockholm/Sweden

PostPosted: Wed Jun 22, 2016 6:37 am    Post subject: Reply with quote

Looks like with the new version of plasma and qt 5.6 that issue is fixed.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 7139
Location: Austria

PostPosted: Wed Jun 22, 2016 7:37 am    Post subject: Reply with quote

Yes, crashes due to monitor standby/switch-off and some multi-monitor glitches should be fixed by Qt-5.6.1 and a backported fix in plasma-workspace-5.6.5.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
zebbedi
Tux's lil' helper
Tux's lil' helper


Joined: 05 Sep 2003
Posts: 118

PostPosted: Wed Jun 22, 2016 7:38 am    Post subject: Reply with quote

What's the easiest/best way to unmask etc all the required packages for an upgrade to that?
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 7139
Location: Austria

PostPosted: Wed Jun 22, 2016 8:26 am    Post subject: Reply with quote

You can pick the kde-plasma-5.6.keywords from there: https://gitweb.gentoo.org/proj/kde.git/tree/Documentation/package.accept_keywords
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
870Fragmaster
Tux's lil' helper
Tux's lil' helper


Joined: 01 Jul 2002
Posts: 92
Location: Gulfport, Ms

PostPosted: Wed Jun 22, 2016 11:25 pm    Post subject: Reply with quote

I switched from the nvidia driver (version 340.93 on my old card) to the nouveau driver. It reduced the number of crashes from plasma, but I still am having issues with my mouse stopping after leaving the computer idle and coming back. Could be from switching with the KVM switch.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum