The error message is that notification-daemon-xfce (version 0.3.5) conflicts with notification-daemon-xfce-0.3.6-5mdv2007.0.i586. The 0.3.5 version of teh package came with 4.3.99.2; the 0.3.6 came with 4.4.0. A number of key gnome applications (evolution, gdm) depend on notification-daemon-0.3.5.

Is this a packaging error, or is 0.3.6 truely different from 0.3.5? Thanks for any insights.

Re: Notification-daemon-xfce-0.3.6 (4.4.0) conflicts with version of RC2?) [SOLVED]

Thanks Nick. I have got libnotify1-0.4.2 installed (cannot install libnotify1-0.4.3.2 as that requires notification-daemon-xfce-0.3.6 which concflicts with notification-daemon-0.3.5).

Could this lead to problems with auto-mouting of USB-keys and/or CD's? I notice that with 4.4.0 tehse do not automatically mount, whereas 4.4.RC2 auto-mounted (at least) USB keys without problem (open, thunar, click on Icon which appears in Thunar shortcuts and you'll see all files). Now I get the following message instead:

Failed to mount "sda1".
exo-mount: Cannot mount by HAL device UDI, because HAL support was disabled for this build.

Re: Notification-daemon-xfce-0.3.6 (4.4.0) conflicts with version of RC2?) [SOLVED]

I do have /usr/lib/libexo-hal-0.3.so.0 and /usr/lib/libexo-hal-0.3.so.0.4.0. These come from libexo, versions 0.3.1.8 and 0.3.2. My guess is that the the 0.3.2 version was built differently than the 0.3.1.8 version -- such is progress (and the concept of building from source is becoming another step more attractive, may be this is the time to check the Os-cillation installer). Will do some further digging and probably file a report with Mandriva

Re: Notification-daemon-xfce-0.3.6 (4.4.0) conflicts with version of RC2?) [SOLVED]

Got it!

I replaced the folowing packages from Mandriva's standard install by the ones prepared by Charles Edwards:

thunar-0.8.0

libthunar1_2-0.8.0

exo-0.3.2

libexo-0.3_0

These packages apparently have been compiled with HAL support; clicking on the USB-key icon mounts it (provided a directory /mnt/key exists, but that is something I can fix). Note that just replacing exo and libexo was [i]not/i] sufficient.