Bug #9347

Investigate if Seahorse has hardcoded timeouts causing transient network issues

Added by anonym 2015-05-05 14:38:03 . Updated 2015-10-30 05:46:16 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.7
Start date:
2015-05-05
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The issues referred to are those in Bug #9095#note-9.

Subtasks

History

#1 Updated by anonym 2015-05-05 14:38:18

  • Status changed from New to Confirmed

#2 Updated by anonym 2015-05-05 14:38:54

  • blocks #8538 added

#3 Updated by intrigeri 2015-06-04 21:35:56

Seahorse uses libsoup, iirc => I would start with “git grep soup_” or similar.

#4 Updated by anonym 2015-07-01 11:54:41

  • Target version changed from Tails_1.4.1 to Tails_1.5

#5 Updated by anonym 2015-08-03 10:59:34

  • Target version changed from Tails_1.5 to Tails_1.6

#6 Updated by anonym 2015-09-16 12:33:34

  • blocked by deleted (#8538)

#7 Updated by anonym 2015-09-16 12:34:14

  • blocks #8538 added

#8 Updated by anonym 2015-09-22 15:03:11

  • Target version changed from Tails_1.6 to Tails_1.7

#9 Updated by intrigeri 2015-10-20 03:49:08

#10 Updated by anonym 2015-10-30 05:45:31

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)

I’ve had a quick look, and… GNOME’s C code is just not something that I find easy to read. Sorry, I won’t do this. Besides, it seems like a waste of time since Seahorse has been behaving really well on Jenkins lately.