Bug 264923 - Dolphin crashed
Summary: Dolphin crashed
Status: RESOLVED FIXED
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:
: 265053 265267 265421 270362 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-31 10:39 UTC by Daniel Lipowicz
Modified: 2012-02-10 13:27 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.8.0


Attachments
New crash information added by DrKonqi (5.36 KB, text/plain)
2011-11-28 09:58 UTC, Alex Godko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Lipowicz 2011-01-31 10:39:32 UTC
Application: dolphin (1.6)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.38-1-generic i686
Distribution: Ubuntu natty (development branch)

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

- Unusual behavior I noticed:

.............................................................

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

Thread 2 (Thread 0xb3559b70 (LWP 13892)):
#0  0x00ab5d31 in clock_gettime (clock_id=1, tp=0xb3559000) at ../sysdeps/unix/clock_gettime.c:116
#1  0x0130c6a8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x013d89d2 in updateCurrentTime (this=0x9460734, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0x9460734, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x013d7222 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb35590dc) at kernel/qeventdispatcher_glib.cpp:136
#6  0x013d72bd in timerSourcePrepare (source=0x9460700, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x0153e194 in g_main_context_prepare (context=<value optimized out>, priority=0xb355914c) at /build/buildd/glib2.0-2.27.92/glib/gmain.c:2761
#8  0x0153f023 in g_main_context_iterate (context=0x9460c10, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.27.92/glib/gmain.c:3071
#9  0x0153f6e4 in g_main_context_iteration (context=0x9460c10, may_block=1) at /build/buildd/glib2.0-2.27.92/glib/gmain.c:3154
#10 0x013d7a67 in QEventDispatcherGlib::processEvents (this=0x932f6f8, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#11 0x013a9859 in QEventLoop::processEvents (this=0xb3559290, flags=...) at kernel/qeventloop.cpp:149
#12 0x013a9af2 in QEventLoop::exec (this=0xb3559290, flags=...) at kernel/qeventloop.cpp:201
#13 0x012b3c08 in QThread::exec (this=0x9412f50) at thread/qthread.cpp:490
#14 0x0138b6fb in QInotifyFileSystemWatcherEngine::run (this=0x9412f50) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x012b6689 in QThreadPrivate::start (arg=0x9412f50) at thread/qthread_unix.cpp:285
#16 0x009eae99 in start_thread (arg=0xb3559b70) at pthread_create.c:304
#17 0x001e05ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb77e6710 (LWP 13888)):
[KCrash Handler]
#7  0x04b9ebaa in QRasterWindowSurface::~QRasterWindowSurface (this=0x9335240, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:104
#8  0x04b9ec42 in QRasterWindowSurface::~QRasterWindowSurface (this=0x9335240, __in_chrg=<value optimized out>) at painting/qwindowsurface_raster.cpp:108
#9  0x04bba811 in QWidgetBackingStore::~QWidgetBackingStore (this=0x908ecc0, __in_chrg=<value optimized out>) at painting/qbackingstore.cpp:883
#10 0x049e0e2b in QWidgetBackingStoreTracker::destroy (this=0x937bfc0) at kernel/qwidget.cpp:205
#11 0x049e0f81 in QWidgetPrivate::deleteExtra (this=0x905bf80) at kernel/qwidget.cpp:1750
#12 0x049e11ae in QWidgetPrivate::~QWidgetPrivate (this=0x905bf80, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:318
#13 0x049e14a2 in QWidgetPrivate::~QWidgetPrivate (this=0x905bf80, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:323
#14 0x013c28b0 in cleanup (this=0x905bf50, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62
#15 ~QScopedPointer (this=0x905bf50, __in_chrg=<value optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100
#16 QObject::~QObject (this=0x905bf50, __in_chrg=<value optimized out>) at kernel/qobject.cpp:817
#17 0x049e36c9 in QWidget::~QWidget (this=0x905bf50, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1477
#18 0x011eb949 in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0x905bf50, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfoprovider_x11.cpp:145
#19 0x011eb982 in KModifierKeyInfoProvider::~KModifierKeyInfoProvider (this=0x905bf50, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfoprovider_x11.cpp:152
#20 0x01103234 in KModifierKeyInfo::~KModifierKeyInfo (this=0x903b3a8, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfo.cpp:38
#21 0x01103272 in KModifierKeyInfo::~KModifierKeyInfo (this=0x903b3a8, __in_chrg=<value optimized out>) at ../../kdeui/util/kmodifierkeyinfo.cpp:39
#22 0x003315a5 in destroy () at ../../../../apps/dolphin/src/dolphincontextmenu.cpp:59
#23 0x0033526b in KCleanUpGlobalStatic::~KCleanUpGlobalStatic (this=0x364ed4, __in_chrg=<value optimized out>) at /usr/include/kglobal.h:62
#24 0x0013f8bf in __run_exit_handlers (status=0, listp=0x26d324, run_list_atexit=true) at exit.c:78
#25 0x0013f91f in exit (status=0) at exit.c:100
#26 0x00126cee in __libc_start_main (main=0x80485a0 <main(int, char**)>, argc=5, ubp_av=0xbfbc3f64, init=0x80485c0 <__libc_csu_init>, fini=0x8048620 <__libc_csu_fini>, rtld_fini=0xbbda20 <_dl_fini>, stack_end=0xbfbc3f5c) at libc-start.c:258
#27 0x080484f1 in _start ()

Possible duplicates by query: bug 255081.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2011-02-01 16:36:33 UTC
*** Bug 265053 has been marked as a duplicate of this bug. ***
Comment 2 Frank Reininghaus 2011-02-01 16:37:31 UTC
Thanks for the bug report! Looks like it could be a problem related to Qt's raster paint system.
Comment 3 Frank Reininghaus 2011-02-05 12:25:04 UTC
From bug 265421:

- What I was doing when the application crashed: pressing the "close" (X)
button on the window frame causes a seg fault. The same using the menu entry 
"File → Exit". This is always reproducible 100%.

- Unusual behavior I noticed: Dolphin also crashes when the "information" panel
(F11) is shown AND the user mouse over certain files (it doesn't depend on the
file type, btw: i.e., I have three Powerpoint files in a folder, but Dolphin
crashes only when I select one of them).

EDIT:
The crash is related to the use of "QtCurve" style AND the "Ozone" setting.

When switching to "Oxygen" Style or selecting "QtCurve" AND !"Ozone", Dolphin
closes as expected without segfault.
Comment 4 Frank Reininghaus 2011-02-05 12:26:16 UTC
*** Bug 265421 has been marked as a duplicate of this bug. ***
Comment 5 Frank Reininghaus 2011-02-05 12:27:42 UTC
To the other reporters: Could you tell us if you are also using the QtCurve style with the Ozone setting? If yes, could you try if changing these settings fixes the crash for you? Thanks.
Comment 6 Robi 2011-02-05 14:02:49 UTC
I've upgraded to the last version of QtCurve (1.8.4): now Dolphin doesn't crash anymore upon exit when QtCurve style AND Ozone setting are selected. 
Fixed for me.

I still have some issues when my mouse hovers certain files: Dolphin crashes when the "Information" panel is open.
Comment 7 Frank Reininghaus 2011-02-05 14:23:19 UTC
(In reply to comment #6)
> I've upgraded to the last version of QtCurve (1.8.4): now Dolphin doesn't crash
> anymore upon exit when QtCurve style AND Ozone setting are selected. 
> Fixed for me.

That's good to know, thanks for the feedback.
 
> I still have some issues when my mouse hovers certain files: Dolphin crashes
> when the "Information" panel is open.

Please file a new bug report about that (the rule is: only one issue per report), and provide 
a) a backtrace of the crash, and
b) a file that can be used to reproduce the crash
in the new report (without this information, we can't do anything about the crash).
Comment 8 Люсиен 2011-02-05 16:34:17 UTC
I;m sorry guys i can't feedback for the issues in the new kde anymore... i update the video drivers and i can't boot any more :( its freeze after the splash and the monitor goes off even if i load recovery mode or old kernel... nothing just after mounting the sda devices the monitor goes off like doesn't have connection with the videocard and there is nothing i can do:(i will miss KDE ;(
Comment 9 george panta 2011-02-08 17:33:46 UTC
(In reply to comment #5)
> To the other reporters: Could you tell us if you are also using the QtCurve
> style with the Ozone setting? If yes, could you try if changing these settings
> fixes the crash for you? Thanks.

I get the same trace using Oxygen transparent with transparency enabled.

I believe the appmenu patch (included in K/Ubuntu's Qt package) has something to do with this. If I use a normal unpatched qt the same crashes are not triggered.

However bespin and QtCurve styles do not crash anymore.

Is there anyway I can help in resolving this? I have reported this to Hugo Perreira Da Costa in kde-look and at launchpad for the patch.
Comment 10 Люсиен 2011-02-08 23:16:38 UTC
(In reply to comment #9)
> (In reply to comment #5)
> > To the other reporters: Could you tell us if you are also using the QtCurve
> > style with the Ozone setting? If yes, could you try if changing these settings
> > fixes the crash for you? Thanks.
> 
> I get the same trace using Oxygen transparent with transparency enabled.
> 
> I believe the appmenu patch (included in K/Ubuntu's Qt package) has something
> to do with this. If I use a normal unpatched qt the same crashes are not
> triggered.
> 
> However bespin and QtCurve styles do not crash anymore.
> 
> Is there anyway I can help in resolving this? I have reported this to Hugo
> Perreira Da Costa in kde-look and at launchpad for the patch.
Yes i used oxygen-transperent to... i like it more then bespin :P hoever i;m not using K'Ubuntu right now like i said, i hope i get videocard soon as possible :( god i miss linux even with his bugs :D
Comment 11 george panta 2011-02-10 23:08:05 UTC
This bug has been fixed by both the Oxygen-transparent author and the Appmenu Qt author.

Here's the link to the patch by Aurelien Gateau for kdelibs that I think should be committed:

https://bugs.launchpad.net/appmenu-qt/+bug/710810/+attachment/1842216/+files/kmodifierkeyinfoprovider_x11-no-qwidget.diff

Hugo Perreira da Costa has committed the patch that fixes oxygen-transparent to svn already so yay! \o/

Thanks KDE devs!
Comment 12 Люсиен 2011-02-11 05:25:01 UTC
will; try it soon as i can :P
Comment 13 Frank Reininghaus 2011-04-14 15:10:45 UTC
I'm CC'ing the author of KModifierKeyInfoProvider, so he can comment on Aurelien's patch. Even if the crash is fixed already, making the class inherit QObject rather than QWidget might save some unnecessary overhead when running applications that use it.

(In reply to comment #11)
> Here's the link to the patch by Aurelien Gateau for kdelibs that I think should
> be committed:
> 
> https://bugs.launchpad.net/appmenu-qt/+bug/710810/+attachment/1842216/+files/kmodifierkeyinfoprovider_x11-no-qwidget.diff
Comment 14 Christoph Feck 2011-05-14 13:52:30 UTC
*** Bug 270362 has been marked as a duplicate of this bug. ***
Comment 15 Christoph Feck 2011-05-14 14:31:19 UTC
*** Bug 265267 has been marked as a duplicate of this bug. ***
Comment 16 Alex Godko 2011-11-28 09:58:32 UTC
Created attachment 66143 [details]
New crash information added by DrKonqi

dolphin (1.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4

- What I was doing when the application crashed:

just closed dolphin.........................

-- Backtrace (Reduced):
#6  0x00007f099bdf6c09 in QRasterWindowSurface::~QRasterWindowSurface (this=0x23dd480, __in_chrg=<optimized out>) at painting/qwindowsurface_raster.cpp:110
#7  0x00007f099bdf6c89 in QRasterWindowSurface::~QRasterWindowSurface (this=0x23dd480, __in_chrg=<optimized out>) at painting/qwindowsurface_raster.cpp:114
#8  0x00007f099be1026e in QWidgetBackingStore::~QWidgetBackingStore (this=0x240e580, __in_chrg=<optimized out>) at painting/qbackingstore.cpp:883
#9  0x00007f099bc4da29 in QWidgetBackingStoreTracker::destroy (this=0x23c1390) at kernel/qwidget.cpp:210
#10 0x00007f099bc4db7e in QWidgetPrivate::deleteExtra (this=0x1c37d10) at kernel/qwidget.cpp:1796
Comment 17 Alex Godko 2011-11-28 15:50:14 UTC
probably duplicate of #264923, which is fixed
Comment 18 Peter Penz 2012-02-10 13:27:14 UTC
Please reopen the issue if you can still reproduce it with KDE 4.8.x and Qt 4.8.x A lot of rastersystem-related fixes have done there and I cannot reproduce this crash. Thanks!