on some of my devices, yes;

This is still 2.9.1.1209 from Canonical. Ofc, you are free to say "not invented here".

Hello,
On my BQ E4.5 it takes always around 10++ secs to start the gallery-app until the tiles of the pictures thumbnails are showing up. Today I was lazy and tried to figure out what might be the problem.

First, I unloaded the small sqlite database, only the table ' MediaTable' has rows of all the picture files (around 1323) and I checked with a script: all the pictures are existing.

Second, I tried to attach strace to the starting proc gallery-app, which is a bit tricky, because it is launched from the Unity desktop. But I managed it and, surprise surprise, the problem is that is spending nearly all time with nothing else at these syscalls:

stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2619, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2619, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2619, ...}) = 0
...
nearly 200.000 times:

root@ubuntu-phablet:/home/phablet# grep /etc/local gallery.tr | wc -l
192097

Any ideas what the hell it is doing with /etc/localtime?

Matthias

@unisuperbox said in mounting the root fs writable:

Basically, your changes will be clobbered. The update system will unconditionally overwrite whatever is currently on the system with its changed version.

I've never heard of remounting rw breaking the update process.

How is this "overwrite" done? Some kind of tar-archive unpacked or a tree and copied over the existing tree or some kind of to be installed click-packages, or ...?

Thanks.

All these "it worked for me for now" type messages do not lead to any secure information. Want an example based on the change of the file /etc/hosts? The next OWA will just work fine (because it does not care or update the /etc/hosts file). But some OWA in the future wants to update /etc/hosts and checks before the md5 hash of the file because its unmodified hash value is known. And stops now because the md5 hash is not the same any more.

This is only a guessed example. Without deep knowledge and information about the OWA update process, all is wild guessing.

@advocatux said in Community infrastructure: Forum and Telegram:

@guru said in Community infrastructure: Forum and Telegram:

+1 for using the (existing) mailing-list as primary channel for technical discussions and support.

Are you talking about the UBports's ones or the old Canonical's Ubuntu-Phone list?

Both would do the job. The old one even better because a lot of UT users are still subscribed there and would may be encouraged to move to the UBports devices.

@dave said in Community infrastructure: Forum and Telegram:

Hi,

I sort of start feeling old, trying to participate in UBports: An open source project without a mailing list and without IRC channel does not really integrate with the modes of communication I'm used to use.

Just tried to make a telegram account (via web.telegram.org), however it needs a phone number, and (one of my) "landline" SIP-based phone numbers is not accepted ("incorrect phone number"). I'm not really willing to give my cell phone number to an untrusted 3rd party to participate in an open-source project. I mean, if I were, then I probably would just be using Google Android and not bothering with UBports, would I :) ?

So I guess I'll have to stay at the outside for now.

cheers,

Dave

+1 for using the (existing) mailing-list as primary channel for technical discussions and support.

Matthias

There was a longer discussion about this issue in the LP mailing-list and IIRC it was some kind of resource issue. Search the archives of the mailing-list. I've see this as well two times with my E4.5 still running Canonical's OTA15.

@lakota said in Unhearable ringing:

@grepo
If it doesn't go to the ubports welcome and install Telegram group and ask there. ...

If someone ask such technical question there in the tg group, do you really think he/she will see the answer (if any) in all this chatting there? Can he later do a search for the own question and (if there are any) the answers?

matthias

Every now and then someone who is tweaking his phone, advises to re-mount the root fs writable for a short time (to change something there, install add-ons, ..). In the times of Canonical they gave the strict advice not to do so because it could make fail the OTA updates later.

Is anybody here in the position and knowledge to explain a bit, based on the structure of the OTA file distribution, what exactly could cause problems and what exactly should be avoided or not touched this way? Thanks in advance.