[Fremantle Maemo5] [Announce] Yappari - New maintainership and new features! - Page 47 - maemo.org

Active Topics

Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 5 hrs, 22 mins ago
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 9 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 22 hrs ago
n770 youtube video (0)
to General by nmdv - 5 days, 21 hrs ago
more...

Page 47 of 157

Thread Tools

TARIKO	2015-02-23 , 08:18
Posts: 24 \| Thanked: 10 times \| Joined on Mar 2012 @ Spain	#461

Originally Posted by TARIKO

These are the last lines opening yappari from command line.
Crash after a couple of message received.

After this message yappari has been without crash almost 21 hr and still alive. The connection has been home wifi all time, now I will move to work and see what happen, changing connection from wifi to lost connection, then to 3G and in the office wifi again.
See you later.

Quote & Reply |

The Following 3 Users Say Thank You to TARIKO For This Useful Post:
BLC, ceene, enne30

enne30	2015-02-23 , 14:34
Posts: 242 \| Thanked: 169 times \| Joined on Nov 2011	#462

Originally Posted by TARIKO

After this message yappari has been without crash almost 21 hr and still alive. The connection has been home wifi all time, now I will move to work and see what happen, changing connection from wifi to lost connection, then to 3G and in the office wifi again.
See you later.

me too, up and running from about 24 hrs... (mixed 2g/3g/wifi/off-line mode).

that's very strange: as if crashes happen in the same period of time for a group of users.. maybe a server message/action performed only on certain clients?

Quote & Reply |

TARIKO	2015-02-24 , 09:54
Posts: 24 \| Thanked: 10 times \| Joined on Mar 2012 @ Spain	#463

Originally Posted by TARIKO

After this message yappari has been without crash almost 21 hr and still alive. The connection has been home wifi all time, now I will move to work and see what happen, changing connection from wifi to lost connection, then to 3G and in the office wifi again.
See you later.

After arraive to the office it crash, I Have to think that it's doesn't support change connection it's the matter. Nothing about mute groups.

Quote & Reply |

	CepiPerez	2015-02-24 , 12:33
	Posts: 1,023 \| Thanked: 4,421 times \| Joined on Feb 2010 @ Argentina	#464

@ceene:

About segmentation fault, please try this:

Code:

void Client::read()
{
    connectionMutex.lock();
    while (socket->bytesAvailable() > 0)
    {
        try {
            connection->read();
        }
        catch (IOException &e)
        {
            lastError = e.toString();
            Utilities::logData("read(): There was an IO Exception: " + lastError);
            connectionClosed();
            showStatus(lastError + " Retrying in 10 seconds..");
            break;
        }
        catch (ProtocolException &e)
        {
            lastError = e.toString();
            Utilities::logData("read(): There was a Protocol Exception: " + lastError);
            connectionClosed();
            showStatus("Protocol Exception. Retrying in 10 seconds...");
            break;
        }
    }

    connectionMutex.unlock();
}

__________________
Filebox / FileCase for Maemo / Harmattan / Sailfish
FlowPlayer for Maemo / Harmattan / Sailfish
Whatsup for Harmattan / Sailfish
CallBlocker for Harmattan

Support my work:
Paypal / Bitcoin

Quote & Reply |

The Following 5 Users Say Thank You to CepiPerez For This Useful Post:
BLC, ceene, enne30, handaxe, newone2

kishorekrray	2015-02-24 , 14:46
Posts: 7 \| Thanked: 0 times \| Joined on Feb 2015	#465

Originally Posted by handaxe

Obviously something is wrong on your device, as others do not see this. Try to get some idea of why it crashes.

In a terminal, start yappari (it should be in the path but to avoid issues): /opt/maemo/usr/bin/Yappari (return)

See if an error is printed upon the crash.

sorry i tried in terminal /opt/maemo/usr/bin/Yappari (return)
it showing not found..

kindly can u plz tell how to check or what is the solution ..as i am not much a techque guy..so dont knw much use of terminal and its coding. thnx

Quote & Reply |

handaxe	2015-02-24 , 20:11
Posts: 1,378 \| Thanked: 1,604 times \| Joined on Jun 2010 @ Göteborg, Sweden	#466

Originally Posted by kishorekrray

sorry i tried in terminal /opt/maemo/usr/bin/Yappari (return)
it showing not found..

kindly can u plz tell how to check or what is the solution ..as i am not much a techque guy..so dont knw much use of terminal and its coding. thnx

You know that the (return) is the enter key?

Because if Yappari is installed, it will run with the command:
/opt/maemo/usr/bin/Yappari

if you follow it with an "enter" also known as return.

Quote & Reply |

kishorekrray	2015-02-25 , 10:16
Posts: 7 \| Thanked: 0 times \| Joined on Feb 2015	#467

Originally Posted by handaxe

You know that the (return) is the enter key?

Because if Yappari is installed, it will run with the command:
/opt/maemo/usr/bin/Yappari

if you follow it with an "enter" also known as return.

hi,thanks for ur help..i got the below in terminal once i enterd the command

segmentation fault

and also yappari opens and crash again..thanks

Quote & Reply |

enne30	2015-02-25 , 15:29
Posts: 242 \| Thanked: 169 times \| Joined on Nov 2011	#468

Originally Posted by CepiPerez

@ceene:

About segmentation fault, please try this:

Code:

void Client::read()
{
    connectionMutex.lock();
    while (socket->bytesAvailable() > 0)
    {
        try {
            connection->read();
        }
        catch (IOException &e)
        {
            lastError = e.toString();
            Utilities::logData("read(): There was an IO Exception: " + lastError);
            connectionClosed();
            showStatus(lastError + " Retrying in 10 seconds..");
            break;
        }
        catch (ProtocolException &e)
        {
            lastError = e.toString();
            Utilities::logData("read(): There was a Protocol Exception: " + lastError);
            connectionClosed();
            showStatus("Protocol Exception. Retrying in 10 seconds...");
            break;
        }
    }

    connectionMutex.unlock();
}

If necessary, I could try this, if ceene puts the update in extras-devel... it keeps crashing, so I could log the new stuff and post it here.

Quote & Reply |

ceene	2015-02-25 , 17:14
Posts: 207 \| Thanked: 967 times \| Joined on Apr 2014 @ Madrid, Spain	#469

Sorry! I'm out again due to work and I don't have access to my build machine. I expect to compile cepiperez changes this weekend.

Best regards!

__________________
OVI and downloads.maemo.nokia.com mirror
Yappari for Maemo
pyLedger for Maemo

If you want to donate, please read this. If you still want to donate, contact me via private message or email. Thank you.

Quote & Reply |

The Following 5 Users Say Thank You to ceene For This Useful Post:
BLC, Boemien, enne30, handaxe, newone2

handaxe	2015-02-25 , 17:21
Posts: 1,378 \| Thanked: 1,604 times \| Joined on Jun 2010 @ Göteborg, Sweden	#470

Originally Posted by kishorekrray

hi,thanks for ur help..i got the below in terminal once i enterd the command

segmentation fault

and also yappari opens and crash again..thanks

OK, it failed to reveal any info about the segfault. That's a shame.

It may be that your issue is the same as the other segfault reported here recently but that seems to be connection related and intermittent. (see my post below - it may be related).

The fixes written about above may help. I recently saw a connection related segfault that always happened with one connection type.

Last edited by handaxe; 2015-02-25 at 17:35.