Bug 373028 - Rocs is not responding
Summary: Rocs is not responding
Status: RESOLVED WORKSFORME
Alias: None
Product: Rocs
Classification: Applications
Component: visual graph editor (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Rocs Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-28 13:07 UTC by Sean
Modified: 2022-11-26 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Graphical representation of Bug. (87.53 KB, image/png)
2016-11-28 13:07 UTC, Sean
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sean 2016-11-28 13:07:57 UTC
Created attachment 102496 [details]
Graphical representation of Bug.

## Output of uname -a 

Linux glassplanet 4.8.9-1-MANJARO #1 SMP PREEMPT Fri Nov 18 19:17:47 UTC 2016 x86_64 GNU/Linux

## OS : KDE/Manjaro branch of Netrunner

## ROCS version 2.1.50; KDE Framework 5.28.0 QT 5.7.0, xcb Window System

## Problem

In the visual graph editor, the application doesn't respond to mouse events.

## Steps to reproduce: 

1. Start Rocs

2. Make a graph with 6+ nodes

3. Change the edge style (e.g. a new color)

4. Try to add a new edge.
- Click on one node
- Drag to another node

At this point, some nodes will be "frozen" that the edge will not be added. You can't even move the "frozen" node around.

See the attached picture, starting from the root (node 0) the first node at the top is frozen (green circle). I can add edges among the bottom nodes as i wish, but the first top node doesn't respond. Clicking on it also doesn't bring the orange highlighting around it.

This is a bit of inconvenience.
Comment 1 Sean 2016-11-28 13:10:17 UTC
> the top is frozen (green circle).

Orange, sorry.
Comment 2 Sean 2016-11-28 13:12:24 UTC
ALSO; PS: no usable output when started from command line - i.e. no error message.
Comment 3 Justin Zobel 2022-10-27 02:48:20 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-11 05:19:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-26 05:16:53 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!