[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-07-19 Thread Me via KDE Bugzilla
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 /etc/systemd/logind.conf #KillYUserProcesses=no

IF I opt to perform a Logout, then once at the SDDM Login Greeter screen (which
happens as quickly as one expects it should); then clicking on either the
Reboot or Shutdown icon, the selected process proceeds as quickly as one
expects it should; the annoying 1 minute 30 second delay does not happen.

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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
attachment-25466-0.html

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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?

Paul Loughman
sno...@icloud.com




> On Jun 11, 2016, at 12:10 PM, Harald Sitter via KDE Bugzilla 
>  wrote:
> 
> 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 Sitter  ---
> If you were logged in on a terminal, or you were logged in over ssh, or you
> switched user, or you logged out and back in again, you would end up with a
> second session. There's possibly other cases, but generally those are the main
> things.
> 
> Pretty much anything that resembles a login of any type will create a session.
> 
> And pretty much any process created as part of login but not killed by some
> entity other than systemd would then block shutdown.
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.
> ___
> neon mailing list
> n...@kde.org
> https://mail.kde.org/mailman/listinfo/neon

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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
attachment-21709-0.html

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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 exit konsole, that process should be killed, so if I then do a shutdown;
K Menu > Shut Down (I’m using Application Dashboard), which of these processes
is Session 2 for Paul?

Paul Loughman
sno...@icloud.com




> On Jun 11, 2016, at 12:10 PM, Harald Sitter via KDE Bugzilla 
>  wrote:
> 
> 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 Sitter  ---
> If you were logged in on a terminal, or you were logged in over ssh, or you
> switched user, or you logged out and back in again, you would end up with a
> second session. There's possibly other cases, but generally those are the main
> things.
> 
> Pretty much anything that resembles a login of any type will create a session.
> 
> And pretty much any process created as part of login but not killed by some
> entity other than systemd would then block shutdown.
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.
> ___
> neon mailing list
> n...@kde.org
> https://mail.kde.org/mailman/listinfo/neon

-- 
You are receiving this mail because:
You are watching all bug changes.

[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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&action=edit
A stop job is running_1.png

-- 
You are receiving this mail because:
You are watching all bug changes.


[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown

2016-06-11 Thread Me via KDE Bugzilla
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’ve screen-captured
this:



Where is this second session of ‘me’ coming from? It’s this second session that
is hung (I believe it’s actually dead — a zombie?) and causes systemd to delay
the shutdown; it waits for the second session to terminate “on it’s own”, and
when, after the default time of 1min 30s, it hasn’t, systemd then kills it and
the shutdown finishes as it should.

Paul Loughman
sno...@icloud.com




> On Jun 10, 2016, at 1:49 PM, Thomas Pfeiffer via KDE Bugzilla 
>  wrote:
> 
> 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 applications, but "Let's expose other
> people's fuck-ups so they'll fix them" has not been a very successful approach
> for us in the past. 
> Usually what happens is that those who fucked up don't do anything about it,
> and our users blame _us_ for the problems.
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.
> ___
> neon mailing list
> n...@kde.org
> https://mail.kde.org/mailman/listinfo/neon

-- 
You are receiving this mail because:
You are watching all bug changes.

[muon] [Bug 358659] Muon package manager does not close

2016-02-28 Thread Me via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358659

Me  changed:

   What|Removed |Added

 CC||sno...@icloud.com

--- Comment #1 from Me  ---
I can confirm this.

KDE neon:
Muon Package Manager (Version 5.5.0; KDE Frameworks 5.20.0; Qt 5.5.1 (built
against 5.5.1); The xcb windowing system)
KDE Plasma Version: 5.4.4
Qt Version: 5.5.1
Kernel Version: 4.2.0-30-generic
Workplace Theme: Breeze
Cursor Theme: Breeze
Color Scheme: Breeze

and,

Kubuntu 16.04:
Muon Package Manager (Version 5.4.3; KDE Frameworks 5.15.0; Qt 5.5.1 (built
agains 5.4.2); The xcb windowing system)
KDE Plasma Version: 5.4.3
Qt Version: 5.5.1
Kernel Version: 4.4.0-7-generic
Workplace Theme: Breeze
Cursor Theme: Breeze
Color Scheme: Breeze

It isn't possible to close the application by clicking on the circled X icon in
the upper-right corner of the application window. Nothing happens. File > Quit
works as expected.

This anomalous behavior of Muon Package Manager is not present in Kubuntu 15.10
and earlier.

-- 
You are receiving this mail because:
You are watching all bug changes.


[amarok] [Bug 355986] freezes when opened

2015-12-04 Thread me via KDE Bugzilla
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 not run
that pid thing becuase there seems to be good output from just that.  let me
know if you still want me to run that...

-- 
You are receiving this mail because:
You are watching all bug changes.


[amarok] [Bug 355986] freezes when opened

2015-12-04 Thread me via KDE Bugzilla
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 it
get up to Track 2000 something.  

when i remove the cd from the drive it works fine.  

here is the output to file, like you said i just took a bunch of lines from the
bottom, not all...

amarok:   [00;36mEND__:[00;39m static QScriptValue
ScriptableServiceScript::ScriptableServiceScript_prototype_ctor(QScriptContext*,
QScriptEngine*) [00;36m[Took: 0.003s][00;39m 
amarok:   [00;34mBEGIN:[00;39m void
ScriptableServiceScript::slotCustomize(const QString&) 
amarok:   [00;34mEND__:[00;39m void
ScriptableServiceScript::slotCustomize(const QString&) [00;34m[Took:
0s][00;39m 
amarok: [00;32mEND__:[00;39m bool ScriptManager::slotRunScript(const
QString&, bool) [00;32m[Took: 0.004s][00;39m 
amarok:   [00;34mEND__:[00;39m void ScriptManager::configChanged(bool)
[00;34m[Took: 0.11s][00;39m 
amarok: [00;32mEND__:[00;39m void ScriptManager::updateAllScripts()
[00;32m[Took: 0.11s][00;39m 
amarok: [00;35mBEGIN:[00;39m void
Playlist::PrettyListView::slotPlaylistActiveTrackChanged() 
amarok:   [00;36mBEGIN:[00;39m void
Playlist::PrettyListView::scrollToActiveTrack() 
amarok:   [00;36mEND__:[00;39m void
Playlist::PrettyListView::scrollToActiveTrack() [00;36m[Took: 0s][00;39m 
amarok: [00;35mEND__:[00;39m void
Playlist::PrettyListView::slotPlaylistActiveTrackChanged() [00;35m[Took:
0s][00;39m 
amarok: [00;31mBEGIN:[00;39m void Analyzer::Base::connectSignals() 
amarok: [00;31mEND__:[00;39m void Analyzer::Base::connectSignals()
[00;31m[Took: 0s][00;39m 
amarok: [00;32mBEGIN:[00;39m void
Playlist::PrettyListView::bottomModelRowsInsertedScroll() 
amarok: [00;32mEND__:[00;39m void
Playlist::PrettyListView::bottomModelRowsInsertedScroll() [00;32m[Took:
0s][00;39m 
amarok: [00;34mBEGIN:[00;39m void
Collections::ScriptableServiceQueryMaker::fetchAlbums() 
amarok:   [ScriptableServiceQueryMaker] parent id:  -1 
amarok:   [00;35mBEGIN:[00;39m void
ScriptableServiceScript::slotPopulate(QString, int, int, QString, QString) 
amarok: SCRIPT "Free Music Charts" :  "populating fmc level: 1" 
amarok: SCRIPT "Free Music Charts" :  "fetching fmc xml..." 
amarok: [00;36mBEGIN:[00;39m static QScriptValue
Downloader::init(QScriptContext*, QScriptEngine*, bool) 
amarok: [00;36mEND__:[00;39m static QScriptValue
Downloader::init(QScriptContext*, QScriptEngine*, bool) [00;36m[Took:
0s][00;39m 
amarok: SCRIPT "Free Music Charts" :  "done fetching fmc xml..." 
amarok:   [00;35mEND__:[00;39m void
ScriptableServiceScript::slotPopulate(QString, int, int, QString, QString)
[00;35m[Took: 0s][00;39m 
amarok: [00;34mEND__:[00;39m void
Collections::ScriptableServiceQueryMaker::fetchAlbums() [00;34m[Took:
0.001s][00;39m 
amarok: [00;31mBEGIN:[00;39m void
Collections::ScriptableServiceQueryMaker::fetchArtists() 
amarok:   [00;32mBEGIN:[00;39m void
ScriptableServiceScript::slotPopulate(QString, int, int, QString, QString) 
amarok: [00;34mBEGIN:[00;39m int
ScriptableServiceScript::donePopulating() const 
amarok:   [00;35mBEGIN:[00;39m void
ScriptableServiceManager::donePopulating(const QString&, int) 
amarok: Service name:  "Librivox.org" , parent id:  -1 
amarok: [00;36mBEGIN:[00;39m void
Collections::ScriptableServiceCollection::donePopulating(int) 
amarok:   [00;31mBEGIN:[00;39m void
Collections::ScriptableServiceQueryMaker::slotScriptComplete() 
amarok: [ScriptableServiceQueryMaker] there are  1  artists 
amarok:   [00;31mEND__:[00;39m void
Collections::ScriptableServiceQueryMaker::slotScriptComplete() [00;31m[Took:
0s][00;39m 
amarok: [00;36mEND__:[00;39m void
Collections::ScriptableServiceCollection::donePopulating(int) [00;36m[Took:
0s][00;39m 
amarok:   [00;35mEND__:[00;39m void
ScriptableServiceManager::donePopulating(const QString&, int) [00;35m[Took:
0s][00;39m 
amarok: [00;34mEND__:[00;39m int
ScriptableServiceScript::donePopulating() const [00;34m[Took: 0s][00;39m 
amarok:   [00;32mEND__:[00;39m void
ScriptableServiceScript::slotPopulate(QString, int, int, QString, QString)
[00;32m[Took: 0s][00;39m 
amarok: [00;31mEND__:[00;39m void
Collections::ScriptableServiceQueryMaker::fetchArtists() [00;31m[Took:
0s][00;39m 
amarok: [00;32mBEGIN:[00;39m void
WikipediaEnginePrivate::_dataContainerUpdated(const QString&, const Data&) 
amarok:   [WikipediaEngine] "updated preferred wikipedia languages:" ("en") 
amarok: [00;32mEND__:[00;39m void
WikipediaEnginePrivate::_dataContainerUpdated(const QString&, const Data&)
[00;32m[Took: 0s][00;39m 
amarok: [00;34mBEGIN:[00;39m void WikipediaApplet::dataUpdated(const
QString&, const Data&) 
amarok: [00;34mEND__:[00;39m void WikipediaApplet::dataUpdated(const
QString&, const Data&) [00;34m[Took: 0s][00;39m 
amarok: QModelIn