Bug 270362 - Dolphin crashes when being closed
Summary: Dolphin crashes when being closed
Status: RESOLVED DUPLICATE of bug 264923
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 21:13 UTC by stefan.kramer
Modified: 2011-05-14 13:52 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stefan.kramer 2011-04-07 21:13:34 UTC
Application: dolphin (1.6.1)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu Natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

Closing Dolphin, I get a segmentation fault error message.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f5ab4d1a780 (LWP 5040))]

Thread 2 (Thread 0x7f5a9e6da700 (LWP 5045)):
#0  0x00007f5ab460ff03 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f5aacdae104 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f5aacdae639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f5ab0a95446 in QEventDispatcherGlib::processEvents (this=0x1420bf0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f5ab0a69882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f5ab0a69abc in QEventLoop::exec (this=0x7f5a9e6d9dd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f5ab0980924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007f5ab0a4bc2f in QInotifyFileSystemWatcherEngine::run (this=0x12ef120) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f5ab0983175 in QThreadPrivate::start (arg=0x12ef120) at thread/qthread_unix.cpp:320
#9  0x00007f5aad279d8c in start_thread (arg=0x7f5a9e6da700) at pthread_create.c:304
#10 0x00007f5ab461d04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f5ab4d1a780 (LWP 5040)):
[KCrash Handler]
#6  0x00007f5ab161cfa9 in QRasterWindowSurface::~QRasterWindowSurface (this=0x1465840, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:104
#7  0x00007f5ab161d029 in QRasterWindowSurface::~QRasterWindowSurface (this=0x1465840, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:108
#8  0x00007f5ab16375e2 in QWidgetBackingStore::~QWidgetBackingStore (this=0x14c91b0, __in_chrg=<value optimized out>) at painting/qbackingstore.cpp:883
#9  0x00007f5ab1473779 in QWidgetBackingStoreTracker::destroy (this=0x13dd0c0) at kernel/qwidget.cpp:210
#10 0x00007f5ab14738c9 in QWidgetPrivate::deleteExtra (this=0xefbbd0) at kernel/qwidget.cpp:1776
#11 0x00007f5ab1473b0c in QWidgetPrivate::~QWidgetPrivate (this=0xefbbd0, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:337
#12 0x00007f5ab1473e19 in QWidgetPrivate::~QWidgetPrivate (this=0xefbbd0, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:342
#13 0x00007f5ab0a81645 in cleanup (this=0xf29e40, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#14 ~QScopedPointer (this=0xf29e40, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#15 QObject::~QObject (this=0xf29e40, __in_chrg=<value optimized out>) at kernel/qobject.cpp:818
#16 0x00007f5ab1475f70 in QWidget::~QWidget (this=0xf29e40, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1508
#17 0x00007f5ab22805cf in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0xf29e40, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfoprovider_x11.cpp:145
#18 0x00007f5ab22805f9 in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0xf29e40, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfoprovider_x11.cpp:152
#19 0x00007f5ab21b1631 in KModifierKeyInfo::~KModifierKeyInfo (this=0xe55290, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfo.cpp:38
#20 0x00007f5ab21b1649 in KModifierKeyInfo::~KModifierKeyInfo (this=0xe55290, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfo.cpp:39
#21 0x00007f5ab4570961 in __run_exit_handlers (status=0) at exit.c:78
#22 exit (status=0) at exit.c:100
#23 0x00007f5ab4555f06 in __libc_start_main (main=0x400730 <_start+256>, argc=6, ubp_av=0x7fff3409c5f8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff3409c5e8) at libc-start.c:258
#24 0x0000000000400659 in _start ()

Possible duplicates by query: bug 269671, bug 265421, bug 265053, bug 264923, bug 255081.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2011-04-08 13:18:12 UTC
Thanks for the bug report! Looks like bug 264923. Which style do you use?
Comment 2 stefan.kramer 2011-04-13 23:07:13 UTC
(In reply to comment #1)
> Thanks for the bug report! Looks like bug 264923. Which style do you use?

I'm using oxygen-transparent, but that has not been a problem in previous versions of Kubuntu (10.10) and KDE (4.6.1)
Comment 3 Frank Reininghaus 2011-04-14 15:02:57 UTC
According to bug 264923 comment 11, the issue with oxygen-transparent is fixed, but I couldn't find information on the first version containing the fix.
Comment 4 Christoph Feck 2011-05-14 13:52:30 UTC

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