1) After booting and first login, Maté starts without usual window controls in each window displayed. 2) As well, a shell application programmed to start on login does not start. 3) If a new window is opened, they appear in the top left corner, overwriting the top panel, and with the usual window controls. 4) This ALWAYS occurs after reboot. 5) The installation (MGA5) is fully updated. Workaround : If one logs out, then logs back in without rebooting, the usual window controls are displayed. (All of the above mentioned symptoms no longer occur.) Note that waiting for a while (a half hour or more) before first login does not change the symptoms. If one logs into XFCE instead of Maté, this problem does not occur. (There are other problems without evident workarounds, such as not being able to log out without reboot.) This problem is new with MGA5. I suspect that it may be a race condition related to systemd ?
CC: (none) => mageia, tarakbumba
point (3) above s/with/without/ I think I have found the factor related to the cause. (approximate translation from french) Under menu system::preferences::applications_on_start there was the entry "Maximus Window Management" which is set to invoke "mate-maximus" However mate-maximus doesn't (seem to) exist in Mageia 5. So I unchecked "Maximus Window Management", and added the entry "marco" to invoke marco, the window manager for Maté in Mageia 5. Now window management in Maté works correctly on boot. A little surprised that this bug wasn't already reported. Isn't anyone else using Maté in Mageia 5 (not Cauldron) ?
Summary: Maté starts without window controls => Maté starts without window controls in MGA5 (probable cause found)Source RPM: not starting: marco-1.8.2-2.mga5.src.rpm ... maybe related: systemd-217-11.mga5.src.rpm => not starting: marco-1.8.2-2.mga5.src.rpm ... probably related: mate-control-center-1.8.3-3.mga5.src.rpm
Sorry for the late reply. mate-maximus is provided by mate-netbook package along with it's autostart desktop file. You probably installed mate-netbook by mistake. Would you mind to query installed rpms for mate-netbook? If it is installed, i think probably, uninstalling would fixes this issue for you. Note that task-mate or task-mate-minimal or other mate packages don't require/depend on this package.
You were right, mate-netbook was installed. It would help avoid this situation if the description indicated that it was a alternative to marco. However uninstalling mate-netbook did not remove mate-maximus from the startup preferences, as should have happened. (Since mate-maximus would no longer be available, it would just be messy, causing no real harm.) Since mate-maximus interferes with using marco, shouldn't there be a "conflict" with marco, and mate-netbook having a "provide" of marco (or the equivalent) ? That way one can't accidentally have both installed.
(In reply to andré blais from comment #3) > You were right, mate-netbook was installed. > It would help avoid this situation if the description indicated that it was > a alternative to marco. > > However uninstalling mate-netbook did not remove mate-maximus from the > startup preferences, as should have happened. (Since mate-maximus would no > longer be available, it would just be messy, causing no real harm.) > > Since mate-maximus interferes with using marco, shouldn't there be a > "conflict" with marco, and mate-netbook having a "provide" of marco (or the > equivalent) ? > That way one can't accidentally have both installed. mate-netbook or mate-maximus is not an alternative to marco; it is just window management tool that users: * Allows you to set basic rules for a window type, such as maximise|undecorate * Allows exceptions to the rules, based on string matching for window name and window class. * Allows 'reversing' of rules when the user manually changes something: * Re-decorates windows on un-maximise. So, it still uses marco for these operations. I can not use provides for this. Also, this package is not part of task-mate or task-mate-minimal. A user should explicitly install mate-netbook. But, after uninstallation there shouldn't be any leftover autostart desktop file. Would you mind to check if there is a /etc/xdg/autostart/mate-maximus-autostart.desktop file?
(In reply to Atilla ÃNTAÅ from comment #4) ... > > mate-netbook or mate-maximus is not an alternative to marco; it is just > window management tool that users: > > * Allows you to set basic rules for a window type, such as > maximise|undecorate > * Allows exceptions to the rules, based on string matching for window name > and window class. > * Allows 'reversing' of rules when the user manually changes something: > * Re-decorates windows on un-maximise. > > So, it still uses marco for these operations. I can not use provides for > this. Also, this package is not part of task-mate or task-mate-minimal. A > user should explicitly install mate-netbook. Given all that, why would the default setting cause a problem ? I had not in any way configured mate-netbook, just installed it. > But, after uninstallation there shouldn't be any leftover autostart desktop > file. Would you mind to check if there is a > /etc/xdg/autostart/mate-maximus-autostart.desktop file? No, that file is not installed. But the corresponding entry under menu:system:preferences:startup_applications had remained in place, until I explicitly deleted it.
What should be done with this bug report?
CC: mageia => marja11Assignee: bugsquad => tarakbumba
I think this one is invalid. Mate-netbook doesn't installed by default and if one installs it it should be activated to run.Last comment from reporter indicates that user activated it and there is a user setting remains in ~/.config/autostarts folder even mate-netbook is uninstalled. I'm closing this report as invalid now. Feel free to reopen if this occurs on clean installs.
Status: NEW => RESOLVEDResolution: (none) => INVALID