[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Erik Quaeghebeur]

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

--- Comment #9 from Erik Quaeghebeur  ---
Even if I couldn't find the file that causes the error for me, Igor provided
sufficient material for a developer to seriously look at this issue. That is
what needs to happen at this point.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

--- Comment #8 from Igor Zhuravlov  ---
Hmm, the command "balooctl disable" wipes dir ~/.local/share/baloo/ where
indexed data are stored. So, if disabling and then enabling commands have
fulfilled correctly then full reindexing must start since the index is empty.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Erik Quaeghebeur]

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

--- Comment #7 from Erik Quaeghebeur  ---
It seems all the candidates found by looking at the journal and balooctl
monitor are already indexed[*]; I can't seem to find the culprit :-(

[*] Skipping: /path/to/file.ext Reason: Already indexed

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

--- Comment #6 from Igor Zhuravlov  ---
> “Baloo Index could not be opened”.

It seems like baloo cannot reset to initial state. After "balooctl disable"
ensure:
- files ~/.config/baloo*
- dir ~/.local/share/baloo/
- running baloo* processes
are absent. If not, then try to restart the parent subsystem akonadi too, e.g.
by this:
1) stop akonadi by "akonadictl stop",
2) kill baloo* akonadi* file.so and mysqld processes if there are any,
3) remove files and dir specified above manually,
4) reboot,
5) login as user,
6) check akonadi status by "akonadictl status" and start it manually by
"akonadictl start" if it's not running yet,
7) enable baloo by "balooctl enable",
8) start baloo by "balooctl start".

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Erik Quaeghebeur]

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

--- Comment #5 from Erik Quaeghebeur  ---
(In reply to Igor Zhuravlov from comment #4)
> When journalctl will show baloo_file_extr error, then baloo hangs so the
> last 1-2-3 names displayed by baloo monitor are the best candidates to check
> by command: balooctl index
Ok, I tried this, but I get the response “Skipping: /path/file.ext Reason:
Already scheduled for indexing” or, after stopping/disabling and
enabling/starting baloo again, “Baloo Index could not be opened”.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

--- Comment #4 from Igor Zhuravlov  ---
Erik, to identify problem file the following approach may be used:
1. stop baloo indexing by command: balooctl stop
2. reboot, log in
3. start baloo monitoring in separate console by command: balooctl monitor
4. start system journal monitoring in separate console by command: sudo
journalctl -f
5. start baloo indexing again by command: balooctl start

When journalctl will show baloo_file_extr error, then baloo hangs so the last
1-2-3 names displayed by baloo monitor are the best candidates to check by
command: balooctl index

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Erik Quaeghebeur]

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

Erik Quaeghebeur  changed:

   What|Removed |Added

 CC||kdebugs@equaeghe.nospammail
   ||.net

--- Comment #3 from Erik Quaeghebeur  ---
I think I hit the same issue. In my logs, I find that on every boot, I get

baloo_file_extr[2217]: segfault at 4 ip 003186d5da58 sp 7ffcf0cd6d38
error 4 in libexiv2.so.14.0.0[3186c0+2b7000]

I assume there is some file causing this.

Possible duplicate: Bug 370172

So, please mark as confirmed for 5.37.0. (I'm using Gentoo.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

--- Comment #2 from Igor Zhuravlov  ---
Yet another file getting baloo_file_extractor to crash:

> rpm -qa | egrep 'baloo|lmdb'
baloo5-file-5.26.0-2.1.x86_64
baloo5-widgets-16.08.2-1.1.x86_64
baloo5-5.26.0-2.1.x86_64
lmdb-debugsource-0.9.14-5.4.x86_64
baloo5-imports-5.26.0-2.1.x86_64
baloo5-lang-5.26.0-2.1.noarch
liblmdb-0_9_14-0.9.14-5.4.x86_64
baloo5-kioslaves-5.26.0-2.1.x86_64
liblmdb-0_9_14-debuginfo-0.9.14-5.4.x86_64
baloo5-file-debuginfo-5.26.0-2.1.x86_64
baloo5-tools-5.26.0-2.1.x86_64

> balooctl index 
> /home/myusername/j64-806/addons/labs/labs/examples/data/toolbar.bmp
Ошибка сегментирования (core dumped)

> sudo journalctl -f
...
Sep 13 10:49:58 myhostname kernel: traps: balooctl[31242] general protection
ip:7fc7794549d9 sp:7fff89fa2fe0 error:0 in
liblmdb-0.9.14.so[7fc779449000+13000]traps: 
Sep 13 10:49:59 myhostname systemd-coredump[31244]: Process 31242 (balooctl) of
user 1000 dumped core.

> coredumpctl gdb 31242
...
Core was generated by `balooctl index
/home/myusername/j64-806/addons/labs/labs/examples/data/toolbar.bmp'.
Program terminated with signal SIGSEGV, Segmentation fault.
£0  0x7fc7794549d9 in mdb_txn_commit (txn=0x69616d5f74726174) at mdb.c:3207
3207if (txn == NULL || txn->mt_env == NULL)
[Current thread is 1 (Thread 0x7fc77b93f880 (LWP 31242))]
Missing separate debuginfos, use: zypper install ...
(gdb) l
3202{
3203int rc;
3204unsigned int i;
3205MDB_env *env;
3206
3207if (txn == NULL || txn->mt_env == NULL)
3208return EINVAL;
3209
3210if (txn->mt_child) {
3211rc = mdb_txn_commit(txn->mt_child);
(gdb) p txn
$1 = (MDB_txn *) 0x69616d5f74726174
(gdb) p txn.mt_env
Cannot access memory at address 0x69616d5f74726194
(gdb) bt
£0  0x7fc7794549d9 in mdb_txn_commit (txn=0x69616d5f74726174) at mdb.c:3207
£1  0x7fc7794549f0 in mdb_txn_commit (txn=0x40475b) at mdb.c:3211
£2  0x7fc77b32304e in Baloo::Transaction::commit()
(this=this@entry=0x7fff89fa35b0) at
/usr/src/debug/baloo-5.26.0/src/engine/transaction.cpp:266
£3  0x004087b7 in main(int, char**) (argc=3, argv=) at
/usr/src/debug/baloo-5.26.0/src/tools/balooctl/main.cpp:220
(gdb) quit

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

--- Comment #1 from Igor Zhuravlov  ---
Created attachment 107829
  --> https://bugs.kde.org/attachment.cgi?id=107829=edit
this file crashes baloo_file_extractor

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-baloo] [Bug 384607] baloo_file_extractor SIGSEGV on some files

[Igor Zhuravlov]

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

Igor Zhuravlov  changed:

   What|Removed |Added

Summary|baloo_file_extractor|baloo_file_extractor
   |SIGSEGV on broken JPG   |SIGSEGV on some files

-- 
You are receiving this mail because:
You are watching all bug changes.