![]() |
Re: [Announce] Yappari - New maintainership and new features!
@ceene Aqui un gaditano a tu disposición :D
Tuve un N900 desde que salió.. hasta que en 2011 el microUSB dijo byebye y bueno ahora mismo fijate que estoy pensando en deshacerme de mi Note 2 para volver al N900, un poco locura pero asi puede ser jaja un saludo paisano. And now my answer in english, somebody knows if is possible use Yappari and Whatsapp on Nitdroid with the same phone number? |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
I have 2 N900, one with broken USB. My main problem is segmentation fault, it close Yappari too many times. I hope Ceene solve this problem. |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Once you have installed it, and after you've experienced a Yappari crash, you need to send me files that will have been placed under /home/user/MyDocs/core-dumps/ This is intended not only for Tariko, but also for all of you that are suffering crashes. Without these files I won't be able to fix this standing issue. Thanks a lot! |
Re: [Announce] Yappari - New maintainership and new features!
ceene it's there any possibility to add privacy settings and fix the status issu too
|
Re: [Announce] Yappari - New maintainership and new features!
a donde envió los archivos?
|
Re: [Announce] Yappari - New maintainership and new features!
Quote:
Gracias! |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
|
Re: [Announce] Yappari - New maintainership and new features!
Quote:
I hope with this core dump I'll be able to find what is happening. Thanks a lot! |
Re: [Announce] Yappari - New maintainership and new features!
Another workaround to prevent crashes:
Put this on top of read() function: Code:
void Client::read() |
Re: [Announce] Yappari - New maintainership and new features!
Quote:
It's quite late now in Spain and I'm going to bed, but most probably tomorrow I'll release a new version with this fix. I've just taken a look at log from guidofasano and at first sight his crash seems to be unrelated, since his log doesn't end with a disconnection, just with a new group found: Group found: 584999999999-1379999999@g.us - Subject: Familia Fasano And gdb backtrace shows only this (I'll be generating also a .deb package with debug symbols to help with these crashes). (gdb) bt #0 0x41dca700 in QString::lastIndexOf(QLatin1String const&, int, Qt::CaseSensitivity) const () from /usr/lib/libQtCore.so.4 #1 0x000d9f40 in ?? () #2 0x0009ca08 in ?? () #3 0x0017a8b4 in ?? () #4 0x41ec7be4 in ?? () from /usr/lib/libQtCore.so.4 #5 0x41ec7be4 in ?? () from /usr/lib/libQtCore.so.4 Backtrace stopped: previous frame identical to this frame (corrupt stack?) |
All times are GMT. The time now is 16:43. |
vBulletin® Version 3.8.8