Bug #8423

Document that Pidgin can't open an account with Persistence enabled in Read-only mode

Added by emmapeel 2014-12-12 08:56:43 . Updated 2015-03-22 12:11:52 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.3.1
Start date:
2014-12-12
Due date:
% Done:

100%

Feature Branch:
bitingbird:doc/8423-bug_pidgin_persist
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Instant Messaging
Deliverable for:

Description

reported by user, confirmed by me.

Pidgin fails to load any previous accounts if booting Tails in Read-only mode with Persistence enabled.

Also doesn’t load the defaults accounts. Just comes empty (no nick randomizer neither)

I know is a corner case, but if its not easy we can at least document it.

Subtasks

Related issues

Related to Tails - Bug #8465: Pidgin can't open an account with Persistence enabled in Read-only mode Rejected 2014-12-19
Related to Tails - Feature #8419: Point back from persistence features to the relevant tools Resolved 2014-12-11

History

#1 Updated by intrigeri 2014-12-16 21:22:08

  • QA Check deleted (Info Needed)

I agree it could be worth documenting. I don’t think it’s worth a code ticket with higher than low priority.

#2 Updated by BitingBird 2014-12-19 14:08:46

  • Subject changed from Pidgin can't open my accounts with Persistence enabled in Read-only mode to Document that Pidgin can't open an accounts with Persistence enabled in Read-only mode
  • Type of work changed from Discuss to Documentation

Add a line in known issue.

#3 Updated by BitingBird 2014-12-19 14:09:22

  • Subject changed from Document that Pidgin can't open an accounts with Persistence enabled in Read-only mode to Document that Pidgin can't open an account with Persistence enabled in Read-only mode

#4 Updated by BitingBird 2014-12-19 14:10:00

  • related to Bug #8465: Pidgin can't open an account with Persistence enabled in Read-only mode added

#5 Updated by intrigeri 2014-12-19 14:21:49

  • Priority changed from Low to Normal

#6 Updated by sajolida 2014-12-24 13:17:06

What about a

section in /doc/anonymous_internet/pidgin instead?

#7 Updated by intrigeri 2014-12-24 15:37:01

> What about a

section in /doc/anonymous_internet/pidgin instead?

I agree it’s better than known issues, which is maybe too general.

Now, I really don’t know what would be best between:

  • doc/anonymous_internet/pidgin, since it’s about Pidgin
  • the relevant section on doc/first_steps/persistence/configure, since it affects only Pidgin users who have persistence enabled

No strong feelings.

#8 Updated by sajolida 2014-12-25 15:48:10

> * doc/anonymous_internet/pidgin, since it’s about Pidgin
> * the relevant section on doc/first_steps/persistence/configure, since it affects only Pidgin users who have persistence enabled

We already have a bug related to a persistent feature for Claws in
https://tails.boum.org/doc/first_steps/persistence/configure#claws_mail
so let’s put it there as well.

Note that this is related to Feature #8419.

#9 Updated by sajolida 2014-12-25 15:48:41

  • related to Feature #8419: Point back from persistence features to the relevant tools added

#10 Updated by sajolida 2014-12-30 15:44:00

I’ve seen that this has been added to the agenda for the January meeting but it has a Documentation type of work.

  • Aren’t we statisfied with the proposal made until no which is adding a bug section in persistence/configure#claws_mail?
  • What else needs to be discussed?

#11 Updated by sajolida 2015-01-03 23:48:55

During the January meeting:

  • We confirmed that the read-only option for persistence is a best-effort feature. So documenting the bug looks good enough for now.
  • Real fix and automated tests for the read-only mode are more than welcome.

https://tails.boum.org/contribute/meetings/201501/

#12 Updated by BitingBird 2015-01-31 12:39:43

  • Status changed from Confirmed to In Progress
  • Assignee set to BitingBird
  • Target version set to Tails_1.3
  • % Done changed from 0 to 40

#13 Updated by BitingBird 2015-01-31 12:46:49

  • Assignee changed from BitingBird to sajolida
  • % Done changed from 40 to 50
  • QA Check set to Ready for QA
  • Feature Branch set to bitingbird:doc/8423-bug_pidgin_persist

Built, looks good. Please review.

#14 Updated by BitingBird 2015-02-10 01:15:59

  • Priority changed from Normal to Elevated

It’s just a small note, review could be quick.

#15 Updated by intrigeri 2015-02-10 14:02:24

  • Assignee changed from sajolida to BitingBird
  • “in Read-only mode with Persistence enabled” is unclear: Tails is always in read-only mode, so in this case it’s only for persistence; besides, we don’t use the “read-only mode” terminology, see doc/first_steps/persistence/use.
  • the description of the symptom seems overly detailed: IMO we should just say that it’s broken and not supported in that context
  • generally, a bug div should link to the ticket about resolving the bug (Bug #8465)

#16 Updated by intrigeri 2015-02-10 14:02:58

  • QA Check changed from Ready for QA to Dev Needed

#17 Updated by BitingBird 2015-02-10 14:20:10

  • Target version changed from Tails_1.3 to Tails_1.3.2

#18 Updated by BitingBird 2015-03-03 12:08:04

  • Assignee changed from BitingBird to intrigeri
  • QA Check changed from Dev Needed to Ready for QA

Corrected as suggested, built the wiki, everything looks good. Please merge :)

#19 Updated by intrigeri 2015-03-03 12:37:11

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Applied in changeset commit:62e8766589ec76e153b01eb1d84ea897554965b8.

#20 Updated by intrigeri 2015-03-03 12:38:39

  • Assignee deleted (intrigeri)
  • QA Check changed from Ready for QA to Pass

Added a HTML/CSS styling fix on top, merged, thanks!

#21 Updated by BitingBird 2015-03-22 12:11:52

  • Target version changed from Tails_1.3.2 to Tails_1.3.1