Tails

#1 Updated by intrigeri 2019-01-04 14:55:04

• Assignee changed from intrigeri to alant

Alan, can you please take a look and ask help desk whatever additional info you might need?

#2 Updated by anonym 2019-01-30 11:59:38

• Target version changed from Tails_3.12 to Tails_3.13

#3 Updated by alant 2019-03-03 17:22:54

• Assignee changed from alant to mercedes508

intrigeri wrote:
> Alan, can you please take a look and ask help desk whatever additional info you might need?

Was an admin password set ?

It that’s not the issue, I’d need the syslog.

#4 Updated by mercedes508 2019-03-11 17:12:22

• Assignee changed from mercedes508 to alant

Setting or not an admin password doesn’t change anything, we’re not asked for it anyway.

Could you please be more precise about syslog? How to get these?

#5 Updated by alant 2019-03-11 23:14:33

• Assignee changed from alant to mercedes508

mercedes508 wrote:
> Setting or not an admin password doesn’t change anything, we’re not asked for it anyway.
>
pkexec exit status 127 means authentication failure : “Upon successful completion, the return value is the return value of PROGRAM. If the calling process is not authorized or an authorization could not be obtained through authentication or an error occured, pkexec exits with a return value of 127.” This is why I guessed that failing to set an admin password in the greeter could lead to this error.

> Could you please be more precise about syslog? How to get these?

Either the output of sudo journalctl -t tails-additional-software or execute DEBUG=1 tails-additional-software-config

#6 Updated by mercedes508 2019-03-12 15:54:21

• File journalctl added
• Assignee changed from mercedes508 to alant

I attached the output of journalctl -t tails-additional-software, and when executing DEBUG=1 tails-additional-software-config, it worked just fine.

#7 Updated by alant 2019-03-14 10:53:07

• Subject changed from Error when trying to remove packages from additional software feature to pkexec error when trying to remove ASP through persistence-setup

mercedes508 wrote:
> I attached the output of journalctl -t tails-additional-software,

I don’t see any issues there.

> and when executing DEBUG=1 tails-additional-software-config, it worked just fine.

I didn’t find anything in the logs, but reproduced the issue:

pkexec[29843]: tails-persistence-setup: The value for the SHELL variable was not found the /etc/shells file [USER=root] [TTY=unknown] [CWD=/] [COMMAND=/usr/local/sbin/tails-additional-software-remove vim]

So when launched through tails-persistence-setup, the environnment of tails-additional-software-remove seems not to be good. It should be notes that in this case, tails-additional-software-remove is run as tails-persistence-setup user.

#8 Updated by CyrilBrulebois 2019-03-20 14:34:11

• Target version changed from Tails_3.13 to Tails_3.14

#9 Updated by alant 2019-03-21 21:29:21

• Status changed from Confirmed to In Progress

Applied in changeset commit:tails|3b3f178958d1d4cf157b56b12547bc5f83403cd7.

#10 Updated by alant 2019-03-21 21:30:53

• Feature Branch set to bugfix/16273-pkexec-error
• Type of work changed from Research to Code

#12 Updated by CyrilBrulebois 2019-05-23 21:23:30

• Target version changed from Tails_3.14 to Tails_3.15

#13 Updated by CyrilBrulebois 2019-07-10 10:34:11

• Target version changed from Tails_3.15 to Tails_3.16

#14 Updated by intrigeri 2019-08-30 17:29:14

• related to Bug #16982: Can't start Synaptic from Additional Software that was itself started from tails-persistence-setup added

#15 Updated by intrigeri 2019-08-30 17:29:43

• Target version deleted (Tails_3.16)

Hi!

We’ve set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to:

• better reflect your plans;
• bring down your amount of work-in-progress to a sustainable level;
• encourage team work and increase the chances that someone finishes the work;
• avoid a human doing ticket triaging and asking you the same questions on each such ticket.

In particular, this process identifies:

• Stalled work-in-progress
• Reviews waiting for a long time

However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on Feature #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I’m doing on this ticket.

You now have a few options, such as:

• Deassign yourself. That’s fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
• If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable “Target version”. This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today’s choice.

Cheers!

#16 Updated by alant 2020-03-08 18:47:33

• Assignee deleted (alant)