<wunderw>
I have a problem with Maemo Leste on my N900
<Wizzup>
hi
<Wizzup>
what kind of problem?
mardy has quit [Quit: WeeChat 2.8]
<Wizzup>
uvos: ping
<wunderw>
I can't run Telegram Desktop
<uvos>
Wizzup: hmm?
<Wizzup>
uvos: do you want VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip ?
<Wizzup>
wunderw: what happens if you run it?
<uvos>
i dont need it anymore atm
<Wizzup>
uvos: ok
<uvos>
i just dded the device tree from the device
<wunderw>
When I try to run TG desktop (installed via apt-get) it automatically closes
<uvos>
Wizzup: but a android 2.3.2 device tree for xt894 would be usefull
<Wizzup>
uvos: how did you decompile it?
<uvos>
i patched dtc
<Wizzup>
care to share that patch please?
<Wizzup>
wunderw: not enough ram maybe? what if you run it from terminal?
<wunderw>
When I run TG in terminal, it stucks on warning related to GLib-GObject-CRITICAL
<wunderw>
I can upload img to imgur if you want
<Wizzup>
sure
<uvos>
Wizzup: btw with leste-config-droid3
<uvos>
and no accel matrix
<uvos>
in udev
<uvos>
i still have the wrong orientation
<uvos>
its wron 180 deg around y
<Wizzup>
uvos: right I think I still needed to fix that
<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
<Wizzup>
wunderw: you can redirect the output
<Wizzup>
telegram-desktop &> log.txt
<Wizzup>
or something
<wunderw>
And GLib-GObject-WARNING **: <time>: cannot register existing type 'GdkDisplayManager'
<Wizzup>
wunderw: where did you get it from btw?
<wunderw>
Apt-get, default devuan repo
<wunderw>
Where I can find log.txt from TG?
<Wizzup>
wait, telegram-desktop is in the debian/devuan repo?
<uvos>
yes
<wunderw>
Yeah
<Wizzup>
o
<wunderw>
But older version
<uvos>
and it works fine on d4
<uvos>
im not sure why the suprise
<uvos>
its foss
<Wizzup>
maybe it also works better on the new n900 stuff we're working on
<wunderw>
I will try full upgrading via apt-get
<Wizzup>
uvos: yeah I assumed the protocol being proprietary/centralised that the sw would be too
<wunderw>
I only wait for calling and SMS-es with GUI on N900's Leste ;)
<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
<wunderw>
What working?
<wunderw>
Leste?
<Wizzup>
wunderw: yeah we're going to push a big update soon that will at least make 3d more stable and get newer kernel
<wunderw>
Wow, very good!
<Wizzup>
wunderw: no, telegram-desktop
<uvos>
Wizzup: right thats why i want old xt894 to compear
<wunderw>
Can't wait :)
<uvos>
since the newer dts is different
<Wizzup>
wunderw: to be clear, people have posted screenshots of telegram-desktop on a droid4 running leste is what I meant
<Wizzup>
uvos: mhm
<wunderw>
It's not-believiable, the device from 2010 can run 5.x.x Linux kernel
<Wizzup>
uvos: I only have VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
<wunderw>
And even some desktop apps
<Wizzup>
wunderw: :)
<uvos>
thats the version i have too :(
<uvos>
thats 4.0.4
<wunderw>
Wizzup: Really great work
<Wizzup>
it's the work of many folks over the years
<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
<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
<Wizzup>
so we didn't want to enable accelerometer to automatically rotate display since that would crash the display server
<wunderw>
Wizzup: thanks for this link! Will try :)
<wunderw>
Wow, Leste is even for PinePhone :P
<wunderw>
Now I saw the new build! Will dd now to SD ;)
<Wizzup>
wunderw: do you mean new n900 build? it doesn't contain the new stuff yet
<dreamer>
Wizzup: batteries came in. you wanted 2 right?
<wunderw>
Yes
<Wizzup>
dreamer: yes pls
<wunderw>
From dec 26
<wunderw>
Wizzup: I want to test
<dreamer>
Wizzup: even included bunch of tools and stickers. one for set each battery o.O
<dreamer>
Wizzup: let me know how/where/when you want them :)
<wunderw>
Want to ask, who is the main creator, developer etc. of Leste?
wunderw_ has joined #maemo-leste
<wunderw_>
Can you repeat answer? XChat disconnected me :-)
<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 ;)
<Wizzup>
dreamer: I am in the netherlands for 3 weeks already
<Wizzup>
dreamer: for ~2 more weeks
<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
<wunderw_>
Thanks
inky has quit [Ping timeout: 240 seconds]
wunderw_ has quit [Quit: Leaving]
inky has joined #maemo-leste
<uvos>
what kind of battery are we horse trading?
<Wizzup>
uvos: I think some aliexpress d4 battery
<Wizzup>
dreamer: regarding when/where, not sure what makes sense
<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
<Wizzup>
I mean testing the (non existing) -devel image
<uvos>
freemangordon: to make it clear that those images are really out of date
<uvos>
and the underlying devices lack support
<uvos>
or dont work even
<uvos>
like the n9/50 images dont even boot reportably
<freemangordon>
but, aren't those rebuild anyways?
<uvos>
no
<freemangordon>
ah
<uvos>
we only build d4/bionic/n900/pp/rpi/vm and now d3
<freemangordon>
ok
<Wizzup>
uvos: right regardng images
<wunderw>
uvos: Yes, I tried to run Maemo Leste for N9, wasn't able to
<Wizzup>
wunderw: yeah ok, good point
<Wizzup>
uvos: so something like images-unsupported?
<uvos>
Wizzup: that would be fine yeah
<uvos>
Wizzup: or archive
<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
<Wizzup>
I am not too surprised, we haven't tested that one yet
<Wizzup>
sounds like hildon-desktop not starting
<wunderw>
Possible. Flashing again the older build
<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?
<freemangordon>
broken fs?
<Wizzup>
freemangordon: reinstalled, same file sizes
<Wizzup>
and my d4 has the same
<Wizzup>
it looks very much like sapwood not working ok
<Wizzup>
it also seems to happen to stable images afaict
<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
<Wizzup>
I also confirm this on -devel images
<Wizzup>
freemangordon: seems unlikely to be broken fs since I just flashed and it also happened for this guy using stable image
<Wizzup>
/etc/hildon/theme seems ok
<Wizzup>
as is /usr/share/themes/default
<Wizzup>
it very much looks like glib-based file reading not working, since it affects h-d and sapwood
<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
<Wizzup>
and the fix is to run update-mime-database
<Wizzup>
but that must already get run
<freemangordon>
mhm
<freemangordon>
but I don;t see it being run
<freemangordon>
which means postinst didn;t get called, IIUC
<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...
<Wizzup>
I suppose we could force-add the call to arm-sdk or something
<Wizzup>
anyway I'll reflash
<freemangordon>
Wizzup: I think we shall find the reason for postinst not being called
<freemangordon>
we could have similar breaks elsewhere
<Wizzup>
it might get called as well, but the file just not kept
<Wizzup>
fwiw there is also /var/lib/dpkg/info/shared-mime-info.postinst
<freemangordon>
hmm, is it possible that hildon-update-category-database breaks mime info somehow?
<Wizzup>
and that definitely contains a check for triggered
<Wizzup>
freemangordon: maybe, can check
<Wizzup>
dd'ing now
<freemangordon>
Wizzup: could you save /usr/share/mime before reinstalling?
<Wizzup>
too late
<Wizzup>
but I can re-run after dd
<freemangordon>
no, I mean the broken one
<freemangordon>
so we can compare after fixing
<freemangordon>
well, why VM is not broken tren?!?
<Wizzup>
freemangordon: I understand, I will cp before fixing
<Wizzup>
but the dd already started when you asked
<freemangordon>
that's fine as you can;t get the broken one without dd :)
belcher has quit [Ping timeout: 268 seconds]
inky has quit [Ping timeout: 245 seconds]
<Wizzup>
freemangordon: regarding the triggers, that seems likely the cause somehow
<Wizzup>
does the shared mime info package also have those triggers
<freemangordon>
I guess yes, but I would expect more that one trigger per directory to be allowed