qutecom crashed with SIGSEGV in QLibrary::setFileName()

[adse]

Binary package hint: qutecom

on ubuntu 9.10 x64 (up to date via updatemanager as of 13.10.2009) qutecom either does not start at all or it gives a crashreport upon starting.
once i was able to start qutecom and i could use it without any problems at all.
when i shutdown/reboot ubuntu a message is shown, telling me an unknown program is still active. that unknown program is qutecom. it seems to stay in memory.

hope this was useful.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 14 09:11:31 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/qutecom
NonfreeKernelModules: nvidia
Package: qutecom 2.2~rc3.hg396~dfsg1-2build1
ProcCmdline: qutecom
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SegvAnalysis:
 Segfault happened at: 0x7f0f924b8632: mov (%rax),%rbx
 PC (0x7f0f924b8632) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qutecom
StacktraceTop:
 ?? () from /usr/lib/libQtCore.so.4
 QLibrary::setFileName(QString const&) ()
 ?? () from /usr/lib/libQtDBus.so.4
 QDBusConnection::connectToBus(QDBusConnection::BusType, QString const&) () from /usr/lib/libQtDBus.so.4
 ?? () from /usr/lib/libQtDBus.so.4
Title: qutecom crashed with SIGSEGV in QLibrary::setFileName()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Ludovico Cavedon (cavedon)]

Could you please try and see if running

qutecom -style plastique

helps, please?

It sould fix the non-starting problem, but not the crash :(

Thanks for reporting the bug!

[Ludovico Cavedon (cavedon)]

One additional thing:
could you run
OWLOGGER_DEFAULT=debug qutecom
and attach here the output when it crashes, please?

Thanks!

[adse (doncolon)]

Hi Ludovico Cavedon!

Your hint solved my problem! (I'm new to Ubuntu.) Not only is QuteCom starting now, but also works perfectly for me!
For convenience I'm gonna avoid future use of the terminal "qutecom -style plastique" and change my launcher to what you wrote instead.

in case you care for the terminal log ("qutecom -style plastique"):
<START>
user@user-laptop:~$ qutecom -style plastique
(info) 10:50:33 [Common] void QtLanguage::loadLanguageFromConfig(): no Qt translation available for locale ''
(info) 10:50:33 [Common] void QtLanguage::loadLanguageFromConfig(): no application translation available for locale ''
sVoIP_phapi_handle_invite_in
<END>

running "OWLOGGER_DEFAULT=debug qutecom" in terminal makes QuteCom start correctly as well and does not result in a crash like it did before. Since there is no crash thistime I don't know if you still care for the log file (I attached it anyway).

THANKS FOR THE QUICK HINT & greetings from Germany!

[Ludovico Cavedon (cavedon)]

Gald it is working!
However this is a bad workaround, rather than a fix, so I would leave the bug open until it is really fixed.
Thanks for the log.

[Apport retracing service (apport)]

StacktraceTop:?? () from /usr/lib/libQtCore.so.4
QLibrary::setFileName ()
?? () from /usr/lib/libQtDBus.so.4
QDBusConnection::connectToBus ()
?? () from /usr/lib/libQtDBus.so.4

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libqtcore4: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libqt4-dbus: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libqt4-network: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libboost-thread1.38.0: installed version 1.38.0-7+b1, latest version: 1.38.0-6ubuntu6
libqt4-xml: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libboost-signals1.38.0: installed version 1.38.0-7+b1, latest version: 1.38.0-6ubuntu6
libqtgui4: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libqt4-svg: installed version 4.5.2-0ubuntu6, latest version: 4.5.3really4.5.2-0ubuntu1
libboost-program-options1.38.0: installed version 1.38.0-7+b1, latest version: 1.38.0-6ubuntu6
libboost-serialization1.38.0: installed version 1.38.0-7+b1, latest version: 1.38.0-6ubuntu6

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[JOna (jblistat)]

> This might be caused by some outdated packages which were installed
> on your system at the time of the report

I have a fresh install of ubuntu-9.10 karmic beta / samsung nc10 netbook with all the latest updates.

Is there something I could do to help fix this bug?

[David Oxland (doxland)]

My problem is the same and output is
david@david-desktop:~$ qutecom -style plastique
Segmentation fault (core dumped)
david@david-desktop:~$ OWLOGGER_DEFAULT=debug qutecom
(debug) 00:36:09 [Common] int main(int, char**): Started
(debug) 00:36:09 [File] virtual bool FileReader::open(): loading /usr/share/qutecom//config/config.xml
(debug) 00:36:09 [File] virtual bool FileReader::open(): loading /home/david/.qutecom/config.xml
(debug) 00:36:09 [Purple] void* PurpleMainEventLoop(void*): Starting gMainLoop
(debug) 00:36:11 [Purple] virtual PurpleIMFactory::~PurpleIMFactory(): Stopping gMainLoop
Segmentation fault (core dumped)
david@david-desktop:~$

[Ludovico Cavedon (cavedon)]

Fixed by version 2.2~rc3.hg396~dfsg1-3

[sl45sms (sl45sms)]

Same problem here (karmic)
OWLOGGER_DEFAULT=debug qutecom
(debug) 22:05:58 [Common] int main(int, char**): Started
(debug) 22:05:58 [Purple] void* PurpleMainEventLoop(void*): Starting gMainLoop
(debug) 22:05:58 [File] virtual bool FileReader::open(): loading /usr/share/qutecom//config/config.xml
(debug) 22:05:58 [File] virtual bool FileReader::open(): loading /home/kostas/.qutecom/config.xml
(debug) 22:06:00 [Purple] virtual PurpleIMFactory::~PurpleIMFactory(): Stopping gMainLoop
(debug) 22:06:00 [Purple] void* PurpleMainEventLoop(void*): gMainLoop stopped
Segmentation fault

[Ludovico Cavedon (cavedon)]

This crash only happens when there is another qutecom running in the background. Please try run:
   killall qutecom
and than start qutecom again. Note that there is another bug that affects qutecom in karmic, which cause qutecom to start but not show any GUI. This second bug can be avoided by starting qutecom with
   qutecom -style plastique

This bug has been fixed in lucid, so I am marking it as fix released.
I have just uploaded an updated version qutecom for karmic in my ppa https://edge.launchpad.net/~cavedon/+archive/qutecom. It should be built in a while.

[Richard Leger (richard-leger)]

As I was not aware of the ppa for qutecom (and I still have to look into it), if like me you did a simple
sudo apt-get install qutecom
to have application installed in Ubuntu 9.10 amd64, it does work fine with the work arround described above :)

In addition, for those which would like to create a launcher in gnome panel on the Desktop, I have noticed it is better to use the full path to the binary of the application usr/bin/qutecom instead of simply qutecom.
So by re-using the type above, the full command of the launcher would be :
/usr/bin/qutecom -style plastique

Be sure to do a :
killall qutecom
before you retry to launch the application.

It works fine for me.
Hope it would help others :)

Cheers!