elastic_1 has joined #maemo-leste
elastic_dog is now known as Guest497
elastic_1 is now known as elastic_dog
_whitelogger has joined #maemo-leste
macros_ has quit [Ping timeout: 248 seconds]
macros_ has joined #maemo-leste
joerg has quit [Ping timeout: 255 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 252 seconds]
macros_ has joined #maemo-leste
maemish_ has joined #maemo-leste
Daaanct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 248 seconds]
ceene has joined #maemo-leste
<freemangordon> uvos__: yes, numbers
maemish_ has quit [Quit: Connection closed for inactivity]
xmn has quit [Quit: ZZZzzz…]
tsaebdeleehwxis is now known as sixwheeledbeast
uvos has joined #maemo-leste
akossh has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
akossh has quit [Ping timeout: 252 seconds]
sunshavi_ has joined #maemo-leste
sunshavi has quit [Ping timeout: 265 seconds]
akossh has joined #maemo-leste
uvos has quit [Remote host closed the connection]
pere has quit [Ping timeout: 255 seconds]
pere has joined #maemo-leste
xmn has joined #maemo-leste
<Wizzup> for chimaera, what else do we want to do before we announce it 'officially' ?
<Wizzup> there's some bug/crash fixes (maep comes to mind), some regressions (syncevo), and some quality of life improvements like swap by default on n900, and making the modem load properly automatically on the n900
<Wizzup> I think chimaera wise, really only maep and syncevo are the ones related to chimaera?
<buZz> i'm still not sure the chimaera issues i see are repeatable by anyone else
<Wizzup> buZz: which?
<buZz> like ; OTG not working, wireguard statusmenu item disappeared, jabber wont connect
<buZz> oh the 'rotation lock' statusmenu also disappeared
<Wizzup> I can try these
<buZz> if you could, i'd be grateful :)
<sixwheeledbeast> jabber.org cert expired recently if that helps... may not be related.
macros_2ndPC has joined #maemo-leste
macros_ has quit [Ping timeout: 248 seconds]
<buZz> sixwheeledbeast: no i'm using a private server instance
<Wizzup> buZz: when you mean otg, you mean having the phone act as host?
<buZz> yes
<Wizzup> not sure if I can test that rn
<Wizzup> wireguard menu is there for me, where does it disappear for yo
<Wizzup> you*
<buZz> its completely missing perhaps, i can look later
<buZz> gotta get going preparing dinner :)
<Wizzup> so
<Wizzup> is status menu hard crashes
<Wizzup> it will load with only stable plugins
<Wizzup> s/is status/if status/
<Wizzup> you might be seeing this
<Wizzup> buZz: hmm
<Wizzup> buZz: can you run this: GABBLE_PERSIST=1 GABBLE_DEBUG=all /usr/lib/telepathy/telepathy-gabble
<Wizzup> and then reconnect with mc-tool or some other way
<buZz> oh that might be something? how can i call all plugins 'stable' again?
<Wizzup> kill status
<Wizzup> pkill status
<Wizzup> hm, actually that somehow doesn't give me debug output
<Wizzup> hang on, probably need this G_MESSAGES_DEBUG or something
<Wizzup> G_MESSAGES_DEBUG=all WOCKY_DEBUG=debug GABBLE_PERSIST=1 GABBLE_DEBUG=debug /usr/lib/telepathy/telepathy-gabble
<Wizzup> ironically if I run this, it just works for me, but if I don't run it manually, it seems to not work
<buZz> ah, so you can repeat my jabber issues?
<buZz> reproduce*
<buZz> ahhhh afk, bbl
<Wizzup> buZz: not sure yet
<Wizzup> it looks like telepathy-gabble crashes, maybe it cannot access the dbus session
<Wizzup> could be elogind related
<Wizzup> -maybe-
<Wizzup> string "ConnectionErrorDetails"
<Wizzup> variant array [
<Wizzup> string "debug-message"
<Wizzup> variant string "Name owner lost (service crashed?)"
<Wizzup> dict entry(
<Wizzup> )
<Wizzup> freemangordon: how is telepathy-gabble started, by dbus, or mission control?
ceene has quit [Ping timeout: 268 seconds]
Daaanct12 has quit [Remote host closed the connection]
Daaanct12 has joined #maemo-leste
Daaanct12 has quit [Remote host closed the connection]
Daaanct12 has joined #maemo-leste
Daaanct12 is now known as Danct12
<freemangordon> Wizzup: I think dbus
<freemangordon> and yes, if it uses wring session bus it will not work
<freemangordon> but, it is started on behalf of user, so not sure what the issue might be
<freemangordon> maybe check in syslog
<freemangordon> could be some selinux issue
<Wizzup> freemangordon: wring?
<Wizzup> oh wrong
<freemangordon> yeah, apparmor: https://pastebin.com/vbD8yifC
<Wizzup> huh
<freemangordon> Wizzup: https://pastebin.com/B54bXuTi
<Wizzup> so, debian aa profiles are not ok?
<freemangordon> looks like, dunno
<freemangordon> I am not really hte one to ask about aa and such
<Wizzup> ok, will dive into this in a bit
<freemangordon> :)
<freemangordon> Wizzup: seems we'll have to adjust the profiles
<freemangordon> usr.lib.telepathy
<freemangordon> hmm, all complains are for telepathy-haze
<freemangordon> Wizzup: I cannot install dh_python
<freemangordon> it wants to remove python-is-python2
<freemangordon> which hildon-meta depends on
<freemangordon> any idea what is this?
<freemangordon> ugh, how do we manage to build that?
<freemangordon> *that* is telepathy-gabble
<Wizzup> freemangordon: yes, this is a debian problem
<Wizzup> freemangordon: you need dh_python from backports
<freemangordon> ah, ok
<Wizzup> not sure why they can't just promote it
<freemangordon> Wizzup: didn't help
<Wizzup> we do this in CI
<Wizzup> just a sec, let me try
* Wizzup starts up vm
<freemangordon> in backports there is no dh_python2
<Wizzup> freemangordon: what dh-python do you have
<Wizzup> ii dh-python 5.20220215~bpo11+1 all Debian helper tools for packaging Python libraries and applications
<Wizzup> $ dpkg -S /usr/bin/dh_python2
<Wizzup> dh-python: /usr/bin/dh_python2
<freemangordon> 5.20230130~bpo11+1
<freemangordon> they have removed it it seems
<freemangordon> E: Version '5.20220215~bpo11+1' for 'dh-python' was not found
<Wizzup> what
<freemangordon> installing version from chimaera repon and ignoring python-is-python2 dependency in control file allows me to build it
<freemangordon> argh
<freemangordon> make[3]: *** No rule to make target 'telepathy-gabble.systemd.in', needed by 'telepathy-gabble.service'. Stop.
<Wizzup> I'm rebuilding gabble on the CI to see what happens
<freemangordon> ok
<Wizzup> yeah, it's gone from the new version
<Wizzup> wth are they doing!?
<freemangordon> well, this is backport
<freemangordon> but, we *do not* need it
<freemangordon> package build perfectly fine with python-is-python2 dependency removed
<Wizzup> actually, you can see CI fails now
<Wizzup> and yes, we need it really badly for most of our python packages
<freemangordon> good, but I am not sure =meta shall depend on it
<freemangordon> hmm, wait
<freemangordon> ignore that
<freemangordon> the gabble package itself shall not depend
<freemangordon> lemme try to fix that
<Wizzup> * Remove dh_python2, dh_pypy, and related debhelper sequences, supporting
<Wizzup> the removal of the Python 2.7 stack before bookworm release.
<Wizzup> (closes: 942959)
<Wizzup> this guy merged this to bullseye-backports
<Wizzup> even though he had a fix in bullseye-backports before for this problem you're having
<freemangordon> nice
<Wizzup> what is happening here
* Wizzup is disappointed
<Wizzup> if it works fine without, then remove it
<Wizzup> but all our other stuff is fubar now
<freemangordon> maybe oken a bug
<freemangordon> *open
<Wizzup> honestly I think I will just curse at them currently, so maybe later
<freemangordon> :D
<freemangordon> ok
<freemangordon> Wizzup: in the meanwhile https://pastebin.com/PxmFzvyt
<freemangordon> after dinner will repeat that with debug symbols
<Wizzup> hmm
<Wizzup> so do we just build our own dh-python then
<Wizzup> obviously debian doesn't actually support python2 in bullseye
<freemangordon> Wizzup: https://pastebin.com/b50GAi4k
<freemangordon> ugh
<freemangordon> Wizzup: process has XDG_RUNTIME_DIR=/run/user
<freemangordon> should be XDG_RUNTIME_DIR=/run/user/1000 IIUC
<freemangordon> Wizzup: mission-control also runs with wrong XDG_RUNTIME_DIR
<freemangordon> hmm: export XDG_RUNTIME_DIR=/run/user/$UID
<freemangordon> oh, ok
<freemangordon> $UID is not defined
<freemangordon> does anybody know who sets that env var?
<Wizzup> good searching
<Wizzup> no, don't know, sorry
<freemangordon> ok, it is bash that sets it
<freemangordon> or shell, in general
<freemangordon> going to fix
<Wizzup> is UID even a regular env var?
<freemangordon> Wizzup: autologin etc is in chimaera already, right?
<freemangordon> no idea
<Wizzup> freemangordon: I don't think so, it might just be in -devel
<Wizzup> I wonder if we even need to set XDG_RUNTIME_DIR there
<Wizzup> I think probably elogind will do that?>
<freemangordon> no
<freemangordon> umm,
<freemangordon> not sure
<freemangordon> lemme try without it
<Wizzup> it's set on my laptop, but I never set it, it could be some standard gentoo script
<freemangordon> mayeb grep in etc
<freemangordon> my fix works, but I want to check what will happen if I dont set it
<Wizzup> nothing in etc, probably /usr/share or some place now
<Wizzup> since apparently /etc is not the place for config anymore :p
<freemangordon> :)
<Wizzup> https://wiki.archlinux.org/title/XDG_Base_Directory says it's set through pam_systemd
<freemangordon> ok, if we don;'t set it, it is set :D
<freemangordon> so I'll remove that file
<Wizzup> great
<freemangordon> hmm
<freemangordon> not that easy
<Wizzup> how so?
<freemangordon> it is in /etc
<freemangordon> needs special massage, will see
<Wizzup> can't you just remove the displace?
<freemangordon> doesn't remove from /etc
<Wizzup> really? that's dumb
<Wizzup> you can make a debian/leste-config-common.postinst
<Wizzup> debian/leste-config-mapphone.postinst as an example
<freemangordon> ok
<freemangordon> Wizzup: hmm, actually version in chimaera is bigger than chimaera-devel
<freemangordon> so I gues everything is in stable
<freemangordon> well, 'stable'
<Wizzup> freemangordon: for autologin?
<freemangordon> for leste-config
<freemangordon> so I guess autologin stuff is in 'stable'
<Wizzup> hm
<Wizzup> no
<freemangordon> Wizzup: apt-cache policy leste-config-common
<freemangordon> before my build of few minutes ago, the version in -devel was 1.85-1+m7
<freemangordon> and 1.87-1+m7 in stable
<Wizzup> freemangordon: ok, but the autologin package is not in stable
<freemangordon> well...
<freemangordon> what I can say :)
<Wizzup> I am not sure what the problem is, but we can promote autologin and others
<freemangordon> yes, better do it
<freemangordon> I am upgrading my d4 with the new leste-config
<freemangordon> to confir is till works
<Wizzup> ok
<Wizzup> building autologin now
<Wizzup> what else do we need - xorg ?
<freemangordon> xorg itself?
<freemangordon> also, maemo-system-services
<Wizzup> and hildon-base
<freemangordon> what for?
<Wizzup> probably the conflicts
<Wizzup> I'm just looking at repodiff
<freemangordon> ok
<freemangordon> yes, please do all of those
<freemangordon> not sure how to do at once :)
<freemangordon> YAY! sip@ antisip is logged in :)
<freemangordon> Wizzup: it works :)
<Wizzup> the leste-config change?
<freemangordon> yes
<freemangordon> Wizzup: we shall decide on polkit auth agent
<freemangordon> Wizzup: shall I write our own one? we can base on ukui-polkit which is QT based and supports biometric authentication (it seems)
<Wizzup> I don't really have an opinion on this tbh
<freemangordon> well, for now we can start with gnome one until we have our own
<freemangordon> I am tempted to fork https://github.com/ukui/ukui-biometric-auth and fix the UI
<Wizzup> hehe
<freemangordon> ok, tomorrow will fix maemo-system services to start gnome polkit agent
<freemangordon> and will start implementing our own qt based one when I have some time
<Wizzup> ok
<Wizzup> :)
arno11 has joined #maemo-leste
<arno11> hi guys. with tricky settings retroarch is working well !
<arno11> nes and super nes at full speed
<arno11> megadrive at 70-80 %
<Wizzup> with overclock?
<arno11> yes
<arno11> only at 800
<arno11> but i think 600 is enough for nes and super nes
<arno11> the problem with retroarch is the sh***y doc
<arno11> settings is a nightmare
<arno11> on droid it should rocks !
<freemangordon> arno11: BTW, we just fixed a nasty bug leading to session daemons working with wrong XDG_RUNTIME_DIR
<freemangordon> IOW-now telepathy should be ok in terms of daemons
<arno11> goooooaaallll
<arno11> well done
<freemangordon> Wizzup: I will push leste-config to stable
<Wizzup> sure, I was just about to build it
<Wizzup> only mce is left now (newer in devel than chimaera)
<arno11> Wizzup: is it ready for dist upgrade ?
<freemangordon> should be
<arno11> ok
arno11 has left #maemo-leste [#maemo-leste]
<arno11> let's try
arno11 has joined #maemo-leste
<Wizzup> did it work?
<arno11> now XDG_RUNTIME_DIR=1000
<arno11> now my fb mess bitlbee connexion works again in conversatios
<arno11> *ions
<arno11> in fact not
<arno11> loggin works again but conversations seems to crash
<arno11> pkill conversations and now it works lol
<freemangordon> arno11: XDG_RUNTIME_DIR=1000?!?
<freemangordon> are you sure?
<freemangordon> it should be XDG_RUNTIME_DIR=/run/user/1000
<arno11> to avoid misunderstanding: /run/user/1000
<arno11> no probs
<freemangordon> ok, that's how it should be :)
<arno11> yep :)
<Wizzup> arno11: yeah that still needs work
<arno11> yes but that's already usable
<arno11> excepting calls and camera everything else is usable i think (on n900)
arno11 has left #maemo-leste [#maemo-leste]
sunshavi_ has quit [Ping timeout: 260 seconds]
akossh has quit [Quit: Leaving.]