Bug 344044 - baloo crashed when disabling search
Summary: baloo crashed when disabling search
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-02-11 18:36 UTC by Landis
Modified: 2016-12-29 08:35 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 Landis 2015-02-11 18:36:24 UTC
Application: baloo_file (0.1)
KDE Platform Version: 4.14.4
Qt Version: 4.8.5
Operating System: Linux 3.11.10-25-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
System Settings
un-check (disable) search (desktop)
click apply
crash.

Disabled because baloo was Crashing Every time i shutdown or restarted system

quad core, 6 gb ram, 500 gb hdd, all updates via opensuse.org (ver 13.1)

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File (baloo_file), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f4bdf001799 in QRasterWindowSurface::~QRasterWindowSurface (this=0x1c64b50, __in_chrg=<optimized out>) at painting/qwindowsurface_raster.cpp:117
#7  0x00007f4bdf001819 in QRasterWindowSurface::~QRasterWindowSurface (this=0x1c64b50, __in_chrg=<optimized out>) at painting/qwindowsurface_raster.cpp:121
#8  0x00007f4bdf019b2c in QWidgetBackingStore::~QWidgetBackingStore (this=0x1d40ad0, __in_chrg=<optimized out>) at painting/qbackingstore.cpp:909
#9  0x00007f4bdee568f9 in QWidgetBackingStoreTracker::destroy (this=0x1d26490) at kernel/qwidget.cpp:225
#10 0x00007f4bdee56a99 in QWidgetPrivate::deleteExtra (this=this@entry=0x1d2d9d0) at kernel/qwidget.cpp:1833
#11 0x00007f4bdee56cad in QWidgetPrivate::~QWidgetPrivate (this=0x1d2d9d0, __in_chrg=<optimized out>) at kernel/qwidget.cpp:365
#12 0x00007f4bdee56f39 in QWidgetPrivate::~QWidgetPrivate (this=0x1d2d9d0, __in_chrg=<optimized out>) at kernel/qwidget.cpp:370
#13 0x00007f4be1e18c35 in cleanup (pointer=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:62
#14 ~QScopedPointer (this=0x1d2d978, __in_chrg=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:100
#15 QObject::~QObject (this=0x1d2d970, __in_chrg=<optimized out>) at kernel/qobject.cpp:816
#16 0x00007f4bdee5f6ac in QWidget::~QWidget (this=0x1d2d970, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1554
#17 0x00007f4be063f970 in ~XSyncBasedPoller (this=0x1d2d970, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.14.4/kutils/kidletime/xsyncbasedpoller.cpp:100
#18 XSyncBasedPoller::~XSyncBasedPoller (this=0x1d2d970, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.14.4/kutils/kidletime/xsyncbasedpoller.cpp:102
#19 0x00007f4be063f7fd in ~XSyncBasedPollerHelper (this=0x1d2c0b0, __in_chrg=<optimized out>) at /usr/src/debug/kdelibs-4.14.4/kutils/kidletime/xsyncbasedpoller.cpp:33
#20 destroy () at /usr/src/debug/kdelibs-4.14.4/kutils/kidletime/xsyncbasedpoller.cpp:38
#21 0x00007f4bde124059 in __run_exit_handlers () from /lib64/libc.so.6
#22 0x00007f4bde1240a5 in exit () from /lib64/libc.so.6
#23 0x00007f4bde10dbec in __libc_start_main () from /lib64/libc.so.6
#24 0x000000000040a069 in _start ()

Possible duplicates by query: bug 330038, bug 327798, bug 320766, bug 295018, bug 294229.

Reported using DrKonqi
Comment 1 Christoph Feck 2015-02-12 09:51:08 UTC
Can you please confirm (by adding a comment to this bug report) that you can read comments added by bug triagers here?
Comment 2 Christoph Feck 2015-02-16 18:18:14 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2015-02-24 19:47:58 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Christoph Feck 2015-05-15 12:26:43 UTC
No response, changing status.
Comment 5 Myriam Schweingruber 2016-12-29 08:35:34 UTC
*** Bug 374186 has been marked as a duplicate of this bug. ***