Feature #7963

Replace default desktop background with another

Added by zbuhiazx 2014-09-27 14:04:46 . Updated 2015-03-19 13:29:36 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Start date:
2015-01-22
Due date:
% Done:

100%

Feature Branch:
feature/7963-background-color
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Replace TAILS’ default blue screen of death desktop background with another one of Debian’s default desktop backgrounds already inc;uded in tails.


Subtasks

Feature #8777: Update screenshots on the website if relevant Resolved

100

Feature #8796: Consider using the purple of the logo as background color Rejected

0


History

#1 Updated by zbuhiazx 2014-09-27 14:16:58

*included

#2 Updated by intrigeri 2014-09-27 17:11:57

This ticket might get more positive attention if you explained why we should do that.

#3 Updated by intrigeri 2014-09-27 17:17:17

  • Subject changed from Replace TAILS' default desktop background with another to Replace default desktop background with another
  • Assignee set to zbuhiazx
  • QA Check set to Info Needed
  • Type of work changed from User interface design to Discuss

#4 Updated by mercedes508 2014-09-28 10:14:16

I would say that having a background similar to Debian default would make a little bit less obvious to someone in the room Tails is running, but then comes the Windows 8 camo.

But still the present blue background is too shiny too me and kind of hurt my eyes, which is no security issue but kind of UX.

#5 Updated by intrigeri 2014-09-29 06:02:32

> But still the present blue background is too shiny too me and kind of hurt my eyes, which is no security issue but kind of UX.

I don’t want to see you hurt. May you please try making the background color a bit darker until the point when it is harmless for you? (Oh well, as harmless as using computers can be.)

#6 Updated by mercedes508 2014-09-30 04:59:06

Well, I’ll try to figure it out precisely, but then I find it easier to pick same as Debian default. Wondering if it would be kind of confusing for user used to Debian.

#7 Updated by BitingBird 2014-09-30 10:14:55

Debian default background has the Debian swirl, and we’re not Debian, so I don’t think that’s a good idea. We could use the main color as background instead of the blue, though.

#8 Updated by BitingBird 2014-10-17 09:55:56

  • Status changed from New to Confirmed

#9 Updated by BitingBird 2014-10-17 09:56:18

  • Assignee deleted (zbuhiazx)

#10 Updated by sajolida 2014-11-05 11:15:11

Discussed in the November meeting: https://tails.boum.org/contribute/meetings/201411/

#11 Updated by sajolida 2014-11-05 11:15:27

  • Assignee set to sajolida
  • Type of work changed from Discuss to Research

#12 Updated by intrigeri 2014-11-05 11:22:03

> Discussed in the November meeting: https://tails.boum.org/contribute/meetings/201411/

The decision is: “We agreed on trying to reduce the brightness and
saturation of the current background to be less hurting to the eyes.
While keeping the same blue color.”

#13 Updated by sajolida 2014-11-05 11:32:17

  • Target version set to Tails_1.3

#14 Updated by BitingBird 2014-11-06 12:05:59

  • QA Check changed from Info Needed to Dev Needed

#15 Updated by Tails 2015-01-22 18:46:32

  • Status changed from Confirmed to In Progress

Applied in changeset commit:ae1c6221211796d2b701b79b634a13486dc3c4da.

#16 Updated by sajolida 2015-02-05 21:10:48

  • Assignee deleted (sajolida)
  • QA Check changed from Dev Needed to Ready for QA
  • Type of work changed from Research to Code

#17 Updated by intrigeri 2015-02-05 23:13:47

  • Feature Branch set to feature/7963-background-color

#18 Updated by intrigeri 2015-02-10 13:09:55

  • Assignee set to intrigeri

#19 Updated by Tails 2015-02-10 13:53:35

  • Status changed from In Progress to Fix committed
  • % Done changed from 50 to 100

Applied in changeset commit:33779f6bc037af444d454060509c08d2a129f6de.

#20 Updated by intrigeri 2015-02-10 13:54:29

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

#21 Updated by BitingBird 2015-02-24 22:48:56

  • Status changed from Fix committed to Resolved