**** BEGIN LOGGING AT Sun Jul 09 03:00:02 2017 Jul 09 03:41:09 so im trying to update to diablo cssu Jul 09 03:41:25 keep getting errors from the wiki Jul 09 03:41:42 about an exe that failed to download? Jul 09 03:43:41 oh.. nm.. seems to be working now heh Jul 09 04:06:04 im at a loss Jul 09 04:06:23 i installed the repo and updater but dont see the updater Jul 09 04:06:33 am i missing something? Jul 09 04:08:34 i dont see an update Jul 09 04:16:22 blah Jul 09 04:16:35 guess ill wait until i can flash it Jul 09 07:45:42 http://www.cnx-software.com/2017/07/09/jolla-tablet-take-2-youyouta-tablet-runs-linux-based-sailfish-os-2-1-operating-system-crowdfunding/ lol, intel? Jul 09 07:47:50 ported Hildon-Desktop would surely run on it with MESA :) Jul 09 11:02:09 The original tablet was also intel Jul 09 11:06:40 i wonder what is/will be the battery life Jul 09 11:40:07 KotCzarny, around 3 hours I think Jul 09 11:40:10 and the tablet was canceled with on a few backers having received their tablet. Jul 09 11:40:26 (not owner of original Jolla Tablet, just have generic Bay Trail-based one) Jul 09 11:40:26 that's where I stopped heh. I couldn't get past the typo Jul 09 11:40:51 yah. Jul 09 11:41:15 I can't get this n810 to see the cssu update. Jul 09 11:41:48 think I have to flash it. I can't even remember what I put on it last. Jul 09 11:46:12 umm what was the command to get the link for lazyflashing? Jul 09 11:46:25 ~flashing Jul 09 11:46:26 maemo-flashing is, like, http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing Jul 09 11:46:49 ~lazyflashing Jul 09 11:46:49 from memory, lazyflashing is http://wiki.maemo.org/Updating_the_tablet_firmware#The_Lazy_Approach Jul 09 11:47:12 cool. Guess they r saved to web log soonish? Jul 09 11:48:57 3 hours battery life? lol Jul 09 11:52:47 hmm, it seems im growing a bad habbit here. Second time in a day that i drop my phone and have it exploded to three pieces. Glad that n900 is rather sturdy. Jul 09 12:38:33 Wizzup, 20000 mAh powerbank will probably help it a bit :) Jul 09 12:39:28 is there any onscreen keyboard for hildon-desktop that can be recompiled? Jul 09 14:15:09 hm Jul 09 14:15:27 i give up on whatever is on this n810 heh Jul 09 14:16:32 looks like i will just have to flash it to figure it out Jul 09 14:16:54 the cssu repo isnt showing me an update on it Jul 09 14:19:40 W: GPG error: http://repository.maemo.org diablo Release: The follo wing signatures couldn't be verified because the public key is not available: NO_PUBKEY E40DC434616730BD Jul 09 14:19:49 maybe that too? Jul 09 14:50:16 W == Warning Jul 09 14:50:54 *should* not break anything Jul 09 14:51:45 I'm not sure there's actually a diablo CSSU repo Jul 09 15:04:46 DocScrutinizer05: maybe just a cssu in general? Jul 09 15:04:52 that key is for fremantle? Jul 09 15:05:25 either way. i think i'm going to resort to flashing it later anywyas. i can't seem to update to cssu ... repo installs.. updates. no update shown in either app manager or apt in a shell Jul 09 15:06:01 any other operating systems that run on the N810 that are worthwhile? i vaguely remember gentoo being able to run on it. although i'd probably never use gentoo Jul 09 15:06:06 the repos changed a bit during last 8 or 9 years Jul 09 15:06:20 yah heh. i'm sure. especially with the move away from nokia Jul 09 15:06:31 yep, exactly Jul 09 15:06:48 ~cssu Jul 09 15:06:48 to this day i curse noka for ditching maemo when they went to meego then abandoned everything Jul 09 15:06:48 it has been said that cssu is http://wiki.maemo.org/Community_SSU, or (Community Seamless Software Update) Jul 09 15:06:59 DocScrutinizer05: yah i looked at that and followed the diablo instructions Jul 09 15:07:13 should have pretty much been ... the link. app manager. install. update. Jul 09 15:07:25 so this? http://wiki.maemo.org/Diablo_Community_Project Jul 09 15:07:45 yes Jul 09 15:07:54 tried stable and unstable Jul 09 15:08:03 i see the pkg installed. but no update when refreshed Jul 09 15:08:33 hmm http://repository.maemo.org/community/dists/diablo/ still exists Jul 09 15:08:33 too bad i have my other laptops packed up otherwise i'd have used one to flash it Jul 09 15:09:01 I guess last commits to the diablo CSSU repo been years ago, many years Jul 09 15:09:23 2013 the freshest Jul 09 15:09:35 2013 is probably better than what i have on it now heh Jul 09 15:09:40 anything else i can run on it? Jul 09 15:10:05 hardly, N8x0 have software blob controlled battery charging afaik Jul 09 15:10:24 blah. ah well. i'll just install carman and see if the bt odb2 connector i have owrks Jul 09 15:10:35 others in here are more savvy regarding diablo and N8x0 Jul 09 15:11:04 yah it's just incredibly old. just thought it would be neat to use it for something. like when my iphone is charging and i want to irc heh Jul 09 15:11:10 I might bet a few users actually still use it every day Jul 09 15:11:42 if you want a player that can play almost any file format you could try oscp Jul 09 15:12:00 btw any reporting in here about diablo is highly welcome. At very least by me since I got a 6 devices to upfate as well Jul 09 15:12:05 update even Jul 09 15:12:25 well i'll worry about it after i am able to flash it. the thing wasn't touched since like 2011... i'm surprised the battery still works Jul 09 15:13:04 the neo900 looks interesting .. would be nice to have something that could run maemo again and was a bit beefier Jul 09 15:13:16 it's just still a bit dated compared to newer things. is that a maemo blob issue? Jul 09 15:14:06 I had one running 24/7/366 until a two or three years ago it failed on reboot out of nothing. I never found the time to look into it and meanwhile forgot all the knowhow Jul 09 15:14:36 N810 that is Jul 09 15:14:53 oh. the neo900 is a refurbished n900 with a newer board? Jul 09 15:15:08 indeed Jul 09 15:15:08 yes Jul 09 15:15:16 is supposed to be* Jul 09 15:16:04 are they even selling these? because the price is for partial funding.. for a higher price? and at 480EU Jul 09 15:16:09 that's crazy expensive heh Jul 09 15:16:23 it's basically me and no, it's still in development Jul 09 15:16:56 yes, unbearably expensive, due to low sales volume Jul 09 15:17:43 are you having the cases fabricated? or are you actually finding old n900s to use the cases from? Jul 09 15:17:51 the latter Jul 09 15:18:15 ouch. that is probably difficult Jul 09 15:18:18 til now. Might have to change to the former if we want to go for higher sales volume Jul 09 15:18:30 yes, very difficult Jul 09 15:18:57 not easier to see about having a case made? or a different sized case that can fit the board? Jul 09 15:19:08 i'm guessing the qwerty has to be an absolute pain to have made Jul 09 15:19:11 possibly Jul 09 15:19:33 yes, mechanical parts are a pita and very expensive tooling to make Jul 09 15:19:42 i was thinking more about the internationalization Jul 09 15:19:51 ie: german vs US qwerty Jul 09 15:19:58 niche problem :-) Jul 09 15:20:01 which i'm guessing is a big reason people moved away from hw qwerty Jul 09 15:20:38 keymats are still available, though other than qwerty are hard to find meanwhile Jul 09 15:21:02 so you'd pretty much have to ebay an old n900. gut it. swap the board. send it out? Jul 09 15:21:12 seems russian layout is widely available Jul 09 15:21:36 sort of, yes. We buy them in batches of 20 or 40 though Jul 09 15:21:46 old n900s? from where?! Jul 09 15:21:48 via our chinese boots on the ground Jul 09 15:21:51 oh Jul 09 15:22:14 almost seems easier if you could get some chinese company to make a case that fits the board. but you'd probably run into quality issues Jul 09 15:22:20 we sourced all we need for the preorders Jul 09 15:22:35 yes, exactly Jul 09 15:22:45 not probably, for sure Jul 09 15:23:15 you seen/watched http://neo900.org/stuff/cccamp15/ccc2015talk/neo900-wpwrak_CCC2015.webm ? Jul 09 15:25:09 o/ bbl Jul 09 15:40:27 hi all Jul 09 15:40:34 trying, at the ong last, to install CSSU Jul 09 15:40:46 and HAM gives me errors Jul 09 15:41:28 * rysiek|pl is getting the logfile now Jul 09 15:42:17 there's a lot of stuff like Jul 09 15:42:18 apt-worker: Ignoring version from wrong domain: osso-pdf-viewer-l10n-cscz Jul 09 15:45:12 and then there's a number of "PNG Decompression errors" Jul 09 15:45:26 then "[ Some installed packages are broken! ]" Jul 09 15:45:47 the only upgradeable package is libqtm-contacts Jul 09 15:45:57 but when I try to upgrade it I get a conflict Jul 09 15:46:28 with a metric shit-ton of qt4 packages Jul 09 15:46:47 reflash maybe then try ? Jul 09 15:46:52 ~cssu Jul 09 15:46:53 well, cssu is http://wiki.maemo.org/Community_SSU, or (Community Seamless Software Update) Jul 09 15:50:20 hmmm Jul 09 15:50:28 trying `apt-get install mp-fremantle-community-pr` Jul 09 15:50:30 let's see Jul 09 15:50:36 wrong way. Jul 09 15:50:45 ? Jul 09 15:50:47 go to that page and follow correct installation steps Jul 09 15:51:01 I went to that page and followed the correct installation steps. they failed. Jul 09 15:51:19 you might be having some blocking packages probably Jul 09 15:51:39 and then I went here: Jul 09 15:51:39 https://wiki.maemo.org/Community_SSU/Installation_FAQ Jul 09 15:52:02 """ Jul 09 15:52:02 In case there are a lot of packages causing the problem you may run the following command in X Terminal with root privileges: Jul 09 15:52:02 apt-get update Jul 09 15:52:02 apt-get install mp-fremantle-community-pr Jul 09 15:52:02 That will allow upgrade to the CSSU. Jul 09 15:52:04 """ Jul 09 15:52:27 it's already running, so I'll just see what happens I guess Jul 09 15:55:57 are you running that as root? Jul 09 15:56:20 yes Jul 09 15:57:10 so far so good Jul 09 15:57:20 done Jul 09 15:57:25 should I reboot? Jul 09 15:57:48 hmm, can't hurt Jul 09 15:58:01 m'kay Jul 09 15:58:05 and afterwards? Jul 09 15:58:13 try with the CSSU link again? Jul 09 15:58:28 anyway you noticed the recommended CSSU installation process consists of TWO steps? Jul 09 15:59:03 this? https://wiki.maemo.org/CSSU Jul 09 15:59:13 I see 9 steps there Jul 09 15:59:47 yes Jul 09 16:00:32 got to step 5 Jul 09 16:00:38 and HAM crapped out, repeatedly Jul 09 16:00:57 did you check step1 ? Jul 09 16:01:05 yes Jul 09 16:02:09 trying step 5 again Jul 09 16:03:12 >>Make sure you have no too weird catalog settings in Application manager, esp it's recommended you never disable the core Nokia SSU repositories. see 1.<< disable additional repos / catalogs you have Jul 09 16:03:14 ah, now it works Jul 09 16:03:42 yes, did that Jul 09 16:04:01 seems to work now Jul 09 16:05:07 we shall see Jul 09 16:10:30 huh Jul 09 16:10:40 no "Community SSU" icon in the applications menu Jul 09 16:11:32 there's no application "Community SSU" Jul 09 16:12:04 just like there's no application "debian wheezy" Jul 09 16:13:01 there is (or shall be) a "about CSSU" item in system menu Jul 09 16:14:11 sorry, in "Settinhs" app Jul 09 16:14:43 7. Once this is completed, close HAM and go into the applications menu. Tap the Community SSU icon. This will run through a series of scripts to ensure the community repository are set up. Jul 09 16:14:49 so. Jul 09 16:15:13 well that is the second step I meant Jul 09 16:15:28 yes, and I do not have thayt "app" Jul 09 16:16:14 I do have About Community CSU in Settings though Jul 09 16:16:15 huh Jul 09 16:17:54 ok, let's reboot and see what happens Jul 09 16:18:02 sorry, you have to wait for the CSSU experts then. The instructions worked for a bazillion of users Jul 09 16:18:02 this is weird Jul 09 16:18:10 yeah Jul 09 16:18:23 thanks anyway Jul 09 16:19:24 the Community SSU icon is a one shot thing completing the CSSU installation. It's possible you shortcut that step by your problem workaround Jul 09 16:20:04 open HAM and see which updates are available Jul 09 16:21:43 none Jul 09 16:23:28 apt says otherwise thouhg Jul 09 16:23:33 17 not upgraded Jul 09 16:23:35 hmmm Jul 09 16:24:58 you're probably not waiting for HAM to finsih Jul 09 16:25:39 your initial report up here already sounded fishy, not anything a apt-get install could fix Jul 09 16:26:14 well it explicitly says "no updates available" Jul 09 16:26:21 sounds like you got repos enabled that conflict with CSSU Jul 09 16:26:58 I have 2 Nokia mirrors, and the Community CSSU repo Jul 09 16:27:02 did you edit the repo list manually? Jul 09 16:27:04 these are the three I have enabled Jul 09 16:27:05 ever? Jul 09 16:27:06 no Jul 09 16:27:08 never Jul 09 16:27:32 should I do community-cssu-disabler, and then community-cssu-enabler again? Jul 09 16:27:53 no, disabler doesn't work Jul 09 16:28:17 is there a way to force the enabler to re-install CSSU? Jul 09 16:28:32 for sure there is, but I don't know it Jul 09 16:28:36 ok Jul 09 16:28:41 wait for Pali Jul 09 16:28:45 do you have CSSU on your n900? Jul 09 16:28:46 or merlin1991 Jul 09 16:28:55 sure Jul 09 16:29:02 I'd like to know which version of some packages I should have Jul 09 16:29:06 say, pulseaudio Jul 09 16:29:32 I'm at ii pulseaudio 0.9.15-1maemo43+0m5 PulseAudio sound server Jul 09 16:29:39 that doesn't sound correct Jul 09 16:30:09 DocScrutinizer05: can you check which version you're on? Jul 09 16:30:29 http://paste.ubuntu.com/25054665 Jul 09 16:30:56 no warranty this is all up to date Jul 09 16:31:39 yeah Jul 09 16:31:51 but I don't even have "cssu" in package versions Jul 09 16:31:52 wtf Jul 09 16:31:53 http://paste.ubuntu.com/25054671 Jul 09 16:32:27 thx Jul 09 16:33:45 ask Pali, he's the expert Jul 09 16:33:50 it's as if it completely ignores deb http://repository.maemo.org/community/ fremantle free non-free Jul 09 16:33:53 will do Jul 09 16:33:54 thanks Jul 09 16:34:31 what is the problem? Jul 09 16:36:16 if you're somewhat experienced with apt and shell, you may want to have a look at http://maemo.cloud-7.de/maemo5/session-log_enable-catalogs_README.txt and the source http://maemo.cloud-7.de/maemo5/usr/local/sbin/enable-catalogs Jul 09 16:36:26 Pali: CSSU install failed Jul 09 16:36:35 Pali: hey Jul 09 16:36:46 just click on install icon on wiki Jul 09 16:36:57 http://wiki.maemo.org/CSSU Jul 09 16:37:11 [2017-07-09 Sun 17:40:46] and HAM gives me errors Jul 09 16:37:13 [2017-07-09 Sun 17:41:27] * rysiek|pl is getting the logfile now Jul 09 16:37:14 [2017-07-09 Sun 17:42:17] there's a lot of stuff like Jul 09 16:37:16 [2017-07-09 Sun 17:42:18] apt-worker: Ignoring version from wrong domain: osso-pdf-viewer-l10n-cscz Jul 09 16:37:17 [2017-07-09 Sun 17:45:12] and then there's a number of "PNG Decompression errors" Jul 09 16:37:19 [2017-07-09 Sun 17:45:26] then "[ Some installed packages are broken! ]" Jul 09 16:37:23 Pali: yeah, I did that. first it failed a couple of times with an "error" in HAM, then I got a bit desperate and did apt-get install mp-fremantle-community-pr Jul 09 16:37:37 and then it kinda worked, I guess (HAM installed something), but: Jul 09 16:37:43 1. I still have old package versions Jul 09 16:37:49 remember he has n8x0 Jul 09 16:37:57 no, n900 Jul 09 16:38:06 2. even though in Settings I do have Community SSU Jul 09 16:38:07 oh? then it was the other guy, eh Jul 09 16:38:25 3. and even though community-ssu-enabler tells me all is installed Jul 09 16:38:57 Pali: so my question is, is there a way to *force* community-ssu-enabler to re-do all necessary steps even though it thinks they're done Jul 09 16:39:01 are you installing stable or testing? Jul 09 16:39:05 stable Jul 09 16:39:10 but I am open to testing also Jul 09 16:39:21 that's a device that's not used actively Jul 09 16:39:30 open HAM and check if CSSU stable catalogue is enabled Jul 09 16:39:43 ooh, you can install testing any time over stable Jul 09 16:40:00 yes, you can upgrade from stable --> testing Jul 09 16:40:09 Pali: "Community SSU" is enabled Jul 09 16:40:23 then there are "Community SSU (testing)" (and others) that are disabled Jul 09 16:40:27 but you should try to investigate errors in HAM instead of desparately trying apt-get install mp-fremantle-community-pr Jul 09 16:40:33 click on it, view, and write URL Jul 09 16:40:40 what is configured for that catalogue Jul 09 16:40:56 http://repository.maemo.org/community/ Jul 09 16:41:04 distro: freemantle Jul 09 16:41:10 components: free non-free Jul 09 16:41:18 disabled: false Jul 09 16:41:26 that is OK Jul 09 16:41:37 aye Jul 09 16:41:40 click in HAM where is button: check for updates Jul 09 16:41:43 and wait Jul 09 16:42:01 waaaaait ;-) Jul 09 16:42:12 this isn't speedyham yet Jul 09 16:42:27 yes, wait, HAM in stock maemo and cssu stable is slooow Jul 09 16:42:36 sometimes it can take about 30minutes... Jul 09 16:42:36 checking, and then... "no updates available" Jul 09 16:42:38 like, 10 minutes Jul 09 16:42:46 as in, it explicitly says there are no updates Jul 09 16:42:56 after it checks (displaying a progress bar and all) Jul 09 16:43:09 first it say "no updates", but icon is animating/rotating Jul 09 16:43:09 as if the Community SSU repo is being ignored Jul 09 16:43:19 it is not animating nor rotating Jul 09 16:43:27 CPU usage is low Jul 09 16:43:31 check for updates again Jul 09 16:43:43 sure Jul 09 16:44:00 and... open menu and check if you see there application icon named "Community SSU Enabler" Jul 09 16:44:00 checking... Jul 09 16:44:12 no updates available Jul 09 16:44:42 also run: apt-cache policy mp-fremantle-community-pr Jul 09 16:44:43 no, I do not have that icon Jul 09 16:45:24 http://wklej.org/id/3215951/ Jul 09 16:46:42 heretic thought: how about a reflash and then install CSSU again? Jul 09 16:46:46 ok, going to look at version numbers... Jul 09 16:47:01 DocScrutinizer05: quite a nuclear option ;) Jul 09 16:47:03 at least in git I see updates from 017-06-29 09:42:03 (ileuu) Jul 09 16:47:08 indeed Jul 09 16:47:12 DocScrutinizer05: might go for it if nothing else works Jul 09 16:47:20 so there is something new... Jul 09 16:47:26 see ~lazyflashing for that Jul 09 16:47:30 mhm Jul 09 16:47:45 eventually Jul 09 16:47:48 possibly Jul 09 16:47:50 maybe Jul 09 16:47:53 nope, in git is only testing Jul 09 16:47:57 -stable not updated Jul 09 16:48:12 in git is -stable 21.2011.38-1Smaemo7 Jul 09 16:48:16 upgrade to testing for now? Jul 09 16:48:27 and from apt we see: 21.2011.38-1Smaemo8 Jul 09 16:48:32 start from scratch with testing Jul 09 16:48:33 Pali: I definitely have an old pulseaudio version, for example Jul 09 16:48:47 Pali: as in, I don't think CSSU updates went through Jul 09 16:48:48 suggestion ^^^^ or even question Jul 09 16:48:58 should I click on the testing version icon in wiki/CSSU? Jul 09 16:49:01 Pali: ^^^ Jul 09 16:49:10 rysiek|pl: you do not have old pulseaudio Jul 09 16:49:30 cssu-stable uses same pulseaudio as in stock maemo Jul 09 16:49:35 aaaah Jul 09 16:49:44 ok, should I do the testing thing then Jul 09 16:49:49 wait... Jul 09 16:49:54 k Jul 09 16:50:10 open control panel (or how it is called) Jul 09 16:50:16 settings Jul 09 16:50:17 and check if there is cssu menu Jul 09 16:50:54 plus run: apt-cache policy libcpaboutcssu Jul 09 16:51:28 http://paste.ubuntu.com/25054793 Jul 09 16:52:09 rysiek|pl: ^^^ Jul 09 16:52:34 not from you DocScrutinizer05... Jul 09 16:52:43 sure, just for reference Jul 09 16:53:09 though that's Testing Jul 09 16:53:09 Pali: http://wklej.org/id/3215957/ Jul 09 16:53:27 that is ok Jul 09 16:53:37 you should have in "settings" icon of "cssu" Jul 09 16:53:37 Pali: there is "About Community SSU" in Settings Jul 09 16:53:40 open it Jul 09 16:53:46 what is there? Jul 09 16:53:47 do you see the "about community ssu" button in settings? Jul 09 16:54:02 nm Jul 09 16:54:22 Community SSU installed Jul 09 16:54:36 Version: 21.2011.38-1Smaemo8 Jul 09 16:54:47 Flavor: Stable Jul 09 16:54:47 flavor: Stable Jul 09 16:54:58 so cssu-stable is installed Jul 09 16:55:01 ok Jul 09 16:55:05 well then Jul 09 16:55:05 the "S" in version gives it away Jul 09 16:55:12 sorry for the commotion Jul 09 16:55:20 how do I upgrade to testing, then? :) Jul 09 16:55:29 open wiki page and click on testing Jul 09 16:55:35 since I nede the newer pulseaudio (that's what I am actually after) Jul 09 16:55:38 ok, doing that now Jul 09 16:55:39 thanks a lot Jul 09 16:56:04 please report back as soon as something doesn't work "normal" Jul 09 16:56:12 okok Jul 09 16:56:28 I don't expect anything to work "normal" ;) Jul 09 16:57:07 pone update Jul 09 16:57:09 *one Jul 09 16:57:15 Maemo 5 Community SSU Jul 09 16:57:25 that's step 2 I guess Jul 09 16:57:38 fun! Jul 09 16:57:39 :) Jul 09 16:58:20 1. step open wiki and click install; 2. step install update via HAM; 3. step stick on the icon in menu "Commutity SSU enabler" 4. step update via HAM Jul 09 16:58:45 you probably need to skip 3. step if icon is not there Jul 09 16:59:00 and after everything finish, reboot device Jul 09 16:59:50 3. step was the tricky stuff with "we need update done that can't get done since HAM gets closed" or somesuch? Jul 09 17:01:03 I think this was the whole reason for having that "Commutity SSU enabler" app icon Jul 09 17:01:08 sure Jul 09 17:02:20 enabler is adding new repository into system with option to allow updating system packages Jul 09 17:02:52 yep, and that can't fly without restarting apt/HAM so can't get done via postinst Jul 09 17:03:06 and once new catalogue is added, it is converted to apt repository Jul 09 17:03:06 iirc Jul 09 17:03:15 which means apt-get update needs to be called Jul 09 17:03:29 oh ffs Jul 09 17:03:35 and you cannot call apt-get update from posting deb package as apt database is locked Jul 09 17:03:52 so it needs to be done manually after HAM is finish all dpkg operations Jul 09 17:03:57 the n900 turned off mid-update because battery was dead (it's an old and bad battery) *even though* it was connected to power Jul 09 17:04:00 :nod: Jul 09 17:04:08 let's see if it's alive Jul 09 17:04:58 did it regularly shut down, with breaking-glass-audio etc? Jul 09 17:05:05 yeah Jul 09 17:05:09 ok then Jul 09 17:05:22 no idea what that did to the update Jul 09 17:06:42 yeah, new puleaudio Jul 09 17:06:51 *pulseaudio Jul 09 17:06:51 * DocScrutinizer05 still wonders if we couldn't have scheduled a alarmd event to take care about step 3 Jul 09 17:06:57 all seems fine Jul 09 17:07:39 rysiek|pl: ask Pali, maybe an apt-get update; apt-get upgrade is due now Jul 09 17:08:05 will do it anyway Jul 09 17:08:10 something you usually never should do Jul 09 17:08:33 you might find that useful info: Jul 09 17:08:36 ~jrtools Jul 09 17:08:37 methinks jrtools is http://wiki.maemo.org/User:Joerg_rw/tools Jul 09 17:09:03 thx Jul 09 17:10:50 opening HAM again and continue should work Jul 09 17:11:02 check for updates, wait until finish and upgrade Jul 09 17:11:50 DocScrutinizer05: last version of cssu-enabler in git forks from postinstall script, wait until apt finish and start that enabler Jul 09 17:12:00 it is glorious Jul 09 17:12:01 plus it instruct user to close HAM Jul 09 17:12:10 all seems to work fine Jul 09 17:12:13 checked for updates Jul 09 17:12:15 none available Jul 09 17:12:26 \o/ Jul 09 17:12:32 so it would be more automatical... but first we need new cssu release... Jul 09 17:12:36 Pali: genius! Jul 09 17:12:38 :-D Jul 09 17:13:02 rysiek|pl: check cssu version in "settings" Jul 09 17:13:45 Pali: keep in mind it may take minutes until apt-worker thread quits after close of HAM Jul 09 17:13:55 iirc Jul 09 17:14:13 you want to keep user informed about that wait Jul 09 17:14:39 "stay calm, the train will depart in a few minutes" Jul 09 17:15:06 I think killing apt.worker thread is a poor idea Jul 09 17:15:20 Pali: (...)1Tmaemo11 Jul 09 17:15:26 Flavor: Testing Jul 09 17:15:29 woo-hoo Jul 09 17:15:31 loiks good Jul 09 17:16:09 you should have portait mode and portrait lock icon in systray now Jul 09 17:16:31 plus "lightning fast" HAM Jul 09 17:16:56 plus a bazillion other less obvious bugfixes and improvements Jul 09 17:17:49 slightly smarter battery capacity report in systray menu Jul 09 17:18:20 yaddayadda Jul 09 17:19:45 Pali: they locked my ticket X-P - basically "wontfix": https://github.com/systemd/systemd/issues/6309 Jul 09 17:20:48 rysiek|pl: http://wiki.maemo.org/Community_SSU/Features http://wiki.maemo.org/Community_SSU/Changelog Jul 09 17:23:01 thx Jul 09 17:24:15 rysiek|pl: priceless: gconftool-2 -s /apps/osso/hildon-desktop/key-actions/ctrl_backspace_in_tasknav -t int 5 Jul 09 17:24:24 see ~jrtools Jul 09 17:26:14 http://maemo.cloud-7.de/maemo5/media/MHD_demo_20090108_001.mp4 Jul 09 17:27:18 exactly same like alt+tab on regular desktop Jul 09 17:28:50 just instead of alt+shift+tab for backwards rotation, you hold backspace and click the ctrl key, while for regular forward you hold ctrl and click bs Jul 09 17:30:15 releasing ctrl first and then bs wil keep the taskswitcher open Jul 09 17:30:45 releasing ctrl last will activate the window in focus (upper left) Jul 09 17:38:22 Pali: there's a quirk in MHD hotkeys taskswitcher (/apps/osso/hildon-desktop/key-actions/ctrl_backspace_in_tasknav -t int 5): when I press Ctrl+BS and release BS then Ctrl key *before* the animation stopped, it doesn't foreground the focused window Jul 09 17:40:25 the Ctrl key-up event should get stored in a buffer or whatever until animation finished. It gets flushed and discarded instead Jul 09 17:42:59 weird: fast doubleclick of either BS versus Ctrl key reveals the BS button gets not buffered while Ctrl button *actually gets buffered as long as BS pressed* Jul 09 17:44:56 I.E. when I do a fast triple click of CTRL while holding BS, the animation does 3 swaps even after last click done long ago. On triple click of BS key the animation stops after finishing one swap Jul 09 17:45:39 weird Jul 09 18:01:05 (ticket) tixxdz obfuscated stuff until total non-recognition, then threw the killer tantrum https://github.com/systemd/systemd/issues/6309#issuecomment-313911276 "fix it elsewhere!" Jul 09 18:04:11 'our shitty software is the best and sticks to our shitty policy so break other tools to fit to our shitty software' Jul 09 18:04:59 I'm temped to open yet another ticket "systemd maintainers insist in enforcing policies regarding usernames by simply denying service to certain names they personally don't like. Should leave the policy decision to the tools like useradd/adduser et al instead" Jul 09 18:25:24 how about a ticket named 'you trolls stop trashing linux ecosystem and go back to your shitty cockroach holes' Jul 09 18:31:11 that's not the first ticket with wording to that effect Jul 09 18:36:27 for a decent ticket: man adduser|less -j3 +"/the configurable regular expression" Jul 09 18:37:54 THIS is the only valid policy regarding "syntactically" correct usernames, and that may change any time in each particular system, leaving old non-conforming but still valid usernames in password database Jul 09 18:38:34 and even that is not really valid as username policy as soon as you got NFS or samba mounts, YP etc Jul 09 18:41:10 'not a problem, fix nfs, sambba, yp', problem solved Jul 09 19:10:58 Pali: I didn't get an icon for diablo Jul 09 19:11:12 the cssu enabler Jul 09 19:11:20 jrg: I do not know how cssu is working in diablo Jul 09 19:11:25 probably fully differently Jul 09 19:11:30 oh ok. Jul 09 19:11:54 instructions seem a bit similar Jul 09 19:16:32 (systemd) man useradd|less -j6 +'/On Debian, the only constraints are.*$' Jul 09 19:19:49 where would I open a ticket against debian (systemd)? Jul 09 19:21:22 Pali: http://wiki.maemo.org/Diablo_Community_Project Jul 09 19:21:58 http://repository.maemo.org/community/dists/diablo/ Jul 09 19:22:06 DocScrutinizer05: ticket for debian is reporting via "reportbug" tool Jul 09 19:22:15 /usr/bin/reportbug on debian system Jul 09 19:22:26 damn, that requires a working debian system Jul 09 19:22:34 or Jul 09 19:22:47 you can send well-known formatted email to well-known adress Jul 09 19:22:55 ummm Jul 09 19:23:07 https://www.debian.org/Bugs/Reporting Jul 09 19:23:15 see section: How to report a bug in Debian using email Jul 09 19:24:37 basically send email to address submit@bugs.debian.org with first line in body "Package: package_name" and second line "Version: package_version", make one line empty and then write description Jul 09 19:25:11 >>BUG: debian systemd 'user=' denies service to usernames that are perfectly valid according to `man useradd|less -j6 +'/On Debian, the only constraints are.*$' ` -- the 'syntax' check on name values for key "user=" should get removed completely since it doesn't serve any obvious purpose<< Jul 09 19:26:08 package_name would be: systemd Jul 09 19:26:23 list of known systemd bugs in debian are at: https://bugs.debian.org/systemd Jul 09 19:29:11 so if you want to report bug, just write email with those two lines... whole bug reporting system is working via emails, that web interface is just read-only view Jul 09 19:35:46 yah i don't think i can flash in sierra Jul 09 19:35:51 flasher doesn't work :/ Jul 09 19:37:11 RX-44_DIABLO_5.2008.43-7_PR_COMBINED_MR0_ARM.bin Jul 09 19:37:15 heh Jul 09 19:37:24 wow.. 2008 :) Jul 09 19:41:50 are there cssu bins i an flash to the n810 instead of the original image? Jul 09 19:42:15 nope, cssu is OTA update Jul 09 19:42:26 ah ok. then i'm at a loss. Jul 09 19:42:41 you flash original image and then you update CSSU from apt repository Jul 09 19:42:41 installed the repo and don't have an icon or a way to start it. neither the app manager or apt see anything Jul 09 19:42:47 is there maybe a script i need to run? Jul 09 19:43:31 guess maybe the n810 repo is broken or something else is on the n810 Jul 09 19:44:08 diablo cssu install steps are different, there is no icon Jul 09 19:44:15 read diablo wiki: http://wiki.maemo.org/Diablo_Community_Project#Upgrading_to_the_.22stable.22_version Jul 09 19:45:12 i did that Jul 09 19:45:26 flashing should work, just use regular linux machine, not some virtualisation from windows Jul 09 19:46:00 Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update Jul 09 19:46:03 i don't see the update Jul 09 19:46:05 it is known that windows has usb enumeration and plus windows virtualisation is not so good... Jul 09 19:46:30 even tho i see the repo in app manager Jul 09 19:49:07 ah well. when i get the chance i'll flash and try the ota updat eagain and see what happens Jul 09 19:49:20 somewhere around me should be one n810... but today I already failed to find it... otherwise I would try upgrade Jul 09 19:49:46 Efforts to rewrite or open previously closed components of Diablo have been unsuccessful. Jul 09 19:49:58 I found this thread: https://talk.maemo.org/showthread.php?t=96247 and wrote answer Jul 09 19:50:01 that's too bad Jul 09 19:50:03 maybe could help you Jul 09 19:58:25 nope. still no updates Jul 09 19:58:34 not sure what is going on with the thing Jul 09 19:58:45 don't see anything that allows me to update to cssu for diablo Jul 09 20:02:21 oh Jul 09 20:02:50 repository.maemo.org/catalogue/dists/diablo/user/binary-armel/Packages.gz failed to refresh Jul 09 20:09:54 I remember talks about not completely reversed closed-source PulseAudio modules Jul 09 20:10:05 are they required for VoIP? Jul 09 20:13:51 ok. i give up i can't seem to update this thing lol Jul 09 20:14:09 i'll flash it when i get a chance and yank a linux laptop out of a box and try it again some other day Jul 09 21:50:59 Sorry for the delayed response, yes I got a new token mailed and voted. Jul 09 21:51:37 Elections always seem to be when I am away or busy. Jul 10 00:33:05 WRT that systemd thing .. my system at work (debian) handles usernames starting with "0" fine. Jul 10 00:33:59 systemd does, that is .. wher `User=0max` and the "0max" user actually exists. Jul 10 00:34:25 If it doesn't exist, it fails with status=217/USER Jul 10 00:35:12 must be either a recent regression or some behaviour that depends on another library .. didn't notice anyone mentioning something like that when reading through the issue though. Jul 10 00:37:19 * Maxdamantus is using systemd 222 **** ENDING LOGGING AT Mon Jul 10 03:00:02 2017