Bug 2794 - Erreur during the update of GConf2-sanity-check
Summary: Erreur during the update of GConf2-sanity-check
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-09-20 20:21 CEST by Bernard SIAUD
Modified: 2012-02-03 13:51 CET (History)
1 user (show)

See Also:
Source RPM: GConf2-3.1.92-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Bernard SIAUD 2011-09-20 20:21:06 CEST
136/230: GConf2-sanity-check   ###########################################################################################
process 10740: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3483.
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
/var/tmp/rpm-tmp.gnFUBd : ligne 3 : 10740 Abandon                 /bin/systemctl daemon-reload 2>&1
Comment 1 Marja Van Waes 2011-12-01 17:13:38 CET
Hi Bernard,

Sorry we never responded to this bug report. We are very short on triagers.

We are on version 2-3.2.3-1 in cauldron now, did this error repeat itself with last update?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Marja Van Waes 2012-01-18 10:52:45 CET
@ Bernard

Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD.
Comment 3 Marja Van Waes 2012-02-03 13:51:19 CET
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD


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