Skip to content

Show user and groups settings under "System" #304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

stefonarch
Copy link
Member

I retry. The correct place is "System".

Desktop Entry/Name: "Users and Groups"
Desktop Entry/GenericName: "User and Group Settings"
Desktop Entry/Comment: "Configure the users and groups of your system"

@tsujan
Copy link
Member

tsujan commented Dec 6, 2024

Disagree. It belongs to LXQt and should be under LXQt Settings.

@stefonarch
Copy link
Member Author

It belongs yes to LXQt but it affects any DE and any users installed as its settings aren't LXQt-specific.

@tsujan
Copy link
Member

tsujan commented Dec 7, 2024

"LXQt Settings" is a category for gathering important tools that are provided by LXQt for setting up an LXQt session — whether they're admin tools or not.

No user is surprised to see that LXQt gives priority to LXQt — on the contrary, the opposite would be very weird.

@stefonarch
Copy link
Member Author

We have LXQt Settings, System Settings and Other Settings int the configuration center. It's a system setting.

@tsujan
Copy link
Member

tsujan commented Dec 7, 2024

It's a system setting

IMO, it would be not only weird but impractical to put an important setting provided by LXQt outside the LXQt category, whether it's an admin tool or not. That would pass modularity and turn into the lack of identity.

@TGODiamond
Copy link

Why not have the program be present in both categories then?

@stefonarch
Copy link
Member Author

stefonarch commented Mar 9, 2025

Why not have the program be present in both categories then?

I think that's redundant, but could be a compromise ;)
But I noticed another "issue": It can't be found outside of LXQt, for example in plasma's runner or menu. If I remember well for a some time Plasma didn't even have a GUI, and now it's very poor in confront: only name, email, account type normal or admin. Another question is how people could know about it.

IMO we could remove the OnlyShowIn=LXQt; line. It will show up under "System" in Plasma and probably other systems too.

@tsujan
Copy link
Member

tsujan commented Mar 9, 2025

Caring for Plasma?! Let everyone care for themselves.

@stefonarch
Copy link
Member Author

Ehem, we could well give something back in exchange for kscreen, kwindowsystem and solid, no?

@TGODiamond
Copy link

TGODiamond commented Mar 9, 2025

Non-technical nonsense... lxqt-admin runs great on plasma. lxqt and plasma both primarily use Qt for GUIs...

@tsujan
Copy link
Member

tsujan commented Mar 9, 2025

we could well give something back in exchange for …

We already do. I know some KDE users use pcmanfm-qt instead of Dolphin ;)

@stefonarch
Copy link
Member Author

Let's turn it the other way round: Tell me some good reasons to not show it in any other DE? There are few dependencies.

@TGODiamond
Copy link

TGODiamond commented Mar 9, 2025

Take a look what freedesktop.org specs say: https://specifications.freedesktop.org/menu-spec/latest/category-registry.html

@tsujan
Copy link
Member

tsujan commented Mar 9, 2025

Tell me some good reasons to not show it in any other DE?

I can't give reasons for what I didn't say ;) I said it should appear in "LXQt Settings" category, where it is now. OnlyShowIn=LXQt; can be removed.

@TGODiamond
Copy link

Ok, do we all agree on this: We remove OnlyShowIn=LXQt;, and append System; to the categories, while keeping the category LXQt;?

@stefonarch
Copy link
Member Author

stefonarch commented Mar 9, 2025

and append System; to the categories, while keeping the category LXQt;?

I'm afraid @tsujan won't agree, as so it will show up under "System".

@tsujan
Copy link
Member

tsujan commented Mar 9, 2025

I'm afraid @tsujan won't agree

Actually, I'm not even sure that the removal of OnlyShowIn=LXQt; is OK. I'll have nothing to say if a dev of another DE says, "Your item clutters our menu; you shouldn't shown it here."

And think about other possibilities, like lxqt-admin-time.desktop, lxqt-config-file-associations.desktop, lxqt-config-monitor.desktop, ….

What I mean is that the good intention of caring for other DEs can be interpreted as intrusive. Let's not care too much!

@TGODiamond
Copy link

TGODiamond commented Mar 9, 2025

Do you think that other DE devs care about a 3rd party systems utillity program? Those are always installed by the user or distro, if they WANT said program added to their system. I, as a user on plasma, found this software very useful. But I needed to change that damn .desktop file to remove OnlyShowIn=LXQt;, else, it won't even show up AT ALL in ANY categories!

@tsujan
Copy link
Member

tsujan commented Mar 9, 2025

Do you think that other DE devs care about a 3rd party systems utillity program?

I don't know, but they have right to do when that utility belongs to another DE. That can't be said about apps like file manager, archive manager, etc.

Personally, I don't like it when I see KDE's utilities show up in my LXQt menus and have to hide them manually.

@stefonarch
Copy link
Member Author

Actually, I'm not even sure that the removal of OnlyShowIn=LXQt; is OK

I tested this: Categories=LXQt;Settings;DesktopSettings;Qt;System; and it will show up under "System", I guess because we filter it that way.

And think about other possibilities, like lxqt-admin-time.desktop, lxqt-config-file-associations.desktop, lxqt-config-monitor.desktop, ….

That's true, but what I saw on XFCE and Plasma their tools are equivalent for that, maybe even better, so this here should remain the only one.

FYI I think that is still the situation:
https://unix.stackexchange.com/questions/546589/lack-of-user-account-interface-manager-in-xfce-desktop-manager

@stefonarch
Copy link
Member Author

#313

@tsujan tsujan mentioned this pull request Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants