Bug 1711001

Summary: Notification (libnotify) are not working
Product: [Fedora] Fedora Reporter: Hubert FONGARNAND <hubert>
Component: deepin-session-uiAssignee: Robin Lee <robinlee.sysu>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: felixonmars, robinlee.sysu, sensor.wen, sztsian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-19 22:45:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hubert FONGARNAND 2019-05-16 18:06:38 UTC
Description of problem:

My Slack application freezed when an event launch a notification (that's how i've discovered the bug)

$ notify-send test

wait 20 seconds and nothing is displayed.

It works well with other desktop environment on the same machine


Version-Release number of selected component (if applicable): 
$ dnf info deepin-session-ui

How reproducible: always


Steps to Reproduce:
1. $ notify-send test


Actual results:
wait 20 seconds and nothing is displayed.


Expected results:
it should display a notification with test title


Additional info:

Comment 1 Robin Lee 2019-05-17 01:55:21 UTC
I don't meet this issue on my system. Does 'org.freedesktop.Notifications' name exist on D-BUS session bus?
And which program serving this name? On my system it is /usr/libexec/deepin-daemon/dde-osd

Comment 2 Hubert FONGARNAND 2019-05-17 05:07:00 UTC
[hufon@ipponhufon ~]$ qdbus org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.DBus.Introspectable.Introspect
Error: org.freedesktop.DBus.Error.NoReply
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Comment 3 Hubert FONGARNAND 2019-05-17 05:09:24 UTC
The same command on kde
[hufon@ipponhufon ~]$ qdbus org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.DBus.Introspectable.Introspect
<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node>
  <interface name="org.freedesktop.Notifications">
    <signal name="NotificationClosed">
      <arg direction="out" type="u" name="id"/>
      <arg direction="out" type="u" name="reason"/>
    </signal>
    <signal name="ActionInvoked">
      <arg direction="out" type="u" name="id"/>
      <arg direction="out" type="s" name="action_key"/>
    </signal>
    <method name="Notify">
      <annotation value="QVariantMap" name="org.qtproject.QtDBus.QtTypeName.In6"/>
      <arg direction="out" type="u"/>
      <arg direction="in" type="s" name="app_name"/>
      <arg direction="in" type="u" name="replaces_id"/>
      <arg direction="in" type="s" name="app_icon"/>
      <arg direction="in" type="s" name="summary"/>
      <arg direction="in" type="s" name="body"/>
      <arg direction="in" type="as" name="actions"/>
      <arg direction="in" type="a{sv}" name="hints"/>
      <arg direction="in" type="i" name="timeout"/>
    </method>
    <method name="CloseNotification">
      <arg direction="in" type="u" name="id"/>
    </method>
    <method name="GetCapabilities">
      <arg direction="out" type="as" name="caps"/>
    </method>
    <method name="GetServerInformation">
      <arg direction="out" type="s" name="name"/>
      <arg direction="out" type="s" name="vendor"/>
      <arg direction="out" type="s" name="version"/>
      <arg direction="out" type="s" name="spec_version"/>
    </method>
  </interface>
  <interface name="org.freedesktop.DBus.Properties">
    <method name="Get">
      <arg name="interface_name" type="s" direction="in"/>
      <arg name="property_name" type="s" direction="in"/>
      <arg name="value" type="v" direction="out"/>
    </method>
    <method name="Set">
      <arg name="interface_name" type="s" direction="in"/>
      <arg name="property_name" type="s" direction="in"/>
      <arg name="value" type="v" direction="in"/>
    </method>
    <method name="GetAll">
      <arg name="interface_name" type="s" direction="in"/>
      <arg name="values" type="a{sv}" direction="out"/>
      <annotation name="org.qtproject.QtDBus.QtTypeName.Out0" value="QVariantMap"/>
    </method>
    <signal name="PropertiesChanged">
      <arg name="interface_name" type="s" direction="out"/>
      <arg name="changed_properties" type="a{sv}" direction="out"/>
      <annotation name="org.qtproject.QtDBus.QtTypeName.Out1" value="QVariantMap"/>
      <arg name="invalidated_properties" type="as" direction="out"/>
    </signal>
  </interface>
  <interface name="org.freedesktop.DBus.Introspectable">
    <method name="Introspect">
      <arg name="xml_data" type="s" direction="out"/>
    </method>
  </interface>
  <interface name="org.freedesktop.DBus.Peer">
    <method name="Ping"/>
    <method name="GetMachineId">
      <arg name="machine_uuid" type="s" direction="out"/>
    </method>
  </interface>
</node>

Comment 4 Robin Lee 2019-05-17 05:48:22 UTC
(In reply to Hubert FONGARNAND from comment #2)
> [hufon@ipponhufon ~]$ qdbus org.freedesktop.Notifications
> /org/freedesktop/Notifications org.freedesktop.DBus.Introspectable.Introspect
> Error: org.freedesktop.DBus.Error.NoReply
> Did not receive a reply. Possible causes include: the remote application did
> not send a reply, the message bus security policy blocked the reply, the
> reply timeout expired, or the network connection was broken.

Was /usr/libexec/deepin-daemon/dde-osd running on your Deepin environment? Any strange log entry found in user journal?

Comment 5 Hubert FONGARNAND 2019-05-17 07:01:50 UTC
no, dde-osd don't run in my system.
But if i start it manually in a terminal, it works! It seems that dde-osd is not started automatically.

Where can i found the user journal?

Comment 6 Robin Lee 2019-05-17 07:44:14 UTC
(In reply to Hubert FONGARNAND from comment #5)
> no, dde-osd don't run in my system.
> But if i start it manually in a terminal, it works! It seems that dde-osd is
> not started automatically.
> 
> Where can i found the user journal?

'journalctl -b --user' will print all user log of current system boot.

Comment 7 Robin Lee 2019-05-17 07:51:25 UTC
Is dde-osd running at a freshly logged-in Deepin session?
Does com.deepin.dde.osd name exist on D-BUS session bus?

Comment 8 Hubert FONGARNAND 2019-05-17 08:37:08 UTC
No, dde-osd is not running at a freshly loggin-in Deepin session.

but sometimes, it loads after 1,2 minutes, sometimes not.

Comment 9 Robin Lee 2019-05-17 11:12:15 UTC
I can reproduce this now. Just login DDE through sddm.

Comment 10 Hubert FONGARNAND 2019-05-17 12:14:09 UTC
Nope, i've switched to ssdm.

The loading of dde-osd is still random...
Sometimes, it never loads, sometimes it loads 5min later after login.

Comment 11 Fedora Update System 2019-05-20 08:26:32 UTC
golang-deepin-go-lib-1.9.1-2.20190226git89a0355.fc30 startdde-3.12.1-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c938fcfb84

Comment 12 Fedora Update System 2019-05-20 08:26:37 UTC
golang-deepin-go-lib-1.9.1-2.20190226git89a0355.fc30 startdde-3.12.1-3.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c938fcfb84

Comment 13 Fedora Update System 2019-05-21 01:59:17 UTC
golang-deepin-go-lib-1.9.1-2.20190226git89a0355.fc30, startdde-3.12.1-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c938fcfb84

Comment 14 Hubert FONGARNAND 2019-05-21 07:43:38 UTC
I can confirm, the bug is fixed on my system.
Thank you!!!

Comment 15 Hubert FONGARNAND 2019-05-22 15:51:57 UTC
Hi, 

There's still a problem.

When my computer is going to standby mode, the dde-osd daemon is no more present, and it'no relaunched.

Comment 16 Fedora Update System 2019-06-19 22:45:02 UTC
golang-deepin-go-lib-1.9.1-2.20190226git89a0355.fc30, startdde-3.12.1-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.