Application folder ошибка

Перейти к контенту

const checkIsInApplicationsFolder = () => {
    if (!app.isInApplicationsFolder()) {
        log.error('App has been run not from Application folder');
        dialog.showMessageBox({
            type: 'question',
            message: i18n.__('folder_check_dialog_message.message'),
            detail: i18n.__('folder_check_dialog_detail.message'),
            buttons: [i18n.__('folder_check_dialog_quit.message'), i18n.__('folder_check_dialog_move.message')],
            defaultId: 1,
        }).then((result) => {
            if (result.response === 1) {
                try {
                    const successfullyMoved = app.moveToApplicationsFolder();
                    if (successfullyMoved) {
                        log.warn('App was successfully moved to Applications folder');
                    }
                } catch (error) {
                    log.error(`Error moving App to Application folder: ${error.message}`);
                }
            } else {
                log.info('Force quit application');
                app.exit();
            }
        }).catch((error) => {
            log.error(`Error moving App to Application folder: ${error.message}`);
        });
    }
};

find "/Applications/iTerm.app" -exec xattr -r -d com.apple.quarantine {} ;

find "/Applications/iTerm.app" -exec xattr -r -d com.apple.quarantine {} ;

I changed the folder tree of my CI app on Cpanel from the following path below but i got this error:

Your application folder path does not appear to be set correctly. Please open the following file and correct this: index.php

Previous Folder Structure:

root
 application
 public_html
   site_folder
     system
    .htaccess

Current Folder Structure:

root 
  public_html
    site_folder
      application
      system
     .htaccess

index.php

define('ENVIRONMENT', isset($_SERVER['CI_ENV']) ? $_SERVER['CI_ENV'] : 'development');

switch (ENVIRONMENT)

{
case ‘development’:
error_reporting(-1);
ini_set(‘display_errors’, 1);
break;

case 'testing':
case 'production':
    ini_set('display_errors', 0);
    if (version_compare(PHP_VERSION, '7.2', '>='))
    {
        error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_USER_NOTICE & ~E_USER_DEPRECATED);
    }
    else
    {
        error_reporting(E_ALL & ~E_NOTICE & ~E_STRICT & ~E_USER_NOTICE);
    }
break;

default:
    header('HTTP/1.1 503 Service Unavailable.', TRUE, 503);
    echo 'The application environment is not set correctly.';
    exit(1); // EXIT_ERROR

}

$system_path = 'system';

$application_folder = 'application';

$view_folder = '';

    if (defined('STDIN'))
{
    chdir(dirname(__FILE__));
}

if (($_temp = realpath($system_path)) !== FALSE)
{
    $system_path = $_temp.DIRECTORY_SEPARATOR;
}
else
{
    // Ensure there's a trailing slash
    $system_path = strtr(
        rtrim($system_path, '/\'),
        '/\',
        DIRECTORY_SEPARATOR.DIRECTORY_SEPARATOR
    ).DIRECTORY_SEPARATOR;
}

// Is the system path correct?
if ( ! is_dir($system_path))
{
    header('HTTP/1.1 503 Service Unavailable.', TRUE, 503);
    echo 'Your system folder path does not appear to be set correctly. Please open the following file and correct this: '.pathinfo(__FILE__, PATHINFO_BASENAME);
    exit(3); // EXIT_CONFIG
}

    // The name of THIS file
define('SELF', pathinfo(__FILE__, PATHINFO_BASENAME));

// Path to the system directory
define('BASEPATH', $system_path);

// Path to the front controller (this file) directory
define('FCPATH', dirname(__FILE__).DIRECTORY_SEPARATOR);

// Name of the "system" directory
define('SYSDIR', basename(BASEPATH));

// The path to the "application" directory
if (is_dir($application_folder))
{
    if (($_temp = realpath($application_folder)) !== FALSE)
    {
        $application_folder = $_temp;
    }
    else
    {
        $application_folder = strtr(
            rtrim($application_folder, '/\'),
            '/\',
            DIRECTORY_SEPARATOR.DIRECTORY_SEPARATOR
        );
    }
}
elseif (is_dir(BASEPATH.$application_folder.DIRECTORY_SEPARATOR))
{
    $application_folder = BASEPATH.strtr(
        trim($application_folder, '/\'),
        '/\',
        DIRECTORY_SEPARATOR.DIRECTORY_SEPARATOR
    );
}
else
{
    header('HTTP/1.1 503 Service Unavailable.', TRUE, 503);
    echo 'Your application folder path does not appear to be set correctly. Please open the following file and correct this: '.SELF;
    exit(3); // EXIT_CONFIG
}

define('APPPATH', $application_folder.DIRECTORY_SEPARATOR);

// The path to the "views" directory
if ( ! isset($view_folder[0]) && is_dir(APPPATH.'views'.DIRECTORY_SEPARATOR))
{
    $view_folder = APPPATH.'views';
}
elseif (is_dir($view_folder))
{
    if (($_temp = realpath($view_folder)) !== FALSE)
    {
        $view_folder = $_temp;
    }
    else
    {
        $view_folder = strtr(
            rtrim($view_folder, '/\'),
            '/\',
            DIRECTORY_SEPARATOR.DIRECTORY_SEPARATOR
        );
    }
}
elseif (is_dir(APPPATH.$view_folder.DIRECTORY_SEPARATOR))
{
    $view_folder = APPPATH.strtr(
        trim($view_folder, '/\'),
        '/\',
        DIRECTORY_SEPARATOR.DIRECTORY_SEPARATOR
    );
}
else
{
    header('HTTP/1.1 503 Service Unavailable.', TRUE, 503);
    echo 'Your view folder path does not appear to be set correctly. Please open the following file and correct this: '.SELF;
    exit(3); // EXIT_CONFIG
}

define('VIEWPATH', $view_folder.DIRECTORY_SEPARATOR);

require_once BASEPATH.'core/CodeIgniter.php';

.htaccess

RewriteEngine on
RewriteCond $1 !^(index.php|assets|robots.txt)
RewriteRule ^(.*)$ index.php/$1 [L]

[x] I have checked the issue tracker if my question or bug has already been fixed or answered in another (possibly closed) issue.

• TranslucentTB version: 7.0.0.0
• Windows build number: 18362.418
• Steps to reproduce: Open TranslucentTB AFTER it has stopped working from startup.
• Expected results: the app should open and work
• Actual results: these error messages appear
  
• Other:

I first set the app to run on startup, like this it starts without any issues and keeps working for a certain amount of time.

Then i will notice that the taskbar goes back to its default color which indicates the app crashed.

I check task manager and it is indeed still running
(If I now open another instance of the app and it creates another instance in the task manager but the taskbar does not change whatsoever)

I end the instance forcefully and then reopen the app.

the error messages appear and the app does NOT open or show an instance in the task manager.

I’ve tried uninstalling, reinstalling, windows app, github .exe release, and nothing seems to help.
The one thing that changes is if i use the github .exe it will NOT throw these error messages at me after trying to reopen the app.

Vuze (previously Azureus) is one of the popular BitTorrent clients out there. It is extremely customizable, provides VPN support, has robust settings and options for ultimate torrent control, and also has remote control ability via the web or mobile app.

I have recently installed it on my Ubuntu 18.10 LTS PC and found some concerns with the settings which I will be discussing in this article.

Before heading to the issue I faced, let me quickly put together steps on how to install the program on your Ubuntu PC.

Installing Vuze BitTorrent Client

Vuze is no longer available in Ubuntu repository, but the good news is it’s is available as a Snap Store app.

Step 1) Click “Activities” and launch “Ubuntu Software”.

Step 2) Search for “Vuze” in the Ubuntu Software search box.

Step 3) Click “Install”.

Step 4) Enter root password when you see the prompt.

That’s it!

The Error… “Can’t write to the Application Folder”.

After installing Vuze, you can launch it from Activities search box or from the Applications menu. First time launch will take some time. In a slow system, it could as much as 30 seconds! So be patient.

After the program opens, you may probably see a pop-up saying “Can’t write to Application Folder. The folder “/snap/vuze-vs/3/opt/vuze” is not writable. This will prevent future software updates from being applied”.

This error message definitely looks scary as it’s apparent that future updates will not progress successfully. Evidently, we must fix it to stay updated.

Thankfully, the error message is clear and looks like it’s only an access issue. All we have to do is give necessary write permissions to the concerned directory and everything should be good to go. Here are the complete steps:

Step 1) Launch ‘Terminal”. You can use Ctrl+Alt+T shortcut in Ubuntu.

Step 2) Enter the following command and press enter.

Beginner’s tip: chmod command in Linux is used to set permissions to the files and folders. -R is used to indicate recursive action, i.e. include objects in subdirectories. -v is verbose for displaying the objects.

sudo chmod 775 -Rv /snap/vuze-vs/3/opt/vuze

Step 3) Pay attention to the Terminal and enter the root password when you see the prompt.

Step 4) You should see the lengthy process in the Terminal including some failed objects. It is completely normal. The main directories which are needed should be processed successfully in the end.

Next time when you launch Vuze, you should not see the warning pop-up anymore.

Доброго времени суток. Господа, такая проблема. Стояла Windows 10, в какой-то момент полетели куча программ Sony Vegas, Photoshop и т.д. Просто перестали открываться. Перестали работать некоторые игры, тоже перестали открываться. Проблему выявил за счёт одной игры на движке Unity. При её открытии появлялась ошибка
Application folder:
D:/Games/SUBNAU~1
There should be ‘SUBNAU~3_Data’
folder next to the executable

Эта игра работала ещё день назад. А сейчас не может найти папку «Data» в директории. Но стоило переименовать папку «Subnautica_Data» в «SUBNAU~3_Data» как всё заработало. В ошибках не рабочих программ была та же проблема, они требовали такие пути «PHOTO~3.exe».

Думал конец системе, переустановил, поставил семёрку. Но проблема не решилась, даже с учётом того что я полностью форматировал раздел и ставил чистую ОСь. Сейчас не работают браузеры, в диспетчере задач в названии приложений та же самая история, в конце «тильда+цифра от одного до трёх.exe».
Почему это происходит? Хард доживает своё?

Dec 14, 2017

It’s apparently a foolish idea to login as root from a file manager on Plasma KDE.

This was exactly what caused a number of problems, and among them, most notably, that I could not get past the login screen.

Of course, little did it matter that I installed any of the other display managers available and removed the current in use from the command line. I was still unable to get past the login screen.

In other words, it wasn’t just the usual login failed which indicates the wrong username and/or password. This was exactly the opposite, as after inputting the password for the system, since login automatically was disabled, the screen would fall back as if it loading the kernel again, and then without further ado, back into the login screen.

This feedback loop process was endless. I couldn’t but scourge on Google for some sort of information regarding the issue.

One of the first queries to Google was with the terms plasma kde fails to startx, although I knew that the last element of the query was not the most accurate. For one, because the X server was somehow running, or else how could I have a login screen in the first place. But almost unsurprisingly, the first result from Google was from the Arch Linux forum entitled Cannot start plasma 5.

I tried to follow one of the recommendations and modify the last line to

 exec startkde

but it made no difference.

Perhaps on other desktop environments the change on .xinitrc was a success, but at least on Manjaro Plasma KDE, all of it was failing and I was not able to get past the login screen.

For example, the suggestion to modify the .xinitrc on the xfce desktop environment have proven to succeed without any major problem.

See for example Can’t get past the login screen, where modifying the .xinitrc was more than enough to get it started.

At this point it was futile to modify any further the .xinitrc initialization file when moments before I had restarted the system, an error related to Plasma KDE had popped up on the screen:

A couple more errors from the main file manager Dolphin showed for example the following:

And also

At this point, after the infamous error with the kio_applicationsrc, I very well knew that the culprit of it all occurred when trying to login as root to Plasma from the Dolphin file manager.

Later on, after giving up the have Manjaro KDE running on the system, I found a few posts that spoke about logging in as root on the Plasma environment.

On the same post that for example was highlighted earlier, there is useful information as why running as root as KDE is altogether discouraged: