SDK Read-only file system errors

Applications
1
  • umask 022
  • cd /home/mwa/src/sailfish/build-allthenews-SailfishOS_5_0_0_62_aarch64_in_Sailfish_SDK_Build_Engine-Debug
  • flock /home/mersdk/.mb2.lock.lock flock /home/mersdk/.mb2.lock ln -f /home/mersdk/.mb2.lock.9PO /home/mersdk/.mb2.lock
  • ‘[’ /home/deploy/installroot ‘!=’ / ‘]’
  • rm -rf /home/deploy/installroot
    ++ dirname /home/deploy/installroot
  • mkdir -p /home/deploy
  • mkdir /home/deploy/installroot
  • LANG=C
  • export LANG
  • unset DISPLAY
  • rm -rf /home/deploy/installroot
  • /usr/bin/make install DESTDIR=/home/deploy/installroot ‘INSTALL=/usr/bin/install -p’
    mkdir: cannot create directory ‘/usr/share/harbour-allthenews’: Read-only file system
    make: *** [Makefile:422: install_qm] Error 1

Trying to do some bug fixes and I’m getting this.

Anyone seen this before?

EDIT, I think I found it. I was being overly clever in the spec file. tsk, tsk, tsk.

2

Lemme guess: stupid qmake not respecting DESTDIR, insisting on INSTALL_ROOT?

Or was that cmake? I forget…

3

Ah, something like that :slight_smile: I had been dynamically generating icons on install with rsvg-convert. I decided to stop debugging that and fight with broken webviews instead :slight_smile: Or, maybe they are all broken/!??!!##

4

ah, @nephros It shames me to ask, but I’m confounded and confused. In an attempt to fix a webview i simply copied the functional one from tidings … In the (qml only) app I copied it to, it has that odd ‘split screen’ scrolling issue where the view spilts the container and the webpage cannot scroll. In tidings, the same qml, opened the same way, with the same parameters works without fail. Do you remember this one? I

The only thing I could think of was that tidings is compiled and brings something along that the qml only app does not. But I could not spot what that might be.

5

Hmmm.

Only thing that comes to mind is that WebviewPage and esp. WebviewFlickable do things re. focus and sizes.

Are the QMLs really the same? Not one using one of those types and the other does not?

6

I copied the one over the other, just to make sure.

It’s a Page { WebView {} } construct, but I did try a WebViewPage wrapper and also the the WebViewFlickable. All broken in the same way. I did look at the container Appwindow, too. i’m puzzled.

7

Oh and there’s also the thing with the PREFS_WRITTEN file. Afaik it is created at first launch, and some of the webengine tunables will not take effect later.

Try removing that for the nonworking version.

It is in ~/.local/share/org/app/__PREFS_WRITTEN__

1 Like
8

AH!!! I knew you would find it. I believe that’s the one. I’m pretty sure that’s the issue. Sigh. Completely forgot!

EDIT: yes, that was it. Sigh. Hours wasted. You rock, @nephros

9

I wonder if one could create another Sailjail permission file which hides that file but allows it to be created, and discatds it again when the sandbox terminates.

Would be useful for development.

1 Like