ayatana-indicator-display/src/usb-snap.cpp, branch 22.9.0 Ayatana Indicator Display Service https://openid.arctica-project.org/ayatana-indicator-display/atom?h=22.9.0 2021-11-09T00:54:47+00:00 Rename Lomiri-specific properties to x-lomiri 2021-11-09T00:54:47+00:00 Robert Tari robert@tari.in 2021-11-09T00:54:47+00:00 urn:sha1:e61cc79af79d6d09cc61a0d987f38831dff8d300 Raname x-canonical properties to x-ayatana 2021-10-27T16:10:32+00:00 Robert Tari robert@tari.in 2021-10-27T14:20:10+00:00 urn:sha1:2cefc0f4f3c12a3956b8e8383ddbc8838d21cff5 remove the temporary tracers 2016-04-27T08:43:08+00:00 Charles Kerr charles.kerr@canonical.com 2016-04-27T08:43:08+00:00 urn:sha1:020e49163abd558ae095ab9a00b6b69b4fdaef2a choosing an action in the snap decision closes the notification, so when that happens clear our notification_id s.t. our dtor doesn't try to remove a notification that no longer exists 2016-04-27T08:22:00+00:00 Charles Kerr charles.kerr@canonical.com 2016-04-27T08:22:00+00:00 urn:sha1:a277302b1c1c2568c456abcb3432eb8f8ead0925 add tracers for the notification warning 2016-04-27T07:56:53+00:00 Charles Kerr charles.kerr@canonical.com 2016-04-27T07:56:53+00:00 urn:sha1:f8a8646b5cc0e9b59a5f953dcd8129c93d162915 replace text 'Deny' with 'Don't Allow' for consistency with other permission prompts 2016-03-23T17:16:06+00:00 Charles Kerr charles.kerr@canonical.com 2016-03-23T17:16:06+00:00 urn:sha1:82588108a40fb50b2bbd3c7b89b990f76f488edc in UsbManager, reset AdbdClient on usb disconnect 2016-03-21T22:05:01+00:00 Charles Kerr charles.kerr@canonical.com 2016-03-21T22:05:01+00:00 urn:sha1:1c4f005f0765f460b28808a624fbec7737324b1a if our USB device is disconnected while prompting the user for ADBD, cancel the prompt. 2016-03-21T18:40:11+00:00 Charles Kerr charles.kerr@canonical.com 2016-03-21T18:40:11+00:00 urn:sha1:7a25132c125f6e5e413ad26ea950ae22bee982f5 de-dupe use of dbus names 2016-03-17T14:59:32+00:00 Charles Kerr charles.kerr@canonical.com 2016-03-17T14:59:32+00:00 urn:sha1:c63d90da0f1d9cbd1eee5dd66a9828c51cc8dcc9 oops, last commit's diagnosis was incorrect. The timing test issue came from async dbus handling interfering with fast setup/teardown of automated tests. Revert the last change and fix by setting up the dbus signal subscription immediately upon getting the dbus connection. 2016-03-15T21:12:05+00:00 Charles Kerr charles.kerr@canonical.com 2016-03-15T21:12:05+00:00 urn:sha1:ee369babc9185bac7c7910a68a1e58bab7efa64c