Bug 1653371 - dbus failure
Summary: dbus failure
Keywords:
Status: CLOSED DUPLICATE of bug 1653059
Alias: None
Product: Fedora
Classification: Fedora
Component: dbus
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-26 16:32 UTC by contactopublico57
Modified: 2018-11-30 14:43 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 14:43:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description contactopublico57 2018-11-26 16:32:17 UTC
Description of problem:Fedora Rawhide upgrade to dbus boot failure.
Bug search revealed no pending since 112519.

Version-Release number of selected component (if applicable):
as of 112618  dbus-1.12.10-9.fc30.x86_64


How reproducible:
upgrade dbus and related files via dnf

Steps to Reproduce:
1.dnf upgrade Fedora 30 Rawhide 
2.reboot dbus failure prevents initialization of key components including
lightdm login manager.
3.Boot fails prior to login manager.  Subsequent reboots fail equally.

Actual results: Failure to initialize key components including Network Manager and Login Manager attributed to dbus failure, visible with verbose bootscreen.


Expected results: Normal boot sequence to Login Manager, Login, Mate Desktop initialiation as normal.


Additional info: Download only and parsing packages to omit install of dbus and related dbus packages eliminates boot failure. 

dbus-1.12.10-9.fc30.x86_64.rpm         
dbus-broker-16-4.fc30.x86_64.rpm       
dbus-common-1.12.10-9.fc30.noarch.rpm  
dbus-daemon-1.12.10-9.fc30.x86_64.rpm  
dbus-libs-1.12.10-9.fc30.x86_64.rpm    
dbus-tools-1.12.10-9.fc30.x86_64.rpm   
dbus-x11-1.12.10-9.fc30.x86_64.rpm

Comment 1 Gwyn Ciesla 2018-11-30 14:43:32 UTC

*** This bug has been marked as a duplicate of bug 1653059 ***


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