вылетает qutim при попытке отправить сообщение/открытии чата

Bug #683052 reported by pinicilin2006
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qutim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: qutim

root@artur-work:/home/artur# uname -a
Linux artur-work 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

При попытке открыть диалоговое окно что бы написать сообщение вылетает qutim(до сегодняшнего дня всё работало чётко). В логах следующее

Nov 30 15:47:16 artur-work kernel: [17589.060163] qutim[3596]: segfault at 10 ip 00007f64e570e280 sp 00007fff2ff247a8 error 4 in libQtWebKit.so.4.7.0[7f64e4b39000+129d000]
Nov 30 15:55:22 artur-work kernel: [18075.204543] qutim[3667]: segfault at 10 ip 00007f5b8c805280 sp 00007fff5b0264d8 error 4 in libQtWebKit.so.4.7.0[7f5b8bc30000+129d000]
Идентичная ситуация и на другом компе

Revision history for this message
Sergey Markelov (sergio-nsk) wrote :

Подтверждаю этот баг для версии 0.2.1-2~git20101130~maverick1 на 64-битной системе.

Вывод в консоли:

Debug: ("/usr/bin/plugins", "/usr/lib/qutim", "/usr/lib/qutim/plugins", "/usr/lib64/qutim", "/usr/lib64/qutim/plugins", "/usr/PlugIns", "/home/me/.config/qutim/plugins")
Debug: "/usr/lib/qutim/libicq.so"
Debug: "/usr/lib/qutim/libjabber.so"
Debug: Share paths: ("", "../share/qutim", "/home/me/.config/qutim")
Debug: Protocol "ICQ" was loaded
Debug: Protocol "Jabber" was loaded
Debug: Language: "Russian" Country: "RussianFederation"
Debug: ("ru_RU", "ru_ru", "ru")
Debug: Loading translation: "Russian"
Debug: "/usr/share/qutim/languages/Russian/main.qm"
Warning: QFSFileEngine::open: No file name specified
Debug: "<email address hidden>"
Debug: 0x0008: "This is gloox 1.0, connecting to jabber.ru:-1..."
Debug: 0x0004: "starting TLS handshake..."
Debug: 0x0008: "connection encryption active"
Warning: 0x0004: "The server offers compression, but negotiating Compression at this stage is not recommended. See XEP-0170 for details. We'll coe anyway."
Debug: 0x0004: "Stream compression initialized"
Debug: 0x0004: "Processing SASL challenge"
Debug: 0x0004: "Processing SASL challenge"
Debug: 0x0004: "SASL authentication successful"
Warning: QDir::exists: Empty or null file name
Debug: "" "" 44436416
Debug: "proxy.jabber.ru" "77.88.57.178" 5277
Debug: "" "" 0
Warning: QMetaObject::connectSlotsByName: No matching signal for on_copyMessage()

/var/log/message

Nov 30 20:59:30 me kernel: [ 1167.509361] qutim[11483]: segfault at 10 ip 0000003f0c9d5280 sp 00007ffff69754a8 error 4 in libQtWebKit.so.4.7.0[3f0be00000+129d000]

summary: - вылетает qutim при попытке отправить сообщение
+ вылетает qutim при попытке отправить сообщение/открытии чата
Revision history for this message
Sergey Markelov (sergio-nsk) wrote :

Установил себе пакеты -dbg. Теперь немного конкретнее информация.

Program received signal SIGSEGV, Segmentation fault.
0x0000003ffb9d5280 in QWebPage::view() const () from /usr/lib/libQtWebKit.so.4
(gdb) bt
#0 0x0000003ffb9d5280 in QWebPage::view() const () from /usr/lib/libQtWebKit.so.4
#1 0x000000000052ac3a in LogsCity::addMessage (this=0x952600, item=..., message=<value optimized out>, date=<value optimized out>,
    history=<value optimized out>, in=false, window_active=<value optimized out>, webkit=0x0)
    at /build/buildd/qutim-0.2.1/src/corelayers/chat/logscity.cpp:766
#2 0x00000000004fe781 in ChatLayerClass::loadHistoryMessages (this=0xa243a0, item=<value optimized out>)
    at /build/buildd/qutim-0.2.1/src/corelayers/chat/chatlayerclass.cpp:586
#3 0x00000000004ffa53 in ChatLayerClass::createChat (this=0xa243a0, item=..., new_message=false)
    at /build/buildd/qutim-0.2.1/src/corelayers/chat/chatlayerclass.cpp:152
#4 0x00000000005720a8 in DefaultContactList::eventFilter (this=0xa24820, obj=0xa28a40, event=0x7fffffffd240)
    at /build/buildd/qutim-0.2.1/src/corelayers/contactlist/defaultcontactlist.cpp:661
#5 0x0000003ff1768507 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#6 0x0000003ff29b7fac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#7 0x0000003ff29be30e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#8 0x0000003ff1768cdc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#9 0x0000003ff29bcdbe in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) ()
   from /usr/lib/libQtGui.so.4
#10 0x0000003ff2a40345 in ?? () from /usr/lib/libQtGui.so.4
#11 0x0000003ff2a3ec5c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#12 0x0000003ff2a6b0e2 in ?? () from /usr/lib/libQtGui.so.4
#13 0x0000003bb2640342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#14 0x0000003bb26442a8 in ?? () from /lib/libglib-2.0.so.0
#15 0x0000003bb264445c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#16 0x0000003ff1795193 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#17 0x0000003ff2a6aa4e in ?? () from /usr/lib/libQtGui.so.4
#18 0x0000003ff1767a02 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#19 0x0000003ff1767dec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#20 0x0000003ff176bebb in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#21 0x0000000000480ff5 in main (argc=1, argv=<value optimized out>) at /build/buildd/qutim-0.2.1/main.cpp:133
(gdb)

Revision history for this message
Sergey Markelov (sergio-nsk) wrote :

Обошёл проблему: в настройках Chat Windows включил WebKit mode.

Revision history for this message
Aleksey Sidorov (aleksey.sidorov) wrote :

В общем или так или юзайте 0.3. Эта бага исправлению не подлежит в виду того, что никто не понимает как тот код работает

Revision history for this message
Maia Everett (linneris) wrote :

This is not a bug in qutim 0.2, which is the version currently packaged in Ubuntu. Please file it against the upstream qutim project at https://launchpad.net/qutim .

Changed in qutim (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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