Contact Us

If you are interested in our services leave your contact details below and our sales representatives will contact you.

The organization which you represent
Email address we will use to contact you
Longer contact form…
 
  • About

    mFabrik Blog is about mobile and web software development, open source and Linux. We tell exciting tales where business, technology, web and mobile convergence.

    Creative Commons License
    This work is licensed under a Creative Commons Attribution 3.0 Unported License.

Debugging Skype crash problems on Ubuntu 10.04 Lucid Lynx Linux

Posted on July 16, 2010  by Mikko Ohtamaa
Filed Under linux, technology, ubuntu

Symptoms: Your Skype crashes on incoming chat message or if you try to open a contact info / chat message – usually this leads to a crash on Skype start-up because there are always incoming chat messages in a queue.

Skype is not really helpful regarding how to get meaningful log information from the client, but it is possible.

Create a log directory

mkdir ~/.Skype/Logs

Run Skype from the command line and open a chat window so that it crashes

moo@murskaamo:~$ skype
Aborted

Now there should be log data available

moo@murskaamo:~$ ls -lh ~/.Skype/Logs/
total 724K
-rw-r--r-- 1 moo moo 607K 2010-07-16 11:10 skype_20100716-1110.log
-rw-r--r-- 1 moo moo 116K 2010-07-16 11:10 skype_20100716-1110.trace.txt

However, those log files are little useful for anybody except Skype developers as they are encrypted. Your only hope is to submit them to  a Skype bug tracker and hope that someone answers you something meaningful. The guidelines how to create a bug report and how they are processed is little unclear – there doesn’t seem to be clear announcement from Skype whether they process  these reports or not.

The crashes probably are due to incompatible system library versions / bugs in them. Try downloading static Skype versions which does not use system libraries.

Read our blog  Subscribe mFabrik blog in a reader Follow us on Twitter Mikko Ohtamaa on LinkedIn

 

Other posts by Mikko Ohtamaa

 

Comments

Leave a Reply