Bug 1084689

Summary: Rejected send message, 2 matched rules; type="method_c all", sender=":1.20" (uid=1000 pid=1818 comm="kdeinit4: plasma-desktop [kdeinit]
Product: [Fedora] Fedora Reporter: Peter H. Jones <jones.peter.busi>
Component: dbusAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: gilboad, jgrulich, jreznik, kevin, lpoetter, rdieter, than, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:18:23 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:
Attachments:
Description Flags
/var/log/messsages none

Description Peter H. Jones 2014-04-05 14:45:55 UTC 
Created attachment 883039 [details]
/var/log/messsages

Description of problem:
Messages in /var/log/messages

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


How reproducible:
Tried only once

Steps to Reproduce:
1. Download and boot http://kojipkgs.fedoraproject.org//work/tasks/8298/6708298/Fedora-Live-Jam-KDE-x86_64-rawhide-20140404.iso on a Tosiba Qosmio X770
2. Select Troubleshooting, and edit the command line to remove "threadirqs". (Otherwise, the kernel crashes with an onscreen trace displayed.)
3. Boot

Actual results:
System runs, but there are messages is /var/log/messages

Expected results:
No bluetooth timeout messages. This is a very fast machine.

Additional info:
bluez messages start at about line 2090 in attached /var/log/messages file.
Comment 1 Peter H. Jones 2014-04-05 19:29:09 UTC 
In Step 2, I thought the system was locked up. However, in bug 1061869, with the next day's ISO, I found that if I waited another 60 seconds, I got the lockup message after the trace.
Comment 2 Jaroslav Reznik 2015-03-03 15:40:04 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 3 Fedora End Of Life 2016-07-19 11:18:23 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.