FS#72609 - [taskwarrior-tui] crash at start, for some configuration settings

Attached to Project: Community Packages
Opened by shilka (shilka) - Tuesday, 02 November 2021, 05:05 GMT
Last edited by Orhun Parmaksız (orhun) - Saturday, 20 November 2021, 08:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Orhun Parmaksız (orhun)
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:
crashed when run taskwarrior-tui in shell.

Error message:
Backtrace (most recent call first):
File "<unknown>", line 0, in __libc_start_main

The application panicked (crashed).
called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }
in src/pane/project.rs, line 143
thread: main


Additional info:
* package version(s)
0.14.6-1

* config and/or log files etc.
My taskrc only define location and theme:
data.location=~/Documents/NM/.task
include /usr/share/doc/task/rc/dark-gray-blue-256.theme

* link to upstream bug report, if any

Steps to reproduce:
run taskwarrior-tui in shell
This task depends upon

Closed by  Orhun Parmaksız (orhun)
Saturday, 20 November 2021, 08:54 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream related bug.
Comment by Alexander F. Rødseth (xyproto) - Friday, 12 November 2021, 11:08 GMT
I'm unable to reproduce the issue.

When I first installed taskwarrior-tui, then created a ~/.taskrc file with:

echo 'data.location=~/.task' > .taskrc

Then made sure the .task directory exists with:

mkdir .task

And then run taskwarrior-tui with:

taskwarrior-tui

Then it worked here, no crashes.

1. Does ~/Documents/NM/.task exist?
2. Does it work if you don't include the theme?
Comment by shilka (shilka) - Saturday, 13 November 2021, 09:56 GMT
Sorry for lack of info.
For Question 1 and 2, the answer are YES.
On my computer he task command and vit(another CLI GUI for taskwarrior) works fine, but taskwarrior-tui not.
Comment by Orhun Parmaksız (orhun) - Saturday, 13 November 2021, 17:01 GMT
Isn't it more appropriate to report this to upstream? I'm not sure if it's really a packaging problem.
Comment by shilka (shilka) - Friday, 19 November 2021, 03:37 GMT
I've no idea. But I'll try submitting the bug report to upstream. Thanks.

Loading...