todo.mdwn 7.63 KB
Newer Older
1
2
[[!toc levels=2]]

Tails developers's avatar
Tails developers committed
3
4
Bugs
====
5

Tails developers's avatar
Tails developers committed
6
7
8
9
10
11
missing correct link to documentation
-------------------------------------

The unified launched has a link to `file:///FIXME` since we don't know
the path to the installer documentation yet.

Tails developers's avatar
Tails developers committed
12
13
crashes with amd64 / 686-pae kernels
------------------------------------
Tails developers's avatar
Tails developers committed
14

Tails developers's avatar
Tails developers committed
15
16
Logs for various crashes experienced when cloning, on amd64 kernel,
follow. At least one similar bug was triggered on 686-pae kernel
Tails developers's avatar
Tails developers committed
17
18
(64bit CPU) too. Launching the program with various linux32's options
does not help.
Tails developers's avatar
Tails developers committed
19

Tails developers's avatar
Tails developers committed
20
21
22
23
Those crashes don't happen on a Wheezy amd64 kernel + amd64 userspace.
Is this bug fixed in Wheezy, or due to mixing 64bit kernel with
32bit userspace?

Tails developers's avatar
Tails developers committed
24
25
26
27
28
29
30
31
	[creator:1160] extlinux not found! Only FAT filesystems will be supported
	*** glibc detected *** /usr/bin/python: malloc(): memory corruption: 0x0951d720 ***
	======= Backtrace: =========
	/lib/libc.so.6(+0x6b19a)[0xf746219a]
	/lib/libc.so.6(+0x6dfb7)[0xf7464fb7]
	/lib/libc.so.6(__libc_malloc+0x5c)[0xf7466bfc]
	vie/usr/bin/python(PyString_FromStringAndSize+0x9c)[0x809da2c]

Tails developers's avatar
Tails developers committed
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
	*** glibc detected *** /usr/bin/python2.6: malloc(): memory corruption: 0x09f5f9f0 ***
	======= Backtrace: =========
	/lib/libc.so.6(+0x6b19a)[0xf74eb19a]
	/lib/libc.so.6(+0x6dfb7)[0xf74edfb7]
	/lib/libc.so.6(+0x706ec)[0xf74f06ec]
	/lib/libc.so.6(realloc+0xd7)[0xf74f0c17]
	/usr/lib/libQtCore.so.4(_Z8qReallocPvj+0x24)[0xf6cbb514]
	/usr/lib/libQtCore.so.4(_ZN9QListData7reallocEi+0x35)[0xf6ce0a35]
	
	[creator:799] Calling /org/freedesktop/UDisks/devices/sdc1.FilesystemMount(vfat, [], ...)
	python2.6: malloc.c:3097: sYSMALLOc: Assertion `(old_top == (((mbinptr) (((char *) &((av)->bins[((1) - 1) * 2])) - __builtin_offsetof (struct malloc_chunk, fd)))) && old_size == 0) || ((unsigned long) (old_size) >= (unsigned long)((((__builtin_offsetof (struct malloc_chunk, fd_nextsize))+((2 * (sizeof(size_t))) - 1)) & ~((2 * (sizeof(size_t))) - 1))) && ((old_top)->size & 0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
	
	[creator:354] ['/sbin/mkfs.vfat', '-n', 'Tails', '-F', '32', '/dev/sdc1']
	[creator:798] Calling /org/freedesktop/UDisks/devices/sdc1.FilesystemMount(vfat, [], ...)
	*** glibc detected *** /usr/bin/python2.6: malloc(): smallbin double linked list corrupted: 0x0a075a50 ***
	======= Backtrace: =========
	Segmentation fault
	
	*** glibc detected *** /usr/bin/python2.6: free(): corrupted unsorted chunks: 0x099d1e20 ***
	======= Backtrace: =========
	/lib/libc.so.6(+0x6b19a)[0xf748b19a]
	/lib/libc.so.6(+0x6c9e8)[0xf748c9e8]
	/lib/libc.so.6(cfree+0x6d)[0xf748fb2d]
	/usr/bin/python2.6[0x80903ba]
	/usr/bin/python2.6[0x806c74b]
	/usr/bin/python2.6[0x80903a4]
	Segmentation fault
	
	[creator:354] ['/sbin/sgdisk', '--info', '1', '/dev/sdc']
	*** glibc detected *** /usr/bin/python2.6: malloc(): memory corruption: 0x09d2c988 ***
	======= Backtrace: =========
	/lib/libc.so.6(+0x6b19a)[0xf74c219a]
	/lib/libc.so.6(+0x6dfb7)[0xf74c4fb7]
	/lib/libc.so.6(__libc_malloc+0x5c)[0xf74c6bfc]
	/usr/lib/libstdc++.so.6(_Znwj+0x27)[0xf6bf0ba7]
	Segmentation fault
Tails developers's avatar
Tails developers committed
68

Tails developers's avatar
Tails developers committed
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
breaks emergency shutdown
-------------------------

sajolida reports:

- it seems to happen after using the liveusb-creator
- it happened on both Tails 0.10.1 and Tails experimental
- sometimes it happens while doing:
  - boot Tails experimental on a isohybrid
  - "Clone Tails" onto another stick
  - unplug the running Tails
- sometimes the screen turns black with a cursor on the top-left
  corner and nothing else
- sometimes the screen stays the same, the system is still somehow
  responsive but doesn't shutdown
- once I couldn't even shutdown with the red button or by doing `sudo
  halt` in a terminal once I reached this weird state
- once I checked and udev-watchdog was still running on the right
  device but the emergency shutdown still didn't work

intrigeri confirms: On VT1, when unplugging my boot USB stick, I see
various lines about sdb3, sdb2 and sdb1 being removed, followed by
"Bus error". Nothing more happens, and the udev watchdog process is
not there anymore.

Tails developers's avatar
Tails developers committed
94
95
Report the udisks vs. partition attributes bug
----------------------------------------------
96

Tails developers's avatar
Tails developers committed
97
Creating or deleting a second partition using udisks resets the first partition's attributes.
Tails developers's avatar
Tails developers committed
98

Tails developers's avatar
Tails developers committed
99
Normal output is:
100

Tails developers's avatar
Tails developers committed
101
102
103
104
105
106
107
108
109
110
111
112
	$ sgdisk /dev/sdb --attributes=1:show
	1:2:1 (legacy BIOS bootable)
	1:60:1 (read-only)
	1:62:1 (hidden)
	1:63:1 (do not automount)

After creating a second partition, the output is empty.

As documented on the [syslinux
wiki](http://www.syslinux.org/wiki/index.php/Common_Problems#Missing_OS_.28gptmbr.bin.29),
trying to boot such a broken stick results in the `Missing OS` message
and no boot.
113

Tails developers's avatar
Tails developers committed
114
115
`tails-persistence-setup`, that creates the persistence partition,
workarounds this, but we must report this bug upstream.
116

Tails developers's avatar
Tails developers committed
117
118
119
120
121
122
123
124
125
126
127
128
129
130
Would-be-nice
=============

SD Card support
---------------

Maybe does not support SD / SDHC Cards as well as USB?

Unified launcher
----------------

- find 3 images for the buttons
- ship and use these images

131
132
133
Documentation
=============

Tails developers's avatar
Tails developers committed
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
download and installation
-------------------------

Update [[download and installation|download]] documentation.

To be treated carefully:

* The bootstrap steps (when one has no Tails system yet):  it implies
  burning a CD, booting from CD, and cloning. Or do we want to make
  a liveusb-creator `.deb` available on our website?

resetting a Tails USB stick
---------------------------

The `feature/usb_installer` branch has documentation in
`doc/resetting_usb_stick` that explains how to reset a USB stick that
previously contained a isohybrid or GPT Tails to a "normal" state
(i.e. MBR partition table, and optionally FAT32 partition).

Left to do:

* test Windows instructions
Tails developers's avatar
Tails developers committed
156
* link to these pages from the USB installer documentation
Tails developers's avatar
Tails developers committed
157
158
159
160
161

Localization
============

Hand out `.po` files to translators.
Tails developers's avatar
Tails developers committed
162
163
164
165

Later
=====

Tails developers's avatar
Tails developers committed
166
* Remove devices from the list when unplugged.
Tails developers's avatar
Tails developers committed
167
* Set cursor to waiting (hourglass) state while working.
Tails developers's avatar
Tails developers committed
168
169
* *Target Device* list: display more information, such as the stick
  brand and model.
Tails developers's avatar
Tails developers committed
170
171
172
173
174
175
176
177
* If stick is <1.5GB case, support installing but don't show the
  persistence checkbox
* Allow setting the system/overlay partitions size via command-line
  option(s).
* Add Tails to the downloadable images list.
* Allow vendors to set
  - default release to download
  - list of downloadable files
178
179
* When run from inside Tails, provide an opt-in option to download the
  ISO outside Tor.
Tails developers's avatar
Tails developers committed
180
181
182
183
184
* GPG signature verification
  - verify GPG signatures delivered with iso images (see verify_iso_sha1 called in gui.py)
  - Debian provides gpgv-win32 that can be used on Windows
- command-line option --local-hard-disks that would enable
  installation on local hard disks (= not external USB);
Tails developers's avatar
Tails developers committed
185
  is half-implemented by `--force`, see special casing in the
Tails developers's avatar
Tails developers committed
186
  detect_removable_devices method.
Tails developers's avatar
Tails developers committed
187
188
189
190
191
192
* currently lists all partitions on the same USB stick. What should it
  do instead?
  - if one of those partitions is labelled `Tails`, and we're
    upgrading, it probably makes sense hiding other partitions on the
    same physical device

Tails developers's avatar
Tails developers committed
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209

Windows support?
----------------

As [[documented already|doc/installing_onto_a_usb_stick/windows]],
the basic Tails install onto a USB stick from Windows is already easy
to do.

Therefore, even if our installer does not run on Windows / until it
does, those who want to get a "standard" install of Tails on USB can
either burn a CD or use a "basic" install of Tails on USB, and then
run our installer in clone mode from Tails.

Proper Windows support would be welcome, though.

Try http://www.pyinstaller.org/ to create a single binary file for
Windows and for OS X. Include those binaries on Tails images?
Tails developers's avatar
Tails developers committed
210
211
212
213
214

Should be more explicit when no target device is available
----------------------------------------------------------

Empty list, no message, is not that easy to understand.