Bug 272832 - Virtual Desktops do not retain name change KDE 4.6.3
Summary: Virtual Desktops do not retain name change KDE 4.6.3
Status: RESOLVED DUPLICATE of bug 272666
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-09 06:22 UTC by Texstar
Modified: 2011-05-10 02:07 UTC (History)
4 users (show)

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 Texstar 2011-05-09 06:22:27 UTC 
Version:           4.6 (using Devel) 
OS:                Linux

Virtual Desktop names in the pager do not retain changed names after logout in KDE 4.6.3

Reproducible: Always

Steps to Reproduce:
Change the names of your Virtual Desktops in the Pager. 
Log out 
Log in


Actual Results:  
Names revert to Desktop1 Desktop2 etc...

Expected Results:  
Expected names to remain changed.

PCLinuxOS 2010 updated to KDE 4.6.3, QT4 4.7.3, gcc 4.5.2, glibc 2.12.1
Comment 1 Felix Tiede 2011-05-09 06:37:20 UTC 
Have the same problem here,

Gentoo Linux, KDE 4.6.3, Qt4 4.7.2, gcc 4.4.5, glibc 2.11.3
Comment 2 Hans-Rudi Denzler 2011-05-09 09:54:53 UTC 
Component is 'widget-pager'.

Bug happens since KDE 4.6.2 -> 4.6.3 in openSUSE 11.2.
Comment 3 Jonathan Marten 2011-05-09 11:08:16 UTC 
Confirmed with current trunk.  After login, the relevant section in kwinrc is always reset to:

[Desktops]
Name_1=
Name_2=
Name_3=
Name_4=
Number=4
Comment 4 Terry 2011-05-09 11:27:52 UTC 
I have the same problem with the same system as the original reporter:
PCLinuxOS 2010 updated to KDE 4.6.3, QT4 4.7.3, gcc 4.5.2, glibc 2.12.1
Comment 5 Christoph Feck 2011-05-10 02:07:41 UTC 
> Confirmed with current trunk.

According to bug 272666 it should be fixed in current master. Could you reopen bug 272666 if the fix does not work?

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