Project

General

Profile

Bug #9688

t-p-s fails to start on Jessie

Added by intrigeri over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
-
Category:
Persistence
Target version:
Start date:
07/05/2015
Due date:
% Done:

100%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

t-p-s 1.0.20-1+jessie, perl5lib 0.8.7-1+jessie2, running from (virtual) DVD:

amnesia@amnesia:~$ /usr/local/bin/tails-persistence-setup
localuser:tails-persistence-setup being added to access control list
WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. at /usr/share/perl5/Gtk3.pm line 301.
BEGIN not safe after errors--compilation aborted at /usr/lib/i386-linux-gnu/perl5/5.20/Moose/Exception/CouldNotCreateMethod.pm line 3.
Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 317.
Compilation failed in require at /usr/bin/tails-persistence-setup line 25.
BEGIN failed--compilation aborted at /usr/bin/tails-persistence-setup line 25.

History

#1 Updated by intrigeri over 3 years ago

The culprit seems to be in create_persistent_encrypted_filesystem, and more specifically in:

         ->Format(
             dbus_call_async, dbus_call_timeout, 3600 * 1000,
             $fstype, $fsoptions);

... and seems to be caused by the fact we're not enabling jessie-backports in feature/jessie, and thus we don't have the version of libnet-dbus-perl that we need.

#2 Updated by intrigeri over 3 years ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100

b23835a and b30a2fe0 fixed it :)

Also available in: Atom PDF