https://bugs.kde.org/show_bug.cgi?id=363851
Harald Sitter changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #34 from Vishal Rao ---
Appears to be working for me too now. Thank you!
Note on some reboots it still shows "stop job running" but completes at about 7
seconds duration when I set the /etc/systemd/system.conf interval settings to
30 second
https://bugs.kde.org/show_bug.cgi?id=363851
Sebastian Kügler changed:
What|Removed |Added
CC||se...@kde.org
--- Comment #33 from Sebastian
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #32 from Harald Sitter ---
sudo apt update && sudo apt install neon-settings
then reboot at least twice
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363851
Harald Sitter changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363851
Bug 363851 depends on bug 364340, which changed state.
Bug 364340 Summary: upon session logout keyboard module crashes
https://bugs.kde.org/show_bug.cgi?id=364340
What|Removed |Added
---
https://bugs.kde.org/show_bug.cgi?id=363851
Vishal Rao changed:
What|Removed |Added
CC||vishal...@gmail.com
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=363851
Pranav Sharma changed:
What|Removed |Added
CC||pranav.sharma@gmail.com
--- Comment #30 fro
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #29 from Harald Sitter ---
nevermind, still broken. won't be solved until plasma learns to clean up and
our software learns to not crash in destructors.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #28 from Harald Sitter ---
I think this should be solved in dev editions within the hour and for user
edition some time this week.
http://packaging.neon.kde.org/cgit/neon/settings.git/commit/?id=3a723d1daf55ce4b69b5af56c0a2ef35a31430b6
--
https://bugs.kde.org/show_bug.cgi?id=363851
J Janz changed:
What|Removed |Added
CC||k...@juniorjanz.net
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #27 from romulu...@gmail.com ---
I also set KillYUserProcesses=yes and removed comments to see if it really
avoid the waiting, but it did not worked in my case. I'm using Neon in case.
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=363851
romulu...@gmail.com changed:
What|Removed |Added
CC||romulu...@gmail.com
--- Comment #26 from r
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
anewuser changed:
What|Removed |Added
CC||caip...@fastmail.fm
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=363851
Julien HENRY changed:
What|Removed |Added
CC||henr...@yahoo.fr
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=363851
Andreas Hartmetz changed:
What|Removed |Added
CC||ahartm...@gmail.com
--- Comment #24 from And
https://bugs.kde.org/show_bug.cgi?id=363851
Harald Sitter changed:
What|Removed |Added
Depends on||364340
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #23 from Harald Sitter ---
https://bugs.kde.org/show_bug.cgi?id=364340
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #22 from Harald Sitter ---
I spoke too soon. Apparently kded just likes to crash every time I want to
reboot. Seeing as it then is suspended it wouldn't' react until forcefully
murdered.
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #21 from Harald Sitter ---
Has anyone tested this actually?
I just tried and it looks to me that setting killuserprocess is not going to be
enough on its own. In particular I seem to recall someone from the Plasma team
mentioning that reboo
https://bugs.kde.org/show_bug.cgi?id=363851
Martin Steigerwald changed:
What|Removed |Added
CC|mar...@lichtvoll.de |
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #20 from Martin Steigerwald ---
I think one major issue here is that systemd then doesn´t seem to handle
shutdown different to log out, i.e. I and quite some other users I read from
prefer processes to be kept running on logout, but when I s
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
Harald Sitter changed:
What|Removed |Added
Assignee|n...@kde.org|neon-b...@kde.org
--- Comment #13 from Harald S
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=363851
Roman changed:
What|Removed |Added
CC||subd...@gmail.com
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #9 from Thomas Pfeiffer ---
(In reply to Martin Steigerwald from comment #8)
> Entirely your choice and in the end I don´t care, cause I do not intend to
> use Neon. Yet, you mask bugs this way.
Sure, I'm all for fixing the misbehaving appl
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #8 from Martin Steigerwald ---
Entirely your choice and in the end I don´t care, cause I do not intend to use
Neon. Yet, you mask bugs this way.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #7 from Thomas Pfeiffer ---
Also, in all honesty: Users who need processes to continue running even after
logout are _not_ a significant enough portion of neon's target audience to
change the _default_ config to better suit their needs.
The
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #6 from Harald Sitter ---
In a systemd world I think you are meant to start it as a scope
> systemd-run --scope --user screen
and let systemd manage the thing properly.
Not being able to differentiate between what is actually meant to run "f
https://bugs.kde.org/show_bug.cgi?id=363851
Martin Steigerwald changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
CC|
https://bugs.kde.org/show_bug.cgi?id=363851
m_loui...@yahoo.com changed:
What|Removed |Added
CC||m_loui...@yahoo.com
--- Comment #4 from m_
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #3 from Harald Sitter ---
Oh yeah. FYI, this also happend with lightdm last I checked. So it might as
well be that ksmserver should make sure the session is dead. As I was saying,
the documentation, that I didn't manage to find, probably wou
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #2 from Harald Sitter ---
After weeks of pondering I am actually thinking ksmserver needs to run shutdown
through sddm. and sddm needs to TERM all of its sessions, so when systemd hits
a running session it will actually make sense for system
https://bugs.kde.org/show_bug.cgi?id=363851
--- Comment #1 from Jonathan Riddell ---
This is common to distros like Fedora too. There's a process which is spawned,
possibly gpg, and nothing is reponsible to shut it down so the shutdown hangs
until a timeout in systemd means it gets killed
--
Y
40 matches
Mail list logo
