libera/#maemo-leste/ Wednesday, 2021-12-22

rafael2kWizzup: nope, X from the repo05:30
rafael2kWizzup: lemme know how to test your setup today again07:19
rafael2kmorning07:19
rafael2kno matter what it will break the package system, right? (just for me to be more well prepared this time)07:26
rafael2kalso, for the new pinephone kernel, please consider adding all the crypto stuff, luks and so on... I can not mount my PostMarketOS partition under Maemo kernel.07:50
rafael2kbtw, is maemo moving to chimaera?08:18
freemangordonWizzup: which repo to use for non-CMA buffers parch?09:06
rafael2kso, I'm not sure what changed in leste-config-pinephone / leste-config-common09:39
rafael2kbut it broke the audio in voice calls09:39
rafael2kI can see ucm2 directory have files changed...09:40
rafael2kIt seems some audio samplerate or other configuration mismatch, as I get some crazy noises in the phone...09:41
sicelorafael2k: i know at least pmos also saw audio breakage. apparently ucm loves to break things every now and then09:41
sicelomaybe check what they had to do09:41
rafael2ksicelo: well, this is related to latest config changes in leste-config-pinephone09:42
rafael2knot related to alsa version change itself09:42
sicelook09:42
rafael2kI can see stuff at /usr/share/alsa/ucm2/sun50i-a64-audio was deleted09:48
rafael2kpcm_slave.sl2 {09:50
rafael2k        pcm "hw:0,0"09:50
rafael2k        rate 8820009:50
rafael2k}09:50
rafael2kthis sound suspicious too at 00_alsa_pinephone_dshare.conf09:50
rafael2kHiFi audio playback is fine09:53
rafael2kjust VoiceCalls got trashed09:53
rafael2k1.54-1+2m7.1 was working fine10:00
rafael2k1.56-1+2m7 broke audio10:01
rafael2kalways when I think I have my Maemo all working, an update comes...10:02
rafael2k:/10:02
rafael2klemme check in PmOS if calls audio is fine there10:04
rafael2k in pmOS is still fine, I'll copy over the ucm2 and alsa config10:10
rafael2kok, the ucm2 files are corrupted10:36
rafael2k(in maemo)10:36
rafael2kI made the diff10:36
rafael2kshould I make a pull request?10:37
rafael2khttp://173.255.215.196/pinephone/VoiceCall.conf.diff10:39
rafael2khttp://173.255.215.196/pinephone/HiFi.conf.diff10:39
rafael2kfound just the offending like10:56
rafael2kmaking a pull request10:56
rafael2k*line10:56
lelrafael2k opened a pull request: https://github.com/maemo-leste/leste-config/pull/27 (fix voice calls in pinephone)10:59
rafael2kuvos: sometimes the dialer does not open when I receive a call, also, is it normal that the dialer disapears just after a call is established?11:01
uvosrafael2k: the dialer should close and the call ui should open allmost immidatly. the call ui is opened as soon as ofono registers the call and starts dialing, on mapphones this happens without any delay11:04
uvoson the calls it dosent show up on please use ofono scripts to see if ofono is registering the call11:05
rafael2khumm11:05
rafael2kit does not show up11:05
rafael2kright, ofono monitor will help me - btw - does sphone have no daemon?11:06
uvossphone is a deamon11:06
uvosthe desktop files just issue commands over dbus11:06
rafael2kstrange11:06
rafael2kso this is why it is not showing up when I receive a call11:06
uvosi dont know11:06
rafael2kI think it is dying somewhere11:06
uvosplease run killall sphone; sphone -v -v11:07
rafael2kok11:07
uvosopen the dialer and place a call11:07
uvosmaybe it crashes11:07
rafael2kshould I run as root or user?11:07
uvosuser11:07
rafael2kok11:07
uvosyou can send the log to devnull@uvos.xyz if you dont want to paste it publicly11:08
uvosor censor it11:08
uvos(it will show the phone number)11:08
rafael2know it is working11:10
rafael2klemme play a bit more, it was after some time playing11:10
rafael2ksphone: gui_history_list_double_click_callback11:10
rafael2ksphone: gtk_gui_dialer_show: with +....11:11
rafael2kthis is something I found - the number does not show up11:11
rafael2kok11:11
rafael2kthen if I just press any key11:11
rafael2kit shows (after I pick a number in recent)11:11
rafael2kok, found the real bug11:12
rafael2ksphone: gui_calls_select_callback11:13
rafael2ksphone: gui_calls_select_callback11:13
rafael2ksphone: gui_calls_update_global_status: 1, 111:13
rafael2ksphone: gui_calls_select_callback11:13
rafael2ksphone: gui_calls_double_click_callback11:13
rafael2k(sphone:5037): GLib-GObject-CRITICAL **: 13:12:35.116: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed11:13
rafael2kwhen I was calling to it11:13
rafael2k(receiving a call)11:13
uvosand what where you doing to trigger this?11:15
uvosbesides a incomeing call11:16
rafael2kI tapped in the hangup I think11:17
rafael2klemme try to repeat11:17
rafael2kdouble tapped maybe11:17
rafael2kthen the UI closed and I could not really hangup the call11:18
uvosdid you accept the incomeing call first11:18
rafael2kno11:23
rafael2kI got a segmentation fault11:24
rafael2kshould have enabled core files11:24
rafael2k:(11:24
rafael2kno core created11:24
rafael2ksphone-dbgsym ++11:25
rafael2k; )11:25
uvosoh right i see the problem11:26
uvosthat bit isent implemented11:26
uvosand its sending a null down the datapipe11:26
uvosyou clicked the remote pary name/ the remote phone number right?11:26
uvos*party11:26
uvosrafael2k: fixed: https://github.com/maemo-leste/sphone/commit/3708a2a8a8afe3fcb6d902012f7a5e532971d2e511:35
Wizzuprafael2k: yo11:36
Wizzupfreemangordon: https://github.com/maemo-leste/droid4-linux/commits/wip/n900/maemo-5.15-cleaned-up11:37
uvosrafael2k: btw testing sphone is a lot eaiser if you add:11:37
uvos[Modules]11:37
uvosModules=rtconf-libprofile;test;route-pulseaudio;playback-gstreamer;sphone-mce;comm-ofono;manager;external-exec;contacts-evolution;comm-error-gtk;contacts-ui-exec;store-rtcom;commtest11:37
Wizzuprafael2k: we do plan to move to chimaera but it is a massive undertaking that we don't want to do just yet11:37
uvosto a file called wahtever.conf in ~/.sphone/11:37
Wizzuprafael2k: regarding X, just dpkg -i the packages I provided yesterday (only the ones I mentioned should be enough, otherwise add -dev ones as dpkg complains)11:39
Wizzuprafael2k: when you then reboot and have X working still, let me know11:39
rafael2kuvos: tks!11:40
freemangordonWizzup: thanks, will be on it as soon as I have some spare time11:41
freemangordonBTW, is this boot fine on d4?11:41
rafael2kuvos: where should I put this Modules line?11:41
freemangordon*does this11:41
rafael2kuvos: understood11:41
rafael2kWizzup: hey!11:42
uvosrafael2k: a new file in ~/.sphone/11:42
uvosdont forget the [Modules] section header11:42
Wizzupfreemangordon: should, yes11:43
rafael2kWizzup: ok! tks!11:43
freemangordonok11:43
rafael2kuvos: did it11:44
rafael2kuvos: yes - I clicked remote phone number! will compile from source and keep testing11:53
Wizzuptmlind: I don't feel like we're going to get a response from Nitin about the compaction12:02
Wizzupmaybe he's on holidays or something :)12:02
rafael2kbtw, I'm making sure eg25-manager works upstream without mm12:21
rafael2kthen we can create a package of it to the pinephone12:21
rafael2kand remove the ad-hoc init scripts which bring up the modem12:22
Wizzupwhat does it do?12:27
rafael2kbasically a modem daemon which sets the modem parameters and is used to properly suspend and resume the modem12:43
Wizzupok12:47
rafael2kdunno if it isnt better to integrate in Maemo stach12:59
rafael2k*stack12:59
parazydrafael2k: Nice! We already have a package so we can update it whenever you say.13:01
parazydhttps://github.com/maemo-leste-upstream-forks/eg25-manager13:01
tmlindWizzup: yeah maybe he's oof13:02
tmlindout of office13:03
rafael2kparazyd: cool! did not know!13:05
rafael2kthe only difference will be the removal of libmm-glib-dev dependency13:06
rafael2kand I just edited meson.build to require meson 0.49 instead of 0.50 (it builds fine with 0.49 from beowulf) in eg25-manager main13:07
rafael2k(difference from a packaging perspective, I mean)13:08
rafael2kparazyd: when you have time to create another pp kernel, lemme know, I can test13:09
parazydWill do13:10
rafael2kalso, concerning ofono for pp, lemme know how can I help13:10
rafael2kI can work in building with internal libell if needed13:11
Wizzupno, we can figure that out I think13:12
parazydIs our plan to use ofono-d4 for Pinephone as well?13:13
parazydBecause otherwise we already have a build with ell13:13
parazydhttps://github.com/maemo-leste-upstream-forks/ofono13:14
parazydhttps://github.com/maemo-leste-upstream-forks/ofono/commit/1a5016f1b4a38abae6738b8d1c7b9200978b24ff13:14
Wizzupparazyd: yeah I want to merge them13:16
parazyd*nod*13:16
rafael2kI based the debian dir of my repo in this repo https://github.com/maemo-leste-upstream-forks/ofono13:17
rafael2kthe ell files there are not enough for latest ofono as far as I could test13:18
rafael2kbut it is just a matter of copying files over...13:18
rafael2k(from libell source)13:18
rafael2kWizzup: I did not forget about your X packages - will do it later today15:46
rafael2kjust trying figuring out if u-boot in pinephone already has the vol up / vol down to choose between what distro to boot (i'll do it between eMMC PMOS and Maemo in the SD)15:47
Wizzuprafael2k: all good, I just want to confirm you're seing the same thing15:47
rafael2kand figuring out how to see batery level15:47
rafael2kis there a plugin for it in Maemo, right?15:48
Wizzupit should just show yes15:49
rafael2khum15:49
rafael2kit never really showed for me15:49
rafael2k(since 10 years ago with the N900... eheheheh)15:49
Wizzupright15:49
Wizzupprobably parazyd didn't pick up the patch I added to make sure upower sees the battery and exports the battery type15:50
Wizzupi.e. https://github.com/maemo-leste/pine64-kernel/commit/c62a8aeab344523190c7f539de60d94ba6c9cc5f15:50
siceloheh, on N900 Fremantle you couldn't see battery level? :-D15:51
bencohsounds like a crippled user experience :]15:53
freemangordonparazyd: could you have a look at https://github.com/maemo-leste/liblocation/pull/116:02
parazydYes16:06
Wizzupuvos: do you recall how to use the qmimodem on the d417:33
Wizzupwe had some other udev rules for it iirc17:33
rafael2ksicelo: last time I saw the batery level -17:36
rafael2k( )17:37
rafael2k: )17:37
uvosWizzup: sure it uses the udev var OFONO_DRIVER18:46
uvosWizzup: just use udevadm info on the modem to figure out what to match against18:46
Wizzupuvos: ok, might be good for some testing18:48
Wizzup(to compare to motmdm)18:53
uvosthe ofono driver is called motorolamodem, but yes18:57
uvos(just nit picking here in case you want to force it later)18:57
Wizzupmhm18:59
rafael2kyay, the u-boot already shipped in maemo already has support for multi-boot using volume keys!19:50
rafael2k; ))19:50
rafael2k_this_ is handy!19:50
Wizzup:)19:51
rafael2know with volume_up I can boot the PmOS on the eMMC19:55
rafael2knot having to open the phone and remove the SD to boot the eMMC is wonderful19:57
uvosyeah having multiple boot entrys is very usefull20:03
uvosi have like 10 :P20:03
uvosi hate that android bootloaders dont allow this20:03
rafael2kandroid per se is a plague20:06
rafael2kcurrent u-boot in pp supports at least 3 different boot entries, vol up, vol down, or no volume key pressed20:08
rafael2kif test x$volume_key = xup ; then20:09
rafael2k  # choice when pressing volume up key20:09
rafael2kelif test x$volume_key = xdown ; then20:09
rafael2k  # choice when pressing volume down key20:09
rafael2kelse20:09
rafael2k  # default choice20:09
rafael2kfi20:09
rafael2kcrazy that I just discovered I already had the bootloader I need to multi-boot already installed...20:12
rafael2kand thanks for the one who wrote this... https://leste.maemo.org/PinePhone20:15
rafael2kmkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr20:15
rafael2kthis was the line I was looking for20:15
rafael2kbtw... if anyone can test (or trust in the tests / bisection I did): https://github.com/maemo-leste/leste-config/pull/2721:20
Wizzupok21:20
WizzupI'll merge it21:20
rafael2ktks!21:21
rafael2kWizzup: could you pass me again the link the the x pacckages tarball?21:22
rafael2kfound21:31
Wizzuprafael2k: sorry phone call21:45
Wizzuprafael2k: ok, am here now21:46
rafael2kno problem21:46
rafael2k; )21:46
rafael2kok, I'll stop for a bit trying to read network logs to see if MTS has VoLTE enabled or not21:47
rafael2k:P21:47
rafael2kyelp me21:47
rafael2kinstall mesa first from repo21:47
rafael2k(from experimental)21:48
WizzupI think you add experimental and just 'apt-get dist-upgrade'21:48
Wizzupthat should pull in mesa21:48
Wizzupif it doesn't let me check my pinephone21:49
rafael2kit worked21:49
rafael2kinstalling the packages already21:49
rafael2kconcerning the X packages21:51
Wizzupok21:51
rafael2kI should cherry pick just X (not overlapping with was just updated), without unneeded -devs right?21:51
rafael2kdone the dist-upgrade21:52
WizzupI think I gave you a list yeah21:52
Wizzupwell you need the -dev pkgs only if you have the -dev pkgs installed already at lower version21:52
rafael2kthere is stuff like xserver-common_1.20.13-3_all.deb and xserver-common_21.1.1-2_all.deb21:54
rafael2kwhat should I install?21:54
Wizzupwait, I send you 1.20 ones?21:54
Wizzupremote all 1.20 debs21:54
Wizzupremove*21:54
Wizzupfrom the tar, if any21:54
rafael2kyes21:54
rafael2kmany 1.20 mixed with 21.1.121:54
rafael2kok21:54
BlagovestPetrov[[offtopic] Guys, are there any requirements for writing "native" applications for Maemo? QML libs, etc?21:54
Wizzupdsc_ has some experience with it21:55
Wizzuprafael2k: if you want I can double check my tar21:56
rafael2kdpkg -i libxcvt0_0.1.1-1+b1_arm64.deb libxi6_1.8-1_arm64.deb xdmx_1.20.13-3_arm64.deb xdmx-tools_1.20.13-3_arm64.deb xnest_21.1.1-2_arm64.deb xserver-common_21.1.1-2_all.deb xserver-xephyr_21.1.1-2_arm64.deb xserver-xorg-core_21.1.1-2_arm64.deb xserver-xorg-input-evdev_2.10.6-1_arm64.deb xserver-xorg-legacy_21.1.1-2_arm64.deb xvfb_21.1.1-2_arm64.deb21:56
Wizzuprafael2k: I think you just need the three I suggested21:56
WizzupI don't think you need xnest or xephyr21:56
Wizzupsame for xdmx tools21:56
rafael2kyou never know21:56
rafael2k:P21:56
Wizzupok21:56
rafael2kI like X21:56
Wizzupit might have more deps21:56
Wizzupbut you can try21:56
Wizzupin any case xdms, xdmx-tools, xnest and xephyr you don't need21:57
Wizzupxdmx*21:57
WizzupBlagovestPetrov[: conversations at least is a qml app that we have now21:57
rafael2kgtk2!21:57
BlagovestPetrov[:D21:57
BlagovestPetrov[thanks. I'll check the conversations code :)21:58
rafael2kjust xserver-xephyr errored21:58
rafael2kremoved21:58
rafael2kok, all good21:58
Wizzuprafael2k: ok, so you might want to turn on glaor21:58
Wizzupglamor21:58
Wizzupso not have accelmethod none21:58
rafael2kok21:58
dsc_BlagovestPetrov[: QML works fine, I was going to make a bare bones sample QML project that people can extend and turn into their own project21:58
dsc_generally its not different from other platforms21:58
rafael2kok,  reboooting21:58
uvosBlagovestPetrov[: the only toolkit that compleatly works atm is gtk221:59
BlagovestPetrov[understand.. but still, I'll try the qml22:00
BlagovestPetrov[only the theming API in the newest qt quick controls is weird22:01
uvosBlagovestPetrov[: qwidgets and qml is partally implemented, but lacks keyboard input and has some bugs with both stacked windows and qmenus22:01
Wizzupwhat are the bugs with qmenus?22:02
BlagovestPetrov[ah, ok22:02
dsc_s/keyboard input/virtual keyboard input/22:02
uvosWizzup: the arrow is missing, there is a wierd timeing bug with the grab transfer22:02
dsc_keyboard input works, at least for QLineEdit22:02
uvosno22:02
uvosit dosent22:02
rafael2kBlagovestPetrov[: gtk2 + hildon22:02
uvoskeyboard vs xlib works22:02
rafael2kWizzup: up22:02
uvosbut not him22:02
uvosie it only works with physical keyboards22:02
rafael2kcrazy fonts22:03
rafael2kvery big22:03
BlagovestPetrov[what is used for the keyboard, xvkbd or something from Nokia?22:03
Wizzuprafael2k: ok, yeah22:03
rafael2k; ))22:03
uvosrafael2k: you have to set the incorrect dpi of 9622:03
Wizzuprafael2k: that is something I worked around in the /etc/init.d/xorg, it's unrelated to all of this22:03
rafael2kgood, I'll open a wine here to start enjoyng these font size22:03
Wizzupit's just that my lab psu is not doing what I want it to do atm22:03
WizzupI think you just need to add -dpi 96 to the xorg options22:03
Wizzup*think*22:04
uvosyou can do that22:04
dsc_BlagovestPetrov[: as for QML performance, I can happily conclude that stuff like scrolling is pretty smooth on, for example, the Motorola Droid 422:04
uvosor you can set the size of the display in xorg conf22:04
Wizzupyes, it is the easiest solution since we don't want to deal with this problem now at all22:04
uvosso that 96 dpi results22:04
Wizzupthat works too22:04
rafael2kright22:04
BlagovestPetrov[:)22:04
Wizzuprafael2k: in any case, portrait mode should be quite smooth for you I think22:04
Wizzuplandscape is not that fast, but it should be ok22:05
Wizzupnow, let me find the rendering issues that I saw22:05
rafael2kthis font size does not really bother me22:05
rafael2klets test the X22:05
Wizzuprafael2k: well so what issues were you seeing before22:05
Wizzupjust to get a sense of what you think we were at before22:06
rafael2kX does not crash anymore, and I can see videos in youtube in firefox, but otherwise, the crazy annoying bug, for example, in firefox, which re-draws things randomly keeps going22:07
Wizzupright22:07
Wizzupso let's try something22:07
Wizzup(booting my pp...)22:07
rafael2kkeyboard vkb letters show, then does not show, then shows again, then not22:07
Wizzupyes, so let's test a potential 'fix'22:07
Wizzuprafael2k: btw, do you get portrait mode?22:08
rafael2kindeed, taps are not precise also, which was not happening before22:08
rafael2kI tap the vkb, and many "letters" are typed together22:08
Wizzuprafael2k: that seems weird, I didn't see that, but it might be unrelated to the rendering problems22:09
rafael2kI was using portrait22:09
rafael2klemme try landscape22:09
Wizzupfirefox runs in landscape for you?22:09
Wizzuperr portrait*22:09
rafael2klandscape - I was talking about the terminal in that message22:10
uvosforcerotation = 1 probubly22:10
rafael2kfirefox rotates to landscape when I open it22:10
uvosmakes the expirance better anyhow imo22:10
Wizzupit doesn't matter so much, really, I just wanted to know if portrait was also smoother for you in say desktop scrolling22:10
Wizzuprafael2k: right exactly22:11
Wizzuprafael2k: that's good22:11
Wizzupok, so let's focus on the rendering stuff22:11
Wizzupin /usr/share/hildon-desktop/shortcuts.ini22:11
Wizzupadd this:22:11
WizzupUnredirect=XF86AudioLowerVolume22:11
Wizzupand maybe just remove whatever is assigned to any volume buttons22:11
uvosrafael2k: set in /usr/share/hildon-desktop/transitions.ini forcerotation = 1 to allow anything to rotate22:11
Wizzupuvos: this is not relevant atm22:11
rafael2kok22:11
uvosWizzup: if you say so22:12
Wizzuprafael2k: if you made that change, you can now temporarily disable compositing for windows22:13
rafael2kLeftButton=XF86AudioLowerVolume22:13
rafael2kI already have this assigned...22:13
uvoshe also has to killall hildon-desktop22:13
Wizzuprafael2k: so what I noticed is that if I hit that button when osso-xterm is active, and then raise vkb, it has no problems whatsoever22:13
Wizzuprafael2k: so just remove that22:13
Wizzupuvos: yes, I was getting to that22:13
rafael2kok22:13
Wizzuprafael2k: keep in mind that this compositing disable is only temporary, it comes back when you return from vkb22:14
rafael2kall changes done22:14
Wizzuprafael2k: ok, so either reboot or killall hildon-desktop to refresh22:15
rafael2kdo you know where X is beeing called, to add the -dpi 96 ?22:15
Wizzup/etc/init.d/xorg22:15
rafael2kok, killedall hilden-desktop22:17
rafael2knothing happens22:17
Wizzupso now the lower volume button can be used to turn off compositing for an active window temporarily22:17
Wizzupso open xterm22:17
Wizzupand touch the screen22:17
Wizzupyou'll likely see vkb pop up and see artifacts22:17
Wizzupright?22:18
rafael2kthe ui is frozen22:18
rafael2kI'll kill X22:18
Wizzupuh22:18
rafael2kok, not really frozen22:18
rafael2kit just does not accept input anymore22:19
Wizzupjust reboot the device I think22:19
rafael2kbetter22:19
uvosxf86-input-libinput22:20
uvosis a module22:20
uvosthat now wont load22:20
uvosunles you have the ignore abi thing in xorg.conf22:20
uvoswe had that for some time and some old installs have left over files...22:20
Wizzupuvos: the devices should come with evdev still22:20
WizzupI specifically provided him the .deb for that22:20
uvosnopt22:20
uvosnope22:20
Wizzupis the case for mine22:20
Wizzupfully up to date22:20
uvosi moved all devices to libinput22:20
uvosexcept n90022:21
Wizzupin any case the input abi didn't change22:21
Wizzupiirc22:21
Wizzupjust the video one22:21
uvosyes it did22:21
uvosinput also changed22:21
uvosfor the gestures22:21
Wizzuprafael2k: you said better, so I assume it works again?22:21
uvosi gues tho that maybe xorg will try evdev if libimput dosent load22:22
uvosbut only if its installed22:22
WizzupI didn't have libinput on my device22:22
uvosnot sure if its an external module actually22:22
* Wizzup trying to figure out why one of his lab power supplies now slowly builds up from 1V to 3.8V instead of going there directly22:23
Wizzupmust be some weird setting22:23
uvosdose it hold against load at 3.8?22:23
rafael2kit is working22:23
rafael2kyes22:23
uvosotherwise thats classic output transistor with a shorted base22:23
Wizzupuvos: the led is at C.V instead of C.C22:23
Wizzupuvos: it is likely a config option, the working one is at C.V22:24
rafael2kand it did not crash yet22:24
Wizzuprafael2k: ok, so let's try to do this again22:24
Wizzuprafael2k: so I am not seeing any crashes, but I want to investigate the flickering/redrawing problems22:24
rafael2kWizzup: now I have sane font sizes22:24
Wizzupfirst I'd like you to trigger that flicker/redraw bug22:24
Wizzupand then we can see if you see the same as I do with the window 'un-composited'22:24
rafael2kthe fickering / redraw bug is exactly the same22:25
Wizzupok22:25
Wizzupas expected22:25
Wizzupdo you reproduce this with osso-xterm?22:25
rafael2kyes22:25
Wizzupok22:25
Wizzupso now go to osso-xterm22:25
Wizzupand press the volume down key22:25
Wizzupthe title bar of osso-xterm will change22:25
Wizzupand then press the key again22:25
Wizzupyou should have a behaving vkb then22:25
uvoshuh22:26
uvosyeah its wrong22:26
uvoshttps://github.com/maemo-leste/hildon-meta/blob/3dbf06b6b347674b3b0d3624f2908ef5b59ca2ba/debian/control#L15522:26
uvosits switched over to libinput in leste config22:26
uvosbut the meta is wrong22:26
rafael2kI press the volume down two times?22:26
Wizzupuvos: btw I assume that fullscreen is also unredirected by default?22:26
Wizzuprafael2k: just once does it for me22:26
uvosWizzup: its wierd and buggy22:27
uvossometimes it is22:27
uvossometimes it isent22:27
Wizzupuvos: ok, let's exclude it from the test then22:27
Wizzuprafael2k: just to check you did set the ini as I suggested right, the shortcuts?22:28
Wizzupthat is, this is present: Unredirect=XF86AudioLowerVolume22:28
Wizzupand nothing else uses XF86AudioLowerVolume22:28
rafael2kI'm not sure22:28
rafael2kfirst time it seemed it got better22:29
rafael2kyes yes, I set22:29
Wizzuprafael2k: yes, it only lasts once22:29
Wizzupyou had to do it every time22:30
Wizzupso if you see it was better the first time, then it worked22:30
Wizzupnow try it in firefox or something else22:30
rafael2kwai22:30
rafael2kwait22:30
rafael2ktesting this magic key in firefox22:31
rafael2kmuch better22:31
Wizzupright, so we know that compositing somehow causes this problem22:32
Wizzupand looks like you're seeing the same as I am22:32
rafael2kI mean, I could use like this22:32
rafael2kit is fine22:32
Wizzup(but good that the crashes are fixed, either with newer mesa or newer X)22:32
Wizzuprafael2k: yes, but we can't just disable compositing :)22:32
rafael2kwhy not?22:33
Wizzupbecause then many parts just don't function anymore22:33
Wizzuplike the title bar22:33
rafael2know I want this "disabling compositing" too22:33
rafael2kright, got it22:33
Wizzupok22:34
Wizzupso what we need to do is either file a bug with hildon-desktop as example use case, or narrow it down further somehow22:34
rafael2kI'm not really sure why we need it, but even my 11th gen intel with nvidia which can do raytracing, I always make sure I have this compositing disabled in my wm22:34
Wizzupuvos suggested trying clutter demos22:34
rafael2k:P22:34
Wizzuprafael2k: hildon-desktop cannot work without compositing22:34
rafael2kWizzup: this is a bug in Mali driver...22:35
Wizzuprafael2k: yes, it seems like that, in lima22:35
Wizzupbut hildon-desktop is not in normal debian distro, so if we file a bug it might be hard(er) to get developer to test22:36
rafael2klima, yes22:36
WizzupI'm just going to go to the channel and ask22:37
rafael2kthere are even gtk4 bugs opened in lima driver, I remember looking at them like 10 months ago22:37
rafael2kthe problem is certainly not with hildon...22:37
rafael2klemme find the opened bug report22:38
rafael2kI sent it here like begining of 202122:38
rafael2khttps://gitlab.freedesktop.org/mesa/mesa/-/issues/359222:39
WizzupI don't think it is the job timeout bug though, is it?22:40
rafael2kLIBGL_DEBUG=verbose GDK_DEBUG=opengl,gl-gles22:41
rafael2kif we could grab some crazy messages from mesa debug...22:41
rafael2kI think so22:42
Wizzupwe could, of course22:42
rafael2kbtw, vkb is not working anymore, it worked once, then never more showed up22:42
rafael2k:/22:42
uvosprobubly makes more sense to first find something with the minimum draw calls that triggers this22:42
rafael2k(after the upgrade)22:43
uvosand then do that22:43
rafael2kagreed22:43
uvosside note: since we established its not glamor causing issues, but h-ds clutter rendering, the least performance impacting (still terrible) workaround would be to set GALIUM_DRIVER for just h-d instead of accelMethod=none22:43
uvossince that breaks acceleration only for h-d instead of for everything22:43
rafael2kit is clearly buggy, a couple of widgets already expose the issue22:43
Wizzupdoesn't that still mean that all transitions would be cpu?22:43
Wizzuprafael2k: yeah so we need to try some other compositing window manager and perhaps put some widgets on top of each other perhaps22:44
uvosWizzup: yes it would still be terrible, only marginally better than accelMethod=none22:44
uvosyou gain video acceleration and xorg 2d accel22:44
uvosand games22:44
WizzupI think it would be better to just get a bug filed and not bother with other workarounds imho22:44
rafael2kthen video playback is possible - this is good!22:44
WizzupI joined #lima on oftc irc22:45
uvossure, im just mentioning it for rafael2k and inky who both currently use the acellMethod=none path22:45
Wizzupand left a wall of text explaining the bug22:45
Wizzupoh, urgh, now my apt is unhappy because of X :-)22:46
Wizzupwill be fun to install stuff now22:46
rafael2kWizzup: eheheheh22:46
* Wizzup just removes meta pkgs for now22:46
rafael2knothing bad happens, it is just scary to type "Yes I want to fuck up my system!" to apt22:47
rafael2kfun in the end22:47
Wizzupyeah it does that now because I marked hildon-meta as 'essential' :)22:47
Wizzupuvos: so what, like compton with i3wm and windows on top of each other or something?22:47
uvosWizzup: i dont follow22:49
rafael2ksome simple sample to demonstrate the error, right?22:50
Wizzupregarding more simple reproduce case22:50
uvosmore like just xorg and some clutter demo that shows it22:50
rafael2kwith all "LIBGL_DEBUG=verbose GDK_DEBUG=opengl,gl-gles" and other possible verbosity22:50
uvosand strip that demo of draw calls untill it no longer shows the problem22:50
Wizzupwell I was hoping they could do some of the work22:51
Wizzupuvos: so what tests did yiu recommend?22:53
Wizzupbecause I only see clutter-1.0-tests22:53
Wizzupwhich is not clutter 0.822:53
Wizzup(which is what we use)22:53
uvoswell you could test if 1.0 also exibits the problem with those, failing that im sure you can find some .8 demos or?22:54
uvosthose demos probubly where ported over22:54
uvosso the git history maybe22:54
Wizzupok, I hope the tests don't expose random other problems that lead nowhere :P22:54
rafael2kor we could just boot debian bullseye with xorg and demonstrate the problem?22:54
uvosyeah but demostrate with what22:55
uvosexactly22:55
Wizzuprafael2k: if you can, please22:55
rafael2kI'd try any gtk app and some wm like gnome22:55
Wizzupthe clutter tests are not at all interactive22:55
Wizzupthey jsut print 'ok'22:55
uvosthe toys22:56
uvosi ment the toys22:56
uvosnot the unit tests22:56
Wizzupwhat is the package name? I can't find it in apt22:56
rafael2kin the end... one solution is just use the proprietary drivers...22:57
Wizzuplet's not for now22:57
rafael2k(I'm the one fine with noaccel :P )22:58
Wizzupsearching for 'clutter toys' on google is extremely useful22:58
Wizzup...22:58
uvosWizzup: https://github.com/clutter-project/toys22:58
uvosi dont think these are packaged22:59
uvosbut maybe im wrong22:59
uvosno idea22:59
uvosi would also try comption too22:59
uvossince thats easy23:00
uvosand elimites a problem with the offscreen pixmaps23:00
uvosthat are used for composition23:00
uvosbut i find this unlikely23:00
Wizzupif i have compton running, then osso-xterm with the vkb doesn't show the problem23:01
uvosok not that then23:01
Wizzupthe problem is also not there with matchbox-window-manager, unsurprisingly I guess23:03
uvosmatchbox dosent do any rendering at all23:03
Wizzupany particular toy you have in mind? and do I run it with compton?23:05
uvosno, try them untill you find one that hopefully shows the issues23:06
uvosno23:06
uvosno comption23:06
uvosjust xorg23:06
uvosor matchbox if you like23:06
WizzupI wonder if there are some mesa env vars we can try somehow23:07
Wizzuplike flush after every draw or something23:07
Wizzuphmmm23:15
WizzupI see some issues when I do the following:23:15
Wizzupadd to:23:16
Wizzup/etc/hildon-desktop.env23:16
Wizzupexport LIBGL_DEBUG=verbose23:16
Wizzupexport MESA_DEBUG=flush,incomplete_tex,incomplete_fbo23:16
Wizzupexport MESA_LOG_FILE=/tmp/hd.log23:16
WizzupMesa: User error: GL_INVALID_ENUM in glTexParameter(param=GL_NONE)23:17
WizzupMesa: User error: GL_INVALID_ENUM in glGetTexParameteriv(pname=0x8191)23:17
WizzupMesa: User error: GL_INVALID_ENUM in glEnable(GL_TEXTURE_2D)23:17
Wizzuphttps://dpaste.com/HVB8HP4W923:18
Wizzupuvos: ^23:19
Wizzupthis seems to come fromcogl-texture23:20
Wizzupthe error doesn't show when I am just scrolling h-d23:20
WizzupI guess it might be worth testing with llvmpipe or something else in vm and see if the errors also occurs?23:20
Wizzupfreemangordon: any idea perhaps?23:23
Wizzupmightr be a red herring23:24
Wizzupuvos: another potential interesting test would be to pull out the old clutter 1.0 hd and see if it has the same problems23:24
Wizzupbut clutter 1.0 performs terribly23:24
* Wizzup break time23:27
Wizzupomg lol23:36
Wizzupmy messages never made it to lima :D23:36

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!