| Summary: | Fail to open logs where a unique name is unknown | ||
|---|---|---|---|
| Product: | Bustle | Reporter: | Marco Barisione <marco.barisione> |
| Component: | General | Assignee: | Will Thompson <will> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
Fixed in master; will be in 0.2.4. Bustle now just warns and makes :1.97 spring into existence just in time for the message that needs it. A bunch of other cases where corrupt logs would lead to an unhelpful error bubble have also been made to make stuff up. The warnings go to the console; in a better world they would be shown in a panel in the UI. But hey. Thanks for the report! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
I got a lot from somebody that cannot be opened by bustle because of this error message: OtherName {unOtherName = "org.freedesktop.Telepathy.Connection.gabble.jabber.testipersoona_40gmail_2ecom_2f2ea6dddf"} claimed by unknown unique name UniqueName {unUniqueName = ":1.97"} It looks like bustle-dbus-monitor doesn't list :1.97 at the beginning of the log (wtf?). In any case it would be nicer if it could cope better with this problem.