this post was submitted on 13 Jan 2026
355 points (98.9% liked)

Technology

78661 readers
3425 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] jj4211@lemmy.world 1 points 4 hours ago (1 children)

You can't to the same degree. If you let the user use a typical desktop environment like gnome or plasma., then they can set their wallpaper.

Now if you want to make a kiosk thing, so much easier in Linux. But if you want to have a general purpose desktop experience but restrict stupid stuff like wallpaper, windows has got you.

I would rather use and administer Linux systems at scale any day, but if you hated your users and wanted to lock personalization, then Windows has done the work to enable that.

[โ€“] just_another_person@lemmy.world 1 points 2 hours ago* (last edited 21 minutes ago)

Sorry, ma dude. This is 100% incorrect. Been doing this a long time, and have managed massive numbers of desktop sessions for enterprise end users.

Lookup dconf. It's the tool that manages the underlying configuration engine for Gnome specifically.

Outside of the granularity there, you could also just lock everything to a group and exclude logged in users from that group. That's a very simplistic way of explaining it, but achieves the exact same thing. You build a base image with only the apps the user needs, set execution to an inclusive group that user belongs to, and everything else to some other groups, and there you go. Dead simple.

Of course that's not how you'd do it for an org with thousands of users, but you get the point.