00:07
belcher_ has joined #maemo-leste
00:11
belcher has quit [Ping timeout: 268 seconds]
00:33
belcher_ is now known as belcher
01:00
kdsch has quit [Quit: WeeChat 2.8]
01:20
Pali has quit [Ping timeout: 264 seconds]
01:26
joerg has joined #maemo-leste
01:42
<
sunshavi >
there is a question about 'DM_USB_GADGET' on the list.
02:13
akossh has quit [Quit: Leaving.]
02:32
diejuse has quit [Quit: Leaving.]
04:38
joerg is now known as Guest4354
04:38
Guest4354 has quit [Killed (sodium.libera.chat (Nickname regained by services))]
04:38
joerg has joined #maemo-leste
06:09
<
mighty17[m] >
what browser works in maemo (and pvr)
06:30
Twig has joined #maemo-leste
06:34
Twig has quit [Remote host closed the connection]
07:20
<
sicelo >
Almost any, depending on RAM usage, availability and your needs
07:20
<
sicelo >
E.g. on droid 4, firefox works reasonably okay.
08:08
xmn has quit [Quit: ZZZzzz…]
08:19
xmn has joined #maemo-leste
08:44
<
mighty17[m] >
sicelo: and matrix client?
08:45
<
sicelo >
Same answer :-p
08:46
<
sicelo >
Quarternion, etc.
09:20
<
mighty17[m] >
Nheko doesnt open virtual keyboard :(
09:27
<
Wizzup >
is it qt5? gtk3?
09:33
<
Danct12 >
mighty17[m] on my n900, i use dillo
09:33
<
bencoh >
(dillo <3)
09:33
<
Danct12 >
i kinda want to go with netsurf but i can't find it in beowulf
09:34
<
bencoh >
Yeah, I was about to say it was removed for some reason
09:34
<
Wizzup >
hm, I thought parazyd packaged it
09:34
<
mighty17[m] >
dillo is less resource intensive :D
09:34
<
bencoh >
(either that, or we used to build it from source, but I vaguely recall it was indeed removed)
09:59
uvos has joined #maemo-leste
10:00
xmn has quit [Quit: ZZZzzz…]
10:06
sixkxbeh has joined #maemo-leste
10:06
sixkxbeh has quit [Remote host closed the connection]
10:07
sixkxbeh has joined #maemo-leste
10:09
sixkxbeh has quit [Remote host closed the connection]
10:20
Pali has joined #maemo-leste
10:23
Twig has joined #maemo-leste
10:42
Twig has quit [Remote host closed the connection]
10:46
mrkrisprolls has quit [Ping timeout: 244 seconds]
10:50
<
parazyd >
Wizzup: I packaged surf, not netsurf
10:56
uvos has quit [Ping timeout: 252 seconds]
11:02
<
Wizzup >
parazyd: ah ok
11:10
inky_ has quit [Ping timeout: 252 seconds]
11:13
inky_ has joined #maemo-leste
11:19
<
Wizzup >
parazyd: did you upgrade ke-recv over ssh?
11:23
<
Wizzup >
parazyd: I need your daemon.log info
11:24
<
parazyd >
Wizzup: Yes, I did apt update && apt install ke-recv
11:25
<
parazyd >
The latter does an upgrade of ke-recv only
11:25
<
parazyd >
I'm not at home now so can't access the N900 I did it on atm
11:25
<
Wizzup >
parazyd: do we log warnings in syslog?
11:25
<
parazyd >
What do you need from daemon.log? I pasted already two sprunges when the error happened
11:25
<
parazyd >
syslog and messages
11:25
<
Wizzup >
I mean warning level
11:26
<
parazyd >
I don't know
11:26
<
Wizzup >
ke-recv is
*very* verbose about all the things that make it fail
11:26
<
Wizzup >
and I cannot find any message in syslog
11:26
<
Wizzup >
which is weird
11:26
<
Wizzup >
one of the thoughts was that maybe if you upgrade through ssh, then ke-recv and/or dsme are restarted with wrong/different env vars and that causes problems
11:27
<
Wizzup >
It would be good to check that those log calls actually work I guess
11:27
<
parazyd >
I upgraded both times through ssh
11:27
<
parazyd >
The full upgrade which caused a reboot and only the ke-recv upgrade which didn't cause a reboot
11:28
<
Wizzup >
yes, but the other case it sounded like you only changed ke-recv and no dsme or other stuff
11:28
<
Wizzup >
I really wonder if we want dsme to 'restart' at all during an upgrade
11:28
<
Wizzup >
I don't think Nokia did that a whole lot, if ever
11:29
<
Wizzup >
freemangordon: ^ any thoughts?
11:29
<
parazyd >
IMHO it shouldn't restart at all
11:29
<
parazyd >
uvos and I discussed this
11:29
<
Wizzup >
but it seems to restart currently
11:29
<
parazyd >
Yeah I mean the lifeguard is useless and gives you no freedom to debug
11:29
<
parazyd >
If a service fails
11:29
<
parazyd >
And rebooting is not a solution to "fix" the system
11:30
<
Wizzup >
I don't think we are on the same page at all
11:30
<
Wizzup >
I was saying that debian should not restart dsme upon upgrade
11:30
<
Wizzup >
I was not talking about dsme restarting
11:30
<
Wizzup >
(the system)
11:30
inky_ has quit [Ping timeout: 252 seconds]
11:30
<
parazyd >
This might work with dh_installinit --no-start
11:31
mrkrisprolls has joined #maemo-leste
11:31
<
Wizzup >
if I can make that not happen when upgrading my device, it would help I think
11:31
inky_ has joined #maemo-leste
11:31
<
parazyd >
eh, it already is --no-start, so i guess not
11:32
<
parazyd >
I don't recall dsme being restarted actually
11:32
<
Wizzup >
I am trying to see if I can find that in the logs now
11:32
<
Wizzup >
in any case ke-recv seems very verbose with it's logging, so there should be messages about how it fails for sure
11:33
<
Wizzup >
ah we also stubbed stopping dsme it seems
11:33
<
Wizzup >
stop() { ebegin "Stopping dsme" eend 0
11:34
<
parazyd >
There's also dsme-dbus
11:34
<
Wizzup >
basically everything logs to syslog
11:35
<
Wizzup >
it looks like signal handler failing to install does attempt to log before opening the log
11:35
<
Wizzup >
but that's about it
11:36
<
Wizzup >
I'm wondering how I can debug this when I attempt an upgrade
11:36
<
parazyd >
Jun 17 14:06:27 localhost ke_recv[2130]: ke-recv.c:801: Returned from the main loop
11:37
<
Wizzup >
I think that is from:
11:37
<
Wizzup >
{ g_main_loop_quit(mainloop);
11:37
<
Wizzup >
static void sigterm(int signo)
11:37
<
Wizzup >
g_main_loop_run(mainloop);
11:37
<
Wizzup >
ULOG_DEBUG_L("Returned from the main loop");
11:37
<
parazyd >
But that looks fine, yeah
11:37
<
Wizzup >
but we don't see any messages from ke-recv at all after that
11:37
<
Wizzup >
which is really weird
11:37
<
parazyd >
It just fails from dsme
11:39
<
parazyd >
Does anything happen if you just send a sigterm to ke-recv?
11:40
<
dreamer >
permission*
11:40
<
parazyd >
dreamer: Can I give you admin somehow so you deal with it :)
11:40
<
Wizzup >
parazyd: I can try in a bit, we could also change ke-recv startup policy from -t to -f, which does not cause SW reset if it fails to restart, but that mostly makes sense from a debug pov imho
11:40
<
parazyd >
That could be fine for now
11:41
<
dreamer >
parazyd: hehehehehe. root on the machine hosting the wiki? ;)
11:41
<
Wizzup >
it's a lxc container iirc
11:41
<
dreamer >
same difference
11:41
<
parazyd >
No I mean on the mediawiki
11:41
<
dreamer >
or add me to admin group on the wiki
11:42
<
parazyd >
ok I think I did it
11:42
<
parazyd >
Please have a look
11:42
<
dreamer >
ok, lets see
11:42
<
dreamer >
`Member of groups:Administrators, Autoconfirmed users, Interface administrators, Users` << hopefully good enough yeah :)
11:43
* dreamer
will be poking around some more. probably on some temporary pages to get a feel of how cargo works
11:43
<
Wizzup >
parazyd: I wonder if ke-revc should use DLOG, not ULOG
11:43
<
Wizzup >
#define ULOG_OPEN(X) openlog(X, LOG_PID | LOG_NDELAY, LOG_USER)
11:43
<
Wizzup >
#define DLOG_OPEN(X) openlog(X, LOG_PID | LOG_NDELAY, LOG_DAEMON)
11:43
<
dreamer >
parazyd: have to start by adding a new table before you can query it ;)
11:44
<
dreamer >
anyway, I'll be poking around. don't expect results asap :P
11:44
<
parazyd >
Wizzup: Maybe it makes sense if it runs as root
11:44
<
parazyd >
dreamer: Sure
11:44
<
Wizzup >
parazyd: I think it also determines where the log messages go
11:44
<
Wizzup >
let me booy my droid and poke around
11:45
<
parazyd >
I think syslog is a concatenation of everything
11:45
* Wizzup
doesn't think so
11:45
<
Wizzup >
but I have to check :)
11:45
<
parazyd >
I'm not sure, but something in my mind tells me that it is :D
11:45
<
parazyd >
Either syslog or messages, don't remember
11:45
<
Wizzup >
messages is just kernel
11:45
<
Wizzup >
syslog I think is not everything either
11:46
<
Wizzup >
I will check
11:49
diejuse has joined #maemo-leste
11:51
<
Wizzup >
parazyd: daemon.log is not the same as syslog
11:54
<
Wizzup >
parazyd: ke-recv messages end up in /var/log/user.log lol
11:54
<
parazyd >
ah obviously
11:54
<
parazyd >
Yeah I didn't even think of checking it
11:54
<
Wizzup >
see /etc/rsyslog.conf
11:54
<
parazyd >
I'll have a look when I have my N900 again
11:54
<
parazyd >
But if you can make the upgrade, you should repro it too
11:56
<
Wizzup >
yeah I understand
11:56
<
Wizzup >
trying to check some other stuff first
11:57
<
Wizzup >
it looks like our rsyslog does not log CRIT to messages at least
11:57
<
Wizzup >
but it does log WARN
12:05
<
buZz >
hmm , apt upgrade just ended with 'Hangup'
12:05
<
buZz >
what a weird msg :P
12:06
cockroach has joined #maemo-leste
12:07
<
Wizzup >
buZz: hm, any idea what happened?
12:08
<
buZz >
it was building initrd at the time, it seemed
12:09
<
buZz >
it somehow destroyed wifi i think :(
12:09
<
Wizzup >
on the d4, or what?
12:09
<
Wizzup >
dpkg-reconfigure ?
12:10
<
buZz >
i'll try, just doing another reboot now to be sure
12:11
<
Wizzup >
full system upgrades are difficult, there's a reason nokia only did a few and locked down the system + reboot once it was done :p
12:11
<
buZz >
oh , i remember it updated mce in this upgrade
12:11
<
buZz >
and it failed to shutdown mce
12:11
inky_ has quit [Ping timeout: 252 seconds]
12:13
<
buZz >
what should i dpkg-reconfigure ?
12:13
<
buZz >
what package i mean
12:13
<
buZz >
i tried 'mce' but doesnt seem able to configure it
12:13
<
Wizzup >
well maybe that's too much
12:13
<
Wizzup >
just whatever people do when apt is interrupted
12:13
<
Wizzup >
apt-get install -f?
12:13
* Wizzup
's memory is hazy atm
12:14
<
buZz >
yeah thats not the issue i think? hmm
12:15
<
buZz >
dpkg-reconfigure linux-image-droid4 now
12:18
<
buZz >
meh, keeps giving 'no connections available'
12:18
<
buZz >
i'm considering just wiping SD and reinstalling ;)
12:18
<
buZz >
or someone maybe has a good idea? :P
12:18
<
Wizzup >
are you on -devel
12:19
<
Wizzup >
parazyd: btw I did apt upgrade just now and didn't get that problem
12:19
<
buZz >
i had a 24 package update
12:19
<
Wizzup >
buZz: dpkg -l | grep suppli
12:19
<
Wizzup >
I wonder what the two versions are
12:20
<
Wizzup >
for wpa supplicant and the licdicd-network-wpasupplicant
12:20
<
buZz >
wpa supplicant is 2.9.0-21+2m7.1
12:20
<
buZz >
libicd-net-wpas is 0.1.7+2m7
12:21
<
buZz >
wpa supplicant is 2:2.9.0-21+2m7.1
12:21
<
Wizzup >
that should work, at least that part of the stack
12:21
<
buZz >
anything else you'd like me to try?
12:21
<
Wizzup >
does wpa_cli work?
12:21
<
Wizzup >
'scan', 'scan_results', etc
12:22
<
Wizzup >
do you see networks?
12:22
<
buZz >
yep, all the same as normal
12:22
<
Wizzup >
ok, but not from ui?
12:22
<
Wizzup >
is icd2 running?
12:23
<
Wizzup >
pidof icd2
12:23
inky_ has joined #maemo-leste
12:23
<
buZz >
'/usr/sbin/icd2 -l2'
12:23
<
Wizzup >
and apt reports nothing else to fix/do?
12:23
<
buZz >
as far as apt is concerned , everything is ok, it seems
12:24
<
buZz >
apt -f install doesnt want to execute anything
12:24
<
Wizzup >
can you reconfigure icd2 and those other packages?
12:24
<
buZz >
mayyybe, lets see
12:26
<
parazyd >
Wizzup: hmm ok
12:27
<
buZz >
i have linux-image-droid4 5.11.2 installed
12:27
<
buZz >
but uname -a tells me i'm running 5.11.22
12:27
<
parazyd >
uname != package version
12:27
<
buZz >
oh right, ok
12:27
<
bencoh >
that's pretty confusing thoug
12:27
<
Wizzup >
parazyd: random q, how can I enter charging mode from kexecboot on d4? I don't see the menu entry
12:27
<
parazyd >
Yeah, I'm thinking of setting it up to always keep the pkg version at 5.11.0
12:27
<
parazyd >
Debian does it this way too
12:27
xmn has joined #maemo-leste
12:28
<
buZz >
i've dpkg-reconfigure'd everything with networking in my last apt upgrade
12:28
<
bencoh >
yeah, but that's confusing as well tbh
12:28
<
buZz >
but nope, nothing changed
12:28
<
parazyd >
Wizzup: We didn't push that update yet
12:28
<
Wizzup >
parazyd: to -devel ? ok
12:28
<
Wizzup >
and emergency shell should work, right?
12:28
<
parazyd >
You can put softlevel=charge-mode in boot.cfg cmdline after you install charge-mode
12:28
<
Wizzup >
I'm booting it now for the first time :)
12:28
<
Wizzup >
I think it's booting normally though
12:29
<
Wizzup >
maybe I don't know how to use kexecboot keys :D
12:29
<
parazyd >
Well, you'll still see a tty
12:29
<
Wizzup >
I see X and everything, h-d
12:29
<
parazyd >
ah then it passed through
12:29
<
parazyd >
uvos said this happens sometimes
12:29
<
Wizzup >
in any case nvm for now, I'm not too interested in it atm
12:30
<
parazyd >
And ofc you need to be charging for it to actually show up
12:30
<
parazyd >
But he said sometimes the current draw is too high(?) so it skips
12:30
<
parazyd >
Only a mapphone problem
12:34
<
bencoh >
firefox suggests to download it, instead of displaying the page
12:40
<
Wizzup >
seems like missing index.html default or some
12:41
<
parazyd >
misconfig
12:41
Guest68 has joined #maemo-leste
12:43
<
parazyd >
bencoh: Try now
12:44
<
bencoh >
yay, works! thanks :)
12:44
<
bencoh >
it's lovely and pretty useful, by the way
12:44
<
bencoh >
did you reuse code from the devuan infra?
12:45
<
bencoh >
(oh and, you might want to display the package arch in the listing)
12:47
<
parazyd >
The architecture is in the URL
12:47
<
parazyd >
And if you open a package's page you also see it listed
12:48
<
parazyd >
I wrote the search in a very barebones, filesystem-as-db way though
12:49
<
parazyd >
So it's not the fastest thing, but it does the trick
12:49
<
bencoh >
(and I yeah, I was only referring to the listing itself, regarding the arch)
12:51
Guest68 has quit [Quit: Client closed]
13:18
<
buZz >
so no ideas how i can get icd2 working again? :P then i'll just reinstall from scratch, nothing unique on my install atm
13:18
<
bencoh >
did you try purging/reinstalling?
13:20
<
buZz >
which packages? the libicd- one ?
13:20
<
buZz >
wpa_cli is working fine , btw
13:20
<
bencoh >
err, actually I dont know which of those package hosts the config files
13:21
<
buZz >
i bet icd2-settings-default and icd2-network-wpasupplicant-config
13:21
<
buZz >
1.11+2m7 and 0.1.7+2m7 , are the ones i have
13:22
<
bencoh >
ah, you're on devel
13:42
<
Wizzup >
parazyd: so the provider will create a second entry in the UI for every network it maches
13:42
<
Wizzup >
parazyd: this gets messy quickly with lots of wifi APs
13:43
<
Wizzup >
since you now get double the amount of connections
13:43
_uvos_ has joined #maemo-leste
13:45
kdsch has joined #maemo-leste
13:46
<
_uvos_ >
Wizzup: so on mapphones the charging state in sysfs is set by the kernel simply to "charging" or not depending on current_now. ofc that is very noizy so this value flickers back and fourth all the time. some times when charging_mode reads the state it will happen to chance upon the value while it not charging and simply boot to desktop
13:47
<
_uvos_ >
we can either fix this somehow, or enter charing mode depending on usb connected state instead of charging state or both
13:49
_uvos_ has quit [Quit: _uvos_]
14:33
<
parazyd >
Wizzup: ok
14:33
<
parazyd >
Does this apply to existing networks that have a saved connection, or it comes up on scan for all of them?
14:34
<
parazyd >
In any case, we could add some state and tweak connui
14:55
<
Wizzup >
parazyd: all of them
15:19
<
parazyd >
Wizzup: So could the code be modified/copied to work like one-for-all networks
15:23
kdsch has quit [Ping timeout: 252 seconds]
15:24
<
parazyd >
Perhaps modifying is better since nothing else ever used this code
15:24
kdsch has joined #maemo-leste
15:27
<
parazyd >
I suppose the way it works now is allowing you to set a provider per-network
15:28
<
parazyd >
Perhaps there is just a way to have it show up when you're connected to a network
15:28
<
parazyd >
That sounds ideal
15:28
<
parazyd >
And could be a simple connui tweak
16:52
xmn has quit [Quit: xmn]
17:01
xmn has joined #maemo-leste
17:33
inky_ has quit [Ping timeout: 258 seconds]
17:34
inky_ has joined #maemo-leste
17:38
<
Wizzup >
maybe it could be a dialog + pref
17:53
<
buZz >
dbus starts with 'unknown username 'geoclue''
17:54
<
buZz >
on 6-20 image on droid4
17:54
<
buZz >
dont think its anything serious , seems to boot fine
17:55
<
buZz >
at least wifi works now \o
17:56
<
buZz >
the new font on the theming is nice!
18:15
inky_ has quit [Read error: Connection reset by peer]
18:15
inky_ has joined #maemo-leste
18:23
michiel__ has quit [Remote host closed the connection]
18:23
michiel__ has joined #maemo-leste
18:51
inky_ has quit [Ping timeout: 265 seconds]
18:52
inky_ has joined #maemo-leste
19:02
<
freemangordon >
Pali: well, at least Tom looks like a sane guy
19:28
<
sicelo >
parazyd: by the way, I have permanent Location button on my status menu. Not sure if that's expected
19:29
<
freemangordon >
I guess not
19:33
<
parazyd >
Yeah it shows always, but it's easy to hide it
19:34
<
parazyd >
We can do that if it's necessary
19:36
<
freemangordon >
parazyd: well, in fremantle that button is only visible when there is active GPS session
19:36
<
sicelo >
I'm not used to seeing it all the time, so yes :-)
19:37
<
parazyd >
I'll add that
19:37
<
freemangordon >
parazyd: lots of status menu items are like that, which kinda makes sense, otherwise status menu will easily get crowded
19:38
<
parazyd >
freemangordon: Yeah, makes sense.
19:45
inky_ has quit [Read error: Connection reset by peer]
19:48
inky_ has joined #maemo-leste
19:56
cockroach has quit [Quit: leaving]
21:14
Pali has quit [Quit: Pali]
21:38
Pali has joined #maemo-leste
22:42
xes has joined #maemo-leste
22:49
xes has quit [Quit: WeeChat 3.0.1]
22:54
xes has joined #maemo-leste
23:04
kdsch has quit [Quit: WeeChat 2.8]
23:10
kdsch has joined #maemo-leste
23:19
l_bratch has quit [Ping timeout: 240 seconds]
23:31
l_bratch has joined #maemo-leste
23:35
Pali has quit [Ping timeout: 265 seconds]
23:41
kdsch has quit [Quit: WeeChat 2.8]