1135003 - firefox logs errors in the console that make no sense and can't move/rename downloaded files

Status: RESOLVED DUPLICATE of bug 1042134

(Firefox :: Untriaged, defect)

Description

[Georgi Chorbadzhiyski]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20150128124606

Steps to reproduce:

I'm using Slackware64-current and Firefox 35.0.1. I'm starting firefox from the shell to see the errors.


Actual results:

Firefox runs, but it logs:

console.error: 
  Could not write session state file 
  Message: Unix error 0 during operation move on file /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups/recovery.js (No error information)

each couple of seconds.

Here is what the directory contains.

gf@gf:~$ ls -l /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups/recovery.js
/bin/ls: cannot access /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups/recovery.js: No such file or directory
gf@gf:~$ ls -l /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups/
total 12
-rw------- 1 gf users 8835 Feb 20 12:49 recovery.js.tmp
gf@gf:~$ 

The permissions are fine (every file is 600, every directory is 700):

gf@gf:~$ ls -ld /home/gf/.mozilla/firefox/hl74g230.default/
drwx------ 17 gf users 4096 Feb 20 12:52 /home/gf/.mozilla/firefox/hl74g230.default//
gf@gf:~$ ls -ld /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups/
drwx------ 2 gf users 4096 Dec 11 01:15 /home/gf/.mozilla/firefox/hl74g230.default/sessionstore-backups//

The above messages are a symptom of something worse.

Using Firefox I can't download anything using "save" or "save as". Save as doesn't even bring file chooser dialog.

When I press CTRL-S the file is downloaded in $TMPDIR but then they are not moved to where they should be moved, they stay in /tmp with their temp name.

I have tried to change $TMPDIR, reset firefox, start with new profile, delete all profiles and start clean - nothing helps.

The only strange thing in my setup is that /home is on crypto block device:

gf@gf:~$ mount
/dev/md0 on / type ext4 (rw,noatime)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw,noatime,nosuid,nodev,size=5%)
tmpfs on /tmp type tmpfs (rw,noatime,nosuid,nodev,size=25%)
/dev/mapper/crypthome on /home type ext4 (rw,noatime)
/dev/mapper/cryptcontent on /home/gf/content type ext4 (rw,noatime)

This thing that prevents downloads, prevents also addons from updating. When I try to update them I get these error messages (an example from one addon):

1424430149377   addons.xpi      WARN    Failed to install /home/gf/tmp/tmp-13h.xpi from https://addons.cdn.mozilla.net/user-media/addons/1865/adblock_plus-2.6.7-sm+tb+fx+an.xpi: Unix error 0 during operation stat on file /home/gf/.mozilla/firefox/hl74g230.default/extensions/staged/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi (No error information) No traceback available

I have no idea when this problem started (it must have been at least 4-5 firefox releases ago), since I was unable to fix it I was just sidestepping it by "copy link location" and using wget but now that I've noticed that even addons can't be updated I decided to report it.


Expected results:

"Unix error 0" makes no sense. Zero return code is not an error. It seems that file moving fails for some reason.

Comment 1

[Georgi Chorbadzhiyski]

My problem sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1042134 which is resolved as WORKSFORME, but I'm still seeing the problem with my distro package.

Comment 2

[:Gijs (he/him)]

(In reply to Georgi Chorbadzhiyski from comment #1)
> My problem sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1042134
> which is resolved as WORKSFORME, but I'm still seeing the problem with my
> distro package.

... which you compiled yourself, because slackware, right? With which compiler? If you read bug 1042134, it seemed to be caused by a buggy version of GCC, because codewise, the message indeed makes no sense (as you concluded already in comment #0). It would be helpful if you could see if you have the same problem with an official mozilla.org build, and/or if you can detail what compiler/linker/mozconfig/configure options you're using.