LjL^ has joined #maemo-leste
dos- has joined #maemo-leste
antranigv_ has joined #maemo-leste
antranigv has quit [Read error: Connection reset by peer]
narodnik has quit [Ping timeout: 276 seconds]
dos has quit [Read error: Connection reset by peer]
RedM has joined #maemo-leste
narodnik has joined #maemo-leste
LjL has quit [Read error: Connection reset by peer]
RedW has quit [Ping timeout: 276 seconds]
dos- is now known as dos
LjL^ is now known as LjL
antranigv_ is now known as antranigv
xmn has quit [Quit: xmn]
Anasko has quit [Ping timeout: 252 seconds]
joerg has quit [Ping timeout: 268 seconds]
joerg has joined #maemo-leste
uvos__ has quit [Quit: Konversation terminated!]
xmn has joined #maemo-leste
ceene has joined #maemo-leste
_fab has quit [Quit: _fab]
_fab has joined #maemo-leste
<freemangordon> so, some results using a simple qtwidgets application (will post source code later on) https://paste.debian.net/1371450/
<freemangordon> Wizzup: ^^^
<freemangordon> maemo5 (or gtk2) style plugin is doing somethign very stupid
apac has joined #maemo-leste
<freemangordon> I wonder if it thinks theme has changed several times during stratup
apac has quit [Ping timeout: 265 seconds]
Twig has joined #maemo-leste
pere has quit [Ping timeout: 265 seconds]
pere has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
<Wizzup> freemangordon: good debugging
<Wizzup> freemangordon: try with gtk style plugin as well perhaps?
mkfx has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11> this libpvr weird behaviour in qt has been mentioned several times, and fyi happens 'outside' qt5 stuff like last picodrive (i.e using opengles scaling option)
<arno11> *with no any kind of tweaks
<Wizzup> that is just loading libgl or libgles and init
<arno11> yep but why it is so long and why it sometimes load/unload it several times, that's the question
<arno11> this msg never appeared in chimaera afaik
<arno11> *when loading qt apps
kiva has joined #maemo-leste
<kiva> Devuan installed to Nokia RX-72. I am not sure is wifi driver open source, but everything else should work with open-source drivers, even camera. So maybe Maemo Leste i686 someday?
<kiva> or maybe better to have generic i586 with VESA drivers for starting point?
Livio has joined #maemo-leste
<kiva> ...generic i586 for old netbooks PCs.
<Wizzup> arno11: given fmg's example , 1300ms total seems acceptable
<Wizzup> since that also has the pvr stuff in there
<Wizzup> kiva: cute
kiva has quit [Quit: Client closed]
<arno11> Wizzup: yeah indeed. i.e when i launch hamsterfiler, libpvr takes around 1-2 sec. the huge 'waiting' time happens before
<arno11> (around 10 sec before libpvr msg)
Livio has quit [Ping timeout: 264 seconds]
apac has joined #maemo-leste
apac has quit [Ping timeout: 260 seconds]
apac has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
pere has joined #maemo-leste
_fab has quit [Quit: _fab]
apac has quit [Ping timeout: 272 seconds]
_fab has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
arno11 has quit [Ping timeout: 272 seconds]
System_Error has joined #maemo-leste
Livio has joined #maemo-leste
apac has joined #maemo-leste
apac has quit [Remote host closed the connection]
apac has joined #maemo-leste
apac has quit [Ping timeout: 265 seconds]
<freemangordon> arno11: the times measured include everything
<freemangordon> so,it has nothing to do with pvr
<freemangordon> see the code https://paste.debian.net/1371530/
<freemangordon> the same code, but without using MainWindow takes 10ms
<dsc_> is this reproducable in a VM
<dsc_> probably not?
<freemangordon> maybe, didn;t try
<freemangordon> lemme do it\
<dsc_> well, I'm using the VM a lot and I didnt notice such things, just fyi
<dsc_> was just wondering if I could quickly take a look
<freemangordon> I doubt
<freemangordon> this seem IO related
<freemangordon> *seems
<dsc_> ok
<freemangordon> hmm, either my n900 TS got broken or last upgrade broke it
* freemangordon boots to fremantle
<freemangordon> TS works properly in fremantle
<freemangordon> I have a feeling that mce if kind of broken after last upgrade
<freemangordon> ugh:
<freemangordon> (process:4952): GLib-GObject-WARNING **: 19:37:05.340: g_object_get_is_valid_property: object class 'UpDevice' has no property named 'capacity-level'
<freemangordon> mce: battery_upower: Percentage: 93 -> 92
<freemangordon> mce: battery_upower: Capacity Level: � -> F`k�j�8�.���j
<freemangordon> mce: battery_upower: Voltage: 3.915000 -> 3.810000
<freemangordon> munmap_chunk(): invalid pointer
<freemangordon> sicelo: ^^^
<freemangordon> fixed
Livio has quit [Ping timeout: 264 seconds]
arno11 has joined #maemo-leste
<arno11> fremangordon: btw @TS, do you use emmc swap ? because not working TS for a while (10-60 sec) is a common issue with emmc + 6.6.y
<freemangordon> arno11: it was mce restarting every couple of seconds
<arno11> oh
<sicelo> freemangordon: thanks.
<sicelo> although based on the error and your change, most likely libupower/glib had not been updated. capacity_level is already getting set to NULL in upowbat_init.
<freemangordon> sure, but that does not change the fact the code has bug :)
<sicelo> yes, that's why i appreciate the fix :-)
<sicelo> out of curiosity, what was the TS doing?
<freemangordon> mce restarting too many times seems to end up with TS disabled
<sicelo> ah
<freemangordon> Wizzup: it is gtk2 style that adds at least 1.5 seconds startup time
<freemangordon> also, we spend lots of time parsing fontconfig
<Wizzup> freemangordon: I think it might be because we have no ofnt config set
<Wizzup> or does that make no sense?
<freemangordon> what os ofnt config?
<freemangordon> *what is
<freemangordon> in /etc/fontconfig there are lots of xml files
<freemangordon> I think those are parsed every time
<freemangordon> hmm, in fontconfig, rescan is set to 30 seconds
apac has joined #maemo-leste
<Wizzup> this seems wrong
Livio has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
uvos has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
<freemangordon> Wizzup: in any case, a simple QMainWindow application using 64 MiB seems a bit too much
<freemangordon> with maemo5 style it is even worse: ~76MiB
<dsc_> can this be attributed to whatever maemo5, in turn, links against?
<freemangordon> maemo5 style adds ~10MiB
<freemangordon> event without it mem usage is still too high
<freemangordon> I don;t have time now, but tomorrow will compile the same code on my a33, which is still on chimaera, to see what would be the memory usage there
<freemangordon> 64MiB for as single window application...
<freemangordon> *for a
Twig has quit [Ping timeout: 276 seconds]
<dsc_> https://bpa.st/raw/PTYA 80M, but I suspect many of those libs are already in memory/cached
apac has quit [Ping timeout: 265 seconds]
<Wizzup> yeah I would agree
<Wizzup> and they'd be shared
<Wizzup> freemangordon: also, even conversations doesn't use that much afaik, so that's also strange
<Wizzup> freemangordon: are you stripping your build?
apac has joined #maemo-leste
ceene has quit [Ping timeout: 244 seconds]
mkfx has left #maemo-leste [Error from remote client]
apac has quit [Ping timeout: 252 seconds]
arno11 has quit [Quit: leaving]
akossh has joined #maemo-leste
uvos has quit [Quit: Konversation terminated!]
akossh has quit [Quit: Leaving.]