Bug 218224 - Closing Krita get that crash
Summary: Closing Krita get that crash
Status: RESOLVED DUPLICATE of bug 228424
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 03:12 UTC by sinozzuke
Modified: 2010-03-29 19:39 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 sinozzuke 2009-12-11 03:12:37 UTC
Application that crashed: krita
Version of the application: 2.1 RC 1
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Playing around with krita, doing several things, without incidents. After that choose File-Quit and get that crash. I submited because reporting assistant drop me 3 stars. But I don't think was wrong, get opengl unchecked and no 3d compositing in desktop.

 -- Backtrace:
Application: Krita (krita), signal: Segmentation fault
[Current thread is 1 (Thread 0x7ff65d8f57a0 (LWP 5197))]

Thread 2 (Thread 0x7ff632346910 (LWP 5219)):
[KCrash Handler]
#5  QMutex::lock (this=0x80) at thread/qmutex.cpp:152
#6  0x00007ff65bb7d588 in QMutexLocker::relock (arg=<value optimized out>) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:120
#7  QMutexLocker (arg=<value optimized out>) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:102
#8  QThreadPrivate::finish (arg=<value optimized out>) at thread/qthread_unix.cpp:198
#9  0x00007ff65bb7d44d in ~__pthread_cleanup_class (arg=0x2ce8990) at /usr/include/pthread.h:535
#10 QThreadPrivate::start (arg=0x2ce8990) at thread/qthread_unix.cpp:190
#11 0x00007ff657953a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#12 0x00007ff65d3867bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff65d8f57a0 (LWP 5197)):
#0  0x00007ff65d37a373 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff65316629a in ?? () from /usr/lib/libxcb.so.1
#2  0x00007ff6531667d7 in ?? () from /usr/lib/libxcb.so.1
#3  0x00007ff653166a85 in xcb_writev () from /usr/lib/libxcb.so.1
#4  0x00007ff657012d4a in _XSend () from /usr/lib/libX11.so.6
#5  0x00007ff657013295 in _XFlush () from /usr/lib/libX11.so.6
#6  0x00007ff656feb11a in XFlush () from /usr/lib/libX11.so.6
#7  0x00007ff65c60c530 in QWidgetPrivate::hide_sys (this=0x251f0a0) at kernel/qwidget_x11.cpp:2045
#8  0x00007ff65c5d53f4 in QWidgetPrivate::hide_helper (this=0x251f0a0) at kernel/qwidget.cpp:6832
#9  0x00007ff65c5dcd80 in QWidget::setVisible (this=0x2522c50, visible=<value optimized out>) at kernel/qwidget.cpp:7012
#10 0x00007ff65c5d2c15 in QWidget::hide (this=0x2522c50, __in_chrg=<value optimized out>) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:477
#11 ~QWidget (this=0x2522c50, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1348
#12 0x00007ff65c607771 in ~QDesktopWidget (this=0x7fffb3174ec0, __in_chrg=<value optimized out>) at kernel/qdesktopwidget_x11.cpp:228
#13 0x00007ff65c59001c in ~QApplication (this=0x7fffb3175280, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:980
#14 0x00007ff65d61882f in kdemain () from /usr/lib/libkdeinit4_krita.so
#15 0x00007ff65d2c5abd in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fffb3175418) at libc-start.c:220
#16 0x0000000000400679 in _start ()

This bug may be a duplicate of or related to bug 217200

Reported using DrKonqi
Comment 1 Halla Rempt 2010-03-29 19:39:29 UTC
I am fairly sure it's a duplicate of 228424 -- Reported in here: https://bugs.launchpad.net/kubuntu-7/+bug/550492.

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