M1peter10[m] has quit [Quit: Client limit exceeded: 20000]
pere has joined #maemo-leste
pere_ has joined #maemo-leste
pere has quit [Read error: Connection reset by peer]
rafael2k has quit [Ping timeout: 240 seconds]
_inky has quit [Ping timeout: 256 seconds]
Twig has joined #maemo-leste
inky has joined #maemo-leste
pere_ has quit [Ping timeout: 250 seconds]
pere_ has joined #maemo-leste
inky_ has quit [Ping timeout: 240 seconds]
_inky has joined #maemo-leste
pere_ has quit [Quit: Leaving]
pere has joined #maemo-leste
Pali has joined #maemo-leste
<Wizzup>
Pali: as mailed, I can look at u-boot starting around ~10 feb, and then it shouldn't be more than a few days I think to get a rfc patch
<Wizzup>
let's hope that's okay for them
<Pali>
ACK!
M1peter10[m] has joined #maemo-leste
inky has quit [Ping timeout: 256 seconds]
inky_ has joined #maemo-leste
Danct12 has quit [Ping timeout: 240 seconds]
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
_inky has quit [Ping timeout: 250 seconds]
rafael2k has joined #maemo-leste
inky_ has quit [Ping timeout: 240 seconds]
Twig has quit [Ping timeout: 256 seconds]
_inky has joined #maemo-leste
Oksanaa has quit [Ping timeout: 256 seconds]
pere has quit [Ping timeout: 250 seconds]
<lel>
boshtannik opened an issue: https://github.com/maemo-leste/bugtracker/issues/601 (Language switch, or spec symbol window open by Ctrl + Space and fn + ctrl are broken for me. (russian 2 arrow keyboard))
pere has joined #maemo-leste
inky_ has joined #maemo-leste
macros__ has quit [Quit: Konversation terminated!]
inky_ has quit [Ping timeout: 256 seconds]
<Wizzup>
uvos: wondering if it is possible that the shift logic improvements cause the above problem (at least for special keys)
pere has quit [Ping timeout: 256 seconds]
marabej has joined #maemo-leste
<reinob>
Yesterday when I installed leste I also noticed that the arrow keys on my German keyboard where wrong. I could "solve" it by replacing the keypad with a US one, which is something I had always planned on doing :)
<reinob>
In my case I had set the hardware keyboard language using the settings (so no ctrl-space, just the standard setting)
xmn has quit [Quit: ZZZzzz…]
inky_ has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
<freemangordon>
Wizzup: dma_buf issue is still not solved, I know why the leak but still don;t know how ti fix it without sacrificing the performance a bit
<freemangordon>
in 1-2 days hopefully will have a fix
xmn has joined #maemo-leste
macros_ has quit [Quit: Konversation terminated!]
<Wizzup>
freemangordon: ok :)
<Wizzup>
reinob: I think you should be able to configure the hw layout
<Wizzup>
reinob: right, like you said
<reinob>
Wizzup: sorry I didn't make it clear. Configuring the HW keyboard settings didn't help.. I physically replaced the German layout (the keyboard overlay) with a US one I had lying around nearby :)
System_Error has joined #maemo-leste
<Wizzup>
reinob: ok, I think it should work, but currently it is set to us in /etc/default/keyboard
<Wizzup>
to 'us' in*
<Wizzup>
so that's a part of what needs changing I think
<Wizzup>
and hildon-input-method seems a bit broken regarding this too
<Wizzup>
s/and/but/
<reinob>
yup. As a test I just changed the setting back to German but it didn't have any effect. I have yet to have a look at the whole init process..
<Wizzup>
I think this is more a matter of 'yeah, we still have to finish this part' :-)
<reinob>
sure :) for all I care, this is a finished product :). I mean, it boots to something one can work/play with, and it's debian (pardon, devuan), so the limit is actually the 256MB of RAM :), but it's still nice to have such a useful N900 in 2022 :)
inky_ has quit [Ping timeout: 268 seconds]
<Wizzup>
yeah, there's definitely a few tings to fix before it's a finished product, though ;)
uvos has joined #maemo-leste
<uvos>
Wizzup: what shift key logic improvements?
<uvos>
Wizzup: we dident change anything with that
<uvos>
Wizzup: i uredirected return
<uvos>
Wizzup: but the redirected return was KP_RETURN
<uvos>
Wizzup: not return
<uvos>
Wizzup: so this dident affect d4 at all , except solve issues where gtk2 applications dident accept return as return (only kp)
<uvos>
wrt special keys breaking, this might have happend with the xcb input method, not sure, but was maybe around this time
<Wizzup>
so it's not say 24edfc425808f6cfed026f70d9c5c7e8bdb2a56a
<uvos>
not sure why that would happend, theroetcily this isent touched at all
<Wizzup>
right
<uvos>
whats that hash of?
<uvos>
him? the vkb plugin?
<uvos>
or gtk2
<Wizzup>
hildon-input-method
<uvos>
no
<uvos>
thats changes the bavrior of the utf-8 -> xcb keysmb
<uvos>
translator
<uvos>
this dosent touch the vkb or the hwkbd at all
<Wizzup>
ok
<uvos>
hildon-im-xcode.c is the xcb backend
<uvos>
the most likely culprit is src/hildon-im-ui.c changes in fad2c3540ff8bb74a687d6cf8538d2c276a02186
<uvos>
for special keys
<uvos>
maybe regession test that
<uvos>
yeah ok
<uvos>
i see the problem
<Wizzup>
:)
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
inky_ has joined #maemo-leste
<Wizzup>
btw, I don't recall ctrl+space ever working (to cycle through keyboard layout), but if you feel like looking at that, I think that would help with https://github.com/maemo-leste/bugtracker/issues/601
<uvos>
mce allready explicitly adds its own warning flags for instance
<uvos>
quite explictly the ones set in cmakelists
<Wizzup>
The hardening+=all might not be possible through cmake and require a debian/rules tweak, right?
<uvos>
not sure still the others are bullshit
<Wizzup>
strong words but yeah, does not look like they are necessary
<uvos>
well they are worse than not nescesarry since it will leave you quite confised if you change the waring flags in the build system because of some specific false positive
<Wizzup>
right
<uvos>
i also dislike DEB_BUILD_MAINT_OPTIONS
<uvos>
makes more sense to just apply the harding flags yourself
<uvos>
as i use it not just on debian
<uvos>
im just going to revert this
<Wizzup>
It is considered good practice to have hardening flags on in debian
<Wizzup>
And debian has specific spec files for those
<Wizzup>
cmake doesn't follow CPPFLAGS. A fix was briefly available in sid, but had been revoked since upstream rejected the patch. See bug 653916 for details. As a workaround appending CPPFLAGS to CFLAGS and CXXFLAGS should work in most cases. Debhelper (since 0.9.20120417, only with compat=9 and dh_auto* commands!) and cdbs (since 0.4.110) handle this automatically so the workaround is no longer necessary if
<Wizzup>
they are used.
<Wizzup>
from above page
<Wizzup>
looks like with autotools it's supposed to just work, which is probably why most of our packages don't specify this stuff
<uvos>
the bug dosent apply here
<Wizzup>
uvos: it seems to relate mostly to -D_FORTIFY_SOURCE, do you mean you already set that?
<Wizzup>
in any case I don't have a strong opinion here either way
<uvos>
no im saying i also build for arch
<uvos>
and that is usefull
<uvos>
and therefore it makes more sense to have int in buildystem
<uvos>
instead of applying it in both packages
<uvos>
*in the buildsystem
_inky has quit [Ping timeout: 256 seconds]
<Wizzup>
the problem is that if debian change the hardening spec in say stable+1, then you won't notice and won't be in sync
<Wizzup>
gentoo just adds a whole lot of flags by itself typically iirc
<uvos>
sure yes
<uvos>
anyhow how im reading this it should be applied atomaticly anyhow
<uvos>
so this is unesscary
<uvos>
have to check if it dose
<Wizzup>
*nod*
_inky has joined #maemo-leste
rafael2k has quit [Ping timeout: 256 seconds]
rafael2k has joined #maemo-leste
<sicelo>
Wizzup: from GKH, "[PATCH 5.10 297/563] ARM: dts: omap3-n900: Fix lp5523 for multi color" - what does this mean? he's importing it into LTS?
<Wizzup>
yeah
<sicelo>
wow, that's nice :-)
<Wizzup>
let's hope they also pick the patch I send :)