[3.2.0] System upgrade leaves lots of junk in memory

Question

5

[3.2.0] System upgrade leaves lots of junk in memory

Tracked by Jolla

asked 2019-10-29 18:18:46 +0300

Giacomo Di Giacomo

8691 ●117 ●144 ●160

After the upgrade I find myself with several gigabytes less available in the already scarce home partition. Any safe advice to remove installation junk without risking to cause harm?

Comments

1

Happened to me too. For me the upgrade through gui failed (kept downloading over and over again), so I upgraded through terminal. Now the home partition has gone from ca. 6 GB to 1,4 GB.

tmy ( 2019-10-29 21:56:26 +0300 )

GUI and terminal failed for me (it was known later that it was a Store issue), then I made the final update via GUI and it worked.

Giacomo Di Giacomo ( 2019-10-30 10:15:01 +0300 )

1

The same happened to me. I got a "No more storage" toast warning, and what a surprise to see in Storage that the "User data" partition had 0 B available O_o (compared to at least 3GB before upgrading). Here is what my .cache/tracker dir was looking like before clearing it through Utilities:

[nemo@Sailfish tracker]$ du -sh *
4.0K    db-locale.txt
4.0K    db-version.txt
14M     meta.db
7.2M    meta.db-shm
3.6G    meta.db-wal
352K    ontologies.gvdb
0       parser-sha1.txt

Sthocs ( 2019-11-16 21:05:40 +0300 )

add a comment

Happened to me too. For me the upgrade through gui failed (kept downloading over and over again), so I upgraded through terminal. Now the home partition has gone from ca. 6 GB to 1,4 GB.
tmy ( 2019-10-29 21:56:26 +0300 )
GUI and terminal failed for me (it was known later that it was a Store issue), then I made the final update via GUI and it worked.
Giacomo Di Giacomo ( 2019-10-30 10:15:01 +0300 )
The same happened to me. I got a "No more storage" toast warning, and what a surprise to see in Storage that the "User data" partition had 0 B available O_o (compared to at least 3GB before upgrading). Here is what my .cache/tracker dir was looking like before clearing it through Utilities:
[nemo@Sailfish tracker]$ du -sh * 4.0K db-locale.txt 4.0K db-version.txt 14M meta.db 7.2M meta.db-shm 3.6G meta.db-wal 352K ontologies.gvdb 0 parser-sha1.txt
Sthocs ( 2019-11-16 21:05:40 +0300 )

Accepted Answer

6

answered 2019-10-29 19:08:29 +0300

Giacomo Di Giacomo

8691 ●117 ●144 ●160

Solved by clearing tracker cache via Sailfish Utilities. Weird thing, I wonder if somebody else experienced it and if it was really due to the installation process.

link

Comments

Solved it for me too.

tmy ( 2019-10-29 21:59:38 +0300 )

Had this earlier (cannot rememebr whether JollaC or XA2) and resetting tracker helped

peterleinchen ( 2019-10-29 22:42:59 +0300 )

How did you do that? please a description for dummies... ;-)

Raymaen ( 2019-10-29 22:52:55 +0300 )

3

@Raymaen Install Sailfish Utilities from Jolla Store. It will provide a new option in settings, use that to find the relevant option.

addydon ( 2019-10-30 04:40:41 +0300 )

add a comment

[3.2.0] System upgrade leaves lots of junk in memory

Comments

1 Answer

Comments

Question tools

Stats

Related questions

[3.2.0] System upgrade leaves lots of junk in memory

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions