[gentoo-user] Dolphin confusing different run instances.

[gentoo-user] Dolphin confusing different run instances.

[Dale]

Howdy,

I use Dolphin a lot.  I like it and all but recently, it started doing
something that annoys me.  When I'm doing something, I tend to open a
instance of Dolphin for whatever it is I'm doing.  I also leave
instances open and ready for when I do routine things.  Some things I do
so often, I leave them open all the time.  Usually that is four
instances.  If needed, for example when I'm getting videos off trail
cameras, I open another instance until I'm done with that task.  So, I
use Dolphin for different things on different desktops with tabs in
different places.  It just makes things easier, faster and works best
for me. 

What I don't like is this, when I open a new instance, it tries to copy
the last instance I used that is still open.  When I open a new
instance, I want it to open where I want but not be affected by other
instances that are running.  Just as a example.  Yesterday I was trying
to copy videos from my trail cameras to a USB stick while also copying
and organizing them on my hard drive.  When I put in a USB stick or the
card from the camera, I click the notification thing and tell it to open
the USB stick or the card.  Thing is, it tries to copy the instance,
usually the one I use to watch TV from, which has a lot of open tabs.  I
have to close all the tabs I don't want to get things like it should be
to begin with. 

I also have KDE set to save my session.  When I first login with four
saved instances, it creates a mess.  Sometimes, it just jumbles them
up.  Sometimes it sort of works.  It never works like it used to tho. 
Also, sometimes the Folder panel on the left doesn't work either.  It's
either blank or only has /bin and nothing else.  Nothing I do gets it to
work right so I have to start a new instance and close the broken one. 

This is fairly new and very consistent.  It started a couple updates ago
and I was hoping it was a bug and would be fixed.  I'm starting to think
it is a new feature.  I've looked in preferences and can't find any
setting related to this behavior.  Smplayer for example has a setting
for either multiple or single instances.  It works the way you set it. 
I can't find anything similar in Dolphin tho. 

Anyone have any info on this?  Is this the new way Dolphin works?  Is
there a way to disable it somewhere?  Do I need to look for another file
manager that behaves like I want? 

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] Dolphin confusing different run instances.

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]

Am Thu, Sep 12, 2024 at 07:54:25AM -0500 schrieb Dale:
> Howdy,
> 
> I use Dolphin a lot.  I like it and all but recently, it started doing
> something that annoys me.  When I'm doing something, I tend to open a
> instance of Dolphin for whatever it is I'm doing.  I also leave
> instances open and ready for when I do routine things.  Some things I do
> so often, I leave them open all the time.  Usually that is four
> instances.  If needed, for example when I'm getting videos off trail
> cameras, I open another instance until I'm done with that task.  So, I
> use Dolphin for different things on different desktops with tabs in
> different places.  It just makes things easier, faster and works best
> for me. 
> 
> What I don't like is this, when I open a new instance, it tries to copy
> the last instance I used that is still open.  When I open a new
> instance, I want it to open where I want but not be affected by other
> instances that are running.  Just as a example.  Yesterday I was trying
> to copy videos from my trail cameras to a USB stick while also copying
> and organizing them on my hard drive.  When I put in a USB stick or the
> card from the camera, I click the notification thing and tell it to open
> the USB stick or the card.  Thing is, it tries to copy the instance,
> usually the one I use to watch TV from, which has a lot of open tabs.  I
> have to close all the tabs I don't want to get things like it should be
> to begin with. 

Dolphin settings, very first page, very first setting: set it to open a 
fixed location at startup. Then it will not restore any previous internal 
state.

-- 
Grüße | Greetings | Salut | Qapla’
Abolish Christmas, Joseph confessed everything!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Dolphin confusing different run instances.

[Dale]

[-- Attachment #1: Type: text/plain, Size: 3320 bytes --]

Frank Steinmetzger wrote:
> Am Thu, Sep 12, 2024 at 07:54:25AM -0500 schrieb Dale:
>> Howdy,
>>
>> I use Dolphin a lot.  I like it and all but recently, it started doing
>> something that annoys me.  When I'm doing something, I tend to open a
>> instance of Dolphin for whatever it is I'm doing.  I also leave
>> instances open and ready for when I do routine things.  Some things I do
>> so often, I leave them open all the time.  Usually that is four
>> instances.  If needed, for example when I'm getting videos off trail
>> cameras, I open another instance until I'm done with that task.  So, I
>> use Dolphin for different things on different desktops with tabs in
>> different places.  It just makes things easier, faster and works best
>> for me. 
>>
>> What I don't like is this, when I open a new instance, it tries to copy
>> the last instance I used that is still open.  When I open a new
>> instance, I want it to open where I want but not be affected by other
>> instances that are running.  Just as a example.  Yesterday I was trying
>> to copy videos from my trail cameras to a USB stick while also copying
>> and organizing them on my hard drive.  When I put in a USB stick or the
>> card from the camera, I click the notification thing and tell it to open
>> the USB stick or the card.  Thing is, it tries to copy the instance,
>> usually the one I use to watch TV from, which has a lot of open tabs.  I
>> have to close all the tabs I don't want to get things like it should be
>> to begin with. 
> Dolphin settings, very first page, very first setting: set it to open a 
> fixed location at startup. Then it will not restore any previous internal 
> state.
>
> -- Grüße | Greetings | Salut | Qapla’ Abolish Christmas, Joseph
> confessed everything!


I saw that setting.  First place I looked.  Thing is, since I didn't
want it to always start at the same place, I thought that wouldn't
work.  I thought that no matter what I clicked, it would open at that
place.  Given you said that would work, I tried it.  I set it to /, or
root, but if I click on a folder on the desktop, sure enough, it starts
and opens the folder I clicked on.  Did that a few times just to be
sure.  LOL  I also plugged in a USB stick, mounted it and then told the
notification thingy to open in File Manager.  Yep, it opened right where
it should.  I was looking for a instance setting or something since it
kept copying other running instances and their tabs.  I wouldn't have
ever thought to try that setting.

They might want to explain that setting a little bit.  While I saw it, I
certainly didn't expect it to behave this way.  I expected it to open at
that location no matter how Dolphin was started. 

I'll play with this a few days but so far, looks like a good solution. 

Thanks much.  I can stop pulling my hair out now. 

Dale

:-)  :-) 

P. S.  Planning to try that checksum script soon.  It's a large number
of files so it will take a long time to run.  I think you mentioned that
if stopped, it will resume where it left off.  Oh, I did use rsync and
checksum option on backups the other day.  I couldn't check all the
files tho.  I just checked the ones recently accessed.  It found four
out of the few hundred I checked.  I restored them after some testing. 

[-- Attachment #2: Type: text/html, Size: 4155 bytes --]

Re: [gentoo-user] Dolphin confusing different run instances.

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 3303 bytes --]

Am Thu, Sep 12, 2024 at 08:53:17AM -0500 schrieb Dale:

> Frank Steinmetzger wrote:
> > Am Thu, Sep 12, 2024 at 07:54:25AM -0500 schrieb Dale:
> >> Howdy,
> >>
> >> I use Dolphin a lot.  I like it and all but recently, it started doing
> >> something that annoys me.  When I'm doing something, I tend to open a
> >> instance of Dolphin for whatever it is I'm doing.  I also leave
> >> instances open and ready for when I do routine things.  Some things I do
> >> so often, I leave them open all the time.  Usually that is four
> >> instances.  If needed, for example when I'm getting videos off trail
> >> cameras, I open another instance until I'm done with that task.  So, I
> >> use Dolphin for different things on different desktops with tabs in
> >> different places.  It just makes things easier, faster and works best
> >> for me. 
> >> […]
> > Dolphin settings, very first page, very first setting: set it to open a 
> > fixed location at startup. Then it will not restore any previous internal 
> > state.
> 
> I saw that setting.  First place I looked.  Thing is, since I didn't
> want it to always start at the same place, I thought that wouldn't
> work.  I thought that no matter what I clicked, it would open at that
> place.  Given you said that would work, I tried it.  I set it to /, or
> root, but if I click on a folder on the desktop, sure enough, it starts
> and opens the folder I clicked on.  Did that a few times just to be
> sure.  LOL  I also plugged in a USB stick, mounted it and then told the
> notification thingy to open in File Manager.  Yep, it opened right where
> it should.  I was looking for a instance setting or something since it
> kept copying other running instances and their tabs.  I wouldn't have
> ever thought to try that setting.
> 
> They might want to explain that setting a little bit.  While I saw it, I
> certainly didn't expect it to behave this way.  I expected it to open at
> that location no matter how Dolphin was started. 

Perhaps it’s actually a bug. Even if Dolphin is supposed to restore a 
previous session, it *should* open the location it is given by parameter.

> P. S.  Planning to try that checksum script soon.  It's a large number
> of files so it will take a long time to run.  I think you mentioned that
> if stopped, it will resume where it left off.

Only if it creates checksums, because it knows by the existence of checksums 
where to resume. But if you want to read checksums and verify them, you need 
to use arguments to tell it how many directories to process and how many to 
skip at the beginning.

Perhaps try it first with a few small directories to get a feel for its 
behaviour. The normal way to go is:

dh -u [DIR] to create the checksum files
dh [DIR] do read it back
Use the --skip option to skip the given number of dirs at the beginning.

Remember that by default it will not create checksums in directories that 
have subdirectories. I know this sounds a little strange, but for a 
hierarchy of music albums, this seemed sensible 10 years ago.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

Big events may cast their shadow under the eyes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Dolphin confusing different run instances.

[Dale]

Frank Steinmetzger wrote:
> Am Thu, Sep 12, 2024 at 08:53:17AM -0500 schrieb Dale:
>
>> Frank Steinmetzger wrote:
>>> Am Thu, Sep 12, 2024 at 07:54:25AM -0500 schrieb Dale:
>>>> Howdy,
>>>>
>>>> I use Dolphin a lot.  I like it and all but recently, it started doing
>>>> something that annoys me.  When I'm doing something, I tend to open a
>>>> instance of Dolphin for whatever it is I'm doing.  I also leave
>>>> instances open and ready for when I do routine things.  Some things I do
>>>> so often, I leave them open all the time.  Usually that is four
>>>> instances.  If needed, for example when I'm getting videos off trail
>>>> cameras, I open another instance until I'm done with that task.  So, I
>>>> use Dolphin for different things on different desktops with tabs in
>>>> different places.  It just makes things easier, faster and works best
>>>> for me. 
>>>> […]
>>> Dolphin settings, very first page, very first setting: set it to open a 
>>> fixed location at startup. Then it will not restore any previous internal 
>>> state.
>> I saw that setting.  First place I looked.  Thing is, since I didn't
>> want it to always start at the same place, I thought that wouldn't
>> work.  I thought that no matter what I clicked, it would open at that
>> place.  Given you said that would work, I tried it.  I set it to /, or
>> root, but if I click on a folder on the desktop, sure enough, it starts
>> and opens the folder I clicked on.  Did that a few times just to be
>> sure.  LOL  I also plugged in a USB stick, mounted it and then told the
>> notification thingy to open in File Manager.  Yep, it opened right where
>> it should.  I was looking for a instance setting or something since it
>> kept copying other running instances and their tabs.  I wouldn't have
>> ever thought to try that setting.
>>
>> They might want to explain that setting a little bit.  While I saw it, I
>> certainly didn't expect it to behave this way.  I expected it to open at
>> that location no matter how Dolphin was started. 
> Perhaps it’s actually a bug. Even if Dolphin is supposed to restore a 
> previous session, it *should* open the location it is given by parameter.

Well, so far it has been working fine.  I've had to open a couple things
and have been using instances that I have running all the time.  It's
working like I want it seems. 


>> P. S.  Planning to try that checksum script soon.  It's a large number
>> of files so it will take a long time to run.  I think you mentioned that
>> if stopped, it will resume where it left off.
> Only if it creates checksums, because it knows by the existence of checksums 
> where to resume. But if you want to read checksums and verify them, you need 
> to use arguments to tell it how many directories to process and how many to 
> skip at the beginning.
>
> Perhaps try it first with a few small directories to get a feel for its 
> behaviour. The normal way to go is:
>
> dh -u [DIR] to create the checksum files
> dh [DIR] do read it back
> Use the --skip option to skip the given number of dirs at the beginning.
>
> Remember that by default it will not create checksums in directories that 
> have subdirectories. I know this sounds a little strange, but for a 
> hierarchy of music albums, this seemed sensible 10 years ago.
>

Well, I read through the help page and settled on this.  I might have
did this wrong.  ;-)

/root/dh -c -F 1Checksums.md5 -v

Right now I have the command in /root.  I just did a cd to the parent
directory I wanted it to work on and then ran that command.  Right now,
it is working on this bit.


(dir 141 of 631)

and

(file  8079 of 34061)

It has been running for about 6 hours or so now.  I think it's gonna
take a while.  I asked it to change the name a bit so that the checksum
file would be at the top.  That way if I go to a directory and want to
watch every video in that directory, I can do a CTRL + A and then hold
the control key and click to deselect the checksum file which should be
at the top.  Then start the video player.

I was wondering tho, is there a way to make it put all the checksum
files in one place, like a directory call checksums, and they just all
go in there?  Or just a single file in the parent directory?  That way
the files aren't in each directory.  Thing is, can I still just run it
on one directory if I have a suspected bad one?  Your tool does a lot. 

So far, yet another awesome script tool.  Awesome work.  This should
pick up on file problems easy enough. 

Dale

:-)  :-) 

P. S.  USPS claimed my memory sticks would arrive by Wednesday.  Still
not there.  Just says arriving late now.  Should have sent via UPS or
something.  LOL  Oh, did get some rain today.  Also got some serious wind. 

Re: [gentoo-user] Dolphin confusing different run instances.

[Frank Steinmetzger]

[-- Attachment #1: Type: text/plain, Size: 3370 bytes --]

Am Fri, Sep 13, 2024 at 01:19:00AM -0500 schrieb Dale:

> >> P. S.  Planning to try that checksum script soon.  It's a large number
> >> of files so it will take a long time to run.  I think you mentioned that
> >> if stopped, it will resume where it left off.
> > Only if it creates checksums, because it knows by the existence of checksums 
> > where to resume. But if you want to read checksums and verify them, you need 
> > to use arguments to tell it how many directories to process and how many to 
> > skip at the beginning.
> >
> > Perhaps try it first with a few small directories to get a feel for its 
> > behaviour. The normal way to go is:
> >
> > dh -u [DIR] to create the checksum files
> > dh [DIR] do read it back
> > Use the --skip option to skip the given number of dirs at the beginning.
> >
> > Remember that by default it will not create checksums in directories that 
> > have subdirectories. I know this sounds a little strange, but for a 
> > hierarchy of music albums, this seemed sensible 10 years ago.
> >
> 
> Well, I read through the help page and settled on this.  I might have
> did this wrong.  ;-)
> 
> /root/dh -c -F 1Checksums.md5 -v
> 
> Right now I have the command in /root.  I just did a cd to the parent
> directory I wanted it to work on and then ran that command.  Right now,
> it is working on this bit.
> 
> 
> (dir 141 of 631)
> 
> and
> 
> (file  8079 of 34061)

I am thinking about adding filesize information, but that would require 
updating the status line during the processing of a file instead of only 
between files. That’s not trivial, as it involves timers and threads.

> I was wondering tho, is there a way to make it put all the checksum
> files in one place, like a directory call checksums, and they just all
> go in there?

Hm … from an algorithmic point of view, it would actually not be that 
complicated by creating a shortened filename from the source directory, but 
the real-world use seems a bit far-fetched. Checksums should be close to 
their data. If you have read errors for either, then the other is useless 
anyways. :D

> Or just a single file in the parent directory?  That way
> the files aren't in each directory.

That’s what the -s option is for. This will create only one checksum file at 
the root level for each directory argument. So if you run `dh -us foo/ bar/`, 
then it will go into foo/, create one checksum file there and put all lines 
into that one file, even for subdirectories, and do the same in bar/.

However, at the moment automatically detecting and properly verifying those 
files is still in the works. So I think you have to use the -s option or -F 
all to read them.

> Thing is, can I still just run it
> on one directory if I have a suspected bad one?

Not with one checksum file at the root level for an entire tree. The way I 
would handle this case: run dh -u on the directory of interest and then 
compare the checksums in the root-level file and the newly created file with 
a diff tool. Or copy the lines from the existing checksum file, create a new 
file in the directory of interest, remove the directory part of the paths 
and then run dh on just that directory.

-- 
Grüße | Greetings | Salut | Qapla’
I don’t have a problem with alcohol, just without!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Dolphin confusing different run instances.

[Peter Humphrey]

On Thursday 12 September 2024 13:54:25 BST Dale wrote:

> This is fairly new and very consistent.  It started a couple updates ago
> and I was hoping it was a bug and would be fixed.  I'm starting to think
> it is a new feature.  I've looked in preferences and can't find any
> setting related to this behavior.

Is it related to the recent problem in sddm or plasma, in which things appear 
on the wrong desktops on startup, or all piled up on top of one another?

-- 
Regards,
Peter.

Re: [gentoo-user] Dolphin confusing different run instances.

[Dale]

Peter Humphrey wrote:
> On Thursday 12 September 2024 13:54:25 BST Dale wrote:
>
>> This is fairly new and very consistent.  It started a couple updates ago
>> and I was hoping it was a bug and would be fixed.  I'm starting to think
>> it is a new feature.  I've looked in preferences and can't find any
>> setting related to this behavior.
> Is it related to the recent problem in sddm or plasma, in which things appear 
> on the wrong desktops on startup, or all piled up on top of one another?
>


Not this time.  There was a setting for this but I didn't think it would
do what I wanted so I didn't try it.  Frank mentioned that was the
correct setting and I tried it.  Sure enough, that was the problem.  I
figured I either missed something or Dolphin just made a big change. It
was me. 

I will say this to tho, I was getting the same plasma thing until I
started setting up window rules for all my apps.  I also removed the
plasma panel thingy at the bottom of screen two.  That also helped with
some other issues.  Firefox started going to screen 2 the other day.  I
set up window rules for it and included both size and screen location. 
It seems the Force option is the only reliable way to make it work tho. 

I notice another KDE release is on the way.  It's unstable when it hits
the tree but I run unstable for KDE and friends.  It may have some fixes
as well.  Introduce a new feature, get half a dozen bugs to fix.  Fix
those and then repeat.  LOL  Isn't that the way software works??? 

Should have a nice update to do this weekend. 

Dale

:-)  :-) 

P. S.  Checksum tool says this now.  (dir 190 of 631)  It's chewing on
it.  Just like eating a elephant.  :-D

Re: [gentoo-user] Dolphin confusing different run instances.

[Peter Humphrey]

On Friday 13 September 2024 11:03:08 BST Dale wrote:

> I notice another KDE release is on the way.  It's unstable when it hits
> the tree but I run unstable for KDE and friends.  It may have some fixes
> as well.  Introduce a new feature, get half a dozen bugs to fix.  Fix
> those and then repeat.  LOL  Isn't that the way software works??? 
> 
> Should have a nice update to do this weekend. 

Good news - I've just installed it, and it does seem to have fixed my problem 
with misplaced windows. Just a quick look so far, but it seems good. I only 
have the one connected monitor, though.

-- 
Regards,
Peter.