[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[Wolfgang Bauer]

https://bugs.kde.org/show_bug.cgi?id=382444

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||andr...@stikonas.eu

--- Comment #11 from Wolfgang Bauer  ---
*** Bug 380974 has been marked as a duplicate of this bug. ***

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[Coacher]

https://bugs.kde.org/show_bug.cgi?id=382444

--- Comment #10 from Coacher  ---
(In reply to David Edmundson from comment #9)

Thank you very much. This improves the situation a lot, but there's one thing
still missing. I use cmst with classic (legacy) systray provided by tint2 and
cmst icon appears after a very long delay. Not reproducible with
plasma-workspace-5.9.x.

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=382444

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kno
   ||tifications/1c97e1d9741fd15
   ||962474f47932dd09728dae76b
 Status|CONFIRMED   |RESOLVED

--- Comment #9 from David Edmundson  ---
Git commit 1c97e1d9741fd15962474f47932dd09728dae76b by David Edmundson.
Committed on 29/08/2017 at 08:44.
Pushed by davidedmundson into branch 'master'.

Don't block starting notification service

Summary:
We don't need to manually start the DBus service.
It blocks the calling app, and dbusServiceExists means that we will
always end up going the DBus route over a popup anyway, so it won't
do anything useful.

The service (in the plasma case plasma-wait-for-name) will be started
automatically when we actually send the notification.

Also fix d-dbusServiceExists being cleared to false when the first
service owner exits.

Subscribers: #frameworks

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D6963

M  +11   -17   src/notifybypopup.cpp

https://commits.kde.org/knotifications/1c97e1d9741fd15962474f47932dd09728dae76b

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=382444

David Edmundson  changed:

   What|Removed |Added

 CC||itumaykin+...@gmail.com

--- Comment #8 from David Edmundson  ---
*** Bug 383439 has been marked as a duplicate of this bug. ***

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=382444

--- Comment #7 from David Edmundson  ---
Yeah, patch on phabricator...

https://phabricator.kde.org/D6963

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=382444

--- Comment #6 from Christoph Feck  ---
David, any progress with comment #3?

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[James Lee]

https://bugs.kde.org/show_bug.cgi?id=382444

James Lee  changed:

   What|Removed |Added

 CC||ja...@james.tl

--- Comment #5 from James Lee  ---
Created attachment 107141
  --> https://bugs.kde.org/attachment.cgi?id=107141=edit
Backtrace from kwrite with debug symbols during hang

I am seeing this same issue running KDE apps like kwrite outside of Plasma when
no notification service is running.  This is with kde-frameworks/knotify-5.36.0
and kwrite-17.04.3.  If I start a notification service, like dunst, the hang
goes away.  I've attached a backtrace of my kwrite with debug symbols during
the hang.

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382444

csz...@gmail.com changed:

   What|Removed |Added

 CC||csz...@gmail.com

--- Comment #4 from csz...@gmail.com ---
(In reply to David Edmundson from comment #1)
>  If it is that's a bug in
> the notification lib.

I don't believe this has anything to do with a library.

When the bus is sent StartServiceByName, it will not send a reply until the
started process exits or the desired name is registered (I have not confirmed
if there are also timeouts involved.) This means that plasma_waitforme will
block all programs that call StartServiceByName for
org.freedesktop.Notifications for one minute.

I have read but not confirmed that the bus will start at most one service for
each name. E.g. if there are two service files providing the
org.freedesktop.Notifications name, then the bus will only start one of them.
If this is so, then the very presence of the
org.kde.plasma.Notifications.service file will __PREVENT__ the real
org.freedesktop.Notifications service from starting.

This means that simply installing plasma on your system will likely break all
applications using notifications. That is unless you're also actively using
plasma or autostarting a notification service via some other means.

If you agree with this analysis then I hope that this problem will be fixed as
soon as possible, e.g. by moving the offending service file to a separate,
optional package.

Thanks in advance

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=382444

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=382444

David Edmundson  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #3 from David Edmundson  ---
Ugh, yep. Will fix.
Thanks

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=382444

--- Comment #2 from bluescreenaven...@gmail.com ---
Created attachment 106758
  --> https://bugs.kde.org/attachment.cgi?id=106758=edit
Small trace of konsole hanging

I don't have the full symbols, I can recompile with them if you want, but it
looks like it waits...

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

[frameworks-knotifications] [Bug 382444] Applications hang when trying to call org.freedesktop.Notifications due to plasma_waitforname, when plasma is not running

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=382444

David Edmundson  changed:

   What|Removed |Added

Version|master  |5.36.0
   Target Milestone|1.0 |---
 CC||k...@davidedmundson.co.uk,
   ||kdelibs-b...@kde.org
Product|plasmashell |frameworks-knotifications
   Assignee|k...@privat.broulik.de   |mklape...@kde.org
  Component|Notifications   |general

--- Comment #1 from David Edmundson  ---
plasma_waitforname being activated is fine.

Konsole shouldn't be blocked on anything though. If it is that's a bug in the
notification lib. 

If you can get a backtrace of konsole whilst it is blocked that would be great.

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