We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-07-15 13:43:48 +0200 |
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog will be made available in a separate post shortly.
2 | No.2 Revision |
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog will be made is available in a separate post shortly.post
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog is available in a separate post
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog is available in a separate post
5 | No.5 Revision |
Update: 1.1.7.25, fixing an issue in package management middleware, will be rolled out to early access soon
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
1.1.7.25 (17.7.2015): Fix an issue in package management middleware
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog is available in a separate post
6 | No.6 Revision |
Update: 1.1.7.25, fixing an issue in package management middleware, will be rolled out to early access soon
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
1.1.7.25 (17.7.2015): (27.7.2015): Fix an issue in package management middleware
New gcc 4.8 based tool chain is used on SailfishOS platform from this release onwards, bringing C++11, among other things
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog is available in a separate post
7 | No.7 Revision |
Update: 1.1.7.25, 1.1.7.27, fixing an issue in package management middleware, a reboot bug when using hotspot and GPS, will be rolled out to early access soonsoon. The source for updates sometimes taking hours has not been found yet, the on-device update texts have been adjusted to warn about this issue.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
The full changelog is available in a separate post
8 | No.8 Revision |
Update: 1.1.7.27, fixing a reboot bug when using hotspot and GPS, 1.1.7.27 will be rolled out to early access a small group of regular users soon. The source for updates sometimes taking hours has not been found yet, the on-device update texts have been adjusted to warn about this issue.issue. If you encounter a long or incomplete update, please tell us. If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
9 | No.9 Revision |
Update: 1.1.7.27 1.1.7.28 will be rolled out to early access users and a small group of regular users soon. The source for updates sometimes taking hours has not been found yet, the on-device update texts have been adjusted to warn about this issue. If you encounter a long or incomplete update, please tell us. If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
10 | No.10 Revision |
Update:Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update will take a long time to complete, please be patient.
In some cases (<1% so far in the early access users and a small group of regular users soon. group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The source for updates sometimes taking hours has not been found yet, the on-device update texts have been adjusted to warn about this issue. If you encounter a long or incomplete update, please tell us. issue.
If you have developer mode enabled, enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change /etc/systemd/journald.conf
Storage=volatile to Storage=automatic and create Storage=volatile
to Storage=automatic
/var/log/journal before downloading the update. Change it back to volatile after the upgrade /var/log/journal
went goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
11 | No.11 Revision |
Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update will take a long time to complete, please be patient.
In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.
If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, and your account is subscribed for early access releases, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
12 | No.12 Revision |
Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update process will take a long time to complete, complete (especially the file system optimizations), please be patient.
In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.
If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly. When updating from 1.1.6 your device might go through lengthy file system optimizations before installing the update.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
13 | No.13 Revision |
Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.
If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
14 | retagged |
Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.
If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post
15 | retagged |
Update on 31.8.2015: 1.1.7.28 will be rolled out to all our users today. The update process will take a long time to complete (especially the file system optimizations), please be patient.
In some cases (<1% so far in the early access group), it has taken about 1.5-2 hours where the upgrade was stuck at 95-99%. The on-device update texts have been adjusted to warn about this issue.
If you have developer mode enabled, you may enable persistent logging to help us get logs to identify this issue: In /etc/systemd/journald.conf, change Storage=volatile to Storage=automatic and create /var/log/journal before downloading the update. Change it back to volatile after the upgrade goes through.
As the issue remains open at the moment, we've added a new feature in 1.1.7.28 to enable persistent logs during software upgrade process. Should this issue reoccur while upgrading to 1.1.9, you will be able to retrieve logs from affected devices to assist the debugging.
Please ensure that you have ~1.5GB of free disk space before attempting to upgrade your Jolla. This release introduces a new build toolchain, which means almost all packages will get updated: The more space you have, the better. If connected to the internet, your Jolla should receive an OS update notification shortly.
As usual,
For detailed instructions on updating software, visit Zendesk
CVE-2013-7423 CVE-2014-0172 CVE-2014-8116 CVE-2014-8117 CVE-2014-8484 CVE-2014-8485 CVE-2014-8501 CVE-2014-8502 CVE-2014-8503 CVE-2014-8504 CVE-2014-8737 CVE-2014-9402 CVE-2014-9447 CVE-2014-9496 CVE-2015-0247 CVE-2015-1472 CVE-2015-1473 CVE-2015-1572 CVE-2015-2806 CVE-2015-3143 CVE-2015-3144 CVE-2015-3145 CVE-2015-3148 CVE-2015-3153
/etc/systemd/journald.conf
change Storage=volatile
to Storage=automatic
and create /var/log/journal
before downloading the update. Change it back to volatile after the upgrade went through.The full changelog is available in a separate post