Community Packages

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!
Tasklist

FS#78278 - [ario] Segmentation fault when opening

Attached to Project: Community Packages
Opened by Nicola Revelant (nicolarevelant44) - Friday, 21 April 2023, 20:41 GMT
Last edited by Toolybird (Toolybird) - Sunday, 21 May 2023, 21:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Cannot open Ario, upon opening it is killed by a SIGSEGV (Segmentation fault)

Additional info:
* Version: 1.6-2

Steps to reproduce:
Open a terminal emulator, type "/usr/bin/ario" and the program will be killed by a SIGSEGV
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 21 May 2023, 21:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please follow up with upstream.
Comment by Christian Heusel (gromit) - Friday, 21 April 2023, 21:38 GMT
For me the program only segfaults upon closure, but I just installed it to have a look at this issue.
I created a bactrace of the crash I observed and attached it here.

Also I tried just to rebuild the package in a clean chroot but that didn't change anything.
   trace.log (29.7 KiB)
Comment by Toolybird (Toolybird) - Friday, 21 April 2023, 22:14 GMT
I have the exact same experience as @gromit with similar trace. Opens up fine, crashes on exit. But I didn't try to fully set everything up (daemons etc). This needs to be reported upstream so please do so.
Comment by Nicola Revelant (nicolarevelant44) - Saturday, 22 April 2023, 09:51 GMT
Update: I've deleted ~/.config/ario and now it opens correctly, and it closes with SIGSEGV.
Could be an upstream problem.

Loading...