Inconsistent Behavior with using phy with multiple users on same server
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 430
- Forks
- 187
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 2
Description
We seem to have an odd issue where one user using phy will not get the two terminal windows to show in the GUI while another user on the same system will get the two terminal windows to populate but nothing else will populate in the GUI. A third user with a different installation of phy (local to his account) has everything working. Is there a simple way to track what init files are being called to see where the differences are in loading up phy?
-smb
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing phy startup with the affected users and comparing the installations that show different GUI behavior. Trace which initialization files are called for each user and record the differences in terminal-window and GUI population. Done means the relevant per-user or installation difference is identified and the inconsistent startup behavior has a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100