1428626 - Lost profile on start Could not write session state file Object

Status: RESOLVED INVALID

(Toolkit :: Startup and Profile System, defect)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0
Build ID: 20180102224146

Steps to reproduce:

Maybe problems with file permissions when load profile.




Actual results:

See errors:

Could not write session state file  Object { operation: "open", path: "/home/wellington/.mozilla/firefox-t…", unixErrno: 13, stack: "", fileName: "(unknown module)", lineNumber: undefined }   SessionFile.jsm:396
Unix error 13 during operation open on file /home/wellington/.cache/.mozilla/firefox-trunk/v3uent20.23Set2017/startupCache/webext.sc.lz4 (Permissão negada)  DeferredTask.jsm:315
Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode”  browser.xul
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”  browser.xul
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.  SessionFile.jsm
getScreenshot error: Error: page-thumbnail:error  Screenshots.jsm:61
Content Security Policy: Ignoring ‘x-frame-options’ because of ‘frame-ancestors’ directive. (unknown)
Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively. (unknown)
TelemetryStopwatch: key "TELEMETRY_PENDING_LOAD_MS" was already initialized  TelemetryStopwatch.jsm:356
TelemetryStopwatch: requesting elapsed time for nonexisting stopwatch. Histogram: "TELEMETRY_PENDING_LOAD_MS", key: "null"  TelemetryStopwatch.jsm:377
TelemetryStopwatch: requesting elapsed time for nonexisting stopwatch. Histogram: "TELEMETRY_PENDING_LOAD_MS", key: "null"  TelemetryStopwatch.jsm:377
1515341759420	Toolkit.Telemetry	WARN	TelemetryStorage::_enforceArchiveQuota - Unable to find the size of ping d842b3da-148a-416c-bcc6-3368d8b766a1


Expected results:

No errors and profile loaded (no blank profile)

Comment 1

[Adrian Florinescu [:aflorinescu]]

Wellington, would you be kind enough to supplement your bug report with additional information? 
1. What Ubuntu version are you running? 
2. Is this Nightly first run? 
3. Do you have other Firefox versions installed? If yes, what is the status with those?
4. Is the profile you are using coming from another version? (for example, you have FF57 and with the same profile you have opened FF59?)
5. Does this happens for a new profile as well?
6. Is the user a restricted user? (for example - not an admin user?)
7. What do you understand by "No errors and profile loaded (no blank profile)"? - I would assume that the errors listed above are coming from the browser console, which would lead me to believe that the profile did load.

Comment 2

[Wellington Torrejais da Silva]

(In reply to Adrian Florinescu [:AdrianSV] PTO till 01/22 from comment #1)
> Wellington, would you be kind enough to supplement your bug report with
> additional information? 
> 1. What Ubuntu version are you running? 

Lubuntu 18 and Linux Mint 18.2 ( and others)
This problem occurring more at Lubuntu.

> 2. Is this Nightly first run? 

No.

> 3. Do you have other Firefox versions installed? If yes, what is the status
> with those?

I have. I use rarely.

> 4. Is the profile you are using coming from another version? (for example,
> you have FF57 and with the same profile you have opened FF59?)

Maybe. I think is the same.

> 5. Does this happens for a new profile as well?

Some times.

> 6. Is the user a restricted user? (for example - not an admin user?)

Restricted user. My user...

> 7. What do you understand by "No errors and profile loaded (no blank
> profile)"? - I would assume that the errors listed above are coming from the
> browser console, which would lead me to believe that the profile did load.

I think is a permission problem but I don't changed permission by me.
Sometimes I receive new profile like first open. And in this case
I need to configure everything again.

Yes I catch errors from terminal, Browser console and JS Console.

Thanks.

Comment 3

[Adrian Florinescu [:aflorinescu]]

I don't think this is a Firefox error, most likely it is a permissions fault. Could you please check the permissions for  "/home/wellington/.cache/.mozilla" and also check the permissions for the profile folder and Firefox folder as well?

The way to check permissions are either:
a) in UI mode, navigate to folder, then right click and permissions
b) console command, cd to folder and ls - la folder.  
        an output example would be something  like: 
               adrianflorinescu:~/Documents/FF$ ls -la Nightly/
               total 16
               drwxrwxr-x 4 adrianflorinescu adrianflorinescu 4096 ian  8 15:53 .
               drwxrwxr-x 8 adrianflorinescu adrianflorinescu 4096 ian 12 13:58 ..
               drwxrwxr-x 3 adrianflorinescu adrianflorinescu 4096 dec 27 17:16 nightly

Comment 4

[Wellington Torrejais da Silva]

(In reply to Adrian Florinescu [:AdrianSV] from comment #3)
> I don't think this is a Firefox error, most likely it is a permissions
> fault. Could you please check the permissions for 
> "/home/wellington/.cache/.mozilla" and also check the permissions for the
> profile folder and Firefox folder as well?
> 
> The way to check permissions are either:
> a) in UI mode, navigate to folder, then right click and permissions
> b) console command, cd to folder and ls - la folder.  
>         an output example would be something  like: 
>                adrianflorinescu:~/Documents/FF$ ls -la Nightly/
>                total 16
>                drwxrwxr-x 4 adrianflorinescu adrianflorinescu 4096 ian  8
> 15:53 .
>                drwxrwxr-x 8 adrianflorinescu adrianflorinescu 4096 ian 12
> 13:58 ..
>                drwxrwxr-x 3 adrianflorinescu adrianflorinescu 4096 dec 27
> 17:16 nightly

Hi,

Yes, It's a permission problem. I tried to change and worked.
But sometimes I got the the problem again.

It's possible to the browser auto-fix this type of problem? Because I don't know the real origin of the permission or owner change. :-(

What I should to do?

Thanks!

Comment 5

[Adrian Florinescu [:aflorinescu]]

(In reply to Wellington Torrejais da Silva from comment #4)

> Yes, It's a permission problem. I tried to change and worked.
Glad to hear your problem got solved by permissions change.

> But sometimes I got the the problem again.
I have no clue why the problem would reappear. Once you've set the w/r permission, they shouldn't regress. 

> It's possible to the browser auto-fix this type of problem? Because I don't
> know the real origin of the permission or owner change. :-(
The browser cannot "autofix" these kinds of problems, since the permissions deny come from user roles of the OS: that's how it's designed to work.

> What I should to do?
Pay attention what actions have regressed the permissions. The only scenario that comes to my mind for example is that you have installed firefox by using sudo, hence when you try to run it from a non-admin user, the folders do not allow your user to have write enabled. Hence, there might be an update situation or something where the permissions reset for the folders, although that shouldn't really happen.


All-in-all, the problem is not from Firefox, hence marking this issue as invalid.

Comment 6

[Wellington Torrejais da Silva]

Hello,

If not closed, could be closed. It's a old bug.
I'm still using Firefox these days.
If necessary, i will open a new bug.

Thanks!