Bug #11984

Error message when starting Totem: "Failed to get bookmarks list: library routine called out of sequence"

Added by elouann 2016-11-21 15:53:31 . Updated 2016-12-14 20:10:51 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Start date:
2016-11-21
Due date:
% Done:

100%

Feature Branch:
bugfix/11984-totem-apparmor
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Since Tails 2.7, an error appears whent starting Totem:

“Failed to get bookmarks list: library routine called out of sequence”


Subtasks


Related issues

Related to Tails - Bug #11578: Totem AppArmor profile allows opening OTR private key Resolved 2016-07-19
Has duplicate Tails - Bug #11978: totem player error on start after tails 2.7 upgrade Duplicate 2016-11-21

History

#1 Updated by elouann 2016-11-25 10:29:26

  • has duplicate Bug #11978: totem player error on start after tails 2.7 upgrade added

#2 Updated by intrigeri 2016-11-27 17:26:46

  • Assignee set to intrigeri
  • Priority changed from Normal to Elevated
  • Target version set to Tails_2.9.1
  • % Done changed from 100 to 0
  • Type of work changed from User interface design to Code

elouann: next time, please reassign such a regression to a member of the Foundations team. One should not rely on the fact we track all Redmine. Thanks :)

#3 Updated by elouann 2016-11-29 18:07:13

Ok I got it, thanks

#4 Updated by intrigeri 2016-12-04 15:47:07

  • related to Bug #11578: Totem AppArmor profile allows opening OTR private key added

#5 Updated by intrigeri 2016-12-04 15:51:19

(Blame-free) post-mortem: I’ve messed things up when doing Bug #11578, then entirely relied on our automated test suite (that doesn’t expose this bug), and then I guess that bertagaz did exactly the same when he reviewed’n’merged my branch. Along the way from dev to release, apparently nobody ever started Totem without giving it an argument. I don’t think we should rely on anyone doing that manually, given we have pretty good automated tests for Totem, and it makes sense to implicitly rely on them. So I wonder if we should perhaps add a test case about Totem starting from the apps menu without making a fuss (but I’m not sure if it’s easy with Dogtail to check that Totem didn’t display any error message); bertagaz, anonym: if you agree, please file the ticket.

Now I’m going to fix the actual bug.

#6 Updated by intrigeri 2016-12-05 09:23:24

  • Subject changed from Error message when starting Totem : "Failed to get bookmarks list: library routine called out of sequence" to Error message when starting Totem: "Failed to get bookmarks list: library routine called out of sequence"
  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to anonym
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

Tested locally (just starting Totem), works. No regression on Jenkins: https://jenkins.tails.boum.org/view/Tails_ISO/job/test_Tails_ISO_bugfix-11984-totem-apparmor/1/

#7 Updated by anonym 2016-12-05 14:44:34

  • Feature Branch set to bugfix/11984-totem-apparmor

#8 Updated by anonym 2016-12-05 19:52:32

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check changed from Ready for QA to Pass

Fix works => merged!

intrigeri wrote:
> Along the way from dev to release, apparently nobody ever started Totem without giving it an argument.

I’m not surprised — the Totem “main” window is truly mystifying, so I expect users to only start it through file associations in GNOME Files (or the command line).

> So I wonder if we should perhaps add a test case about Totem starting from the apps menu without making a fuss (but I’m not sure if it’s easy with Dogtail to check that Totem didn’t display any error message);

The error message will block any further action so if we make a test using Totem’s UI to add a video and then watch it, we are good.

> bertagaz, anonym: if you agree, please file the ticket.

Feature #12019

#9 Updated by anonym 2016-12-14 20:10:51

  • Status changed from Fix committed to Resolved