Bug 129173 - Self Nicknames are not applied
Summary: Self Nicknames are not applied
Status: RESOLVED DUPLICATE of bug 116365
Alias: None
Product: kopete
Classification: Unmaintained
Component: libkopete (other bugs)
Version First Reported In: 0.12
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-15 04:39 UTC by Jonathan Jara-Almonte
Modified: 2006-06-15 12:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Jara-Almonte 2006-06-15 04:39:58 UTC 
Version:           0.12 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc 3.4.6 CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer"
OS:                Linux

After upgrading to Kopete 0.12 my self-nickname (Jon) is no longer applied in chat windows and instead I see my username (jmja89) but nicknames for other people are still used. I have a global profile enabled with a custom nickname set to Jon as is evident from my ~/.kde/share/apps/kopete/global-identities.xml file:

<kopete-global-identities-list>
    <identity contactId="AIMProtocol:jmja89:jmja89" name="Default Identity" >
        <display-name>Jon</display-name>
        <photo syncWithKABC="false" ></photo>
        <property-sources>
            <name source="custom" >
                <contact-source nameSourcePluginId="AIMProtocol" nameSourceAccountId="jmja89" nameSourceContactId="jmja89" />
            </name>
            <photo source="contact" >
                <contact-source nameSourcePluginId="AIMProtocol" nameSourceAccountId="jmja89" nameSourceContactId="jmja89" />
            </photo>
        </property-sources>
    </identity>
</kopete-global-identities-list>
Comment 1 Olivier Goffart 2006-06-15 12:04:28 UTC 
Read comment #20 in Bug 116365

Thanks for the report


(test if bugzilla do good link Bug 116365#20    Comment 116365#20 )

*** This bug has been marked as a duplicate of 116365 ***