Bug 287866

Summary: Telepathy Text UI crashes every time when trying to start chat
Product: [Unmaintained] telepathy Reporter: Pavel Punegov <pavelpngv>
Component: text-uiAssignee: Telepathy Bugs <kde-telepathy-bugs>
Status: RESOLVED NOT A BUG    
Severity: crash CC: blagozlatev, kde, mklapetek, myriam
Priority: NOR    
Version: unspecified   
Target Milestone: 0.4.0   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Pavel Punegov 2011-11-29 20:50:43 UTC 
Application: telepathy-kde-text-ui (0.2.60)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.3
Operating System: Linux 3.1.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
- What I was doing when the application crashed:

Every time I try to start chat Text UI crashes. The window appears with message - "Failed to load a valid theme. Please make sure you run the chat window configuration program first. Will now crash."

The crash can be reproduced every time.

-- Backtrace:
Application: Telepathy Text Ui (telepathy-kde-text-ui), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f7d010dd780 (LWP 2985))]

Thread 2 (Thread 0x7f7ceb0d4700 (LWP 5221)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f7cfefcfbc7 in ?? () from /usr/lib/libQtWebKit.so.4
#2  0x00007f7cfefcfd29 in ?? () from /usr/lib/libQtWebKit.so.4
#3  0x00007f7cfaa0cb40 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007f7cfb34136d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f7d010dd780 (LWP 2985)):
[KCrash Handler]
#6  ChatWindowStyle::content (this=0x0, id=ChatWindowStyle::Template) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/lib/chat-window-style.cpp:288
#7  0x00007f7cfd98cc4b in ChatWindowStyle::getTemplateHtml (this=<optimized out>) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/lib/chat-window-style.cpp:149
#8  0x00007f7cfd996bd2 in AdiumThemeView::initialise (this=0x15da9e0, chatInfo=...) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/lib/adium-theme-view.cpp:138
#9  0x00007f7cfd986679 in ChatWidget::ChatWidget (this=0x15deae0, channel=..., account=..., parent=<optimized out>) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/lib/chat-widget.cpp:148
#10 0x0000000000412511 in ChatTab::ChatTab (this=0x15deae0, channel=<optimized out>, account=..., parent=<optimized out>) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/app/chat-tab.cpp:35
#11 0x000000000040c92e in TelepathyChatUi::handleChannels (this=<optimized out>, context=..., account=..., connection=<optimized out>, channels=<optimized out>, channelRequests=<optimized out>, userActionTime=..., handlerInfo=...) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/app/telepathy-chat-ui.cpp:168
#12 0x00007f7cff9ea6b2 in Tp::ClientHandlerAdaptor::onReadyOpFinished (this=0x1593790, op=<optimized out>) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/TelepathyQt4/client-registrar.cpp:509
#13 0x00007f7cff9f07b8 in Tp::ClientHandlerAdaptor::qt_metacall (this=0x1593790, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffaf6aa7b0) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/build/TelepathyQt4/_gen/client-registrar-internal.moc.hpp:411
#14 0x00007f7cfbf10cca in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#15 0x00007f7cffb094af in Tp::PendingOperation::finished (this=<optimized out>, _t1=0x15a17d0) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/build/TelepathyQt4/_gen/pending-operation.moc.hpp:98
#16 0x00007f7cffb09cd1 in Tp::PendingOperation::emitFinished (this=0x15a17d0) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/TelepathyQt4/pending-operation.cpp:133
#17 0x00007f7cffb0c35c in Tp::PendingOperation::qt_metacall (this=0x15a17d0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x15a6650) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/build/TelepathyQt4/_gen/pending-operation.moc.hpp:86
#18 0x00007f7cffb0c830 in Tp::PendingComposite::qt_metacall (this=0x15a17d0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x15a6650) at /home/pavel/Development/KDE Telepathy/telepathy-qt4/build/TelepathyQt4/_gen/simple-pending-operations.moc.hpp:225
#19 0x00007f7cfbf1487a in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00007f7cfcc3d9f4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#21 0x00007f7cfcc42881 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#22 0x00007f7d005e46f6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#23 0x00007f7cfbefe16c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#24 0x00007f7cfbf01528 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#25 0x00007f7cfbf28843 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00007f7cf76fa0cf in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007f7cf76fa8c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007f7cf76faa99 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x00007f7cfbf28c9f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007f7cfcce1a4e in ?? () from /usr/lib/libQtGui.so.4
#31 0x00007f7cfbefd372 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0x00007f7cfbefd56f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x00007f7cfbf01717 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#34 0x000000000040b177 in main (argc=1, argv=0x7fffaf6ab5d8) at /home/pavel/Development/KDE Telepathy/Telepathy Text UI/app/main.cpp:81

Reported using DrKonqi
Comment 1 David Edmundson 2011-11-29 20:55:32 UTC 
You've installed to somewhere not in your kde path, it can't find the files it needs at runtime.
Comment 2 Blagovest Zlatev 2011-11-30 14:31:42 UTC 
I couldn't reproduce the bug and find any duplicates of it.
Comment 3 Pavel Punegov 2011-11-30 17:11:20 UTC 
> --- Comment #1 from David Edmundson <kde davidedmundson co uk>
> You've installed to somewhere not in your kde path, it can't
> find the files it needs at runtime.

I have installed all KDE Telepathy components into /usr/local dir. 
KDEDIRS=/usr/local:/usr is set properly. Other kde apps such as Amarok and 
KDevelop are working.
After trying to chat the descriped above window appears and notification 
"org.freedesktop.Telepathy.Error.NotAvailable: Handler no longer available"
Process telepathy-kde-text-ui is running before crash.
Comment 4 Martin Klapetek 2011-11-30 17:21:21 UTC 
That's because you don't have dbus files installed correctly.

See http://community.kde.org/Real-Time_Communication_and_Collaboration/Troubleshooting#TroubleShooting -- "Nothing happens when I try and start a chat with someone from the contact list."
Comment 5 David Edmundson 2011-11-30 17:27:47 UTC 
Martin, actually I don't think that's relevant.
The dbus file must be ok, because it's starting the Text-UI long enough for it to crash.

Just because the handler fails before accepting the channel the CL sees the request as failed.

Still definitely a path problem though. 

If you're setting KDEDIRS evn locally (i.e in a bash script or something) when the app is dbus activated I bet this isn't kept/loaded. We do have issues with dbus-loaded apps not really keep sessions envs.

Where do you set KDEDIRS? Personally I favour adding an entry in /etc/kde4rc.
Comment 6 Pavel Punegov 2011-11-30 18:09:56 UTC 
>That's because you don't have dbus files installed correctly.
They have been copied to the /usr/share/dbus-1/services.

KDEDIRS is set in script in .kde/env/

Setting the KDEDIRS in /etc/kde4rc helped me. Now it works.
Thank you guys for helping!