| Summary: | When trying to launch the desktop icon on desktop view you are asked "root password" to continue Tumbleweed | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | stakanov |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | bshah, mklapetek, plasma-bugs-null |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.5.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
stakanov
2016-02-17 10:43:23 UTC
>#7 0x00007f1066867bce in KJob::exec() () from /usr/lib64/libKF5CoreAddons.so.5
Bah, there's our problem
Can you give me steps on how you brought up that dialog please.
Hello. I am sorry that I will not be able to help you more than with the description to reproduce this (as long as you do not have the same snapshot under hand with a machine running a Nvidia Graphicscard with nouveau drivers) - in that way I am sure and certain you have my very same condition. That snapshot came out with that particularity. The dialogue came up very very straightforward. I had "desktopview" on my main desktop. The very default outlay of Tumbleweed (no magic, no particularity). After the update (and reboot) for that snapshot, there was that behavior from then on: left click on the desktop icon to open /home folder you would be presented the dialogue to input the root password. Of course I did NOT do this. I said cancel. Now the funny thing: that opened a window of dolphin anyway, claiming to be ... superuser dolphin but ...afaik without superuser rights. I was able e.g. to open files in the root directory (rc for example) folder but they would open read only. Why I did this: well I wanted to know if, without password, if dolphin superuser was written (having canceled the password) I would have been superuser. AFAIK no. That circumstance persisted up to the next snapshot (currently it is not any more the case, but now the have the mimetype "screwed up" so that, when you open /home it would open with gwenview). So if the error is interesting to you : I am quite sure there should be the archives of that snapshot. And it should give that error. With the rolling releases and their speed you have unfortunately that limitation of repeatability. However since this was repeatable always and since clicking on "properties" would crash plasma, that did ring an alarm bell (always rings when a root password is asked without reason, sorry for the paranoia) and that was the motivation to report the bug. So to reproduce: left click with the mouse on the home folder of desktop view of that snapshot (that is normal folder selection - every day task) and that will reproduce this problem. Furthermore any right click on the icon crashes plasma with the report I did sent in. With that particular snapshot I can confirm that it was repeatable - always. Sorry for not having more to give you. But since the desktop is still there, updated of course, please tell me if you want to have some log, some config or whatever else. Happy to help whenever I can. So do I understand it correctly that you cannot reproduce this anymore? No, in the very moment tumbleweed does not crash any more. That snapshot had the issue. Since then they are a few versions of KDE further so now we have a mime type problem, the trash opens with gwenview etc. These are things that come and go. Still I wanted to report it as a) when the automatized procedure of the crash starts I usually think it is useful to report (if there is no duplicate) b) it was especially irritating because of the root password. Please advice me if you do NOT wish crashes of tumbleweed to be reported (or better if you want them first reported to the distribution) as it is one of the major problems of users not to know if a crash shall be reported to KDE, shall be reported downstream or even not reported at all... Especially with a rolling distribution. That is something one get regularly a mouthwash with soap. When you do report it, as the turnover is so terrible fast, you simply cannot know if this will be fixed, if it is packaging related or else. In general I am stupidly trusting the "stars" of konqi and deliver if either that problem is recurrent (as it was in that snapshot, happened always) or if it claims excellent content. So you can close it if you deem useless, I apologize if it enters in the "noise". Had no intention to make you people loose time for nothing. It's certainly ok if you file any bugs, thanks for that. However if there is no reliable way for us to reproduce it and/or if you cannot reproduce it with couple subsequent builds of rolling packages, that report becomes less useful for us because there isn't much we can do as the bug stems from wrong integration on distro level. Please continue submitting crashes and bug reports, but always see if you can reproduce it between several rolling builds first. |