Thank you for reporting this.
[It is not necessary to install both 'task-gnome' & 'task-gnome-minimal', the  former includes the latter. No matter.]

For 'gvfs-google', I do not think this should be a requirement of Gnome. If you want to use it, it is quite reasonable to have to install it. It is a specialised application.

For the real bug, can you describe in what circumstance Nautilus crashes after installing gvfs-google (before running the binary)?
Do you have to specifically run the binary before each use of the the remote mount?

Source RPM: (none) => gvfs-1.40.1-4.1.mga7.src.rpm, task-gnome-3.32.0-2.mga7.src.rpm
CC: (none) => lewyssmith

No i canot, because it crash only once, the first try, but online account is depandancy of task gnome also nautilus, after configuring my Google account, file is check by défaut and imediatly we see the e-mail adress in left panel but unable to mount it, with no debug error, for an lambda user it is aweason, also, all the gvfsq are installed execpt the Google one.
Realy, the Best way is to include it to simplify and clarify....

Thank you for the extra information. I have been digging around this. The key is, I think:
> all the gvfsq are installed except the Google one
$ urpmq --requires-recursive gvfs | grep gvfs
 gvfs
 gvfs-archive
 gvfs-fuse
 gvfs-gphoto2
 gvfs-iphone
 gvfs-mtp
 gvfs-smb
$ urpmq --requires-recursive task-gnome-minimal | grep gvfs
gives the same list +
 gvfs-goa
which is the whole available set *except* (as you bug) 'gvfs-google'. Which looks more like an oversight than intentional; and more likely 'gvfs' than 'task-gnome-minimal'.

It does not explain your one-off manoeuvre (comment 0) to make it work the first time. Perhaps that necessitated a logout at least to take effect.

Assigning to the gnome group.

CC: lewyssmith => (none)
Summary: bad dependancy of task-gnome => gvfs-google dependancy missing from gvfs or task-gnome-minimal
Assignee: bugsquad => gnome

I'd say it intentional.

som users considers google (and others) "public cloud" services not pro freedom as they do all thy can to "know everything about you" so it should stay as a "if you want it, install it"

Gnome does not need it to work properly in normal use cases...

CC: (none) => tmb

I understand, but, by défaut, the online account, then Google is here, so, because one advantage of Linux is the choice, it is critical to have no info, no easy way to know gvfs-google, i m using mandrake since the begin,if you search google rpm you will have all the Google font, to conclude, i was just luky to discover this missing rpm, because of that i used gdriveocamlfuse since long time.
Installing gvfsd-google, really mean is activated and spy or it need, wait the user use it ?

Looking at the spec history it seems Google was once split off by wally. He also removed the goa Recommends. A bit weird. I don't really see a problem of having Recommends.

CC: (none) => olav

There is no problem if you're using Gnome. But we have also other DEs using gvfs that don't need/use goa.

CC: (none) => jani.valimaa

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

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