Bug 205849 - plasma segmentation fault on 'show dashboard'
Summary: plasma segmentation fault on 'show dashboard'
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-31 23:38 UTC by Ewan A. A. Gunn
Modified: 2012-05-28 22:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ewan A. A. Gunn 2009-08-31 23:38:39 UTC
Version:            (using KDE 4.3.0)
Compiler:          gcc-4.3.2 
OS:                Linux
Installed from:    Gentoo Packages

Every time I use a screen corner to activate 'show dashboard', plasma crashes.

Steps to reproduce:
1. Set a corner via 'screen edges' in kcontrol to 'show dashboard'.
2. Move mouse to that corner.

Frequency:
Happens every time.

Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 0 (LWP 14966)]

Thread 2 (Thread 0x7faad39cd950 (LWP 14969)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007faaf56b893b in QWaitCondition::wait (this=0xbcfae0, mutex=0xbcfad8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  0x00007faaf69a6e81 in QHostInfoAgent::run (this=0xbcfac0) at kernel/qhostinfo.cpp:260
#3  0x00007faaf56b7c3f in QThreadPrivate::start (arg=0xbcfac0) at thread/qthread_unix.cpp:189
#4  0x00007faaf5448ff7 in start_thread (arg=<value optimized out>) at pthread_create.c:297
#5  0x00007faaf279a48d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7faaf7f60790 (LWP 14966)):
[KCrash Handler]
#5  QWidget::mapToParent (this=0x0, pos=@0x7fffc4c71fa0) at kernel/qwidget.cpp:3829
#6  0x00007faaf492e8e8 in QWidget::mapTo (this=<value optimized out>, parent=0xedc000, pos=@0x61a) at kernel/qwidget.cpp:3785
#7  0x00007faaf4aab4fe in QWidgetBackingStore::flush (this=0xf0bf80, widget=<value optimized out>, surface=<value optimized out>) at painting/qbackingstore.cpp:98
#8  0x00007faaf4aac767 in QWidgetBackingStore::sync (this=0xf0bf80) at painting/qbackingstore.cpp:1271
#9  0x00007faaf4933e8d in QWidgetPrivate::syncBackingStore (this=0xedcb30) at kernel/qwidget.cpp:1602
#10 0x00007faaf493d51d in QWidget::event (this=0xedc000, event=0x1068240) at kernel/qwidget.cpp:7799
#11 0x00007faaf4c51c64 in QFrame::event (this=0xedc000, e=0x1068240) at widgets/qframe.cpp:559
#12 0x00007faaf4cc8e41 in QAbstractScrollArea::event (this=0xedc000, e=0x1068240) at widgets/qabstractscrollarea.cpp:918
#13 0x00007faaf48f8fd5 in QApplicationPrivate::notify_helper (this=0x9d4d60, receiver=0xedc000, e=0x1068240) at kernel/qapplication.cpp:4057
#14 0x00007faaf490033a in QApplication::notify (this=0x9b77e0, receiver=0xedc000, e=0x1068240) at kernel/qapplication.cpp:4022
#15 0x00007faaf6317e94 in KApplication::notify (this=0x9b77e0, receiver=0xedc000, event=0x1068240) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#16 0x00007faaf577a78e in QCoreApplication::notifyInternal (this=0x9b77e0, receiver=0xedc000, event=0x1068240) at kernel/qcoreapplication.cpp:606
#17 0x00007faaf577af77 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x9a7e40) at kernel/qcoreapplication.h:213
#18 0x00007faaf579c309 in postEventSourceDispatch (s=<value optimized out>) at kernel/qcoreapplication.h:218
#19 0x00007faaef77ebf6 in IA__g_main_context_dispatch (context=0x9d7120) at gmain.c:2144
#20 0x00007faaef781de5 in g_main_context_iterate (context=0x9d7120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#21 0x00007faaef781ff7 in IA__g_main_context_iteration (context=0x9d7120, may_block=1) at gmain.c:2841
#22 0x00007faaf579bff9 in QEventDispatcherGlib::processEvents (this=0x9c5270, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:324
#23 0x00007faaf49728e6 in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x00007faaf57794e4 in QEventLoop::processEvents (this=<value optimized out>, flags={i = -993579648}) at kernel/qeventloop.cpp:149
#25 0x00007faaf5779668 in QEventLoop::exec (this=0x7fffc4c72dc0, flags={i = -993579568}) at kernel/qeventloop.cpp:196
#26 0x00007faaf577b204 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x00007faaf7c4221f in kdemain (argc=1, argv=0x7fffc4c730c8) at /var/tmp/portage/kde-base/plasma-workspace-4.3.0/work/plasma-workspace-4.3.0/plasma/shells/desktop/main.cpp:50
#28 0x00007faaf26e85c6 in __libc_start_main (main=0x4009c8 <main>, argc=1, ubp_av=0x7fffc4c730c8, init=0x4009f0 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fffc4c730b8) at libc-start.c:226
#29 0x0000000000400929 in _start ()
Comment 1 Alexis MENARD 2009-09-01 11:34:11 UTC
Unable to reproduce here and we tried on three different machine.

How Qt is compiled on gentoo?

According to 0x00007faaf492e8e8 in QWidget::mapTo (this=<value optimized out>,
parent=0xedc000, pos=@0x61a) at kernel/qwidget.cpp:3785 it is probably compiled with some optimization flags that we don't support (lines are different, this has a strange value but just before it was valid). Is it debug or release? It seems to be release build but the case is perfectly handle according to the code.I would say that the compiler is trying to do some magic that we don't control.

I close the bug because it seems to be related to Gentoo...
Comment 2 Alexis MENARD 2009-09-01 11:35:52 UTC
Gentoo issue i would say...
Comment 3 Ewan A. A. Gunn 2009-09-01 12:28:02 UTC
My CFLAGS are "-march=nocona -O2 -pipe -ggdb".  ggdb is there having followed the guidelines for useful bug reports on the techbase.  I did compile with the debug use flag, but that broke virtually everything I had (I was getting spurious output all over the damned place), so recompiled again without that useflag.  

They told me to submit this upstream when I asked in IRC.  I'll submit another bug downstream and link to this one.
Comment 4 Maciej Mrozowski 2009-09-10 16:40:25 UTC
Are you using nvidia drivers? with backing store enabled?
Comment 5 Myriam Schweingruber 2012-05-28 22:14:31 UTC
Closing correctly.valdi