**** BEGIN LOGGING AT Tue May 01 03:00:06 2018
May 01 15:05:01 <halftux> DocScrutinizer51: 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
May 01 15:05:30 <DocScrutinizer05> hmmm
May 01 15:06:34 <DocScrutinizer05> I wonder if the maemo clock been replaced in CSSU. I also wonder how to find out if or if not
May 01 15:07:03 <halftux> DocScrutinizer51: btw psmisc-gnu is in extras-devel
May 01 15:07:13 <DocScrutinizer05> oooh nice
May 01 15:07:51 <DocScrutinizer05> do you think you could promote to testing?
May 01 15:08:05 <halftux> ah you were talking about maemo alarm not alarmed will look if cssu changed something
May 01 15:09:25 <halftux> yeah 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.
May 01 15:09:30 <DocScrutinizer05> yes, the thing that opens when you click time/date in status menu
May 01 15:09:58 <DocScrutinizer05> the alarmclock function there - absolutely life critical to me
May 01 15:11:10 <DocScrutinizer05> we 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
May 01 15:11:54 <DocScrutinizer05> possibly alarm clock is even more re4levant and mission critical than the whole phone call functionality
May 01 15:12:01 <halftux> you changed something lately? Maybe this kind of database file about alarms is corrupted
May 01 15:12:05 <DocScrutinizer05> no
May 01 15:12:14 <DocScrutinizer05> not really, except updates
May 01 15:12:27 <halftux> cssu testing?
May 01 15:12:30 <DocScrutinizer05> yep
May 01 15:13:18 <DocScrutinizer05> and the alarm worked, but segfaulted some point in time around me snoozing the alarm
May 01 15:14:02 <DocScrutinizer05> luckily I was already awake enough to realize what happened and get up, since obviously the alarm never came back from that segfaulting snooze
May 01 15:14:50 <DocScrutinizer05> could check if I got some postmortem dump lingering around somewhere
May 01 15:15:30 <DocScrutinizer05> anyway alarm clock segfaulting is a TOTAL NOGO
May 01 15:16:02 <DocScrutinizer05> if it was Nokia's failt, I'd sue them for a missed flight
May 01 15:16:08 <DocScrutinizer05> fault even
May 01 15:16:47 <DocScrutinizer05> missed flight plus all the damage resulting from that
May 01 15:16:50 <halftux> :-)
May 01 15:19:07 <DocScrutinizer05> now how do I verify which binary and libs my system uses for the alarmclock?
May 01 15:19:16 <DocScrutinizer05> apt? ls?
May 01 15:19:25 <DocScrutinizer05> cssu changelogs?
May 01 15:19:37 <DocScrutinizer05> alarmd --version?
May 01 15:20:16 <DocScrutinizer05> hmm
May 01 15:20:19 <DocScrutinizer05> IroN900:~# alarmd --version
May 01 15:20:20 <DocScrutinizer05> 1.1.16+0m5+0cssu1
May 01 15:20:26 <DocScrutinizer05> no surprise, that's expected
May 01 15:20:27 <halftux> good question I think there are many packages involved
May 01 15:20:44 <DocScrutinizer05> indeed, the alarm clock != alarmd
May 01 15:20:47 <halftux> clockd alarmd clock-ui
May 01 15:21:00 <DocScrutinizer05> clock-ui is what I glare at
May 01 15:21:10 <halftux> you on thumb?
May 01 15:21:25 <DocScrutinizer05> nope
May 01 15:21:27 <DocScrutinizer05> IroN900:~# clockd --version
May 01 15:21:28 <DocScrutinizer05> Attempt to remove filter function 0xcca8 user data (nil), but no such filter has been added
May 01 15:22:03 <DocScrutinizer05> clock-ui doesn't exist by that name
May 01 15:22:09 <DocScrutinizer05> maemo-clock-ui?
May 01 15:22:55 <DocScrutinizer05> IroN900:~# apt-cache search clock-ui
May 01 15:22:56 <DocScrutinizer05> clock-ui - UI part of the clock
May 01 15:22:58 <DocScrutinizer05> clock-ui-dbg - Debug symbols for clock-ui application
May 01 15:22:59 <DocScrutinizer05> IroN900:~# clock-ui
May 01 15:23:01 <DocScrutinizer05> bash: clock-ui: command not found
May 01 15:23:22 <halftux> worldclock
May 01 15:23:26 <DocScrutinizer05> duh
May 01 15:23:28 <halftux> as binary
May 01 15:24:31 <DocScrutinizer05> http://wklej.org/id/3430784
May 01 15:24:59 <DocScrutinizer05> took a while to return, I bet it opened a dialog on device screen ;-P
May 01 15:25:18 <DocScrutinizer05> indeed it did
May 01 15:26:01 <DocScrutinizer05> HMMM
May 01 15:26:04 <DocScrutinizer05> IroN900:~# ls -l `which worldclock.launch`
May 01 15:26:05 <DocScrutinizer05> -rwxr-xr-x 1 root root 450744 2017-10-24 04:42 /usr/bin/worldclock.launch
May 01 15:26:39 <halftux> worldclock inside maemo-invoker
May 01 15:26:48 <DocScrutinizer05> of course
May 01 15:27:07 <DocScrutinizer05> that's why I checked *.launch, not worldclock
May 01 15:27:34 <DocScrutinizer05> worldclock itself is only a symlink to maemo-launcher or maemo-invoker
May 01 15:28:09 <DocScrutinizer05> IroN900:~# ls -l `which worldclock`
May 01 15:28:11 <DocScrutinizer05> lrwxrwxrwx 1 root root 13 2017-11-29 18:35 /usr/bin/worldclock -> maemo-invoker
May 01 15:28:52 * DocScrutinizer05 HMMMs on the mdate though
May 01 15:29:09 <DocScrutinizer05> 2017-10-24 04:42
May 01 15:29:41 * DocScrutinizer05 checks his backups for that file, pre that date
May 01 15:31:24 <DocScrutinizer05> GRRRR
May 01 15:31:34 <DocScrutinizer05> jr@saturn:~> sudo ls -l /home/jr-backup-hardlinked-2014-03-30/jr/Documents/N900/backup/iron900/usr/bin/worldclock.launch
May 01 15:31:36 <DocScrutinizer05> root's password:
May 01 15:31:37 <DocScrutinizer05> -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
May 01 15:32:10 <DocScrutinizer05> note the filesize too!
May 01 15:32:38 <DocScrutinizer05> *dislike*
May 01 15:33:21 <DocScrutinizer05> what the hell was wrong with that file so it needed to get replaced by a 4 times larger one that segfaults?
May 01 15:37:23 <DocScrutinizer05> IroN900:~# find /var -name '*worldcl*' -ls
May 01 15:37:24 <DocScrutinizer05> 689320    4 -rw-r--r--   1 root     root            2 Apr 29 10:02 /var/lib/dsme/rich-cores/worldclock
May 01 15:37:58 <DocScrutinizer05> pretty precisely the segfault time... But... 2 bytes?
May 01 15:38:56 <DocScrutinizer05> content: "2<CR>"
May 01 15:39:21 <halftux> hmm don't know not much information
May 01 15:39:45 <DocScrutinizer05> I wonder how to find out where coredumps are supposed to be stored
May 01 15:40:00 <DocScrutinizer05> some syscfg stuff iirc
May 01 15:42:45 <DocScrutinizer05> dafaq, infinite spamming in syslog:
May 01 15:42:47 <DocScrutinizer05> Apr 30 07:16:48 IroN900 mce[810]: Error when reading from /dev/input/event4: No such device
May 01 15:42:48 <DocScrutinizer05> Apr 30 07:16:48 IroN900 mce[810]: GLIB CRITICAL ** GLib - g_io_channel_seek_position: assertion `(error == NULL) || (*error == NULL)' failed
May 01 15:45:32 <DocScrutinizer05> http://wklej.org/id/3430803
May 01 15:46:34 <DocScrutinizer05> so here you are: g_strrstr: assertion `needle != NULL' failed
May 01 15:46:51 <DocScrutinizer05> junkie?
May 01 15:51:40 <DocScrutinizer05> here you are:
May 01 15:51:42 <DocScrutinizer05> IroN900:~# ls -l /media/mmc1/core-dumps/*world*
May 01 15:51:44 <DocScrutinizer05> -rwxrwxrwx 1 user root 4168169 2018-04-29 10:02 /media/mmc1/core-dumps/worldclock-8551-11-13155.rcore.lzo
May 01 15:51:45 <DocScrutinizer05> -rwxrwxrwx 1 user root 7210448 2018-04-14 09:51 /media/mmc1/core-dumps/worldclock-8551-11-14336.rcore.lzo
May 01 15:53:06 <DocScrutinizer05> *cough*
May 01 15:53:09 <DocScrutinizer05> IroN900:~# du -sh /media/mmc1/core-dumps
May 01 15:53:10 <DocScrutinizer05> 200M    /media/mmc1/core-dumps
May 01 15:54:09 <DocScrutinizer05> http://termbin.com/t3cd
May 01 15:57:35 <halftux> thats something oh fahrplan crashes too
May 01 15:59:02 <DocScrutinizer05> the other one is just dsme's silly crashcounters:
May 01 15:59:04 <DocScrutinizer05> IroN900:~# cat /var/lib/dsme/rich-cores/camera-ui
May 01 15:59:06 <DocScrutinizer05> 18
May 01 15:59:34 <halftux> what you did to get the core-dumps saved? I don't have something similar on my device
May 01 15:59:52 <DocScrutinizer05> prolly installed rich-cores
May 01 16:00:57 <DocScrutinizer05> sp-rich-core - Rich core
May 01 16:01:17 <DocScrutinizer05> the sp-* stuff is pretty useful
May 01 16:01:37 <DocScrutinizer05> see sp-rich-core-postproc
May 01 16:02:50 <DocScrutinizer05> IroN900:~# apt-cache policy sp-rich-core
May 01 16:02:51 <DocScrutinizer05> sp-rich-core:
May 01 16:02:53 <DocScrutinizer05>   Installed: 1.35+0m5
May 01 16:03:12 <halftux> ah I see from the tools repo
May 01 16:03:37 <DocScrutinizer05> apt-cache search '^sp-'
May 01 16:04:01 <DocScrutinizer05> yeah
May 01 16:04:03 <DocScrutinizer05>  *** 1.35+0m5 0
May 01 16:04:04 <DocScrutinizer05>         500 http://repository.maemo.org fremantle/tools/free Packages
May 01 16:05:06 <DocScrutinizer05> hmmm >>sp-error-visualizer - Displays errors (or anything from stdin) as banners<<
May 01 16:11:34 <DocScrutinizer05> ~pkg
May 01 16:11:34 <infobot> pkg is probably http://maemo.org/packages/
May 01 16:21:34 <DocScrutinizer05> after IroN900:~# rich-core-extract /media/mmc1/core-dumps/worldclock-8551-11-14336.rcore.lzo  :  http://wklej.org/id/3430837
May 01 16:28:23 <DocScrutinizer05> halftux: http://maemo.cloud-7.de/tmp/paste/
May 01 16:44:13 <halftux> ok grabbed the files, 25.3mb unpacked its huge
May 01 16:50:04 <DocScrutinizer05> well, the binary is already 0.45 MB
May 01 16:50:51 <DocScrutinizer05> and prolly my syslog is already 10MB uncompressed ;-)
May 01 16:51:21 <DocScrutinizer05> this thing gets spammed with such a lot of crap... incredible
May 01 16:51:36 <DocScrutinizer05> most of which is WLAN related I guess
May 01 16:51:56 <bencoh> sicelo: not sure it works better for me (gps/supl) but I'll have a look at the forum post, thanks
May 01 16:52:14 <bencoh> (I'm currently on the go)
May 01 16:52:26 <DocScrutinizer05> or 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 
May 01 16:54:10 <DocScrutinizer05> could you check ls /dev/input/event4 on your system?
May 01 16:54:12 <bencoh> I do see some traffic (tcpdump) though
May 01 16:54:55 <DocScrutinizer05> bencoh: enabling 3G helps a friggin lot, much better than any SUPL
May 01 16:55:22 <DocScrutinizer05> ~gsm-agps
May 01 16:55:22 <infobot> RRLP is the Radio Resource LCS (Location Service) Protocol as specified first in GSM TS 04.31, or http://osmocom.org/projects/security/wiki/RRLP
May 01 16:55:48 <DocScrutinizer05> ~U-TDOA
May 01 16:55:48 <infobot> u-tdoa is probably http://en.wikipedia.org/wiki/U-TDOA
May 01 17:07:07 <DocScrutinizer05> bencoh: make sure your system time is correct
May 01 17:07:54 <DocScrutinizer05> without correct time and a good estimation at least about the country you're in, SUPL can't work it seems
May 01 17:08:39 <DocScrutinizer05> this also means not only system time but also timezone shall be set correctly
May 01 17:44:25 <DocScrutinizer05> there's a good reason GPS is an integrated part of the modem
May 01 17:44:52 <DocScrutinizer05> it just benefits a lot from RRLP
May 02 01:25:27 <Oksana> Where does estimation of country come from? Because GPS location often shows up on equator in Papua New Guinea or something, at first, and only later jumps back into Australia, New South Wales. Inconvenient, cannot it stay at last remembered actual location until GPS lock is achieved, instead of
May 02 01:25:55 <Oksana> And yes, timezone is automatically set correctly from cellular.
May 02 01:25:55 <Oksana> going and jumping into the ocean because of initial-imprecise-pre-lock estimation?
May 02 01:51:20 <DocScrutinizer05> Oksana: I think there are several sources of info for first location estimation, TZ for example, plus actually last GPS fix, plus a number of other 
May 02 01:51:35 <DocScrutinizer05> GSM network being one
**** ENDING LOGGING AT Wed May 02 03:00:03 2018