|
Bugzilla – Full Text Bug Listing |
| Summary: | kopete uses wrong account for some displays | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Gerald Pfeifer <gp> |
| Component: | KDE | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P4 - Low | CC: | dmueller, forgotten_kHYb7eJGnH |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 10.2 | ||
| Whiteboard: | |||
| Found By: | Product Management | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Screenshot #1
Screenshot #2 Screenshot of configuration screen KDE 4.3.1 kopete crash |
||
|
Description
Gerald Pfeifer
2007-04-26 23:58:55 UTC
Created attachment 135413 [details]
Screenshot #1
Created attachment 135414 [details]
Screenshot #2
in Configure Kopete...->Identity do you have "Enable global identity" checked? If so, Kopete will use the global nickname configured in that tab. If not it will use each account's nickname. Also, for Groupwise this only affects what you see locally - there is no user configurable display name in the protocol. Created attachment 135861 [details] Screenshot of configuration screen > in Configure Kopete...->Identity do you have "Enable global identity" checked? > If so, Kopete will use the global nickname configured in that tab. If not it > will use each account's nickname. No, I do not have "Enable global identity" checked. See attached screenshot. (Interestingly, the account displayed -- greyed out -- is the one which was shown in my case.) > Also, for Groupwise this only affects what you see locally - there is no user > configurable display name in the protocol. So it's only a display issue? Good. :-) Upstreamed as http://bugs.kde.org/show_bug.cgi?id=116365 mass reopening all 10.2 LATER+REMIND bugs. close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it. Still seeing this, and it seems a number of people are running into it. Created attachment 330116 [details]
KDE 4.3.1 kopete crash
Crash with default kde.
Responded to the wrong bug and it reopened, please ignore. But why are you then marking a bug that was open as resolved?? If you aren't sure what the previous state was, Bugzilla has a history function. If this is reported upstream shouldn't it be resolved that way as per http://en.opensuse.org/KDE/BugSquashing#Upstreaming_bugreports Closing as upstream as per comment 7 Hope that is all good Cheers Steve |