Bug 160064 - Kwin Crash after terminating konqueror
Summary: Kwin Crash after terminating konqueror
Status: RESOLVED DUPLICATE of bug 156998
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 156789 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-03-29 17:49 UTC by Oliver Putz
Modified: 2008-05-05 18:10 UTC (History)
1 user (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 Oliver Putz 2008-03-29 17:49:54 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc version 4.1.2 20070214 
OS:                Linux

I was browsing some local folders with konqueor as all of a sudden konqueror became unresponsive. I then closed it by terminating it. After I terminated konqueror, KWin crashed with the following backtrace: (kdebase r790102)

Application: KWin (kwin), signal SIGSEGV
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb66416e0 (LWP 5683)]
[New Thread 0xb51afb90 (LWP 7747)]
[KCrash handler]
#6  QProcess::setProcessState (this=0x82f82d8, state=QProcess::NotRunning)
    at io/qprocess.cpp:1295
#7  0xb7964d97 in QProcessPrivate::cleanup (this=0x8286f88)
    at io/qprocess.cpp:424
#8  0xb796667f in QProcessPrivate::_q_processDied (this=0x8286f88)
    at io/qprocess.cpp:677
#9  0xb79ae92d in QProcessPrivate::waitForFinished (this=0x8286f88, 
    msecs=30000) at io/qprocess_unix.cpp:1172
#10 0xb796510c in QProcess::waitForFinished (this=0x82cc238, msecs=30000)
    at io/qprocess.cpp:1284
#11 0xb796546c in ~QProcess (this=0x82cc238) at io/qprocess.cpp:767
#12 0xb7eab0b1 in KWin::Client::gotPing (this=0x8250ef8, timestamp=4217904181)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/kwin/client.cpp:1117
#13 0xb7eca6ee in KWin::RootInfo::gotPing (this=0x81956f0, w=58720257, 
    timestamp=4217904181)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/kwin/events.cpp:204
#14 0xb6cee460 in NETRootInfo::event (this=0x81956f0, event=0xbfc99308, 
    properties=0xbfc98ea8, properties_size=5)
    at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/windowmanagement/netwm.cpp:1950
#15 0xb7ec9d0a in KWin::Workspace::workspaceEvent (this=0x80aff08, 
    e=0xbfc99308)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/kwin/events.cpp:233
#16 0xb7eb9ad4 in KWin::Application::x11EventFilter (this=0xbfc99544, 
    e=0xbfc99308)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/kwin/main.cpp:359
#17 0xb6f0e9ae in qt_x11EventFilter (ev=0xbfc99308)
    at kernel/qapplication_x11.cpp:367
#18 0xb6f1c1b7 in QApplication::x11ProcessEvent (this=0xbfc99544, 
    event=0xbfc99308) at kernel/qapplication_x11.cpp:2972
#19 0xb6f44c75 in QEventDispatcherX11::processEvents (this=0x8054488, 
    flags=@0xbfc993f4) at kernel/qeventdispatcher_x11.cpp:134
#20 0xb79cee61 in QEventLoop::processEvents (this=0xbfc99460, 
    flags=@0xbfc99428) at kernel/qeventloop.cpp:146
#21 0xb79cef8f in QEventLoop::exec (this=0xbfc99460, flags=@0xbfc99468)
    at kernel/qeventloop.cpp:197
#22 0xb79d1476 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:838
#23 0xb6eabe37 in QApplication::exec () at kernel/qapplication.cpp:3267
#24 0xb7ebb224 in kdemain (argc=3, argv=0xbfc99714)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/kwin/main.cpp:508
#25 0x080487c2 in main (argc=50331830, argv=0x61)
    at /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase_build/workspace/kwin/kwin_dummy.cpp:3
#26 0xb6790fdc in __libc_start_main (main=0x80487a0 <main>, argc=3, 
    ubp_av=0xbfc99714, init=0x80487f0 <__libc_csu_init>, 
    fini=0x80487e0 <__libc_csu_fini>, rtld_fini=0xb7f3d100 <_dl_fini>, 
    stack_end=0xbfc9970c) at libc-start.c:229
#27 0x08048711 in _start ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Lubos Lunak 2008-04-02 15:22:55 UTC
Can you reproduce the problem?
Comment 2 Oliver Putz 2008-04-02 16:29:38 UTC
No, regrettably I have not found a way to reproduce this problem yet. But as the backtrace is with debugging symbols I thought I'd open a bugreport for it. Maybe some developer can see from the backtrace why it crashed in the first place.
Comment 3 Lubos Lunak 2008-04-18 15:25:26 UTC
*** Bug 156789 has been marked as a duplicate of this bug. ***
Comment 4 Lubos Lunak 2008-05-05 18:10:59 UTC

*** This bug has been marked as a duplicate of 156998 ***