https://bugs.kde.org/show_bug.cgi?id=363851
Me changed:
What|Removed |Added
CC||sno...@icloud.com
--- Comment #25 from Me ---
I've left /
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #19 from Me ---
Created attachment 99460
--> https://bugs.kde.org/attachment.cgi?id=99460&action=edit
Processes.png
--- Comment #18 from Me ---
Created attachment 99459
--> https://bugs.kde.org/attachment.cgi?id=99459&action=edit
attac
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #17 from Me ---
These are the processes running after a starting KDE neon (Oracle VirtualBox
VM), logging in (SDDM), and opening a konsole on the Desktop:
So which one of these is the offending session? Or is it even identified here?
Pau
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #16 from Me ---
Created attachment 99456
--> https://bugs.kde.org/attachment.cgi?id=99456&action=edit
Processes.png
--- Comment #15 from Me ---
Created attachment 99455
--> https://bugs.kde.org/attachment.cgi?id=99455&action=edit
attac
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #14 from Me ---
These are the processes running after a starting KDE neon (Oracle VirtualBox
VM), logging in (SDDM), and opening a konsole on the Desktop:
/etc/systemd/logind.conf #KillYUserProcesses= is currently set to ‘no’.
When I exi
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #12 from Me ---
Created attachment 99454
--> https://bugs.kde.org/attachment.cgi?id=99454&action=edit
A stop job is running_2.png
--- Comment #11 from Me ---
Created attachment 99453
--> https://bugs.kde.org/attachment.cgi?id=99453&act
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #10 from Me ---
I’m running KDE neon in an Oracle VirtualBox VM. I keep it fully apt-get
dist-upgraded.
If I leave #KillUserProcesses=no, then the shutdown process ‘hangs’ once the
KDE neon 5.6.90 logo screen appears for a full 1min 30s. I’
https://bugs.kde.org/show_bug.cgi?id=358659
Me changed:
What|Removed |Added
CC||sno...@icloud.com
--- Comment #1 from Me ---
I can confir
https://bugs.kde.org/show_bug.cgi?id=355986
--- Comment #4 from me ---
one more things on this, after i open amarok with a cd, in order to get it to
stop i need to kill it. but then after i do that, if i open amarok after it is
unresponsive even if the cd was removed after it was killed. i did
https://bugs.kde.org/show_bug.cgi?id=355986
--- Comment #3 from me ---
okay, i kind of figured out what was going on here. apparently i had a cd in
my drive and so, from the output, amarok was finding the cd tracks but it
seemed to be stuck doing that over and again. it would not stop. i saw
10 matches
Mail list logo