| Summary: | "Open terminal here" action opens shell in home directory | ||
|---|---|---|---|
| Product: | [Applications] krusader | Reporter: | Kornel Jankowski <k3rnelj> |
| Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | krusader-bugs-null, nikita+kde, toni.asensi |
| Priority: | NOR | ||
| Version First Reported In: | 2.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
/usr/share/krusader/layout.xml
/opt/krusader/share/krusader/layout.xml |
||
|
Description
Kornel Jankowski
2018-05-02 11:27:02 UTC
Hi, Kornel:
I've tried it using the latest git version of Krusader, with a clean profile, under Kubuntu 18.04, and I didn't see the problem.
Can you use the latest git version of Krusader? The "compile Krusader from source" instructions can be seen in:
https://commits.kde.org/krusader?path=INSTALL
(In reply to Toni Asensi Esteve from comment #1) > Hi, Kornel: > > I've tried it using the latest git version of Krusader, with a clean > profile, under Kubuntu 18.04, and I didn't see the problem. > > Can you use the latest git version of Krusader? The "compile Krusader from > source" instructions can be seen in: > https://commits.kde.org/krusader?path=INSTALL Hi! I've tried with a freshly compiled version (6e9de699d94414dd58d0ffe1aec3dc142705eb1b was head), and cleared all the configuration files on the paths mentioned in the installation instructions; still no luck --- wherever I try 'opening terminal here' it opens in the homedir. When I attempt to do that same thing in Dolphin, it works just fine, hence I doubt this is something outside of krusader itself... It might be the case that this is in some crazy way specific to my system, it stopped working properly when I upgraded from 16.04.4 to 18.04 lately Kornel, if you create a new user in your operating system, and with it you execute that git version of Krusader, the problem is seen? Additionally, if you execute
find / -name "layout.xml" 2>/dev/null
what does it show? It it shows some files like
/usr/share/krusader/layout.xml
/home/user/krusader/krusader/layout.xml
could you attach them to this bug report?
Created attachment 112444 [details]
/usr/share/krusader/layout.xml
the layout.xml file from the machine where the problem manifested
Created attachment 112445 [details]
/opt/krusader/share/krusader/layout.xml
The layout file from the freshly-compiled version.
Tori, as I should've checked even before reporting - for a newly created user it works fine, both on the freshly compiled and the ubuntu-packaged version. I found the files you asked about, added them as attachements with names being their paths of origin. Is there any other configuration file that the installation manual does not mention I might have failed to clear trying to get back to a fresh state? It seems that those files are correct. If you execute: find / -name "krusaderui.rc" 2>/dev/null what does it show? Could you attach those files to this bug report? If
find / -name "krusaderui.rc" 2>/dev/null
shows something like
/usr/share/kxmlgui5/krusader/krusaderui.rc
/home/user/.local/share/kxmlgui5/krusader/krusaderui.rc
[...]
then you can try exiting from Krusader, renaming
/home/user/.local/share/kxmlgui5/krusader/krusaderui.rc
to
/home/user/.local/share/kxmlgui5/krusader/krusaderui.rc.backup
executing Krusader, and trying again the 'open terminal here' functionality.
Please provide your krusaderui.rc, you may have an incorrect binding. If you can provide the information requested in comment #11, please add it. To further investigate this issue, KDE developers need the information requested in comment #11. If you can provide it, or need help with finding that information, please add a comment. No response, changing status. If you have new information, please add a comment. |