DBUS-CYNARA rejects "NameLost"

Won't Fix

Description

Dbus with cynara rejects NameLost signals

See log extract below:

Jun 19 13:17:22 m3ulcb dbus-daemon[3655]: [system] Rejected receive message, 1 matched rules; type="signal", sender="(unset)" ((bus)) interface="org.freedesktop.DBus" member="NameLost" error name="(unset)" requested_reply="0" destination=":1.26" (uid=0 pid=4317 comm="sshd: root [priv] " label="System") privilege="http://tizen.org/privilege/internal/dbus"

This is related integration of cynara in DBUS.

Environment

None

Activity

Show:

Walt Miner 
March 29, 2023 at 6:31 PM

App FW deprecated from UCB starting with Marlin release (14.0.0)

jose bollo 
July 10, 2019 at 7:58 AM

I haven't seen consequences and then postponed the resolution of that issue at low priority.

Not seeing consequence doesn't mean that there is no consequence. So it has to be fixed.

I shortly investigated that issue without seeing how to solve it. My current understanding is that it happens because the sender is "(unset)" and then the code has to be changed to handle it correctly. But not 100% sure that it is the right explanation.

Scott Murray 
July 9, 2019 at 9:58 PM

Just wondering, is there a consequence from this happening, or are they harmless?

Details

Assignee

Reporter

Contract ID

Components

Priority

Created June 19, 2019 at 1:25 PM
Updated March 29, 2023 at 6:31 PM
Resolved March 29, 2023 at 6:31 PM

Flag notifications