Bug 185944

Summary: cannot see any messages in chat window
Product: [Unmaintained] kopete Reporter: Ignat Semenov <i.semenov.kde>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: martin.batora
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Ignat Semenov 2009-03-02 11:41:35 UTC
Version:            (using Devel)
Compiler:          gcc 4.3.1 
OS:                Linux
Installed from:    Compiled sources

Using Kopete from kde-network rev 933701 and qt 4.5 from qt-copy
Cannot see any ICQ messages, incoming or outgoing, in chat window, that is, neither chat participants names are shown nor the messages themselves (chat window is just empty). Incoming messages can still be seen in notifications, however, when I switch to chat window, I see nothing.
Comment 1 martin batora 2009-03-04 18:07:28 UTC
Hi, I can confirm this bug.
I have updated kde to 4.2.65.svn932664 (openSUSEs KDE unstable repo)
after this update incoming and outgoing messages in kopete are not shown in
chat window. when someone send me a message, pop-up bubble is shown and contain
message, but when I open chat window, its clear. also when I send message, it
is not displayed in the window.
In 4.2.64.svn927949 was everything fine.

martin@siren:~>kopete --version
Qt: 4.5.0
KDE: 4.2.65 (KDE 4.2.65 (KDE 4.3 >= 20090226)) "release 1.2"
Kopete: 0.70.50
Comment 2 martin batora 2009-03-25 13:20:58 UTC
Hi again!
If you are experiencing this problem, set your chat window style.
Settings -> configure -> chat window -> style
This should fix it.
Comment 3 Matt Rogers 2009-03-29 06:21:16 UTC
Sounds like a missing chat theme configuration. Please select one using the above steps (thanks Martin!) and reopen if you can still reproduce this bug.
Comment 4 Ignat Semenov 2009-04-04 19:55:05 UTC
Selecting a theme in configuration solved the problem. But why isn't a theme selected by default? This looks like another bug.