As a software developer, hearing “it works on my machine” from a subset of users is actually helpful information. It means the problem is environmental, or data related, instead of an explicit code issue. It does narrow things down a bit.
The issue arises when some people treat it as a reason to ignore a problem.
I mean, that’s basically how I find the root cause of problems that occur in one environment but not the other.
Most recently was when a plasma desktop of any newly created user wouldn’t shut down properly, at logout it would hang for about a minute with an error in the logs stating that plasma-plasmashell.service was not responding to a sigterm, and was then ultimately force killed by systemd. On my main desktop, I didn’t have this issue.
By meticulously diffing plasma related config files, I found that the culprit was in ~/.config/plasma-org.kde.plasma.desktop-appletsrc. Disabling a few system tray applets that I didn’t need (and that I indeed had already disabled on my main desktop) fixed the issue.
As a software developer, hearing “it works on my machine” from a subset of users is actually helpful information. It means the problem is environmental, or data related, instead of an explicit code issue. It does narrow things down a bit.
The issue arises when some people treat it as a reason to ignore a problem.
Yeah it’s just a problem of generating a
diffand having a quick look /jI mean, that’s basically how I find the root cause of problems that occur in one environment but not the other.
Most recently was when a plasma desktop of any newly created user wouldn’t shut down properly, at logout it would hang for about a minute with an error in the logs stating that
plasma-plasmashell.servicewas not responding to a sigterm, and was then ultimately force killed by systemd. On my main desktop, I didn’t have this issue.By meticulously diffing plasma related config files, I found that the culprit was in
~/.config/plasma-org.kde.plasma.desktop-appletsrc. Disabling a few system tray applets that I didn’t need (and that I indeed had already disabled on my main desktop) fixed the issue.