Bug 1020038 - tons of rejected send messages when switching bluetooth off in gnome-shell
Summary: tons of rejected send messages when switching bluetooth off in gnome-shell
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-16 20:42 UTC by Georg Sauthoff
Modified: 2015-02-17 17:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:42:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
log journal entries after switching bluetooth off in gnome-shell (5.39 KB, text/plain)
2013-10-16 20:42 UTC, Georg Sauthoff
no flags Details

Description Georg Sauthoff 2013-10-16 20:42:36 UTC
Created attachment 813104 [details]
log journal entries after switching bluetooth off in gnome-shell

Description of problem:

When clicking on 'Bluetooth->Off' in the gnome-shell top bar the log journal is flooded with 'rejected send message' messages etc. by dbus and co.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. boot into gnome-shell
2. click on the bluetooth symbol
3. click on off
4. watch journactl -f output

Actual results:

ends with:

Oct 16 10:14:23 host systemd[1]: Stopping Bluetooth.
Oct 16 10:14:23 host systemd[1]: Stopped target Bluetooth.
Oct 16 10:14:23 host gnome-session[1694]: Agent unregistration failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Method "UnregisterAgent" with signature "o" on interface "org.bluez.Adapter" doesn't exist
Oct 16 10:14:23 host gnome-session[1694]: 'g-io-error-quark'
Oct 16 10:14:23 host dbus-daemon[532]: dbus[532]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.92" (uid=1000 pid=1956 comm="/usr/bin/gnome-shell ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=502 comm="/usr/sbin/bluetoothd -n ")
Oct 16 10:14:23 host dbus[532]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.92" (uid=1000 pid=1956 comm="/usr/bin/gnome-shell ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.0" (uid=0 pid=502 comm="/usr/sbin/bluetoothd -n ")

see attachment for complete logs

Expected results:

No error messages in the log journal.

Additional info:

Using the builtin bluetooth hardware on a Thinkpad x220.

Comment 1 Fedora End Of Life 2015-01-09 20:16:50 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 17:42:57 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.