Bug 453756

Summary: Location bar resets after several seconds when typing
Product: [Applications] dolphin Reporter: Tracy Poff <tracy.poff>
Component: bars: locationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: REPORTED ---    
Severity: normal CC: admin+kdebugs, cesarg9, faldrian, jeremyh.contact, kfm-devel, luca76, maxime.lemonnier, nate, voidpointertonull+bugskdeorg
Priority: NOR    
Version: 22.12.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Screen recording of issue
Dolphin bug on KDE 5.26.3
/etc/inputrc
bug in Krusader 2.8.0, too!
Video demonstrating the bug with Docker

Description Tracy Poff 2022-05-13 19:00:11 UTC
SUMMARY
When typing a location in the location bar, the contents of the bar will reset to the current directory after several seconds. This doesn't happen every time, but it is very common.


STEPS TO REPRODUCE
1. Open dolphin.
2. Press CTRL+L.
3. Begin typing an address, e.g. /home/...

OBSERVED RESULT
The location shown in the address bar will reset to the current directory, losing what was typed.

EXPECTED RESULT
The typed location should not be overwritten.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
I saw this bug mentioned on 2022-01-11: https://www.reddit.com/r/kde/comments/s1m2sx/dolphin_location_navigation_refreshes/
Comment 1 Nate Graham 2022-05-16 17:35:58 UTC
Cannot reproduce the issue. Could you attach a screen recording that shows it happening?

Also can you upgrade to Frameworks 5.93 or 5.94? If either of those fixes the issue, it's possible it was fixed by https://invent.kde.org/frameworks/kio/-/commit/fdacbf4e290c856a72a5988f5a612360a76af896
Comment 2 Tracy Poff 2022-05-19 14:02:33 UTC
Created attachment 148996 [details]
Screen recording of issue
Comment 3 Tracy Poff 2022-05-19 14:05:42 UTC
(In reply to Nate Graham from comment #1)
> Cannot reproduce the issue. Could you attach a screen recording that shows
> it happening?
> 
> Also can you upgrade to Frameworks 5.93 or 5.94? If either of those fixes
> the issue, it's possible it was fixed by
> https://invent.kde.org/frameworks/kio/-/commit/
> fdacbf4e290c856a72a5988f5a612360a76af896

I've added a screen recording. I'll try upgrading tonight or tomorrow, and report back.
Comment 4 Tracy Poff 2022-05-25 03:35:39 UTC
This bug persists with KDE Frameworks version 5.94.0.
Comment 5 Bug Janitor Service 2022-06-09 04:35:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Luca76 2022-11-29 13:40:46 UTC
I confirm this bug, in Fedora 36

KDE 5.26.3
KDE Frameworks 5.100.0
QT 5.15.7
Using X11 (not Wayland)

Dolphin 22.08.1
Comment 7 Luca76 2022-11-29 13:46:49 UTC
Created attachment 154137 [details]
Dolphin bug on KDE 5.26.3

Example of this bug
Comment 8 Felix Ernst 2022-12-02 17:38:02 UTC
*** Bug 462479 has been marked as a duplicate of this bug. ***
Comment 9 Luca76 2022-12-06 08:01:50 UTC
After a reboot, the problem disappeared.
Comment 10 Sergey Popov 2022-12-06 08:03:14 UTC
(In reply to Luca Manganelli from comment #9)
> After a reboot, the problem disappeared.

Not for me, i tried to reboot and use clean profile on different user - same issue persists
Comment 11 Luca76 2022-12-06 08:05:25 UTC
(In reply to Sergey Popov from comment #10)
> Not for me, i tried to reboot and use clean profile on different user - same
> issue persists

Have you customized inputrc file (in ~/.inputrc or in /etc/inputrc)?
Comment 12 Sergey Popov 2022-12-06 08:12:05 UTC
Created attachment 154351 [details]
/etc/inputrc
Comment 13 Sergey Popov 2022-12-06 08:12:19 UTC
(In reply to Luca Manganelli from comment #11)
> Have you customized inputrc file (in ~/.inputrc or in /etc/inputrc)?

pinkbyte@oas1 ~ $ ls -la ~/.inputrc
ls: cannot access '/home/pinkbyte/.inputrc': No such file or directory
pinkbyte@oas1 ~ $ equery b /etc/inputrc 
 * Searching for /etc/inputrc ... 
sys-apps/baselayout-2.8 (/etc/inputrc)
pinkbyte@oas1 ~ $ qcheck sys-apps/baselayout
Checking sys-apps/baselayout ...
 MD5-DIGEST: /etc/hosts
  * 33 out of 34 files are good

Basically this output means: i am using Gentoo, /etc/inputrc is installed from package baselayout and it was not changed(the only file from baselayout package with different checksum is /etc/hosts). I am attaching my /etc/inputrc just in case...
Comment 14 Jérémy 2023-01-09 08:36:36 UTC
*** Bug 464038 has been marked as a duplicate of this bug. ***
Comment 15 Jérémy 2023-01-09 08:41:13 UTC
I always had and have this problem (several computers and dolphin / kde versions).
Still have no matter number of reboots.
Comment 16 Luca76 2023-01-16 14:06:51 UTC
Any development? This bug makes my dolphin completely useless, since I cannot access to my SFTP shares.

I can't even write a single character. I tried with the "Text completion" to NONE, but it is still not working.
Comment 17 Luca76 2023-01-17 08:53:10 UTC
Created attachment 155369 [details]
bug in Krusader 2.8.0, too!

This bug appears in krusader 2.8, too! I've attached a screen recording.
Comment 18 Luca76 2023-05-22 11:28:46 UTC
After updating to Fedora 38 and Dolphin 23.04.1, the problem disappeared.
Comment 19 Nate Graham 2023-05-22 17:38:46 UTC
Tracey, is that the case for you as well?
Comment 20 Sergey Popov 2023-05-24 10:03:33 UTC
I upgraded to 23.04.1, unfortunately it does not help :-(
Comment 21 Luca76 2023-06-05 07:52:32 UTC
I think I finally found the cause of this bug!

I have Docker that generates continuously (ever second) a file called /tmp/runc-* and deletes it.

This prevents the editing ability on the location bar.

Stoppoing Docker fixes this problem.
Comment 22 Luca76 2023-06-05 09:07:00 UTC
Created attachment 159472 [details]
Video demonstrating the bug with Docker

Hi, I've attached  a video showing the bug and how stopping docker, it disappears
Comment 23 Sergey Popov 2023-06-07 19:41:29 UTC
(In reply to Luca Manganelli from comment #21)
> I think I finally found the cause of this bug!
> 
> I have Docker that generates continuously (ever second) a file called
> /tmp/runc-* and deletes it.
> 
> This prevents the editing ability on the location bar.
> 
> Stoppoing Docker fixes this problem.

OMG, never thought that Docker would be culprit here!
I confirm that issue is no longer persist after stopping Docker daemon.
Thank you! At least we have workaround for now...
Comment 24 Luca76 2023-06-10 17:32:51 UTC
(In reply to Sergey Popov from comment #23)
> OMG, never thought that Docker would be culprit here!
> I confirm that issue is no longer persist after stopping Docker daemon.
> Thank you! At least we have workaround for now...

For curiosity, what docker container are you using?
Comment 25 Sergey Popov 2023-06-11 09:14:26 UTC
(In reply to Luca Manganelli from comment #24)
> For curiosity, what docker container are you using?

oas1 ~ # docker ps -a
CONTAINER ID   IMAGE                                COMMAND                      CREATED          STATUS                            PORTS     NAMES
9af29255df7b   zerotier/zerotier:1.10.6   "/entrypoint.sh af0c…"   12 hours ago   Up 12 hours (healthy)                    zerotier
Comment 26 Tracy Poff 2023-06-11 18:59:09 UTC
I also run docker. Lots of different containers (postgres, nginx, …), though not that zerotier one.
Comment 27 Faldrian 2023-07-20 13:23:25 UTC
I also have running docker (and this issue), but could not find the /tmp/runc-* file yet.
But shutting down docker is no option, since I need it constantly for work.
We need a solution for this, as it severely cripples dolphins usefullness.
Comment 28 Maxime Lemonnier 2023-08-29 15:00:59 UTC
I confirm running docker stop $(docker ps -a -q) removes the problem. I *think* I did not have the problem before I add 'fs.inotify.max_user_watches=524288' in sysctl.conf. I'd have to check. 

using Dolphin Version 21.12.3
Comment 29 Pedro V 2024-02-08 16:45:48 UTC
Does the location bar seem to track changes in the directory?
Suspected a TOCTOU problem, but in my case autocompletion seems to read the contents of the directory once, then it doesn't care about any changes at all, new directories don't appear in /tmp while at least "/t" is in the URL, have to get to just "/" so it starts autocompleting there, then getting back to "/tmp/" refreshes the cache.
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0

Attempted to reproduce with the following ran as root which should be similar to what Docker (actually runc) appears to be doing:
rm -rf /tmp/dolphintest; while :; do mkdir /tmp/dolphintest; chmod 2700 /tmp/dolphintest; sleep 1; rm -rf /tmp/dolphintest; sleep 1; done

Directory content tracking tends to break though after heavy I/O, so checked on another system too which was only likely used, but autocompletion seems to be "sticky" there too, so I'm really wondering if I'm going in the wrong direction, or autocompletion updates with changes for others.
Comment 30 Cesar Garcia 2024-04-27 03:36:12 UTC
Also happening on Plasma 6 with Dolphin 24.02.2. I am using k3s instead of Docker, and also the location bar starts working again once i stop k3s and kill all the containers.

Operating System: Arch Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-arch1-1 (64-bit)
Graphics Platform: Wayland