| inky_ | bencoh, thank you so much, i losh quickflickr and could not find. there was also jockr i believe but again i cannot find it | 00:42 |
|---|---|---|
| sunshavi_ | df | 02:07 |
| sunshavi_ | kbd issue. sorry | 02:08 |
| rafael2k | tested the pigzz's pinhole... still very early stages, but he is writing in a very portable way, supporting kirigami, silica, qt-controls and uuitk | 08:38 |
| rafael2k | managed to compile with qt-controls and kirigami, all good | 08:38 |
| rafael2k | the UI seems nice, without any big issue | 08:39 |
| rafael2k | yay, got it working | 09:02 |
| rafael2k | lets package it | 09:03 |
| rafael2k | http://abradig.org.br/maemo-crazyness/pinhole/pinhole-1.jpeg | 09:07 |
| rafael2k | http://abradig.org.br/maemo-crazyness/pinhole/pinhole-2.jpeg and http://abradig.org.br/maemo-crazyness/pinhole/pinhole-3.jpeg | 09:07 |
| rafael2k | a screen cap with import: http://abradig.org.br/maemo-crazyness/pinhole/pinhole.jpg | 09:07 |
| dsc_ | kewl | 09:08 |
| rafael2k | still very early stages... but I think we have a winner : ) | 09:08 |
| rafael2k | btw, sometimes the ov5640 gets boged in boot with the current 6.1.3 kernel in Chimaera.. just rmmod and modprobe it starts working... still debugging the issue | 09:18 |
| dsc_ | BlagovestPetrov4: when are you receiving the cables? | 09:32 |
| BlagovestPetrov4 | I'm waiting for the micro usb connectors from AliExpress. Hopefully in two weeks | 09:33 |
| dsc_ | cool, I have 2x droid4's that are 'bricked' | 09:34 |
| BlagovestPetrov4 | Sunder? | 09:34 |
| dsc_ | yes | 09:35 |
| BlagovestPetrov4 | :))) | 09:35 |
| dsc_ | :D | 09:35 |
| dsc_ | BlagovestPetrov4: https://plak.infrapuin.nl/selif/xpfzjbxu.mp4 | 09:35 |
| BlagovestPetrov4 | we can try to replace the batteries with working phones in initlab | 09:35 |
| BlagovestPetrov4 | cool! | 09:36 |
| dsc_ | BlagovestPetrov4: soon^tm? | 09:36 |
| BlagovestPetrov4 | I might be in the lab in the afternoon, but still cannot confirm it. There is a strong wind outside :D | 09:39 |
| BlagovestPetrov4 | but tomorrow, definitely | 09:39 |
| dsc_ | alright | 09:39 |
| rafael2k | so, about the volume applet | 09:51 |
| rafael2k | this should be in a platform specific package, right? /usr/share/maemo-statusmenu-volume/sinks.ini | 09:51 |
| rafael2k | yay, volume working | 10:02 |
| rafael2k | sink_name=alsa_output.0.HiFi__hw_PinePhone_0__sink | 10:02 |
| uvos | rafael2k: thats not the solution | 10:34 |
| uvos | as i discribed before | 10:34 |
| uvos | there is no reason this needs to be "hardcoded" into any config file at all | 10:35 |
| rafael2k | until nobody fixes it, it is a solution, even if temporary | 10:35 |
| rafael2k | : ) | 10:35 |
| freemangordon | rafael2k: what is that white stripe on top of camera application? | 11:06 |
| freemangordon | also, you may want to set some fullscreen flag (not sure which one) | 11:07 |
| rafael2k | freemangordon: good question, I'd love to get rid of it | 11:12 |
| freemangordon | dsc_: how do you start the application? | 11:13 |
| freemangordon | also, is this chimaera? | 11:13 |
| rafael2k | chimaera, yes | 11:14 |
| freemangordon | rafael2k: oops, "how do you start the application?" was pointed to you | 11:15 |
| freemangordon | like, do you change qt platform plugin? | 11:16 |
| rafael2k | ah no no | 11:21 |
| rafael2k | I did not change nothing | 11:21 |
| rafael2k | just called the app | 11:21 |
| rafael2k | should I try some QT switches? | 11:21 |
| freemangordon | no | 11:24 |
| freemangordon | I was thinking if you may possibly start with wrong theme or platform plugin | 11:24 |
| rafael2k | I could open the project in QT Creator and see if there is some stuff in the top | 11:24 |
| freemangordon | if you start on desktop, do you still see that white stripe? | 11:24 |
| freemangordon | right | 11:24 |
| rafael2k | need to try, did not compile on my bullseye desk yet | 11:25 |
| rafael2k | will do it | 11:25 |
| dsc_ | freemangordon: its in a 'works on my machine' state currently, needs some packaging still | 12:02 |
| Wizzup | morning | 12:03 |
| dsc_ | yes chimaera | 12:03 |
| * Wizzup trying waydroid on maemo-leste to set up his bank account before the 24h expiry | 12:38 | |
| freemangordon | Wizzup: change the bank | 14:32 |
| Wizzup | freemangordon: yeah I found one that isn't like this | 14:33 |
| freemangordon | right, that's how we shall heal them ;) | 14:38 |
| Wizzup | the one I am at should also offer a token | 14:39 |
| Wizzup | but they said 'they do not have them' | 14:39 |
| freemangordon | hehe | 14:39 |
| Wizzup | the other bank also said it but then when I insisted the 'found some' | 14:39 |
| Wizzup | *shrug* | 14:39 |
| Wizzup | brb | 14:39 |
| freemangordon | I still don;t get it what's wrong with OTP | 14:39 |
| norayr | >hildon-base : Conflicts: elogind but 246.10-2 is to be installed | 14:41 |
| Wizzup | norayr: yes, this is mentioned in the news post. | 14:41 |
| norayr | that's in emulator. trying to build something, but apt build-dep . returns that. | 14:41 |
| Wizzup | this is why we don't tell people to use chimaera, it's not ready | 14:41 |
| Wizzup | :) | 14:42 |
| norayr | i was able to build other things without this problem. :/ | 14:42 |
| Wizzup | there is no workaround here | 14:42 |
| norayr | ok, i'll try to do something. | 14:42 |
| norayr | i thought this is solved. | 14:42 |
| norayr | because i guess this was solved on droid. and on pp. | 14:42 |
| Wizzup | not solved anywhere | 14:42 |
| Wizzup | 100% | 14:42 |
| Wizzup | the phones are usable without elogind but it has spread as some virus to most pkgs so they now hard depend on it | 14:43 |
| Wizzup | so we need to accept it and also support elogind | 14:43 |
| Wizzup | until then, we're stuck here | 14:43 |
| norayr | eh. i still resist installing elogind on my gentoo. (: | 14:43 |
| norayr | ok will try to install dependencies somehow and build the package. | 14:44 |
| norayr | will ask for a repo soon. hopefully. | 14:44 |
| Wizzup | cool | 14:45 |
| Wizzup | bbl | 14:45 |
| norayr | Wizzup: did you notice we discussed that the volume up key is unable to trigger vkb on pp? | 15:07 |
| norayr | as uvos helped to find out, it gets blocked by volume applett. | 15:08 |
| norayr | uvos, Wizzup, right now it is impossible to write in pidgin on pp because of that. i cannot do Enter, because enter doesn't work well with old vkb backend. and new vkb backend is not triggerable. | 15:08 |
| norayr | can we just switch to new vkb backend and give up the old one? | 15:09 |
| Wizzup | norayr: what is this magical new vkb backend | 15:14 |
| norayr | x11 backend by uvos? | 15:14 |
| norayr | we have currently two backends. uvos can explain it better. | 15:14 |
| Wizzup | I think you lack a lot of info here | 15:14 |
| norayr | new backend is why we are able to write in non hildonized apps. | 15:14 |
| norayr | old backend is for hildonized apps. | 15:15 |
| Wizzup | not really | 15:15 |
| Wizzup | right now any gtk2 and gtk3 application will have a virtual keyboard, where they are 'maemo'ized or not | 15:15 |
| Wizzup | what is missing is the qt5 equivalent, which I didn't port yet | 15:16 |
| norayr | okay, still, right now maemo is not usable at all, since enter key is not possible. we need to do something with that. | 15:16 |
| norayr | look | 15:16 |
| Wizzup | then there is this x11 thing that is limited and has to be invoked manually | 15:16 |
| norayr | enter key will be possible with new uvos backend for vkb | 15:16 |
| Wizzup | then there is the suggestion to use at-spi2 for this, which nobody did | 15:16 |
| norayr | when you tap on edit box, or you trigger the vkb with the key (search on d4) you get different keyboards actually. | 15:16 |
| Wizzup | the reality is that using maemo leste now on a device without keyboard means you're in for a world of pain, which we know | 15:16 |
| norayr | so the kbd that you trigger with a hardware key has proper working enter key. | 15:17 |
| Wizzup | and we need the volume buttons to be the volume buttons, I'd say | 15:17 |
| norayr | the kbd that triggers because of the tap on the edit field - doesn't. | 15:17 |
| Wizzup | whatever the 'enter key' issue is, seems like a different problem | 15:17 |
| norayr | i know because i was using the pp with onscreen kbd, as well as d4. this bug is common to both devices. | 15:18 |
| norayr | if you trigger the kbd by the hardware key, the enter works. | 15:18 |
| norayr | uvos was saying that's because it has new, x11 backend. | 15:18 |
| norayr | and he wrote it. while the old code has all sorts of bugs, and kbd triggered by tap is more buggy. | 15:18 |
| norayr | so enter may not work there. | 15:18 |
| norayr | so i was typing a message, then i was coming back to edit field, then i was triggering other version of the keyboard with volume up, and then enter would work. | 15:19 |
| norayr | that was already very discomfort, but now it is even worse. because the new keyboard code is not triggerable. | 15:19 |
| norayr | not sure that the volume up is a good solution. i would prefer to not explain to my friends whom i try to convince to use maemo leste that in order to type enter they need to trigger the kbd by other key. | 15:20 |
| norayr | not by tapping. | 15:20 |
| Wizzup | maybe you can file a bug report for pidgin, assuming it's gtk3, and enter not working | 15:29 |
| Wizzup | I've never tried pidgin since I just want to use it through tp ;) | 15:29 |
| norayr | no no, it's not pidgin. | 15:41 |
| norayr | we duscussed it here with uvos before, last year, and year before last year. | 15:41 |
| norayr | my message is: | 15:41 |
| norayr | if i send enter by triggering vkbd by hardware key (like vol+up or search) then enter works! | 15:42 |
| norayr | that's not pidgin, that's vkbd, and apparently you didn't know about the issue. | 15:42 |
| norayr | just tried again, that's what i am saying: in maemo's xterm, in hildonized leafpad enter works. | 15:44 |
| norayr | in pluma it doesn't work. | 15:44 |
| norayr | you cannot write in pluma and send enter by vkb | 15:44 |
| norayr | unless you trigger the vkb by hardware key, like vol up or search on d4 | 15:44 |
| norayr | you need to know that we have two different backends for vkb. | 15:45 |
| norayr | or uvos has to come to clear it up. | 15:45 |
| Wizzup | right, so your problem is that enter doesn't work from the normal triggered keyboard. | 15:49 |
| Wizzup | I think that's what I surmised earlier | 15:49 |
| Wizzup | in any case I never use the x11 keyboard version on my droid | 15:49 |
| Wizzup | so I don't know how it works differently | 15:49 |
| dsc_ | I am running 2x droid4 with distcc for distributed compiles | 16:42 |
| dsc_ | lel | 16:42 |
| Wizzup | dsc_: if you turn the screen off it disabled one core, jfyi | 16:43 |
| Wizzup | this is for power saving purposes | 16:43 |
| Wizzup | but you might want to consider keeping the screen on | 16:43 |
| dsc_ | Wizzup: ahhhhh I was wondering why `htop` would sometimes show 1 core | 16:45 |
| dsc_ | was thinking maybe I was starting to go crazy | 16:45 |
| dsc_ | probably wasted a lot of time as well | 16:47 |
| dsc_ | not knowing this lol | 16:47 |
| Wizzup | :( | 16:47 |
| dsc_ | this distcc stuff is cool though | 17:19 |
| dsc_ | cmake + ccache, distributed over multiple droid's | 17:20 |
| Wizzup | heh, you have multiple working ones now? :D | 17:20 |
| dsc_ | https://plak.infrapuin.nl/selif/td0h9pws.png | 17:21 |
| dsc_ | Wizzup: Yeah I have 2, and hopefuly BlagovestPetrov4 can bring 2 others from the dead ^^ | 17:21 |
| Wizzup | I can probably too when I get there | 17:22 |
| Wizzup | usually just a wall charger is enough for me to get it working | 17:28 |
| Wizzup | it's weird, I've never actually bricked any | 17:28 |
| dsc_ | it simply wont start charging when wall charger is connected | 17:29 |
| dsc_ | :( | 17:29 |
| Wizzup | if you leave it there for a day or two usually magic happens still | 17:29 |
| dsc_ | :D | 17:29 |
| Wizzup | alternatively you can -probably- use one of the working d4s with some battery swapping magic | 17:29 |
| Wizzup | but yeah | 17:29 |
| BlagovestPetrov4 | oh, I could easily brick them :D | 17:29 |
| BlagovestPetrov4 | yeah, that's the easiest way. I'm using the one that came with the lapdock | 17:30 |
| sicelo | re: vkb - norayr and others - what about, instead of using a volume key, add a status menu item with high priority (so it doesn't get moved too far to the bottom)? it's a really ugly workaround, but in the absence of other immediate solutions ... | 18:22 |
| Wizzup | sicelo: how about just finding a proper solution :) | 18:25 |
| Wizzup | like, the at-spi module | 18:25 |
| sicelo | well if there's time for that, sure :-) | 18:25 |
| sicelo | i was just mentioning since it sounds like an immediate problem for norayr for some reason | 18:26 |
| freemangordon | Wizzup: or swipe bottom-up | 18:27 |
| Wizzup | I think ultimately we have a few things on our hand with hildon input method | 18:27 |
| Wizzup | one is qt5, perhaps through at-spi, the other is that we don't always want it 'over' the application | 18:27 |
| Wizzup | neither are simple, so I don't think it'll happen in the next week or so | 18:27 |
| freemangordon | umm, qt5 should not be at-spi | 18:29 |
| freemangordon | we already have qt4 inegration with him on fremantle | 18:30 |
| freemangordon | I guess we can port it to qt5 | 18:30 |
| freemangordon | I doubt it is that complicated | 18:30 |
| freemangordon | but, if you promise to fix the theming, I will make qt5 him input plugin :p | 18:30 |
| freemangordon | deal? | 18:30 |
| bencoh | I got some strange usb/uart-related error after disconnecting droid4 from laptop and connecting it to some noname wallcharger: droid4:~$ dpkg -l |grep linux-image | 18:36 |
| bencoh | rc linux-image-droid4 5.10.9-1+2m7.1 armhf Linux kernel for Motorola Droid4 | 18:36 |
| bencoh | ii linux-image-omap 5.18.9-2+2m7 armhf Linux kernel for OMAP devices running Maemo Leste | 18:36 |
| bencoh | woops | 18:36 |
| bencoh | http://pastebin.notk.org/pastebin.php?show=m1993d95e | 18:36 |
| rafael2k | my temporary workaround for absent/bad vkb - use qtwebbrowser and literm | 18:37 |
| bencoh | (I think that the same happened a few hours ago but at that time it looked like phone crashed, I had to hardreset it) | 18:37 |
| Wizzup | freemangordon: fix the qt theming you mean? | 18:37 |
| Wizzup | freemangordon: I think it will be relatively complicated | 18:37 |
| Wizzup | but you're very welcome to try | 18:37 |
| Wizzup | and yeah I can try to commit to the theming fixes | 18:37 |
| Wizzup | those ... seem ... easier | 18:37 |
| Wizzup | bencoh: maybe try 6.1.x kernel from -devel, I *vaguely* seem to recall this was fixed | 18:38 |
| bencoh | oh, alright | 18:38 |
| Wizzup | btw.. | 18:38 |
| Wizzup | $ ./voicecall-test | 18:38 |
| Wizzup | hello, world | 18:38 |
| Wizzup | "/org/freedesktop/Telepathy/Account/sofiasip/sip/_3708530001_40sip_2efreedom_2enl0" | 18:38 |
| Wizzup | voiceCallsChanged | 18:38 |
| Wizzup | activeVoiceCallChanged | 18:38 |
| Wizzup | answering | 18:38 |
| Wizzup | hangup | 18:38 |
| Wizzup | voiceCallsChanged | 18:38 |
| freemangordon | :) | 18:38 |
| Wizzup | activeVoiceCallChanged | 18:38 |
| Wizzup | sorry for the spam :) | 18:39 |
| bencoh | Wizzup: I'm still running beowulf, I guess I should upgrade to chimaera? | 18:39 |
| freemangordon | no | 18:39 |
| rafael2k | (and vkb plugin in chromium... and a physical usb-c->usb-a adapter + usb keyboard or bt keyboard) | 18:39 |
| Wizzup | bencoh: I think beowulf-devel has 6.x, but maybe we should promote the 6.1.x to beowulf stable too | 18:39 |
| bencoh | lemme see ... | 18:39 |
| freemangordon | rafael2k: unfortunately chromium has broken gtk3 input method support :( | 18:40 |
| rafael2k | freemangordon: but there are good vkb as plugins... they solve for now | 18:41 |
| freemangordon | like, it does not follow gtk3 requirements | 18:41 |
| freemangordon | I tried all of them a months or so ago | 18:41 |
| freemangordon | none worked | 18:41 |
| freemangordon | *a month | 18:41 |
| rafael2k | me too, but I foundd one that works, lemme see the name | 18:41 |
| freemangordon | that's be surprising :) | 18:42 |
| freemangordon | *that'd | 18:42 |
| freemangordon | (another typos day :) ) | 18:42 |
| Wizzup | I think he is talking about a chrome extension | 18:42 |
| Wizzup | not a gtk plugin/extension | 18:42 |
| freemangordon | mhm | 18:42 |
| freemangordon | I know | 18:42 |
| rafael2k | chrome extension, yes | 18:42 |
| Wizzup | oh, ok | 18:42 |
| * Wizzup hides | 18:42 | |
| freemangordon | I tried 4 or 5 back then | 18:43 |
| freemangordon | maybe chromium in beowulf was too old, dunno | 18:43 |
| rafael2k | I'm in Chimaera, indeed | 18:44 |
| rafael2k | https://chrome.google.com/webstore/detail/screen-virtual-keyboard-s/gkiknnlmdgcmhmncldcmmnhhdiakielc?hl=ru | 18:46 |
| freemangordon | thanks! | 18:47 |
| rafael2k | but there is an issue.. it does not work in the url bar | 18:47 |
| rafael2k | :( | 18:47 |
| freemangordon | right | 18:47 |
| rafael2k | need to call chromium https://website from cmd line, and then yes, you can use it for on-screen website text boxes | 18:48 |
| rafael2k | I had found one in the past that was working... but could not find it again | 18:48 |
| rafael2k | don't remember if that was in firefox or chromium thou | 18:48 |
| freemangordon | I think it is easier to just fix chromium input method support | 18:49 |
| freemangordon | basically the issue is that it does not set focus window unless physical kbd key is pressed | 18:49 |
| freemangordon | so it sends focus in/out events when you enter text field, but no window events | 18:50 |
| freemangordon | just adding that missing line of code will make him vkb working | 18:50 |
| rafael2k | right, did not know that was the bug | 18:51 |
| freemangordon | see https://github.com/chromium/chromium/blob/a798c106aac5dd0d2ccee53b9ebd14a4cce7d2a0/chrome/browser/ui/libgtkui/input_method_context_impl_gtk.cc | 18:51 |
| freemangordon | SetContextClientWindow() is called only in DispatchKeyEvent() :) | 18:52 |
| rafael2k | I'm following a bug ticket also in which chromium will be able to use pipewire (which in turn can get video from libcamera) in order I can join a webrtc call using the camera | 18:52 |
| Wizzup | so now we'll have to compile with qtwebengine and chromium? | 18:53 |
| rafael2k | tks! | 18:53 |
| * Wizzup crawls under a bed ;) | 18:53 | |
| Wizzup | s/with/both/ | 18:53 |
| rafael2k | :P | 18:53 |
| freemangordon | Wizzup: not now, but you got the idea :p | 18:53 |
| rafael2k | I want my chromium working in webrtc calls with video! | 18:53 |
| rafael2k | eheheheh | 18:53 |
| bencoh | wait, does pipewire work in leste? | 18:54 |
| rafael2k | it is in the repo... did not tested it yet | 18:54 |
| rafael2k | it kind of works in bullseye | 18:54 |
| bencoh | don't we have pulseaudio-specific modules? | 18:54 |
| rafael2k | but my use case would be just for video... for audio it was a bit flacky in bullseye / chimaera | 18:55 |
| rafael2k | yes | 18:55 |
| bencoh | like the sphone volume pa plugin, or whatever that was called | 18:55 |
| rafael2k | pipewire can be a drop-in replacement to pulseaudio | 18:55 |
| Wizzup | only in the most basic setups | 18:56 |
| rafael2k | but I will not use pipewire for audio at this point, just for routing video | 18:56 |
| Wizzup | pipewire requires a lot of configuration, but yes, it's superior to pulseaudio for sure | 18:56 |
| Wizzup | but if we start pulling out PA now for pipewire I think our jenga mobile distro will come tumbling down :P | 18:56 |
| rafael2k | but in bullseye / chimaera it is a bit old... I did not like it on my desktop tbh... had some issues | 18:56 |
| Wizzup | (metaphorically of course) | 18:56 |
| rafael2k | dont do it | 18:57 |
| rafael2k | it is not stable enough in the old version we have right now in chimaera | 18:57 |
| rafael2k | but for video it can save lives, yes | 18:58 |
| freemangordon | ok, I will fork chromium and will try to make it work properly with him | 18:58 |
| freemangordon | not now | 18:58 |
| bencoh | rafael2k: if you really need it you could probably add it without enabling the pipewire-pulse service | 18:59 |
| rafael2k | https://webrtc-review.googlesource.com/c/src/+/261620/18 | 18:59 |
| Wizzup | rafael2k: we can package a newer one later if we want | 19:00 |
| bencoh | hmm, interestingly enough, the droid4 does not recognize my noname wallcharger | 19:00 |
| bencoh | whereas (picky) n900 does | 19:00 |
| Wizzup | I think fmg was working on charger patches for the kernel somewhat recently | 19:00 |
| Wizzup | charger detection specifically | 19:00 |
| bencoh | yet same wallcharger was able to power droid4 and make it boot | 19:00 |
| rafael2k | bencoh: lemme see if I manage to make webrtc work in chromium with the version we already have, then if we need a newer version, it should be easy to package indeed | 19:00 |
| bencoh | (with an empty battery) | 19:00 |
| rafael2k | bencoh, and I agree we should not enable pipewire-pulse | 19:01 |
| bencoh | Wizzup: upgraded to 6.1.0-rc8 btw (it's funny that my phone has the most recent kernel of all my devices here) | 19:01 |
| Wizzup | :) | 19:04 |
| bencoh | should dist-upgrade work for beowulf->chimaera? | 19:04 |
| Wizzup | ehhh... potentially :) | 19:05 |
| Wizzup | I did it for my phone | 19:05 |
| bencoh | :] | 19:06 |
| bencoh | any recommendation before running it? | 19:06 |
| bencoh | apart from /etc/no_lg_reboots* | 19:06 |
| Wizzup | full battrery, wifi | 19:07 |
| Wizzup | sry mtg | 19:07 |
| bencoh | let's see ... | 19:07 |
| sicelo | bencoh: you got it wrong ... (picky)droid4 😃 | 19:16 |
| bencoh | haha | 19:19 |
| bencoh | well, n900 was supposedly picky with usb chargers back then | 19:19 |
| Guest5254 | 2 | 20:36 |
| uvos | the mainline kernel on d4 dosent detect any charger at all | 21:30 |
| uvos | ie it dose no charge detection | 21:30 |
| uvos | mbm will only boot if it detects a wall charger, but thats totaly unrelated to the kernel ofc | 21:31 |
| norayr | when connecting to hidden wifi, maemo asks for ssid, not for password. is it normal or bug? | 22:37 |
| norayr | but when i enter something, it doesn't want also a password. | 22:37 |
| norayr | i think it asks for ssid but it treats it as password. | 22:37 |
| norayr | rafael2k: well, it qtwebbrowser doesn't type in pluma or pidgin. and secondly, it doesn't type in armenian. or anything other than latin. | 22:39 |
| uvos | pretty sure the qt keyboard has all kinds of languages | 22:55 |
| uvos | https://doc.qt.io/qt-5/qtvirtualkeyboard-index.html | 22:55 |
| uvos | yes | 22:55 |
| uvos | see Supported Languagessee | 22:55 |
| Wizzup | norayr: it shuld ask both, but ssid first, then it tries to find ap | 23:06 |
| Wizzup | if found it will ask for password | 23:07 |
| Wizzup | you can set it up through cpa sa well | 23:07 |
| Wizzup | uvos: btw I'm close to the tp module for sphone :) | 23:07 |
| uvos | Wizzup: weee | 23:07 |
| norayr | hmm | 23:07 |
| norayr | uvos, wow i didn't know it has. | 23:08 |
| sixwheeledbeast | If Hidden it would need the SSID first | 23:11 |
| bencoh | hmm, is that a known issue (while upgrading to chimaera)? dpkg-divert: error: 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-droid4' clashes with 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-mapphone' | 23:34 |
| bencoh | apparently leste-config-mapphone depends on leste-config-droid4 | 23:34 |
| Wizzup | bencoh: well, it should be fixed, but yeah. | 23:39 |
| Wizzup | bencoh: the ml contains a fix | 23:39 |
| Wizzup | bencoh: try | 23:39 |
| Wizzup | dpkg-divert --remove /lib/udev/rules.d/85-input-devices.rules | 23:39 |
| bencoh | yeah that's what I did | 23:43 |
| Wizzup | bencoh: but yeah I -thought- it was fixed | 23:44 |
| bencoh | and then let it reinstal/reconf the leste-config-droid4 package, and only after that I reinstalled the mapphone one | 23:44 |
| Wizzup | yeah. | 23:44 |
| bencoh | overall the dist-upgrade somewhat failed a few times and I fixed it by running apt --fix-broken install and re-run dist-upgrade, but overall it worked | 23:47 |
| bencoh | deviced rebooted properly to hildon ) | 23:47 |
| bencoh | :) | 23:47 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
