[Bug 1017533] New: Krusader left/right arrow behavior wrong: doesn't navigate columns but changes directory
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533 Bug ID: 1017533 Summary: Krusader left/right arrow behavior wrong: doesn't navigate columns but changes directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 URL: https://bugs.kde.org/show_bug.cgi?id=374238 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: gennady.uraltsev@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This bug appears upstream here: https://bugs.kde.org/show_bug.cgi?id=374238 The problem is that in brief visualization mode the behavior of arrow keys has inadvertently changes and rendering the software completely unusable. The left-right keys are supposed to navigate the columns to the left and to the right in brief mode. The bug changed this behavior and now left key goes to the parent folder while right folder descends. This bug has been fixed by a commit today. It seems a simple fix and it is important to backport it. Would this be possible, otherwise Krusader in the main repos is essentially broken. Thank you in advance. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
Gennady Uraltsev
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c1
--- Comment #1 from Gennady Uraltsev
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c2
--- Comment #2 from Gennady Uraltsev
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c3
--- Comment #3 from Gennady Uraltsev
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c4
--- Comment #4 from Gennady Uraltsev
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c5
Wolfgang Bauer
Does anyone even look at these bugs?
Yes. But krusader is not the only package we provide, and this is also not the only bug report we got in the last weeks, and personally I was a bit out of touch during the holiday season (and even sick for a few days this week). Not to mention that this is a community distribution, many people just work on it in their spare time (me included). And just for the record, you reported this less than a week ago. No need to get impatient already, especially in this time of the year. I will add the upstream fix, but I don't consider this "Major" so lowering the severity. After all, this is just a "wrong" handling of the cursor keys for some particular operation mode, which still works fine using the mouse. I don't see how this "essentially breaks" krusader. Also, we do not even install krusader by default. Btw, it doesn't help much to attach a modified spec file here. We do know how to add patches... ;) And attaching the patch is not really necessary either if you already point to the upstream bug report and/or commit. If you do want to help/contribute, better branch the package on OBS (krusader is maintained in KDE:Extra), add the patch and submit it back. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c6
--- Comment #6 from Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c7
--- Comment #7 from Gennady Uraltsev
Btw, it doesn't help much to attach a modified spec file here. We do know how to add patches... ;) And attaching the patch is not really necessary either if you already point to the upstream bug report and/or commit.
I have no doubt that you know how to apply patches. I tried to be helpful by making sure that the upstream commit can be applied to the version in Leap 42.2. I built the RPM on my system to check that there were no unintended consequences and reported my findings here.
If you do want to help/contribute, better branch the package on OBS (krusader is maintained in KDE:Extra), add the patch and submit it back.
I am not an expert coder but I often backport bugfixes from upstream into rpms on my system. I was wondering how I could I be most useful for the community with this skill. Any suggestions are welcome. I was not familiar with branch and resubmit things on OBS.
I will add the upstream fix, but I don't consider this "Major" so lowering the severity.
Obviously it is not "Major" at the level of the whole distribution. It does however impact usability a lot for most use cases of krusader. One of the primary features of this file manager is a high level of control using keyboard alone (it is close to MC in this aspect). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c9
--- Comment #9 from Wolfgang Bauer
Sorry, I didn't want to pass off as disrespectful. It was an authentic question: I was wondering if I should post the thing here or maybe somewhere else.
Ok. Sorry too, my reply was maybe a bit too harsh. But I noticed this bug report a few hours earlier and planned to add the fix to our packages in the evening. Then after going through another dozens of bug reports (not all related to KDE), I read your question, and somehow it seemed to imply to me an accusation that we were just ignoring bug reports here... I probably overreacted a bit.
I have no doubt that you know how to apply patches. I tried to be helpful by making sure that the upstream commit can be applied to the version in Leap 42.2. I built the RPM on my system to check that there were no unintended consequences and reported my findings here.
And that's fine and welcome. But as I wrote, it doesn't really help to attach things here that are already common knowledge (like how to modify the specfile, or a patch you provided a link to anyway). This was not meant as criticism, just a hint to save you unnecessary work in the future.
I am not an expert coder but I often backport bugfixes from upstream into rpms on my system. I was wondering how I could I be most useful for the community with this skill. Any suggestions are welcome. I was not familiar with branch and resubmit things on OBS.
You don't have to be an expert coder for that obviously, and you already did (most of) the necessary work yourself anyway. (as another side-note, we do not use the %changelog entry in the specfile anymore, each package has a separate .changes file nowadays) FYI, openSUSE packages are created/maintained in OBS: http://build.opensuse.org/ You should be able to login there with the same credentials as here in bugzilla. Further explanations would probably be out of scope of this bug report, but see here: https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap (most things can be done via the web interface too) And there's the buildservice forum for further questions: https://forums.opensuse.org/forumdisplay.php/692-Open-Build-Service-(OBS) I'm only mentioning this in case your interested though, I do not expect you to do this actually.
Obviously it is not "Major" at the level of the whole distribution. It does however impact usability a lot for most use cases of krusader. One of the primary features of this file manager is a high level of control using keyboard alone (it is close to MC in this aspect).
I'm sure that bug annoyed you and it affects your workflow. However, I still disagree that it is a "Major loss of function" (which is implied by a severity of "Major", see https://bugzilla.opensuse.org/page.cgi?id=importance_matrix.html) even if one considers krusader alone. Brief view is not even the default, and that problem definitely doesn't make krusader completely unusable as you put it. Anyway, there's no point in discussing this point further IMNSHO, the fix is submitted (it's already in Tumbleweed btw) and the severity of this bug report doesn't influence the further 42.2 maintenance workflow at all... Thanks for your report though! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533
http://bugzilla.opensuse.org/show_bug.cgi?id=1017533#c11
Wolfgang Bauer
participants (1)
-
bugzilla_noreply＠novell.com