Release Telegram


@ingoreis : it start on my side (restart your pandora, you may have something wrong with the pnd still mounted while copying a new version).. But I still have that strange "almost hang" behavior with xkb. It was fixed when I tryied after building but it seems it's back once in the PND... I have to take a look about that...
 
Restart did not work,
Reflash/reupgrade the OS did not work too
Redownload of the PND did not help again.

Maybe Fat32 is the Problem?

Ever the same Error in the pndrun :(
 
I downloaded the from the repo and put it back on my SDCard to be sure (that is a Fat32 one).

Can you you make a md5sum of the PND?
On my side, I have
Code:
7bb169acdfc9bc6dafa40d585f7d3d44  /media/PANDOSEB/pandora/menu/telegram.pnd
 
I downloaded the from the repo and put it back on my SDCard to be sure (that is a Fat32 one).

Can you you make a md5sum of the PND?
On my side, I have
Code:
7bb169acdfc9bc6dafa40d585f7d3d44  /media/PANDOSEB/pandora/menu/telegram.pnd
Same md5sum here.

I deleted old Telegram Appdata again.
Now other Errors:

It seem to make a Directory on my Nand Home named .TelegramDesktop

Ok after waiting a few Seconds more...Telegram start in a windows where i do not see anything:
Zwischenablage02.jpg


Strange that its so difficult to get run this time for me.
Btw:
I did not used the Update Function..i used a blank SD Card
Zwischenablage03.jpg


Edit:
Reflashed,Reformated the SD Card,Reupgraded,redownloaded the Telegram PND again
and the same Error:
-Directory on my Nand Home named .TelegramDesktop
-Telegram start in a windows where i do not see anything

Edit:Edit:
Its an QT Error:
QT: Session management error: Authenification Rejected,Reason : None of the authentification protocols specified are supported and host based authentification failed
The X11 connection broke (error1). Did the X11 Server die?
 
Last edited:
A folder in the Nand? It should not, but I'll double check

Anyway, yes, it sometimes is super slow to start, and sometimes not, not sure why.
I used the old Qt 5.5.1 from last build, to avoir building a new patched 5.6 released (to save some time, but it still took me a week to get that build). But maybe I have to use the 5.6.
the "Qt: Session managment error" is not harmfull. I have seen it already for every Qt app...

But the "The X11 connection broke" is more a problem.
 
I'm having the same issue, it says exactly this:

Code:
=======================================================================================
PND             : /media/1/pandora/apps/telegram.pnd
PND_FSTYPE      : Squashfs
APPDATADIR      : /media/1/pandora/appdata/telegram
APPDD_FSTYPE    : ext4
PND_CPUSPEED    : <unset>
EXENAME         : runscript.sh
ARGUMENTS       : <unset>
=======================================================================================
[ START ]--- Mount the PND ----------
WARNING Union already mounted, using it
+++++++
Loopback devices :
/dev/loop0: [b301]:1580490 (/media/1/pandora/apps/telegram.pnd)
Are mounted on :
/dev/loop0 on /mnt/utmp/telegram type squashfs (ro,relatime)
For these Union :
none on /mnt/utmp/telegram type aufs (rw,relatime,si=13bb859f)
[SUCCESS]--- Mount the PND ----------
[ START ]--- Starting the application ( runscript.sh  ) ----------
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
./runscript.sh: line 82:  2756 Segmentation fault      ./Telegram "$*"
[ FAILED]--- Starting the application ( runscript.sh  ) ----------
[ START ]--- Restoring the frame buffer status ----------
[SUCCESS]--- Restoring the frame buffer status ----------
[ START ]--- uMount the PND ----------
[ START ]--- Waiting the Union to be available ----------
./runscript.sh: line 82:  3070 Segmentation fault      ./Telegram "$*"
[ FAILED]--- Starting the application ( runscript.sh  ) ----------
[ START ]--- Restoring the frame buffer status ----------
[SUCCESS]--- Restoring the frame buffer status ----------
[ START ]--- uMount the PND ----------
[ START ]--- Waiting the Union to be available ----------
[SUCCESS]--- Waiting the Union to be available ----------
rmdir: failed to remove `/mnt/utmp/telegram': Device or resource busy
[ START ]--- Waiting the PND mount dir to be free ----------
[SUCCESS]--- Waiting the PND mount dir to be free ----------
cleanup done
[SUCCESS]--- uMount the PND ----------
=======================================================================================
Return code is : 5
[SUCCESS]--- Waiting the Union to be available ----------
umount: /mnt/utmp/telegram: not found

Usage:
losetup loop_device                             give info
losetup -a | --all                              list all used
losetup -d | --detach <loopdev> [<loopdev> ...] delete
losetup -f | --find                             find unused
losetup -c | --set-capacity <loopdev>           resize
losetup -j | --associated <file> [-o <num>]     list all associated with <file>
losetup [ options ] {-f|--find|loopdev} <file>  setup

Options:
-e | --encryption <type> enable data encryption with specified <name/num>
-h | --help              this help
-o | --offset <num>      start at offset <num> into file
      --sizelimit <num>   loop limited to only <num> bytes of the file
-p | --pass-fd <num>     read passphrase from file descriptor <num>
-r | --read-only         setup read-only loop device
      --show              print device name (with -f <file>)
-v | --verbose           verbose mode

cleanup done
[SUCCESS]--- uMount the PND ----------
=======================================================================================
Return code is : 5
 
@Silent-Hunter : it doesn't look like the same issue, but you seems to have a problem with your PND. It double mount it? Did you updated the PND while it was still mounted? I too suggest you restart you Pandora, download the PND again (before launching it) and try again.

anyway, I'll see if I can update the static Qt build to 5.6, but it will take days probably...
 
I have a new pnd. It's not uploaded to the repo but I will do it tonight probably.

I have fixed a memory corruption issue (bad mixing between Qt internal xkbcommon and external libxkbcommon.so, no all external).
The PND is here if you want to test.: telegram.pnd

Not sure it'll fix every "PND"-related issue, but it should help anyway.
 
Yes this PND s better.
I can start,i can login.

The Window do not Fit the Screen for Typing Messages.
I had played one Time a recieved Audio Message and it crashed.
After that it crashed often randomly.

And it seem to make a .Telegram Directory eighter in my Nand Home.

My pnd out is here:
Code:
=======================================================================================
PND             : /media/FAT32/pandora/desktop/telegram.pnd
PND_FSTYPE      : Squashfs
APPDATADIR      : /media/FAT32/pandora/appdata/telegram
APPDD_FSTYPE    : vfat
PND_CPUSPEED    : <unset>
EXENAME         : runscript.sh
ARGUMENTS       : <unset>
=======================================================================================
[ START ]--- Mount the PND ----------
Mounting : mount -t squashfs -o ro "/dev/loop0" "/mnt/utmp/telegram"
Mounting the Union FS : mount -t aufs -o exec,noplink,dirs="/media/FAT32/pandora/appdata/telegram=rw+nolwh":"/mnt/pnd/telegram=rr" none "/mnt/utmp/telegram"
[SUCCESS]--- Mount the PND ----------
[ START ]--- Starting the application ( runscript.sh  ) ----------
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
AL lib: (EE) ALCcaptureAlsa_open: snd_pcm_hw_params_set_rate(self->pcmHandle, hp, device->Frequency, 0) failed: Invalid argument
AL lib: (EE) ALCcaptureAlsa_open: snd_pcm_hw_params_set_rate(self->pcmHandle, hp, device->Frequency, 0) failed: Invalid argument
The program 'Telegram' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue'.
  (Details: serial 2676 error_code 2 request_code 139 minor_code 51)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
AL lib: (EE) alc_cleanup: 1 device not closed
[ FAILED]--- Starting the application ( runscript.sh  ) ----------
[ START ]--- Restoring the frame buffer status ----------
[SUCCESS]--- Restoring the frame buffer status ----------
[ START ]--- Restoring nub mode ----------
[SUCCESS]--- Restoring nub mode ----------
[ START ]--- uMount the PND ----------
[ START ]--- Waiting the Union to be available ----------
[SUCCESS]--- Waiting the Union to be available ----------
rmdir: failed to remove `/mnt/utmp/telegram': Device or resource busy
[ START ]--- Waiting the PND mount dir to be free ----------
[SUCCESS]--- Waiting the PND mount dir to be free ----------
cleanup done
[SUCCESS]--- uMount the PND ----------
=======================================================================================
Return code is : 11
 
@ingoreis : can you try changing the .alsoftrc in appdata/telegram and switch from alsa to oss?

The NAND writting, I'll take a look at it.

Size of the window? I'll try to take a look.
 
Good News..after deleting all older Files on Nand and Appdata..no more crashes here.
This PND work fine.
Audio Playing work fine too.

The downloaded Pictures and Videos are all unfortunaly on my Nand.
And the Window must be resized.

Little Question:
Do you know anything about MimeTypes?
I want to play Videos from Telegram with Mplayer.
Can you try to build in the Mplayer from the Smplayer PND and set the MimeTypes for xdg-open?(mp4,avi,mov,3gp)
https://repo.openpandora.org/?page=detail&app=package.smplayer2

The Message after Trying play Videos with Telegram was:
Code:
xdg-open: no method aviable for opening file ///mnt/utmp/telegram/home/Downloads/Telegram%20Desktop/video.mov

Wow work not bad..the older Crashes where my Fault because older Config Files :)

Thaaaaaaank you :D

Edit: Good News2...downloaded Videos are in /mnt/utmp/telegram/home/Downloads and not in the Nand.
In the Nand are even over 7MB Data in the .Telegram Directory
 
Last edited:
I have updated the pnd (still same link).

The writing to the NAND should be fixed.

I tried something for the Window size, so it should be ok now (if not, check the settings and ensure the GUI is @100% and not more).
 
This Version is nearly perfect ;)

Little Issues:
- A right Mouse Klick in this Windows crash Telegram
- The Window Size is nearly perfect...
...when i autohide thePanel...
....see the Screenshot:
Zwischenablage02.jpg


Maybe you can decrase the Window little bit more that we dont must hide the Panel? ;)

Another Question..
..have you looked about that Mime Types?
An Buildin Mplayer would be realy nice :)
 
A crash on right click? I'll try tohave a look. But about the size of the window, I don't think I can do much about it, I have very little control about that.
And the mime type, no I haven't looked. I'm not a user of Telegram, so I cannot test anything.
 
Is that Sdl based?
Maybe you can zooming in it a little with Sdl Scaler?

Or a Virtual 800x600 Desktop Resolution
Maybe you can set a Desktop Resolution to 800x600 and Zoom that to 800x480?

Maybe without the Window Boarder?

Maybe we can insert little Icons instead of that Big Icons?

Just Ideas :D
 
Last edited:
Sdl? What I you talking about. I wrote this week-end that I need to recompile Qt...
So it use Qt...
And the problem of size, I have defined the minimum height to be 400 now (it was 600 before). It still doesn't really fit the screen, because when the window is sized, it just take the screen size (so 800x480), withut taking into acount the height eat by Menu bar and window decoration (like the title bar). I'll try to see if I can fix that, but I'm not sure I want to spend much time in this.

About the right-click crash, as I wrote earlier, I cannot reproduce, so you will have to reproduce and provide me a gdb Backtrace.

So here is how to proceed:
1. download the update version (same link). This pnd has an unstripped version of telegram (so the pnd weight 160Mb instead of 45Mb!).
2. Using a Codeblocks (latest beta if possible) command line, mount the pnd (without launching it) using:
Code:
/usr/pandora/script/pnd_run -p /PATH/TO/telegram.pnd -m
3. than launch telegram with gdb, and without using the launch script, with
Code:
cd /mnt/utmp/telegram
OPENSSL_armcap=0 QT_XKB_CONFIG_ROOT=/usr/share/X11/xkb HOME=/mnt/utmp/telegram/home LD_LIBRARY_PATH=/mnt/utmp/telegram/lib:$LD_LIBRARY_PATH gdb ./telegram
If you are using SSH, don't forget to add DISPLAY=:0 in front the command line
4. After some seconds, gdb will be ready, so just type
Code:
r
to run it. Than try to reproduce the crash
5. When the segfault occur, nothing will happens on the telegram screen, because it will be in a "frozen" state by gdb. You need to switch to the command line window (if not using an SSH)... On it, you will see that gdb intercepted a SEGFAULT somewhere. Type
Code:
bt
to get the BackTrace. I'll need the whole gdb output here.
6. you can quit gdb, with
Code:
q
and unmount the pnd
Code:
cd $OLDPWD
/usr/pandora/script/pnd_run -p /PATH/TO/telegram.pnd -u

That's it...
 
Wow so much work and so complicated.
I will try your Howto this Evening.

If the Telegram use the Desktop Resolution...
..is maybe a Chance to set the Pandora Screen Resolution to 800x400 and after starting Telegram back to 800x480?
Maybe Telegram fit then automatic to 800x400 and stay at that Resolution by switch back to 800x480?

That with Sdl was only an Idea..dont worry about that.
I know its Qt and i do not know much about QT...
.. but i know that Qt is a very complicated Beast.

This Evening when i come back from Work i try your Howto with the Backtrace.
This Crash with the Right Mousbutton is only on the Part of the Screen where my Cat is in the Bag.
 
Back
Top