Bug 197 - dbus_message_unref() error message with systemd
Summary: dbus_message_unref() error message with systemd
Status: RESOLVED FIXED
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-02-26 17:26 CET by stephane FLAVIGNY
Modified: 2011-05-14 18:03 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description stephane FLAVIGNY 2011-02-26 17:26:20 CET 
I can read (when I push: Ctrl+Alt+"F7"):

process 1795: arguments to dbus_message_unref() were incorrect, assertion "!message->in_cache" failed in file dbus-message.c line 1548.
D-Bus not build with -rdynamic so unable to print a backtrace.

Stef.



Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2011-03-09 09:34:21 CET 
Which program generated this?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Comment 2 stephane FLAVIGNY 2011-03-11 11:57:46 CET 
When I start. 

KDM don't start. I have only black screen. If I do Ctrl+Alt+"F7" I can read it.

After I log me on tty2 and do telinit 5 and after kdm start. Bug I'm not sure it's the same problem.

How to know witch proccess is 1795? 

Stef.
Comment 3 John Balcaen 2011-03-15 11:17:25 CET 
you can use ps & grep for that pid.

CC: (none) => balcaen.john

Comment 4 D Morgan 2011-03-23 00:20:14 CET 
can you please provide the info asked in comment 3 ?

CC: (none) => dmorganec

Comment 5 stephane FLAVIGNY 2011-03-23 17:53:46 CET 
Not now.

I come back at home in April normaly.

Stef.
Comment 6 stephane FLAVIGNY 2011-04-14 18:20:00 CEST 
No information with ps and top.

Stef.
Comment 7 stephane FLAVIGNY 2011-04-16 10:08:42 CEST 
I think the best way, it to know with process start after alsa.

This line arrive after alsa start.

How to do it?

Stef.
Comment 8 Michael Scherer 2011-04-26 16:37:07 CEST 
You should start with nopinit on kernel command line, or try to search in the log.

CC: (none) => misc

Comment 9 stephane FLAVIGNY 2011-04-27 10:48:14 CEST 
I make this option. With this one, the boot continu but I can read the last message too, and at the and of boot, X don't start.

stef.
Comment 10 stephane FLAVIGNY 2011-04-27 10:48:55 CEST 
I don't find some information in log ( message and X).
Comment 11 Angelo Naselli 2011-04-27 11:45:41 CEST 
just out of curiosity could you please check start order in runlevel 5 of messagebus and dm?

CC: (none) => anaselli

Comment 12 stephane FLAVIGNY 2011-04-27 15:09:04 CEST 
Can you explain how to do it please.
Comment 13 Angelo Naselli 2011-04-27 15:24:09 CEST 
ls /etc/rc5.d/S*messa*
ls /etc/rc5.d/S*dm
Comment 14 stephane FLAVIGNY 2011-04-27 15:40:58 CEST 
For:
ls /etc/rc5.d/S*messa*
=>  /etc/rc5.d/S53messagebus@

ls /etc/rc5.d/S*dm
=> /etc/rc5.d/S15mdadm@ /etc/rc5.d/S55dm@

stef.
Thierry Vignaud 2011-04-28 08:47:21 CEST

Summary: dbus_message_unref() => dbus_message_unref() error message with systemd

Comment 15 stephane FLAVIGNY 2011-05-14 18:03:43 CEST 
I'm installing the beta 2 today.

I don't arrive to reproduce it.

For me it solved.

Stef.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.