**** BEGIN LOGGING AT Sat Feb 04 02:59:58 2012 Feb 04 05:41:31 Hi, I'm creating a desktop widget using example-desktop-widget as an example. Can I get some help? My problem is that when I compile not everything is linked. I've included another library to preform a curl request Feb 04 05:42:20 I tried running ./autogen.sh and also ./configure.. Feb 04 06:30:37 winokia really killed maemo huh :( Feb 04 06:52:01 hah Feb 04 06:52:08 nokia killed maemo years ago Feb 04 06:52:27 it still kicks ass tho Feb 04 06:52:36 personally i still haven't found a better distro of linux for a mobile device Feb 04 06:56:02 it is the best bar-none Feb 04 06:56:14 hildon desktop would kick android's ass given a chance Feb 04 06:57:04 there is a project trying to bring it to market, unfortunatly they are trying to bundle it with a tablet device instead of replacing the OS entierly Feb 04 07:17:40 well Feb 04 07:17:47 if hildon was open maybe Feb 04 07:17:51 but nokia kept too much of it closed Feb 04 07:20:36 yeah nokia screwed the pooch, had I worked for nokia at the time that they went with windows (or even meego) I would have exposed the code Feb 04 07:20:52 i'm actually surprised a nokia dev didn't do that :) Feb 04 07:20:54 heh Feb 04 07:21:04 since i'm sure eventually they were fired anyways Feb 04 07:21:16 in favor for ms Feb 04 07:22:02 I think the real threat is that a cell phone really isn't that different from a walkie-talkie the difference being that one is basically free and the other has huge corporations behind it Feb 04 07:22:31 google can be trusted, meanwhile they are locking down their phone to the point that there is no off-switch Feb 04 07:22:43 (trusted by big-corp) Feb 04 07:24:41 the next big thing in cell phone technology will be a peer to peer communication network outside of the billing of big-corp, this cannot be allowed Feb 04 07:28:56 * newbie007 figured out my compile issue Feb 04 09:12:12 _freemangordon, ping Feb 04 10:26:43 maemo.org is down Feb 04 10:27:04 same here Feb 04 10:27:42 <_freemangordon> WFM Feb 04 10:35:33 <_freemangordon> trumee, pong Feb 04 14:17:25 Pali: nothing new Feb 04 14:18:02 DocScrutinizer, what should be new? Feb 04 14:18:38 everything should be new and exciting, but actually maemo.org down isn't that much Feb 04 14:20:07 btw not actually down but just dead slow Feb 04 14:20:25 so most likely some timeout will kick in before page got loaded Feb 04 14:20:38 now is maemo.org working Feb 04 14:20:46 before Error 503 Feb 04 14:21:25 well, there were times where this been "normal weekend operation mode" of maemo.org Feb 04 14:22:48 quite obviously it's best practice to push all the fishy updates and service packs 30min before everybody leaves for weekend, better yet: for xmas holiday Feb 04 14:23:09 always been like this Feb 04 14:25:12 I never got the point in doing this - if I were to manage that bunch of admins/devels/ I'd have announced a mega big NOGO for *any* infra updates/mods on Fridays Feb 04 14:26:39 and if you pushed an update on Thursday that *requires* a fix on Friday, your weekend is moot - stay at office watch the shit hit the fan, and goddam FIX it in time Feb 04 14:28:04 Nokia however never got the feeling they should be too concerned about an occasional few days abysmal user experience on their web appearance Feb 04 14:28:40 elinks working fine... Feb 04 14:28:51 e-what? Feb 04 14:29:00 only firefox, chromium, konqeror is too slow :D Feb 04 14:29:12 elinks - web browser Feb 04 14:29:29 http://elinks.cz/ Feb 04 14:29:37 mhm, maybe eventually I'll google that Feb 04 14:30:19 elinks is the best (text) browser Feb 04 14:31:07 sudo apt-get install elinks (on debian/ubuntu) Feb 04 14:31:47 yeah, you might have a point there, quite usually it's their "media content" I.E. pictures, icons, CSS, whatnot, that's fsckdup when sth breaks Feb 04 14:32:07 and sorry, no buntkuh crap here :-D Feb 04 14:32:29 elinks support some parts of CSS Feb 04 14:32:39 RPM based system with proper sysV init Feb 04 14:33:08 it could have also packaged elinks Feb 04 14:33:12 no gnome abomination either Feb 04 14:34:54 * mgedmin pictures DocScrutinizer compiling kernels by hand in some hermit cave high in the mountains Feb 04 14:34:54 and GODDAMN I wish I could say "no lennart crap at all" Feb 04 14:35:42 ~SLES Feb 04 14:35:52 ~wiki SLES Feb 04 14:35:55 At http://en.wikipedia.org/wiki/SLES (URL), Wikipedia explains: "'SLES' is an initialism for: * Sodium lauryl ether sulfate * SUSE Linux Enterprise Server, a server-oriented Linux distribution supplied by Novell, Inc. and targeted at the business market. " Feb 04 14:38:02 well, actually I run my own distro, regarding all the "personalizations" I did, but it's kinda "riped OpenSuse" Feb 04 14:39:06 actually considering 'rebase' to some RPM based LTS commercial distro Feb 04 14:39:26 or maybe even centOS etc Feb 04 14:41:43 DocScrutinizer, centOS is very poor for desktop experience Feb 04 14:42:03 DocScrutinizer, atleast the previous version was. Feb 04 14:42:38 I'm the sole responsible for my user experience Feb 04 14:43:31 it's just a question of how much work I'm willing to spend for administration of my system, and for which aspects thereof Feb 04 14:44:05 opensuse is good in that respect. Feb 04 14:44:22 however, gentoo works best for me. Feb 04 14:45:30 I admit the concept of gentoo where it came from is a tad *too* radical for me Feb 04 14:45:56 DocScrutinizer, did you looked at my bq2415x kernel driver? Feb 04 14:46:05 Pali: nope Feb 04 14:46:11 sorry Feb 04 14:46:46 I've read about the Q and A though, and they made me think you're on a good way Feb 04 14:50:23 for me what counts is: driver exposes a comprehensive set of methods to control each aspect of the chip in the most finegrained way, while still getting some abstract concepts to do things in a more convenient way. And then again, please no layering violations by implementing USB specific things like query for fastcharger or invoking ENUM from a kernel hw driver for a charger chip Feb 04 14:50:41 seems you got all that sorted Feb 04 14:52:05 the comment about "you better use that powersupply driver (API?)" is off topic to me, as the bq24150 is no powersupply, except maybe for boostmode and consumer USB peripherals Feb 04 14:55:14 ok Feb 04 14:55:37 (maemo.org dead) yeah, after 10 minutes of loading, I see the very familiar image-less fsckdup rendering of plain text on http://maemo.org Feb 04 14:56:00 so it's quite obvious why your elink works :-D Feb 04 14:56:36 I guess it's CSS that's borked in such a case (though no HTML expert here) Feb 04 14:58:43 oooh, the images are on static.maemo.org? that's the one to be down then maybe? Feb 04 15:00:00 http://static.maemo.org/style_maemo2009/img/maemo.jpg seems down Feb 04 15:01:27 indeed, "block images from static.maemo.org" makes the page maemo.org load with normal speed Feb 04 15:05:05 while "normal" display/rendering of http://maemo.org tries to chainload a truckload from static.maemo.org and each of those http-gets has to time out prior to your page finally displaying any content - that can take ages, depending on your local connection settings like server-connection-timeout etc Feb 04 15:26:15 hello Feb 04 15:26:21 got a small problem Feb 04 15:26:39 had some serius battery drain with latest kp49 and had to reflash Feb 04 15:26:54 now I'm unable to install kernel-power-settings Feb 04 15:27:01 any hints? Feb 04 15:29:30 DocScrutinizer, hildon app manager by default breaking apt locks... Feb 04 15:29:42 it is correct? Feb 04 15:31:47 i get the error while trying to build for release using qt creator Feb 04 15:31:49 dpkg-shlibdeps: failure: no dependency information found for /opt/QtSDK/Maemo/4.6.2/sysroots/fremantle-arm-sysroot-20.2010.36-2-slim/usr/lib/libgdigicam-0.3.so.0 Feb 04 15:32:08 how do add the dependency information for gdigicam Feb 04 15:32:21 i already have it installed in my sysroot... Feb 04 15:32:24 plz help Feb 04 15:35:59 someone help Feb 04 15:42:14 gitorious is down too Feb 04 15:42:37 bad day: maemo.org and gitorious.org not working... Feb 04 15:45:36 Pali: sorry? Feb 04 15:47:24 Pali: HAM ignoring apt's lockfile? Feb 04 15:47:37 seems yes Feb 04 15:47:41 it shouldn't Feb 04 15:47:54 can you test if it is true? Feb 04 15:47:59 though it's a rather niche case Feb 04 15:48:53 yeah it is Feb 04 15:48:57 hmm, kinda annoying to test, as you'd have to make sure apt doesn't remove the lockfile "too early" Feb 04 15:49:02 break_locks: Setting this to true will break the lock of the dpkg status database if necessary. Feb 04 15:49:36 maybe meant to recover from previous aborts Feb 04 15:50:08 I'd rather not touch it Feb 04 15:51:11 it really unlink() lock file and then lock it Feb 04 15:52:05 scenario: your device reboots during apt trying to do arbitrary stuff that sets lockfile. After that you'll face a HAM that's not working until you manually remove apt's lockfile, or start up apt manually again so it would take care about the stale lockfile itself Feb 04 15:53:50 DocScrutinizer, but after reboot unix lock on that file will not be set Feb 04 15:54:12 so apt-worker can set lock on that file Feb 04 15:54:14 that's not the point, the file itself lingers on Feb 04 15:54:31 no, it doesn't work that way afaik Feb 04 15:54:51 apps check if file exists, not if it's locked Feb 04 15:56:49 HAM couldn't unlink() the lockfile if there's been any flock set on it, I suppose - though iirc on linux flock is 'cooperative' so HAM had to check if there's any flock set, otherwise it wouldn't even notice there is and could happily unlink it nevertheless Feb 04 15:57:28 the "semaphore" is not the flock on the file, but the mere existence of the lockfile itself Feb 04 15:58:18 that's why you prefer to have all those lockfiles on a ramdisk Feb 04 15:58:42 as that ramdisk for sure gets cleaned on reboot Feb 04 16:01:20 it using apt lock which is use fcntl(FD,F_SETLK,&fl) Feb 04 16:02:55 and: struct flock fl; fl.l_type = F_WRLCK; fl.l_whence = SEEK_SET; fl.l_start = 0; fl.l_len = 0; Feb 04 16:04:17 so HAM checking if fcntl return != 1 Feb 04 16:04:47 and if problem, ham unlink file, create it again and call that fcntl Feb 04 16:06:14 hmm, it seemed to work just fine so far, so my advice: don't touch it Feb 04 17:37:20 Is there an IRC channel or blog where Nokia N810 users hang out? Feb 04 17:40:08 this was it before n900 drowned it out :) Feb 04 17:41:08 OldBear: you'll find the highest density of N810 owners here in this very channel Feb 04 17:41:42 * DocScrutinizer seems to recall a N810 subsection on tmo... Feb 04 17:42:38 * DocScrutinizer pets his N810 Feb 04 17:42:45 * DocScrutinizer pets his other N810 Feb 04 17:43:06 * ShadowJK 's N800, N810, N900 and N900 are powered on :) Feb 04 17:43:24 * DocScrutinizer pets his both N900 Feb 04 17:43:44 * DocScrutinizer glares at that other crap that pretends to run maemo Feb 04 17:44:10 lol Feb 04 17:44:21 no love for n950? Feb 04 17:44:27 not really Feb 04 17:45:03 semi nice hw (modulo the c-ts I never will have any love for), but an unbearable abomination of OS Feb 04 17:45:36 no uSD slot? Feb 04 17:45:38 MEH Feb 04 17:45:51 I just acquired the N810 because I wanted a WiFi only device to use when travelling for email, IM and Skype. Feb 04 17:46:14 for sure a decision you'll not regret Feb 04 17:47:05 I used N810 for IRC almost exclusively, for almost 2 years Feb 04 17:47:14 Was standing outdoors queueuing for burgers yesterday, took out my N900 to check stove and airtemp at home, and the guy next to me was like "how do you do that, mine doesn't work!?", he had some c-ts htc device, I told him to take off his gloves, and it worked like half a minute Feb 04 17:47:35 then his frozen finger wasnt registered anymore Feb 04 17:47:35 heh Feb 04 17:47:46 LOL Feb 04 17:47:59 yeah, c-ts is awesome, isn't it? Feb 04 17:48:32 I notice the c-touchpad on my netbook doesn't register my finger unless I blow on my finger first Feb 04 17:49:20 As my grandmother used to quote: "Cold hands, warm heart" Feb 04 17:51:05 heh Feb 04 17:51:22 I always had my N810 switch to 3g (via bluetooth via my cellphone) when outside wifi back before i had N900 Feb 04 17:52:24 has anybody here tried meego on the n900 lately? Feb 04 18:13:50 is there a permanent fix for a bluetooth headset with n900? on 75% attempts to use it, it disconnects after less than a minute Feb 04 18:16:57 shanttu: what kernel are you running? Feb 04 18:46:17 trumee, kp49 Feb 04 18:47:18 shanttu: kp49 is buggy for some headsets. Pre50 will have patch to fix that Feb 04 18:48:05 shanttu: best to stick with stock until 50 hits the repos, or roll your own kernel without the bt-mice patch Feb 04 18:48:12 trumee, excellent. thanks for the info. Feb 04 18:48:46 trumee, not in a rush. just wanted to know what could be worng and glad to hear it's known Feb 04 18:52:25 shanttu: http://talk.maemo.org/showpost.php?p=1158491&postcount=2676 Feb 04 19:01:45 trumee, thanks Feb 04 19:01:53 shanttu: np Feb 04 20:53:32 hai there guys Feb 04 20:53:41 (and girls if any ) Feb 04 20:53:42 :P Feb 04 20:57:52 ced117 ? from #libxenon ? :P Feb 04 20:59:09 nop xbox_gamer :-) Feb 04 21:00:11 oops sorry Feb 04 21:00:11 :/ Feb 04 21:00:45 funny Feb 04 21:01:03 he has almost the same nick as that guy Feb 04 21:01:04 -.- Feb 04 21:01:12 Pure Geeks Nokia finest Feb 04 21:01:21 no problem :-) Feb 04 21:02:05 i was wondering why noone has attempted to update alsa on N900 :P Feb 04 21:04:01 because last month there was a new release... 1.0.25 Feb 04 21:05:12 SmilyOrg: pozdravlen :P **** ENDING LOGGING AT Sun Feb 05 02:59:59 2012