**** BEGIN LOGGING AT Wed May 21 02:59:58 2014 May 21 07:18:16 2300 will be pointless, 2038 is the maximum POSIX time May 21 07:35:06 sixwheeledbeast: is that actually still the case? May 21 07:35:21 I figured that people would actually be switching the typedef over to 64 bit by now May 21 08:28:48 it's been 64bit for most systems for a while now May 21 08:30:28 not on maemo.. May 21 08:31:31 eeeh May 21 08:31:36 just recompile shit May 21 08:37:06 is this enough only to recompile? You need a update of glibc and (maybe) kernel etc May 21 08:37:26 recompile everything May 21 08:37:38 except the closed bits May 21 08:37:43 fuck the closed bits May 21 09:05:06 moin :) May 21 14:43:58 It's the closed bits that are the issue. May 21 14:48:12 maemo doesn't matter with this May 21 14:48:18 strictly speaking of course :P May 21 14:48:32 unless people are going to still be using their n900s in 2038 May 21 14:48:48 even neo900 should be 64 bit time friendly shouldn't it? May 21 14:49:10 neo900 gehts a 64 bit cpu now? May 21 14:49:19 (I assume that we won't *happen* to have prebuilt binaries for the new cpu) May 21 14:49:28 Humpelstilzchen: try "long long" on your 32 bit cpu May 21 14:49:32 it gets you a 64 bit number May 21 14:49:54 which needs more then one register.. May 21 14:50:04 which you can do May 21 14:50:20 you just do the equivalent of e_x on i386 May 21 14:50:27 one register is the low portion, one register is the high portion May 21 14:51:31 and guess how much software is parsing time_t to int May 21 14:51:48 time_t in a struct will also fail May 21 14:52:04 64bit will break alignment May 21 14:52:29 Humpelstilzchen: which is why things need to be recompiled May 21 14:52:37 you don't think that this stuff is handled upstream by now? May 21 14:53:11 no, not enough 64 bit ARMs May 21 14:53:22 but that's the magical thing May 21 14:53:39 pretty much everything that runs on maemo prefers running on x86 May 21 14:53:46 which has been 64 bit friendly for over a decade May 21 15:25:25 hmm DocScrutinizer05, actually my problem with my screen blinking (yesterday) isn't really fixed by disassembling the device. I don't have any syslog file in /var/log, only dmesg filled with "kb_lock (GPIO 113) is now open" (and closed) May 21 15:25:47 slide events (GPIO 71) are normal, when I open/close the lid May 21 15:27:19 LOL May 21 15:27:34 your lockswitch is broken May 21 15:28:23 and dimming the screen is one natural thing tk_lock does May 21 15:28:46 hmm the lockswitch okay May 21 15:29:13 is there a way to tell maemo to ignore events sent by this switch ? May 21 15:29:45 maybe it has its own driver which can be added to modules.blacklist? May 21 15:29:59 please check channel backscroll and log, I answered this question some week(?) ago, the guy was able to work around broken lockswitch iirc May 21 15:30:44 I wasn't on this chan before yesterday, but if there is a log somewhere, I will be very glad to read it May 21 15:31:06 found May 21 15:31:14 my irssi title bar wasn't long enough May 21 15:31:23 there seems to be a pretty simple /sys/bla/foo/bar/gpio113/enable node (or similar name), which takes 0 as an argument May 21 15:31:33 okay thx May 21 15:31:51 yw May 21 15:34:44 [2014-05-04 Sun 15:26:18] DocScrutinizer05, where should i put "echo 1 > /sys/devices/platform/gpio-switch/kb_lock/disable" now? not in rcS, right? ) May 21 15:35:25 all hail to 9999 lines of backscroll May 21 15:35:37 meik: ^^^ May 21 15:36:38 ~phonecontrol May 21 15:36:40 somebody said phonecontrol was http://wiki.maemo.org/Phone_control May 21 15:37:39 hmm it's not on there... May 21 15:37:50 sixwheeledbeast: ?? May 21 15:38:02 dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_start_manual_vibration int32:250 int32:3000 May 21 15:38:29 anybody know what each int does? May 21 15:38:50 amplitude, duration ? May 21 15:38:53 guessing m/s of something May 21 15:39:07 speed -255,255 May 21 15:39:11 duration in milliseconds May 21 15:39:20 spee -255, awesome ;-P May 21 15:39:30 [-255..255] I mean May 21 15:39:31 hi javispedro!!!!! May 21 15:39:44 heck, long time no see May 21 15:39:45 hi May 21 15:40:31 thx DocScrutinizer05 :) May 21 15:40:37 yw May 21 15:41:36 meik: you don't by any chance own vdv's device now? May 21 15:42:11 haha nope May 21 15:42:43 well, then it seems we have another systematic weak spot / point of failure in N900 May 21 15:43:08 it started behaving that way a few weeks ago, but since it's not my main phone, I didn't bother May 21 15:43:27 which is good to know about, in case somebody plans to build a device with a similar switch May 21 15:44:31 yep, I've seen that there is a "neo900" which is planned May 21 15:44:43 btw I guess holding device face/screen down should "fix" the broken switch May 21 15:45:24 ? May 21 15:46:06 the hallswitch ? May 21 15:46:43 hmm prolly not, the switch already *is* "upside down" when screen facing up May 21 15:47:07 bencoh: this is about lockswitch May 21 15:47:15 oh May 21 15:47:28 Yep, thanks, speed maximum 255 and duration in m/s May 21 15:47:40 sixwheeledbeast: sure thing May 21 15:48:10 javispedro: interested in Neo900? May 21 15:48:29 we could use a gifted hacker like you May 21 15:49:10 "we" probably is "fptf" here May 21 15:49:45 ~fptf May 21 15:49:46 i guess fptf is the Fremantle Porting Task Force, see http://talk.maemo.org/showthread.php?t=91308 May 21 15:50:55 but also relevant is dos1's work: https://www.youtube.com/watch?v=p1IM9Vd2_2s May 21 15:57:15 http://talk.maemo.org/showthread.php?p=1426013#post1426013 ff May 21 15:58:14 >>Hopefully I'll soon be able to record similar video, but with Fremantle instead of Replicant/SHR. That would be a great milestone for "NeoFremantle" project << May 21 16:08:06 DocScrutinizer05: sadly no commitments from me these days May 21 16:09:39 a pity May 21 16:09:56 too much RL? May 21 16:10:30 not this week I hope, but it'll get worse again soon. May 21 16:18:50 javispedro: anyway please share your thoughts about Neo900 any time you feel there's enough free time for you to do May 21 17:28:55 HMMM! http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/RTCOM seems missing a "diagram" that never been there. Daniel Wilms forgot to add it? May 21 17:30:17 >>The diagram below shows the entities of the RTCOM subsystem,...<< already in initial page, also no such diagram in initial page. http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Architecture/RTCOM&oldid=21136 May 21 18:30:40 is it possible to create a wireless hotspot with a N900 so i can connect to the internet using a laptop whats close by? May 21 18:35:22 wizbit: I don't think there's anything about that on the wiki page for tethering May 21 18:35:34 Mobile HotSpot is in the applications May 21 18:35:40 oh May 21 18:35:43 then presumably you can :P May 21 18:35:49 and Qt Mobile Hotspot May 21 18:35:56 have to find out whats the best May 21 18:36:17 Qt Mobile Hotspot May 21 18:36:28 generally if you see an x and Qt x, Qt x is the newer one May 21 18:36:44 ace May 21 18:41:01 wizbit: the wiki seems to say that you basically use bluetooth to set up ppp it seems? May 21 18:41:06 but maybe mobile hotspot will actually do wifi May 21 18:41:24 since I'm a poor american on at&t I only get edge, so tethering isn't really worth it. I have no experience May 21 18:59:44 wizbit: Note that those don't actually use wi-fi module as hotspot, instead they create an ad-hoc connection May 21 19:00:42 There is also some proprietary software, forgot how it's called May 21 19:02:11 Qt Mobile Hotspot also allows you to share the connection via USB, not only Wi-Fi May 21 19:11:10 * Tekk_ recommends sharing via usb May 21 19:11:17 I always find it more reliable than wifi when tethering on any phone May 21 19:31:16 hello, i had an error on apt-get remove. where can i find the log file for apt/dpkg? May 21 19:31:24 there isn't one May 21 19:31:51 mtnman: also you probably shouldn't use apt-get May 21 19:31:54 it makes DocScrutinizer05 angry :D May 21 19:32:02 it can also mess up your system May 21 19:32:14 hm? May 21 19:32:15 (which is why it makes him angry :P) May 21 19:32:24 DocScrutinizer05: isn't it your constant advice to never use apt-get? May 21 19:32:24 why should i worry about that? May 21 19:32:29 * mtnman likes apt-get May 21 19:32:33 least that's what I recall last time I used it May 21 19:32:38 Tekk_: nope May 21 19:32:45 it's not an advice to not use apt May 21 19:32:50 Tekk i need a better reason May 21 19:32:53 it's a mandate of not asking for support after using apt May 21 19:33:03 don't use apt-get unless you exactly know what you're doing May 21 19:33:12 mtnman: I may be misremembering this, but basically there's a very tiny OS partition May 21 19:33:17 and bad things happen when you fill it May 21 19:33:24 when you use ham it puts it in an application partition and symlinks it in May 21 19:33:32 DocScrutinizer05: about right? May 21 19:33:39 nope May 21 19:33:42 oh May 21 19:33:46 ham doesn't do any special thing with packages May 21 19:33:47 so what's the ham magic then? May 21 19:33:51 there isn't one May 21 19:34:00 don't listen to kerio May 21 19:34:03 Tekk_ i know that apt and ham dont sync May 21 19:34:23 i'm trying to clean out cruft identified by deborphan May 21 19:34:33 of course HAM does things that apt-get doesn't, and sometimes those are vital May 21 19:34:34 can''t do that with ham May 21 19:34:35 mtnman: don't trust the dependencies May 21 19:34:50 kerio explain May 21 19:35:00 dependencies for at least some packages are fucked May 21 19:35:09 system packages, that si May 21 19:35:09 is May 21 19:35:14 maemo dependencies are fucked for almost everything May 21 19:35:15 especially stuff that comes from nokia May 21 19:35:26 yes May 21 19:35:38 * mtnman has used apt for years and LIKES it May 21 19:35:48 sure, everybody does May 21 19:36:08 see May 21 19:36:12 ~jrtools May 21 19:36:15 [jrtools] http://wiki.maemo.org/User:Joerg_rw/tools May 21 19:36:38 i don't like getting ppl telling me to be scared of something without explaining the danger May 21 19:37:11 me neither, but then I didn't tell you anything like that May 21 19:37:22 mtnman: HAM doesn't let you do anything to packages that aren't marked as "user" May 21 19:37:31 exactly May 21 19:37:34 ah May 21 19:37:39 kerio fine. May 21 19:38:04 but how can i find out what apt (dpkg) did? is there really no log file? May 21 19:38:31 apt-get install procps will yield surprising unpleasant results May 21 19:39:02 Doc i'm just trying to uninstall cruft identified by deborphan May 21 19:39:13 that "cruft" might be needed May 21 19:39:32 apt-get upgrade also will, particularly when you enabled extras-devel (the latter is identical to HAM though) May 21 19:39:56 apt-get autoremove is a terrible idea May 21 19:40:03 kerio how so? deborphan only flags pkgs that have no dependencies May 21 19:40:07 ... May 21 19:40:07 as is apt-get dist-upgrade May 21 19:40:16 dependencies for at least some packages are fucked May 21 19:40:21 mtnman: because as it was noticed before, deps are fucked May 21 19:40:23 quit tellng me what doesn't work and please answer my questions May 21 19:40:24 as it was mentioned* May 21 19:40:57 ~fapman May 21 19:40:58 from memory, fapman is Faster Application Manager, a frontend for apt which uses own repositories catalog, and shouldn't be used to do system upgrades (like CSSU). It also does "apt-get autoremove" after every operation, by default. in short, it's deprecated May 21 19:41:47 hmm, let's see May 21 19:41:49 ~mp May 21 19:41:52 from memory, mp is Northern Mariana Islands May 21 19:42:02 *shrug* May 21 19:42:15 the questions is: is there a log file or other way to find out more info about error msgs reported by apt-get? May 21 19:42:31 paste it here, we'll try to take a look at it May 21 19:42:37 there's no logfile May 21 19:42:55 "paste it here" ??? really now? May 21 19:42:59 Errors were encountered while processing: May 21 19:42:59 libcityinfo-settings-002 May 21 19:43:00 E: Sub-process /usr/bin/dpkg returned an error code (1) May 21 19:43:05 mtnman: DocScrutinizer05 linked to a page which gave you logs May 21 19:43:19 did I? May 21 19:43:35 i did not see anything like that May 21 19:43:44 DocScrutinizer: yeah May 21 19:43:58 http://wiki.maemo.org/User:Joerg_rw/tools May 21 19:44:03 that seems to have an apt wrapper for logs May 21 19:44:05 mtnman: there should be something before that May 21 19:44:12 http://wiki.maemo.org/User:Joerg_rw/tools#Miniwrapper_for_apt-get_logs. May 21 19:44:13 didn't know there's sth about apt logs there May 21 19:44:28 Tekk but that won't help after the fact. May 21 19:44:47 ooh, that May 21 19:45:03 that's logging user actions, not apt's diagnostic output May 21 19:45:50 ah May 21 19:46:01 so how can i find out what went wrong with libcityinfo-settings during apt-get remove? May 21 19:47:25 anyone? bueller? May 21 19:47:49 apt-get install -f May 21 19:47:59 for "fix" May 21 19:48:10 and pay attention to what's going on May 21 19:48:38 also, wasn't there a --simulate aka dryrun? May 21 19:48:55 the problem was with the config part of the installation May 21 19:49:02 you can't dryrun that, it's arbitrary shell scripts May 21 19:49:12 :nod: May 21 19:50:04 I think the postrm script gets stored somewhere and you can inspect and rerun it, though May 21 19:50:50 var/lib/apt/*/*/... ? May 21 19:52:32 /var/lib/dpkg/something May 21 19:53:45 well thanks for tryingbut my question problem remains unsolved. May 21 19:53:50 hm.. May 21 19:55:24 your last question been >>so how can i find out what went wrong with libcityinfo-settings during apt-get remove?<<, the answer to that been I think the postrm script gets stored somewhere and you can inspect and rerun it, though /var/lib/dpkg/something May 21 19:56:37 wasn't there some way to install meego on the microsd card? I thought I saw something about it on the wiki but I can't seem to find it now May 21 19:56:48 * Tekk_ is sufficiently bored that it seems like an okay idea, if he can find a mirror with the image May 21 19:56:50 doc i did not find the postrm scripst, but dpkg -s says the config files are still there May 21 19:57:53 they don't seem to be in /etc so i'm perplexed May 21 19:58:01 ls May 21 19:58:03 oops May 21 19:58:04 AFAIK apt-get remove is supposed to keep the config files, that's a feature. To remove config files use apt-ger purge May 21 19:58:31 actually i did apt-get --purge remove foopkg May 21 19:59:49 nitdroid would be interesting too I guess, but I'm afraid of how android will "run" on 256 MB of ram May 21 20:00:01 use dpkg -P May 21 20:00:14 for what? May 21 20:00:24 to purge again May 21 20:00:27 even if it's not installed May 21 20:00:51 afaik -P == --purge May 21 20:00:54 eyup May 21 20:01:01 ~maemo-multiboot May 21 20:01:03 i heard maemo-multiboot is deprecated, and a horrible hack. PROBLEMS WITH NITDROID/MULTIBOOT? reflash rootfs&kernel aka COMBINED May 21 20:01:04 but apt-get will just give up if the package isn't installed May 21 20:01:37 kerio what do you mean? that is not clear to me May 21 20:02:01 apt!=dpkg May 21 20:02:27 oh... ok... sorry i parsed it incorrectly May 21 20:02:29 apt-get --purge != dpkg -P May 21 20:03:59 similar result from dpkg May 21 20:04:28 well, just restore your backup May 21 20:04:32 we are all aware that apt is a front-end for dpkg, aren't we? May 21 20:05:14 I don't like the tone in here, cya l8r May 21 20:05:58 kerio if you are talking to me about backup then i'm not sure you understand what i'm trying to accomplish. May 21 20:06:13 * mtnman did the dpkg -P and got a similar result May 21 20:06:17 I'm sure you didn't mention it May 21 20:06:43 mtnman: you're clearly better than us, why are you asking us for advice? May 21 20:06:52 i'm out May 21 20:11:19 deborphan, ohmy May 21 20:16:03 * DocScrutinizer05 sets up an autoresponder "quit tellng me what doesn't work and please answer my questions" --> "*PLONK*" May 21 20:16:44 everything after that been wasted time anyway May 21 20:34:10 ok i'm pretty sure i figured out my problem with apt-get --purge and failure of the post-rm script... seems there is an error in the script!! May 21 20:34:52 ORLY? May 21 20:35:03 guess i should submit a bug report. May 21 21:26:11 libcityinfo-settings-002? Where did he even get that package? May 21 21:41:19 IroN900:~# apt-cache policy libcityinfo0-0 May 21 21:41:21 libcityinfo0-0: May 21 21:41:22 Installed: 0.5.15-1+0m5 May 21 21:41:24 Candidate: 0.5.15-1+0m5 May 21 21:41:25 Version table: May 21 21:41:27 *** 0.5.15-1+0m5 0 May 21 21:41:28 500 https://downloads.maemo.nokia.com ./ Packages May 21 21:43:52 http://maemo.org/packages/view/libcityinfo0-0/ May 21 21:44:27 for sure a brilliant idea to uninstall that May 21 21:44:39 $ [ "libcityinfo-settings-002" == "libcityinfo0-0" ] && echo true || echo false May 21 21:44:41 false May 21 21:45:18 there's no such stuff like libcityinfo-settings-.* on my system May 21 21:45:27 and I don't even know where from you got that May 21 21:46:14 That's the package he tried to remove May 21 21:46:37 oooh, 2014-05-21 Wed 21:42:59] libcityinfo-settings-002 May 21 21:46:49 nfc May 21 21:47:05 package interface doesn't know of it either May 21 21:47:25 this suggests it's not even in extras-* May 21 21:47:42 I only found this log: http://pastie.org/1048904 May 21 21:47:55 prolly he installed it from a .deb downloaded from acme.org May 21 21:48:43 (which demonsrates utility of dist-upgrade on fremantle btw) May 21 21:48:52 dist-upgrade??? OUUUUUUUUUCH! May 21 21:49:26 hxka: exactly! May 21 21:49:43 well, he likes apt! ;-) May 21 21:50:17 * DocScrutinizer05 humms "love hurts..." May 21 21:51:13 http://www.youtube.com/watch?v=IJ7Myy7Hpxw May 21 21:55:22 seems to indicate libcityinfo-settings-002 is a "patch" to original libcityinfo *system* package that somebody uploaded to extras(-devel) in a misguided attempt to fix nokia's core maemo system. We got CSSU for that, exactly because it doen't work that way May 21 21:56:20 I think it's from US variant of N900 firmware, actually May 21 21:56:33 but hey, when people love apt, what can you do. Can't stop love May 21 21:56:54 002 stinks, yes May 21 21:57:57 dunno what's US variant of COMBINED fiasco. Is it "02"? May 21 21:58:55 let's check in my comprehensive backup of tabletsdev May 21 21:59:04 https://bugs.maemo.org/show_bug.cgi?id=6878#c10 May 21 21:59:06 04Bug 6878: UK Country variant of firmware not available for download May 21 21:59:15 UK? May 21 21:59:45 Maemo 5 USA variant for Nokia N900 - May 21 21:59:47 RX-51_2009SE_1.2009.42-11.002_PR_COMBINED_002_ARM.bin May 21 21:59:56 thought as much May 21 22:00:42 so finally we found one difference between US and global/EU variant? the libcityinfo May 21 22:01:22 (whatever that actually does) May 21 22:01:50 * DocScrutinizer05 thinks libcityinfo is related to TZ setting based on next larger city May 21 22:02:04 a flawed design May 21 22:03:54 it's for sure easier for me to look at next watch to get the current local time, and then the system checks the offset to UTC, rather than me looking up next larger city known to libcityinfo. Particularly when I'm abroad and don't know shit about even the city I'm in May 21 22:04:53 the heck, sometimes I couldn't even spell the city I'm in May 21 22:05:25 but I *always* been able to find out about semi-correct local time May 21 22:05:30 in a few seconds May 21 22:06:30 and then there's always GPS, if everything else fails May 21 22:07:06 "next larger city known by libcityinfo" PFFFFFF! May 21 22:07:30 I replaced mr0 with 002 in SSU repo URL, and indeed, there is a libcityinfo-settings-002 package May 21 22:07:55 ok May 21 22:08:09 still a silly idea to uninstall it May 21 22:08:15 "Customisation package for Cityinfo Library", it says May 21 22:08:57 not in HAM, I guess May 21 22:09:15 Sure May 21 22:09:24 Section: libs May 21 22:09:35 OOOOoooo May 21 22:09:42 OOOooo love hurts May 21 22:10:02 ;-P May 21 22:10:33 * DocScrutinizer05 tries hard to get rid of dark sarcasm May 21 22:11:19 oooh, btw, ebay leaked *all* user credentials May 21 22:12:11 I already seen my email addr (known nowhere else, basically) getting used to send SAPM *to* it (not *from* it - ... yet?) May 21 22:12:57 well, _potentially_ "all" May 21 22:13:06 prolly heartbleed, I guess May 21 22:13:15 so unclear what they actually leaked May 21 22:16:03 The whole content of that package is this gconf schema, lol: http://privatepaste.com/ee964b2d3c May 21 22:20:03 And the package failed to remove because postrm contains rmdir -p --ignore-fail-on-non-empty $OLD_DIR May 21 22:20:23 which of course busybox doesn't support May 21 22:22:46 Stock busybox, that is May 21 22:23:01 Hilarious May 22 01:01:26 indeed May 22 02:07:51 DocScrutinizer: infobot joined! May 22 02:08:06 about time **** BEGIN LOGGING AT Thu May 22 02:25:12 2014 **** ENDING LOGGING AT Thu May 22 02:59:58 2014