Bug 405815

Summary: logout screen shows "%2(i18n_argument_missing)" if an user account is logged-in in tty
Product: [Plasma] plasmashell Reporter: Patrick Silva <bugseforuns>
Component: Theme - BreezeAssignee: visual-design
Status: RESOLVED LATER    
Severity: minor CC: kde, nate, plasma-bugs
Priority: NOR    
Version: 5.15.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshot

Description Patrick Silva 2019-03-24 14:34:43 UTC
Created attachment 118996 [details]
screenshot

STEPS TO REPRODUCE
1. start plasma
2. swith to a tty by pressing ctrl+alt+F[3-12]
3. do login and switch back to plasma session
4. press crtrl+alt+del to show logout screen

OBSERVED RESULT
logout window shows "%2(i18n_argument_missing)",
see the screenshot please.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Comment 1 Patrick Silva 2019-05-18 14:43:39 UTC
I can't reproduce on Arch (Plasma 5.16 beta) and neon dev unstable
running Wayland session. The warning shown in the attached screenshot does not appear on X11, is this intentional?
Comment 2 David Edmundson 2019-05-19 16:42:20 UTC
You won't be able to reproduce unless you have a debug build of ki18n
Comment 3 Nate Graham 2019-11-14 04:07:53 UTC
(In reply to David Edmundson from comment #2)
> You won't be able to reproduce unless you have a debug build of ki18n
Do you think it's worth fixing?
Comment 4 David Edmundson 2019-11-14 14:56:56 UTC
Probably, I can't see the bug though.

            text: i18ndp("plasma_lookandfeel_org.kde.lookandfeel",
                         "One other user is currently logged in. If the computer is shut down or restarted, that user may lose work.",
                         "%1 other users are currently logged in. If the computer is shut down or restarted, those users may lose work.",
                         sessionsModel.count)
            visible: sessionsModel.count > 1


it's visible so we know sessionsModel.count is defined 

and the rest looks fine
Comment 5 Nate Graham 2022-06-25 20:25:53 UTC
I don't think we have the resources to fix this given how esoteric of an issue it is, and the fact that it's specific to people using debug builds. Sorry if that's not the answer folks were looking for. Resources are limited and we need more developers to help out to fix small unusual workaroundable issues like this.