<Wizzup>
might get a bit painful on our few linux forks, but yeah :D
<mkf>
good evening.
Juest has quit [Ping timeout: 245 seconds]
Juest has joined #maemo-leste
pere has quit [Ping timeout: 276 seconds]
<mkf>
internal error means a seg fault?
<mkf>
where should i look for core dump?
pere has joined #maemo-leste
<sicelo>
Wizzup: cool. Will have a look at that. Otherwise, search per repository is still fine overall.
<sicelo>
back to my inhibit monologue 🤭 ... what happens if, while doing system updates via HAM, the user initiates shutdown?
<sicelo>
Everything is a nail when all you have is a hammer (and my hammer is inhibit locks) ... this is one area where an inhibit lock would fit well. when HAM UI is open, it would take the lock until it is done
<sicelo>
anyhow, long term project, but maybe I should open an issue so it doesn't get forgotten someday
arno11 has joined #maemo-leste
<arno11>
mkf: core dumps appear in /home/user
<arno11>
Wizzup: @calls issue: seems to be a pulseaudio crash when it stops ringing (according to sphone logs). if no ringtone (silent mode), no crash
<arno11>
i looked @PA changes between PA 14 and 16, the only diff is module-gconf (missing in PA 16), all other config files seem similar
<arno11>
i tried to increase shm a bit more (and a lot more), same issue
<arno11>
if i play a music file and call the n900 (silent mode), no issue and remixing between call audio and music works as usual
<arno11>
so the issue seems related to ringtone but i really don't know how to monitor what's going on
<sicelo>
maybe stop PA and run it manually in debug mode, then hopefully it'll tell you what causes the crash?
<arno11>
i see it in sphone logs: it crash @/src/pulse/thread-mainloop.c
<arno11>
function pa_threaded_mainloop_stop()
<arno11>
line 166
<arno11>
will try later with PA debug mode
<arno11>
hmm in fact PA is aborting and sphone crash and restart with no issue
<arno11>
any ringtone issue on daedalus d4 btw ?
lyubov has quit [Read error: Connection reset by peer]
lyubov has joined #maemo-leste
_fab has quit [Quit: _fab]
ceene has quit [Ping timeout: 245 seconds]
Daanct12 has quit [Quit: WeeChat 4.5.2]
arno11 has left #maemo-leste [#maemo-leste]
_fab has joined #maemo-leste
<freemangordon>
sicelo: made one comment on mce patch, not sure how to link to it
<sicelo>
thanks! saw the email. will implement
uvos__ has quit [Ping timeout: 260 seconds]
<dsc_>
freemangordon: ehm.. I have a AMD 3600x laying around if you want it for free
<dsc_>
it will be faster than this 2011 cpu :x
_fab has quit [Read error: Connection reset by peer]
<Wizzup>
will add some repos and oauth2 a bit later
<dsc_>
nice
System_Error has quit [Remote host closed the connection]
vectis_ has joined #maemo-leste
<arno11>
cool
System_Error has joined #maemo-leste
lyubov has quit [Read error: Connection reset by peer]
mkftab has joined #maemo-leste
<mkftab>
hello from converstions
<mkfx>
Hello mkf
<mkftab>
Wonderful, this thing works much better than chimaera
lyubov has joined #maemo-leste
akossh has joined #maemo-leste
mkftab has quit [Ping timeout: 272 seconds]
Livio has joined #maemo-leste
<mkf>
do we have debug symbols in repositories?
<mkf>
for maemo packages
<arno11>
usually yes, pkg_name-dbgsym
<mkf>
wonderful.
<mkf>
going from beowulf to chimaera to daedalus have been quite a big bump on reousrces used in this poor tablet. hm.
<mkf>
i wonder if i can somehow conserve ram and cpu usage.
pere has quit [Ping timeout: 268 seconds]
<Wizzup>
mkf: there should not have been an increase
<arno11>
indeed, and you can even expect better perfs (a bit) with daedalus
<mkf>
i think it's not in leste side, but general gnu/linux stuff getting fatter over the releases
<arno11>
hmm on n900, ram and cpu usage is quite low on daedalus, i mean not higher than chimaera
<arno11>
btw, how things work with qt5 on your tablet ?
<mkf>
i'm not sure.
<mkf>
telegram wrecks havoc, converstions is peaceful
<mkf>
telegram used to be better in chimaera
<arno11>
ah
<arno11>
maybe you have troubles with Qt5
<mkf>
could be. how can i check?
uvos__ has quit [Quit: Konversation terminated!]
<arno11>
i.e are qt apps very slow to launch ?
<arno11>
like calculator or calendar ?
<mkf>
i'll test.
<mkf>
should i test right after boot or i can wait a while until things are fully loaded
<mkf>
(in other words, do maemo-launcher loads qt5 stuff?)
<arno11>
no maemo-launcher for qt unfortunately
<mkf>
alright.
<arno11>
yes you can wait to be sure all things are fully loaded
<sicelo>
i wonder if there's some way to have 'signal' that things have settled :-)
<arno11>
good question
<sicelo>
then we could simply display a banner on screen ("Booting. Please wait ..."), and when everything settles, we can auto-close this banner. It's ugly, but might help us not end up with N900s thrown against walls
<arno11>
yes definitely
<sicelo>
the answer probably depends on knowing what is causing that initial 'hang'
<arno11>
mhm
<sicelo>
Wizzup: any idea how to 'restart' the status applets without reboot?
<arno11>
you mean hildon-status-menu ?
<sicelo>
yes
<arno11>
just killall it, it restarts immediately
<sicelo>
cool. i remember now, from when you had some other problem ... was it the IM account Online indication?
<arno11>
yes :)
<mkf>
btw sicelo, do you have problems with telegram on leste?
<sicelo>
i haven't run telegram in ages. arno11 does though ..
<mkf>
ah
<mkf>
mine barely works. going to settings panel gives a segfault, which i couldn't debug since debian lacks a lot of debugsyms
<arno11>
telegram is very slow to start
<arno11>
around 40-60 sec on n900 and hang for 2 min on daedalus and then works fine
<arno11>
no hang on chimaera but it was an older tg version and no qt5 troubles
<arno11>
mkf: sorry, didn t see your segfault msg
<arno11>
yes the segfault is common issue
<arno11>
you have to do a long press on buttons to avoid segfault
<mkf>
odd.
<arno11>
yep
<arno11>
and you need a proper alsoft.conf file in /.config to avoid audio issues
<mkf>
there is also a error of no seat in that tablet during the boot in daedalus
<arno11>
ah
<arno11>
battery related
<sicelo>
mkf: consistent? or intermittent? (no seat during boot)
<mkf>
qalendar loads in like 5s
<mkf>
sicelo: consistent
<mkf>
also no matter how many times i charge it, it always needs calibration
<mkf>
it got really better recently, but i think that might be a bug somewhere. (hi james)
<sicelo>
what do you have in /sys/class/power_supply?
<mkf>
axp20x-battery/ axp20x-usb/ axp22x-ac/
<mkf>
blindly enabled them all.
<sicelo>
oh, i think PP has that one too (or at least same family)
<sicelo>
i was hoping `capacity` would be writeable ... your device has same problem as Droid 4, where on boot, calibration is lost. at least on D4 you are able to write the capacity, so there's a service which stores the last calibration when you poweroff, and restores it at boot, before upower starts
<sicelo>
what does `health` contain?
<mkf>
Good
<mkf>
fwiw, this device has very generic batteries
<sicelo>
in fact, show what's in `uevent`
<mkf>
idk if they are smart or dumb
<mkf>
also capacity tells `100`
<Wizzup>
mkf: maybe the dist upgraded added some weight