scratch stuck with a vertical bar in the middle
Bug #1467564 reported by
Reginald San
on 2015-06-22
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Scratch |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After opening Scratch, I chose "New File" and this happened. There seems to be a vertical bar "|" in the top-center of what's supposed to be a blank text file.
While this is happening, the window where text should go is unresponsive. The buttons of Scratch are still working, by the way.
I have attached something of how it looks like.
Reginald San (aboynamedred) wrote : | #1 |
Daniel Fore (danrabbit)
on 2015-06-22
affects: | elementaryos → scratch |
Daniel Fore (danrabbit) wrote : | #2 |
Changed in scratch: | |
milestone: | none → loki-beta1 |
status: | New → Confirmed |
Cody Garver (codygarver)
on 2015-09-16
Changed in scratch: | |
importance: | Undecided → Medium |
Selwyn Orren (selwyn) wrote : | #3 |
Thanks Daniel,
I noticed in my home folder tat scratch-text-editor as well as the unsaved folder inside it was all root. I changed teh ownership of scratch-text-editor to my user-name and it all works fine now.
Thanks for the help
Daniel Fore (danrabbit)
on 2016-04-02
Changed in scratch: | |
milestone: | loki-beta1 → none |
I have encountered this bug in Loki beta 2.
(But it will appear loading image instead of the vertical bar)
This might still be affected.
weeix (weeaix) wrote : | #5 |
To post a comment you must log in.
Okay I finally figured out how to reproduce this issue! The problem is that "~/.local/ share/scratch- text-editor/ unsaved" becomes owned by root. Likely this is because someone is running Scratch for the first time as root doing some kind of modification, then they come back trying to use it normally. To reproduce simply:
1. Make sure you don't have "~/.local/ share/scratch- text-editor/ unsaved" such as you wouldn't on a clean install
2. Run scratch as root. You don't need to have any unsaved files (in fact it's simpler if you don't)
3. Run scratch as a user.