https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/syst
|
https://bugs.kde.org/show_bug.cgi?id=417219
Bug Janitor Service changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #38 from Bug
https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
CC||aspotas...@gmail.com
--- Comment #37 from Nate
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #36 from Rex Dieter ---
I'll re-iterate the background I outlined in comment #24 and comment #25,
See dolphin's org.kde.dolphin.FileManager1.service file installed for dbus
activation, contains:
Name=org.freedesktop.FileManager1
It is
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #35 from Attila ---
(In reply to Nate Graham from comment #34)
> I don't know of that's necessarily the best solution. I don't want a
> daemonized Dolphin instance always running in the background, consuming some
> resources, when dbus
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #34 from Nate Graham ---
I don't know of that's necessarily the best solution. I don't want a daemonized
Dolphin instance always running in the background, consuming some resources,
when dbus activtion works just fine for me.
We could make
https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
CC||pubc...@free.fr
--- Comment #33 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #32 from Elvis Angelaccio ---
@Rex: this should probably be discussed on plasma-devel. From the dolphin side
I don't think we would have problems with plasma autostarting `dolphin
--daemon`.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #31 from Rex Dieter ---
The full saga is in the linked bug,
Bug 1394927 - Dolphin takes over the desktop folder in GNOME in F25
https://bugzilla.redhat.com/show_bug.cgi?id=1394927
Cliff's notes:
As the title suggests, by default dolphin
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #30 from Nate Graham ---
(In reply to Rex Dieter from comment #28)
> I'll echo here what I also said in the other bug.
>
> I'd argue this is still a bug worth solving on the kde side. dolphin
> --daemon processes should *not* be restored
https://bugs.kde.org/show_bug.cgi?id=417219
Rex Dieter changed:
What|Removed |Added
Resolution|DUPLICATE |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #28 from Rex Dieter ---
I'll echo here what I also said in the other bug.
I'd argue this is still a bug worth solving on the kde side. dolphin --daemon
processes should *not* be restored via session management.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #27 from Attila ---
(In reply to Rex Dieter from comment #24)
> Fedora does autostart 'dolphin --daemon' for plasma sessions, I can confirm
> this. I implemented it on purpose.
>
> It's a workaround to not rely on dbus activation, since
https://bugs.kde.org/show_bug.cgi?id=417219
Fabsk changed:
What|Removed |Added
CC|fa...@free.fr |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #25 from Rex Dieter ---
Related bug references,
https://bugzilla.redhat.com/show_bug.cgi?id=1394927
https://bugzilla.redhat.com/show_bug.cgi?id=1808716
https://bugs.kde.org/show_bug.cgi?id=418322
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #24 from Rex Dieter ---
Fedora does autostart 'dolphin --daemon' for plasma sessions, I can confirm
this. I implemented it on purpose.
It's a workaround to not rely on dbus activation, since there can be multiple
providers. I believe
https://bugs.kde.org/show_bug.cgi?id=417219
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #23 from Attila ---
I think I have got it, but first let me just mention something.
In your case Dolphin was autostarted because of
"~/.config/autostart/dolphin.desktop". You had that file for an unknown reason
and the behaviour was
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #22 from Fabsk ---
I'm afraid I don't know more that you about the cause of the issue. There must
be a configuration specific to Fedora that launches "dolphin --deamon". I'm too
lazy to investigate any further. Again, does it cause any
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #21 from Attila ---
One more additional information. I have changed the setting from "restore last
session" to "start with an empty session".
The output of the command "ps -efj |grep dolphin" is the same. Process ID "1"
and "--daemon".
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #20 from Attila ---
Here you go. The output of the command "ps -efj |grep dolphin"
myusername 1446 1 1445 1445 1 10:49 ? 00:00:00 /usr/bin/dolphin
--daemon
The process ID is "1" and it is launched with "--daemon".
Is this
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #19 from Fabsk ---
@attila, could you run in a command line (Konsole for example) the following
command after your login (as described in your summary):
ps -efj |grep dolphin
to see with which arguments the mysterious instance was
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #18 from Attila ---
(In reply to Fabsk from comment #17)
> Regarding my previous comment, tt turns out that for an unknown reason I had
> a file "~/.config/autostart/dolphin.desktop" which started "dolphin
> --deamon". After removing it,
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #17 from Fabsk ---
Regarding my previous comment, tt turns out that for an unknown reason I had a
file "~/.config/autostart/dolphin.desktop" which started "dolphin --deamon".
After removing it, the additional Dolphin window/process does not
https://bugs.kde.org/show_bug.cgi?id=417219
Fabsk changed:
What|Removed |Added
CC||fa...@free.fr
--- Comment #16 from Fabsk ---
I think
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #15 from Attila ---
This could help perhaps to investigate the issue.
It is always reproducible. Please see the attached scrennshots.
1. Before I logout, I make sure that the process "dolphin" is not running.
2. Logout.
3. Login again.
4.
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #14 from Attila ---
Created attachment 130041
--> https://bugs.kde.org/attachment.cgi?id=130041=edit
After login dolphin launched
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #13 from Attila ---
Created attachment 130040
--> https://bugs.kde.org/attachment.cgi?id=130040=edit
After login
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #12 from Attila ---
Created attachment 130039
--> https://bugs.kde.org/attachment.cgi?id=130039=edit
Before logout
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417219
Julian Schraner changed:
What|Removed |Added
CC||m...@xyquadrat.ch
https://bugs.kde.org/show_bug.cgi?id=417219
Attila changed:
What|Removed |Added
Version|19.12.1 |19.12.2
--- Comment #10 from Attila ---
Hi,
I have
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #9 from Attila ---
It sounds like this bug is on Fedora and perhaps on some other distros, but not
on openSuse. That's why I have specified "Fedora RPMs" as platform.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #8 from Nate Graham ---
I would say, "yes, this is definitely not intentional behavior from a user
perspective; re-opening" but I cannot reproduce the issue on my machine
(openSUSE Tumbleweed). I use session restore and Dolphin doesn't come
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #7 from Attila ---
(In reply to Elvis Angelaccio from comment #6)
> (In reply to Nate Graham from comment #1)
> > Yes, the background daemon is to support the "open new folders in tabs
> > rather than new windows" feature. If you don't want
https://bugs.kde.org/show_bug.cgi?id=417219
Elvis Angelaccio changed:
What|Removed |Added
CC||elvis.angelac...@kde.org
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #5 from Attila ---
(In reply to Nate Graham from comment #4)
> FWIW I cannot reproduce the issue.
Hi,
what do you mean by you cannot reproduce the issue?
How did you test it?
Did you try NEON? Like I said everything is OK on NEON. No bug.
https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
Keywords||triaged
--- Comment #4 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #3 from Attila ---
Just tested on neon-user-20200207-1737.iso.
I can't see any "dolphin-process" after quitting Dolphin. This means to me,
Dolphin never runs deamonized in both cases when "open new folders in tabs" is
set or not.
--
You
https://bugs.kde.org/show_bug.cgi?id=417219
--- Comment #2 from Attila ---
In my case "open new folders in tabs" is not set. However it seems that Dolphin
is running daemonized.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417219
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Summary|Dolphin is
41 matches
Mail list logo
