GNOME Bugzilla – Bug 557792
Movement of list causes program freeze (window manager related?)
Last modified: 2018-07-02 10:38:19 UTC
Please describe the problem: Program becomes unresponsive if date selector is open for a list item that is being moved up or down in the list. Steps to reproduce: 0. given: 2 or more items under the 'Overdue' subheading 1. Check the box to complete item 1 2. while the change is processing, and the item has not yet been removed from the list, click to open the date selector for the second item. 3. when the first item finishes processing, the first item disappears, the second item moves up in the list, and you are left with a blank grey box where the date selector used to appear. At this point, the program becomes unresponsive. By right-clicking on the task bar icon and choosing 'about', you can restore functionality to the progam. (Notably, choosing other options like 'refresh tasks', or 'preferences' does not restore functionality) Actual results: Expected results: Does this happen every time? Reproducible every time on Ubuntu 8.04, using RTM backend, GNOME and mostly default settings. Other information: Feel free to contact me with questions or if more information is required. Thanks for this great little app.
Yow, this one sucks. Good find!
This one may not get fixed for 0.1.8, as I'm not entirely sure how to fix it. Downgrading to Major, though, since there is the one workaround.
Sorry for the spam. Setting milestone to 0.1.10 aka "Crashes fixed Release"
I can't reproduce this bug. However I see something different. Instead of getting the gray box, the second task is marked as done. This doesn't make sense because the second task wasn't edited at all.
Seeing same behavior as Mario, can't reproduce the hang anymore. I'm using Metacity these days, maybe I was using Compiz in the past, or maybe it's been fixed.
Created attachment 162342 [details] [review] proposed patch for task toggling (In reply to comment #4) > I can't reproduce this bug. > > However I see something different. Instead of getting the gray box, the second > task is marked as done. This doesn't make sense because the second task wasn't > edited at all. I think this because of the "toggled" variable (see commit f7cc72b3ead56ebc46eb5d401342641f7da6f777), it'll be set to true when the first task is toggled and the "taskBeingEdited" variable will be set to another task. Once the first task is deleted from the tree, one of the "Edited" or "EditingCanceled" (I don't remember) will be triggered and evaluate the associating if statement. In short, deactivating the selected, yet the wrong, task. I think this patch should help preventing this problem. (In reply to comment #5) > Seeing same behavior as Mario, can't reproduce the hang anymore. > > I'm using Metacity these days, maybe I was using Compiz in the past, or maybe > it's been fixed. I can reproduce the freezing problem on Windows XP SP3, using the git version. This kinda rules out window managers leaving us to a buggy Tasque or a buggy GTK#. What do you think?
Created attachment 162686 [details] [review] proposed "patch" for the freezing problem After some extensive testing, it looks like the problem is on the side of GTK#. Adding a handler to EditingStarted event for a CellRendererCombo seems to cause the freezing problem, regardless of the implementation inside the handler. So I came with this ugly patch of an ugly hack, but it does work, on Windows at least. By the way, opening About dialog doesn't resolve the freezing issue on Windows.
I have the same problem. I use compiz and aurora-gtk2 engine, if that matters.
Review of attachment 162342 [details] [review]: Patch has been applied in git master.
Tasque is not under active development anymore and has not seen code changes for five years, and both its mailing lists have seen their last activity three years ago at https://mail.gnome.org/archives/tasque-list/ and https://groups.google.com/forum/#!forum/tasky Its codebase has been archived: https://gitlab.gnome.org/Archive/tasque/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.