[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1109671: marked as done (triggered by re-mounts using Systemd-Automount : Dolphin erroneously moves 1 level (../) up in all tabs and warns about 'current location changed')

Your message dated Wed, 1 Oct 2025 18:16:22 +0200
with message-id <l7js2wvvsftihgp4rw24xgpa3smttmodkkcerpy2yoaza7rzsi@25w4anw4nodw>
and subject line close bug, because somehow fixed with an update in forky, but fix-version + pkg currently unknown
has caused the Debian Bug report #1109671,
regarding triggered by re-mounts using Systemd-Automount : Dolphin erroneously moves 1 level (../) up in all tabs and warns about 'current location changed'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1109671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109671
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: dolphin
Version: 4:25.04.2-1
Severity: important

Every midnight (checked several times shortly after 00:00) existing tabs in
dolphin (I have maybe 20 open usually) all erroneously warn about "current
location changed" and move 1 level (../) up. One can "easily" navigate back to
the last location/path with the "go back" command by pressing the respective
button or shortcut (default: backspace). If I forget to "repair" the location
of a tab, next midnight the location is moved up 1 level (../) again. This
behaviour/bug is really annoying to me. I've not seen/tested what happens on
root-level (/).
The tabs on my machine point to folder paths on different partitions using the
file-types ext4 and btrfs.

Because it's always on midnight I think the faulty behaviour is caused /
triggered by some cron-job or systemd.timer.

Recently I had hope that a bugfix in dbus-broker 37-2 would maybe fix the
issue, because some dbus+dolphin related messages appeared shortly after
midnight (but they still occur) :
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Service file
'/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named
after the D-Bus name 'org.freedesktop.FileManager1'.                │
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Service file
'/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the
D-Bus name 'org.kde.KScreen'.                                          │
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Policy to allow eavesdropping
in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
│
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Policy to allow eavesdropping
in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
│
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Kernel is missing AppArmor
DBus support.
│
│Jul 21 00:00:01 levi dbus-broker-launch[87704]: Service file
'/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named
after the D-Bus name 'org.freedesktop.Notifications'.

Looking into the journal I couldn't identify any other suspicious entries
regarding dolphin. Is there a way to log debug messages for why dolphin brings
these "current location changed" warnings?


PS : Looking forward to the trixie release.

Keep rocking, Oli


-- System Information:
Debian Release: 13.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing-proposed-updates'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.35+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dolphin depends on:
ii  baloo6                                 6.13.0-1
ii  dolphin-data                           4:25.04.2-1
ii  kio6                                   6.13.0-6
ii  libc6                                  2.41-9
ii  libdolphinvcs6                         4:25.04.2-1
ii  libkf6baloo6                           6.13.0-1
ii  libkf6baloowidgets6                    4:25.04.0-1
ii  libkf6bookmarks6                       6.13.0-1
ii  libkf6bookmarkswidgets6                6.13.0-1
ii  libkf6codecs6                          6.13.0-1
ii  libkf6colorscheme6                     6.13.0-1
ii  libkf6completion6                      6.13.0-1
ii  libkf6configcore6                      6.13.0-2
ii  libkf6configgui6                       6.13.0-2
ii  libkf6configwidgets6                   6.13.0-1
ii  libkf6coreaddons6                      6.13.0-1
ii  libkf6crash6                           6.13.0-1
ii  libkf6dbusaddons6                      6.13.0-1
ii  libkf6filemetadata3                    6.13.0-1
ii  libkf6guiaddons6                       6.13.0-1
ii  libkf6i18n6                            6.13.0-1
ii  libkf6iconthemes6                      6.13.0-2
ii  libkf6jobwidgets6                      6.13.0-1
ii  libkf6kcmutils6                        6.13.0-2
ii  libkf6kcmutilscore6                    6.13.0-2
ii  libkf6kiocore6                         6.13.0-6
ii  libkf6kiofilewidgets6                  6.13.0-6
ii  libkf6kiogui6                          6.13.0-6
ii  libkf6kiowidgets6                      6.13.0-6
ii  libkf6newstuffwidgets6                 6.13.0-1
ii  libkf6notifications6                   6.13.0-1
ii  libkf6parts6                           6.13.0-1
ii  libkf6service-bin                      6.13.0-1
ii  libkf6service6                         6.13.0-1
ii  libkf6solid6                           6.13.0-1
ii  libkf6textwidgets6                     6.13.0-1
ii  libkf6userfeedbackcore6                6.13.0-1
ii  libkf6userfeedbackwidgets6             6.13.0-1
ii  libkf6widgetsaddons6                   6.13.0-1
ii  libkf6windowsystem6                    6.13.0-2
ii  libkf6xmlgui6                          6.13.0-1
ii  libpackagekitqt6-1                     1.1.2-1+b1
ii  libphonon4qt6-4t64                     4:4.12.0-5
ii  libqt6core6t64 [qt6-base-private-abi]  6.8.2+dfsg-8
ii  libqt6dbus6                            6.8.2+dfsg-8
ii  libqt6gui6                             6.8.2+dfsg-8
ii  libqt6widgets6                         6.8.2+dfsg-8
ii  libqt6xml6                             6.8.2+dfsg-8
ii  libstdc++6                             14.2.0-19
ii  phonon4qt6                             4:4.12.0-5

Versions of packages dolphin recommends:
ii  dolphin-doc                4:25.04.2-1
ii  dolphin-plugins            4:25.04.0-1
ii  ffmpegthumbs               4:25.04.0-2
ii  kdegraphics-thumbnailers   4:25.04.0-1
ii  kdenetwork-filesharing     4:25.04.0-1
ii  kimageformat6-plugins      6.13.0-2
ii  kio-extras                 4:25.04.2-1
ii  qt6-image-formats-plugins  6.8.2-4

Versions of packages dolphin suggests:
pn  kio-admin  <none>

-- no debconf information

--- End Message ---
--- Begin Message --- 
STATUS :

The good news is that after some pkg update in testing/forky the bug is not occuring anymore (so far). 
Lucky me, because this problem was super annoying every day.

CAUSE and AFFECTED VERSIONS :

I narrowed down the cause / trigger to using SystemD-Automount and Dolphin, 
after searching upstream for similar bug reports (https://bugs.kde.org/buglist.cgi?quicksearch=dolphin%20location%20changed) 
and came across "Dolphin Navigates Up One Level Each Time Automount Times Out" (https://bugs.kde.org/show_bug.cgi?id=500413). 
So, I deactivated the Automount in fstab for the external hdd and the problem was gone!

I first used the automount feature with Dolphin on the Plasma 6 generation in early 2025. 
I guess the problem was introduced between 5.27.5-2 (latest 5.x) and 6.3.0-1

REPRODUCTION REQUIREMENTS :

The critical entry in fstab is like this :
/dev/mapper/wd-usb-crypt1   /mnt/usb-back1  ext4  noatime,nodiratime,errors=remount-ro,nofail,x-systemd.automount,x-systemd.device-timeout=5s,x-systemd.idle-timeout=5min   0   2

Yes this drive is also encrypted, but that made no difference in my reproduction scenarios.

KNOWN TRIGGERS :

A trigger was most probably something like (p)locate that is configured to be run short after midnight on my machine :
$ journalctl -eu mnt-usb\\x2dback1.automount
Sep 30 20:39:47 levi systemd[1]: Set up automount mnt-usb\x2dback1.automount.
Oct 01 00:02:01 levi systemd[1]: mnt-usb\x2dback1.automount: Got automount request for /mnt/usb-back1, triggered by 25225 (updatedb.plocat)

Another trigger was installing a kernel update. I assume somehow mounts are touched during the update process.

A simple 'ls /mnt/usb-back1' or similar did NOT trigger the issue!

OTHER OBSERVATIONS :

Interestingly the unwanted behaviour only occurred after midnight in Dolphin, when a tab was selected/focussed 
that didn't begin with /home/<current-logged-in-plasma-user>/ .
Not even a single tab pointed to a folder on the automounted external hdd. 
However, a link to the external device was displayed in the Places panel.

ACTIVITIES + CONCLUSION :

So I tried to reproduce the problem in Virtual Machines on "original debian trixie (no updates installed, no point release)", 
as well as recent "debian testing/forky", "kde neon dev" and new immutable "kde linux" distros, but was NOT successfull.

In the mean time I stayed with Debian testing, the transition to forky happened and 
some update of pkgs between SystemD and Dolphin seems to fix the issue. 
So closing the bug for now.

- Oli

--- End Message ---
Reply to: