View Issue Details

IDProjectCategoryView StatusLast Update
0005547DUMoBugpublic2019-07-04 23:55
ReporterwolfAssigned ToKyle_Katarn 
PrioritynormalSeverityminorReproducibilitysometimes
Status acknowledgedResolutionopen 
PlatformOSWindows 10 64-bitOS Version1809
Product Version2.17.5 
Target VersionFixed in Version 
Summary0005547: Sporadic strange start behaviour of DUMo
DescriptionDUMo sometimes has a strange startup behaviour. While most of the times it works as expected, a few times it seems only to start normally. But in fact it's then unusable. Although its buttons are displayed as usable, they're not. Clicking on them has no effect. It also doesn't perform auto-check. In such a situation, I may repeat this check request as often I like, always with the same result of no effect.

I observed this behaviour with several versions in the past two months, not only the current version.
Additional InformationWork-around for the described situation is to close DUMo normally. This menu item works as expected even in this situation. Then start DUMo again. I never observed that this start behaviour returned the same day when closing DUMo ordinarily and then restarting it another time. This new start works after DUMo closing has finished. No need to wait some time. So I guess that there is some internal race condition concerned appearing seldom, of time to time.
TagsNo tags attached.

Relationships

related to 0005173 resolvedKyle_Katarn DUMo DUMo shall not (auto)check while licence has not been checked 
related to 0005262 resolvedKyle_Katarn SUMo Unable to check until restart if no answer to licence check 
related to 0005172 resolvedKyle_Katarn SUMo SUMo shall not (auto)check while licence has not been checked 

Activities

Kyle_Katarn

2019-06-17 21:16

administrator   ~0003484

Last edited: 2019-06-17 21:18

View 2 revisions

Likely a side effect of 0005172 / 0005173 (change on DUMo and SUMo) with DUMo not being covered by 0005262 (SUMo only)

To confirm : please next time when problem happens, click "check" 2-3 times, open logs and copy it here.

Issue History

Date Modified Username Field Change
2019-06-17 12:41 wolf New Issue
2019-06-17 21:00 Kyle_Katarn Assigned To => Kyle_Katarn
2019-06-17 21:00 Kyle_Katarn Status new => acknowledged
2019-06-17 21:16 Kyle_Katarn Status acknowledged => feedback
2019-06-17 21:16 Kyle_Katarn Note Added: 0003484
2019-06-17 21:16 Kyle_Katarn Relationship added related to 0005173
2019-06-17 21:16 Kyle_Katarn Relationship added related to 0005262
2019-06-17 21:17 Kyle_Katarn Relationship added related to 0005171
2019-06-17 21:17 Kyle_Katarn Relationship deleted related to 0005171
2019-06-17 21:17 Kyle_Katarn Relationship added related to 0005172
2019-06-17 21:18 Kyle_Katarn Note Edited: 0003484 View Revisions
2019-07-04 23:55 Kyle_Katarn Status feedback => acknowledged