Librem Manager issueshttps://source.puri.sm/francois.techene/librem-manager/-/issues2022-05-23T08:08:11Zhttps://source.puri.sm/francois.techene/librem-manager/-/issues/16Move to Librem5/ or PureOS/ namespace2022-05-23T08:08:11ZEvangelos Ribeiro TzarasMove to Librem5/ or PureOS/ namespaceWe should potentially move the repository over to the L5 or PureOS namespace unless @francois.techene wants the privilege (or burden) of maintenance all for himself ;)We should potentially move the repository over to the L5 or PureOS namespace unless @francois.techene wants the privilege (or burden) of maintenance all for himself ;)https://source.puri.sm/francois.techene/librem-manager/-/issues/15Package in PureOS2022-04-26T15:33:08ZDorota CzaplejewiczPackage in PureOSAs discussed at a Librem 5 meeting, there's demand from users to have an easy to use tool to recover the phone in case of an accident.As discussed at a Librem 5 meeting, there's demand from users to have an easy to use tool to recover the phone in case of an accident.https://source.puri.sm/francois.techene/librem-manager/-/issues/14Use continuous testing2022-04-26T15:32:08ZDorota CzaplejewiczUse continuous testingClosely related to https://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/49
Since this program is supposed to be user-friendly, its recovery methods should be regularly tested against more-or-less up-to-date images pretending to ...Closely related to https://source.puri.sm/Librem5/librem5-devkit-tools/-/issues/49
Since this program is supposed to be user-friendly, its recovery methods should be regularly tested against more-or-less up-to-date images pretending to be users' phones needing recovery. That's because the recovery tool can't serve its purpose if we accidentally make a change elsewhere that renders it unoperative (e.g. change the kernel compression method or partition layout).https://source.puri.sm/francois.techene/librem-manager/-/issues/13Define typical problems users recover from2022-04-26T15:29:17ZDorota CzaplejewiczDefine typical problems users recover fromWhile users' systems can get broken in a multitude of ways, there should be some uneven distribution of problems. We should cover the most typical ones, especially those that don't arise from the user trying to be clever and failing. Onc...While users' systems can get broken in a multitude of ways, there should be some uneven distribution of problems. We should cover the most typical ones, especially those that don't arise from the user trying to be clever and failing. Once we define what we need, we can start implementing automated solutions.
What comes to mind:
- reinstall a kernel after the battery runs out during installation
- reinstall a kernel after space runs out during installation
From a developer's POV:
- reinstall a kernel after installing a broken onehttps://source.puri.sm/francois.techene/librem-manager/-/issues/12Hang on "Looking for Installation files"2021-12-08T19:26:02ZDavid HamnerHang on "Looking for Installation files"Got a lockup here:
![Screenshot_from_2021-12-08_11-20-08](/uploads/8f4efaf9c7b45ca0ff7c00b457d2347a/Screenshot_from_2021-12-08_11-20-08.png)
Logs:
```
purism@librem14:~/Downloads$ libremmanager
DEBUG:root:Selected device: Evergreen
DE...Got a lockup here:
![Screenshot_from_2021-12-08_11-20-08](/uploads/8f4efaf9c7b45ca0ff7c00b457d2347a/Screenshot_from_2021-12-08_11-20-08.png)
Logs:
```
purism@librem14:~/Downloads$ libremmanager
DEBUG:root:Selected device: Evergreen
DEBUG:root:Selected image: Byzantium
DEBUG:root:Main thread : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:USB Listener thread : <Thread(Thread-1, started daemon 139819573311232)>
Couldn't open device, some information will be missing
DEBUG:root: Found device on /dev/sg2
DEBUG:root: Found device on /dev/sdd2
DEBUG:root: Found device on /dev/sdd
DEBUG:root: Found device on /dev/sdd1
DEBUG:root: Found device on /dev/bsg/5:0:0:0
DEBUG:root: Found device on /dev/sg3
DEBUG:root: Found device on /dev/sde
DEBUG:root: Found device on /dev/bsg/5:0:0:1
DEBUG:root:Update callback thread : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:Librem5FlashController : Selected device has changed
DEBUG:root: Found system drive as /dev/sdd
DEBUG:root: Found system drive as /dev/sdd
DEBUG:root: Found volume /dev/dm-2 in system drive
DEBUG:root: Found volume /dev/sdd1 in system drive
DEBUG:root: Found encrypted volume at /dev/dm-2
DEBUG:root: Mounted system volume as /dev/dm-2
DEBUG:root:Notifying from device state change
DEBUG:root:Update callback thread : <_MainThread(MainThread, started 139819953645376)>
[sudo] password for purism: DEBUG:root:Calling flash device : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:Running flash device : <Thread(Thread-7, started daemon 139819517638400)>
DEBUG:root: Found volume /dev/dm-2 in system drive
DEBUG:root: Found volume /dev/sdd1 in system drive
DEBUG:root: Mounted system volume as /dev/dm-2
DEBUG:root:Running _do_backup_user_data : <Thread(Thread-9, started daemon 139819327895296)>
DEBUG:root:Copying home data from /media/purism/f7c1b869-4e4a-4012-957d-0bbacf8eed7a to /home/purism/.librem-manager/librem5/librem5_home_rz40dfyw ...
DEBUG:root:Calling from : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantium image
DEBUG:root:Calling flash device : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:Running flash device : <Thread(Thread-11, started daemon 139819344680704)>
DEBUG:root: Found volume /dev/dm-2 in system drive
DEBUG:root: Found volume /dev/sdd1 in system drive
DEBUG:root: Mounted system volume as /dev/dm-2
DEBUG:root:Running _do_backup_user_data : <Thread(Thread-13, started daemon 139819319502592)>
DEBUG:root:Copying home data from /media/purism/f7c1b869-4e4a-4012-957d-0bbacf8eed7a to /home/purism/.librem-manager/librem5/librem5_home_6ubxwb9k ...
DEBUG:root:Calling from : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantium image
DEBUG:root:Calling flash device : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:Running flash device : <Thread(Thread-15, started daemon 139819371984640)>
DEBUG:root: Found volume /dev/dm-2 in system drive
DEBUG:root: Found volume /dev/sdd1 in system drive
DEBUG:root: Mounted system volume as /dev/dm-2
DEBUG:root:Running _do_backup_user_data : <Thread(Thread-17, started daemon 139819036440320)>
DEBUG:root:Copying home data from /media/purism/f7c1b869-4e4a-4012-957d-0bbacf8eed7a to /home/purism/.librem-manager/librem5/librem5_home_gn8d6baf ...
DEBUG:root:Calling from : <_MainThread(MainThread, started 139819953645376)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantium image
Exception in thread Thread-10:
Traceback (most recent call last):
File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/lib/python3.9/http/client.py", line 1417, in connect
super().connect()
File "/usr/lib/python3.9/http/client.py", line 921, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.9/socket.py", line 822, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 431, in jenkins_open
response = urlopen(req, timeout=self.timeout).read()
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/usr/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 1389, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.9/urllib/request.py", line 1349, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/usr/lib/python3.9/threading.py", line 892, in run
self._target(*self._args, **self._kwargs)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 627, in get_image_and_flash_device
image_ref = self.find_image(self.args.image_job, board, self.args.variant, self.args.dist)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 734, in find_image
info = server.get_job_info(jobname)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 358, in get_job_info
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 430, in jenkins_open
self.maybe_add_crumb(req)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 302, in maybe_add_crumb
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 461, in jenkins_open
raise JenkinsException('Error in request: %s' % (e.reason))
jenkins.JenkinsException: Error in request: [Errno -2] Name or service not known
Exception in thread Thread-14:
Traceback (most recent call last):
File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/lib/python3.9/http/client.py", line 1417, in connect
super().connect()
File "/usr/lib/python3.9/http/client.py", line 921, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.9/socket.py", line 822, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 431, in jenkins_open
response = urlopen(req, timeout=self.timeout).read()
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/usr/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 1389, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.9/urllib/request.py", line 1349, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/usr/lib/python3.9/threading.py", line 892, in run
self._target(*self._args, **self._kwargs)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 627, in get_image_and_flash_device
image_ref = self.find_image(self.args.image_job, board, self.args.variant, self.args.dist)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 734, in find_image
info = server.get_job_info(jobname)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 358, in get_job_info
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 430, in jenkins_open
self.maybe_add_crumb(req)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 302, in maybe_add_crumb
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 461, in jenkins_open
raise JenkinsException('Error in request: %s' % (e.reason))
jenkins.JenkinsException: Error in request: [Errno -2] Name or service not known
Exception in thread Thread-18:
Traceback (most recent call last):
File "/usr/lib/python3.9/urllib/request.py", line 1346, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/lib/python3.9/http/client.py", line 1417, in connect
super().connect()
File "/usr/lib/python3.9/http/client.py", line 921, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.9/socket.py", line 822, in create_connection
for res in getaddrinfo(host, port, 0, SOCK_STREAM):
File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 431, in jenkins_open
response = urlopen(req, timeout=self.timeout).read()
File "/usr/lib/python3.9/urllib/request.py", line 214, in urlopen
return opener.open(url, data, timeout)
File "/usr/lib/python3.9/urllib/request.py", line 517, in open
response = self._open(req, data)
File "/usr/lib/python3.9/urllib/request.py", line 534, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
result = func(*args)
File "/usr/lib/python3.9/urllib/request.py", line 1389, in https_open
return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.9/urllib/request.py", line 1349, in do_open
raise URLError(err)
urllib.error.URLError: <urlopen error [Errno -2] Name or service not known>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/usr/lib/python3.9/threading.py", line 892, in run
self._target(*self._args, **self._kwargs)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 627, in get_image_and_flash_device
image_ref = self.find_image(self.args.image_job, board, self.args.variant, self.args.dist)
File "/usr/share/libremmanager/libremmanager/librem_5_flash_controller.py", line 734, in find_image
info = server.get_job_info(jobname)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 358, in get_job_info
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 430, in jenkins_open
self.maybe_add_crumb(req)
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 302, in maybe_add_crumb
response = self.jenkins_open(Request(
File "/usr/lib/python3/dist-packages/jenkins/__init__.py", line 461, in jenkins_open
raise JenkinsException('Error in request: %s' % (e.reason))
jenkins.JenkinsException: Error in request: [Errno -2] Name or service not known
```https://source.puri.sm/francois.techene/librem-manager/-/issues/11mmcblk0 could not be opened.2021-12-07T16:25:22ZDavid Hamnermmcblk0 could not be opened.While trying to flash while keeping user data, flashdrive failed to startup giving the error:
```/dev/mmcblk0 could not be opened, possible eMMC defect.```
What version of jumpdrive is this using? It may need an updated kernel to be mo...While trying to flash while keeping user data, flashdrive failed to startup giving the error:
```/dev/mmcblk0 could not be opened, possible eMMC defect.```
What version of jumpdrive is this using? It may need an updated kernel to be more reliable. Libremmanager was not able to detect the error, perhaps add a timeout if the device fails to enter jumpdrive mode.https://source.puri.sm/francois.techene/librem-manager/-/issues/10Failed flash: An error has occurred while backing up your data2021-12-08T21:30:24ZDavid HamnerFailed flash: An error has occurred while backing up your dataRan into this:
![Screenshot_from_2021-12-06_08-55-32](/uploads/c1fa4c010ed27a2e9340d62d9e22490c/Screenshot_from_2021-12-06_08-55-32.png)
While testing an upgrade to Byzantium. It seems to have flashed and re-encrypted the drive, but fa...Ran into this:
![Screenshot_from_2021-12-06_08-55-32](/uploads/c1fa4c010ed27a2e9340d62d9e22490c/Screenshot_from_2021-12-06_08-55-32.png)
While testing an upgrade to Byzantium. It seems to have flashed and re-encrypted the drive, but failed to copy the data back.
```
DEBUG:root:Selected device: Evergreen
DEBUG:root:Selected image: Byzantium
DEBUG:root:Main thread : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:USB Listener thread : <Thread(Thread-1, started daemon 140687886247680)>
Couldn't open device, some information will be missing
DEBUG:root: Found device on /dev/sg2
DEBUG:root: Found device on /dev/sdc2
DEBUG:root: Found device on /dev/sdc
DEBUG:root: Found device on /dev/sdc1
DEBUG:root: Found device on /dev/bsg/4:0:0:0
DEBUG:root: Found device on /dev/sg3
DEBUG:root: Found device on /dev/sdd
DEBUG:root: Found device on /dev/bsg/4:0:0:1
DEBUG:root:Update callback thread : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:Librem5FlashController : Selected device has changed
DEBUG:root: Found system drive as /dev/sdc
DEBUG:root: Found system drive as /dev/sdc
DEBUG:root: Found volume /dev/sdc2 in system drive
DEBUG:root: Found volume /dev/sdc1 in system drive
DEBUG:root: Mounted system volume as /dev/sdc2
DEBUG:root:Notifying from device state change
DEBUG:root:Update callback thread : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:Calling flash device : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:Running flash device : <Thread(Thread-5, started daemon 140687693575936)>
DEBUG:root: Found volume /dev/sdc2 in system drive
DEBUG:root: Found volume /dev/sdc1 in system drive
DEBUG:root: Mounted system volume as /dev/sdc2
DEBUG:root:Running _do_backup_user_data : <Thread(Thread-7, started daemon 140687647385344)>
DEBUG:root:Copying home data from /media/purism/ff06ef7d-e55a-4855-8930-95b2dd1b1ee1 to /home/purism/.librem-manager/librem5/librem5_home_a4ml7kfr ...
$ cp -arv /media/purism/ff06ef7d-e55a-4855-8930-95b2dd1b1ee1/home/ /home/purism/.librem-manager/librem5/librem5_home_a4ml7kfr
$ sync
DEBUG:root:Calling from : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantium image
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726//api/json HTTP/1.1" 200 915
DEBUG:root:Found disk image Build 9726 'luks librem5r4 byzantium image' from Sun 05 Dec 2021 10:19:10 PM
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/u-boot_builds/job/uboot_librem5_build/82//api/json HTTP/1.1" 200 918
DEBUG:root:Found uboot Build 82 from Fri 10 Sep 2021 11:19:03 AM
DEBUG:root:Downloading to /home/purism/.librem-manager/librem5
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/files/meta.yml HTTP/1.1" 200 154
DEBUG:root:Image size is 4500000256
INFO:root:Downloading image from https://arm01.puri.sm/job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "HEAD /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 200 0
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 4301875276
DEBUG:root:Proceeding from 0 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3934937284
DEBUG:root:Proceeding from 366937992 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3916892769
DEBUG:root:Proceeding from 384982507 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2780922425
DEBUG:root:Proceeding from 1520952851 bytes
INFO:root:Calculating sha256sum of /home/purism/.librem-manager/librem5/librem5r4.img
DEBUG:root:Unmounting /dev/sdc2
DEBUG:root:Unmounting /dev/sdc1
4479516672 bytes (4.5 GB, 4.2 GiB) copied, 73 s, 61.3 MB/s
1072+1 records in
1072+1 records out
4500000256 bytes (4.5 GB, 4.2 GiB) copied, 173.612 s, 25.9 MB/s
$ sync
DEBUG:root:Calling from : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root:Running reencrypt : <Thread(Thread-10, started daemon 140687647385344)>
DEBUG:root:Re-encrypting the drive : /dev/sdc2
$ sync
INFO:root:resizing partition
$ sync
DEBUG:root:Calling from : <_MainThread(MainThread, started 140688195368768)>
DEBUG:root: Found volume /dev/sdc1 in system drive
DEBUG:root: Found volume /dev/sdc2 in system drive
DEBUG:root: Mounting /dev/sdc1
ERROR:root:Cannot mount /dev/sdc1 : g-io-error-quark: No object for D-Bus interface (0)
DEBUG:root: Mounting /dev/sdc2 with pw
ERROR:root:Cannot mount /dev/sdc2 : g-io-error-quark: No object for D-Bus interface (0)
DEBUG:root: Mounted system volume as /dev/sdc2
```https://source.puri.sm/francois.techene/librem-manager/-/issues/9Increase max connection errors for crappy networks2021-12-06T16:20:08ZDavid HamnerIncrease max connection errors for crappy networksI had a failed flash over WiFi. It almost finished downloading when I got:
```
DEBUG:root:Calling from : <_MainThread(MainThread, started 139909502023488)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantiu...I had a failed flash over WiFi. It almost finished downloading when I got:
```
DEBUG:root:Calling from : <_MainThread(MainThread, started 139909502023488)>
DEBUG:root:flashing board librem5r4
INFO:root:Looking for librem5r4 luks byzantium image
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726//api/json HTTP/1.1" 200 915
DEBUG:root:Found disk image Build 9726 'luks librem5r4 byzantium image' from Sun 05 Dec 2021 10:19:10 PM
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/u-boot_builds/job/uboot_librem5_build/82//api/json HTTP/1.1" 200 918
DEBUG:root:Found uboot Build 82 from Fri 10 Sep 2021 11:19:03 AM
DEBUG:root:Downloading to /home/purism/.librem-manager/librem5
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/files/meta.yml HTTP/1.1" 200 154
DEBUG:root:Image size is 4500000256
INFO:root:Downloading image from https://arm01.puri.sm/job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "HEAD /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 200 0
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 4301875276
DEBUG:root:Proceeding from 0 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3937556498
DEBUG:root:Proceeding from 364318778 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3801249579
DEBUG:root:Proceeding from 500625697 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3578508757
DEBUG:root:Proceeding from 723366519 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 3042722823
DEBUG:root:Proceeding from 1259152453 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2945902259
DEBUG:root:Proceeding from 1355973017 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2856481221
DEBUG:root:Proceeding from 1445394055 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2823048148
DEBUG:root:Proceeding from 1478827128 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2501326141
DEBUG:root:Proceeding from 1800549135 bytes
INFO:root:Connection error, retrying
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): arm01.puri.sm:443
DEBUG:urllib3.connectionpool:https://arm01.puri.sm:443 "GET /job/Images/job/Image%20Build/9726/artifact/librem5r4.img.xz HTTP/1.1" 206 2314662848
DEBUG:root:Proceeding from 1987212428 bytes
ERROR:root:Max connection errors reached, aborting
ERROR:root
```https://source.puri.sm/francois.techene/librem-manager/-/issues/7Librem Manager assumes picocom is a part of the dialout group2021-12-13T18:32:02ZJoao AzevedoLibrem Manager assumes picocom is a part of the dialout groupWhen using the application to connect to a Librem 5 it fails because it assumes picocom is a part of the `dialout` group.
Which by default it is not.
The command `picocom -b 115200 /dev/tty/ACM0` to work would need either sudo. Or if yo...When using the application to connect to a Librem 5 it fails because it assumes picocom is a part of the `dialout` group.
Which by default it is not.
The command `picocom -b 115200 /dev/tty/ACM0` to work would need either sudo. Or if you do not want the user to be prompted for a password for `picocom` to be added to the `dialout` group when the libremmanager app installs.
No idea if the last part is usually done by packagers; making a dependency a part of the sudo group for your app to work.