By the way, I saw the Bug4308, which seems similar, but about using a second session (not my case), so I don't know if this is actually a duplicate bug.

I also saw Bug1440 (and a bunch of other marked as duplicates), but it was for Mageia 1 and closed as not reproduced on Mageia 2 (which I may have just done then!).

A difference though in Bug1440 is that the diagnostic seemed to be that it is related to messagebus being stopped. In my case, it is started.

root@DarkMarmot  $ service messagebus status
dbus.service - D-Bus System Message Bus
          Loaded: loaded (/lib/systemd/system/dbus.service; static)
          Active: active (running) since Mon, 01 Oct 2012 14:20:53 +0900; 1h 53min ago
         Process: 3028 ExecStartPre=/bin/rm -f /var/run/messagebus.pid (code=exited, status=0/SUCCESS)
         Process: 3025 ExecStartPre=/usr/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
        Main PID: 3030 (dbus-daemon)
          CGroup: name=systemd:/system/dbus.service
                  â 3030 /usr/bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
                  â 3127 /usr/lib64/upowerd

Oct 01 14:35:22 DarkMarmot dbus-daemon[3030]: dbus[3030]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='ud...service'
Oct 01 14:35:22 DarkMarmot dbus[3030]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Oct 01 14:35:22 DarkMarmot dbus[3030]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Oct 01 14:35:22 DarkMarmot dbus-daemon[3030]: dbus[3030]: [system] Successfully activated service 'org.freedesktop.UDisks2'


Not sure if that helps.

seems all you issue are related to dbus, 

Colin, Thierry, Thomas, is dbus restarted during an update (specially of a kernel)?

CC: (none) => mageia, thierry.vignaud, tmb
Source RPM: drakx-net-applet-1.12.2-1.mga2 => dbus

Manuel: I did not just upgrade to a new Kernel.
I see that my message may have been misleading on this particular point. I just wanted to explain why the pasted debug log would show "Kernel version = 3.5.4-desktop-1.mga3". The reason being that I installed this kernel from Cauldron (but only this rpm, my distribution is otherwise not configured to use cauldron and is a normal Mageia 2). I needed it to have support for the Intuos 5 graphical tablet (support appeared since 3.5 kernels).

But other than that, I did this installation and have worked without a problem with this kernel for about 2 weeks now. And I kept the old 3.3.8 kernel and could confirm the issue also happens there. So does not seem kernel-related.
The multiple crashs have only been happening for the last 2 days. And I can't see what I may have installed recently which may screw up that much the system. Is there a log which shows all recent installed or uninstalled packages?

Hi,

I did a fresh reinstall of my Mageia 2 and the same issue happened again!
But this time, I kept a log of all the packages I installed between one boot and another, so I could find the culprit.

It was mpd-0.16.6-2.mga2.tainted.x86_64
After install, I only updated the /etc/mpd.conf by changing the values "music_directory" and "playlist_directory" to proper paths, and set a PulseAudio output, as shown on the web, instead of the Alsa one (which I commented out) which defaults the package (by the way, as Mageia apparently chooses PulseAudio as its default output, so that should be set by default):

audio_output {
        type    "pulse"
        name    "My MPD PulseAudio Output"
        #server  "localhost"   # optional
        #sink    "alsa_output" # optional
}

Then if I start the service, works fine and all (can listen to music using a mpd client, like gmpc)... until next reboot where I got the crash of net_applet, etc. (and mpd service is not working anymore after reboot either, even though a "status" tells it is, but the "restart" hanged for minutes, so I killed it).

Now that I think of it, it was highly possible that I recently installed mpd on my old Mageia 2.

@Jehan, this looks totally unrelated to this bug? Did you perhaps comment on the wrong one? If you find the right one please comment there and make sure I'm in the CC field. Thanks.

Colin: as strange as it looks, it is not unrelated.

History:
- I had these strange crashes of net_applet (and sometimes draknetcenter too) at startup (apparently dbus issue, according to Manuel above). As I use a lot my machine and sometimes don't stop it for some time, I had no idea what could have caused it at the time, or what I could have installed recently.

- I reinstalled recently my whole Mageia 2, brand out of the installer, and encountered again crashes this morning when booting, but this time I knew what I just installed the day before. I tried to uninstall mpd, I reboot. No crash anymore.
Note that to be extra-sure this is not pure bad luck, I made a test again, I reinstalled mpd, rebooted. Paf! net_applet crash at startup.
I uninstall, reboot. No crash.

I have absolutely no idea what is the problem, but seems to be related.

I can make a test again, if you want me to be extra-extra-sure. I can also try to set some logs, if you tell me which ones/how.

@Jehan, interesting results.

I'll try and take a look at this. 

Just as a small extra test that would be very useful, is simply disabling the mpd service enough here to prevent the crash (and cause it again after reenabling)? It would be nice to know if it's either
 a) The fact the package is installed
or
 b) The fact the service is running

that is causing these problems.

Just run, "systemctl disable mpd.service" (as root) and do a few reboots and see if there are crashes, if not, then "systemctl enable mpd.service" and do a few more reboots and confirm that things crash.

That would be most helpful!

* If I disable the service at startup with `systemctl disable mpd.service`, net_applet doesn't crash.
So the answer to the crash is  "b) The fact the service is running".

* I have also made a few configuration test: if I use the default configuration (using Alsa output), there is no crash either. Only when commenting out Alsa audio output and setting Pulseaudio instead, there is a crash.
I made a test where I changed *only* the audio output (and not also the music_directory and playlist_directory like before), and it would crash. With no change at all, no crash though.
Of course, we could say "don't use pulseaudio", but as Mageia now uses Pulseaudio as a default, and this version of mpd is supposed to support Pulseaudio (cf. `mpd --version`), I'd say this is not the right answer.
I copy again my audio output:

audio_output {
        type    "pulse"
        name    "My MPD PulseAudio Output"
}

This config is taken from the official wiki: http://mpd.wikia.com/wiki/PulseAudio

* If I deactivate mpd at startup, but activate the service manually with `service mpd start` after some time, it works well, and there is no net_applet crash.
net_applet crash happens only when mpd is started as a startup service.

It makes me think that the problem is that MPD, through pulseaudio, must hang the connection with dbus, or something like this; and it provokes a net_applet crash, because it can't connect. But if I start manually later, it does not block net_applet. Or something similar?

Hope this helps. In my case, this is reproducible 100% up to now, after a dozen reboots.

This is very useful thanks.

As one of the upstream PulseAudio maintainers, I can state that this should definitely work, even if there are still caveats to the limits of working in this context.

I'll try and do some tests and write up a more detailed reply shortly.

Col

mine throw 
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied
Cannot open /dev/input/eventX: Permission denied

when tried to connect/disconnect from net_applet

even i do not have mpd.service

# systemctl disable mpd.service
Failed to issue method call: No such file or directory

CC: (none) => andry_yosua

Colin: "I'll try and do some tests and write up a more detailed reply shortly." :)

CC: (none) => stormi

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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