Bug 102925

Summary:	telepathy-logger makes Polari crash because of archived logs
Product:	Telepathy	Reporter:	Mildred Ki'Lya <mildred-bug.freedesktop>
Component:	logger	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	critical
Priority:	medium
Version:	0.8
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	logs that cause the crash

Description Mildred Ki'Lya 2017-09-21 10:14:04 UTC

Created attachment 134404 [details]
logs that cause the crash

Polari issue: https://gitlab.gnome.org/GNOME/polari/issues/2

We get a crash because of logs files in ~/.purple/logs that are incorrect XML:

/home/mildred/.local/share/TpLogger/logs/idle_irc_mildred3/chatrooms/#fdn/20170921.log:27: parser error : xmlParseCharRef: invalid xmlChar value 27
'normal'>Tu lis ce que tu veux, c&apos;est ce que t&apos;écris qui compte&#x1b;
                                                                               ^

This causes a crash in Polari. Attaching offending log files.

Comment 1 diane 2017-09-21 17:52:02 UTC

Hi,

Could you get the user to rerun the test with debugging symbols installed? And once you have them could you attach them here?

The stacktrace I saw on the GNOME gitlab site didn't seem to have them.

Also does the new gitlab site reuse any of the older GNOME bugzilla account information or do would I need to register a new account?

Comment 2 Jan Tojnar 2018-05-07 18:58:28 UTC

I am getting the following trace when I try to load a log containing  &#x1b; entity in a message:

Core was generated by `/nix/store/128imqqscad6gy921s5jqarwsrydqr1f-polari-3.28.0/bin/polari --gapplica'.
Program terminated with signal SIGSEGV, Segmentation fault.

#0  tpl_log_iter_xml_get_events (iter=<optimized out>, num_events=5, error=<optimized out>) at log-iter-xml.c:88
#1  0x00007f11a0035a91 in tpl_log_walker_fill_cache_async_thread (simple=0x5131d00, object=<optimized out>, cancellable=<optimized out>) at log-walker.c:310
#2  0x00007f11d7e31ca4 in run_in_thread () from /nix/store/azxcljz7prb2qm36andkfc7zqzccb4ks-glib-2.56.0/lib/libgio-2.0.so.0
#3  0x00007f11d7e1cf46 in io_job_thread () from /nix/store/azxcljz7prb2qm36andkfc7zqzccb4ks-glib-2.56.0/lib/libgio-2.0.so.0
#4  0x00007f11d7e449a6 in g_task_thread_pool_thread () from /nix/store/azxcljz7prb2qm36andkfc7zqzccb4ks-glib-2.56.0/lib/libgio-2.0.so.0
#5  0x00007f11d78bd490 in g_thread_pool_thread_proxy () from /nix/store/azxcljz7prb2qm36andkfc7zqzccb4ks-glib-2.56.0/lib/libglib-2.0.so.0
#6  0x00007f11d78bcac5 in g_thread_proxy () from /nix/store/azxcljz7prb2qm36andkfc7zqzccb4ks-glib-2.56.0/lib/libglib-2.0.so.0
#7  0x00007f11d64ec5a7 in start_thread (arg=0x7f11a1dff700) at pthread_create.c:463
#8  0x00007f11d707a22f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Comment 3 Jan Tojnar 2018-05-07 20:11:37 UTC

I retract my previous comment, I was building from 0.8.0 tarball. 0.8.2 does not crash.

Comment 4 GitLab Migration User 2019-12-03 19:32:51 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-logger/issues/47.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.