Jan Biedermann

  

@ilya-fedin I see, i think i understand. I apologize if i appeared unfriendly, that was not my intention. So best greetings to your decision maker, shipping a non-functional product is...

Thanks, I just wanted something to tinker with and go from there ... i will figure it out ... eventually ... maybe

Suddenly the build finished ... and i can confirm ... using the build ... that the crash does NOT happen. Nothing to fix, except for the snap thing maybe, ill...

... it fails, because it must be from the 80's or something, complaining about internet connectivity. Ethernet no good? Anyway, here is the message: ``` craft-providers error: A network related...

I can further confirm, that the static build provided via link from the repos root also does NOT crash. So the fix is easy: Uninstall snap versions, install another version.

> > I read the docs, but there is nothing about internet. I give up, unless maybe @ilya-fedin you have another tip for me? > > Do you have both...

... 3 weeks later ... the build finished. I can confirm telegram-desktop_4.14.15-3-g8b6a7a443_amd64.snap to be crashing. I noticed, that the snap may pull in different versions of libraries than the other...

If you look at snapcraft.yaml it demands libwhateversomethingfancy, but it doesnt say which version of it. That would explain, why builds behave differently, as it may pull in a different...

So the last patch makes bridge for subclasses work and no longer cuts of the prototype chain ``` class A { a() {return 'a'}} class B extends A { b(){return...