ikmaak has quit [Ping timeout: 276 seconds]
Pali has quit [Ping timeout: 250 seconds]
ikmaak has joined #maemo-leste
Danct12 has quit [Quit: Quitting]
mrtux8 has joined #maemo-leste
mrtux has quit [Ping timeout: 248 seconds]
mrtux8 is now known as mrtux
joerg is now known as Guest3997
Guest3997 has quit [Killed (copper.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
macros_2ndPC has quit [Ping timeout: 240 seconds]
macros_2ndPC has joined #maemo-leste
vagag has joined #maemo-leste
Danct12 has joined #maemo-leste
<freemangordon> buZz: yes, conversations still lack los of things
<freemangordon> *lots
<freemangordon> in addressbook, stuff works, but you need your account to be online
<freemangordon> do you have any account set up?
ceene has joined #maemo-leste
Twig has joined #maemo-leste
vagag has left #maemo-leste [#maemo-leste]
Daanct12 has joined #maemo-leste
mardy has joined #maemo-leste
<buZz> account??
<buZz> for what?
<freemangordon> umm...
<freemangordon> like google-talk, or irc, or...
<freemangordon> whom do you want to chat to?
<freemangordon> a conversation need "from" and "to" parties, no?
<freemangordon> *needs
<buZz> eh?
<buZz> oh
<buZz> i'm using it for SMS
<buZz> didnt know it did anything else
<buZz> i wish i could copy details from addressbook to actually use
<buZz> or tap on a number for calling or sending a txt
ceene has quit [Ping timeout: 240 seconds]
<freemangordon> tapping on number fro sms should work
<freemangordon> but it needs /ring/tel/account0 telepathy account to be created
<freemangordon> don't know if conversations registers itself with telepathy though, Wizzup knows better
uvos has joined #maemo-leste
<freemangordon> sicelo: a side question - do you know if there is a chance to enable tls1.2 on fremantle?
<Wizzup> morning
<freemangordon> hi!
<freemangordon> Wizzup: the same question to you
uvos has quit [Ping timeout: 248 seconds]
Daanct12 has quit [Quit: Leaving]
<sicelo> freemangordon: i think jonwil tried at some point. while he had some success, overall it was an uphill climb
<sicelo> He was focusing mostly on tls1.2 for microb
<sicelo> Why you ask though?
<buZz> freemangordon: it doesnt work anyway :P
<buZz> and not really any clue how telepathy should work :P
<buZz> or works
<sicelo> it works via telepathy :-p
<sicelo> Dictionary definition
<Wizzup> freemangordon: no idea @ fremantle, I think I just want to move to leste asap
<Wizzup> buZz: conversations in repo is read-only for the db atm
<Wizzup> buZz: I'm going to continue work on it basically now with dsc__
<freemangordon> Wizzup: yea, but I have to connect to outlook.office.365 from my n900 fremantle :)
<freemangordon> will try to setup mtimproxy
<buZz> Wizzup: ah yeah, couldnt send SMS from it, worked with the sphone sms sender though
<Wizzup> yes
<Wizzup> freemangordon: there is a way to do this
<Wizzup> freemangordon: what protocol is it
<freemangordon> https I guess
<Wizzup> you can run a local proxy written in a static language, say go, that sends it on
<freemangordon> yeah
<Wizzup> I have done this in the past and can try to dig it up
<freemangordon> please do
<Wizzup> ok
<freemangordon> but, I am not sure modest supports proxy
<Wizzup> you don't use proxy
<Wizzup> you just point it at localhost
<freemangordon> so it must be transparent ssl proxy, somehow
<freemangordon> ah, ok
<Wizzup> i'd be like ./go-proxy-thing -remote outlook.office.365 -local localhost:7777
<Wizzup> or w/e
<freemangordon> yeah
<Wizzup> (searching)
<freemangordon> thanks
<sicelo> freemangordon: activesync?
<freemangordon> mhm
<sicelo> or imap?
<freemangordon> activesync
<buZz> is there somewhere a list what telegraphy can support as transports?
<buZz> telepathy
<buZz> i mean, not all that 'ever' worked, but what currently works ;)
<freemangordon> gtalk for sure
<buZz> thats xmpp right?
<freemangordon> mhm
<buZz> actually cant even remember if i ever used gtalk :P is that the phonecalls one aswell?
<freemangordon> telepathy-gabble
<freemangordon> yeah, but google removed voice/video support
<Wizzup> freemangordon: ok let me test this
<buZz> ah
<buZz> telepathy-gabble is a connection manager for the XMPP (Jabber) protocol. It uses Wocky for implementing the XMPP protocol and Telepathy GLib for implementing the Telepathy D-Bus API.
<freemangordon> Wizzup: thanks
<sicelo> Yes gabble is xmpp
<freemangordon> buZz: you need telepathy-ring as well
<freemangordon> (for sms/phone)
<buZz> i have functioning sms already
<Wizzup> freemangordon: what is the host, outlook.office.365 is not right
<buZz> at least, they arrive in conversations
<Wizzup> outlook.office:365
<Wizzup> ?
<freemangordon> Wizzup: outlook.office365.com
<Wizzup> port ?
<freemangordon> 443
<sicelo> I am afraid tls might be less of your problem. Unless you're lucky your admins haven't set the base activesync policy too high.
<freemangordon> sicelo: admin is my friend
<freemangordon> :)
<freemangordon> so my device is allowed
<sicelo> Or lucky you :-)
<freemangordon> it is just that recently server just resuses tls1.0
<freemangordon> *refuses
Pali has joined #maemo-leste
<freemangordon> as soon as it sees tls1 client hello, it drops the connection
<Wizzup> hm, ok, well, my proxy solution might work, but if the server does weird https redirects it might not work
<Wizzup> (to other hosts etc)
<sicelo> Wizzup's proxy thing should work then. Also halftux has similar using nginx (documented on tmo)
<freemangordon> I hope it does not
<freemangordon> is that some kind of reverse proxy?
<Wizzup> build with GOOS=linux GOARCH=arm go build proxy.go
<Wizzup> yes, you tell it what host to forward local connections to
<freemangordon> umm, where to build?
<Wizzup> sudo ./proxy -remote outlook.office365.com:443 -local 127.0.0.1:80
<Wizzup> should work on ubuntu
<Wizzup> I can also build it for you
<freemangordon> ok, lemme try
<freemangordon> no, my ubuntu is old, lets try on it
<Wizzup> you should get static executable
<freemangordon> ok
<Wizzup> iirc I had some problems with it not finding the certs on the n900
<Wizzup> but that we'll see later
<freemangordon> mhm
<Wizzup> (you could tell it not to verify, but yikes)
<freemangordon> afaik there is a difference in hashes between 0.9.8 and 1.x
<Wizzup> not just that but you might lack newer certs too
<freemangordon> no, certs are fine
<freemangordon> I was able to connect till a week or so ago
<sicelo> For the sake of logs, the nginx way: https://talk.maemo.org/showpost.php?p=1566371&postcount=68
<Wizzup> yeah the nginx way might be more solid
<Wizzup> oh I remember, I made an irc bot in go and ran it on fremantle
<freemangordon> lemme try the proxy first
<freemangordon> Wizzup: x86_64-linux-gnu-gccgo-8: error: unrecognized command line option ‘-marm’; did you mean ‘-mabm’?
<freemangordon> this is in leste VM
<freemangordon> lemme try something
<Wizzup> hm I don't have this problem on gentoo
<Wizzup> I don't use gccgo for what it's worth
<freemangordon> but what?
<Wizzup> the default should just be go or golang
<Wizzup> let me check
<freemangordon> oh, golang maybe
<Wizzup> I have to start my d4 because it keeps powering off
<freemangordon> yeah, lemme try
<freemangordon> with golangf
<Wizzup> so is this for email or something else
<freemangordon> yes
<freemangordon> email
<freemangordon> and calendar etc
<Wizzup> ok
<freemangordon> success with golang
<Wizzup> ok, let's hope it actually works for your purposes too
<Wizzup> it has a -verbose flag too
<freemangordon> let me see if it will work on n900
<freemangordon> getting there :)
<freemangordon> 2022/04/29 12:06:00 Backend error: x509: certificate signed by unknown authority
<Wizzup> hm
<Wizzup> yeah so it can't find the certs I guess
<freemangordon> mhm
<Wizzup> you could disable verification
<Wizzup> (as a test)
<freemangordon> lemme try nginx first
<Wizzup> ok
<Wizzup> but nginx way requires a proxy
<Wizzup> so you need to make sure that works I guess
<freemangordon> ah, right
<freemangordon> I have no idea about go, how to disable verification?
<Wizzup> sec
<Wizzup> I do I think
<Wizzup> it's just a tls.config{} thing
<Wizzup> &tls.Config{InsecureSkipVerify: true}
<Wizzup> try that
<Wizzup> if it requires specific host names in the requests we might need to add that
<Wizzup> honestly I just hope it works for your use case and we can forget about it :p
<freemangordon> mhm
<Wizzup> one problem is that this just strips the tls layer, so you still need to make sure you provide the server with a host it knows
<Wizzup> i.e. wget -O - http://localhost:someport will pass 'localhost' to the remote ip
<Wizzup> there's probably something clever that can be done but I haven't tried
<Wizzup> we mostly used this as $previousjob because the windows machines couldn't do proper tls
<Wizzup> this at*
<r3boot> -H 'Host: some.virtual.host'
<freemangordon> ./asredirect.go:76:17: &tls.Config literal evaluated but not used
<Wizzup> freemangordon: r, err := tls.DialWithDialer(&net.Dialer{Timeout: *timeout}, "tcp", *remote, &tls.Config{InsecureSkipVerify: true})
<freemangordon> ah, ok :)
<Wizzup> r3boot: right, but this is some pos software for outlook
<Wizzup> ;)
<Wizzup> (I think)
freemangordon has quit [Quit: Leaving.]
<r3boot> Oh, check :)
<Wizzup> as in, I think so
<Wizzup> maybe it's some exchange thing
freemangordon has joined #maemo-leste
<Wizzup> freemangordon: welcome back
<freemangordon> gnome crashed :D
<freemangordon> lemme see if VM fs is corrupted
Twig has quit [Ping timeout: 276 seconds]
<sicelo> nginx requires what proxy? It's a proxy itself
vagag has joined #maemo-leste
<freemangordon> Wizzup: getting "invalid username or password", getting there it seems
<Wizzup> mhm
<Wizzup> sicelo: that's the point, it only works if the software can use a proxy (nginx)
<sicelo> Ok. If the proxy is set system wide, should work for modest too. But maybe I'm missing something:-)
<Wizzup> right, potentially
pere has quit [Ping timeout: 256 seconds]
<freemangordon> Wizzup: will this proxy accept ssl connections?
<freemangordon> or I shall enabled that somehow?
<freemangordon> *enable
<Wizzup> ssl 3.0?
<Wizzup> freemangordon: no only plain
<freemangordon> tls1.0
<Wizzup> if you want tls1.0 to tls1.2 it gets more tricky I think
<Wizzup> then you'll need to make a cert, and install the ca of that cert in the n900 trusted store
<freemangordon> I will add self-signed cert, no problem
<Wizzup> ok I will need to look at the go code and figure out how to do that again
<Wizzup> it's not too hard
<freemangordon> lemme first try to go through hosts file
<Wizzup> that might be hard since it will also affect go
<Wizzup> but you can try
<freemangordon> to have the real url in the http request
<freemangordon> oh, right
<freemangordon> grrr
<Wizzup> you can use the ip in go, but it might get weird with hosts again
<freemangordon> yeah
<freemangordon> lemme try ip
<Wizzup> it might fail to validate the remote
<freemangordon> it fails either ways :)
<freemangordon> I am still getting 401
<Wizzup> weird
<Wizzup> what reports 401? modest?
<freemangordon> outlook
<Wizzup> it could be that you get 401 because the server doesn't know what host you want to connect to
<Wizzup> and it thus picks the wrong host
<Wizzup> for which your user is not valid
<freemangordon> it is there
<Wizzup> this could become a very deep rabbit hole
<freemangordon> Host: outlook.office365.com
<Wizzup> ok
<freemangordon> but I suspect the issue comes from:
<freemangordon> request URI starting with HTTP://
<freemangordon> instead of HTTPS://
<freemangordon> lemme try https proxy
<Wizzup> uvos: maybe 'kernel panic with v5.18-rc1 on OpenPandora' is related to the wifi regression you saw
ceene has joined #maemo-leste
<mighty17[m]> on 0.14.1
<freemangordon> seems that as-daemon supports proxy
<tmlind> mighty17[m]: no, i've only been testing what the commit is based on as things have been changing, the most recent one is https://github.com/tmlind/wlroots/tree/missing-unpack-subimage
<Wizzup> freemangordon: shall I build gabble for non-devel
<freemangordon> yes
<Wizzup> ok
<Wizzup> freemangordon: btw I made tools to more easily diff the repos
<Wizzup> freemangordon: you can try like
<Wizzup> python3 repodiff.py beowulf-devel beowulf -t missing -f source
<Wizzup> or
<Wizzup> python3 repodiff.py beowulf-devel beowulf -t newer -f source
<freemangordon> Wizzup: yes, I saw it
<freemangordon> but kinda ignored it as I was focused on presence-ui :)
<Wizzup> ok
<mighty17[m]> <tmlind> "mighty17: no, i've only been..." <- It's the same commit, but it doesn't work with phosh on 0.14.1 wlroots
<tmlind> mighty17[m]: you need to use mesa and the blobs from m-l repos with wlroots
<tmlind> and then you need the mesa patch for "egl/dri2: Workaround for EGL_EXT_image_dma_buf_import_modifiers version check"
<tmlind> the link for that should be in the irc logs for file 0001-egl-dri2-Workaround-for-EGL_EXT_image_dma_buf_import.patch
<tmlind> not sure if wlroots 0.14.1 behaves the same as current devel version, but yeah just one wlroots and one mesa patch should be currently needed
<mighty17[m]> Already using mesa from fmg/m-l I'll look into the logs
<mighty17[m]> It was working fine with 0.12 wlroots btw
<Wizzup> ok, most packages are not synced from -devel to stable (apart from the -devel ones like sphone, conversations, all the pulse stuff, etc)
<Wizzup> are now*
<Wizzup> ah I think my d4 had a loose battery contact
noidea_ has joined #maemo-leste
ceene has quit [Remote host closed the connection]
uvos has joined #maemo-leste
<uvos> freemangordon: so dose mce work when autolock is set via gconf with the old cp applets?
<Wizzup> ok yeah the battery contact problem seems fixed
<freemangordon> uvos: yes
<freemangordon> uvos: umm, you mean latest?
<freemangordon> unless you have fixed something, it does not
<uvos> yeah i updated mce yesterday
<freemangordon> ah. sorry, I have to run now, will be mia for the weekend, will test on Sunday
<uvos> i dont use gconf and i dont use the old cp applets so i cant trest it easily
<uvos> but fix was pretty trivial
<freemangordon> I guess sicelo can test
<freemangordon> or somebody else
<freemangordon> sorry, have to run, ttyl
vagag has left #maemo-leste [Error from remote client]
pere has joined #maemo-leste
vagag has joined #maemo-leste
* enyc meows
uvos has quit [Read error: Connection reset by peer]
uvos has joined #maemo-leste
<uvos> freemangordon: some more info on why abadoning osso_service for xterm would be totaly fine:
<uvos> so according to https://github.com/pixelb/ps_mem which devides shared memory by processes that use them a xterm process uses ~ 4.9MiB ram when launched with maemo-launcher and 5.4MiB without
<uvos> so you could have 150 xterms open on d4 and have enough ram to spare for everything else
<uvos> thats reason 1
<uvos> reason 2
<uvos> xterm when launched via its binary allready uses dbus to open a new window instead of spawing a new process, this is how all normal linux signelton applications do this, and is implemented by glib or legacy gnome libunique, (well xterm implemts this by hand but that dosent really matter)
<uvos> this also goes to show that maemo-launcher is a waste of time that makes it harder to package mameo stuff for other distros for no reason
<uvos> since it 1. saves almos no time over just having the libs in page cache, something you can easly achive with systemd-readahead for any lib you want not just the ones launcher uses
<uvos> 2. saves on about 500KB ram per process
<uvos> 3. relies on internal implementation details of the "boosted" libs that would be a huge maintiance burden
<uvos> if boost modules existed for libs that are actively developed
<uvos> 500KB per process for on the order of 10-20 processies is nigh irrelivant
<uvos> on d4
<uvos> and you have to remember
<uvos> d4 is crushingly obsolete
<uvos> it cant even really connect to mobile data anymore
<uvos> any phone any normal user is ever going to want to use is going to be even less resource constrained
<uvos> anyhow theres no good excuse to say "resource constrained" to stop people from having more than one pdf open
<uvos> and so on
<uvos> it just dosent make sense anymore
<uvos> and maemo-launcher feals like a rather desperate hack to get the rather bloated (relative to android from the same time period) maemo 5 to just about fit into the n900s smallish (even for the time) memory
uvos has quit [Quit: Konversation terminated!]
noidea_ has quit [Ping timeout: 240 seconds]
Livio has joined #maemo-leste
Livio has quit [Client Quit]
Livio has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
<tmlind> yeah that dbus crap did not make sense back then either
crab has quit [Quit: WeeChat 3.5]
crab has joined #maemo-leste
Livio has quit [Quit: I'm gone away.]
akossh has joined #maemo-leste
uvos has joined #maemo-leste
<uvos> tmlind: btw since shuting down the modem in kexecboot, i have had no boot failures, not even the random boot failuers i used to get without the evil sim
<uvos> suggesting these are a related, probubly a race that the sim affects the timeing of
<uvos> waiting 3 or so seconds for the modem to shut down is a bit annoying tho
<uvos> im going to investigate if i can just nix the regulator and kexec immidiatly later
vagag has left #maemo-leste [Disconnected: Replaced by new connection]
vagag has joined #maemo-leste
pere has quit [Ping timeout: 240 seconds]
akossh has quit [Quit: Leaving.]
sunshavi has quit [Ping timeout: 276 seconds]
sunshavi has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
pere has joined #maemo-leste
noidea_ has joined #maemo-leste
vectis_ has quit [Ping timeout: 240 seconds]
norayr has joined #maemo-leste
vectis_ has joined #maemo-leste
uvos has quit [Ping timeout: 246 seconds]
<buZz> meh, it worked so well
<buZz> now every time i do 'connect to 2G' i get connectionfailed
<buZz> until i reboot, then -maybe- it can connect once , ~10 minutes after booting (why not directly?) , but -usually- not even a single time
<buZz> just reboot reboot reboot , 10mins each, and -maybe- get a connection eventually
<buZz> :(