[frameworks-baloo] [Bug 385213] New: Baloo crashed when I tried to delete files in the home directory of another user.

[tejzpr]

https://bugs.kde.org/show_bug.cgi?id=385213

Bug ID: 385213
Summary: Baloo crashed when I tried to delete files in the home
directory of another user.
Product: frameworks-baloo
Version: 5.38.0
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: ***@gmail.com
Reporter: ***@gmail.com
Target Milestone: ---

Application: baloo_file (5.38.0)

Qt Version: 5.7.1
Frameworks Version: 5.38.0
Operating System: Linux 4.10.0-35-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

I was trying to delete files in the home directory of another user.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f241b0488c0 (LWP 1968))]

Thread 2 (Thread 0x7f2411a24700 (LWP 1978)):
#0 0x00007f241912170d in poll () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007f241611a38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f241611a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f2419d4a75b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007f2419cf50ba in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007f2419b24f64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007f241b15b735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x00007f2419b29b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007f24187b16ba in start_thread (arg=0x7f2411a24700) at
pthread_create.c:333
#9 0x00007f241912d3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f241b0488c0 (LWP 1968)):
[KCrash Handler]
#6 0x00007f241905b428 in __GI_raise (sig=***@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007f241905d02a in __GI_abort () at abort.c:89
#8 0x00007f241909d7ea in __libc_message (do_abort=2,
fmt=***@entry=0x7f24191b6e98 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/posix/libc_fatal.c:175
#9 0x00007f24190a6dfb in malloc_printerr (ar_ptr=0x7f24193eab20 <main_arena>,
ptr=0x26a21b0, str=0x7f24191b3c35 "corrupted size vs. prev_size", action=3) at
malloc.c:5006
#10 _int_free (av=0x7f24193eab20 <main_arena>, p=<optimized out>, have_lock=0)
at malloc.c:4014
#11 0x00007f24190aa53c in __GI___libc_free (mem=<optimized out>) at
malloc.c:2968
#12 0x0000000000421ef0 in ?? ()
#13 0x000000000041fbf6 in ?? ()
#14 0x00007f2419d221f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x0000000000426994 in ?? ()
#16 0x00007f2419d221f6 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f2419d9a99e in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f2419d2e3eb in QSocketNotifier::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f2419cf70bb in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f2419d4abfd in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f241611a197 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f241611a3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f241611a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f2419d4a73f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007f2419cf50ba in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007f2419cfd6cc in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000000000040aacb in ?? ()
#28 0x00007f2419046830 in __libc_start_main (main=0x40a640, argc=1,
argv=0x7fffa07874a8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffa0787498) at ../csu/libc-start.c:291
#29 0x000000000040ab89 in _start ()

Possible duplicates by query: bug 385056, bug 384860, bug 384737, bug 381268,
bug 381213.

Reported using DrKonqi

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=385213

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #1 from Nate Graham <***@kde.org> ---
*** Bug 385287 has been marked as a duplicate of this bug. ***

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=385213

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Summary|Baloo crashed when I tried |baloo_file crashed with
|to delete files in the home |malloc error (""corrupted
|directory of another user. |size vs. prev_size") when I
| |tried to delete files in
| |the home directory of
| |another user
CC| |***@kde.org
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO

--- Comment #2 from Nate Graham <***@kde.org> ---
Can you reproduce this issue with KDE Frameworks 5.52 or later?

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=385213

--- Comment #3 from Bug Janitor Service <bug-***@kde.org> ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!