Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#60253 - [tilda] segmentation fault at the startup
Attached to Project:
Community Packages
Opened by Muflone (muflone) - Sunday, 30 September 2018, 11:40 GMT
Last edited by Muflone (muflone) - Wednesday, 03 October 2018, 08:49 GMT
Opened by Muflone (muflone) - Sunday, 30 September 2018, 11:40 GMT
Last edited by Muflone (muflone) - Wednesday, 03 October 2018, 08:49 GMT
|
DetailsDescription:
Maybe somehow related to I wasn't able to find the culprit about tilda breakage. The pacman.log of the installed/upgraded package can be found here: http://paste.muflone.com/paste.php?id=38 gdb output: http://paste.muflone.com/paste.php?id=39 Additional info: * tilda 1.4.1-1 Downgrading the package to previous version 1.3.3-4, still segfaults Steps to reproduce: Launch tilda: $ tilda Segmentation fault (core dump created) Even after cleaning the configuration folder (~/.config/tilda), the issue persists. |
This task depends upon
Closed by Muflone (muflone)
Wednesday, 03 October 2018, 08:49 GMT
Reason for closing: Fixed
Additional comments about closing: Now the issue has fixed, maybe related to accountsservice 0.6.53-1 -> 0.6.54-1
Wednesday, 03 October 2018, 08:49 GMT
Reason for closing: Fixed
Additional comments about closing: Now the issue has fixed, maybe related to accountsservice 0.6.53-1 -> 0.6.54-1
Rebuilding the package in my 'dirty' installation still segfaults.
The AUR package tilda-git doesn't segfault.
Thus, if you wish me to tests things, so that you can compare, just say so :-)
Could it be related to accountsservice 0.6.53-1 -> 0.6.54-1 like for
FS#60241?By the way, I'm asking for closing the issue