Android Studio – apps not allowed permissions to save files, can’t change either with Eiciel app

I’ve tried what seems to be everything. Changing permissions in the home folder to my user ownership. Installing the manager Eiciel it won’t let me allow any apps to do anything since everything belongs to root! I can’t do anything except via sudo and a terminal.

And I can’t find a way to login to Ubuntu Studio as sudo or any other way to grant permissions. How does one fix this issue?

I tried adding my username user to visudo, it seems to save files now but the permissions app Eiciel still won’t allow me to add permissions for any users to any apps. Geany located in /usr/bin/geany found with: locate -e geany from the root directory. Tips?

https://www.linode.com/docs/tools-reference/linux-users-and-groups/

enter image description here

Finding Source of Exception: Attribute is Not Allowed

After updating to a new version of Magento, our store is giving us the following exception:

1 exception(s): Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'meta', attribute 'property': The attribute 'property' is not allowed. Line: 993   Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'meta', attribute 'property': The attribute 'property' is not allowed. Line: 993  <pre>#1 Magento\Framework\Config\Dom->__construct() called at [vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php:111] #2 Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject() called at [vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php:66] #3 Magento\Framework\ObjectManager\Factory\Dynamic\Developer->create() called at [vendor/magento/framework/ObjectManager/ObjectManager.php:56] #4 Magento\Framework\ObjectManager\ObjectManager->create() called at [vendor/magento/framework/Config/DomFactory.php:42] #5 Magento\Framework\Config\DomFactory->createDom() called at [vendor/magento/framework/View/Model/Layout/Update/Validator.php:141] #6 Magento\Framework\View\Model\Layout\Update\Validator->isValid() called at [vendor/magento/framework/View/Model/Layout/Merge.php:479] #7 Magento\Framework\View\Model\Layout\Merge->_validateMergedLayout() called at [vendor/magento/framework/View/Model/Layout/Merge.php:455] #8 Magento\Framework\View\Model\Layout\Merge->load() called at [generated/code/Magento/Framework/View/Model/Layout/Merge/Interceptor.php:193] #9 Magento\Framework\View\Model\Layout\Merge\Interceptor->load() called at [vendor/magento/framework/View/Layout/Builder.php:86] #10 Magento\Framework\View\Layout\Builder->loadLayoutUpdates() called at [vendor/magento/framework/View/Layout/Builder.php:63] #11 Magento\Framework\View\Layout\Builder->build() called at [vendor/magento/framework/View/Layout.php:253] #12 Magento\Framework\View\Layout->build() called at [vendor/magento/framework/View/Layout.php:875] #13 Magento\Framework\View\Layout->getBlock() called at [generated/code/Magento/Framework/View/Layout/Interceptor.php:414] #14 Magento\Framework\View\Layout\Interceptor->getBlock() called at [vendor/magento/module-cms/Helper/Page.php:171] #15 Magento\Cms\Helper\Page->prepareResultPage() called at [vendor/magento/module-cms/Controller/Index/Index.php:68] #16 Magento\Cms\Controller\Index\Index->execute() called at [generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php:24] #17 Magento\Cms\Controller\Index\Index\Interceptor->execute() called at [vendor/magento/framework/App/Action/Action.php:107] #18 Magento\Framework\App\Action\Action->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58] #19 Magento\Cms\Controller\Index\Index\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138] #20 Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}() called at [app/code/Anowave/Ec/Plugin/App/Action/Context.php:148] #21 Anowave\Ec\Plugin\App\Action\Context->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135] #22 Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153] #23 Magento\Cms\Controller\Index\Index\Interceptor->___callPlugins() called at [generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php:39] #24 Magento\Cms\Controller\Index\Index\Interceptor->dispatch() called at [vendor/magento/framework/App/FrontController.php:55] #25 Magento\Framework\App\FrontController->dispatch() called at [vendor/magento/framework/Interception/Interceptor.php:58] #26 Magento\Framework\App\FrontController\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138] #27 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php:94] #28 Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135] #29 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:69] #30 Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch() called at [vendor/magento/framework/Interception/Interceptor.php:135] #31 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153] #32 Magento\Framework\App\FrontController\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:26] #33 Magento\Framework\App\FrontController\Interceptor->dispatch() called at [vendor/magento/framework/App/Http.php:136] #34 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:24] #35 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:257] #36 Magento\Framework\App\Bootstrap->run() called at [pub/index.php:37] </pre> 

I understand that I should be looking for a meta tag with a property attribute, but I’ve been unable to locate it in the codebase. Is there a way for me to hone in on the source of this exception?

‘Property PreLaunchTask is not allowed’ en launch.json (Visual Studio Code)

No puedo añadir la línea "PreLaunchTask": "Compilar", en el archivo launch.json. Mi intención es que al comenzar la depuración se compile el archivo ejecutando la tarea “Compilar”.

El archivo launch.json es el siguiente:

{     // Use IntelliSense para saber los atributos posibles.     // Mantenga el puntero para ver las descripciones de los existentes atributos      // Para más información, visite: https://go.microsoft.com/fwlink/?linkid=830387     "version": "0.2.0",     "configurations": [         {             "name": "Debug",             "type": "cppdbg",             "request": "launch",             "program": "$  {workspaceFolder}/$  {fileBasenameNoExtension}.exe",             "args": [],             "stopAtEntry": true,             "cwd": "$  {workspaceFolder}",             "environment": [],             "externalConsole": true,             "MIMode": "gdb",             "miDebuggerPath": "D:\Programas\MinGW\bin\gdb.exe",             "setupCommands": [                 {                     "description": "Enable pretty-printing for gdb",                     "text": "-enable-pretty-printing",                     "ignoreFailures": true                 }             ],             "PreLaunchTask": "Compilar", //<----------------------         }     ] } 

CIS 2.3.4.1 (L1) Ensure ‘Devices: Allowed to format and eject removable media’ is set to ‘Administrators and Interactive Users’

I am implementing CIS on Windows 10 1803 and I cannot work out this control.


Description: This policy setting determines who is allowed to format and eject removable NTFS media. You can use this policy setting to prevent unauthorized users from removing data on one computer to access it on another computer on which they have local administrator privileges. The recommended state for this setting is: Administrators and Interactive Users.

Rationale: Users may be able to move data on removable disks to a different computer where they have administrative privileges. The user could then take ownership of any file, grant themselves full control, and view or modify any file. The fact that most removable storage devices will eject media by pressing a mechanical button diminishes the advantage of this policy setting.


For a start, I have never known anyone not be allowed to eject and format removable media (assuming hard disks, usb drives etc).

But I am even less sure on why the control is asking me to set it to ‘Administrators and Interactive Users’ when the default is just ‘Administrators’.

CSC CIS Windows 1803: The recommended state for this setting is: Administrators and Interactive Users. The default value is Administrators only. Administrators and Interactive Users will be able to format and eject removable NTFS media.

docs.microsoft: It is advisable to set Allowed to format and eject removable media to Administrators. Only administrators will be able to eject NTFS-formatted removable media.

Would this setting also upset software that manages USB devices, such as Checkpoint Removable Media Encryption?

(Magento\Framework\Config\Dom\ValidationException): Element ‘referenceBlock’, attribute ‘class’: The attribute ‘class’ is not allowed

I have this problem and I can’t locate where the problem is :

1 exception(s): Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'referenceBlock', attribute 'class': The attribute 'class' is not allowed. Line: 1124 

This problem occurs as a connected customer, when I try to access the invoice for a test order.

Here is what I tried to do to solve the problem by following a lot of topics on this forum:

  • setup:di:compile
  • Delete the content of /pub/static/frontend
  • Deploy static content

Nothing works.

Note that I searched my XML for a referenceBlock with a class attribute, but I didn’t find anything. Maybe I’m not looking in the right place?

The directories scanned to find the error: – /app/code – /app/design

Can someone explain to me how to locate this error more precisely? Or help me solve it?

Magento version 2.3.1

Thank you in advance.

Magento 2.3.2 Error XML declaration allowed only at the start of the document

I need for a programm to (webwinkelfacturen.nl) to read my taxrates so I can be pushed in an accountingsystem. But I am getting this error when I want to call domainname/ndex.php/rest/V1/taxRates I am getting this error:

This page contains the following errors:
error on line 2 at column 6: XML declaration allowed only at the start of the document
Below is a rendering of the page up to the first error.

The programm is using this to get the taxrates:

https://www.bakmina.com/index.php/rest/V1/taxRates/search?searchCriteria%5Bpage_size%5D=100

And that gives the same error. What is this ? And how can I FIX it ?

Show to, from field in results in Gmail (using 3rd party Software is allowed)

I am trying to get rid of duplicate accounts on some sites. Problem is I don’t remember the E-Mail Id I use to register since I use catch-all with GSuite.

I want to see all the E-Mail I have registered from a site along with the to address, it was delivered to. I don’t want to open each E-Mail manually, so looking for some way to save time.

I am open to use 3rd party Software (as long as it is reputable)

Host ‘XXX.XXX.XXX.XXX’ is not allowed to connect to this MySQL server

I am getting a MySql.Data.MySqlClient.MySqlException (0x80004005) with message Host ‘XXX.XXX.XXX.XXX’ is not allowed to connect to this MySQL server, where IP == Google.cloud IP. I do not know if there is a problem because I change the mysql database password and some how Google Cloud stayed with the old. My C# code for connecting Dialogflow Agent with a mysql database through Google Cloud App Engine and a asp.net core 2.1 work fine with localhost credentials but give that 0x80004005 error when I change the connection string with my GoDaddy mysql database credentials. If I give access to this certain host through GoDaddy’s cPanel and retry with my agent returns the same error with different Host IP.

The errors have been collected through Google Cloud Logging >selected resource GEA application (https://console.cloud.google.com/logs/viewer?)

Script allowed to launch without sudo password works in console, but not in .desktop file

I have set in /etc/sudoers.d a script to be launched without sudo password. It works from bash, but it does not work if invoked from a .desktop file. Why?

Furthermore, this works with sudo, not with pkexec. It seems pkexec does not honor the sudoers rules. Is this a know bug or is intentional?