Multiple Installs leads to Not Authorized to Execute Application

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
[x] I have checked the Resources category (Resources Index)
[x] I have reviewed the Wiki for relevant information
[x] I have read the the Release Notes and Errata

OpenMandriva Lx version:

OpenMandriva Lx release 25.12 (ROME) Rolling for x86_64
Desktop environment: KDE

Description of the issue (screenshots if relevant):

I have Open Mandriva installed on an older PC, this PC has multiple hard drives, one is used for /home (sdb) and the other used for ā€œ/ā€ (sda). It took me multiple installs to get a stable(ish) OM Rolling install working on this hardware. For some reason attempting to install Rolling or Cooker directly failed (Rolling failed to load the OS, Cooker failed to properly install Grub). I tried multiple times on each and had no success. I wanted the Rolling release, or Cooker, to see how XLibre was going. In the end I had to install the Rock release, then right after install change the package channel to Rolling and update. I also cannot install the NVidia drivers for my graphics card as that will kill the OS as well. In the end it took me several days and more than a dozen attempts to get to this point.

Currently the computer boots, it loads some apps ok, however there are several apps that I cannot run. On my desktop the app ā€œinfo and resourcesā€ and ā€œsteamā€ both have orange exclamation marks, if I attempt to execute them I get a Warning popup: ā€œThis will start the program: Steamā€, and when I click Continue I have the error message ā€œYou are not authorized to execute this fileā€. However, if I attempt to open Steam from the menu I get a different message, with the title of ā€œqarmaā€ it states ā€œCouldn’t set up Steam data - please contact technical supportā€. For the ā€œinfo and resourcesā€ app if I attempt to open from the desktop app I get the same warnings as the steam app, but if I navigate to the app (in /usr/bin) I can open it without issue.

I had the same issue with OM-Welcome on the desktop (even though it opened ok when starting the computer), my attempt to fix was to delete the desktop icon and create a link to the app, I no longer have the fancy icon but it starts without issue this way.

My guess is that in the multiple installs my permissions have somehow become messed up. Note: I created the exact same user for this install as previous installs, so the home folder, userid, and user group are all the exact same from previous install.

Relevant informations (hardware involved, software version, logs or output…):

Operating System: OpenMandriva ROME 25.12
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-desktop-1omv2590 (64-bit)
Graphics Platform: X11
Processors: 8 Ɨ IntelĀ® Coreā„¢ i7 CPU 860 @ 2.80GHz
Memory: 12 GiB of RAM (11.7 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 750 Ti
Manufacturer: Dell Inc.
Product Name: Precision T1500
System Version: 00

Welcome back @MrScrith.

Is /home reused from previous installs of some other distro?

Two things to look at for this:

ROME iso problems (12/06/25)

What to do if there is a problem installing OMLx

Do an internet search of ā€˜Linux permissions’ without the tick marks and learn how to discover what permissions are and change them if needed. This is not that difficult. There can be a lot to do though because lots of things have their own permissions.

An alternative would be to start over with a fresh formatted /home. But I can not say from the information I have that that is for certain the problem just that it might be.

Two weeks ago this was a Windows computer, I copied off all files I wanted to save then wiped computer and made attempts to install rolling and cooker, eventually getting rock to install. I then setup second drive as /home and copied things over from my backups. I then tried installing nvidia drivers and killed the OS, I reinstalled several times attempting to make it work and failed. I also had issues switching from Rock to Rolling or from Rock to Cooker (package conflicts), so I had to play with uninstalling or manually installing packages to clear conflicts in order to get the upgrade to work.

Yes, the /home drive is from a previous install of Open Mandriva. I used the same user info (passwords and all) each time I attempted an install.

Then that should not be a problem. I can not help with nVidia, I don’t touch the stuff but there certainly are people that install nvidia drives for the latest nVidia hardware successfully. We do not have drivers for anything but the latest nVidia hardware. This is due to resources, like developer time, available and the fact the nVidia the corporation makes this difficult for Linux distros especially smaller ones to do.

Question: does the nouveau driver that is free and opensource not work for you? I believe this command would tell you if that is in use lsmod | grep video it will list a number of things look for the entry video.

That shows I am using the amdgpu driver for my AMD graphic chip. To list what your exact nvidia hardware is this command will show that lspci | grep VGA.

That shows my AMD graphic hardware.

That probably means your nVidia hardware is older and not supported by the latest nvidia driver which comes from nvidia.com. You mignt try getting a supported driver for your hardware here. They do have a Linux forum. There are other people in this forum that would know more about nVidia stuff than I do.

I can not say what a cause would be for your permissions issues. I can say this is not a common problem, lots of people install OMLx without such issues.

A possible way to trouble shoot this would be to reinstall with a fresh formatted /home partition and see if there are any permissions problems before adding files from the old Windows installation. If there are that would point to a possible corrupted .iso file download or a corrupted copy to installation media such as a usb flash drive. For example if people use Rufus to copy the installation image to flash drive that would cause problems unless Rufus was set to use dd to do the copy. Downloading with browser might lead to a corrupted download, this seems less likely though. This screen shot is from the ROME Release Notes:

Then add the files saved from the old Windows installation one at a time and see if any of these lead to such problems.

There is more information about this stuff in the Forum Resources section and the OM Wiki. If you have not read the Release Notes and Errata for ROME you should do so. For Cooker there is this. The Release Notes and Errata for ROME generally apply to Cooker as well. Rock has it’s own Release Notes and Errata, I am not sure what you are currently using.

IMO our documentation is not perfect or as well organized as it might be. We are a small all unpaid, volunteer, group so what we are able to do within those constraints is what we are able to do.

If you choose to install ROME at this time you need to follow this article. We hope to have these problems fixed soon with the next major ROME upgrade.

If you are using a card older than a GTX 1650, Rolling and newer are not going to work with the proprietary driver. nvidia has put it in Legacy for 59x and newer. This has been in a few posts on the forum already.

You will need to use nouveau or find a newer card.

Your other option is to use the .run file from nvidia, which we don’t support.

1 Like

Ok, I’ll stick with nouveau for now, funds are tight now so older computer and older card are the order of the day.

Unfortunately games suck with this driver, factorio was playable with win 10, but trying it out on OM with nouveau driver reduces it to a handful of frames per second.

I would suggest using your OM installation for a bit and get used to it first then you could try installing the .run (that is the file name) nvidia driver for your hardware. Instructions:

NVIDIA Driver Installation Quickstart Guide

or:

Installing the Latest NVIDIA Drivers From the .run File

Just a thought: I suggest new users, especially if new to Linux as well, always just install their OMLx system and get used to it for a week or two before doing much in the way of changing or customizing. One certainly can install a few things from the OM-Welcome application like preferred browser, ect. right after install.

Even if one is used to Linux you need to be aware the OMLx is different from any other Linux distro. We are unique. There are lots of things that are the same or similar across most Linux distros but there are things specific to the OM way of doing things.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.