On Sat, May 1, 2021 at 8:49 AM Andrew Lowe wrote:
>
> On 1/5/21 3:04 pm, Neil Bothwick wrote:
> > On Sat, 1 May 2021 01:24:23 +0200, Frank Steinmetzger wrote:
> >
> >> I also have experienced something like it. In my case it was Wireshark
> >> coming up after I only launched it once. It is
On 1/5/21 3:04 pm, Neil Bothwick wrote:
On Sat, 1 May 2021 01:24:23 +0200, Frank Steinmetzger wrote:
I also have experienced something like it. In my case it was Wireshark
coming up after I only launched it once. It is probably KDE’s session
management getting into your way. Unfortunately I
On Sat, 1 May 2021 01:24:23 +0200, Frank Steinmetzger wrote:
> I also have experienced something like it. In my case it was Wireshark
> coming up after I only launched it once. It is probably KDE’s session
> management getting into your way. Unfortunately I haven’t found a place
> where to
Am Sat, May 01, 2021 at 01:24:23AM +0200 schrieb Frank Steinmetzger:
> I also have experienced something like it.
Whoopsie, I’m reading up on the list top to bottom and overlooked that your
question was already answered. But it’s good to know my assumption was right
at least. :)
--
Gruß |
Am Sat, Apr 24, 2021 at 08:19:28PM +0800 schrieb Andrew Lowe:
> Hi all,
> My desktop machine is up to date ~amd64 along with KDE. A few days ago I
> think I had, amongst others, a Dolphin update. Now when I turn on the
> machine and log into KDE, I find that I have, for example the login I
Hi all,
My desktop machine is up to date ~amd64 along with KDE. A few days ago
I think I had, amongst others, a Dolphin update. Now when I turn on the
machine and log into KDE, I find that I have, for example the login I
did to write this email, 15 instances, hence the pod pun, of Dolphin
6 matches
Mail list logo