| Summary: | Latest update destroyed all my settings | ||
|---|---|---|---|
| Product: | [Unmaintained] Active | Reporter: | bkorb |
| Component: | General | Assignee: | active |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | major | CC: | carlsymons |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | unscheduled | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
bkorb
2012-03-17 16:59:39 UTC
More info about this: After much travail, I booted up in single user mode and removed all files in /tmp and /var/tmp. Everything is fine now. So it is clear that temporary state caused the kde window manager to go into the ozone and not realize where it was. Therefore: 1. the kde window manager needs better ozone detection, and 2. the user interface needs some way of saying, "I think you may need to clear your temporary state". I downgraded clear down to "major" because there is a workaround, even if Joe Random User would never find the fix. wrong product (this is nothing to do with Plasma Active) and is a downstream packaging issue. I have no idea which component of KDE this belongs in, but it is a KDE problem, tho *perhaps* with openSuSE complicity. There needs to be no possible corruption of /tmp or /var/tmp files that would render KDE unusable. There is. The update on openSuSE was recent (4 days before failure), but I had booted successfully a couple of times afterwards. No, this is a KDE issue. A few more symptoms may help isolate: * the title bar buttons were missing * most windows would not move (though some did) * the activity menu (?? "start button"?) always came up *under* any window that was resting at the bottom * everything was basically "pop under" and the overlaying windows were immobile How can that stuff be construed as being a packager problem? I think not. please do not re-open reports that have been triaged. thank you. i read your report and took an appropriate action for the report. p.s. while we appreciate bug reports and other such feedback from our users, the initial comment was not in line with our expectations from each other in our community. please check out the KDE code of conduct as that records our expectations quite clearly. thanks :) http://www.kde.org/code-of-conduct/ ``i read your report and took an appropriate action for the report.'' No, you did not. You closed it speaking of openSuSE ("downstream") as being responsible. There is no possible way that openSuSE is responsible for the fiddlings of KDE's temp files in /var/tmp and /tmp. Deleting all temp files fixed the issue. It is a KDE problem. Your refusal to look into this in any serious way is a symptom of the general KDE problem -- you seem to be isolated in your own little world and the outside interlopers have little of interest to say. I'm sure your "code of conduct" says "always be pleasant". I used to be pleasant with you-all and wish I could be. Unfortunately, that results in no response at all.
bkorg@gnu.org, Just stop. You filed a bug for the wrong product. And when informed of this, your reply was, "I have no idea which component of KDE this belongs in...". You were also informed that this was a downstream packaging issue by someone who is far more capable of assessing the situation than you are. It is really poor form--stupid even--to argue with a senior developer. Given the pattern of your behavior and self-righteous attitude, it's doubtful that you went to http://en.opensuse.org/openSUSE:Submitting_bug_reports to investigate. In your first post, you write, "Sorry for the rant." If you had learned anything from your first tantrum, you would not have ranted further. It appears that you're not sorry for ranting, but rather engage in it freely and fully justified. Here's your response to a request to a request to check out our Code of Conduct: I'm sure your "code of conduct" says "always be pleasant". I used to be pleasant with you-all and wish I could be. Unfortunately, that results in no response at all. In other words... I didn't read the Code of Conduct. You-all are all the same. You-all only respond to unpleasantness. The Code of Conduct offers much more than that--including how to get your problems solved without being abrasive. If you come back, please bring your manners. |