| Wizzup | uvos: building -devel droid3 image atm, it won't be rsynced yet | 00:52 |
|---|---|---|
| Wizzup | https://phoenix.maemo.org/job/leste-image-droid3-dev/1/console | 00:52 |
| Wizzup | will go to sleep and see if it succeed tomorrow, will add rsync and some -dev suffix then | 00:52 |
| Wizzup | freemangordon: wrt subscribe, maybe use the right side bar and add 'notifications' or something https://gitlab.freedesktop.org/mesa/mesa/-/issues/5800 | 00:53 |
| Wizzup | uvos: also yes it is surprisingly thing for a slider | 00:56 |
| uvos | btw often the clownboot kernel is not happy at all | 00:59 |
| uvos | [ 40.878326] unexpected IRQ trap at vector 0 repeats at nausium | 00:59 |
| uvos | and the device effectivly hangs | 00:59 |
| uvos | dosent happen every boot | 00:59 |
| uvos | but often | 00:59 |
| uvos | but often | 01:01 |
| uvos | looks like the irq issue happens when a cpu is not active on d3 | 11:08 |
| uvos | when kexec happens | 11:08 |
| uvos | seamspinning the cpus at full speed makes it go away | 11:08 |
| Wizzup | uvos: ah, I think tmlind also mentioned that | 12:03 |
| Wizzup | I don't really see it tbh | 12:03 |
| uvos | Wizzup: have solana firmwares? | 12:31 |
| uvos | https://firmware.center/ is gohne | 12:31 |
| uvos | https://uvos.xyz/maserati/stockinfo/dts/ | 12:39 |
| uvos | here is xt862 dts | 12:39 |
| uvos | decompiled | 12:39 |
| Wizzup | uvos: sec, few mins | 12:54 |
| wunderw | Hi! | 13:16 |
| wunderw | I have a problem with Maemo Leste on my N900 | 13:16 |
| Wizzup | hi | 13:16 |
| Wizzup | what kind of problem? | 13:16 |
| Wizzup | uvos: ping | 13:17 |
| wunderw | I can't run Telegram Desktop | 13:17 |
| uvos | Wizzup: hmm? | 13:17 |
| Wizzup | uvos: do you want VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip ? | 13:17 |
| Wizzup | wunderw: what happens if you run it? | 13:17 |
| uvos | i dont need it anymore atm | 13:17 |
| Wizzup | uvos: ok | 13:17 |
| uvos | i just dded the device tree from the device | 13:17 |
| wunderw | When I try to run TG desktop (installed via apt-get) it automatically closes | 13:17 |
| uvos | Wizzup: but a android 2.3.2 device tree for xt894 would be usefull | 13:18 |
| Wizzup | uvos: how did you decompile it? | 13:18 |
| uvos | i patched dtc | 13:18 |
| Wizzup | care to share that patch please? | 13:18 |
| Wizzup | wunderw: not enough ram maybe? what if you run it from terminal? | 13:18 |
| wunderw | When I run TG in terminal, it stucks on warning related to GLib-GObject-CRITICAL | 13:18 |
| wunderw | I can upload img to imgur if you want | 13:19 |
| Wizzup | sure | 13:19 |
| uvos | Wizzup: btw with leste-config-droid3 | 13:19 |
| uvos | and no accel matrix | 13:19 |
| uvos | in udev | 13:19 |
| uvos | i still have the wrong orientation | 13:19 |
| uvos | its wron 180 deg around y | 13:19 |
| Wizzup | uvos: right I think I still needed to fix that | 13:20 |
| wunderw | I don't have any smartphone in my hand, unfortunately :( Generally, the error looks like that: (telegram-desktop:6543): GLin-GObject-CRITICAL ** <time>: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type' failed | 13:21 |
| Wizzup | wunderw: you can redirect the output | 13:21 |
| Wizzup | telegram-desktop &> log.txt | 13:21 |
| Wizzup | or something | 13:21 |
| wunderw | And GLib-GObject-WARNING **: <time>: cannot register existing type 'GdkDisplayManager' | 13:21 |
| Wizzup | wunderw: where did you get it from btw? | 13:21 |
| wunderw | Apt-get, default devuan repo | 13:22 |
| wunderw | Where I can find log.txt from TG? | 13:22 |
| Wizzup | wait, telegram-desktop is in the debian/devuan repo? | 13:22 |
| uvos | yes | 13:22 |
| wunderw | Yeah | 13:22 |
| Wizzup | o | 13:22 |
| wunderw | But older version | 13:22 |
| uvos | and it works fine on d4 | 13:22 |
| uvos | im not sure why the suprise | 13:23 |
| uvos | its foss | 13:23 |
| Wizzup | maybe it also works better on the new n900 stuff we're working on | 13:23 |
| wunderw | I will try full upgrading via apt-get | 13:23 |
| Wizzup | uvos: yeah I assumed the protocol being proprietary/centralised that the sw would be too | 13:23 |
| wunderw | Maybe it will help | 13:23 |
| uvos | Wizzup: nope | 13:23 |
| Wizzup | uvos: wrt the dts, this seems relevant: | 13:23 |
| Wizzup | bus1devices = "lm3532"; | 13:23 |
| Wizzup | bus2devices = "qtouch-obp-ts,isl29030_als_ir"; | 13:23 |
| Wizzup | bus4devices = "akm8975,kxtf9"; | 13:23 |
| uvos | the protocoll isent proprietary either | 13:23 |
| wunderw | Wow, this channel is really active | 13:23 |
| uvos | just the central server is | 13:24 |
| Wizzup | wunderw: sometimes :) | 13:24 |
| wunderw | Great work, BTW | 13:24 |
| wunderw | I only wait for calling and SMS-es with GUI on N900's Leste ;) | 13:24 |
| Wizzup | wunderw: I can try it on my n900 a bit later today, but I have seen reports of people having it working for them | 13:24 |
| wunderw | What working? | 13:24 |
| wunderw | Leste? | 13:24 |
| Wizzup | wunderw: yeah we're going to push a big update soon that will at least make 3d more stable and get newer kernel | 13:24 |
| wunderw | Wow, very good! | 13:24 |
| Wizzup | wunderw: no, telegram-desktop | 13:24 |
| uvos | Wizzup: right thats why i want old xt894 to compear | 13:24 |
| wunderw | Can't wait :) | 13:24 |
| uvos | since the newer dts is different | 13:25 |
| Wizzup | wunderw: to be clear, people have posted screenshots of telegram-desktop on a droid4 running leste is what I meant | 13:25 |
| Wizzup | uvos: mhm | 13:25 |
| wunderw | It's not-believiable, the device from 2010 can run 5.x.x Linux kernel | 13:25 |
| Wizzup | uvos: I only have VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip | 13:25 |
| wunderw | And even some desktop apps | 13:25 |
| Wizzup | wunderw: :) | 13:25 |
| uvos | thats the version i have too :( | 13:25 |
| uvos | thats 4.0.4 | 13:25 |
| wunderw | Wizzup: Really great work | 13:25 |
| Wizzup | it's the work of many folks over the years | 13:26 |
| wunderw | Yes, the main reason that I don't use Leste as main OS (still Fremantle) (N900 is my daily driver :) ) is lack of calls and SMSs support. And also some other bugs | 13:27 |
| uvos | Wizzup: http://uvos.xyz/maserati/patches | 13:27 |
| uvos | sms should work | 13:28 |
| uvos | with sphone | 13:28 |
| uvos | on n900 | 13:28 |
| uvos | (calls dont) | 13:28 |
| Wizzup | I am planning to switch to leste as daily driver before the end of feb | 13:28 |
| Wizzup | either n900 or d4 | 13:28 |
| Wizzup | maybe d3 | 13:28 |
| uvos | Wizzup: better go write a new audio driver to fix the modem issue then :P | 13:28 |
| Wizzup | wunderw: yeah sms and calls work to some degree, but the UIs either aren't fully there or audio is not working well yet | 13:29 |
| Wizzup | uvos: d4 you mean? well, first tp | 13:29 |
| uvos | yeah | 13:29 |
| Wizzup | that's part of the deadline end of january | 13:29 |
| wunderw | The only things I wait for. Then, Leste as main OS ;) | 13:29 |
| uvos | thats the only thing that stops me using d4 atm | 13:29 |
| Wizzup | wunderw: well make sure to stick around | 13:29 |
| uvos | and flaky gsm, but i can use qmicli | 13:29 |
| uvos | gsm data that is / gprs | 13:29 |
| Wizzup | well that's ofono or kernel fault | 13:29 |
| uvos | did you catch the dtc patch? | 13:30 |
| Wizzup | honestly I think if we fix the sim not being seen when it has a pincode (on boot), we'll fix most ofono problems since they're all similar | 13:30 |
| Wizzup | there seems to be something registered for sim changes already but it doesn't fire | 13:30 |
| Wizzup | uvos: I saw the msg didn't look yet | 13:30 |
| uvos | maybe, modem audio issue is kernel tho | 13:30 |
| wunderw | Just ran TuxPaint on N900 :) | 13:31 |
| uvos | really thats the kernels direct fault cpacp tries to do the right thing even | 13:31 |
| Wizzup | wunderw: :p | 13:31 |
| wunderw | But in tuxpaint-config I can't change any options unfortunately | 13:31 |
| wunderw | They are grey | 13:31 |
| Wizzup | uvos: right, we'll try to fix that at least in our tree | 13:31 |
| Wizzup | wunderw: yeah not everything from the repos will work out of the box currently | 13:32 |
| Wizzup | uvos: saw the patch now, thx | 13:32 |
| wunderw | Beter to use apt-get or apt? | 13:40 |
| Wizzup | no difference | 13:40 |
| wunderw | Ok, thanks | 13:41 |
| wunderw | 79 packages can be upgraded :D | 13:41 |
| wunderw | Is it normal that when I upgrade, the device shutdowns? | 13:44 |
| uvos | nope | 13:47 |
| uvos | its a bug and design deficancy in leste | 13:47 |
| uvos | your system may now be borked | 13:47 |
| wunderw | No, it rebooted and still works | 13:48 |
| uvos | you have to complete the upgrade | 13:48 |
| wunderw | How? | 13:48 |
| wunderw | I ran sudo apt update && sudo apt upgrade | 13:49 |
| Wizzup | yeah just run that again | 13:49 |
| wunderw | Ok | 13:49 |
| wunderw | The following packages have been kept back: hildon-meta libicd-network-ipv4 | 13:50 |
| uvos | Wizzup: current leste-config-droid3 is empty | 13:50 |
| Wizzup | wunderw: dist-upgrade? | 13:51 |
| Wizzup | uvos: hmmm let me look | 13:51 |
| Wizzup | uvos: I think there should be a mce file | 13:52 |
| wunderw | Wizzup: Oh, I used normal upgrade | 13:52 |
| uvos | Wizzup: its not there | 13:52 |
| uvos | Wizzup: dpkg -L lists nothing | 13:52 |
| Wizzup | uvos: looks like the debian/ files are missing | 13:52 |
| Wizzup | wunderw: dist-upgrade is almost always better | 13:52 |
| wunderw | Normal apt upgrade upgraded resolvconf and libicd-network-ipv4 | 13:52 |
| uvos | http://uvos.xyz/maserati/50-iio-sensors.rules | 13:52 |
| Wizzup | uvos: this fix accelerometer? | 13:53 |
| uvos | Wizzup: while at it add that file | 13:53 |
| uvos | fixes accel | 13:53 |
| wunderw | In which phone? | 13:54 |
| uvos | xt860 | 13:54 |
| uvos | accel on n900 is still broken | 13:55 |
| uvos | is several ways | 13:55 |
| Wizzup | wunderw: long story short display rotation on n900 causes crashes but we have made many many changes that will fix it in the next big push of sw updates | 13:57 |
| Wizzup | so we didn't want to enable accelerometer to automatically rotate display since that would crash the display server | 13:57 |
| Wizzup | uvos: btw droid3 -devel image is being built here https://phoenix.maemo.org/job/leste-image-droid3-dev/3/console | 13:57 |
| uvos | also we need to add the i2c address of the n900 accel to the st driver | 13:57 |
| uvos | and fix n900 dts | 13:57 |
| Wizzup | yes but we will do that only after the display is fixed :) | 14:01 |
| Wizzup | btw -devel based images will go here https://maedevu.maemo.org/images-devel/ | 14:01 |
| Wizzup | in ~1.5hrs there should be a droid3 one | 14:01 |
| wunderw | Dist-upgrade helped | 14:11 |
| wunderw | Wizzup: thanks for this link! Will try :) | 14:12 |
| wunderw | Wow, Leste is even for PinePhone :P | 14:12 |
| wunderw | Now I saw the new build! Will dd now to SD ;) | 14:13 |
| Wizzup | wunderw: do you mean new n900 build? it doesn't contain the new stuff yet | 14:20 |
| dreamer | Wizzup: batteries came in. you wanted 2 right? | 14:20 |
| wunderw | Yes | 14:20 |
| Wizzup | dreamer: yes pls | 14:20 |
| wunderw | From dec 26 | 14:20 |
| wunderw | Wizzup: I want to test | 14:20 |
| dreamer | Wizzup: even included bunch of tools and stickers. one for set each battery o.O | 14:20 |
| dreamer | Wizzup: let me know how/where/when you want them :) | 14:21 |
| wunderw | Want to ask, who is the main creator, developer etc. of Leste? | 14:21 |
| wunderw_ | Can you repeat answer? XChat disconnected me :-) | 14:22 |
| dreamer | they are at nurdspace now. when are you back in .nl? can do a little leste-workshop here once everyone has their 3rd shot ;) | 14:22 |
| Wizzup | dreamer: I am in the netherlands for 3 weeks already | 14:23 |
| Wizzup | dreamer: for ~2 more weeks | 14:24 |
| Wizzup | wunderw: there is no one creator, but freemangordon parazyd and me were there at the start, but leste builds on work of many more people before it | 14:24 |
| wunderw_ | Thanks | 14:27 |
| uvos | what kind of battery are we horse trading? | 14:31 |
| Wizzup | uvos: I think some aliexpress d4 battery | 14:44 |
| Wizzup | dreamer: regarding when/where, not sure what makes sense | 14:45 |
| Wizzup | wunderw: regarding testing n900 image, there is a known problem that we don't need to test and freemangordon is working on it, once that is fixed, then it makes sense to test | 14:45 |
| Wizzup | I mean testing the (non existing) -devel image | 14:46 |
| Wizzup | uvos: I think https://nl.aliexpress.com/item/32673985375.html | 14:46 |
| dreamer | Wizzup: ah! I won't be in 020 until 10th | 14:48 |
| uvos | Wizzup: those are oem motorola eb41 with a fake sticker | 14:48 |
| Wizzup | uvos: we'll find out | 14:49 |
| Wizzup | this also looks interesting https://nl.aliexpress.com/item/32865155759.html?spm=a2g0o.productlist.0.0.5ba52dd5FDvTgm&algo_pvid=218dc63b-a298-444d-b825-a0e63b98cd37&algo_exp_id=218dc63b-a298-444d-b825-a0e63b98cd37-1&pdp_ext_f=%7B%22sku_id%22%3A%2265425049439%22%7D&pdp_pi=-1%3B12.24%3B-1%3B-1%40salePrice%3BUSD%3Bsearch-mainSearch | 14:50 |
| Wizzup | uvos: yeah rotation works | 14:59 |
| Wizzup | (d3) | 14:59 |
| uvos | great | 15:18 |
| uvos | looks like you fixed the package | 15:18 |
| uvos | Wizzup: wrt images | 15:23 |
| uvos | i think it would be better if we moved the images to devices we dont currently build/support to images-archive or something like that | 15:24 |
| mighty17[m] | `[ 1.238769] omap-dmtimer-pwm dmtimer-pwm@10: period 31250 ns too short for clock rate 32768 Hz` any clues what the period can be? | 15:24 |
| uvos | so that /images/ contains only xt875 xt894 n900 rpi* and vms | 15:25 |
| mighty17[m] | https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/common/arch/arm/mach-omap2/board-espresso-display.c#L149 downstream says 1200, but what? | 15:25 |
| freemangordon | uvos: why is that? | 15:25 |
| uvos | freemangordon: to make it clear that those images are really out of date | 15:25 |
| uvos | and the underlying devices lack support | 15:25 |
| uvos | or dont work even | 15:25 |
| uvos | like the n9/50 images dont even boot reportably | 15:26 |
| freemangordon | but, aren't those rebuild anyways? | 15:26 |
| uvos | no | 15:26 |
| freemangordon | ah | 15:26 |
| uvos | we only build d4/bionic/n900/pp/rpi/vm and now d3 | 15:26 |
| freemangordon | ok | 15:26 |
| Wizzup | uvos: right regardng images | 15:31 |
| wunderw | uvos: Yes, I tried to run Maemo Leste for N9, wasn't able to | 15:35 |
| Wizzup | wunderw: yeah ok, good point | 15:37 |
| Wizzup | uvos: so something like images-unsupported? | 15:37 |
| uvos | Wizzup: that would be fine yeah | 15:38 |
| uvos | Wizzup: or archive | 15:38 |
| wunderw | Wizzup: the build for N900 from Dec (both) are broken. All of the screen is black, only few interface elements are visible (pink). There are not icons at all. Really strange | 15:41 |
| Wizzup | I am not too surprised, we haven't tested that one yet | 15:42 |
| Wizzup | sounds like hildon-desktop not starting | 15:42 |
| wunderw | Possible. Flashing again the older build | 15:44 |
| Wizzup | uvos: untested https://maedevu.maemo.org/images-devel/droid3/20211230/ | 16:05 |
| Wizzup | wunderw: I see the same on the images, looks like some theme symlink is messed up | 17:15 |
| Wizzup | uvos: the image is not working, at least theme seems broken, maybe more | 17:20 |
| Wizzup | I wonder what broke this, no icons load, no images either | 17:31 |
| Wizzup | ** (/usr/bin/hildon-desktop:4374): WARNING **: 16:30:59.350: hd_launcher_tile_set_icon_name: couldn't create texture for /usr/share/pixmaps/htop.png | 17:32 |
| Wizzup | ** (/usr/bin/hildon-desktop:4374): WARNING **: 16:30:59.411: hd_launcher_tile_set_icon_name: couldn't create texture for /usr/share/pixmaps/debian-logo.png | 17:32 |
| Wizzup | etc | 17:32 |
| Wizzup | afk | 17:32 |
| Wizzup | freemangordon: could this be the glib patch somehow? | 18:08 |
| Wizzup | parazyd: maybe the resolv.conf change somehow affects arm-sdk ? | 18:10 |
| Wizzup | parazyd: it's not clear to me what exact step is failing | 18:11 |
| Wizzup | in say https://phoenix.maemo.org/view/Images/job/leste-image-droid3-dev/4/consoleText | 18:11 |
| Wizzup | I think it' | 18:12 |
| Wizzup | s probably not related looking at the blend but it's suspicious it fails | 18:12 |
| parazyd | I'll check. There should be a hardcoded resolv.conf in that stage | 18:15 |
| parazyd | I dunno what's the problem. | 18:16 |
| freemangordon | Wizzup: how's that? | 18:17 |
| freemangordon | Wizzup: I don;t see how it could be related | 18:18 |
| freemangordon | it is about .desktop files, nothing in common with ions | 18:18 |
| freemangordon | *icons | 18:19 |
| Wizzup | gdk_pixbuf_new_from_file_at_size seems to fail | 18:19 |
| Wizzup | more specifically: | 18:20 |
| Wizzup | pixbuf = gdk_pixbuf_new_from_file_at_size(fname, HD_LAUNCHER_TILE_ICON_REAL_SIZE, HD_LAUNCHER_TILE_ICON_REAL_SIZE, 0); | 18:20 |
| Wizzup | could be something else is up, but the file path it prints definitely loads | 18:20 |
| Wizzup | hmm: | 18:22 |
| Wizzup | (osso-xterm:5923): sapwood-engine-WARNING **: 17:22:29.650: sapwood-theme: Failed to load pixmap file /usr/share/themes/alpha/images/toolbar_button_normal.png: read 1, expected 80 bytes | 18:22 |
| * Wizzup reinstalls theme | 18:24 | |
| Wizzup | I don't know what is up | 18:25 |
| Wizzup | (sapwood-server:6040): sapwood-server-WARNING **: 17:25:41.264: /usr/share/themes/alpha/images/toolbar_button_normal.png: Couldn?t recognize the image file format for file ?/usr/share/themes/alpha/images/toolbar_button_normal.png? | 18:25 |
| freemangordon | broken fs? | 18:26 |
| Wizzup | freemangordon: reinstalled, same file sizes | 18:29 |
| Wizzup | and my d4 has the same | 18:30 |
| Wizzup | it looks very much like sapwood not working ok | 18:31 |
| Wizzup | it also seems to happen to stable images afaict | 18:31 |
| Wizzup | parazyd: 15:41 < wunderw> Wizzup: the build for N900 from Dec (both) are broken. All of the screen is black, only few interface elements are visible (pink). There are not icons at all. Really strange | 18:32 |
| Wizzup | I also confirm this on -devel images | 18:32 |
| Wizzup | freemangordon: seems unlikely to be broken fs since I just flashed and it also happened for this guy using stable image | 18:32 |
| Wizzup | /etc/hildon/theme seems ok | 18:32 |
| Wizzup | as is /usr/share/themes/default | 18:32 |
| Wizzup | it very much looks like glib-based file reading not working, since it affects h-d and sapwood | 18:34 |
| Wizzup | also: | 18:36 |
| Wizzup | ** (controlpanel:6561): WARNING **: 17:36:38.789: Couldn't load icon "general_locked": Unrecognized image file format | 18:36 |
| Wizzup | maybe it's mime type related? | 18:37 |
| Wizzup | that's the only thing I can think of that changed | 18:37 |
| freemangordon | makes sense | 18:40 |
| freemangordon | but I don;t see how it would be glib related | 18:40 |
| freemangordon | I made some changes to libhilodnmime | 18:40 |
| freemangordon | but it just adds one more binary that creates a cache file | 18:40 |
| freemangordon | It should not break mime handling, in theory | 18:40 |
| freemangordon | Wizzup: do we have install log? | 18:42 |
| freemangordon | do we have shell? | 18:43 |
| Wizzup | freemangordon: dinner first sry | 18:44 |
| Wizzup | I have ssh yes | 18:44 |
| freemangordon | ok, ping me when you're back | 18:44 |
| freemangordon | no issue booting maemo-leste-1.0-amd64-20211226.vdi | 19:00 |
| Wizzup | ok | 19:20 |
| Wizzup | freemangordon: ping | 19:20 |
| freemangordon | pong | 19:21 |
| freemangordon | what "gio mime text/plain" says? | 19:21 |
| Wizzup | $ gio mime text/plain | 19:22 |
| Wizzup | -bash: gio: command not found | 19:22 |
| freemangordon | hmm | 19:22 |
| Wizzup | I also found mimetype is not installed | 19:22 |
| Wizzup | which belongs to libfile-mimeinfo-perl | 19:22 |
| Wizzup | shall I install that and see what happens | 19:22 |
| freemangordon | sec | 19:22 |
| freemangordon | hmm | 19:23 |
| freemangordon | libglib2.0-bin should be installed, unless I am missing something | 19:23 |
| freemangordon | Wizzup: better install libglib2.0-bin | 19:23 |
| Wizzup | ok, sec | 19:23 |
| Wizzup | $ gio mime text/plain | 19:24 |
| Wizzup | Default application for “text/plain”: vim.desktop | 19:24 |
| Wizzup | Registered applications: vim.desktop debian-vim.desktop | 19:24 |
| Wizzup | Recommended applications: vim.desktop debian-vim.desktop | 19:24 |
| freemangordon | so mime is ok | 19:24 |
| Wizzup | at least for text/plain | 19:24 |
| Wizzup | it might be messed up badly if this tool is needed during any preinstall | 19:24 |
| freemangordon | check /usr/share/mime | 19:25 |
| Wizzup | don't know what to check but seems ok | 19:26 |
| freemangordon | but mime should not be used by gdk_pixbuf_new_from_file_at_size | 19:26 |
| Wizzup | in any case I attached gdb to hildon-desktop and I found that that function (you just mentioned) returns NULL | 19:26 |
| Wizzup | for correct path | 19:26 |
| freemangordon | what is the filesize of that file? | 19:26 |
| Wizzup | no icon is loaded | 19:26 |
| Wizzup | any | 19:26 |
| Wizzup | at any point in any hildon part | 19:27 |
| Wizzup | hildon-desktop, hildon-home, osso-xterm, controlpanel | 19:27 |
| freemangordon | yeah, got that | 19:27 |
| Wizzup | the file syzes were the same as on the d4 | 19:27 |
| Wizzup | (which works fine) | 19:27 |
| Wizzup | sizes* | 19:27 |
| freemangordon | ok, d4 works, vm works | 19:27 |
| Wizzup | no, hang on | 19:27 |
| Wizzup | *my* droid4 works | 19:27 |
| Wizzup | I am not saying the droid4 image works | 19:27 |
| freemangordon | so somehting must have failed during install on n900 | 19:27 |
| Wizzup | I am testing this on a droid3, with an image I just built on the CI | 19:27 |
| freemangordon | do we have image build log? | 19:27 |
| Wizzup | and it doesn't work | 19:27 |
| freemangordon | ah | 19:28 |
| Wizzup | it has the same problems as the n900 image from a few days ago, which was not -devel | 19:28 |
| Wizzup | that is, status area and top left are purple | 19:28 |
| Wizzup | everything else is black | 19:28 |
| Wizzup | which reminded me of the times the theme was not set up ok | 19:28 |
| freemangordon | wait, is this the same issue as on n900 or not? | 19:28 |
| Wizzup | but the theme looks to be ok | 19:28 |
| Wizzup | yes | 19:28 |
| Wizzup | build log is here: https://phoenix.maemo.org/view/Images/job/leste-image-droid3-dev/4/consoleText | 19:28 |
| freemangordon | symlink is ther? | 19:28 |
| Wizzup | yes | 19:28 |
| Wizzup | if you mean $ ls /etc/hildon/theme -lsh | 19:29 |
| Wizzup | 0 lrwxrwxrwx 1 root root 25 Dec 30 17:35 /etc/hildon/theme -> /usr/share/themes/default | 19:29 |
| Wizzup | $ ls -lsh /usr/share/themes/default | 19:29 |
| Wizzup | 0 lrwxrwxrwx 1 root root 23 Dec 30 17:35 /usr/share/themes/default -> /usr/share/themes/alpha | 19:29 |
| freemangordon | mhm | 19:29 |
| Wizzup | parazyd: looks like we still have debugfs not loaded btw | 19:29 |
| Wizzup | s/loaded/mounted/ | 19:29 |
| freemangordon | Wizzup: shall I write some small test app for you to run strace on? | 19:31 |
| Wizzup | freemangordon: I suppose, but I can also strace say osso-xterm | 19:31 |
| freemangordon | hmm, ok | 19:31 |
| freemangordon | please do | 19:31 |
| freemangordon | you will need ti run it by using maemo-summoner I suppose | 19:32 |
| Wizzup | I have been doing that | 19:33 |
| Wizzup | d3 stuck on shutdown because of the kernel oops I think | 19:33 |
| * Wizzup removes battery and restarts | 19:33 | |
| Wizzup | freemangordon: doesn't show anything out of the ordinary | 19:38 |
| Wizzup | in fact it is indistinguishable from broken and non-broken | 19:38 |
| freemangordon | hmm | 19:40 |
| Wizzup | at least anything that refers to those icon names I think | 19:41 |
| freemangordon | Failed to load pixmap file /usr/share/themes/alpha/images/toolbar_button_normal.png: read 1, expected 80 bytes | 19:41 |
| freemangordon | read 1, expected 80 | 19:41 |
| Wizzup | I think this is an error in sapwood | 19:41 |
| Wizzup | not osso-xterm | 19:42 |
| freemangordon | yes | 19:42 |
| freemangordon | but 'read 1' | 19:42 |
| Wizzup | want me to strace that instead? | 19:42 |
| Wizzup | yeah it is weird but could be anything | 19:42 |
| freemangordon | some 32 bits issue? | 19:42 |
| Wizzup | some *new* 32 bits issue maybe | 19:42 |
| freemangordon | mhm | 19:42 |
| freemangordon | yes, please strace sapwood-server | 19:42 |
| Wizzup | https://dpaste.com/BCTEYFQ8P | 19:43 |
| Wizzup | looks fine to me | 19:43 |
| Wizzup | 4.0K -rw-r--r-- 1 root root 154 Jun 28 2021 /usr/share/themes/devel/images/toolbar_button_normal.png | 19:43 |
| freemangordon | right | 19:44 |
| Wizzup | something else that is odd, for osso-xterm, it only prints this for this png | 19:44 |
| Wizzup | not for others | 19:44 |
| Wizzup | maybe it has just one icon :) | 19:44 |
| freemangordon | not really | 19:44 |
| Wizzup | but again, h-d also cannot open pngs | 19:44 |
| freemangordon | but anyways, it seems to be on the other side | 19:45 |
| Wizzup | I see this in sapwood: | 19:45 |
| Wizzup | 2964 write(2, "\n(sapwood-server:2964): sapwood-server-\33[1;33mWARNING\33[0m **: \33[34m18:45:22.247\33[0m: /usr/share/themes/devel/images/toolbar_button_normal.png: Couldn?t recognize the image file format for file ?/usr/share/themes/devel/images/toolbar_button_normal.png?\n", 252) = 252 | 19:45 |
| Wizzup | which I also mentioned above | 19:46 |
| freemangordon | ah, so sapwood-server complains? | 19:47 |
| Wizzup | yes | 19:47 |
| freemangordon | sec | 19:47 |
| Wizzup | but it *must* be some underlying library | 19:47 |
| Wizzup | since it happens everywhere | 19:47 |
| freemangordon | mhm | 19:47 |
| freemangordon | lemme check the code | 19:47 |
| freemangordon | hmm, this error message comes from elsewhere, not from sapwood itself, iiuc | 19:49 |
| freemangordon | Wizzup: do you have XDG_DATA_DIRS set? | 19:50 |
| Wizzup | not on faulty droid3 and not on working droid4 | 19:51 |
| freemangordon | ok | 19:52 |
| freemangordon | checking one more thing | 19:52 |
| freemangordon | Wizzup: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders, modified for 32 bits | 19:53 |
| freemangordon | I bet this one differs on 2 devices | 19:55 |
| Wizzup | I was looking at that just now | 19:55 |
| Wizzup | doesn't look like it | 19:56 |
| Wizzup | I'll paste | 19:56 |
| Wizzup | https://dpaste.com/4ZWM2YG99 droid3 | 19:57 |
| Wizzup | wait let me run it as user to be sure | 19:57 |
| freemangordon | hmm, yeah,looks fine | 19:57 |
| Wizzup | droid3: https://dpaste.com/EMBPTGNYH droid4: https://dpaste.com/9LR83AVF5 | 19:57 |
| freemangordon | but we're getting close | 19:57 |
| Wizzup | yup | 19:57 |
| Wizzup | something is truly messed up | 19:58 |
| freemangordon | ldd /usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so ? | 19:58 |
| Wizzup | do you want to compare? | 19:59 |
| Wizzup | they look the same on d3 and d4 | 19:59 |
| freemangordon | ok | 19:59 |
| freemangordon | hmm | 19:59 |
| freemangordon | wait, you said you don;t have XDG_DATA_DIRS set for which user? | 19:59 |
| Wizzup | all devices do not have that set for usersyes | 19:59 |
| Wizzup | user yes | 19:59 |
| Wizzup | user@maindroid:~$ env|grep XDG | 20:00 |
| Wizzup | XDG_RUNTIME_DIR=/run/user/1000 | 20:00 |
| freemangordon | could you run-standalone.sh bach | 20:00 |
| freemangordon | *bash | 20:00 |
| freemangordon | and then check XDG stuff | 20:00 |
| freemangordon | I have XDG_SESSION_COOKIE=devuan-1640512024.348006-1839873804 here | 20:00 |
| Wizzup | no difference | 20:01 |
| Wizzup | on both devices | 20:01 |
| freemangordon | no XDG_SESSION_COOKIE? | 20:01 |
| Wizzup | no | 20:01 |
| freemangordon | hmm, why do I have that here | 20:01 |
| freemangordon | in the VM that is | 20:01 |
| Wizzup | don't know but unlikely to relate to png file parsing | 20:01 |
| freemangordon | yeah | 20:01 |
| Wizzup | too bad that h-d doesn't even log the error of gdk_pixbuf_new_from_file_at_size | 20:03 |
| Wizzup | although I suppose it will be the same: cannot recognize image format | 20:03 |
| freemangordon | gdk-pixbuf-query-loaders > /usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders.cache | 20:04 |
| freemangordon | update-mime-database /usr/share/mime | 20:04 |
| freemangordon | I guess as root | 20:05 |
| Wizzup | see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234784#c4 | 20:05 |
| Wizzup | freemangordon: ok let me try | 20:05 |
| Wizzup | fwiw /usr/lib/arm-linux-gnueabihf/gdk-pixbuf-2.0/2.10.0/loaders.cache are the same on both devices before updating | 20:05 |
| freemangordon | ok | 20:06 |
| Wizzup | freemangordon: yes, update-mime-database solved it | 20:06 |
| freemangordon | hmm | 20:06 |
| freemangordon | why it is not called? | 20:06 |
| Wizzup | parazyd: ^^^^^ | 20:06 |
| parazyd | That should be part of some postinst | 20:07 |
| freemangordon | I see no update-mime-database call in build log | 20:07 |
| Wizzup | freemangordon: I do see this: | 20:07 |
| Wizzup | * Updating MIME database in /usr/share/mime... | 20:07 |
| freemangordon | shared-mime-info | 20:07 |
| freemangordon | Wizzup: this is from hildon-update-=category-database | 20:08 |
| Wizzup | right | 20:08 |
| freemangordon | Processing triggers for shared-mime-info (1.10-1) | 20:08 |
| freemangordon | and nothing | 20:09 |
| Wizzup | yeah and then nothing happens | 20:09 |
| Wizzup | you're sure it's in that postinst? | 20:09 |
| Wizzup | triggers are not the same as postinst fwiw | 20:09 |
| freemangordon | not sure | 20:09 |
| freemangordon | this is not our package | 20:09 |
| Wizzup | I would expect it to happen here: Setting up shared-mime-info (1.10-1) ... | 20:09 |
| freemangordon | mhm | 20:09 |
| freemangordon | getting source, lemme check | 20:09 |
| Wizzup | I suppose I can reflash the image and apt --reinstall shared-mime-info | 20:10 |
| Wizzup | freemangordon: fwiw here is the vm build log https://phoenix.maemo.org/view/Images/job/leste-image-virtual/83/consoleText | 20:10 |
| freemangordon | looks good to me https://pastebin.com/VWW4ewmn | 20:11 |
| freemangordon | Wizzup: no idea :( | 20:12 |
| Wizzup | same. | 20:12 |
| Wizzup | this is truly SNAFU | 20:12 |
| freemangordon | but yeah, please reflash and reinstall | 20:12 |
| Wizzup | k | 20:12 |
| freemangordon | parazyd: is it possible /me adding a trigger in another package to break this? | 20:12 |
| freemangordon | this https://github.com/maemo-leste/libhildonmime/blob/master/debian/hildon-update-category-database.triggers | 20:13 |
| parazyd | What do you mean with "trigger"? | 20:13 |
| freemangordon | parazyd: ^^^ | 20:13 |
| parazyd | hmm perhaps. I don't know what those do | 20:13 |
| Wizzup | well I think the point is that we seemingly didn't change anything but the mime files of (most?) images are broken to the point it cannot even load a single png | 20:14 |
| Wizzup | and the fix is to run update-mime-database | 20:14 |
| Wizzup | but that must already get run | 20:14 |
| freemangordon | mhm | 20:14 |
| freemangordon | but I don;t see it being run | 20:14 |
| freemangordon | which means postinst didn;t get called, IIUC | 20:14 |
| Wizzup | so perhaps we set some env var now that causes the postinst not to run or something, or it runs too soon, or whatever... | 20:14 |
| Wizzup | I suppose we could force-add the call to arm-sdk or something | 20:19 |
| Wizzup | anyway I'll reflash | 20:20 |
| freemangordon | Wizzup: I think we shall find the reason for postinst not being called | 20:20 |
| freemangordon | we could have similar breaks elsewhere | 20:20 |
| Wizzup | it might get called as well, but the file just not kept | 20:21 |
| Wizzup | fwiw there is also /var/lib/dpkg/info/shared-mime-info.postinst | 20:22 |
| freemangordon | hmm, is it possible that hildon-update-category-database breaks mime info somehow? | 20:22 |
| Wizzup | and that definitely contains a check for triggered | 20:23 |
| Wizzup | freemangordon: maybe, can check | 20:23 |
| Wizzup | dd'ing now | 20:23 |
| freemangordon | Wizzup: could you save /usr/share/mime before reinstalling? | 20:23 |
| Wizzup | too late | 20:24 |
| Wizzup | but I can re-run after dd | 20:24 |
| freemangordon | no, I mean the broken one | 20:24 |
| freemangordon | so we can compare after fixing | 20:24 |
| freemangordon | well, why VM is not broken tren?!? | 20:26 |
| Wizzup | freemangordon: I understand, I will cp before fixing | 20:27 |
| Wizzup | but the dd already started when you asked | 20:27 |
| freemangordon | that's fine as you can;t get the broken one without dd :) | 20:28 |
| Wizzup | freemangordon: regarding the triggers, that seems likely the cause somehow | 20:33 |
| Wizzup | does the shared mime info package also have those triggers | 20:34 |
| freemangordon | I guess yes, but I would expect more that one trigger per directory to be allowed | 20:34 |
| * freemangordon checks | 20:34 | |
| Wizzup | yeah me too | 20:34 |
| Wizzup | https://manpages.debian.org/unstable/dpkg-dev/deb-triggers.5.en.html | 20:35 |
| Wizzup | https://wiki.debian.org/DpkgTriggers | 20:35 |
| Wizzup | https://sources.debian.org/src/dpkg/1.21.1/doc/triggers.txt/ | 20:35 |
| freemangordon | well, I see no issue with what I did | 20:38 |
| freemangordon | unless i am missing something | 20:38 |
| Wizzup | fwiw wl12xx is also not probed on d3 | 20:38 |
| Wizzup | unless I probe it manually | 20:38 |
| Wizzup | I also feel like we need to provide some default nameserver to dnsmasq | 20:40 |
| freemangordon | hmm, hmm | 20:40 |
| Wizzup | in case of ethernet or usbnet | 20:40 |
| Wizzup | https://dpaste.com/G6ZCFNC5Z | 20:40 |
| Wizzup | freemangordon: is it possible your trigger exits with non zero exit code | 20:40 |
| freemangordon | I doubt | 20:41 |
| freemangordon | https://github.com/maemo-leste/libhildonmime/blob/master/debian/hildon-update-category-database.postinst#L8 | 20:41 |
| Wizzup | hmm | 20:41 |
| Wizzup | in any case the --reinstall works | 20:42 |
| Wizzup | let me share old and new mime dirs | 20:42 |
| Wizzup | https://wizzup.org/mimes.tar.bz2 | 20:43 |
| Wizzup | freemangordon: # cat /var/lib/dpkg/info/hildon-update-category-database.postinst | 20:43 |
| Wizzup | #! /bin/sh | 20:43 |
| Wizzup | is that valid, with the space? | 20:43 |
| freemangordon | hmm, is it possible there is no /usr/share/mime by the time hildon-update-category-database is run? | 20:43 |
| freemangordon | yes, it is | 20:43 |
| Wizzup | ok | 20:43 |
| Wizzup | weird | 20:43 |
| freemangordon | see my question ^^^ | 20:44 |
| Wizzup | I have no idea what installs into /usr/share/mime | 20:44 |
| Wizzup | or what creates it | 20:44 |
| freemangordon | shared-mime-info, hildon-application-manager, osso-pdf-viewer, gcr, meld: /usr/share/mime | 20:44 |
| Wizzup | # dpkg -S /usr/share/mime | 20:44 |
| Wizzup | shared-mime-info, hildon-application-manager, osso-pdf-viewer: /usr/share/mime | 20:44 |
| Wizzup | right | 20:44 |
| freemangordon | mhm | 20:44 |
| Wizzup | maybe you can have it depend on shared-mime-info in any case | 20:44 |
| freemangordon | right | 20:44 |
| freemangordon | lemme see what is the $? if non-existent dir is passed | 20:45 |
| Wizzup | ok | 20:45 |
| Wizzup | please also fix the space in the shebang | 20:45 |
| Wizzup | it's confusing | 20:45 |
| Wizzup | I've never seen it | 20:46 |
| freemangordon | yep. sudo hildon-update-category-database /usr/share/mimes gives exit code 1 | 20:46 |
| Wizzup | I think this is probably the problem | 20:46 |
| freemangordon | mhm | 20:46 |
| freemangordon | or, I can just create that dir | 20:46 |
| Wizzup | better to depend on shared-mime-info | 20:46 |
| Wizzup | imho | 20:46 |
| Wizzup | but in any case | 20:47 |
| Wizzup | it still should not cause the postinst to return non-zero | 20:47 |
| Wizzup | if I read it correctly | 20:47 |
| Wizzup | so I don't see how fixing that would help | 20:47 |
| Wizzup | it is set -e no? | 20:47 |
| freemangordon | yes | 20:47 |
| Wizzup | maybe see what the postinst returns | 20:47 |
| Wizzup | if there is no dir | 20:47 |
| Wizzup | maybe it is the shebang somehow :) | 20:48 |
| freemangordon | "-e Exit immediately if a command exits with a non-zero status." | 20:48 |
| freemangordon | nothing wrong with the shebang | 20:48 |
| Wizzup | oh | 20:48 |
| Wizzup | I always confuse -e and +e | 20:48 |
| Wizzup | :) | 20:48 |
| Wizzup | -e to me sounds no "minus errors" | 20:49 |
| freemangordon | I don;t because I know neither :) | 20:49 |
| Wizzup | sounds like | 20:49 |
| Wizzup | yeah I know it controls if shell exits right away if any process erors | 20:49 |
| freemangordon | anyway, I think this is it, will make it depend on | 20:49 |
| Wizzup | but I always forget what is - and what is + | 20:49 |
| Wizzup | ok | 20:49 |
| freemangordon | maybe pre-depends? | 20:49 |
| freemangordon | Wizzup: how we're going to test that? | 20:50 |
| Wizzup | freemangordon: test what? | 20:53 |
| freemangordon | image building with fixed package | 20:53 |
| Wizzup | I will trigger another build | 20:53 |
| Wizzup | you can push to -devel | 20:53 |
| freemangordon | ok | 20:53 |
| freemangordon | ok | 20:53 |
| Wizzup | my droid3 image uses -devel | 20:53 |
| Wizzup | :) | 20:53 |
| Wizzup | uvos: btw I still see hangs sometimes on droid3, do you see them as well? | 22:10 |
| Wizzup | freemangordon: any idea how telepathy-logger works? | 23:02 |
| Wizzup | it seems useful but I don't see any users of it really | 23:02 |
| freemangordon | I think there are plugins to it | 23:04 |
| freemangordon | which expose dbus interfaces | 23:04 |
| freemangordon | but that's all I know about it | 23:04 |
| freemangordon | image seems to be almost ready. lets hope it is fixed | 23:05 |
| Wizzup | I mean it seems to suggest it logs somewhere | 23:11 |
| Wizzup | and you can read the logs | 23:11 |
| Wizzup | but maybe I am misunderstanding it | 23:11 |
| Wizzup | fremantle doesn't use it | 23:11 |
| Wizzup | so I guess we will not use it | 23:14 |
| Wizzup | ah they have log store plugins | 23:15 |
| Wizzup | that is interesting | 23:15 |
| Wizzup | https://github.com/TelepathyIM/telepathy-logger/blob/master/telepathy-logger/log-store-empathy.c | 23:16 |
| Wizzup | we could make a log-store-rtcom | 23:16 |
| Wizzup | hm I think it only reads and doesn't write | 23:17 |
| Wizzup | https://github.com/TelepathyIM/telepathy-logger/blob/master/telepathy-logger/log-store-sqlite.c | 23:18 |
| Wizzup | looks like there is some add_event | 23:19 |
| Wizzup | hmm https://github.com/TelepathyIM/telepathy-logger/blob/master/telepathy-logger/log-store-sqlite.c#L90 | 23:20 |
| freemangordon | Wizzup: image is ready | 23:27 |
| Wizzup | yes | 23:28 |
| Wizzup | I am downloading already | 23:28 |
| freemangordon | ok, please LMK if it is ok | 23:29 |
| Wizzup | working on it | 23:29 |
| Wizzup | so I think telepathy-logger could be interesting potentially | 23:32 |
| Wizzup | we could just use it's binary and write a rtcom plugin | 23:32 |
| Wizzup | then we don't need a logger per program | 23:32 |
| Wizzup | i.e. sphone could drop it's tp interface | 23:32 |
| Wizzup | but it's also relatively limited in what it does, so maybe it's not that useful | 23:32 |
| freemangordon | does it store enough info? | 23:33 |
| Wizzup | well we will have to fork it anyway to add our plugin | 23:33 |
| Wizzup | (most of the code is untouched for years) | 23:33 |
| Wizzup | but I am not sure if it makes sense to have it | 23:33 |
| freemangordon | why fork? | 23:33 |
| Wizzup | the plugins are built in it seems | 23:33 |
| freemangordon | I am almost sure it can be extended, lemme check | 23:34 |
| Wizzup | the htmldoc is pretty poor too | 23:34 |
| Wizzup | and my fav. telepathy guide doesn't even log it | 23:34 |
| Wizzup | en the tp homepage 404's for the telepathy-logger | 23:35 |
| Wizzup | (not saying we should not use it, just some things that discouraged me a bit from using it) | 23:35 |
| Wizzup | (dd almost done) | 23:35 |
| Wizzup | freemangordon: still broken it looks like :( | 23:39 |
| freemangordon | :( | 23:39 |
| freemangordon | ok, going to have some sleep, will see what we can do tomorrow | 23:40 |
| Wizzup | maybe focus on the n900 stuff, I can get this fixed surely | 23:40 |
| freemangordon | yeah | 23:41 |
| freemangordon | night! | 23:41 |
| Wizzup | freemangordon: we can also run it at the end of the arm-sdk for now | 23:42 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!