<Scary_Guy>
Trying another PinePhone install, flashed through JumpDrive. Just going to let it sit plugged in until something happens besides a red dot.
<Scary_Guy>
You speak like I have any clue what I'm actually doing here. I know just barely enough to complain about things :(
<Wizzup>
:)
<Wizzup>
I'm looking, but also at work atm
<Scary_Guy>
Thanks, obviously real paycheck comes first though.
<Scary_Guy>
I just try to make things better in general too. Reporting bugs is about the best I can do to help. Probably will hop back on PmOS edge soon anyway. I really need to get more microSD cards.
<Wizzup>
hehe, yes, more microsd cards help!
Daanct12 has joined #maemo-leste
pagurus has quit [Ping timeout: 252 seconds]
pagurus has joined #maemo-leste
mardy has joined #maemo-leste
joerg has quit [Ping timeout: 245 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 250 seconds]
macros_ has joined #maemo-leste
Daanct12 has quit [Remote host closed the connection]
<freemangordon>
Wizzup: this stacked windows bug is really annoying. I wonder if it happens on 32 bits as wee
<freemangordon>
*well
<Wizzup>
is it only in qt?
<freemangordon>
I dn;t hink so
<freemangordon>
*don;t
<Wizzup>
hm, ok, I didn't have problems before on anything non-qt
<freemangordon>
could be qt related, yeah
<freemangordon>
hmm, no, seems not qt related
<Wizzup>
how do I reproduce?
<freemangordon>
you need addressbook :)
<freemangordon>
but, you can build it
Twig has joined #maemo-leste
Daanct12 has joined #maemo-leste
Twig has quit [Ping timeout: 256 seconds]
Daanct12 has quit [Quit: Quit]
ikmaak has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
ikmaak has joined #maemo-leste
Pali has joined #maemo-leste
Livio has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
pere has quit [Ping timeout: 240 seconds]
Pali has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
Daanct12 has quit [Remote host closed the connection]
l_bratch has quit [Remote host closed the connection]
l_bratch has joined #maemo-leste
macros_ has quit [Ping timeout: 240 seconds]
pere has quit [Ping timeout: 256 seconds]
macros_ has joined #maemo-leste
xmn has quit [Quit: xmn]
ikmaak has quit [Quit: ikmaak]
ikmaak has joined #maemo-leste
Pali has joined #maemo-leste
<sicelo>
i noticed that charge mode keeps the display on the whole time, at least on my droid 4. only the backlight is turned off, but the display can be seen if you angle it
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 250 seconds]
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
<freemangordon>
yeah, lots of stuff is broken in mce, but I want to finish abook first
pere has joined #maemo-leste
<inky>
folks, should i install modest from maemo repos? what about osso-abook?
<inky>
oh let me reconnect
inky has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
norayr has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
<norayr>
would someone from pinephone users package megapixels?
<norayr>
i almost did it once, megapixels doesn't build because it requires gtk4, but megapixels-legacy builds. i was using it on maemo-leste.
<humpelstilzchen[>
iirc rafael2k_ was working on megapixels
RedW has quit [Quit: huh upgrades]
pere has quit [Ping timeout: 252 seconds]
pere has joined #maemo-leste
<freemangordon>
inky_: installing modest will pull osso-abook
<freemangordon>
the library
<freemangordon>
adressbook, the application, is still not ready/available
<freemangordon>
it is being worked on, maybe in 2 weeks we'll have alpha in repos
RedW has joined #maemo-leste
TonyStone has left #maemo-leste [Leaving]
mardy has quit [Quit: WeeChat 2.8]
<norayr>
yay
uvos has joined #maemo-leste
<uvos>
freemangordon: not mutch i can do about that unless you have a way to repo
<uvos>
i know the tklock code is very racy
<uvos>
it makes assumptions about the dbus bus that are not really valid
<freemangordon>
uvos: you mean "mce tklock module" I assume
<uvos>
well both
<uvos>
both sides
<freemangordon>
well, see the pastebin
<uvos>
i see it
<uvos>
but there is state syncorisation between mce and tklock
<uvos>
and this state syncronisation makes assumptions about timeing gurantees dbus dose not make
<uvos>
im not shure how it could end up in a loop but it is racy
<freemangordon>
it is definitely mce that went nuts. I understand that we can;t do much without detailed mce logs
<uvos>
it could also be soemthing else entirely ofc
<freemangordon>
mhm
<uvos>
Wizzup: freemangordon: with regards to charge mode
<uvos>
mce is not involved at all
<uvos>
and yes it dosent power off the display
<freemangordon>
uvos: shall I enable verbose mce logs in init script?
<freemangordon>
so, hopefully next time when this happens we will have more info
<uvos>
freemangordon: sure if you have resonable grounds that you can trigger this again
<uvos>
i have trouble getting sdl behave it registers drm master
macros_ has quit [Ping timeout: 252 seconds]
<uvos>
but you cant get the cookie out of std
<uvos>
sdl
<uvos>
so it cant turn of the display atm
<freemangordon>
well, if I know how to trigger it, I will have provided those logs already :)
<freemangordon>
this happens once in a month or so
<freemangordon>
(with my usage ofc)
<freemangordon>
oh, which reminds me that Wizzup promised to pull latest sdl.
<uvos>
when it happens also try and check mces inputs
<freemangordon>
umm, not sure I understand what you mean by "mce inputs"
<freemangordon>
attach gdb or what?
<uvos>
no check various, evdev and iio-sensor proxy
<freemangordon>
ah
<uvos>
either of those missbhavig could also cause it
<freemangordon>
yeah
<freemangordon>
but I guess verbose logs will give info about that too
<uvos>
partially
<freemangordon>
and give the uSD card I use is 64GiB, I think as a first step I shall enable them
<freemangordon>
*given
<uvos>
mce verbose log is farily quiet really
<freemangordon>
but shall give us some clue about what happens
<uvos>
please not that it is a keylogger
<uvos>
*note
<uvos>
when sharing logs
<freemangordon>
this is a dev device only
<freemangordon>
not to say I am the only one with access to it
<freemangordon>
but yeah, thanks
<freemangordon>
I think I won;t share the whole logs anyway
<freemangordon>
TBH I don;t think this is related to inputs
<freemangordon>
it seems like auto-lock triggers in 3-5 seconds and touching the screen does not reset the timer
<freemangordon>
but it undims the screen
<freemangordon>
anyway, no enough info
<freemangordon>
uvos: BTW, I fixed stacked windows bug on 64 bits
<uvos>
great
<uvos>
its pretty buggy on 32bits too tho
<uvos>
obv other bugs
<freemangordon>
hmm, what bugs do you mean?
<uvos>
well theres the qt applications that dont stack after the first window creation
<freemangordon>
ah, but this is something in qt code I would say
<uvos>
and theres a wierd bug where sometimes the back button will return to a totaly unrelated window from a differents applications stack
<freemangordon>
not in MB
<freemangordon>
uvos: this is on 64bits I think
<freemangordon>
and this is what I fixed
<uvos>
i can make the latter happen by messing around with sphone and modest on d4
<uvos>
for a while
<uvos>
its some kind of race with window creation
<freemangordon>
hmm
<uvos>
i can also make it happen with the phone app and modest on fremantle
<uvos>
so its a legacy bug
<freemangordon>
ok, if you have a way to trigger, please share, I can have a look at it
<uvos>
not realiably
<freemangordon>
I see
<uvos>
its somehow a race with when the windows are created
<uvos>
ie try and create windows (via ssh or applicaion that take a while to load) while also creating another window
<freemangordon>
maybe compile MB/h-d with debug traces enabled and try to rtrigger
<uvos>
yeah
<freemangordon>
MB provides really verbose logs of what happens
<freemangordon>
is it normal that I see "inactivity: device inactivity timeout 30" twice in a row?
<uvos>
yeah
<freemangordon>
ok
<uvos>
depends on where the input is attached
<uvos>
also for ts on d4 is normal again
<uvos>
because it reads the ts twice
<uvos>
because d4 has 2 ts devices
<uvos>
thats sortof a bug (ie mce should check with udev if the device is disabled)
<uvos>
but its without consiquence
<freemangordon>
anyway, mce verbose logs are now enabled, will let you know if there the bug reappears