IRC log for #maemo on 20180501

00:04.01*** join/#maemo jon_y (~enforcer@2001:e68:4075:165d:f64d:30ff:fe63:5a5a)
00:21.16*** join/#maemo infobot (ibot@rikers.org)
00:21.16*** topic/#maemo is Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | "firmware" see ~lf (or ~tabletsdev ~combined ~emmc ~flasher) sdk: ~sb | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet
00:21.16*** mode/#maemo [+v infobot] by ChanServ
00:38.11*** join/#maemo xes (~xes@unaffiliated/xes)
00:47.22*** join/#maemo Hurrian (~hurrian@unaffiliated/rikanee)
03:21.14*** join/#maemo auenf (~David@CPE-58-168-43-190.lns7.cht.bigpond.net.au)
03:25.33*** join/#maemo tm (~sinnlos@unaffiliated/tm)
03:36.33*** join/#maemo auenfx8 (~David@CPE-58-168-43-190.lns7.cht.bigpond.net.au)
03:38.21*** join/#maemo LauRoman (~LauRoman@5-14-47-78.residential.rdsnet.ro)
03:42.40*** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian)
03:52.47*** join/#maemo pagurus` (~user@i59F6086F.versanet.de)
04:37.56*** join/#maemo phlixi (~phlixi@ppp-46-244-214-45.dynamic.mnet-online.de)
06:59.05*** join/#maemo dafox (~dafox@89.200.46.91)
08:01.57*** join/#maemo Pali (~pali@Maemo/community/contributor/Pali)
08:24.38*** join/#maemo atk (~Arch-TK@ircpuzzles/staff/Arch-TK)
08:26.18*** join/#maemo atk (~Arch-TK@ircpuzzles/staff/Arch-TK)
09:37.43*** join/#maemo geaaru (~geaaru@151.60.64.85)
10:02.45*** join/#maemo xy2_ (~xy2_@94.239.177.175)
10:15.30*** join/#maemo Vajb (~Vajb@85-76-139-104-nat.elisa-mobile.fi)
10:27.50*** join/#maemo vakko_ (~vakko@vlan-149-game-131.comnet.bg)
12:04.58*** join/#maemo shentey (~shentey@x55b4ab6c.dyn.telefonica.de)
12:28.12*** join/#maemo sunshavi (~user@181.64.192.62)
12:31.07*** join/#maemo nyakze (~nyakze@2001:bc8:4400:2100::26:f03)
13:31.31*** join/#maemo ecc3g (~eccerr0r@2602:46:3913:b400:5054:ff:fe37:7e04)
14:36.04*** join/#maemo vahe (~vahe@unaffiliated/vahe)
14:38.24*** join/#maemo xes (~xes@unaffiliated/xes)
14:54.15*** join/#maemo halftux (~halftux@i59F6BEE5.versanet.de)
15:05.01halftuxDocScrutinizer51: alarmed also segfaults on my device could fix it by editing alarmed_gui.py line 9 replace "PySide" with "PyQt4" not tested further if it really works
15:05.30DocScrutinizer05hmmm
15:06.34DocScrutinizer05I wonder if the maemo clock been replaced in CSSU. I also wonder how to find out if or if not
15:07.03halftuxDocScrutinizer51: btw psmisc-gnu is in extras-devel
15:07.13DocScrutinizer05oooh nice
15:07.51DocScrutinizer05do you think you could promote to testing?
15:08.05halftuxah you were talking about maemo alarm not alarmed will look if cssu changed something
15:09.25halftuxyeah sure can promote it to testing it installs and deinstalls and the binaries are working so far what I tried. The user needs to manage the path variable themself.
15:09.30DocScrutinizer05yes, the thing that opens when you click time/date in status menu
15:09.58DocScrutinizer05the alarmclock function there - absolutely life critical to me
15:11.10DocScrutinizer05we discussed updating this piece of software in CSSU, long ago. My major concetrn about it was *exactly* this: don't do it until you are 100% sure it's as reliable as the original
15:11.54DocScrutinizer05possibly alarm clock is even more re4levant and mission critical than the whole phone call functionality
15:12.01halftuxyou changed something lately? Maybe this kind of database file about alarms is corrupted
15:12.05DocScrutinizer05no
15:12.14DocScrutinizer05not really, except updates
15:12.27halftuxcssu testing?
15:12.30DocScrutinizer05yep
15:13.18DocScrutinizer05and the alarm worked, but segfaulted some point in time around me snoozing the alarm
15:14.02DocScrutinizer05luckily I was already awake enough to realize what happened and get up, since obviously the alarm never came back from that segfaulting snooze
15:14.50DocScrutinizer05could check if I got some postmortem dump lingering around somewhere
15:15.30DocScrutinizer05anyway alarm clock segfaulting is a TOTAL NOGO
15:16.02DocScrutinizer05if it was Nokia's failt, I'd sue them for a missed flight
15:16.08DocScrutinizer05fault even
15:16.47DocScrutinizer05missed flight plus all the damage resulting from that
15:16.50halftux:-)
15:19.07DocScrutinizer05now how do I verify which binary and libs my system uses for the alarmclock?
15:19.16DocScrutinizer05apt? ls?
15:19.25DocScrutinizer05cssu changelogs?
15:19.37DocScrutinizer05alarmd --version?
15:20.16DocScrutinizer05hmm
15:20.19DocScrutinizer05IroN900:~# alarmd --version
15:20.20DocScrutinizer051.1.16+0m5+0cssu1
15:20.26DocScrutinizer05no surprise, that's expected
15:20.27halftuxgood question I think there are many packages involved
15:20.44DocScrutinizer05indeed, the alarm clock != alarmd
15:20.47halftuxclockd alarmd clock-ui
15:21.00DocScrutinizer05clock-ui is what I glare at
15:21.10halftuxyou on thumb?
15:21.25DocScrutinizer05nope
15:21.27DocScrutinizer05IroN900:~# clockd --version
15:21.28DocScrutinizer05Attempt to remove filter function 0xcca8 user data (nil), but no such filter has been added
15:22.03DocScrutinizer05clock-ui doesn't exist by that name
15:22.09DocScrutinizer05maemo-clock-ui?
15:22.53*** join/#maemo auenf (~David@CPE-58-168-43-190.lns7.cht.bigpond.net.au)
15:22.55DocScrutinizer05IroN900:~# apt-cache search clock-ui
15:22.56DocScrutinizer05clock-ui - UI part of the clock
15:22.58DocScrutinizer05clock-ui-dbg - Debug symbols for clock-ui application
15:22.59DocScrutinizer05IroN900:~# clock-ui
15:23.01DocScrutinizer05bash: clock-ui: command not found
15:23.22halftuxworldclock
15:23.26DocScrutinizer05duh
15:23.28halftuxas binary
15:24.31DocScrutinizer05http://wklej.org/id/3430784
15:24.59DocScrutinizer05took a while to return, I bet it opened a dialog on device screen ;-P
15:25.18DocScrutinizer05indeed it did
15:26.01DocScrutinizer05HMMM
15:26.04DocScrutinizer05IroN900:~# ls -l `which worldclock.launch`
15:26.05DocScrutinizer05-rwxr-xr-x 1 root root 450744 2017-10-24 04:42 /usr/bin/worldclock.launch
15:26.39halftuxworldclock inside maemo-invoker
15:26.48DocScrutinizer05of course
15:27.07DocScrutinizer05that's why I checked *.launch, not worldclock
15:27.34DocScrutinizer05worldclock itself is only a symlink to maemo-launcher or maemo-invoker
15:28.09DocScrutinizer05IroN900:~# ls -l `which worldclock`
15:28.11DocScrutinizer05lrwxrwxrwx 1 root root 13 2017-11-29 18:35 /usr/bin/worldclock -> maemo-invoker
15:28.52DocScrutinizer05HMMMs on the mdate though
15:29.09DocScrutinizer052017-10-24 04:42
15:29.41DocScrutinizer05checks his backups for that file, pre that date
15:30.16*** join/#maemo parazyd (~parazyd@2a03:b0c0:2:d0::f7:f001)
15:30.16*** join/#maemo parazyd (~parazyd@devuan/developer/parazyd)
15:30.39*** join/#maemo chfoo (~chfooZnc@nullhound.fart.website)
15:31.04*** join/#maemo deepy- (deepy@wrongplanet/deepa)
15:31.24DocScrutinizer05GRRRR
15:31.34DocScrutinizer05jr@saturn:~> sudo ls -l /home/jr-backup-hardlinked-2014-03-30/jr/Documents/N900/backup/iron900/usr/bin/worldclock.launch
15:31.36DocScrutinizer05root's password:
15:31.37DocScrutinizer05-rwxr-xr-x 4 jr users 102032 10. Mär 2010  /home/jr-backup-hardlinked-2014-03-30/jr/Documents/N900/backup/iron900/usr/bin/worldclock.launch
15:32.10DocScrutinizer05note the filesize too!
15:32.32*** join/#maemo how900 (~Neo900@chat.dyne.org)
15:32.32*** join/#maemo how900 (~Neo900@neo900/coreteam/communications/how)
15:32.38DocScrutinizer05*dislike*
15:33.21DocScrutinizer05what the hell was wrong with that file so it needed to get replaced by a 4 times larger one that segfaults?
15:34.02*** join/#maemo Trizt (~user@ukko.aho.hk)
15:34.40*** join/#maemo till (~till@vispillo.org)
15:37.23DocScrutinizer05IroN900:~# find /var -name '*worldcl*' -ls
15:37.24DocScrutinizer05689320    4 -rw-r--r--   1 root     root            2 Apr 29 10:02 /var/lib/dsme/rich-cores/worldclock
15:37.37*** join/#maemo auenf (~David@CPE-58-168-43-190.lns7.cht.bigpond.net.au)
15:37.58DocScrutinizer05pretty precisely the segfault time... But... 2 bytes?
15:38.56DocScrutinizer05content: "2<CR>"
15:39.21halftuxhmm don't know not much information
15:39.45DocScrutinizer05I wonder how to find out where coredumps are supposed to be stored
15:40.00DocScrutinizer05some syscfg stuff iirc
15:42.45DocScrutinizer05dafaq, infinite spamming in syslog:
15:42.47DocScrutinizer05Apr 30 07:16:48 IroN900 mce[810]: Error when reading from /dev/input/event4: No such device
15:42.48DocScrutinizer05Apr 30 07:16:48 IroN900 mce[810]: GLIB CRITICAL ** GLib - g_io_channel_seek_position: assertion `(error == NULL) || (*error == NULL)' failed
15:45.31DocScrutinizer05http://wklej.org/id/3430803
15:46.34DocScrutinizer05so here you are: g_strrstr: assertion `needle != NULL' failed
15:46.50DocScrutinizer05junkie?
15:51.40DocScrutinizer05here you are:
15:51.42DocScrutinizer05IroN900:~# ls -l /media/mmc1/core-dumps/*world*
15:51.44DocScrutinizer05-rwxrwxrwx 1 user root 4168169 2018-04-29 10:02 /media/mmc1/core-dumps/worldclock-8551-11-13155.rcore.lzo
15:51.45DocScrutinizer05-rwxrwxrwx 1 user root 7210448 2018-04-14 09:51 /media/mmc1/core-dumps/worldclock-8551-11-14336.rcore.lzo
15:53.06DocScrutinizer05*cough*
15:53.09DocScrutinizer05IroN900:~# du -sh /media/mmc1/core-dumps
15:53.10DocScrutinizer05200M    /media/mmc1/core-dumps
15:54.09DocScrutinizer05http://termbin.com/t3cd
15:57.35halftuxthats something oh fahrplan crashes too
15:59.02DocScrutinizer05the other one is just dsme's silly crashcounters:
15:59.04DocScrutinizer05IroN900:~# cat /var/lib/dsme/rich-cores/camera-ui
15:59.06DocScrutinizer0518
15:59.34halftuxwhat you did to get the core-dumps saved? I don't have something similar on my device
15:59.52DocScrutinizer05prolly installed rich-cores
16:00.57DocScrutinizer05sp-rich-core - Rich core
16:01.17DocScrutinizer05the sp-* stuff is pretty useful
16:01.37DocScrutinizer05see sp-rich-core-postproc
16:02.50DocScrutinizer05IroN900:~# apt-cache policy sp-rich-core
16:02.51DocScrutinizer05sp-rich-core:
16:02.53DocScrutinizer05<PROTECTED>
16:03.12halftuxah I see from the tools repo
16:03.37DocScrutinizer05apt-cache search '^sp-'
16:04.01DocScrutinizer05yeah
16:04.03DocScrutinizer05<PROTECTED>
16:04.04DocScrutinizer05<PROTECTED>
16:05.06DocScrutinizer05hmmm >>sp-error-visualizer - Displays errors (or anything from stdin) as banners<<
16:11.34DocScrutinizer05~pkg
16:11.34infobotpkg is probably http://maemo.org/packages/
16:21.34DocScrutinizer05after IroN900:~# rich-core-extract /media/mmc1/core-dumps/worldclock-8551-11-14336.rcore.lzo  :  http://wklej.org/id/3430837
16:28.23DocScrutinizer05halftux: http://maemo.cloud-7.de/tmp/paste/
16:39.19*** join/#maemo dafox (~dafox@89.200.45.164)
16:44.13halftuxok grabbed the files, 25.3mb unpacked its huge
16:50.04DocScrutinizer05well, the binary is already 0.45 MB
16:50.51DocScrutinizer05and prolly my syslog is already 10MB uncompressed ;-)
16:51.21DocScrutinizer05this thing gets spammed with such a lot of crap... incredible
16:51.36DocScrutinizer05most of which is WLAN related I guess
16:51.56bencohsicelo: not sure it works better for me (gps/supl) but I'll have a look at the forum post, thanks
16:52.14bencoh(I'm currently on the go)
16:52.26DocScrutinizer05or Apr 30 07:16:48 IroN900 mce[810]: Error when reading from /dev/input/event4: No such device   Apr 30 07:16:48 IroN900 mce[810]: GLIB CRITICAL ** GLib - g_io_channel_seek_position: assertion `(error == NULL) || (*error == NULL)' failed
16:54.10DocScrutinizer05could you check ls /dev/input/event4 on your system?
16:54.12bencohI do see some traffic (tcpdump) though
16:54.55DocScrutinizer05bencoh: enabling 3G helps a friggin lot, much better than any SUPL
16:55.22DocScrutinizer05~gsm-agps
16:55.22infobotRRLP is the Radio Resource LCS (Location Service) Protocol as specified first in GSM TS 04.31, or http://osmocom.org/projects/security/wiki/RRLP
16:55.48DocScrutinizer05~U-TDOA
16:55.48infobotu-tdoa is probably http://en.wikipedia.org/wiki/U-TDOA
17:07.07DocScrutinizer05bencoh: make sure your system time is correct
17:07.54DocScrutinizer05without correct time and a good estimation at least about the country you're in, SUPL can't work it seems
17:08.39DocScrutinizer05this also means not only system time but also timezone shall be set correctly
17:38.32*** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse)
17:39.59*** join/#maemo xy2_ (~xy2_@94.239.177.175)
17:44.25DocScrutinizer05there's a good reason GPS is an integrated part of the modem
17:44.52DocScrutinizer05it just benefits a lot from RRLP
18:00.55*** join/#maemo ab (~ab@vda.li)
18:00.56*** join/#maemo ab (~ab@pdpc/supporter/professional/ab)
18:18.15*** join/#maemo dafox (~dafox@2a02:a448:c25a:1::2)
19:04.18*** join/#maemo xes (~xes@unaffiliated/xes)
20:40.02*** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian)
20:55.06*** join/#maemo xes (~xes@unaffiliated/xes)
21:16.07*** join/#maemo Kabouik- (~kabouik@38.ip-37-187-46.eu)
21:22.33*** join/#maemo Oxyd76 (~quassel@5.18.99.0)
22:56.24*** join/#maemo wicket64 (~wicket@dynamic-186-30-182-100.dynamic.etb.net.co)
23:31.32*** join/#maemo Kilroo (~Kilroo@71.71.97.50)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.