Bug 98154 - kdm doesn't take GreetString in Theme mode
Summary: kdm doesn't take GreetString in Theme mode
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
: 139894 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-29 15:52 UTC by Tobias Powalowski
Modified: 2018-04-16 20:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Powalowski 2005-01-29 15:52:41 UTC
Version:            (using KDE KDE 3.3.91)
Installed from:    Compiled From Sources
OS:                Linux

hi
the GreetString defined in kdmrc is not used if you set UseTheme=true

it is hardcoded: 
{ "welcome-label",      I18N_NOOP("Welcome to %h") },	// _greetString

would be nice if it would also possible to use the greetstring defind in kdmrc, else i have to hack kdmlabel.cpp for our greeting string.

greetings from Archlinux team
Comment 1 Oswald Buddenhagen 2005-01-29 21:35:38 UTC
this has a simple reason: the string from kdmrc (and the built-in default, fwiw) is not i18n-ed.
due to the way the kdm config works
- i18n-ing the default is possible, but ugly. ok, not more ugly than the i18n of the auth backend.
- i18n-ing explicitly specified strings (like GreetString[de]) is not possible without major shuffling alltogether.
Comment 2 Stephan Kulow 2005-01-30 13:20:04 UTC
I don't see a sane way either
Comment 3 Fathi Boudra 2007-02-10 21:35:47 UTC
*** Bug 139894 has been marked as a duplicate of this bug. ***
Comment 4 bemalmbe 2015-06-24 20:46:58 UTC
I can confirm this bug.

Custom GreetString= messages are ignored, in kdmrc, until themed mode is turned off.
Comment 5 Nate Graham 2018-04-16 20:21:46 UTC
KDM is unmaintained and not used in KDE Plasma 5.

SDDM is the login manager used in KDE Plasma 5. If you still have this same issue with SDDM, please file an issue on the SDDM bugtracker (after doing a search for existing issues first!): https://github.com/sddm/sddm/issues/