Skip to content

A community workbench for Linux desktops

GooeyLinux Desktop workshop
Discussion view

Testing a theme on a second account.

A full reading thread. The opening note sets a careful test, the reply adds a check, and the follow up records what changed.

Thread note

This reading view is part of the static edition. It shows the shape of a useful thread without inventing member names, post counts, or scores. The live board is the place for real replies.

Opening note

Workshop note

I want to try a new theme on my daily machine, but I do not want a broken session in the middle of a work day. My plan is to make a second user account, install the theme there, and keep the first account untouched. Is that enough, or should I also keep the old theme folder somewhere safe?

Desktop: GNOMEDistribution: current release

Reply

Workshop note

The second account is a good start. Copy the theme folder into that account, not the system folder, and open a fresh session before you judge the result. Keep a copy of the old theme folder as well. A theme can load in one app and fail in another, so test a file manager, a settings window, and a dialog with a text entry.

Adds: a test listNo files required

Follow up

Result

The second account worked. The theme appeared in the settings list, and the dialog test showed one low contrast label on a dark surface. I kept the theme, changed one color, and wrote the change in the release thread. The first account was never touched.

Outcome: theme keptNote added to the release

Why this thread works

  • The opening note names the desktop, the goal, and the risk.
  • The reply adds a concrete test instead of a general opinion.
  • The follow up records the result, including the one problem found.
  • The license and the credit belong in the release thread, not in a reply that is easy to miss.

Try the same pattern

Use a separate account for the first run. Test more than one kind of window. Keep a copy of the old theme. If a label disappears, treat it as a contrast problem and check the theme file before you blame the toolkit.