StartAsRoot for FileCase

Submitted by Schturman on Wed, 2019/02/06 - 11:24

Rating:

Your rating: None Average: 5 (3 votes)

It will create icon to start FileCase app as root. FileCase app should be installed on your device...

v0.1-4
- Changes in SPEC file. Obsoletes changed to Conflicts.

v0.1-3
- Should fix problem with root access.

v0.1-2
- Tablet version.

Beware, use it on your own risk !!!

Donation are welcome :)

Screenshots:

Keywords:

Application versions:

Attachment	Size	Date
filecaseroot-0.1-2.armv7hl.rpm	10.56 KB	13/10/2015 - 00:24
filecaseroot-0.1-2.i486.rpm	10.54 KB	07/02/2019 - 04:41
filecaseroot-0.1-3.i486.rpm	10.86 KB	26/07/2017 - 03:08
filecaseroot-0.1-3.armv7hl.rpm	10.84 KB	26/07/2017 - 03:08
filecaseroot-0.1-4.i486.rpm	15.43 KB	06/02/2019 - 11:23
filecaseroot-0.1-4.armv7hl.rpm	15.16 KB	06/02/2019 - 11:23

Changelog:

- Changes in SPEC file. Obsoletes changed to Conflicts.

Comments

Schturman

Fri, 2017/10/13 - 15:10

Permalink

Thanks... You mean about this problem (terminal should be opened) after you setup pass for root ?

objectifnul

Fri, 2017/10/13 - 19:37

Permalink

Actually the issue is not related with terminal. Probably a matter of delays and/or conflicting background actions being performed by the filesystem. For example, at this moment cargodock has root privileges while filebrowser hasn't. Weird.

--EDIT-- Obviously, the SailfishX file system is not btrfs, with little technical information available, and its behaviour is far from predictable. Currently, filebrowser, cargodock, filetug and filecase in 'startasroot' mode have a completely erratic behaviour with about 30% of occurrences with root privilege successfully granted.

Schturman

Fri, 2017/10/13 - 22:37

Permalink

Thanks for report... I don't know how to fix it... For C, 1 and Tablet - I don't have any problem....

objectifnul

Sat, 2017/10/14 - 18:37

Permalink

Thx for trying. I think there is nothing you can do on your side, this appears to be a SailfishX issue so it's up to Jolla to address it (probably if and when they implement BTRFS like in Jolla One). In the mean time, what I do is this:

(1) open CargoDock in root mode, which will most probably fail (black background, not red).

(2) close it and wait for about one minute.

(3) open it again, check if the screen background is red.

(4) if yes, you are likely to launch other 'rootable' file managers (filebrowser, filetug, filecase) successfully.

Schturman

Fri, 2017/10/13 - 16:26

Permalink

hmmm... ok...

Schturman

Thu, 2017/10/12 - 00:54

Permalink

try to run it as root:

su -c 'invoker --type=silica-qt5 -n /usr/bin/filecase'

or just:

invoker --type=silica-qt5 -n /usr/bin/filecase

The source, just extract content from rpm file and do what you want...

Sailbook

Thu, 2017/10/12 - 07:45

Permalink

[root@Sailfish nemo]# invoker --type=silica-qt5 -n /usr/bin/filecase
invoker: Invoking execution: '/usr/bin/filecase'
invoker: error: Failed to initiate connect on the socket for type silica-qt5.
invoker: warning: Booster silica-qt5 is not available. Falling back to generic.
invoker: error: Failed to initiate connect on the socket for type generic.
invoker: warning: Can't try fall back to generic, already using it
invoker: warning: Connection with launcher process is broken.
invoker: error: Start application /usr/bin/filecase as a binary executable without launcher...
[root@Sailfish nemo]# error: XDG_RUNTIME_DIR not set in the environment.
[C] unknown:0 - Failed to create display (No such file or directory)

The command su -c 'invoker --type=silica-qt5 -n /usr/bin/filecase' dont do nothing.

About the source when you extract the rpm, you dont have the complete source code only a part oif it.