Project

General

Profile

Bug #16273

pkexec error when trying to remove ASP through persistence-setup

Added by mercedes508 12 months ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Persistence
Target version:
-
Start date:
01/04/2019
Due date:
% Done:

0%

Feature Branch:
bugfix/16273-pkexec-error
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Additional Software Packages

Description

In Tails 3.11 when some packages are installed using the additional software persistent feature, we get the following error when trying to remove any of them by going to the persistent configuration assistant, then to the setting button of the additional software feature, then trying to delete a package:

Command
'['pkexec','/usr/local/sbin/tails-additional-software-
remove','mumble']' returned non-zero exit status 127

journalctl (11.4 KB) mercedes508, 03/12/2019 03:54 PM


Related issues

Related to Tails - Bug #16982: Can't start Synaptic from Additional Software that was itself started from tails-persistence-setup Confirmed

Associated revisions

Revision 3b3f1789 (diff)
Added by alant 9 months ago

ASP: set SHELL environnment variable required by pkexec

Will-fix: #16273

Revision f6bc46a9 (diff)
Added by alant 9 months ago

ASP: always ask for admin password

Else, when started from persistence-setup, tails-persistence-setup
password (inexistant) is prompted.

Will-fix: #16273

History

#1 Updated by intrigeri 12 months ago

  • 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 11 months ago

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

#3 Updated by alant 10 months ago

  • 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 9 months ago

  • 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 9 months ago

  • 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 9 months ago

  • 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 9 months ago

  • 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 9 months ago

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

#9 Updated by alant 9 months ago

  • Status changed from Confirmed to In Progress

#10 Updated by alant 9 months ago

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

#11 Updated by alant 9 months ago

A similar bug happens when trying to remove an ASP from the configuration window opened through the "Configure" button of the install failure notification. It seems that pkexec can't find an authentication agent. In the latter case it may be useful to start tails-additional-software-config the way we start the documentation (straight from the notification helper).

#12 Updated by CyrilBrulebois 7 months ago

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

#13 Updated by CyrilBrulebois 5 months ago

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

#14 Updated by intrigeri 4 months ago

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

#15 Updated by intrigeri 4 months ago

  • 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 #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!

Also available in: Atom PDF