nautilus-bzr erroneously reports read-only branch

Bug #676771 reported by Jo-Erlend Schinstad
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Incomplete
Undecided
Unassigned

Bug Description

I wanted to move my development from the local machine onto my work machine. I installed bzr and all relevant tools, including nautilus-bzr -- on the work machine and then copied my ~/src from the local machine onto the work machine. That's all I did.

Now, when I open the folder in Nautilus, it sais "Read-Only Branch". I have confirmed that all the files and folders in ~/src are writable by me. Also, Bazaar Explorer doesn't report any problems, and I am able to commit to it, so it really isn't read-only.

I have changed my identity by using another email address on the work machine though, but Bazaar Explorer shows the old one and the new one without any problems.

Revision history for this message
Martin Pool (mbp) wrote :

It seems like we need to work out what (caught exception?) is making nautilus-bzr decide it's a readonly branch. Does it log them?

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

nautilus-bzr doesn't have a concept of readonly branches so this must be coming from elsewhere. Do you perhaps also have groundcontrol or quickly installed?

Changed in bzr-gtk:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.