Bug#962615: sylfilter: glib error prevent filter working
control: tags -1 - a11y control: notfound -1 0.8-6 control: severity -1 important Not sure what reason, sylfilter's db was corrupt and it was not introduced in this version, and it doesn't always happen so downgrade severity. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#962615: sylfilter: glib error prevent filter working
Hi,
On Sat, 13 Jun 2020 12:13:59 +0200 Xavier Brochard
wrote:
snip
> xfilter_bayes_db_init: opening db: /home/anne/.sylfilter/junk.db
>
> ** (process:21314): WARNING **: 12:04:05.137: Cannot open database:
> /home/anne/.sylfilter/junk.db
> Database initialization error.
I've tried to check source code sylfilter 0.8.
It seems that this error is occurerd in QDBM layer. (In QDBM, system call may
be failed)
Here is the call tree of this situation:
main(src/sylfilter.c)
=> xfilter_bayes_db_init(lib/filters/bayes-filter.c)
==> xfilter_kvs_open(lib/filter-kvs.c)
===> ke.open
> qdbm_open = dpopen (QDBM layer)
"** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127"
means that error was caused at src/sylfilter.c.
dbpath = xfilter_utils_get_base_dir();
if (xfilter_bayes_db_init(dbpath) < 0) {
fprintf(stderr, "Database initialization error.\n");
xfilter_done();
return 127;
}
So, as you mentioned "the problem is with db access.", it has database error.
But the reason why it has happend was not uncertain.
Hmm...
Regards,
Bug#962615: sylfilter: glib error prevent filter working
Hello Le 11.06.2020 01:18, Hideki Yamane a écrit : On Wed, 10 Jun 2020 20:02:27 +0200 Xavier Brochard wrote: Sylfilter doesn't work anymore in Sylpheed. Sylpheed log contains these lines each time sylfilter is launched: GLib-DEBUG: posix_spawn avoided (fd close requested) ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127 Which logfile, could you provide a filename, please? It is Sylpheed internal log from menu "Tools/Connexion log" * What led up to the situation? System update, but user notify me long time after problem start. From which version to version? I can't really answer, because the bug happened long time before the user ask for help. I guess it was on January. There were no Sylfilter or Sylpheed update. Could you try to invoke sylpfiter with terminal and get output like below? (...) Here it is, the problem is with db access. anne@gentille:~$ sylfilter -c email_test.eml -d xfilter_bayes_db_init: init database xfilter_bayes_db_init: path: /home/anne/.sylfilter xfilter_bayes_db_init: making directory: /home/anne/.sylfilter xfilter_bayes_db_init: opening db: /home/anne/.sylfilter/junk.db ** (process:21314): WARNING **: 12:04:05.137: Cannot open database: /home/anne/.sylfilter/junk.db Database initialization error. And how about trying to rename ~/.sylfilter directory and create new db temporary? Does it work? Yes it works. I'm sorry, I should have tried it before. --- Librement, Xavier Brochard xav...@alternatif.org La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre Rosnay)
Bug#962615: sylfilter: glib error prevent filter working
Hi, On Wed, 10 Jun 2020 20:02:27 +0200 Xavier Brochard wrote: > Sylfilter doesn't work anymore in Sylpheed. > Sylpheed log contains these lines each time sylfilter is launched: > GLib-DEBUG: posix_spawn avoided (fd close requested) > ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127 Which logfile, could you provide a filename, please? >* What led up to the situation? > System update, but user notify me long time after problem start. From which version to version? Could you try to invoke sylpfiter with terminal and get output like below? $ sylfilter -c lspci.txt -d xfilter_bayes_db_init: init database xfilter_bayes_db_init: path: /home/henrich/.sylfilter xfilter_bayes_db_init: making directory: /home/henrich/.sylfilter xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/junk.db xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/clean.db xfilter_bayes_db_init: opening data file: /home/henrich/.sylfilter/status.dat filter-manager.c: xfilter_manager_run: run filter chain exec filter: text-content [content filter] in data type: message/rfc822 exec filter: text-content: status 3: out data type: text/plain exec filter: wordsep [content filter] in data type: text/plain exec filter: wordsep: status 3: out data type: text/plain exec filter: bayes-learn-clean [content filter] in data type: text/plain learning clean message xfilter_update_status: writing status to file xfilter_update_status: done exec filter: bayes-learn-clean: status 4: out data type: text/plain xfilter_bayes_db_init: close database And how about trying to rename ~/.sylfilter directory and create new db temporary? Does it work? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#962615: sylfilter: glib error prevent filter working
Package: sylfilter Version: 0.8-6 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, Sylfilter doesn't work anymore in Sylpheed. Sylpheed log contains these lines each time sylfilter is launched: GLib-DEBUG: posix_spawn avoided (fd close requested) ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127 * What led up to the situation? System update, but user notify me long time after problem start. * What exactly did you do (or not do) that was effective (or ineffective)? Other junk mail filter (Bogofilter) works -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylfilter depends on: ii libc6 2.28-10 ii libglib2.0-0 2.58.3-2+deb10u2 ii libqdbm14 1.8.78-9+b1 ii libsqlite3-0 3.27.2-3 ii libsylfilter0 0.8-6 sylfilter recommends no packages. sylfilter suggests no packages. -- no debconf information
