Bug 324247 - Crash on first running of KDE
Summary: Crash on first running of KDE
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.10.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
: 327824 334268 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-08-30 03:23 UTC by Tom Gagne
Modified: 2014-05-03 17:44 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Gagne 2013-08-30 03:23:16 UTC 
Application: kwin (4.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.5
Operating System: Linux 3.10.9-200.fc19.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Frustrated with Gnome-shell taking 100% of my cpu with my second monitor connected (and other gnome frustrations) I wanted to return to KDE.

I yuminstalled the group, installed switchdesk, ran "switchdesk kde," and started KDE with "startx."

It started up, looked to be creating some icons on my second monitor, then BOOM.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#7  0xaf882275 in _swrast_map_texture (ctx=ctx@entry=0x859a938, texObj=0x84aca10) at ../../../src/mesa/swrast/s_texture.c:287
#8  0xaf8824f4 in _swrast_map_textures (ctx=ctx@entry=0x859a938) at ../../../src/mesa/swrast/s_texture.c:353
#9  0xaf84ad9d in _swrast_span_render_start (ctx=0x859a938) at ../../../src/mesa/swrast/s_context.c:876
#10 0xaf84c02a in _swrast_render_start (ctx=ctx@entry=0x859a938) at ../../../src/mesa/swrast/s_context.c:895
#11 0xaf89793f in _swsetup_RenderStart (ctx=0x859a938) at ../../../src/mesa/swrast_setup/ss_context.c:202
#12 0xaf827a73 in run_render (ctx=0x859a938, stage=0x860ed38) at ../../../src/mesa/tnl/t_vb_render.c:276
#13 0xaf822624 in _tnl_run_pipeline (ctx=ctx@entry=0x859a938) at ../../../src/mesa/tnl/t_pipeline.c:163
#14 0xafaf6653 in intelRunPipeline (ctx=0x859a938) at intel_tris.c:1097
#15 0xaf822faa in _tnl_draw_prims (ctx=ctx@entry=0x859a938, arrays=arrays@entry=0x85fcc34, prim=prim@entry=0xbfcc6240, nr_prims=nr_prims@entry=1, ib=ib@entry=0x0, min_index=0, max_index=5) at ../../../src/mesa/tnl/t_draw.c:525
#16 0xaf8236c4 in _tnl_vbo_draw_prims (ctx=0x859a938, prim=0xbfcc6240, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=5, tfb_vertcount=0x0) at ../../../src/mesa/tnl/t_draw.c:425
#17 0xaf80e099 in vbo_draw_arrays (ctx=ctx@entry=0x859a938, mode=mode@entry=4, start=start@entry=0, count=count@entry=6, numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at ../../../src/mesa/vbo/vbo_exec_array.c:624
#18 0xaf80e2a2 in vbo_exec_DrawArrays (mode=4, start=0, count=6) at ../../../src/mesa/vbo/vbo_exec_array.c:776
#19 0x41bb3b16 in glDrawArrays (mode=4, first=0, count=6) at ../../../src/mapi/glapi/glapi_mapi_tmp.h:3586
#20 0xb6caa2bd in KWin::GLVertexBufferPrivate::fallbackPainting (this=0x8774370, region=..., primitiveMode=primitiveMode@entry=4, hardwareClipping=hardwareClipping@entry=false) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinglutils.cpp:1291
#21 0xb6cad8d8 in KWin::GLVertexBuffer::render (this=0x8773510, region=..., primitiveMode=primitiveMode@entry=4, hardwareClipping=hardwareClipping@entry=false) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinglutils.cpp:1365
#22 0xb770ec2c in KWin::SceneOpenGL::Window::renderQuads (region=..., quads=..., tex=0x845b018, normalized=normalized@entry=false, hardwareClipping=hardwareClipping@entry=false, this=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:1304
#23 0xb7713d8f in renderQuads (hardwareClipping=false, normalized=false, tex=<optimized out>, quads=..., region=..., this=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:1286
#24 KWin::SceneOpenGL::Window::performPaint (this=this@entry=0x84e7510, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:1045
#25 0xb7705d75 in KWin::Scene::finalDrawWindow (this=0x8772a68, w=w@entry=0x8355bc0, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:455
#26 0xb77293a8 in KWin::EffectsHandlerImpl::drawWindow (this=0x877f7a8, w=w@entry=0x8355bc0, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/effects.cpp:318
#27 0xb7702637 in KWin::Scene::finalPaintWindow (this=0x8772a68, w=w@entry=0x8355bc0, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:449
#28 0xb77292a3 in KWin::EffectsHandlerImpl::paintWindow (this=0x877f7a8, w=0x8355bc0, mask=mask@entry=1, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/effects.cpp:281
#29 0xb7705213 in KWin::Scene::paintWindow (w=w@entry=0x84e7510, mask=mask@entry=1, region=..., quads=..., this=0x8772a68) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:356
#30 0xb7705d00 in KWin::Scene::paintWindow (this=0x8772a68, w=0x84e7510, mask=1, region=..., quads=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:444
#31 0xb7703985 in KWin::Scene::paintSimpleScreen (this=this@entry=0x8772a68, orig_mask=orig_mask@entry=0, region=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:342
#32 0xb7702578 in KWin::Scene::finalPaintScreen (this=0x8772a68, mask=mask@entry=0, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:186
#33 0xb7729093 in KWin::EffectsHandlerImpl::paintScreen (this=0x877f7a8, mask=0, region=..., data=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/effects.cpp:254
#34 0xb7703ddb in KWin::Scene::paintScreen (this=this@entry=0x8772a68, mask=mask@entry=0xbfcc6aa0, region=region@entry=0xbfcc6ae8) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:140
#35 0xb77129aa in KWin::SceneOpenGL::paint (this=this@entry=0x8772a68, damage=..., toplevels=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:317
#36 0xb7712be7 in KWin::SceneOpenGL1::paint (this=0x8772a68, damage=..., windows=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_opengl.cpp:712
#37 0xb76fc188 in KWin::Compositor::performCompositing (this=this@entry=0x845fb10) at /usr/src/debug/kde-workspace-4.10.5/kwin/composite.cpp:610
#38 0xb76fd5b9 in KWin::Compositor::slotCompositingOptionsInitialized (this=0x845fb10) at /usr/src/debug/kde-workspace-4.10.5/kwin/composite.cpp:275
#39 0xb7676c28 in KWin::Compositor::qt_static_metacall (_o=0x0, _id=1024, _a=0xbfcc6d08, _c=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/i686-redhat-linux-gnu/kwin/moc_composite.cpp:112
#40 0xb63a071b in QMetaObject::activate (sender=sender@entry=0x8466f78, m=m@entry=0xb64f6860 <QFutureWatcherBase::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3547
#41 0xb63ee2e6 in QFutureWatcherBase::finished (this=this@entry=0x8466f78) at .moc/release-shared/moc_qfuturewatcher.cpp:140
#42 0xb626775c in QFutureWatcherBasePrivate::sendCallOutEvent (this=this@entry=0x848ac70, event=event@entry=0xb0700fb8) at concurrent/qfuturewatcher.cpp:439
#43 0xb6267a1c in QFutureWatcherBase::event (this=0x8466f78, event=0xb0700fb8) at concurrent/qfuturewatcher.cpp:344
#44 0xb5889e94 in QApplicationPrivate::notify_helper (this=0x8356dc8, receiver=0x8466f78, e=0xb0700fb8) at kernel/qapplication.cpp:4562
#45 0xb58909a9 in QApplication::notify (this=0xbfcc7368, receiver=receiver@entry=0x8466f78, e=e@entry=0xb0700fb8) at kernel/qapplication.cpp:4348
#46 0xb6a282f5 in KApplication::notify (this=this@entry=0xbfcc7368, receiver=receiver@entry=0x8466f78, event=event@entry=0xb0700fb8) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#47 0xb76a9d6a in KWin::Application::notify (this=0xbfcc7368, o=0x8466f78, e=0xb0700fb8) at /usr/src/debug/kde-workspace-4.10.5/kwin/main.cpp:371
#48 0xb638b53a in QCoreApplication::notifyInternal (this=0xbfcc7368, receiver=receiver@entry=0x8466f78, event=event@entry=0xb0700fb8) at kernel/qcoreapplication.cpp:949
#49 0xb638e855 in sendEvent (event=0xb0700fb8, receiver=0x8466f78) at kernel/qcoreapplication.h:231
#50 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x8315098) at kernel/qcoreapplication.cpp:1573
#51 0xb638ed7d in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466
#52 0xb593b89a in sendPostedEvents () at ../../src/corelib/kernel/qcoreapplication.h:236
#53 QEventDispatcherX11::processEvents (this=0x8320180, flags=...) at kernel/qeventdispatcher_x11.cpp:75
#54 0xb6389f44 in QEventLoop::processEvents (this=this@entry=0xbfcc7268, flags=...) at kernel/qeventloop.cpp:149
#55 0xb638a281 in QEventLoop::exec (this=this@entry=0xbfcc7268, flags=...) at kernel/qeventloop.cpp:204
#56 0xb638fd1f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#57 0xb58882e5 in QApplication::exec () at kernel/qapplication.cpp:3823
#58 0xb76aadae in kdemain (argc=3, argv=0xbfcc7454) at /usr/src/debug/kde-workspace-4.10.5/kwin/main.cpp:537
#59 0x080487dc in main (argc=3, argv=0xbfcc7454) at /usr/src/debug/kde-workspace-4.10.5/i686-redhat-linux-gnu/kwin/kwin_dummy.cpp:3

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-08-30 04:13:18 UTC 
Driver bug.

-> What's the output of "glxinfo -l"?
-> Do you still use UXA or is it SNA (check /var/log/Xorg.0.log)
-> Since you mentioned a second screen: "xrandr -q"

In case it's a i8xx chip: just use xrender compositing.
Comment 2 Tom Gagne 2013-08-30 14:40:01 UTC 
I don't know what chip it is, but another of the setup screens that appeared after the crash suggested changing to xrender, but because it thought the resolution was too high and that performance might suffer if I didn't change to xrender.

After setting it to xrender the CPU problem seems to have disappeared--just as your predicted.
Comment 3 Thomas Lübking 2013-08-30 17:45:02 UTC 
(In reply to comment #2)
> I don't know what chip it is
Ii this case, the IGP, ie. th black square on the motherboard that makes screen pixels colorful ;-)

type eg. "lspci" to see a hardware summary - one of the devices is the IGP (Integrated Graphics Processor)

> but another of the setup screens that appeared
> after the crash suggested changing to xrender, but because it thought the
> resolution was too high and that performance might suffer if I didn't change
> to xrender.

That's a different (but true) issue - and makes an i8xx chip likely - if you post the lspci output, i'll tell you for sure.
Comment 4 Tom Gagne 2013-08-30 18:30:07 UTC 
[tgagne@tgagne2 ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML 
Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML 
Express Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) PCI Express Port 2 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB UHCI #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface 
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) IDE Controller (rev 03)
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG 
[Calexico2] Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated 
FlashMedia Controller
02:06.4 SD Host controller: Texas Instruments 
PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
02:06.5 Communication controller: Texas Instruments 
PCI6411/6421/6611/6621/7411/7421/7611/7621 Smart Card Controller
10:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751M 
Gigabit Ethernet PCI Express (rev 11)
Comment 5 Thomas Lübking 2013-08-30 19:21:33 UTC 
00:02.0 VGA compatible controller: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller (rev 03)

Not 8xx but early 9xx
For the chip you can have a maximum (combined!) screen size of 2048x2048 (though the officially supported dimension is actually 1600x1200) - otherwise you'll resort to software - and you really don't want that ;-)
(Slow and it's apparently also broken)

=> it may work if you arrange the screens (eg. 1024x768 & 1920x1080) vertically, but given the age and HW limited GL capabilities, you'll likely have a better compositing experience on XRender.
Comment 6 Tom Gagne 2013-08-30 19:26:19 UTC 
I'll check the resolution of the 2nd monitor.  It is old equipment. 
Right now I'm using it as a quazi development server--using a local X 
server capable of higher resolutions on three monitors.

On 8/30/2013 3:21 PM, Thomas Lübking wrote:
> https://bugs.kde.org/show_bug.cgi?id=324247
>
> --- Comment #5 from Thomas Lübking <thomas.luebking@gmail.com> ---
> 00:02.0 VGA compatible controller: Intel Corporation Mobile
> 915GM/GMS/910GML Express Graphics Controller (rev 03)
>
> Not 8xx but early 9xx
> For the chip you can have a maximum (combined!) screen size of 2048x2048
> (though the officially supported dimension is actually 1600x1200) - otherwise
> you'll resort to software - and you really don't want that ;-)
> (Slow and it's apparently also broken)
>
> => it may work if you arrange the screens (eg. 1024x768 & 1920x1080)
> vertically, but given the age and HW limited GL capabilities, you'll likely
> have a better compositing experience on XRender.
>
Comment 7 Thomas Lübking 2013-11-19 16:51:59 UTC 
*** Bug 327824 has been marked as a duplicate of this bug. ***
Comment 8 Thomas Lübking 2014-05-03 17:44:38 UTC 
*** Bug 334268 has been marked as a duplicate of this bug. ***