Bug 891597 - Noticed D-Bus not built with -rdynamic so unable to print a backtrace message while rebooting the system.
Summary: Noticed D-Bus not built with -rdynamic so unable to print a backtrace message...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dbus
Version: 18
Hardware: ppc64
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-03 11:10 UTC by IBM Bug Proxy
Modified: 2014-02-05 14:22 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 14:22:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/message (61.07 KB, text/plain)
2013-01-03 11:11 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 87611 0 None None None Never

Description IBM Bug Proxy 2013-01-03 11:10:59 UTC
Problem Description
------------------------------
While rebooting Fedora 18 Beta ppc64 installed onP7 LPAR system,noticed the following D-bus error on console.

[root@ltcfbl6fb06 ~]# reboot
Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
process 4031: arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1618.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted


--- Other Details ---

[root@ltcfbl6fb06 log]# uname -a
Linux ltcfbl6fb06.austin.ibm.com 3.6.6-3.fc18.ppc64p7 #1 SMP Fri Nov 9 11:18:55 MST 2012 ppc64 ppc64 ppc64 GNU/Linux


== Comment: #1 - Mahesh M. Hiremath <maheshhi.com> - ==
[root@ltcfbl6fb06 ~]# service dbus status
Redirecting to /bin/systemctl status  dbus.service
dbus.service - D-Bus System Message Bus
	  Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
	  Active: active (running) since Sun, 2012-12-23 23:43:14 MST; 1 weeks and 3 days ago
	Main PID: 457 (dbus-daemon)
	  CGroup: name=systemd:/system/dbus.service
		  ? 457 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Dec 23 23:43:13 ltcfbl6fb06.austin.ibm.com systemd[1]: Starting D-Bus System Message Bus...
Dec 23 23:43:14 ltcfbl6fb06.austin.ibm.com systemd[1]: Started D-Bus System Message Bus.
Dec 23 23:43:16 ltcfbl6fb06.austin.ibm.com dbus-daemon[457]: dbus[457]: [system] Activating via systemd: service name='org.f...ice'
Dec 23 23:43:16 ltcfbl6fb06.austin.ibm.com dbus[457]: [system] Activating via systemd: service name='org.freedesktop.Policy...vice'
Dec 23 23:43:16 ltcfbl6fb06.austin.ibm.com dbus-daemon[457]: dbus[457]: [system] Successfully activated service 'org.freedes...it1'
Dec 23 23:43:16 ltcfbl6fb06.austin.ibm.com dbus[457]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Dec 23 23:43:22 ltcfbl6fb06.austin.ibm.com dbus[457]: [system] Activating service name='org.freedesktop.nm_dispatcher' (usi...lper)
Dec 23 23:43:22 ltcfbl6fb06.austin.ibm.com dbus-daemon[457]: dbus[457]: [system] Activating service name='org.freedesktop.nm...per)
Dec 23 23:43:24 ltcfbl6fb06.austin.ibm.com dbus-daemon[457]: dbus[457]: [system] Successfully activated service 'org.freedes...her'
Dec 23 23:43:24 ltcfbl6fb06.austin.ibm.com dbus[457]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'


Attached /var/log/messages for reference. 

Thanks,
Mahesh

Comment 1 IBM Bug Proxy 2013-01-03 11:11:19 UTC
Created attachment 671988 [details]
/var/log/message

Comment 2 Fedora Admin XMLRPC Client 2013-02-22 15:21:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2013-02-22 15:25:06 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 IBM Bug Proxy 2013-07-15 13:51:19 UTC
------- Comment From maknayak.com 2013-07-15 13:48 EDT-------
verified on F19 GA-TC5 , did not notice this issue. Looks like its fixed in F19.

Thanks...
Manas

Comment 5 Fedora End Of Life 2013-12-21 10:10:04 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 6 Fedora End Of Life 2014-02-05 14:22:14 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.