qutecom segfault when trying to start up

Bug #465243 reported by Muhammad Akl
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
qutecom (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: qutecom

after installing qutecom from ppa repositories , and trying to start it up , it quit with segfault , attached strace file.

1- ubuntu 9.10

2- qutecom 2.2~rc3.hg396~dfsg1-2build1

Revision history for this message
Muhammad Akl (muhammad-akl) wrote :
Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Hi.
thanks for reporting the bug.

You said you are using the package from the ppa, but qutecom 2.2~rc3.hg396~dfsg1-2build1 is not in the ppa.

Can you also please attach the output when running
OWLOGGER_DEFAULT=debug qutecom

and also, please install qutecom-dbg, run
   gdb qutecom
and when it segfault run
   thread apply all bt
and paste the output here, please

Thanks,
Ludovico

Revision history for this message
Muhammad Akl (muhammad-akl) wrote : Re: [Bug 465243] Re: qutecom segfault when trying to start up
Download full text (6.6 KiB)

hi ludovio,

firstly sorry for that, i was thinking that after adding the ppa
repositories i'm installing from them , but did not notice that i was
downloading from ubuntu universe repositories

anyway i've disabled the universe repositories , and now i've downloaded the
qutecom packages from ppa ,but i can confirm that i'm still having the same
issue

the outputs you wanted after setting OWLOGGER_DEFAULT=debug qutecom :

(debug) 11:31:33 [Common] int main(int, char**): Started
(debug) 11:31:33 [File] virtual bool FileReader::open(): loading
/usr/share/qutecom//config/config.xml
(debug) 11:31:33 [File] virtual bool FileReader::open(): loading
/home/muhammad/.qutecom/config.xml
(debug) 11:31:33 [Purple] void* PurpleMainEventLoop(void*): Starting
gMainLoop
(debug) 11:31:35 [Purple] virtual PurpleIMFactory::~PurpleIMFactory():
Stopping gMainLoop
Segmentation fault

this line also appears in syslog file when it segfault :

kernel: [ 4911.734270] qutecom[6622]: segfault at 0 ip 00007fe2f6b43632 sp
00007fff70099410 error 4 in libQtCore.so.4.5.2[7fe2f6a10000+22d000]

from gnu debugger output was as follows :

gdb qutecom
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/qutecom...Reading symbols from
/usr/lib/debug/usr/bin/qutecom...done.
(no debugging symbols found)...done.
(gdb) set args -style plastique
(gdb) run
Starting program: /usr/bin/qutecom -style plastique
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeae87910 (LWP 6687)]
[New Thread 0x7fffea686910 (LWP 6688)]
[New Thread 0x7fffe925b910 (LWP 6689)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3a82632 in ?? () from /usr/lib/libQtCore.so.4
(gdb) thread apply all bt

Thread 4 (Thread 0x7fffe925b910 (LWP 6689)):
#0 0x00007ffff06f4373 in poll () from /lib/libc.so.6
#1 0x00007ffff7b5736c in ?? () from /lib/libglib-2.0.so.0
#2 0x00007ffff7b579e5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#3 0x0000000000712b4a in PurpleMainEventLoop (data=<value optimized out>)
    at
/build/buildd/qutecom-2.2~rc3.hg396~dfsg1/libs/imwrapper/src/purple/PurpleIMFactory.cpp:163
#4 0x00007ffff7b7cb34 in ?? () from /lib/libglib-2.0.so.0
#5 0x00007ffff1cf4a04 in start_thread () from /lib/libpthread.so.0
#6 0x00007ffff07007bd in clone () from /lib/libc.so.6
#7 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fffea686910 (LWP 6688)):
#0 0x00007ffff06f93c2 in select () from /lib/libc.so.6
#1 0x00007ffff3d8d827 in owsl_monitor_loop (dummy=<value optimized out>)
    at
/build/buildd/qutecom-2.2~rc3.hg396~dfsg1/wifo/owsl/src/core/owsl_monitor.c:205
#2 0x00007ffff1cf4a04 in start_thread () from /lib/libpthread.so.0
#3 0x00007ffff07007bd in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fffeae87910 (LWP...

Read more...

Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Looks like it is the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550947, i.e. it happens only when there is another qutecom process running in the background. Can you confirm it, please?

Thanks,
Ludovico

Revision history for this message
Muhammad Akl (muhammad-akl) wrote :
Download full text (37.5 KiB)

i'm starting to become crazy with qutecom , it starts to work some times ,
and some not , btw a new interesting tracing from both , qutecom's debugger
and from gdb ,

1- muhammad@muhammad-desktop:~$ ps -ef | grep qutecom
muhammad 10278 10153 0 14:09 pts/2 00:00:00 grep --color=auto qutecom
muhammad@muhammad-desktop:~$ gdb qutecom
GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/qutecom...Reading symbols from
/usr/lib/debug/usr/bin/qutecom...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/qutecom
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffeae87910 (LWP 10284)]
[New Thread 0x7fffea686910 (LWP 10285)]
[New Thread 0x7fffe35aa910 (LWP 10286)]
[New Thread 0x7fffe2ba3910 (LWP 10287)]
(info) 14:09:45 [Common] void QtLanguage::loadLanguageFromConfig(): no Qt
translation available for locale 'en_US'
[New Thread 0x7fffd7ffe910 (LWP 10288)]
[Thread 0x7fffd7ffe910 (LWP 10288) exited]
[New Thread 0x7fffd7ffe910 (LWP 10289)]
[Thread 0x7fffd7ffe910 (LWP 10289) exited]
[New Thread 0x7fffd7ffe910 (LWP 10290)]
[Thread 0x7fffd7ffe910 (LWP 10290) exited]
[New Thread 0x7fffd7ffe910 (LWP 10291)]
[Thread 0x7fffd7ffe910 (LWP 10291) exited]
[New Thread 0x7fffd7ffe910 (LWP 10292)]
[Thread 0x7fffd7ffe910 (LWP 10292) exited]
[New Thread 0x7fffd7ffe910 (LWP 10293)]
[Thread 0x7fffd7ffe910 (LWP 10293) exited]
[New Thread 0x7fffd7ffe910 (LWP 10294)]
[Thread 0x7fffd7ffe910 (LWP 10294) exited]
[New Thread 0x7fffd7ffe910 (LWP 10295)]
[Thread 0x7fffd7ffe910 (LWP 10295) exited]
[New Thread 0x7fffd7ffe910 (LWP 10296)]
[Thread 0x7fffd7ffe910 (LWP 10296) exited]
[New Thread 0x7fffd7ffe910 (LWP 10297)]
[New Thread 0x7fffdbdf2910 (LWP 10298)]
[New Thread 0x7fffdb5f1910 (LWP 10299)]
[New Thread 0x7fffdadf0910 (LWP 10300)]
[New Thread 0x7fffda5ef910 (LWP 10301)]
[New Thread 0x7fffd9dee910 (LWP 10302)]
[Thread 0x7fffd9dee910 (LWP 10302) exited]
[New Thread 0x7fffd9dee910 (LWP 10303)]
[Thread 0x7fffd9dee910 (LWP 10303) exited]
[New Thread 0x7fffd9dee910 (LWP 10304)]
[Thread 0x7fffd9dee910 (LWP 10304) exited]
[New Thread 0x7fffd9dee910 (LWP 10305)]
[Thread 0x7fffd9dee910 (LWP 10305) exited]
[New Thread 0x7fffd9dee910 (LWP 10306)]
[Thread 0x7fffd9dee910 (LWP 10306) exited]
[New Thread 0x7fffd9dee910 (LWP 10307)]
[Thread 0x7fffd9dee910 (LWP 10307) exited]
[Thread 0x7fffdbdf2910 (LWP 10298) exited]
[Thread 0x7fffda5ef910 (LWP 10301) exited]

(<unknown>:10281): GLib-GObject-CRITICAL **: g_object_ref: assertion
`object->ref_count > 0' failed

(<unknown>:10281): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
[New Thread 0x7fffd9dee910 (LWP 10308)]
[New Thread 0x7fffd93e6910 (LWP 10309)]
[New Thread 0x7fffd8be5910 (LWP 10310)]
[New Thread 0x7fffcf7fb910 (LWP 10311)]
(wa...

Revision history for this message
Ludovico Cavedon (cavedon) wrote :

Muhammad Akl wrote:
> i'm starting to become crazy with qutecom ,

I know the feeling :(

> it starts to work some times ,
> and some not ,

Even when starting with "-style plastique", sometime works and sometimes
not?

> btw a new interesting tracing from both , qutecom's debugger
> and from gdb ,

Mhm, this a new issue :(
Can you report it to a new bug number, please?

Thanks,
Ludovico

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.