IRC log of #maemo for Sunday, 2013-07-21

ecc2gi'm not familiar with the recovery options on the n900 yet, but ideally you unmount that partition, fsck it and see if it will fix it.  But I'm not sure how to do that on the n900...00:00
*** valeriusL has joined #maemo00:00
FIQ|n900I've had issues with MyDocs corruption earlier and managed to fix it with some fscking and removal of corrupt stuff00:01
FIQ|n900but this is the /home partition...00:01
ecc2gyeah, that's why it's a bit tricky...00:01
FIQ|n900and not as trivial to just umount and fsck00:01
*** ZogG_laptop has joined #maemo00:01
*** ZogG_laptop has quit IRC00:01
*** ZogG_laptop has joined #maemo00:01
ecc2gthere was this recovery program...00:01
FIQ|n900doesn't ext3 have journaling though? i.e. once you *do* manage to get fsck running, it should solve problems far better than fat can do00:03
*** piggz has joined #maemo00:03
FIQ|n900I have backupmenu installed00:03
FIQ|n900perhaps the recovery terminal within it can help00:03
FIQ|n900but I never managed to get that thing usable00:03
FIQ|n900because it kept giving me nothing but a black screen00:04
DrCodehi all00:04
DrCodeI got forbiden in cute youtube when I try to download00:06
DrCodesorry , any idea?00:07
qwazixprobably youtube changed something00:07
qwazixdoes vimeo work?00:08
DrCodeI didnt check yet00:12
DrCodeI am using cssu00:12
*** NIN101 has quit IRC00:13
*** _rd has joined #maemo00:14
qwazixcssu or not it shouldn't have any effect. If vimeo download works on cutetube it means that youtube changed something to not allow video downloads00:16
FIQ|n900they've never allowed video downloads00:16
FIQ|n900people are just playing cat and mouse :P00:17
* RST38h moos00:19
*** perlite_ has joined #maemo00:19
*** perlite has quit IRC00:21
*** perlite_ is now known as perlite00:22
DocScrutinizer05FIQ|n900: fist try a manual fsck00:22
*** Ketil has joined #maemo00:22
DocScrutinizer05FIQ|n900: iirc BM has an fsck option00:23
FIQ|n900oh it has?00:23
FIQ|n900will check it out then00:24
DocScrutinizer05FIQ|n900: anyway you first should do a BM backup00:24
FIQ|n900see you in a few minutes up to some hours00:24
FIQ|n900yeah I'll do that00:24
DocScrutinizer05and don't forget to copy your ~ as well, since iirc BM does *not* backup that00:24
DocScrutinizer05then first thing to try is to remove the dir containing the garbled files, after copying the valuable files in that .xchat2/00:25
*** ketil_k has quit IRC00:25
FIQ|n900it does backup both partitions00:25
DocScrutinizer05It says it backups /opt00:25
FIQ|n900both = rootfs and 2gb00:25
FIQ|n900I assumed it meant both partitions by that00:26
DocScrutinizer05I always tend to think /opt == /home but in fact it isn't00:26
FIQ|n900I guess I can somehow backup that too...00:26
*** konelix_ has quit IRC00:26
DocScrutinizer05simply tar it up to uSD00:26
FIQ|n900don't know if cp is a good idea given those corrupt files00:26
FIQ|n900no uSD here00:27
DocScrutinizer05you tried to read from that file?00:27
FIQ|n900the corrupt file? not directly00:27
DocScrutinizer05tar it to MyDocs then00:27
FIQ|n900but I assume ls -l tries to00:27
DocScrutinizer05ls -l simply reads out the dir inodes00:27
FIQ|n900but xchat perhaps do...00:27
DocScrutinizer05what does ls say how long that file?00:28
FIQ|n900given that xchat said it was unable to open some log files for writing00:28
FIQ|n900nice how00:28
DocScrutinizer05copy everything non-garbled out of .xchat2/, then delete .xchat2/00:28
DocScrutinizer05nice like funny00:29
FIQ|n900will try it00:29
DocScrutinizer05rather, first rename the dir00:30
DocScrutinizer05mv .xchat2 garbled-shit00:30
*** kov has quit IRC00:30
*** kov has joined #maemo00:30
DocScrutinizer05ext3 journal doesn't help once the volume got mounted00:31
DocScrutinizer05not for fsck00:31
*** valeriusL has quit IRC00:32
win7macROTFL... believe it or not, there is a company named Dog Schidt...00:32
win7macand they're serious about it:
DocScrutinizer05a few other thing you can try: stat, lsof, less *00:32
win7macHave a nice trip:
FIQ|n900that might be a problem00:34
DocScrutinizer05fsck -nv /home00:38
FIQ|n900DocScrutinizer05: when I tried to cp everything, a couple of other files gave Invalid argument00:38
FIQ|n900more than these that ls couldn't bother with00:39
DocScrutinizer05which ones?00:39
FIQ|n900*everything from xchat200:39
*** dhbiker has quit IRC00:41
FIQ|n900well for example a file .xchat2/scrollback/QuakeNet/j3b|skoldator.txt - tried ls -l on that directory and saw no issues00:41
FIQ|n900could even read the file with less00:42
FIQ|n900which was a bit confusing00:42
DocScrutinizer05please pastebin whole session of yours00:43
DocScrutinizer05maybe your cp cmd actually had invalid argument?00:43
FIQ|n900not easy given lack of scrollback @terminal...00:43
FIQ|n900ah no that wasn't it00:43
FIQ|n900hmm wait let's try something00:44
*** valeriusL has joined #maemo00:44
FIQ|n900[323][user@Nokia-N900 ~/MyDocs/backups/xchat2/scrollback/QuakeNet]$ cp ~/.xchat2/scrollback/QuakeNet/* .00:45
FIQ|n900cp: kan inte skapa normal fil "./j3b|skoldator.txt": Invalid argument00:45
FIQ|n900nothing wrong with the syntax00:45
FIQ|n900and it manages to create all other files in the directory fine00:45
* DocScrutinizer05 sentimentally recalls old weird stories from the times when linux did a "mv ~/bla/ ~/bla/blaerg/bla"00:46
FIQ|n900why can I read that file but not copy it?00:47
DocScrutinizer05you shouldn't use wildcards00:47
DocScrutinizer05not to copy all the files that are not garbled00:48
DocScrutinizer05also a LANG=en_GB would be nice00:49
FIQ|n900oh yeah00:49
FIQ|n900but point is00:49
DocScrutinizer05[LANG=C doesn't work on maemo >:-(  ]00:49
FIQ|n900couldn't possibly know there wasn't any issues with the file before actually trying to copy it00:49
DocScrutinizer05well, it probably has a rotten inode in file-inodes00:50
DocScrutinizer05or a completely illegal char in filename00:50
FIQ|n900ohhhh might be that @illegal char00:51
DocScrutinizer05or it's even messybox that fails00:51
FIQ|n900or does fat support |?00:51
DocScrutinizer05messybox might not00:51
FIQ|n900no cp is gnu provided00:51
DocScrutinizer05you know wildcards get expanded by shell00:51
FIQ|n900have coreutils-gnu here00:51
FIQ|n900using bash00:51
FIQ|n900ok will try to copy it manually00:52
FIQ|n900w/o wildcarding00:52
DocScrutinizer05do a stat j*00:52
DocScrutinizer05pastebin result pls00:52
DocScrutinizer05or even tab-expand j rather than using wildcard00:52
DocScrutinizer05FIQ|n900: your last reboot resp shutdown been not a gentle one?00:53
FIQ|n900my last reboot was fine00:54
FIQ|n900however I've done some ungentle reboots earlier00:54
DocScrutinizer05no hard shutdown or anything?00:54
FIQ|n900no not last time00:55
FIQ|n900[23:54:46] <FIQ|n900> however I've done some ungentle reboots earlier00:55
FIQ|n900perhaps I should refrain from doing it unless necessary00:55
DocScrutinizer05may have hidden since00:55
FIQ|n900reason is that I usually just switch batteries w/o bothering shutting down beforehand00:55
FIQ|n900never realized it could give annoying consequences...00:56
DocScrutinizer05that's nasty00:56
FIQ|n900well apparently it wasn't a good idea00:56
DocScrutinizer05did you do a fsck -nv meanwhile?00:56
FIQ|n900btw, how do I pastebin content from terminal directly?00:56
FIQ|n900there was some curl-fu way...00:57
FIQ|n900fsck -nv hmm00:57
FIQ|n900DocScrutinizer05: that requires umounting, no?00:57
FIQ|n900even though it's simulation00:57
FIQ|n900(i.e. -n)00:57
DocScrutinizer05IroN900:/home/user# date | pastebinit00:58
FIQ|n900oh I have pastebinit apparently00:58
* FIQ|n900 forgots00:58
FIQ|n900"normal fil" sounds swedish...01:00
FIQ|n900 english localization in case you didn't like the first one01:01
DocScrutinizer05anyway, looks normal01:02
FIQ|n900(i.e. using LANG=en_GB;01:02
FIQ|n900ok will try something01:02
FIQ|n900...that didn't work01:02
FIQ|n900lang=en_GB also doesn't seem to do anything01:03
DocScrutinizer05less f*01:03
FIQ|n900touch: sätter tider på "test|a": No such file or directory01:03
FIQ|n900so basically I found the reason why *that* file failed01:03
FIQ|n900[00:03:01] <FIQ|n900> lang=en_GB also doesn't seem to do anything01:03
FIQ|n900fat doesn't like |01:03
FIQ|n900which is why cp failed with that file01:03
DocScrutinizer05sure thing01:04
FIQ|n900but still01:04
FIQ|n900ok good01:05
FIQ|n900everything cp failed was either one of the 4 files01:05
FIQ|n900or something fat didn't like01:05
DocScrutinizer05use tar01:05
FIQ|n900just taring the partition directly via /dev?01:06
*** odin_ has quit IRC01:06
DocScrutinizer05nah, I thought of taring your ~01:07
FIQ|n900wont that attempt to tar MyDocs too?01:08
FIQ|n900let's see if exclusion is possible01:08
DocScrutinizer05same-fs should be possible01:08
FIQ|n900then this I guess: tar -cf home.tar --one-file-system ~01:11
FIQ|n900btw, can this freeze the system?01:11
FIQ|n900once before when I did a big file download to MyDocs, system froze and proceed to corrupt MyDocs01:12
FIQ|n900so I'd rather avoid that01:12
*** Hurrian has quit IRC01:12
FIQ|n900btw DocScrutinizer0501:16
FIQ|n900ls: kan inte komma åt LaZ-#romhacking.log: Stale NFS file handle01:16
FIQ|n900(sorry about lack of proper localization, see above why)01:16
FIQ|n900that's the error it gives for these 4 inaccessible files01:16
FIQ|n900doesn't tell me anything, perhaps it tells you the exact issue01:17
DocScrutinizer05try find /home/user/ -n -path="*MyDoc*" -exec tar A -f home.tar {} \;01:18
FIQ|n900should I halt the execution of what I gave earlier?01:18
DocScrutinizer05about localization: LANG, not lang01:18
FIQ|n900is what I ran01:19
FIQ|n900i.e. LANG=en_GB (command)01:19
DocScrutinizer05LANG=en_EN cp --help01:20
*** odin_ has joined #maemo01:20
FIQ|n900-n fails @ find01:20
FIQ|n900unknown option01:20
FIQ|n900find: unknown predicate `-n'01:21
FIQ|n900to be exact01:21
*** Hurrian has joined #maemo01:21
DocScrutinizer05but if your other command didn't already freeze01:22
DocScrutinizer05you should let it finsih01:22
FIQ|n900it didn't freeze01:23
FIQ|n900and I let it finish01:23
FIQ|n900it only failed 8 files, 4 in .modest due to permission issues, and then the other 4 in .xchat201:23
DocScrutinizer05permission issues?01:24
FIQ|n900but I assumed there was something wrong with what I gave (like, it excluding stuff or things like that) so I tried your command as well...01:24
*** Hurrian has quit IRC01:24
FIQ|n900tar: /home/user/.modest/cache/cert8.db: Funktion "open" misslyckades: Permission denied01:24
FIQ|n900(and no didn't run that command before with LANG, sorry01:25
FIQ|n900same issue with the other .db files01:25
DocScrutinizer05what's ls -l of those?01:25
*** MadeAllUp has quit IRC01:25
FIQ|n900600, only root has access01:26
DocScrutinizer05-rw------- 1 user users  doesn't give a clue why you couldn't read it01:26
FIQ|n900also it was 3 db files, miscounted lines sorry01:26
*** Hurrian has joined #maemo01:26
*** Hurrian has quit IRC01:26
*** Hurrian has joined #maemo01:26
DocScrutinizer05flock() ?01:27
*** valeriusL has quit IRC01:27
FIQ|n900is the ls -l of that directory01:27
DocScrutinizer05~ $ cp /home/user/.modest/cache/cert8.db xxx01:28
FIQ|n900the 3 who only root can access wasn't able to be included with tar01:28
DocScrutinizer05~ $ ls -l xxx01:28
DocScrutinizer05-rw-------    1 user     users       65536 Jul 21 00:27 xxx01:28
FIQ|n900why is it only for root for me?01:28
FIQ|n900and yeah, trying the same thing logically gave "cp: cannot open `.modest/cache/cert8.db' for reading: Permission denied"01:29
DocScrutinizer05no idea01:29
FIQ|n900should it be like that?01:29
DocScrutinizer05most likely not01:30
FIQ|n900otherwise I guess I could change it with sudo...01:30
DocScrutinizer05you probably should01:30
DocScrutinizer05I guess you did some cert handling as root01:30
FIQ|n900doubt it tbh, but perhaps01:30
DocScrutinizer05back with TURKCERT01:30
qwazixwhat's the package that asks for time each time the N900 forgets it?01:31
FIQ|n900as said earlier - only these 4 files (in .xchat2) appeared to be corrupt given tar results01:31
FIQ|n900and another question you never answered01:31
DocScrutinizer05qwazix: sth like welcome01:31
FIQ|n900wouldn't fsck -nv require umounting the partition?01:31
DocScrutinizer05see my pastebin01:32
FIQ|n900ah ok01:32
qwazixhildon-welcome maybe?01:32
DocScrutinizer05hildon-welcome is shakehands iirc01:32
qwazixsafe to remove?01:32
infobotmethinks jrtools is
FIQ|n900 is the fsck result01:33
FIQ|n900doesn't sound very good to me...01:33
FIQ|n900well it only complained on one thing01:34
qwazixDocScrutinizer05, removing the file works fine, I was wondering if it would be better to remove the package too.01:34
FIQ|n900(besides the obvious issue of partition being mounted)01:34
FIQ|n900DocScrutinizer05: but as I did backup with tar, is it safe to simply shutdown and fsck via BM now?01:35
FIQ|n900I guess it's not *too* bad given only 4 files seem to have issues, all in one directory... but you never know with fs corruptions :x01:37
DocScrutinizer05I'd simply delete .xchat2 first01:37
FIQ|n900will try that01:37
*** _rd has quit IRC01:37
DocScrutinizer05stale nfslock?01:38
FIQ|n900it successfully removed everything in the directory besides those 4 yeah01:38
FIQ|n900(and their parent directories)01:38
DocScrutinizer05rm -rf01:38
FIQ|n900that's what I did01:38
DocScrutinizer05then do a fsck via BM01:39
DocScrutinizer05or even directly on mounted fs, if you can convince fsck01:39
DocScrutinizer05fsck -v should maybe do it01:40
DocScrutinizer05-V even01:41
DocScrutinizer05actually -M is needed to NOT check mounted fs, aiui01:42
DocScrutinizer05-r for "interactively"01:43
*** FIQ|n900 has quit IRC01:43
*** bef0rd has quit IRC01:45
DocScrutinizer05actually, -r isn't needed as well, for e2fsck01:45
qwazixI wonder if I replace the binary with a symlink to rdate...01:45
DocScrutinizer05yes, osso-startup-wizard01:47
*** Hurrian has quit IRC01:47
*** valeriusL has joined #maemo01:48
DocScrutinizer05qwazix: rather find where it gets called01:48
DocScrutinizer05and comment it out01:48
DocScrutinizer05less /etc/osso-cud-scripts/  :-o01:50
DocScrutinizer05 /etc/osso-rfs-scripts/ same01:50
DocScrutinizer05less /usr/share/osso-startup-wizard/mcc.txt01:53
DocScrutinizer05might as well be PIN requester01:53
*** LauRoman has quit IRC01:54
DocScrutinizer05less /usr/share/osso-startup-wizard/startup-ui-settings.config01:56
*** kolp has quit IRC01:58
*** Marshall_Banana has quit IRC01:59
*** brutal_ has joined #maemo01:59
DocScrutinizer05 /home/opt/usr/share/themes/alpha/startup-wizard/StartupWizardClockFace.png :-)02:04
DocScrutinizer05if [ -x $AF_INIT_DIR/ ]; then  wizback_method advance 1; source $AF_INIT_DIR/ start; if [ "x$AFTER_SUW_RESTART_NEEDED" != "x0" ]; then source $AF_INIT_DIR/ ;# re-read locale variables02:08
*** zap__ has quit IRC02:08
DocScrutinizer05 /etc/osso-af-init/real-af-startup02:09
*** FIQ|n900 has joined #maemo02:10
FIQ|n900well ok02:10
FIQ|n900tried to fsck that partition02:10
FIQ|n900it blamed on the 4 files mentioned, but also on some other stuff02:11
FIQ|n900and umm02:11
FIQ|n900now I have a bigger problem than before02:11
FIQ|n900well I do have ~ backed up and possible to restore02:11
FIQ|n900this is not the case with /opt though02:12
psycho_oreosIsn't /opt usually tied in with the same partition as /home?02:13
FIQ|n900I have showing now @ fsck -nv02:14
FIQ|n900psycho_oreos: yes it's the same partition, I forgot a certain step before fscking.. :D02:15
FIQ|n900the actual BM backup02:15
FIQ|n900DocScrutinizer05: should I try to erase the fs and restore an older BM backup?02:16
FIQ|n900or would that break BM before being able to restore?02:16
FIQ|n900remove the fs02:16
FIQ|n900recreate it02:16
FIQ|n900restore rootfs and optfs02:16
FIQ|n900mount MyDocs02:16
FIQ|n900untar home.tar to ~02:16
DocScrutinizer05FIQ|n900: I'd guess it should not break BM but I'm not sure02:17
DocScrutinizer05qwazix: less /etc/osso-af-init/real-af-startup  <- nice read02:17
FIQ|n900DocScrutinizer05: also - that's not everything, e2fsck actually aborted mid-processing02:17
FIQ|n900both during fsck and the fsck simulation now02:18
FIQ|n900Illegal block number passed to ext2fs_test_block_bitmap #909457187 for multiply claimed block map02:18
FIQ|n900e2fsck: aborted02:18
FIQ|n900I don't understand what it's trying to say, but well... it doesn't sound good02:18
FIQ|n900DocScrutinizer05: btw02:18
FIQ|n900fsck blamed me for having the partition mounted while doing it - but I immediately proceed to cancel the process and confirm that - it wasn't mounted at all02:19
FIQ|n900so I don't understand why it said that..?02:19
FIQ|n900or something like that02:20
DocScrutinizer05that's a nasty bug in fsck actually02:20
FIQ|n900I used bm's root console (which actually worked, didn't do it before) because bm's fsck told me to run fsck manually02:21
DocScrutinizer05it sometimes gets inconsistent about whether a fs is mounted or not02:21
FIQ|n900oh you've seen it before?02:21
DocScrutinizer05I once investigated that but forgot everything I found out02:21
FIQ|n900would the plan described above work?02:22
DocScrutinizer05I guess it should, but honestly I don't feel like recommending anything. a bit tired02:22
FIQ|n900i.e. erase optfs and recreate and restore older optfs02:22
FIQ|n900plus the home.tar02:22
FIQ|n900it should work fine, unless BM relies on stuff on /opt02:23
FIQ|n900obviously maemo wouldn't boot02:23
FIQ|n900but BM should02:23
DocScrutinizer05as soon as you nuke optfs you will find system in an inoperable state, unless you're in BM02:23
DocScrutinizer05BM *should* not rely on any opt stuff02:23
FIQ|n900yes but would rebooting make watchdog etc cease to work and break BM?02:23
FIQ|n900I recall restoring a rootfs suited for the wrong kernel earlier02:24
FIQ|n900and that broke BM horribly02:24
FIQ|n900but that was rootfs, not optfs02:24
DocScrutinizer05sure, but that's not opt related02:24
psycho_oreosBM doesn't have any of its own provided files within the installer package residing in /opt.02:25
FIQ|n900well how do I recreate the partition then? because I don't know that02:25
DocScrutinizer05when BM runs, /opt isn't mounted yet, that's the whole point of BM02:25
FIQ|n900I'm willing to try it - after all, there seems to be no other way02:25
DocScrutinizer05mkfs should suffice02:26
DocScrutinizer05but I dunno how to do that either, except via BM console02:26
FIQ|n900mkfs /dev/mmcblk0p2?02:26
FIQ|n900I'm going to use root console02:26
FIQ|n900from bm02:26
DocScrutinizer05that should work02:26
FIQ|n900no other arguments?02:27
FIQ|n900just making sure not to mess up02:27
FIQ|n900given I cannot check here meanwhile lol02:27
psycho_oreosmkfs.ext3 to be a little more specific. In case the MBR tables is a little messed up, also I'd double check with fsck -l02:28
FIQ|n900MBR tables? master boot record?02:28
FIQ|n900on n900?02:28
DocScrutinizer05well, probably you want to add arguments as needed according to man mkfs02:28
FIQ|n900well yeah02:29
FIQ|n900ok so let's see here02:29
FIQ|n900this shouldn't be too hard to just *do*02:30
FIQ|n900if it works or not is another ballgame02:30
psycho_oreos/dev/mmcblk0p2          884866      950401     2097152  83 Linux02:30
FIQ|n900btw DocScrutinizer05 any idea how to get rid of that battery message in the root console?02:30
FIQ|n900I found it somewhat annoying during fsck due to being unable to read things properly02:31
psycho_oreosRather I don't know how you describe it, the boot record that contains the tables for a storage medium02:31
DocScrutinizer05less /etc/mke2fs.conf02:31
qwazixreplacing osso_startup_wizard with a script that does rdate -s after 20s doesn't work02:33
qwazixin case anybody was curious02:33
DocScrutinizer05not exactly a surprise, qwazix02:34
qwazixat least I got rid of the annoying popup02:34
qwazixDocScrutinizer05, why?02:34
DocScrutinizer05qwazix: less /etc/osso-af-init/real-af-startup  <- nice read02:35
DocScrutinizer05FIQ|n900: I don't know what battery message you talk about02:36
FIQ|n900DocScrutinizer05: ok02:36
FIQ|n900another question before I go02:37
DocScrutinizer05might be some output of charge21.sh02:37
FIQ|n900would restoring only optfs (not rootfs) be a bad idea?02:37
DocScrutinizer05err, depends02:37
FIQ|n900latest optfs is not very recent02:37
DocScrutinizer05if it's consistent with rootfs then I dunno what should go haywire02:37
FIQ|n900well my reasoning was that perhaps some applications I've installed since, placed stuff in optfs02:38
*** Malinux has quit IRC02:38
FIQ|n900while its' state of installed is in rootfs02:38
FIQ|n900messing things up02:38
FIQ|n900if that can happen, I'll have to do a rootfs restoration too02:39
DocScrutinizer05this would render such late installed apps broken02:39
FIQ|n900and then I need to check yet another thing...02:39
*** Malinux has joined #maemo02:39
FIQ|n900which rootfs are tied to the correct kernel02:39
DocScrutinizer05you either need to do rootfs reflash then, or re-install the broken apps02:39
FIQ|n900to prevent something I managed before02:39
FIQ|n900(managed to restore a rootfs with vanilla kernel within a powerkernel install)02:40
FIQ|n900no idea how to make sure it's to the right kernel02:40
DocScrutinizer05you need to reinstall all apps then anyway, so why not just reinstall those that were installed after opt backup been done?02:41
FIQ|n900DocScrutinizer05: problem is potential apps I forget about02:41
FIQ|n900but perhaps that's not actually an issue02:41
DocScrutinizer05you can find dtale symlinks to /opt later on02:41
FIQ|n900(and perhaps such apps would expose themselves anyway)02:41
FIQ|n900well I guess I'll just restore optfs then02:42
FIQ|n900seems easier02:42
DocScrutinizer05go ahead02:42
FIQ|n900oh, can Maemo handle lack of ~?02:42
DocScrutinizer05no, not really02:42
FIQ|n900if it can, I'll simply restore home.tar once back into maemo02:42
*** Malinux has quit IRC02:43
FIQ|n900guess I'll have to restore it on root terminal then02:43
*** florian has quit IRC02:43
*** Malinux has joined #maemo02:43
DocScrutinizer05it will recreate user's home if missing, I'd guess02:43
FIQ|n900shouldn't be too hard, just wanted to get back to a comfortable environment asap :P02:43
DocScrutinizer05but as well might bootloop02:43
FIQ|n900oh well02:43
FIQ|n900see you02:43
DocScrutinizer05good luck02:44
FIQ|n900hm wait02:44
FIQ|n900will have to read manpage on amemo lol02:44
qwazixI can not understand how on earth (or any other parallel universe for that matter) reading shell scripts could be nice :P02:44
qwazixbut I see that a is called which I cannot find02:45
DocScrutinizer05visit my universe, you'd be surprised02:45
FIQ|n900DocScrutinizer05: would ext4 be a better idea btw? now that I'll need to reformat anyway02:45
DocScrutinizer05there is no startup-wizard.sh02:46
DocScrutinizer05according to locate02:46
DocScrutinizer05FIQ|n900: some claim it is02:47
DocScrutinizer05but no support in stock kernel for that02:47
FIQ|n900well I'm running powerkernel02:48
FIQ|n900but I guess better safe than sorry02:48
DocScrutinizer05then you probably should be fine02:48
DocScrutinizer05kerio: was that you who had ext4?02:48
FIQ|n900there was a wikipage on how to switch mydocs and ~.. while that's not what I'm doing, perhaps it could tell me a bit what I should do02:48
DocScrutinizer05on /home02:48
FIQ|n900(i.e. mkfs options)02:48
*** LaoLang_cool has joined #maemo02:49
DocScrutinizer05for mkfs options see what I quoted above02:49
DocScrutinizer05less /etc/mke2fs.conf02:49
qwazixIf I can find the script that checks if time == 00:00 2000/01/01 and calls osso_startup_wizard it would be awesome02:49
FIQ|n900DocScrutinizer05: ah02:49
FIQ|n900will look into it02:49
FIQ|n900qwazix: why not just get rid of hildon-welcome? though perhaps that's not what you want to do02:50
* FIQ|n900 did that a while ago02:50
*** Malinux has quit IRC02:51
DocScrutinizer05./X11/Xsession.d/30osso_startup_wizard: /usr/bin/osso_startup_wizard 1>&202:51
*** Malinux has joined #maemo02:51
DocScrutinizer05qwazix: ^^^02:52
DocScrutinizer05if [ ! -e /var/dont_start_suw ]; then02:53
qwazixFIQ|n900, I'm trying to make the N900 get the time automatically from a ntp server if bupbat is down02:54
FIQ|n900hm ok02:54
* FIQ|n900 simply uninstalled hildon-welcome02:54
FIQ|n900time is configured automatically by SIM02:54
qwazixhildon-welcome is irrelevant02:54
FIQ|n900faster and more convenient02:54
qwazixit's the shaking hands video02:55
FIQ|n900oh hmm02:55
FIQ|n900but I removed that startup thing02:55
FIQ|n900seems I recall how wrongly though02:55
FIQ|n900oh well02:56
FIQ|n900let's try fix optfs now02:56
FIQ|n900see you02:56
DocScrutinizer05you can remove /etc//X11/Xsession.d/30osso_startup_wizard02:56
*** LaoLang_cool has quit IRC02:57
*** FIQ|n900 has quit IRC03:00
qwazixdoes that script run as user or as root?03:01
qwazixnow I know why it doesn't work: the whole thing runs before wlan is up. Even if I tell it to sleep I'm just delaying the whole thing03:07
*** nox- has quit IRC03:14
*** amin007110 has joined #maemo03:16
*** Hurrian has joined #maemo03:22
*** unclouded has joined #maemo03:33
*** FIQ|n900 has joined #maemo03:35
FIQ|n900there we go03:35
FIQ|n900went unexpectedly smooth03:35
FIQ|n900even though the optfs was apparently half a year old ...03:36
FIQ|n900guess I'll run into some hiccups still not restoring both fs at the same time03:36
FIQ|n900but I at least solved the obvious issues03:36
FIQ|n900(10 icons in menu not showing up properly, grep not working properly)03:37
FIQ|n900DocScrutinizer05: do you know any way to figure out "missing" symlinks?03:37
*** dos1 has quit IRC03:37
FIQ|n900easily that is03:37
FIQ|n900or better yet, a way for apt to figure out what packages are missing files03:37
FIQ|n900DocScrutinizer51: also, worth pointing out - optfs restoration *did* restore an old ~ as well03:39
FIQ|n900I simply updated ~ with my tar on boot as it was newer than that restoration, but yeah03:39
FIQ|n900next time such issues arise, I'll tar /home rather than /home/user03:39
FIQ|n900or better yet, let BM try it first and only when it fails, do it for hand03:40
FIQ|n900*by hand03:40
DocScrutinizer05FIQ|n900: find can spot dangling symlinks I guess03:40
FIQ|n900also I should really consider restoring my xchat.conf to defaults...03:41
FIQ|n900atm it's kinda broken03:41
infobotwell, jrxchat is
FIQ|n900(it has been like that for a while now, never bothered fixing it)03:42
*** FIQ|n900 has quit IRC03:43
*** M4rtinK has quit IRC03:44
DocScrutinizer05nevertheless, for the record:  man find: >> l      symbolic link; this is never true if the -L option or the -follow option is in effect, unless the symbolic link is broken.<<03:45
*** FIQ|n900 has joined #maemo03:45
FIQ|n900there we go03:45
DocScrutinizer05[2013-07-21 02:43:43] <-- FIQ|n900 has left this server (Quit: Leaving).03:46
FIQ|n900*keybindings.conf not xchat.conf lol03:46
FIQ|n900accidentally messed keybindings earlier when trying to disable C-i idiocy03:46
FIQ|n900xchat completely ignored it >.>03:46
DocScrutinizer05nevertheless, for the record:  man find: >> l      symbolic link; this is never true if the -L option or the -follow option is in effect, unless the symbolic link is broken.<<03:47
*** bef0rd has joined #maemo03:47
FIQ|n900and apart from ignoring C-i rebinding, I also managed to mess up some other keybindings03:48
FIQ|n900so I basically just made it worse :D03:48
FIQ|n900DocScrutinizer05: nice03:49
FIQ|n900I wonder if complaining to author of xchat package could make him fix c-i idiocy03:50
FIQ|n900though I believe the real issue is upon xchat devs03:50
FIQ|n900the problem is, C-i uses their old keybinding functionality not within the configuration file03:51
FIQ|n900and in addition, C-i likes to segfault03:51
FIQ|n900the reason I use it at all is unintended - weechat (and irssi) has nickcompletion on that combination...03:52
FIQ|n900would be nice if c-i could do that instead, or at least *nothing at all* rather than crashing03:52
DocScrutinizer05ctrl-i is TAB03:53
DocScrutinizer05unless shell/xterm keybindings changed it03:54
FIQ|n900not in xchat03:55
FIQ|n900in xchat, ctrl+i breaks current window to a desktop window03:55
FIQ|n900however in n900 version (and in desktop version too! though less often), it crashes xchat03:56
DocScrutinizer05that's weird03:56
*** Avasz has joined #maemo03:56
*** Avasz has joined #maemo03:56
DocScrutinizer05for sure not implemented in n900 xchat03:56
FIQ|n900[02:54:02] <LIP> FIQ|n900: other than removing the item from the source and recompiling, not at this point03:56
FIQ|n900(in #xchat, asking if removing the combination is possible)03:57
DrCodeI want to use mail for exchange to sync exchange server , what can I use to sync gmail (calander,contact)04:00
*** jayne_ is now known as jayne04:01
DocScrutinizer05well, then that's what should be done: comment out that function completely, and while we're at it please also allow to disable the close-channel button in lower-left under the tabs list directly above the scrollbuttons for said tablist04:01
*** cerberus_ has joined #maemo04:02
*** Avasz is now known as Guest7019704:03
*** cerberus_ is now known as Avasz04:03
*** Avasz has joined #maemo04:03
*** Guest70197 has quit IRC04:03
FIQ|n900I don't follow what you mean @ the latter04:03
*** rcg has quit IRC04:03
FIQ|n900DocScrutinizer05: apparently, an user (same one as that paste was from) is already working on a patch for that issue, plus the crashing04:04
FIQ|n900so if it gets released anytime soon, I guess commenting it out wouldn't be necessary, and simply updating to upstream 2.8.10 or whatever is next is enough04:04
FIQ|n900n900's xchat port is outdated anyway04:05
bef0rdsombody should update it04:05
* bef0rd points FIQ|n90004:05
FIQ|n900bef0rd: 1) not a package manager of that package, 2) no maemo sdk :P04:05
bef0rdyou can always request access to update it04:06
FIQ|n900afaik R3st8h is the author of xchat n900 port04:06
FIQ|n900~seen r3st8h04:06
infobotFIQ|n900: i haven't seen 'r3st8h'04:06
FIQ|n900hm perhaps I recall his nick wrong04:06
*** APTX_ has joined #maemo04:07
*** APTX has quit IRC04:08
bef0rdmaybe RST38h04:08
psycho_oreos~seen RST38h04:09
infobotrst38h is currently on #maemo (16h 1m 44s) #maemo-ssu (16h 1m 44s), last said: 'The Adam generates a surge of electromagnetic energy on startup, which can erase the contents of any removable media left in or near the drive.'.04:09
FIQ|n900oh that was it04:09
*** darkschneider has quit IRC04:09
FIQ|n900RST38h: ping? also sorry for getting your nick wrong04:10
*** Avasz has quit IRC04:14
*** zammy has quit IRC04:16
FIQ|n900perhaps I should try to make it a routine to backup (opt|root)fs once a month04:16
FIQ|n900to avoid restorations from too long ago04:16
*** mschlens has joined #maemo04:19
*** mschlens_ has quit IRC04:22
*** Avasz has joined #maemo04:28
*** Avasz has joined #maemo04:28
*** triggerhappy has joined #maemo04:31
*** MetalGearSolid has joined #maemo04:37
*** hardfalcon1 has joined #maemo04:38
*** hardfalcon has quit IRC04:40
*** e-yes has joined #maemo04:43
*** Avasz has quit IRC04:48
*** FIQ|n900 has quit IRC04:57
*** Kilroo has quit IRC05:09
*** Avasz has joined #maemo05:20
*** Avasz has joined #maemo05:20
*** Kilroo has joined #maemo05:24
*** at1as has joined #maemo05:29
*** piggz_ has joined #maemo05:43
*** piggz has quit IRC05:44
*** Ketil has quit IRC05:58
*** dockane has quit IRC06:01
*** lxp has quit IRC06:03
*** dockane has joined #maemo06:05
*** Gh0sty has quit IRC06:18
*** lxp has joined #maemo06:19
*** robbiethe1st has joined #maemo06:20
*** Gh0sty has joined #maemo06:20
*** maybeHere has joined #maemo06:31
*** bef0rd has quit IRC06:32
*** bef0rd has joined #maemo06:33
*** maybeArgh has quit IRC06:33
*** ketas has quit IRC06:42
*** Mike11 has quit IRC06:44
*** ketas has joined #maemo06:50
*** AndrewX192 has quit IRC07:26
*** AndrewX192 has joined #maemo07:27
*** bef0rd has quit IRC07:52
*** AndrewX192 has quit IRC07:54
*** AndrewX192 has joined #maemo07:56
*** bef0rd_ has joined #maemo07:57
*** bef0rd_ has quit IRC08:11
*** bef0rd has joined #maemo08:12
*** bef0rd has quit IRC08:16
*** bef0rd has joined #maemo08:20
*** robbiethe1st has quit IRC08:29
*** em_ has quit IRC08:38
*** em has joined #maemo08:38
*** dhbiker has joined #maemo08:43
*** AndrewX192 has quit IRC08:50
*** bef0rd has quit IRC08:52
*** bef0rd has joined #maemo08:52
*** bef0rd_ has joined #maemo08:53
kerioDocScrutinizer05: i have ext4, yeah08:55
keriofirst, repartition and align to 4mb08:55
keriothen add the raid striping options to ext408:56
keriothen enjoy ext408:56
*** DrCode has quit IRC08:56
*** DrCode has joined #maemo08:57
*** AndrewX192 has joined #maemo09:02
*** AndrewX192 has quit IRC09:07
*** AndrewX192 has joined #maemo09:11
*** mavhc has quit IRC09:21
*** mavhc has joined #maemo09:24
*** mavhc has joined #maemo09:26
*** zammy has joined #maemo09:59
*** croppa has joined #maemo09:59
*** zap__ has joined #maemo10:13
*** florian has joined #maemo10:21
*** konelix_ has joined #maemo10:25
*** e-yes has quit IRC10:26
*** sasquatch has quit IRC10:29
*** utanapischti has joined #maemo10:29
DrCodehi all10:37
DrCodeI understand that mail for exchange can sync only 1 account, Emminnig can sync calander10:37
DrCodeis there way to sync my contact ?10:37
*** kolp has joined #maemo10:42
*** piggz_ has quit IRC10:50
*** piggz_ has joined #maemo10:51
*** jpinx has quit IRC10:52
*** flo_lap has joined #maemo10:57
*** jpinx has joined #maemo10:57
*** florian has quit IRC11:00
*** Hurrian has quit IRC11:06
*** Pali has joined #maemo11:07
*** piggz_ has quit IRC11:12
*** piggz__ has joined #maemo11:12
*** Hurrian has joined #maemo11:13
*** croppa has quit IRC11:14
*** croppa has joined #maemo11:14
*** LauRoman has joined #maemo11:15
*** shamus has quit IRC11:16
*** shamus has joined #maemo11:16
*** frafl has joined #maemo11:18
*** piggz__ has quit IRC11:39
*** amin007110 has quit IRC11:49
*** amin007110 has joined #maemo11:50
*** valeriusL has quit IRC12:07
*** valerius has quit IRC12:07
*** jayne has quit IRC12:07
*** valeriusL has joined #maemo12:07
DocScrutinizer05good (UGT) morning12:07
*** valerius has joined #maemo12:08
*** bef0rd_ has quit IRC12:08
*** bef0rd has joined #maemo12:09
*** bef0rd_ has joined #maemo12:10
*** frafl has quit IRC12:12
*** NIN101 has joined #maemo12:17
*** kolp has quit IRC12:20
*** jayne has joined #maemo12:21
*** M4rtinK has joined #maemo12:25
*** Kabouik has quit IRC12:35
*** Avasz has quit IRC12:36
*** hubutm20 has joined #maemo12:44
*** konelix_ has quit IRC12:52
*** dos1 has joined #maemo12:54
*** sq-one has joined #maemo12:58
*** kolp has joined #maemo13:01
Lava_Croftwtf tempratures13:09
Macerwhy the hell does user not have write access to MyDocs13:27
Macerand the SD?13:27
*** darkschneider has joined #maemo13:30
*** Arkenoi has quit IRC13:32
Maceryou have got to be kidding me13:33
Maceri was wondering why i can't save crap from the device to the vfat13:33
Macerand i find out that for whatever reason user doesn't hve write permissions after updating to thumb13:33
HurrianMacer: check perms, check genfstab.awk13:34
Maceri know the permissions are wrong13:40
Macerit is mounting with root:root as its owner13:41
Maceri just changed the fstab manually for MyDocs13:41
Macerand rebooted..13:41
Macerbut seriously.. wtf?13:41
Macerwhere is genfstab.awk? /etc?13:41
Macerthis is crazy13:43
Macerespecially considering MyDocs is vfat13:43
Maceri don't see a genfstab.awk13:43
Macerand you can't change perms on a vfat fs13:44
Macerthere is no genfstab.awk on my friggin n90013:45
Macerwow. this is amazing. i'm sick of bothering with using old devices. time to just suck it up ebay these and get a GS413:47
Maceran update shouldn't ruin your ability to write to your SD and MyDocs13:47
Macereven attempting to remount with mount with the uid flags set doesn't change it13:51
Macerfk this. i'll just swap the sim out move my stuff off of it and ebay it13:53
Lava_Croftand make someone else happy with a valued n900! \o/13:53
Macerif happy is the word you want to use13:54
Maceri like the n900 but when you have shit like this happen where you are trying to figure out why you can't save an img from an mms13:54
Macerit's time to go13:54
Lava_Croftn900 doesnt even support mms out of the box13:54
Macerthat should tell you a lot right there13:55
Macerbut even so13:55
*** sheepbat has joined #maemo13:55
Lava_Croftmms is deprecated13:55
Macerit isn't the mms that is the problem13:55
Macerlol. if you say so13:55
*** sheepbat has left #maemo13:55
Macerthere are still millions and millions of people who use mms to send pics13:55
Macerbut like i said13:55
Macerthat isn't the issue right now13:56
Macerright now i updated and i can't write to the vfat partitions13:56
Lava_Crofti run thumb, didnt have such a problem13:56
Macernor can i find an easy fix to do so.. so now i have to dive into it and try to figure out what went wrong13:56
Macerand why i can't do something as simple as write to MyDocs and the SD?13:56
Maceri hate to say it but these are the sorts of things that should just work. it is no wonder nokia killed maemo off :)13:57
Lava_Croftsame reason why you cannot do other 'simple' taks on other mobiles13:57
*** croppa has quit IRC13:57
Macerlike..... use PAN, MMS, and write to an SD? :)13:57
Lava_Croftblame nokia for cssu thumb update?13:57
Lava_Croftwhy dont you blame MS too, since thats fashionable13:57
* Lava_Croft huckles13:58
Macernope. but i can understand why they dropped it13:58
Lava_Croftyou cant13:58
Lava_Croftyou are just enraged13:58
DocScrutinizer05Macer: please stop ranting!13:58
*** Arkenoi has joined #maemo13:58
Lava_Croftyeah, ranting is the sole right of DocScrutinizer0513:58
* Lava_Croft chuckles some more13:59
DocScrutinizer05yes, since *I* know how to rant, while Macer just makes a fool of himself, by bitvhing about MyDocs not mounted rw13:59
Lava_Croftopinions probably differ on the first part of your sentence14:00
Lava_Croftbut the last part is correct14:00
DocScrutinizer05if that's a bug then report a bug, don't act like a defiant child that assumes everything done just to annoy him14:00
Lava_Croftand there i thought freemangordon lived off of the misery experienced by people like Macer14:01
Lava_Croftboy was i wrong!14:01
DocScrutinizer05and particularly staements like "I'm not going to do $X to get rid of this <insert-XXX-here> maemo device, and get a $X instead" is not interesting anybody in this channel14:02
Macerwell... if anybody wants to buy this thing let me know. i'm going to ebay it in a bit. i'll give it up for $15014:02
infobotDocScrutinizer05 meant: and particularly staements like "I'm now going to do $X to get rid of this <insert-XXX-here> maemo device, and get a $X instead" is not interesting anybody in this channel14:03
DocScrutinizer05I suppose you try ebay right away, since all your bitching wasn't a good PR for selling your device at that pricetag in here14:04
Macerjust figured i'd ask14:04
DocScrutinizer05150? nah14:04
DocScrutinizer05I'm also no fan of latest CSSU-T fstab hack. It's basically worth nothing and high risk, just implemented to avoid the problems it's actually introducing. But honestly, that's a CSSU-T issue, not a N900 or maemo issue14:06
Maceri would have to agree with you there14:09
Maceri still have my e7 tho. so there is that at least14:09
DocScrutinizer05but hey, all my fighting for a conservative maintenance of CSSU finally succumbed to the fanboys of bleeding edge and "we want monthly updates, no matter what for"14:09
Maceryeah. i just figured it would provide a benefit14:10
Macerseems not but to each their own. im sure devs still love n900s14:10
Macernowadays i just want something that has a qwerty and works lol14:11
Macers4 has the attachable bt qwerty so that should do the trick14:12
Macerand a msd slot. time to give up on the could've beens.14:12
Macerah well. it has been fun. good luck with everything.14:13
Lava_Croftand it has android14:14
Lava_Croftno gnu userland14:14
Lava_Croftsamsung hw14:14
Lava_Croftglass screen14:14
Lava_Crofthave fun with it!14:14
Macermeh. i will put a debian chroot on it. the touchscreen is better with multi finger support... can install cm on it to avoid ad-droid based stuff. and it can multitask just fine14:15
Macerand i am bold enough to say the samsung hw is probably a bit stronger than what the n900 is working with. ;)14:16
Lava_CroftCM is still android14:16
DocScrutinizer05stronger as in...?14:16
Lava_Croftit still has no GNU userland14:16
Lava_Croftand you need a quadcore CPU to run android without lag14:16
DocScrutinizer05sure CPU has higher clock14:17
Macerwell. not like there are many alternatives14:17
Lava_Croftsamsung captiva glide14:17
Lava_Croftat least that has a HW keyboard14:17
Macermaybe ubuntu devices will show promise14:17
Lava_Croftfriend of mine got it to replace his n90014:18
*** dhbiker has quit IRC14:18
Lava_Croftapart from android, he is rather happy with it14:18
Lava_Croftoh, and it lacks a CTRL key:)14:18
Lava_Croftbut there is a CM release for it, so14:18
DocScrutinizer05wow, that looks nice14:18
*** sq-one has quit IRC14:18
Lava_Croftits not maemo, but its not that bad14:18
Hurrianwow, uhh, that's a pretty crappy android phone.14:18
Lava_Crofti think only in the US/Asia tho14:19
Lava_Croftnot EU14:19
Lava_Croftnicer pic14:19
Hurrianmeh, get a phone with a large enough keyboard, and you won't be complaining about hwkb unless you use terminal /a lot/ to edit files in vi.14:20
Lava_Crofthw keyb > *14:20
Lava_Croftno onscreen keyboard can replace it14:20
DocScrutinizer05eeeeek! that looks like one crappy kbd, almost as crappy as N950 or eten M80014:20
*** dhbiker has joined #maemo14:20
HurrianLava_Croft: N9's touch keyboard is fine by me.14:21
Lava_Croftits no replacement14:21
Macerwas thinking more of that14:21
Lava_Croftthat will need another case to protect the screen14:22
Lava_Croftsince its samsung, the shell of the phone is made of rubber-like substance14:22
Lava_Croftmaking the phone bendable as shit14:22
Lava_Croftthats why samsung invests so heavily into flexible screens14:22
Lava_Croftthats easier than learning how to make good HW14:22
Macerlike falling off usb ports? ;)14:23
Lava_Croftnever happened to me or anyone i know with n90014:23
Lava_Crofti only know it from TMO14:23
DocScrutinizer05and the AWESOME keys it got!  "www."  ".com"  `speech input´ "smiley" "OK"14:24
Lava_Croftwelcome to android14:24
DocScrutinizer05can I please get ".de" instead of ".com" ?14:24
Macerwell... that was the 1st one i saw14:24 key is normal in android, with onscreen keyb too14:24
Macerthere are others14:24
*** darkschneider has quit IRC14:24
Macerbut they have them to get a qwerty onto an s414:24
*** Pali has quit IRC14:25
DocScrutinizer05"www." and <smiley> for sure are my alltime favorites14:25
Macerim sure they are easily remapped14:25
Macerto tab and pipe14:25
DocScrutinizer05I hope the printing on key is also scrap-off otherwise too embarrassing14:26
Macerto whom?14:26
DocScrutinizer05to the bearer14:26
Maceri doubt anybody would notice or care. maybe a cs major14:27
DocScrutinizer05I'd be ashamed to carry a device with a smiley hw key14:27
Macerand even then theyd probably just like it because it is a qwerty on an s414:27
Macercant really find too many high end phones with qwerty14:28
Macerif any at all14:28
DocScrutinizer05evem on plane-314:28
Macerprobably because you have to sell them internationally14:28
*** Pali has joined #maemo14:28
Macerwacky germans with z and y swapped14:28
psycho_oreosThe whole trend is pretty much what Apple had started, phones/devices lacking a proper hardware keyboard.14:29
Macerpsycho_oreos: it made sense tho14:29
psycho_oreosEvery other damn manufacturer just followed suit.14:29
Macerwhy make 50 different keyboards?14:29
Macerwhen a vkb is software14:29
Macerit probably saved billions so far heh14:30
psycho_oreosMacer, yeah and why not give end users no freedom to even do simple commands like copy and paste. Afterall, programmers are free to write their own vkb instead.14:30
DocScrutinizer05psycho_oreos: that's just because idiotic industry rather copies than trusting in own R&D and design department14:31
Macerwell i am sure it is all bottom line14:31
Macerlike using cheap solder points on usb ports heh14:31
DocScrutinizer05"iPhone does it this way. iPhone is market leader. So we do it same way, it must be right thing to do"14:31
Lava_Croftiphone is not market leader anywhere except the US14:32
psycho_oreosDocScrutinizer05, for various reasons on various scales, its inevitable that hardware keyboard phones/devices faces their immediate death after PDAs.14:32
Lava_CroftNetherlands is about 70 to 80% android14:32
MacerLava_Croft: but most high end ad-droid phones dont have a kb14:32
psycho_oreosThere was a time when in 2009 some of the top end android devices still featured hardware keyboard. These days hardware keyboard phones/devices are commonly found on dumb/cheap phones.14:33
DocScrutinizer05that's since android mimics iPhone14:33
Macerbut i agree on their reasoning. im sure it also helps with 3rd party international sales14:33
Lava_Croftthats because people dont WANT hw keyboards anymore14:33
Lava_Croftnot because imitating iphone14:33
DocScrutinizer05iPhone been first and always been "leader"14:33
Macersince for the most part they can be universal14:33
*** Hurrian has quit IRC14:33
DocScrutinizer05no matter about recent market share14:34
MacerLava_Croft: i think they can just live without them14:34
Macerif they had them they would use them14:34
Lava_Croftthey dont want it14:34
Lava_CroftHW keyboard equals bigger phone14:34
DocScrutinizer05but copycats like google simply ignore that even Apple might do decisions based on other rationale than mere product usability considerations14:34
Macerbut a hw kb adds bulk(weight)14:34
MacerDocScrutinizer05: cattle eat hay14:35
*** Hurrian has joined #maemo14:35
Macerif they starved to death... theyd eat something else14:36
psycho_oreosThere was a time where innovative features like 9xxx series communicator and E7 had ways to hide the hardware keyboard. Now it seems like hardware keyboard is an unecessary junk/bulk.14:36
DocScrutinizer05see "bigger phone" for example. everybody thinks the trend is to ever smaller devices, while every usability expert can elaborate why that's a deadend path. And recent devices show that trend goes to 5" or even 7" *phones*14:36
Maceri wouldnt say my e7 hides it well14:37
Lava_Croftwhere do you get such general statements from like "everybody thinks the trend is towards blabla"14:37
Maceri guess it isnt that big14:37
Macerim using it now14:37
DocScrutinizer05Lava_Croft: that's a simplified statement to summarize trend of whole industry during last 6 years14:38
DocScrutinizer05maybe last 8 except last 18 months14:38
psycho_oreosN900 isn't all that particularly big with hardware keyboard. It was probably because of the design limitations prohibit N900 to be thin, if you looked at N950 which was virtually based off E7 its noticeably thinner.14:38
Lava_Croftthe trend has been towards largest phones for quite some years14:38
Lava_Croftwith even apple copying the androids and getting a bigger screened phone14:38
Lava_Croft(after stating you would never need a bigger screen, of course)14:39
psycho_oreosLargest and thinnest phones..14:39
*** ron0062000 has joined #maemo14:39
DocScrutinizer05psycho_oreos: yep14:40
*** unclouded has quit IRC14:40
DocScrutinizer05N900 thickness is basically determined by cam module14:40
psycho_oreosThe wars between trends has always been a key factor, just yesterday I was watching N900 demo/teaser on cutetube and reading comments to see people flaming each other about N900 vs <insert_other_random_device_here_or_go_with_iPhone>14:41
DocScrutinizer05the N900 cam module seems rather poor quality regarding size, in my book14:42
*** uen| has joined #maemo14:42
psycho_oreosIn N8, they've improved (probably) that cam module but made it purely symbian.14:43
*** mvp has joined #maemo14:43
DocScrutinizer05plus it makes for that ugly annoying bump on battery cover14:43
DocScrutinizer05I would've shot the ID designers for that14:43
*** uen has quit IRC14:46
*** uen| is now known as uen14:46
DocScrutinizer05but compared to iPhone cam module it's still phantastic, hw wise (my own unsupported notion). Just that apple did a hell of a job on sw side to compensate for the shorcomings of their crap cam14:46
DocScrutinizer05which *usually* makes for nice snapshots on iPhone, unless you go to take photos under certain conditions (moved objects) where the limitations show clearly, by generating nasty artifacts14:48
DocScrutinizer05but then, Apple is a sw developer that knows his busines sw side and eventually decided to do phone hw, while Nokia been a hw developer always and also generally did a lot of outsourcing for the sw side14:49
DocScrutinizer05so the differences in design paradigms are clearly based on compny's history14:50
*** ron0062000 has quit IRC14:52
DocScrutinizer05and not even Nokia is rid of limitations the FOSS idea imposes on hw design14:52
*** darkschneider has joined #maemo14:53
DocScrutinizer05ask dm8tbr about how boneheaded companies like e.g ST-E can act when it comes to proper licensing of simple stupid .h files for e.g. GFX14:54
DocScrutinizer05iirc the MALI400 grafics core can't get used in FOSS just because ST-E refuses to GPL a already disclosed 200lines .h that's "(C) ST-Ericson"14:55
RST38hRewrite the header, use different names14:56
RST38hrearrange them in the header14:56
psycho_oreosI think if it were that simple, they would have contemplated with seriousness.14:56
RST38hpsycho: no14:56
DocScrutinizer05no, since both parties are somewhat boneheaded14:57
psycho_oreosN900 had lots of cool hardware in general, people just don't realise they could unlock the hardware's inner potential and to look at the obvious shortcomings.14:57
DocScrutinizer05well, the fcam guys did14:58
DocScrutinizer05and the blessN900 guys as well14:58
psycho_oreosIt was only then had they got these other people with <insert_random_phone_or_device_here> asking about it and wishing their manufacturer would do the same.14:58
Wizzup_mali can't be used by foss?14:59
DocScrutinizer05but still they can't compete with what a 500 heads developer team for just the cam drivers can do at Apple14:59
Wizzup_this is new to me14:59
Wizzup_I mean, there's no finished foss driver14:59
psycho_oreosThere was other things like fmtxd, the wl1251 module, the trio LED notification.14:59
DocScrutinizer05Wizzup_: that might have changed meanwhile14:59
Lava_Croftlife with the n900 is generally like this: iphone user looks at n900 and smirks about size, screen, stylus14:59
Wizzup_I have it running on my gentoo install14:59
Lava_Croftbut once anything has to be done, n900 has to do it14:59
DocScrutinizer05Wizzup_: that info is like 2 years old14:59
DocScrutinizer05maybe 314:59
Lava_Croftbecause iphone cant/wont/whatever14:59
Wizzup_DocScrutinizer05: libv and others are working on lima14:59
Wizzup_I'm hoping it finishes soon14:59
Wizzup_at least, comes around14:59
DocScrutinizer05Wizzup_: I jusz quoted that instance since I been working inside ST-E at that time, and tried to move sth about the issue with that .h file15:00
DocScrutinizer05after dm8tbr told me about it15:00
DocScrutinizer05alas Ericsson worked on the LTE modem, not the AP/GFX halve of NovaThor15:01
DocScrutinizer05so I couldn't do much15:01
*** FIQ|n900 has joined #maemo15:01
FIQ|n900there's one thing I've become tired of regarding the application "mobilehotspot"15:02
FIQ|n900every now and then, seemingly completely random, it simply doesn't start15:02
FIQ|n900the exact error being "ImportError: No module named os"15:03
FIQ|n900the solution is simply rebooting and hope it doesn't happen again15:03
FIQ|n900and if that fails, do it again (though that happens rarely)15:03
FIQ|n900any idea *what* causes this thing?15:03
DocScrutinizer05share syslog15:04
DocScrutinizer05and start mobilehotspot in terminal or with stdout/stderr redirection to a logfile15:04
psycho_oreosHe basically meant share a log where useful information can probably be extracted. Usually from the likes of dmesg/syslog.15:04
DocScrutinizer05tnx psycho_oreos15:05
psycho_oreosWhen X happens instead of Y, its always best to run things in terminal, look in all the possible logs/avenues, etc.15:05
psycho_oreosYou don't go, oh its annoying me *reboot and hope it goes away*.15:06
*** kolp has quit IRC15:06
FIQ|n900yeah just wasn't sure what he meant with syslog15:06
DocScrutinizer05regularly programs spit some diagnostics to stderr or syslog when something inexpected happens15:06
FIQ|n900psycho_oreos: indeed, but this exact issue *do* get solved by rebooting15:06
FIQ|n900which I found out accidentally once15:06
FIQ|n900and this doesn't make any sense to me15:06
psycho_oreosThat's where its useful to debug rather than doing nothing until it got annoying.15:07
DocScrutinizer05thus: share syslog15:07
infobotextra, extra, read all about it, pkg is
psycho_oreosFIQ|n900, I don't know, that error almost sounds like some issue with python. Though I'm no programmer.15:07
Sicelo+d ;)15:07
psycho_oreos /var/log/syslog15:08
DocScrutinizer05only if sysklogd is installed15:08
DocScrutinizer05otherwise dmesg, though it's sub-par15:08
psycho_oreosSpeaking of dmesg, I found there was a nice perl script to translate those ktimer messages into meaningful syslog lookalike output.15:09
DocScrutinizer05and particularly " mobilehotspot 2>~/MyDocs/MH.log 1>&215:09
FIQ|n900DocScrutinizer05: also I tried to import os manually within a python interpreter15:10
FIQ|n900and it fails to find it as well15:10
FIQ|n900so something weird is going on @python15:10
*** kolp has joined #maemo15:10
DocScrutinizer05psycho_oreos: cooool15:11
psycho_oreosWhen it did work, where was the "import os" usually sourced from?15:11
*** trx has joined #maemo15:11
*** trx has joined #maemo15:11
psycho_oreosDocScrutinizer05, I was going to paste the link, hang on.. I'm going to find it again.15:11
psycho_oreosDocScrutinizer05, <-- only the perl script works on N900, python variant failed.15:12
DocScrutinizer05anyway, I'd probably rather need it on my PC. Thanks a lot15:12
psycho_oreosHehe, oh well, wherever you may find it handy :D15:13
DocScrutinizer05(on N900 I got syslog since ~ beginning of times ;-d )15:13
psycho_oreosno worries.15:13
FIQ|n900[14:11:09] <psycho_oreos> When it did work, where was the "import os" usually sourced from?15:13
*** dhbiker has quit IRC15:13
FIQ|n900I don't know this one atm, so I guess I'll have to reboot into a working MH to find that out? unless you have another solution15:13
* psycho_oreos has had issues with sysklogd failing to start after what was supposedly an issue trying to optify syslog file and wanting to compress it (to save space).15:13
FIQ|n900DocScrutinizer05: also honestly I fail to understand exactly how dmesg is helpful in this case15:14
psycho_oreosFIQ|n900, I'm no programmer, if it did worked at the time during reboots yeah its probably a way I suppose.15:14
FIQ|n900ohh hooray, that pastebinit script requires os too lol15:14
psycho_oreoserr I meant after a reboot.15:14
DocScrutinizer05FIQ|n900: since MH needs kernel support, it *may* be relevant15:14
*** dhbiker has joined #maemo15:15
psycho_oreosHmm I think I have pastebinit also installed.. lemme try something as well from my end.15:15
*** Cor-Ai has quit IRC15:15
FIQ|n900DocScrutinizer05: but when I earlier (before knowing it required KP) tried to use mobilehotspot in vanilla kernel, the application itself started fine15:15
FIQ|n900it just failed to create a wlan interface, i.e. not same issue as now15:15
DocScrutinizer05FIQ|n900: I'm not going to discuss the possible error patterns in any app on this level. It's futile15:16
*** LauRoman has quit IRC15:16
*** Cor-Ai has joined #maemo15:16
DocScrutinizer05a swift look at syslog is way more ffective, if only to rule out sth odd is going on there15:16
DocScrutinizer05to diagnose *any* arbitrary problem with a process, you generally need: stdout.log, stderr.log, syslog15:18
DocScrutinizer05and strace if the aforementioned don't help15:18
DocScrutinizer05there's hardly any bug in a program that can't get tracked down following this pattern15:19
DocScrutinizer05particularly when it's a bug that causes abort or failure to startup15:19
FIQ|n900as I didn't had syslog installed - dmesg output15:19
psycho_oreosSome programs contains hidden extra parameters that can be shown via strings if the program in question is a binary.15:19
FIQ|n900mobilehotspot is a python script though15:20
DocScrutinizer05yeah, dmesg is sub-par, I said it. [   80.442291] wl1251: down is the only slightly interesting thing in dmesg15:21
FIQ|n900DocScrutinizer05: in addition I installed sysklogd for future issues for easier debugging15:21
FIQ|n900 mobilehotspot's stderr15:21
DocScrutinizer05make sure to every now and then clean out your /var/log/* from obsolete old logs or too large current logs15:22
DocScrutinizer05I do that every 3 months or so15:22
FIQ|n900 and the actual mobilehotspot python script (it's small) in case it gives any clues15:22
psycho_oreos <-- my "dpkg -l| grep python| pastebinit -b" output (if that maybe of certain use), goes to show my python version works with pastebinit.15:22
DocScrutinizer05FIQ|n900: stderr already gives a good clue, no?15:23
FIQ|n900DocScrutinizer05: yes it does15:23
FIQ|n900but in case mobilehotspot is doing something funny15:23
FIQ|n900doesn't look like it though15:23
psycho_oreosAlso googling for the exact error phrase may also seem to help as well.15:25
FIQ|n900psycho_oreos: yes I did this before coming here15:26
FIQ|n900but it didn't turn up anything interesting/relevant15:26
DocScrutinizer05err guys, I'm no python crack at all, but I seem to recall a python shebang alsways looks like "#!/bin/env pythonBLAH"15:28
Wizzup_/usr/bin/env yeah15:29
Wizzup_just installed fcam, rebooted, and I have no /dev/video0 anymore15:29
Wizzup_interesting ;-)15:29
DocScrutinizer05not "#!/usr/bin/ python2.5"15:29
*** LauRoman has joined #maemo15:29
FIQ|n900isn't env used to get the correct path to the python binary?15:29
DocScrutinizer05yep, afaik sth like that15:30
DocScrutinizer05disclaimer, see above15:30
DocScrutinizer05nfc here15:30
psycho_oreosFIQ|n900, the first link from google was from stackoverflow which one suggested about using $PYTHONPATH. Now my "find / -name "os.pyc"" outputs these: /opt/pymaemo/usr/lib/python2.5/os.pyc | /usr/lib/python2.5/os.pyc | /home/opt/pymaemo/usr/lib/python2.5/os.pyc15:31
FIQ|n900psycho_oreos: what did you google on? I basically googled the error I pasted above and got no such link15:32
FIQ|n900but yes I can try looking for os.pyc15:33
psycho_oreosFIQ|n900, "ImportError: No module named os" and the link:
psycho_oreosWizzup_, somewhere something got messed up horribly, most likely a bad kernel module.15:34
DocScrutinizer05psycho_oreos: probably the /usr/lib/python2.5/os.pyc is a symlink to optified /opt/pymaemo/usr/lib/python2.5/os.pyc which is a bindmount to /home/opt/15:34
psycho_oreosDocScrutinizer05, yup :) the real python libs would never sit in rootfs anyway considering how limited the space of rootfs is.15:35
DocScrutinizer05""Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]""15:35
DocScrutinizer05seems to me like $PYTHONHOME is unset or incorrect15:36
DocScrutinizer05nfc why15:36
DocScrutinizer05or why it's needed anyway15:36
DocScrutinizer05maybe $PATH or $(pwd) is incorrect15:37
psycho_oreosI don't have $PYTHONHOME set as well (no outputs from my N900), though one guy from that link said to put this in their .bashrc: PYTHONPATH=/usr/local/lib/python2.6 . Obviously that's the wrong Python version but it seems like its one hackish attempts to rectify the issue.15:37
Wizzup_psycho_oreos: it would appear so, but I have no clue why15:37
*** Mike11 has joined #maemo15:37
Wizzup_just installed ``FCamera'' from extras-testing, and I am on power kernel 5015:37
DocScrutinizer05yeah, it's probably needed when sth is non-standard thus non-default on your pathnames and mounts and whatnot15:38
DocScrutinizer05MIGHT again be a fstab issue ;-P15:38
psycho_oreosWizzup_, usually a mismatched kernel with kernel modules loaded can cause issues. Other times it would output invalid module format -1 or something. syslog/dmesg output maybe useful here. I'm using kp52 with fcam modules (latest) and no issues from my end though.15:38
DocScrutinizer05check for `mount`15:38
DocScrutinizer05if the bindmounts for python are there15:39
psycho_oreosYeah that too.15:39
Wizzup_psycho_oreos: manual modprobe seems to fail with invalid module format15:40
DocScrutinizer05for the randomness of the issue, I might figure the new fstab/fsck hack introduced to CSSU-T may fail to bindmount the python mounts when and only when any of the fs needs fsck15:40
Wizzup_that is odd15:40
FIQ|n900hmm interesting, I have and os.pyo but not os.pyc in that directory.. and I tried to set PYTHONPATH manually (it was not set before - just tried) and it successfully imported that module, however now it errors on another module... will try to see where it is in case I need something else in that path as well15:41
psycho_oreos <-- my mount output, if you'll excuse my excessive use of ext3 here *ahem* :)15:41
DocScrutinizer05Wizzup_: zhere's a --ignore-vermagic OWTTE option to modprobe15:41
psycho_oreosWizzup_, That's the reason why :)15:41
FIQ|n900s/- just tried/- as seen on echo $PYTHONPATH/15:41
infobotFIQ|n900 meant: hmm interesting, I have and os.pyo but not os.pyc in that directory.. and I tried to set PYTHONPATH manually (it was not set before - as seen on echo $PYTHONPATH) and it successfully imported that module, however now it errors on another module... w...15:41
Wizzup_thx,will be back soon15:42
psycho_oreosFIQ|n900, I'd also start checking on mount as DocScrutinizer05 pointed out.15:43
FIQ|n900yes which I just did15:43
FIQ|n900in addition, the mounts @python seems to have no issues, see
DocScrutinizer05you start to qualify for a strace session ;-)15:45
* psycho_oreos ponders if the issue might also be to do with older versions of python libraries (hence lacking the necessary facility within their respective postinst) to work properly.15:45
FIQ|n900(non-localized )15:46
DocScrutinizer05FIQ|n900: not needed ;-D15:46
FIQ|n900DocScrutinizer05: also I tried to reinstall all python packages in case something was messed up15:46
FIQ|n900and interestingly it did not go all well15:46
psycho_oreosAhh the only difference is what was written on top, not needed :) I know what the content says :D.15:47
FIQ|n900[14:46:39] <FIQ|n900> DocScrutinizer05: also I tried to reinstall all python packages in case something was messed up - like that optfs restoration yesterday15:47
psycho_oreosFIQ|n900, that's your answer.15:47
psycho_oreos<FIQ|n900> and interestingly it did not go all well <--- That could be the source of the issues.15:47
FIQ|n900will paste apt results sec15:47
psycho_oreosI somewhat would also like to think the issues with these are happening is also because you nuked /opt. It sort of makes programs walk on "broken tiles".15:50
* DocScrutinizer05 suddenly feels sick, considering that some python programs might now (after fstab hack) run *before* possibly deferred bindmount of *python 'volumes'15:50
* psycho_oreos thinks in either case FIQ|n900 is on the way to creating a zombified version of maemo. :)15:51
psycho_oreosLots of hits and misses. I'm guessing python won't be the only solitary issue though.15:52
*** dhbiker has quit IRC15:52
FIQ|n900psycho_oreos: though this issue did exist before optfs restoration as well - but then the reinstall might have worked a little better15:53
psycho_oreosFIQ|n900, outstanding issue? o.O15:55
FIQ|n900and at least I don't think I can make it *worse*, if anything, better15:55
FIQ|n900psycho_oreos: the optfs restoration was due to a corrupt file system15:55
FIQ|n900itself caused by me not realizing that hard shutdowns might be a bad idea... lol15:56
psycho_oreosFIQ|n900, Yeah I know but you had the issue prior to nuking /opt. So it was virtually an issue that you didn't bother to resolve beforehand.15:56
FIQ|n900 apt log15:57
*** piggz has joined #maemo15:57
* psycho_oreos recalls having mount warnings with his microSD about unclean mounts. It was only after.. what, 30+ fsck.ext3 that finally yielded a clean result with the majority of the nokia maps file being corrupted.15:58
FIQ|n900if microSD is ext3, maemo gives an error on mount15:58
FIQ|n900unless you're running a fairly recent version of cssu15:59
*** louisdk has joined #maemo15:59
DocScrutinizer05FIQ|n900: delete *all*  *.pyc15:59
psycho_oreosAt that time I think I was (somewhat), though I had extra mount params like errors=mount-ro.15:59
*** Arkenoi has quit IRC16:00
FIQ|n900uh huh now that's strange16:00
psycho_oreosHmm the warnings from apt log. Doesn't make much sense when /opt was nuked anyway.16:00
FIQ|n900looking through that log16:00
FIQ|n900reinstall gave lot less errors this time16:00
*** louisdk has quit IRC16:00
*** louisdk has joined #maemo16:00
DocScrutinizer05>>Some bytecompiled files may be left behind.<< is the key16:01
DocScrutinizer05I bet16:01
* psycho_oreos doesn't think there would really be any bytecompiled files be left on a nuked /opt. Though if you restored from an older opt.tar that could be a potential issue.16:01
FIQ|n900DocScrutinizer05: last install it blamed on various modules not being found during the installation16:01
psycho_oreosYeah that's usually the result of you nuking /opt :)16:02
DocScrutinizer05if you got an obsolete *.pyc in some place prior in $(PYTHON)PATH than the new *.py, you inevitably run into trouble16:02
FIQ|n900had to reinstall *again* to give a meaningful paste16:02
FIQ|n900in case anyone wonders why I'm implying I did it twice16:02
FIQ|n900including the above mentioned os, and some others as well16:02
psycho_oreosProbably a good idea at the time would be to forcibly remove dead packages and reinstall them. That way apt won't complain (well hopefully).16:02
FIQ|n900er, last line was @ [15:01:56] <FIQ|n900> DocScrutinizer05: last install it blamed on various modules not being found during the installation16:03
FIQ|n900psycho_oreos: hmm maybe16:03
FIQ|n900that's interesting16:04
psycho_oreosWell in either case I'd say go with DocScrutinizer05's suggestion. Clean out old python stuff (after removing python) and then reinstall python again.16:04
FIQ|n900the first reinstall didn't solve anything - the second reinstall seems to have solved everything16:04
psycho_oreosThat should get rid of the leftover junk and start fresh... well hopefully.16:04
FIQ|n900because now stuff seem to work16:04
psycho_oreosPartially, remember that you had to use $PYTHONHOME because it could not find os.pyc.16:05
FIQ|n900yes true16:05
DocScrutinizer05which is odd16:05
psycho_oreosAll that leftover ancient files could cause the confusion.16:05
DocScrutinizer05*.pyc, yes16:06
FIQ|n900but DocScrutinizer0516:06
FIQ|n900don't know if you saw me mention it earlier16:06
FIQ|n900but I didn't have *any* .pyc files in that directory before16:06
psycho_oreosNo guarantees/recommendations here because you do realise you are trying to do something that probably hardly any users have encountered :)16:06
DocScrutinizer05that's the whole point16:06
FIQ|n900(though I did have .py and .pyo files)16:07
psycho_oreosIts the leftover junk/cruft.16:07
DocScrutinizer05you possibly got some in some *other* dir16:07
psycho_oreosIt also could be the issue with restoring old opt.tar. I'm sure it works but to a lesser extent it does.16:07
FIQ|n900(though now I have some as I reinstalled)16:07
FIQ|n900so basically16:07
DocScrutinizer05and I have nfc what's .pyo, probably something similar to .pyc16:08
FIQ|n900I should remove all .pyc files, including the newly created files16:08
FIQ|n900and reinstall all python packages again?16:08
psycho_oreosiinm, .pyo is compiled (binary blob) of .pyc.16:08
psycho_oreosProbably uninstall python first (if you could and to make it not uninstall other packages that depends on python like for instance mobilehotspot).16:09
DocScrutinizer05afaik .pyc is compiled with symbolic names, while .pyo is compiled w/o symbols16:09
DocScrutinizer05anyway both are dynamically created by python interpreter afaik16:09
psycho_oreosAhh I tend to think .pyc is more human readable than .pyo. .pyo is all literally machine code (hence compiled).16:09
psycho_oreosRemove python packages via apt (hopefully.. or use dpkg if you can somehow make it not uninstall MH), then clean out remaining python junk left in /opt/python. Then reinstall python through apt.16:10
psycho_oreosThat might be the best idea imho.16:10
*** Arkenoi has joined #maemo16:10
psycho_oreosDon't remove stuff in /opt/python then remove via dpkg/apt.. you'll make dpkg/apt even more messed up about python stuff, let them know that you don't want python junk so when it comes to reinstalling it will know from its own database that you have previously removed it.16:12
DocScrutinizer05iirc there's a --purge parameter to some of that apt/dpkg stuff16:13
FIQ|n900remove or purge?16:13
FIQ|n900@ dpkg16:13
DocScrutinizer05prolly useful here16:13
psycho_oreos*nods* purge is probably more cleaner.16:13
psycho_oreosI'd also make sure neither of them complain about removing things like MH which depends on python that is to be removed.16:14
psycho_oreosWhichever you choose, purge would be cleaner iinm.16:14
Palihello, any qt guru here? I need output backtrace when some signal is emitted. Any idea if qt has some object/slot for that?16:14
psycho_oreosOr even remove, then purge, purge just gets rid of leftover conf files for instance.16:14
psycho_oreosPali, not sure but you can try #qt. According to alis, there's 505 users/bots in that channel.16:17
PaliI know only about GNU/linux backtrace() function in execinfo.h (man 3 backtrace)16:18
* psycho_oreos hopes they can fix the issue rather than pointing you back into channels like these :) where its all maemo/meego centric and there's no active Qt gurus active (or at least it seems).16:18
* psycho_oreos has very vague information about all of what you said :/ lol. Not a developer so most of this is really flying above my head.16:19
*** Pali has quit IRC16:19
*** Pali has joined #maemo16:19
*** brzys has quit IRC16:20
*** brzys has joined #maemo16:20
*** SAiF has joined #maemo16:20
*** brzys has quit IRC16:21
*** brzys has joined #maemo16:21
FIQ|n900ok, everything was removed fine apart from some directories (the bindmounted ones)16:21
FIQ|n900w/o manual intervention required16:21
FIQ|n900now installing again16:21
psycho_oreosFIQ|n900, don't forget to purge and manually remove any leftover cruft/junk.16:22
*** brzys has quit IRC16:22
*** brzys has joined #maemo16:22
FIQ|n900psycho_oreos: everything was removed as I said, checked all python directories16:22
DocScrutinizer05psycho_oreos: o.O indeed. Pali has strange habits16:23
FIQ|n900(the directories themselves was left intact due to bindmounts and I left them like that as I don't want reinstalling them to fill my rootfs16:24
*** zap__ has quit IRC16:24
psycho_oreosFIQ|n900, ok that's good. Just don't want to hear apt/dpkg complaining again all of the sudden. Its only wild guesses from here on in, into fixing python.16:25
psycho_oreosDocScrutinizer05, heh do tell me :D16:25
FIQ|n900python installation gave no errors this time16:26
psycho_oreosFIQ|n900, I have for some wild guess those bind mounts may get recreated once you installed base python stuff.16:26
FIQ|n900psycho_oreos: well dpkg -P attempted to remove the directories - failing due to bindmounts16:26
DocScrutinizer05FIQ|n900: for bindmounts see pymaemo-optify - PyMaemo optification package16:26
FIQ|n900so my assumption is that apt would not redo the bindmounts16:27
psycho_oreosFIQ|n900, ahh16:27
psycho_oreosSeems like DocScrutinizer05 has pointed out a vital clue here as well.16:27
DocScrutinizer05was some real fun when that pkg got propagated16:28
DocScrutinizer05must've been back in time when PR1.2 came out16:28
FIQ|n900I wonder if there's a quick straightforward way to ask apt about missing files in every single package16:29
FIQ|n900so I would be able to clean up after that optfs thing16:29
DocScrutinizer05err, there is some tool doing that16:29
DocScrutinizer05nfc if it's apt or some supplementary tool though, or even dpkg-*16:30
FIQ|n900simply looking for runaway symlinks isn't enough as some packages install themselves to /opt directly16:30
DocScrutinizer05a really annoying habit16:30
DocScrutinizer05I had a real dispute with iirc shapeshifter about alarmed NOT installing a symlink16:31
*** e-yes has joined #maemo16:31
DocScrutinizer05I consider that a flaw for a cmdline tool to not be available anywhere in usual $PATH16:31
DocScrutinizer05IroN900:/etc# ll `which alarmed`16:32
DocScrutinizer05lrwxrwxrwx 1 root root 23 2011-06-20 15:53 /usr/bin/alarmed -> /opt/alarmed/alarmed.py16:32
DocScrutinizer05had to create that myself16:32
FIQ|n900also sorry for being clueless occasionally with some stuff regarding things like this16:32
DocScrutinizer05no reason for feeling sorry16:33
FIQ|n900DocScrutinizer05: heh16:33
DocScrutinizer05we all started learning about that stuff16:33
DocScrutinizer05some time16:33
FIQ|n900N900 was my first serious step into slightly more complex parts of linux, i.e. before I got a n900 I barely knew what "cd" did lol16:34
FIQ|n900oh well, afk16:34
DocScrutinizer05FIQ|n900: you're clearly willing to learn. so it's a please to help you16:35
DocScrutinizer05a pleasure*16:35
psycho_oreosI'm sure whilst you are experimenting with what we have suggested, we too are in the process of learning as well.16:35
DocScrutinizer05which is why we're all in here doing what we do, isn't it?16:36
psycho_oreosIts not exactly a "one way street" where we knew what the answer was and could give you a direct answer.16:36
psycho_oreosyup :)16:36
infobotmethinks question is If you have a question and want people to give useful answers, make sure you have read this first:
DocScrutinizer05has some nice chapters about that16:37
*** bef0rd_ has quit IRC16:37
DocScrutinizer05it's a recommended read even for experienced hackers16:37
psycho_oreosdpkg -S I found tells me what files belongs to which package. Though I haven't found a single command that could do it easily. If you could get "find" to output broken symlinks then you maybe able to get dpkg -S to show which broken symlink belonged to which deb.16:37
DocScrutinizer05I try to read it at least twice a year16:37
psycho_oreoshehe I've read that page numerous times, very interesting stuff even though not everyone follows it closely.16:38
*** ZogG_laptop has quit IRC16:38
DocScrutinizer05it's hard to follow it closely, but it gives you a perspective each time you read it16:39
psycho_oreosI get a little annoyed when people just say "X is broken" "please help", and then you have to start digging clues out of them to get a basic/general understanding of their setup.16:39
Lava_Croftpeople who says X is broken are correct16:40
psycho_oreosAlso I guess its also a good reminder to ask questions the "right" way as well.16:40
Lava_Croftand it cant be helped16:40
psycho_oreosIts not the program can't be helped, its more like an issue with pebkac ;)16:40
*** FIQ has joined #maemo16:40
psycho_oreosYeah I've sometimes thought of that as well, but it can get a little irritating when you're also dealing with a situation on hand from your end as well and there's nobody else responding.16:42
psycho_oreosAt times certain commands "collide" when you're helping others on X distro when you're on Y distro.16:43
psycho_oreosHaving to think what the command "equivalent" was to match their case.16:44
*** FIQ|n900 has quit IRC16:44
* psycho_oreos thinks right now there might be a hackish way to output dpkg -L| echo $i| find $i when say for instance under archlinux, pacman -Ql by default lists the name of the package along with the files owned by that package.16:45
*** ZogG_laptop has joined #maemo16:46
*** ZogG_laptop has quit IRC16:46
*** ZogG_laptop has joined #maemo16:46
DocScrutinizer05yep, you can craft some cmdline wizardry16:47
DocScrutinizer05but you also can talk the person you try to help thru using all the tools actually available16:47
psycho_oreosThat and the sort of "hackers" way to fix things ;) hackish attempts16:48
DocScrutinizer05example of a useful cmdline wizardry:  man md|less +"/If an array is created"16:49
psycho_oreosThe power of pipe combined with BASH scripting ;)16:50
*** Pali has quit IRC16:51
DocScrutinizer05you wouldn't want to talk the helpee thru less(1) basics16:51
DocScrutinizer05or tell them "look at line 255 of `man md´"16:52
psycho_oreosIn that case I guess grep maybe useful here ;)16:53
DocScrutinizer05nah, not really unless you want to "quote" a very strictly defined limited section out of some text16:53
DocScrutinizer05man md|less +"/If an array is created" -j 916:55
psycho_oreosYeah that would be a little difficult.16:55
*** npm has joined #maemo16:55
*** bef0rd has joined #maemo16:56
*** Macer has left #maemo16:56
psycho_oreosI just searched, there's dpkg -C but doubt it's usefulness.16:56
*** e-yes has quit IRC16:59
DocScrutinizer05man bash|less +"/^[^a-z]*SIGNALS"17:00
*** FIQ|n900 has joined #maemo17:09
Wizzup_psycho_oreos: so I guess you have kernel-power from extras-devel?17:17
psycho_oreosWizzup_, yup17:18
Wizzup_as well as fcam17:18
Wizzup_okay, I'll try that, does blessn900 work with that fcam driver?17:18
psycho_oreosafaik yes.17:19
Wizzup_(I really just want blessn900, but I guess I can upgrade the power kernel)17:19
psycho_oreosYou might be able to just get away with newer fcam-drivers insntead of new power kernel. Though I'm not sure.17:20
Wizzup_tbh I don't understand why the current ``stable'' fcam driver don't work with my power kernel17:20
*** sq-one has joined #maemo17:21
psycho_oreosWhich version do you have just curiously.17:21
psycho_oreosErr my bad not kp version, fcam-drivers version.17:22
Wizzup_0.7.1 I think, let me check17:23
*** mancha has joined #maemo17:23
Wizzup_ shows why there's a -217:24
Wizzup_just not sure for what powerkernel that is17:24
manchaok folks. my n800 suddenly stoped working. it turns on and seems to boot but the screen just cycles though some weird vertical stripes then a flash on the whole screen then black17:24
psycho_oreosdpkg -l fcam-drivers| awk '{ print $3 }'17:24
manchathe only thing i did was charge it several times last night. ideas?17:25
psycho_oreosWhat did you do before this issue started happening?17:25
Wizzup_psycho_oreos: 1.0.7-117:25
manchadownloaded some maps last nite in maemo mapper. that's it.17:26
psycho_oreosWizzup_, that should work with kp50 afaik. It works with kp52 but its been awhile since I looked into what could be the issue.17:26
Wizzup_I'll upgrade kp17:26
* psycho_oreos doesn't know if that'll necessarily fix the problems though.17:27
Wizzup_ah, I should move on with my uinput-mapper package soon...17:27
Wizzup_psycho_oreos: we'll see17:27
psycho_oreosSome files within kp (at least 52) has kernel version specific fcam provided kernel drivers. I'm not sure have they been merged.17:28
psycho_oreosmancha, I misread :/ I thought it was N900 you are talking about not N800. I was going to suggest it could be issue with bootlooping and low battery. I don't have N800 so I don't know I'm afraid.17:29
manchacould i have fried my battery?17:29
psycho_oreosUnlikely unless you charged your battery with some other device.17:30
DocScrutinizer05mancha: possible, but i'm afraid your problem is more severe than that17:30
manchaDocScrutinizer05: how can the thing just go bad all of a sudden?17:30
DocScrutinizer05like all things do17:30
manchais there some kind of safe boot?17:31
*** flo_lap has quit IRC17:31
DocScrutinizer05err, not that I know of17:31
DocScrutinizer05I don't own N800 though17:31
Wizzup_psycho_oreos: hm, extras-devel is suggesting 51r117:31
DocScrutinizer05what battery does N800 use?17:32
psycho_oreosWizzup_, *grr at whoever is playing with the repository* you can probably install kp52 from Pali's own repository or manually.17:32
DocScrutinizer05what when you plug it into charger?17:33
Wizzup_psycho_oreos: my ``Distribution'' is set to fremantle-1.3, I hope that makes sense17:33
Wizzup_that's the only think I can imagine that may be different17:33
psycho_oreosWizzup_, I don't think that would be relevant. Its the issue with the repository still showing 51r1. *looks at his fapman repository configuration*.17:35
psycho_oreosI wouldn't recommend using fapman either :)17:35
Wizzup_no, people told me this a few years ago17:35
manchaDocScrutinizer05: it's the batter.17:36
* psycho_oreos issues an update and checks via apt-cache on kp52.17:36
DocScrutinizer05mancha: glad to hear that17:36
psycho_oreosmancha, so a replacement battery worked?17:37
*** FIQ has quit IRC17:37
*** FIQ|n900 has quit IRC17:37
DocScrutinizer05Wizzup_: that may make a friggin lot of difference, since during migration#1 the fremantle vs fremantle-1.3 duality got messed up17:38
Wizzup_psycho_oreos: getting fcam-drivers from devel worked17:38
*** Vlad_on_the_road has joined #maemo17:38
manchano, but aside from the screen, the bootup sound is faint.17:38
psycho_oreosWizzup_, 1.0.7-2??17:38
Wizzup_DocScrutinizer05: yeah, I recall setting it to -1.3 was the right thing to do, I think I did it properly17:38
Wizzup_psycho_oreos: yes17:38
manchait seems like it's not getting the right charge...i bet i fried the battery by leaving it plugged in all night17:38
Wizzup_psycho_oreos: which is also kind of what his change message says17:39
DocScrutinizer05Wizzup_: the sad truth is: right now there is no "right" setting17:39
Wizzup_DocScrutinizer05: nice ;-)17:39
*** _rd has joined #maemo17:39
psycho_oreosWizzup_, *nods* I thought that was just some custom one I built (when I was tinkering with abc). I never knew that was in extras-devel.17:39
*** mvp has quit IRC17:40
DocScrutinizer05fremantle-1.3 used to be a symlink to fremantle17:40
DocScrutinizer05during migration#1 that got messed up, just doing a mirror or whatever of the repo, and that created TWO repos: fremantle and fremantle-1.317:40
manchado0es a dead battery sound plausible?17:41
psycho_oreosmancha, I guess it goes back to what DocScrutinizer05 said earlier, sounds like its more severe. I guess there's probably multiple issues, though one step at a time helps I guess.17:41
DocScrutinizer05up to anybody's guess which action adresses which repo, also in autobuilder and repo-management17:41
*** at1as has quit IRC17:41
*** bef0rd has quit IRC17:42
psycho_oreosmancha, its hard to say :) two of us has admitted we don't own N800, so its hard to know what the problem is if we don't know much about it.17:42
manchapsycho_oreos: why do you both assume something more seirous?17:42
psycho_oreosmancha, to me personally the colour stripes showing on the screen before going black. Prior to that you installed a maps software, it might also be screen playing up but hard to know.17:43
DocScrutinizer05mancha: because bad battery usually doesn't cause atrifacts on screen17:43
*** valeriusL has quit IRC17:44
psycho_oreosWhat happens if you tried plugging the charger in whilst having the "dead/bad battery" in place? Does N800 still boot?17:44
*** valerius has quit IRC17:45
DocScrutinizer05afaik N8x0 should kinda work with a battery of any quality and charge, as long as plugged into charger17:45
psycho_oreosYeah I thought of the same thing as well. At least on N900 you can see the nokia logo before it dies and tries to go back into emergency charge mode.17:46
DocScrutinizer05it *might* shut down with battery-low or battery-defect signal17:46
DocScrutinizer05but I never heard of artifacts on screen17:46
psycho_oreosOr the battery is simply too faulty that it fails to even allow charging when power is plugged in.17:47
*** FIQ has joined #maemo17:47
DocScrutinizer05as usual, a comlete reflash might help to distinguish hw from any sw problems17:47
psycho_oreosEither way, its weird but its beyond my knowledge... I'm virtually stabbing in the dark here.17:47
*** louisdk has quit IRC17:47
DocScrutinizer05or you just get a replacement battery17:48
*** louisdk has joined #maemo17:48
DocScrutinizer05and check if things change17:48
manchawell you guys are a very pessimistic bunch. you're real downers.17:48
psycho_oreosOne step at a time :)17:48
psycho_oreosmancha, do you have a better suggestion as to what it might be? :)17:48
DocScrutinizer05no, we aren't17:48
mancha"i don't own an n800 so i have no fucking clue what's up but i'll just pull out my ass it's super serious"  :)17:48
infobotjoerg is, like, a natural born EE, ex HW-developer and engineer of Openmoko, now mainly involved in maintenance of maemo and N900. Usually known as DocScrutinizer17:49
psycho_oreosWe've given you a likely scenario on N900's case.17:49
*** discopig has joined #maemo17:49
DocScrutinizer05mancha: I'm just stating that I don't have N800 to make clear my statements are based on N810 and N900 and general knowledge of embedded hardware17:50
psycho_oreosThe least you could do is try to solve the problem one at a time, first plug it into wall charger with battery in place. If it still doesn't boot, get a replacement battery, if it doesn't boot its probably the screen at fault (or others).17:50
manchaok, if the battery got fried, it's old. and the cells leaked, can this not be providing less volage/amperage than is needed to power the lcd display?17:50
manchaquestion for the EE :)17:50
DocScrutinizer05still no chance to create artifacts, on all embedded devices I know17:51
manchawhy not?17:51
psycho_oreosProbably because of the way its designed I gather.17:51
DocScrutinizer05because hw doesn't work that way usually, unless my colleagues messed up N800 fubar17:51
DocScrutinizer05and I've seen similar artifacts caused by other hw defects17:52
DocScrutinizer05but never by battery17:52
DocScrutinizer05actually your error description is very similar to what you get on N900 when flex connector is broken17:53
DocScrutinizer05now the N800 doesn't have a flex connector for all I know17:53
DocScrutinizer05since it doesn't have a slide-out kbd17:54
DocScrutinizer05anyway N8x0 battery charging is notorious fubar, and I suggest you get a spare battery to check17:54
psycho_oreosThe very least you could do is try the suggestion I mention beforehand. I'm not an EE, I don't own a N800 but I'm giving you advice from what a N900 user would try otherwise.17:55
*** sq-one has quit IRC17:55
manchait boots.17:55
manchabut i can't see anything cause the screen is fucked.17:56
psycho_oreosIf it boots with power in place, then its probably a faulty battery.17:56
manchacmon dude.17:56
psycho_oreosYeah sounds like possible multiple issues.17:56
DocScrutinizer05no, when LCD still fux0red then it's a hw defect17:56
manchano way17:56
psycho_oreosmancha, what do you think it is? that it is our fault?17:56
manchalook, multiple issues don't just happen out of the blue at the same time. sorry that dog don't hunt.17:56
manchaif the multiple issues are related somehow then i'll bite, otherwise it's just nonsense.17:57
psycho_oreosI hate to say this but N800 is an aging device.17:57
DocScrutinizer05he meant multiple alternative causes17:57
manchaoh i see.17:57
psycho_oreosN900 is facing the same path as well.17:57
manchathat's irrelevant whether it's an aging device.17:57
psycho_oreosElectronics generally don't *last* forever.17:57
manchai've not used it much and more important are usage cycles.17:58
DocScrutinizer05get a damn spare battery!17:58
psycho_oreosI know old PSU outputs less power gradually over time before the machine (should the motherboard be intelligent enough) to prevent the machine from booting if PSU is simply not outputting enough power. That's one use case with aging electronics from what I know.17:59
manchaDocScrutinizer05: trying to find a store now.17:59
manchathe battery is prolly 10 years old17:59
DocScrutinizer05reasonably considered dead17:59
psycho_oreosBatteries also doesn't last forever as well.. the case is very evident when it comes to laptops.17:59
*** valeriusL has joined #maemo18:00
psycho_oreosYou don't see a 10 year old laptop with 10 year old battery working like brand spanking new from the shops.18:00
DocScrutinizer05but honestly when your device boots up and acts in reasonable ways to input, just doesn't display on LCD anymore, then you do _not_ have battery issue18:01
manchait sorta boots, sometimes faint boot sound othertimes nothing18:01
DocScrutinizer05when your device shuts down any time, by whatever nasty procedure, then you *might* have a battery problem18:01
psycho_oreosI'm sure almost every PC technician goes by the general rule of thumb, and that is to try one thing at a time.. if this doesn't work try that, if that doesn't work try another.18:01
manchai think it's on last legs18:01
psycho_oreosThere's no secret about debugging hardware issues.18:02
manchaDocScrutinizer05: does the n800 have the ability to run batteryless (plugged in)18:02
DocScrutinizer05generally not18:02
manchaso can't test that way...18:02
manchabest buy has no bp-5l's18:02
manchathe fuck18:02
DocScrutinizer05otherwise we had suggested to you already18:03
*** Avasz has joined #maemo18:03
*** Avasz has joined #maemo18:03
psycho_oreosTo be frank I would leave DocScrutinizer05 to answer that one, I personally don't know of anyone that owns N800 out where I live. I've only seen very few N900 owners.18:05
DocScrutinizer05N810 (BP-4) works with BL-5J as well, when you press it to the contacts18:05
manchaok folks, you've been very helpful and i've been crabby (pissed at my "broken" hw)18:06
manchai'll get a replacement battery and start there.18:06
DocScrutinizer05I feel with you18:06
manchaif that doesn't work, then it's game over right? nokia won't service this dinosaur, yes?18:06
DocScrutinizer05see if you maybe borrow a battery from another device that has identical battery contacts18:07
psycho_oreosWe all will probably go into denial at first with aging stuff. Its inevitable as we try to clamber on the remains.18:07
manchai tried from my phone and the contacts don't line up :/18:07
*** _rd has quit IRC18:07
DocScrutinizer05they won't service it anymore I guess. But it can't hurt to ask - if worst case hits you18:07
*** _rd has joined #maemo18:07
psycho_oreosYou might be able to source N800 screen and go from there. The only question from here on in lies in how much money will you want to fork in on the device alone to resurrect it.18:08
*** Vlad_on_the_road has quit IRC18:08
DocScrutinizer05mancha: I'd almost bet BP-4L and BP-5L have identical battery contacts, so BL-5J should work for you as well. It can be found in quite a number of devices from Nokia18:09
*** freemangordon_ has joined #maemo18:10
*** freemangordon has quit IRC18:10
DocScrutinizer05mancha: just *carefully* compare writing on your battery and on spare other model battery for same "signals" on same pins (GND or (-), (+), and some "BSI" or whatever on middle contact probably)18:11
*** cehteh_ is now known as cehteh18:11
DocScrutinizer05oops nope!!!18:11
* psycho_oreos imagines a few years ahead in time one will probably see N900 dying/withering away.18:12
DocScrutinizer05on middle is GND/-18:12
DocScrutinizer05the "BSI" is opposite of (+)18:12
DocScrutinizer05(+) is on corner of battery, BSI to the center18:13
DocScrutinizer05you also can tell GND/- contact in device - it's a tiny bit longer than other two18:13
DocScrutinizer05mmmpf, on N810 both + and - are longer, and BSI is the only shorter one18:14
DocScrutinizer05probably same on N90018:15
*** sq-one has joined #maemo18:15
DocScrutinizer05anyway, good luck18:15
*** Kabouik has joined #maemo18:16
manchait's not the battery18:17
*** Kabouik has quit IRC18:17
psycho_oreosSo now the case continues on possibly the screen being the issue.. either the screen or otherwise.18:18
psycho_oreosErr the screen, its connectors or otherwise.18:18
manchai have a bootloader on it. wonder if i should reflash with factory18:18
psycho_oreosThe idea of reflashing was suggested earlier on by DocScrutinizer05.18:19
DocScrutinizer05when it's only the screen then you probably can reflash18:19
DocScrutinizer05if it's only software then you can reflash18:19
DocScrutinizer05if it's some problem with main hw components like CPU/SoC then you will face severe problems no matter what you try to do18:20
DocScrutinizer05mancha: how did you make sure it's not the battery?18:20
*** Mike11 has quit IRC18:23
manchai connected a gps battery which is also 3.7 volts and if i held it in place the contacts touched.18:23
manchathe thing boots the same way...with artifacts.18:23
manchai will try reflashing now.18:24
*** mvp has joined #maemo18:24
ApicGood Luck.18:24
DocScrutinizer05yes, that rules out battery18:24
*** _rd has quit IRC18:24
infoboti heard maemo-flashing is
DocScrutinizer05for you:
DocScrutinizer05you can use flasher-3.5 nevertheless18:27
manchareflash was successful and problem is unfixed.18:31
*** ian---- has quit IRC18:31
manchathe thing's bricked18:33
psycho_oreosBricked? o.O18:35
manchawell i didn't brick it in the flash18:35
manchai mean the flash was successful and the problem remains.18:35
DocScrutinizer05well, LCD or controller od SoC's video engine defect18:35
manchaand that can just go bad?18:36
manchaout of the fuckin' blue?18:36
DocScrutinizer05or sth as simple as connectors18:36
psycho_oreosI believe someone mentioned with electronics, its either 1 or 0, Alive or dead, there's no in-between.18:37
DocScrutinizer05yes, chips can go defect in an instant18:37
psycho_oreosInevitably electronics are what humans made. Inperfect as they are just as we are inperfect ourselves.18:38
*** frafl has joined #maemo18:39
infobotpsycho_oreos meant: Inevitably electronics are what humans made. Inperfect as they are just as we are imperfect ourselves.18:40
psycho_oreosbah, case sensitive.18:40
DocScrutinizer05and you forgot /g anyway18:41
infobotDocScrutinizer05 meant: aBcabcabcabc18:41
infobotDocScrutinizer05 meant: aBcaBcaBcaBc18:41
manchawell. thanks all. this sucks. i'll go sulk now.18:41
manchabe well.18:42
infobotpsycho_oreos meant: ABcAbcAbc18:42
*** mancha has left #maemo18:43
psycho_oreosmancha, there's still hope. you could try with another LCD to see if its LCD that's faulty or if its really the SoC video engine dead.18:43
*** kolp has quit IRC18:47
*** kolp has joined #maemo18:47
*** sq-one has quit IRC18:51
*** nox- has joined #maemo18:55
*** qwerty has joined #maemo18:58
*** qwerty is now known as Guest4504718:58
Guest45047hi how to change font in nokia n900??18:58
Guest45047anyone here?18:59
*** Guest45047 has quit IRC19:01
*** qwerty123 has joined #maemo19:02
qwerty123changing font on nokia n900??19:04
qwerty123?? anyone here/19:07
ApicYes, but no Idea how to change the Font.19:07
ApicIt's normal X11, so it should not be _too_ difficult.19:07
ApicI think the Terminal App has Functionality to change the Font it uses.19:08
*** rcg has joined #maemo19:08
qwerty123theme customizer changes the font. but i need to change the font of the textbox in vkb19:08
qwerty123rest, as far as i can see, font has been changed xcpt for the textbox of vkb19:09
psycho_oreosHave you tried searching/posting thread on tmo as well?19:12
*** kolp has quit IRC19:12
*** piscodig has joined #maemo19:12
*** discopig has quit IRC19:15
*** zap__ has joined #maemo19:15
*** SAiF_ has joined #maemo19:17
*** SAiF_ is now known as Guest8950319:17
*** qwerty123 has quit IRC19:18
*** SAiF has quit IRC19:19
*** triggerhappy has quit IRC19:26
*** cerberus_ has joined #maemo19:28
*** Avasz has quit IRC19:28
*** cerberus_ is now known as Avasz19:28
*** Avasz has joined #maemo19:28
*** FredrIQ has joined #maemo19:30
*** kolp has joined #maemo19:31
*** FIQ has quit IRC19:31
*** FredrIQ is now known as FIQ19:31
*** bef0rd has joined #maemo19:33
*** valeriusL has quit IRC19:34
*** bef0rd has quit IRC19:37
*** japa-fi has quit IRC19:39
*** valeriusL has joined #maemo19:44
*** bef0rd has joined #maemo19:45
*** bef0rd has joined #maemo19:46
*** japa-fi has joined #maemo19:48
*** Guest89503 has quit IRC19:51
*** Mike11 has joined #maemo19:52
*** Pali has joined #maemo19:54
*** SmilyOrg has joined #maemo19:55
*** Smily has quit IRC19:58
*** eijk has joined #maemo20:11
*** KaffeeJunky123 has joined #maemo20:17
*** AndrewX192 has quit IRC20:23
*** platoscave has quit IRC20:25
*** platoscave has joined #maemo20:26
*** platoscave has joined #maemo20:27
*** platoscave has joined #maemo20:28
*** AndrewX192 has joined #maemo20:28
*** platoscave has joined #maemo20:29
*** platoscave has joined #maemo20:30
*** platoscave has joined #maemo20:31
*** platoscave has joined #maemo20:31
*** platoscave has joined #maemo20:32
*** platoscave has joined #maemo20:33
*** AndrewX192 has quit IRC20:45
*** AndrewX192 has joined #maemo20:45
*** flo_lap has joined #maemo20:50
*** AndrewX192 has quit IRC20:50
*** AndrewX192 has joined #maemo20:50
*** flo_lap has quit IRC20:51
*** florian has joined #maemo20:51
*** florian has joined #maemo20:51
*** Avasz has quit IRC21:00
*** rcg has quit IRC21:01
*** e-yes has joined #maemo21:08
*** kolp has quit IRC21:13
*** ecc2g is now known as ecc3g21:22
*** FIQ has quit IRC21:22
*** FIQ has joined #maemo21:29
*** rcg has joined #maemo21:31
DocScrutinizer05DAMN!! was it THAT qwerty123?21:32
DocScrutinizer05prolly not21:32
*** fmunozs12 has joined #maemo21:32
DocScrutinizer05I also guess he been called qwerty1221:33
*** zammy has quit IRC21:33
psycho_oreosI somehow doubt it'll be him. (qwerty12)21:34
*** KaffeeJunky123 has left #maemo21:34
*** Woody14619 has quit IRC21:37
*** frafl has quit IRC21:38
*** darkschneider has quit IRC21:38
*** uen has quit IRC21:38
*** Hurrian has quit IRC21:38
*** utanapischti has quit IRC21:38
*** ketas has quit IRC21:38
*** mschlens has quit IRC21:38
*** Malinux has quit IRC21:38
*** Wizzup_ has quit IRC21:38
*** MohammadAG has quit IRC21:38
*** robink has quit IRC21:38
*** XDS2010_ has quit IRC21:38
*** guerby has quit IRC21:38
*** xkr47 has quit IRC21:38
*** rm_work has quit IRC21:38
*** realitygaps has quit IRC21:38
*** Kaadlajk_ has quit IRC21:38
keriodat freenode21:38
*** Vanadis_ has joined #maemo21:39
*** wmarone has quit IRC21:40
*** npm has quit IRC21:40
*** npm has joined #maemo21:41
*** platoscave has quit IRC21:42
*** Vanadis has quit IRC21:43
*** platoscave has joined #maemo21:46
*** Kaadlajk has joined #maemo21:48
*** mschlens has joined #maemo21:48
*** realitygaps has joined #maemo21:48
*** frafl has joined #maemo21:48
*** uen has joined #maemo21:48
*** xkr47 has joined #maemo21:48
*** Wizzup has joined #maemo21:48
*** darkschneider has joined #maemo21:48
*** realitygaps has quit IRC21:48
*** realitygaps has joined #maemo21:48
*** utanapischti has joined #maemo21:48
*** Malinux has joined #maemo21:48
*** guerby has joined #maemo21:48
*** rm_work|away has joined #maemo21:48
*** thedead1440 has quit IRC21:48
*** ketas has joined #maemo21:48
*** rm_work|away is now known as rm_work21:48
*** rm_work has quit IRC21:48
*** rm_work has joined #maemo21:48
*** robink has joined #maemo21:49
*** hardfalcon1 has quit IRC21:50
*** thedead1440 has joined #maemo21:50
*** hardfalcon has joined #maemo21:50
*** lbt has quit IRC21:50
*** npm has quit IRC21:51
*** npm has joined #maemo21:51
*** Guest31480 has quit IRC21:51
*** lbt has joined #maemo21:52
*** lbt has quit IRC21:52
*** lbt has joined #maemo21:52
*** XDS2010_ has joined #maemo21:52
*** platoscave has quit IRC21:52
*** valeriusL has quit IRC21:53
*** valeriusL has joined #maemo21:53
*** Guest64444 has joined #maemo21:55
*** wmarone has joined #maemo21:56
*** MohammadAG has joined #maemo21:56
*** platoscave has joined #maemo22:02
*** piggz_ has joined #maemo22:12
*** saidinesh has joined #maemo22:14
*** VD has joined #maemo22:14
*** thedead1440__ has joined #maemo22:14
*** VD is now known as Guest9884822:14
*** Veggen has joined #maemo22:14
*** pigeon has joined #maemo22:15
*** kraft has quit IRC22:15
*** zammy has joined #maemo22:15
*** kraft has joined #maemo22:16
*** mattaust1n has joined #maemo22:17
*** lbt has quit IRC22:17
*** emma has joined #maemo22:17
*** lbt has joined #maemo22:18
*** lbt has quit IRC22:18
*** lbt has joined #maemo22:18
*** FIQ has quit IRC22:20
*** platoscave has quit IRC22:20
*** fmunozs12 has quit IRC22:20
*** piggz has quit IRC22:20
*** NIN101 has quit IRC22:20
*** em has quit IRC22:20
*** MetalGearSolid has quit IRC22:20
*** RP_ has quit IRC22:20
*** kov has quit IRC22:20
*** mattaustin has quit IRC22:20
*** VD2 has quit IRC22:20
*** pigeon_ has quit IRC22:20
*** thedead1440_ has quit IRC22:20
*** saidinesh5 has quit IRC22:20
*** ArGGu^^ has quit IRC22:20
*** Veggen_ has quit IRC22:20
*** miniyo has quit IRC22:20
*** miniyo has joined #maemo22:21
*** platoscave has joined #maemo22:22
*** fmunozs12 has joined #maemo22:22
*** ArGGu^^ has joined #maemo22:22
*** _rd has joined #maemo22:23
*** platoscave has joined #maemo22:23
*** NIN101 has joined #maemo22:23
*** RP_ has joined #maemo22:26
*** FIQ|n900 has joined #maemo22:27
*** RP_ has quit IRC22:27
*** RP_ has joined #maemo22:27
FIQ|n900well this os issue I had earlier22:27
FIQ|n900was apparently caused *solely* by the optfs restoration22:27
FIQ|n900because, now, the "normal" issue of that just returned22:27
FIQ|n900i.e. the one where reboots solved it22:28
FIQ|n900set PYTHONHOME manually22:28
FIQ|n900I checked the lib directory in case it was missing22:28
FIQ|n900and found something interesting - there was *nothing* there22:28
FIQ|n900checked mountpoints22:28
FIQ|n900and for some reason python failed to be mounted correctly, because all python mountpoints isn't there (none is)22:30
FIQ|n900i.e. the bindmounts to /opt/pymaemo22:30
FIQ|n900issuing "mount" fixes this issue22:30
*** platoscave has quit IRC22:30
FIQ|n900but what causes it in first place?22:30
*** platoscave has joined #maemo22:32
FIQ|n900I also noticed that this was the first time (since then) where the clock was reset to jan 122:33
FIQ|n900perhaps that's related in some way?22:33
*** platoscave has joined #maemo22:33
*** Vanadis has joined #maemo22:38
*** _rd has quit IRC22:38
*** dhbiker has joined #maemo22:40
*** Cor-Ai_ has joined #maemo22:41
*** jaska__ has joined #maemo22:42
*** zap_ has joined #maemo22:42
*** thedead1440_ has joined #maemo22:42
*** sobukus_ has joined #maemo22:42
*** Gizmokid2010 has joined #maemo22:43
*** piggz__ has joined #maemo22:43
*** Malinux- has joined #maemo22:43
*** piscodig has quit IRC22:43
*** FredrIQ|n900 has joined #maemo22:43
FredrIQ|n900hi again22:44
FredrIQ|n900 perhaps that can give any clue to why python stuff isn't mounted occasionally but I don't know22:44
*** discopig has joined #maemo22:46
FredrIQ|n900(also, if you know a better method to get a single session than cat -n syslog | grep syslog, see the relevant line number, and do cat syslog | tail -n +4890 | pastebin, that would be nice to know of lol)22:46
*** dos1 has quit IRC22:47
*** kov has joined #maemo22:47
*** dos1 has joined #maemo22:47
*** auenf has joined #maemo22:47
*** ToJa92 has joined #maemo22:49
*** Pali_ has joined #maemo22:50
FredrIQ|n900the last reboot was fully clean (battery died, I swapped battery, and started up again)22:51
*** ColdFyre_ has joined #maemo22:51
*** platoscave has quit IRC22:52
*** RP_ has quit IRC22:52
*** Gizmokid2005 has quit IRC22:52
*** Gizmokid2010 is now known as Gizmokid200522:52
*** ToJa92 has quit IRC22:53
*** Cor-Ai has quit IRC22:53
*** FIQ|n900 has quit IRC22:53
*** miniyo has quit IRC22:53
*** piggz_ has quit IRC22:53
*** Vanadis_ has quit IRC22:53
*** zap__ has quit IRC22:53
*** jaska has quit IRC22:53
*** thedead1440__ has quit IRC22:53
*** Malinux has quit IRC22:53
*** Pali has quit IRC22:53
*** nox- has quit IRC22:53
*** brzys has quit IRC22:53
*** ColdFyre has quit IRC22:53
*** florentia has quit IRC22:53
*** sobukus has quit IRC22:53
*** utanapischti has quit IRC22:53
*** realitygaps has quit IRC22:53
*** XDS2010_ has quit IRC22:54
*** Wizzup has quit IRC22:54
*** Dynamit has quit IRC22:54
*** auenfx4 has quit IRC22:54
*** Lava_Croft has quit IRC22:54
*** n900-dk_ has quit IRC22:54
*** povbot_ has joined #maemo22:55 [freenode-info] channel trolls and no channel staff around to help? please check with freenode support:
*** n900-dk has joined #maemo22:57
*** povbot has quit IRC22:57
*** jaska__ has quit IRC22:57
*** jaska has joined #maemo22:57
*** sobukus has joined #maemo22:58
*** brzys has joined #maemo22:58
*** utanapischti has joined #maemo22:59
FredrIQ|n900uh huh?22:59
*** mattaustin has joined #maemo22:59
*** sobukus_ has quit IRC22:59
*** MikaT_ has quit IRC22:59
*** grinsekatze has quit IRC22:59
*** sfa has quit IRC22:59
*** g3kk3r has quit IRC22:59
*** mattaust1n has quit IRC22:59
*** realitygaps has joined #maemo22:59
*** realitygaps has quit IRC22:59
*** realitygaps has joined #maemo22:59
*** MikaT has joined #maemo22:59
*** Lava_Croft has joined #maemo23:00
*** platoscave has joined #maemo23:00
*** FredrIQ|n900 has quit IRC23:01
*** Kabouik has joined #maemo23:02
*** g3kk3r has joined #maemo23:02
*** platoscave has quit IRC23:02
*** Dynamit has joined #maemo23:03
*** FIQ has joined #maemo23:03
*** piggz has joined #maemo23:03
*** sfa has joined #maemo23:04
*** Jaffa has joined #maemo23:04
*** piggz__ has quit IRC23:05
*** RP_ has joined #maemo23:06
*** miniyo has joined #maemo23:06
*** discopig has quit IRC23:10
*** SmilyOrg is now known as Smily23:11
*** grinsekatze has joined #maemo23:11
*** brutal is now known as 14WAA3EU323:12
*** Win7Mac has joined #maemo23:12
*** florentia has joined #maemo23:12
*** DocScrutinizer51 has joined #maemo23:12
*** unclouded has joined #maemo23:13
*** zap_ has quit IRC23:13
*** Wizzup has joined #maemo23:13
*** Pali_ has quit IRC23:14
*** hubutm20 has quit IRC23:15
DocScrutinizer05freenode has issues it seems23:17
*** piggz has quit IRC23:17
*** platoscave has joined #maemo23:19
*** FIQ has quit IRC23:22
*** piggz has joined #maemo23:27
*** FIQ|n900 has joined #maemo23:31
FIQ|n900so.. any ideas regarding my issue?23:31
FIQ|n900dunno wtf happened with freenode lol23:31
nox-stupid kids23:34
nox-would be my guess23:34
*** Arkenoi has quit IRC23:36
*** Arkenoi has joined #maemo23:36
*** _rd has quit IRC23:44
*** DrCode has quit IRC23:45
*** DrCode has joined #maemo23:51
*** Mike11 has joined #maemo23:58

Generated by 2.15.1 by Marius Gedminas - find it at!