As part of a test in bug 15832, I installed M5 RC with KDE and tried to add Mate from the DVD (in MCC, "Install and Remove Programs"). To my surprise, MCC refused to install it with the message: Package task-mate-minimal cannot be selected: conflict with mate-settings-daemon-gstreamer... I then did the following: - opened configure medias for update and installation - added internet medias - went to install and remove programs, chose all programs (not just GUI ones) - searched task-mate-minimal - said OK to update rpmdrake when asked then installed task-mate-minimal (this time without any problems) Restarted computer because of new glibc and Mate was there and working. I consider this to be an acceptable workaround, so this bug might be even marked as RESOLVED, WORKSFORME or WONTFIX, since using internet repos is unavoidable due to security issues.
Priority: Normal => Low
> ... since using internet repos is unavoidable due to security issues. Correcting myself, I meant actually: ... since using internet repos is unavoidable due to security UPDATES.
CC'ing maintainer I think QA team has managed to succesfully install Mate during Mageia install, so CC'ing them, too.
CC: (none) => marja11, qa-bugs, tarakbumba
It's caused by a circular dependency error in the mate-settings-daemon.spec. Where I had tested it on Q&A was in a mga4 to mga5 upgrade. mate-settings-daemon and mate-settings-daemon-pulse were Not updated to the current version. The current settings-daemon pkg needs an Obsoletes: mate-settings-daemon < 1.7.0
CC: (none) => cae
Charles had reported this a while ago. We' re in a complete freeze now and i' ll update the package whenever svn is re-open to commits. Assigning this to myself. Thanks for reporting.
Assignee: bugsquad => tarakbumba
Has it been added to Errata?
Priority: Low => NormalWhiteboard: (none) => MGA5TOO FOR_ERRATASeverity: minor => normal
Does it mean that choosing to install MATE from the classical installer will end up in a failed install?
Nope. I tested it and Mate is correctly installed with the M5 RC 586 DVD. Since you're all busy, I'm adding a note on Errata. Feel free to erase it if you got a better idea... under the "Mate" entry in "Software Issues". https://wiki.mageia.org/en/Mageia_5_Errata
(In reply to Charles Edwards from comment #3) > It's caused by a circular dependency error in the mate-settings-daemon.spec. > Where I had tested it on Q&A was in a mga4 to mga5 upgrade. > mate-settings-daemon and mate-settings-daemon-pulse were Not updated to the > current version. > > The current settings-daemon pkg needs an > Obsoletes: mate-settings-daemon < 1.7.0 This cant be right... a package obsoleting itself is crap
CC: (none) => tmb
(In reply to Thomas Backlund from comment #8) > (In reply to Charles Edwards from comment #3) > > It's caused by a circular dependency error in the mate-settings-daemon.spec. > > Where I had tested it on Q&A was in a mga4 to mga5 upgrade. > > mate-settings-daemon and mate-settings-daemon-pulse were Not updated to the > > current version. > > > > The current settings-daemon pkg needs an > > Obsoletes: mate-settings-daemon < 1.7.0 > > > This cant be right... a package obsoleting itself is crap Did you even bother to look at the mga4 and 5 specs? In Mga4 mate-settings-daemon-pulse and mate-settings-daemon-gsteamer are separate src.rpm. Each provides the specific backend and Each provides mate-settings-daemon In Mga5 all 3 are separate rpms from the same src.rpm. mate-settings-daemon provides mate-settings-daemon and each backend only provides mate-settings-daemon-<backend> Without the obsolete in the mga5 1.8.2 pkg, it does cleanly update the mga4 1.6.2 pkgs As is the mga5 installer chooses not to update any mate-settings-daemon rpms Or task-mate-minimal all remain mga4.
After upgrade from 4 to 5 using 64bit dvd only .. $ rpm -qa mate-settings-daemon* mate-settings-daemon-pulse-1.6.2-3.mga4 I'll attach logs
Created attachment 6684 [details] report.bug.xz report.bug.xz does not contain upgrade info but report.bug does, so xz compressed that one instead to attach.
* auto-select: multiple packages (mate-settings-daemon-pulse-1.8.2-2.mga5.x86_64 mate-settings-daemon-gstreamer-1.8.2-2.mga5.x86_64) obsoleting mate-settings-daemon-pulse-1.6.2-3.mga4.x86_64
Just for completeness, a better reply for Rémi -- what I've tested: - Mate as the only desktop installs OK and - Mate together with Xfce and LXDE installs OK. I didn't test the classical installer with Mate and any combination of KDE, Gnome or Cinnamon. If I get the chance to do it, I'll post the results here.
Whiteboard: MGA5TOO FOR_ERRATA => MGA5TOO IN_ERRATA
Tested also installing the whole shebang. It's interesting to notice that Gnome installs Gnome (Gnome 3?) and Gnome Classic (Gnome 2?). And Cinnamon means Cinnamon and Cinnamon 2D. Mate was installed and works. I think I noticed LXDE complain, when one end the session, about a mixer (was it pnmixer or was it about Alsa). Something to be tested again... but that does not happen when one just installs LXDE. Personal rants, quite off-topic, feel free to ignore: 1. That's not really applicable to modern machines, but so that you know, Cinammon and Gnome, in all versions, are extremely slow in that PC. All of them are unusable as installed -- surprisingly Gnome 3 was a tad bit better, but it's still unusable. KDE as installed was very much usable, just for reference. I was surprised a bit, because Mate is quite nimble -- and I take it to be just like Gnome 2. But then Classic perhaps is not Gnome 2. 2. For the trouble Mate gives, I found out I personally can't use it because it lacks several niceties XFce and KDE have. Simple things that are part of the GUI feel. And now that PCmanFM can be told not to select things automatically, I wonder what benefits Mate has over it. Of course, some Mate things are used in Xfce and LXDE, so it may be important after all.
It takes all sorts Renato. Personally, I would drop Mageia like a hot potato if it did not support Mate. It is the only environment in which I feel comfortable. Dislike KDE and could not use GNOME 3 ever. Personal opinion; feel free to ignore. And you are correct, Mate is very like GNOME 2, which was my preferred desktop in Mandriva. I jumped ship when the company started talking about supporting only KDE.
CC: (none) => tarazed25
> It takes all sorts Renato. My late grandfather used to say such things: what would happen to blue if everybody liked yellow? > Personal opinion Thanks for sharing. You'd be amazed at how many things I've learned from "personal opinions" thru the years. People usually think opinion is easy, but some things are not obvious to everyone. Mate feels really fast on older PCs, I'll give you that. Maybe it can be configured to my tastes and I simply don't know how to do it. If the developers can bring to Mate all the niceties that Xfce has, it might become a great desktop. I won't bother you with details,just three things (besides doing single-click in a clean way): - shading a window with the mousewheel (quick to work on things behind it); - not raising a window when one clicks inside it (allows pasting without disrupting the window arrangement) and - tiling/untiling windows at the border. Unless I'm wrong, Compiz might do some of these things... I'll try to find out. Well, I think you're safe because Mageia seems to take Mate more seriously. Also, in Mandriva's case, I think they thought Gnome 2 was going to be unsupported because the Gnome guys would put all bets on version 3 -- which kinda happened when one sees Gnome Classic. Quite frankly, I get annoyed that KDE and Xfce have not the fast response that Mate and LXDE give. We should have the desktop issue solved by now.
(In reply to claire robinson from comment #12) > * auto-select: multiple packages > (mate-settings-daemon-pulse-1.8.2-2.mga5.x86_64 > mate-settings-daemon-gstreamer-1.8.2-2.mga5.x86_64) obsoleting > mate-settings-daemon-pulse-1.6.2-3.mga4.x86_64 I think i have solved the problem by removing obsoletes tag from both mate-settings-daemon-pulse and mate-settings-daemon-gstreamer. I can commit to svn if i'm allowed. I think we should havefixed packages in Mageia 5 Final so people can upgrade just using the Classical Dvd
Hardware: i586 => All
Anne, Thomas does this look right?
CC: (none) => ennael1
Just a little clarification: I just tested Mate's installation, not upgrading (I was testing another bug, actually). > We should have the desktop issue solved by now. Please note that was about the issue of latency in KDE and Xfce desktops, not the present bug. Sorry about any confusion, folks.
commit 78faadb10d6075e242c23031f224579758899c0a Author: Anne Nicolas <ennael@...> Date: Thu Jun 4 22:06:59 2015 +0200 exclude mate-settings-daemon-gstreamer from DVD isos (mga#16066) --- Commit Link: http://gitweb.mageia.org/software/build-system/bcd/commit/?id=78faadb10d6075e242c23031f224579758899c0a
Aham. Good news and bad news. In comment #24 of bug 16065, it is described how to achieve a minimal X installation. Afterwards, I started the MCC and noticed the following. I can select the following packages: *task-cinnamon-minimal *task-gnome-minimal *task-lxde-minimal *task-xfce-minimal =============================================== THIS PART IS IMPORTANT: I cannot select the following packages (select twice to know what is the problem): *task-kde4-minimal, because of conflict with phonon-gstreamer *task-mate-minimal, conflicts with mate-settings-daemon-gstreamer, as already noted === END OF IMPORTANT PART When trying to install from online repos, I noticed I couldn't add media ("media.cfg not found"). I've met a similar bug the other day... bug 12561. In the present case, using (even installing) wget didn't help; as suggested by David Walser on that bug, it might just be a momentous network issue. I went back and tried to reinstall everything again, this second time allowing the suggested packages and basic documentation. Now finally I could install task-kde4-minimal... 751 packages! Very minimal, indeed. BTW, installing KDE is not enough as XDM is still the display manager and thus one cannot select it on the next boot. Before rebooting, it's advisable to use MCC / Initialization / Configure graphical login. Also, the sound was not working: KDE only saw a "fake output" (I'm reading in Portuguese the word "fictitious") while MCC correctly recognized the Alsa sound with Pulseaudio activated. I select the "Stereo input+mono recording" profile and everything worked, even as I return to the original setting ("Analog duplex"). Go figure... That's it. For now, maybe a note for KDE could go into the Errata, just like I did for Mate. These tests are somewhat extreme as people usually know what DE they want from the start. I'm one of those guys who want to try new WMs and DEs in the search of the perfect interface... OTOH, a lot of Linux users might behave the same way...
It's bug 16065, comment #24. The link in the comment above is wrong.
Added a note for KDE -- similar to Mate's.
Added a note to Errata, I mean.
(In reply to Renato Dali from comment #21) ... > > I cannot select the following packages (select twice to know what is the > problem): > > *task-kde4-minimal, because of conflict with phonon-gstreamer > This is probably because phonon-gstreamer-common was missing in classical installer iso -> bug 16025 . This is already fixed for final iso by http://gitweb.mageia.org/software/build-system/bcd/commit/?id=e911b649af61bb073c34eba2f8b756fc28a3347f I've just double-checked that phonon-gstreamer-common is now available on i586 and x86_64 DVD final iso.
CC: (none) => lmenut
Thanks for the clarification, Luc.
Now, i think problems for both Mate per comment #20 and KDE per comment #25 should be fixed. Close this bug report for now?
Attila, I don't know, there are pros and cons. Maybe this is now a release decision (i.e. not for me). Thanks again everyone for the dedication.
I tested again after Mageia 5 release and this bug does not happen anymore. Mate was installed from DVD without online repos over a KDE+Xfce+LXDE previous installation. KDE was installed on a previous minimally installed Mageia 5 (i.e. just IceWM). Some things must be done after installation -- e.g. change the display manager with drakconf to KDM. Apparently, possibly as part of th4e final release, someone already had removed the respective Errata entries. Therefore I'm closing this bug as FIXED. Congratulations on the release of version 5, which brought a lot of additional difficulties. Thanks for a well-done work.
Status: NEW => RESOLVEDResolution: (none) => FIXED