Bug 286030 - KDE restarts when i close unmaximized window
Summary: KDE restarts when i close unmaximized window
Status: RESOLVED DUPLICATE of bug 272495
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.7
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-07 19:12 UTC by Nikolay Golub
Modified: 2011-11-07 21:11 UTC (History)
0 users

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 Nikolay Golub 2011-11-07 19:12:42 UTC
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

Application: plasma-desktop (0.4)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0-ARCH i686

-- Information about the crash:
It has happened every time when i open new window of chromium and this windows
is not maximized.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb56e8710 (LWP 1210))]

Thread 2 (Thread 0xa9db7b70 (LWP 1211)):
#0  0xb780f424 in __kernel_vsyscall ()
#1  0xb60b51ae in poll () from /lib/libc.so.6
#2  0xb5b4209b in g_poll () from /usr/lib/libglib-2.0.so.0
#3  0xb5b335e6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0xb5b3397a in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5  0xb6e8dea7 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#6  0xb6e5eb6d in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#7  0xb6e5edb1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#8  0xb6d623ab in QThread::exec() () from /usr/lib/libQtCore.so.4
#9  0xb6e3f83d in ?? () from /usr/lib/libQtCore.so.4
#10 0xb6d65253 in ?? () from /usr/lib/libQtCore.so.4
#11 0xb27e870c in ?? () from /usr/lib/libGL.so.1
#12 0x00000000 in ?? ()

Thread 1 (Thread 0xb56e8710 (LWP 1210)):
[KCrash Handler]
#7  0xaf5b085c in TaskManager::TaskItem::task() const () from
/usr/lib/libtaskmanager.so.4
#8  0xaf554642 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so
#9  0xaf565658 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so
#10 0xb6e77d04 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#11 0xb6a42f44 in QGraphicsWidget::event(QEvent*) () from
/usr/lib/libQtGui.so.4
#12 0xb6389a24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#13 0xb638edd3 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#14 0xb7596d41 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#15 0xb6e5fb2e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from
/usr/lib/libQtCore.so.4
#16 0xb6e8ff70 in ?? () from /usr/lib/libQtCore.so.4
#17 0xb6e8d492 in ?? () from /usr/lib/libQtCore.so.4
#18 0xb5b32faf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb5b336e0 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb5b3397a in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb6e8de4a in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#22 0xb643cf8a in ?? () from /usr/lib/libQtGui.so.4
#23 0xb6e5eb6d in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/libQtCore.so.4
#24 0xb6e5edb1 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/libQtCore.so.4
#25 0xb6e6350d in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#26 0xb6387894 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#27 0xb07c914b in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#28 0x0804f4a2 in _start ()

Reproducible: Sometimes

Steps to Reproduce:
Sometimes when i have open unmaximized window and i close it plasma crashes and restarts imediately.


Expected Results:  
Plasma shouldn't crash
Comment 1 Christoph Feck 2011-11-07 21:11:19 UTC

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