Hi Riccardo,
On 2025-10-28 14:36:40 +0100 Riccardo Mottola
<[email protected]> wrote:
(...)
How are things with this? Ever happened again?
It did to me - I cannot have a certain way to reproduce it. I thought
it was
triggered by actions like renaming, but I was able to observe it
without.
Stupid things it always takes days.
Things that I guess might trigger are:
- presence of the inspector, maybe only the content inspector and
changing/observing many files
- switching between many directories, perhaps with inspector open
- changes of files "under the hood" by other process (uncertain, most
often,
nothing happens)
The latter should affect more fswatcher, but maybe messages get
htrough? I
don't know.
As I am testing AGNoStep C5C, I noted a more unstable behaviour: It
often happens when I move a document icon on an app icon (namely
TextEdit) on the left Dock: it is as the two docks were conflicting
about which handles the DND action.
On the left Dock (which belongs to GWorkspace) I have only GNUstep app
icons (GWorkspace, TextEdit, SimpleAgenda, Terminal, GNUMail,
InnerSpace and the Recycler) while on the right dock (GWDock) I have
mostly dockapps and only two docked GNUstep apps: AClock and TimeMon.
As I have Dunst notification message in the autostart script, when the
issue happens, I can see this notification shown. So I guess the
autostart is called again, as Window Maker was started again, but all
the GNUstep apps windows are still there: none is closed. So this is
weird, because, unless I see the notification, I could not guess
something unexpected happened.
I think this issue will be difficult to analyse because it is a
GWorkspace and a Window Maker interaction.
Cheers,
Patrick
--
Patrick Cardona - Pi400 - GNU/Linux aarch64 (Debian 13.1)
Xorg (1:7.7+24) - libcairo2 (1.18.4-1+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: AGNOSTEP
- MUA: GNUMail (1.4.0)
