Tails

#6 Updated by intrigeri 2015-03-19 17:06:40

A feature/new-ui branch was just pushed to upstream Git, and ports their code to Qt5. Not sure the port is finished, but it could push in favour of sticking to Qt for the time being.

#7 Updated by intrigeri 2015-05-02 04:19:23

That port to Qt5 is apparently using Qt Quick 2 and QML. I wasn’t able to find the bits needed to run it in Debian => emailed the Debian Qt maintainers, asking for advice / ETA / plans.

#8 Updated by intrigeri 2015-05-02 04:41:56

If “upstream” port to Qt 5 is done in a way that we can’t package it in Debian yet, or in a way that we can’t backport it for Jessie, then GTK 3 is getting more tempting again.

However, it’s not obvious to me that Python + GTK 3 is the best choice long-term wise, considering we want to port Tails Installer to Windows and OSX at some point. Regarding deploying Python + GTK 3 apps on Windows, my understanding is that:

• according to https://blogs.gnome.org/kittykat/2014/01/29/developing-gtk-3-apps-with-python-on-windows/:
  • there’s no official installer for GTK, GObject and friends
  • there’s a third-party installer for those; depending on the version, it’s between 100 and 260MB; it depends on Python being already installed
• it seems possible to bundle stuff with py2exe, but:
  • it’s unclear what exactly gets bundled: Python, GTK3, GObject?
  • is Python 3 supported by py2exe?
  • another source reports success, but it doesn’t see exactly straightforward, and seem to require quite a lot of hand-tuning if one doesn’t want a 180MB Windows installer
  • after reading another report, it’s not clear to me if/how one can generate the .exe from GNU/Linux; it seems that it would at least require installing lots of Windows-specific stuff somewhere, so that py2exe can bundle the DLLs etc.

#11 Updated by intrigeri 2015-06-28 13:44:40

JFTR, regarding Qt 5 (even if it’s now been more or less decided to go with GTK 3 instead): the Debian KDE folks pointed me at http://pkg-kde.alioth.debian.org/qmlmodulesnaming.html, and wrote “Check for packages like qml-module-quick or alike”.

#13 Updated by intrigeri 2015-07-04 10:32:54

As of commit a11b4b4:

• One should make sure that the log file keeps containing a superset of what’s on stderr: e.g. perhaps the newly introduced traceback.print_exc() breaks this assumption.
• When running the installer from a Git checkout, no logo is displayed.
• When the text doesn’t fit anymore in the status area, it’s not visible anymore as this thing doesn’t auto-scroll to the end.
• When the “There are no device suitable to install Tails on” (sic) notification is shown in the infobar, the “close” (cross icon) button in the infobar has no effect.
• One cannot move to the “Install” button with TAB: the status text area is editable, and then pressing TAB in there inserts, well, a TAB.

#15 Updated by alant 2015-07-04 12:10:48

> * When the text doesn’t fit anymore in the status area, it’s not visible anymore as this thing doesn’t auto-scroll to the end.

Fixed in 1b70682 Scroll the log view to always display the last enty

> * When the “There are no device suitable to install Tails on” (sic) notification is shown in the infobar, the “close” (cross icon) button in the infobar has no effect.

Fixed in 80a6fb0 Render the infobar closable

> * One cannot move to the “Install” button with TAB: the status text area is editable, and then pressing TAB in there inserts, well, a TAB.

Fixed in 61bb71a Fix the log view editability and margins

#16 Updated by alant 2015-07-04 12:36:11

> * One should make sure that the log file keeps containing a superset of what’s on stderr: e.g. perhaps the newly introduced traceback.print_exc() breaks this assumption.

Fixed in 7968107 Also log traceback to log file

> * When running the installer from a Git checkout, no logo is displayed.

This was a local misconfiguration on the test machine

All these bugs are fixed!

#18 Updated by intrigeri 2015-07-05 03:38:41

I confirm all these bugs are fixed (congrats!), except:

alant wrote:
> > * When the text doesn’t fit anymore in the status area, it’s not visible anymore as this thing doesn’t auto-scroll to the end.
>
> Fixed in 1b70682 Scroll the log view to always display the last enty

I just saw the “Installation completed” (or similar) final line being truncated vertically, so this doesn’t seem to be fully fixed yet.

#19 Updated by intrigeri 2015-07-06 08:42:52

Here’s a new (minor) bug: lines that don’t fit in the status log area are not wrapped, and there’s a horizontal scrolling bar. IMO they should be wrapped instead.

#20 Updated by intrigeri 2015-07-06 08:45:14

intrigeri wrote:
> Here’s a new (minor) bug: lines that don’t fit in the status log area are not wrapped, and there’s a horizontal scrolling bar. IMO they should be wrapped instead.

I might have fixed in with commit 3412aca.

#21 Updated by intrigeri 2015-07-06 09:45:38

intrigeri wrote:
> intrigeri wrote:
> > Here’s a new (minor) bug: lines that don’t fit in the status log area are not wrapped, and there’s a horizontal scrolling bar. IMO they should be wrapped instead.
>
> I might have fixed in with commit 3412aca.

Confirmed, except the Git server is down right now so I can’t push.

#22 Updated by alant 2015-07-06 14:47:30

intrigeri wrote:
> I confirm all these bugs are fixed (congrats!), except:
>
> alant wrote:
> > > * When the text doesn’t fit anymore in the status area, it’s not visible anymore as this thing doesn’t auto-scroll to the end.
> >
> > Fixed in 1b70682 Scroll the log view to always display the last enty
>
> I just saw the “Installation completed” (or similar) final line being truncated vertically, so this doesn’t seem to be fully fixed yet.

This should be fixed in commit a9d2d50, but I can’t push either.

#23 Updated by intrigeri 2015-07-08 12:17:48

FTR, it now passes all the relevant bits of our automated test suite. So once each of us has been able to push their latest stuff to Git, I plan to merge into feature/jessie (both in the liveusb-creator and in main Tails repositories).