Re: [gentoo-user] Dolphin only allowing a single instance after update

[Dale]

P Levine wrote:
> On Thu, Aug 22, 2019 at 9:16 PM Dale  > wrote:
>
> Dave Fellows wrote:
> >> P Levine wrote:
> >>> On Fri, Aug 16, 2019 at 10:56 PM Dale  
> >>> >>
> wrote:
> >>>
> >>>     Howdy,
> >>>
> >>>     I upgraded my system last night.  I logged out and back in
> earlier and
> >>>     have noticed something new.  It seems to only allow one
> instance of
> >>>     Dolphin to run at a time.  I usually have three or four
> running for
> >>>     doing different things in different locations.  It just
> makes it
> >>>     easier
> >>>     for me to multi-task at times.  What I've noticed with the
> new version
> >>>     is that if I have a instance open on say desktop 7 and
> then want
> >>>     to open
> >>>     a new instance on desktop 4, it moves the already running
> dolphin from
> >>>     desktop 7 to 4.  It doesn't open a new instance.  I then lose
> >>>     where I am
> >>>     when I get ready to go back to work on something in the
> previous
> >>>     instance. 
> >>>
> >>>     Current version of Dolphin and USE flags:
> >>>
> >>>     kde-apps/dolphin-19.08.0:5::gentoo  USE="handbook
> -activities -debug
> >>>     -semantic-desktop -test"
> >>>
> >>>     Previous version that worked normally:
> >>>
> >>>     kde-apps/dolphin-19.04.3
> >>>
> >>>     Has anyone else noticed this?  I've looked in the
> Configure section to
> >>>     see if I can change the behavior but can't find anything
> related.  I
> >>>     checked to see if I could add a option on the command line
> as well.  I
> >>>     even poked around System Settings but can't find anything
> there
> >>>     either. 
> >>>     Is this a new thing, a bug or what? 
> >>>
> >>>     Thanks for the help.
> >>>
> >>>     Dale
> >>>
> >>>     :-)  :-) 
> >>>
> >>>
> >>> The behaviour was changed such that dolphin opens new instances in
> >>> tabs by default.  If you want to change that, edit the desktop
> file
> >>> and add the *--new-window* option to the command.
> >>>
> >>
> >> Added that and it still opens in another instance and adds a
> tab.  After
> >> my edit, it looks like this:
> >>
> >> Exec=dolphin %u --new-window
> >>
> >> The file I edited is located here including the file name:
> >>
> >> /usr/share/applications/org.kde.dolphin.desktop
> >>
> >> Did I add it to the wrong place or does it require more than that? 
> >> There are several .desktop files as listed here:
> >>
> >>
> >> root@fireball / # equery f kde-apps/dolphin | grep desktop
> >> /usr/share/applications/org.kde.dolphin.desktop
> >> /usr/share/dbus-1/interfaces/org.freedesktop.FileManager1.xml
> >> /usr/share/kglobalaccel/org.kde.dolphin.desktop
> >> /usr/share/kservices5/dolphinpart.desktop
> >> /usr/share/kservices5/kcmdolphingeneral.desktop
> >> /usr/share/kservices5/kcmdolphinnavigation.desktop
> >> /usr/share/kservices5/kcmdolphinservices.desktop
> >> /usr/share/kservices5/kcmdolphinviewmodes.desktop
> >> /usr/share/kservicetypes5/fileviewversioncontrolplugin.desktop
> >> root@fireball / #
> >>
> >>
> >>
> >> Thanks.
> >>
> >> Dale
> >>
> >> :-)  :-) 
> >>
> > Try
> > Exec=dolphin --new-window  %u
> >
> > DaveF
> >
>
>
> Same results.  It opens a new tab in a already running instance.  For
> something that can be disabled, it would seem they would document
> how to
> do so or at least link to it.  I've read the online documentation for
> Dolphin and can't find any mention of this or how to disable it. 
> Either
> it isn't there or I missed it somehow, well hidden maybe.  ;-) 
>
> Open for ideas tho. 
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>
>
> Maybe related to
> this: 
> https://www.reddit.com/r/kde/comments/bze2wm/dolphin_opening_tabs_instead_of_windows_from_task/


It sounds like it.  It seems it is hardcoded to do this at the moment. 
This seriously makes me want to start using another file manager.  I
don't mind someone testing new features but at the very least, have it
where it can be disabled for those who do not want it or are set up not
to need it.  This makes me have to do more to get to where I want. 
Instead of clicking my Video folder for example, I have to do a Meta + e
and then navigate to that folder.  Before this, I simply clicked the
Video folder on my desktop and I was there.  It's the same for other
folders as well.  This reminds me of the switch from KDE3 to KDE4 and
the mess that created.  I'm beginning to wonder about KDE.  

For those who prefer this behavior, I'm sure it 

Re: [gentoo-user] Dolphin only allowing a single instance after update

[P Levine]

On Thu, Aug 22, 2019 at 9:16 PM Dale  wrote:

> Dave Fellows wrote:
> >> P Levine wrote:
> >>> On Fri, Aug 16, 2019 at 10:56 PM Dale  >>> > wrote:
> >>>
> >>> Howdy,
> >>>
> >>> I upgraded my system last night.  I logged out and back in earlier
> and
> >>> have noticed something new.  It seems to only allow one instance of
> >>> Dolphin to run at a time.  I usually have three or four running for
> >>> doing different things in different locations.  It just makes it
> >>> easier
> >>> for me to multi-task at times.  What I've noticed with the new
> version
> >>> is that if I have a instance open on say desktop 7 and then want
> >>> to open
> >>> a new instance on desktop 4, it moves the already running dolphin
> from
> >>> desktop 7 to 4.  It doesn't open a new instance.  I then lose
> >>> where I am
> >>> when I get ready to go back to work on something in the previous
> >>> instance.
> >>>
> >>> Current version of Dolphin and USE flags:
> >>>
> >>> kde-apps/dolphin-19.08.0:5::gentoo  USE="handbook -activities
> -debug
> >>> -semantic-desktop -test"
> >>>
> >>> Previous version that worked normally:
> >>>
> >>> kde-apps/dolphin-19.04.3
> >>>
> >>> Has anyone else noticed this?  I've looked in the Configure
> section to
> >>> see if I can change the behavior but can't find anything related.
> I
> >>> checked to see if I could add a option on the command line as
> well.  I
> >>> even poked around System Settings but can't find anything there
> >>> either.
> >>> Is this a new thing, a bug or what?
> >>>
> >>> Thanks for the help.
> >>>
> >>> Dale
> >>>
> >>> :-)  :-)
> >>>
> >>>
> >>> The behaviour was changed such that dolphin opens new instances in
> >>> tabs by default.  If you want to change that, edit the desktop file
> >>> and add the *--new-window* option to the command.
> >>>
> >>
> >> Added that and it still opens in another instance and adds a tab.  After
> >> my edit, it looks like this:
> >>
> >> Exec=dolphin %u --new-window
> >>
> >> The file I edited is located here including the file name:
> >>
> >> /usr/share/applications/org.kde.dolphin.desktop
> >>
> >> Did I add it to the wrong place or does it require more than that?
> >> There are several .desktop files as listed here:
> >>
> >>
> >> root@fireball / # equery f kde-apps/dolphin | grep desktop
> >> /usr/share/applications/org.kde.dolphin.desktop
> >> /usr/share/dbus-1/interfaces/org.freedesktop.FileManager1.xml
> >> /usr/share/kglobalaccel/org.kde.dolphin.desktop
> >> /usr/share/kservices5/dolphinpart.desktop
> >> /usr/share/kservices5/kcmdolphingeneral.desktop
> >> /usr/share/kservices5/kcmdolphinnavigation.desktop
> >> /usr/share/kservices5/kcmdolphinservices.desktop
> >> /usr/share/kservices5/kcmdolphinviewmodes.desktop
> >> /usr/share/kservicetypes5/fileviewversioncontrolplugin.desktop
> >> root@fireball / #
> >>
> >>
> >>
> >> Thanks.
> >>
> >> Dale
> >>
> >> :-)  :-)
> >>
> > Try
> > Exec=dolphin --new-window  %u
> >
> > DaveF
> >
>
>
> Same results.  It opens a new tab in a already running instance.  For
> something that can be disabled, it would seem they would document how to
> do so or at least link to it.  I've read the online documentation for
> Dolphin and can't find any mention of this or how to disable it.  Either
> it isn't there or I missed it somehow, well hidden maybe.  ;-)
>
> Open for ideas tho.
>
> Thanks.
>
> Dale
>
> :-)  :-)
>

Maybe related to this:
https://www.reddit.com/r/kde/comments/bze2wm/dolphin_opening_tabs_instead_of_windows_from_task/

Re: [EXTERNAL] [gentoo-user] empty cdrom drive is busy or mounted

[Andrew Udvare]

> On 2019-08-22, at 12:31, Laurence Perkins  wrote:
> 
> A common tactic is to use grep twice:
> ps auxf | grep -v grep | grep blah

Or grep with brackets:

ps aux | grep '[f]irefox'

I have a function for this:

psgrep() {
  ps aux | grep "[${1:0:1}]${1:1}";
}

This works because the ps output will have "grep [f]irefox" and the regex can't 
match that line (without escaping the [] again).


-- 
Andrew

Re: [gentoo-user] setup x11/plasma in chroot?

[Andrew Udvare]

> On 2019-08-22, at 20:13,  
>  wrote:
> 
> Can I install x11 and plasma on a new system I've chrooted into or do I have 
> to boot into the new system?  thanks. 
> -- “The whole world is watching! The whole world is watching!”
> 
You can install these things fine. Running them within the chroot can be a bit 
painful, however.

Re: [gentoo-user] Dolphin only allowing a single instance after update

[Dale]

Dave Fellows wrote:
>> P Levine wrote:
>>> On Fri, Aug 16, 2019 at 10:56 PM Dale >> > wrote:
>>>
>>> Howdy,
>>>
>>> I upgraded my system last night.  I logged out and back in earlier and
>>> have noticed something new.  It seems to only allow one instance of
>>> Dolphin to run at a time.  I usually have three or four running for
>>> doing different things in different locations.  It just makes it
>>> easier
>>> for me to multi-task at times.  What I've noticed with the new version
>>> is that if I have a instance open on say desktop 7 and then want
>>> to open
>>> a new instance on desktop 4, it moves the already running dolphin from
>>> desktop 7 to 4.  It doesn't open a new instance.  I then lose
>>> where I am
>>> when I get ready to go back to work on something in the previous
>>> instance. 
>>>
>>> Current version of Dolphin and USE flags:
>>>
>>> kde-apps/dolphin-19.08.0:5::gentoo  USE="handbook -activities -debug
>>> -semantic-desktop -test"
>>>
>>> Previous version that worked normally:
>>>
>>> kde-apps/dolphin-19.04.3
>>>
>>> Has anyone else noticed this?  I've looked in the Configure section to
>>> see if I can change the behavior but can't find anything related.  I
>>> checked to see if I could add a option on the command line as well.  I
>>> even poked around System Settings but can't find anything there
>>> either. 
>>> Is this a new thing, a bug or what? 
>>>
>>> Thanks for the help.
>>>
>>> Dale
>>>
>>> :-)  :-) 
>>>
>>>
>>> The behaviour was changed such that dolphin opens new instances in
>>> tabs by default.  If you want to change that, edit the desktop file
>>> and add the *--new-window* option to the command.
>>>
>>
>> Added that and it still opens in another instance and adds a tab.  After
>> my edit, it looks like this:
>>
>> Exec=dolphin %u --new-window
>>
>> The file I edited is located here including the file name:
>>
>> /usr/share/applications/org.kde.dolphin.desktop
>>
>> Did I add it to the wrong place or does it require more than that? 
>> There are several .desktop files as listed here:
>>
>>
>> root@fireball / # equery f kde-apps/dolphin | grep desktop
>> /usr/share/applications/org.kde.dolphin.desktop
>> /usr/share/dbus-1/interfaces/org.freedesktop.FileManager1.xml
>> /usr/share/kglobalaccel/org.kde.dolphin.desktop
>> /usr/share/kservices5/dolphinpart.desktop
>> /usr/share/kservices5/kcmdolphingeneral.desktop
>> /usr/share/kservices5/kcmdolphinnavigation.desktop
>> /usr/share/kservices5/kcmdolphinservices.desktop
>> /usr/share/kservices5/kcmdolphinviewmodes.desktop
>> /usr/share/kservicetypes5/fileviewversioncontrolplugin.desktop
>> root@fireball / #
>>
>>
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-) 
>>
> Try
> Exec=dolphin --new-window  %u
>
> DaveF
>


Same results.  It opens a new tab in a already running instance.  For
something that can be disabled, it would seem they would document how to
do so or at least link to it.  I've read the online documentation for
Dolphin and can't find any mention of this or how to disable it.  Either
it isn't there or I missed it somehow, well hidden maybe.  ;-) 

Open for ideas tho. 

Thanks.

Dale

:-)  :-) 

[gentoo-user] setup x11/plasma in chroot?

[mad.scientist.at.large]

Can I install x11 and plasma on a new system I've chrooted into or do I have to 
boot into the new system?  thanks. 
-- “The whole world is watching! The whole world is watching!”

Re: [gentoo-user] Dolphin only allowing a single instance after update

[Dale]

P Levine wrote:
> On Fri, Aug 16, 2019 at 10:56 PM Dale  > wrote:
>
> Howdy,
>
> I upgraded my system last night.  I logged out and back in earlier and
> have noticed something new.  It seems to only allow one instance of
> Dolphin to run at a time.  I usually have three or four running for
> doing different things in different locations.  It just makes it
> easier
> for me to multi-task at times.  What I've noticed with the new version
> is that if I have a instance open on say desktop 7 and then want
> to open
> a new instance on desktop 4, it moves the already running dolphin from
> desktop 7 to 4.  It doesn't open a new instance.  I then lose
> where I am
> when I get ready to go back to work on something in the previous
> instance. 
>
> Current version of Dolphin and USE flags:
>
> kde-apps/dolphin-19.08.0:5::gentoo  USE="handbook -activities -debug
> -semantic-desktop -test"
>
> Previous version that worked normally:
>
> kde-apps/dolphin-19.04.3
>
> Has anyone else noticed this?  I've looked in the Configure section to
> see if I can change the behavior but can't find anything related.  I
> checked to see if I could add a option on the command line as well.  I
> even poked around System Settings but can't find anything there
> either. 
> Is this a new thing, a bug or what? 
>
> Thanks for the help.
>
> Dale
>
> :-)  :-) 
>
>
> The behaviour was changed such that dolphin opens new instances in
> tabs by default.  If you want to change that, edit the desktop file
> and add the *--new-window* option to the command.
>


Added that and it still opens in another instance and adds a tab.  After
my edit, it looks like this:

Exec=dolphin %u --new-window

The file I edited is located here including the file name:

/usr/share/applications/org.kde.dolphin.desktop

Did I add it to the wrong place or does it require more than that? 
There are several .desktop files as listed here:


root@fireball / # equery f kde-apps/dolphin | grep desktop
/usr/share/applications/org.kde.dolphin.desktop
/usr/share/dbus-1/interfaces/org.freedesktop.FileManager1.xml
/usr/share/kglobalaccel/org.kde.dolphin.desktop
/usr/share/kservices5/dolphinpart.desktop
/usr/share/kservices5/kcmdolphingeneral.desktop
/usr/share/kservices5/kcmdolphinnavigation.desktop
/usr/share/kservices5/kcmdolphinservices.desktop
/usr/share/kservices5/kcmdolphinviewmodes.desktop
/usr/share/kservicetypes5/fileviewversioncontrolplugin.desktop
root@fireball / #



Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] Dolphin only allowing a single instance after update

[P Levine]

On Fri, Aug 16, 2019 at 10:56 PM Dale  wrote:

> Howdy,
>
> I upgraded my system last night.  I logged out and back in earlier and
> have noticed something new.  It seems to only allow one instance of
> Dolphin to run at a time.  I usually have three or four running for
> doing different things in different locations.  It just makes it easier
> for me to multi-task at times.  What I've noticed with the new version
> is that if I have a instance open on say desktop 7 and then want to open
> a new instance on desktop 4, it moves the already running dolphin from
> desktop 7 to 4.  It doesn't open a new instance.  I then lose where I am
> when I get ready to go back to work on something in the previous instance.
>
> Current version of Dolphin and USE flags:
>
> kde-apps/dolphin-19.08.0:5::gentoo  USE="handbook -activities -debug
> -semantic-desktop -test"
>
> Previous version that worked normally:
>
> kde-apps/dolphin-19.04.3
>
> Has anyone else noticed this?  I've looked in the Configure section to
> see if I can change the behavior but can't find anything related.  I
> checked to see if I could add a option on the command line as well.  I
> even poked around System Settings but can't find anything there either.
> Is this a new thing, a bug or what?
>
> Thanks for the help.
>
> Dale
>
> :-)  :-)
>

The behaviour was changed such that dolphin opens new instances in tabs by
default.  If you want to change that, edit the desktop file and add the
*--new-window* option to the command.

Re: [EXTERNAL] Re: [gentoo-user] empty cdrom drive is busy or mounted

[Jack]

On 2019.08.22 12:31, Laurence Perkins wrote:



On Thu, 2019-08-22 at 10:03 +1000, Adam Carter wrote:
> On Thu, Aug 22, 2019 at 5:48 AM james  wrote:
> > On 8/16/19 12:44 PM, Jack wrote:
> > > ps auxf | grep systemd
> >
> > This is new turf for me. Upon issuing this command string I get::
> >
> > # ps auxf | grep systemd
> > root 24947  0.0  0.0  13964   996 pts/6S+   15:43   0:00
> >   |   |   |   \_ grep --colour=auto systemd
> >
>
> This is showing that the only process with systemd in its name is  
the

> grep command itself; you could pass anything to grep and it will be
> found in the process list, eg;
>
> $ ps auxf | grep blah
> adam   52359  0.0  0.0   7708   940 pts/3S+   09:55   0:00
>\_ grep --colour=auto blah
>
> So, there's no systemd process running on this system.

A common tactic is to use grep twice:
ps auxf | grep -v grep | grep blah

That strips out all instances of grep from the results.
Putting what you're searching for first is more efficient, but putting
it last keeps the colorized output intact.

LMP
I often deal with that by using the search function in my terminal  
(usually konsole) to highlight the term I'm actually looking for.

Re: [EXTERNAL] Re: [gentoo-user] empty cdrom drive is busy or mounted

[Laurence Perkins]

On Thu, 2019-08-22 at 10:03 +1000, Adam Carter wrote:
> On Thu, Aug 22, 2019 at 5:48 AM james  wrote:
> > On 8/16/19 12:44 PM, Jack wrote:
> > > ps auxf | grep systemd
> > 
> > This is new turf for me. Upon issuing this command string I get::
> > 
> > # ps auxf | grep systemd
> > root 24947  0.0  0.0  13964   996 pts/6S+   15:43   0:00
> >   |   |   |   \_ grep --colour=auto systemd
> > 
> 
> This is showing that the only process with systemd in its name is the
> grep command itself; you could pass anything to grep and it will be
> found in the process list, eg;
> 
> $ ps auxf | grep blah
> adam   52359  0.0  0.0   7708   940 pts/3S+   09:55   0:00  
>\_ grep --colour=auto blah
> 
> So, there's no systemd process running on this system.

A common tactic is to use grep twice:
ps auxf | grep -v grep | grep blah

That strips out all instances of grep from the results.
Putting what you're searching for first is more efficient, but putting
it last keeps the colorized output intact.

LMP


signature.asc
Description: This is a digitally signed message part