Your message dated Sat, 16 Feb 2019 00:08:33 -0500
with message-id
<CANTw=MMyjQ93m4YAmSXu1cw_TbmjFvv3TQfVX7=z8ve8nas...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#722571: Bug#722571: chromium:
Writes short-lived temp files to /var/tmp instead of /tmp
has caused the Debian Bug report #722571,
regarding chromium: sqlite writes temp files to /var/tmp instead of /tmp
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
722571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722571
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 29.0.1547.57-3
Severity: normal
Control: forwarded -1 https://code.google.com/p/chromium/issues/detail?id=290117
Chromium writes several short-lived files to /var/tmp, but those
should be written to /tmp. Users with SSDs often mount a tmpfs on
/tmp to reduce writes to the SSD. But /var/tmp cannot be a tmpfs,
as it needs to be preserved across reboots. Writing those short-lived
files to /var/tmp thus causes unnecessary writes to the SSD.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (980, 'unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 29.0.1547.57-3
ii gconf-service 3.2.6-1
ii libasound2 1.0.27.2-1
ii libatk1.0-0 2.8.0-2
ii libc6 2.17-92+b1
ii libcairo2 1.12.14-5
ii libcups2 1.6.3-1
ii libdbus-1-3 1.6.14-1
ii libexpat1 2.1.0-4
ii libfontconfig1 2.10.2-2
ii libfreetype6 2.4.9-1.1
ii libgcc1 1:4.8.1-10
ii libgconf-2-4 3.2.6-1
ii libgcrypt11 1.5.3-2
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.4-1
ii libgnome-keyring0 3.8.0-2
ii libgtk2.0-0 2.24.20-1
ii libjpeg8 8d-1
ii libnspr4 2:4.10-1
ii libnss3 2:3.15.1-1
ii libnss3-1d 2:3.15.1-1
ii libpango-1.0-0 1.32.5-5+b1
ii libpangocairo-1.0-0 1.32.5-5+b1
ii libspeechd2 0.7.1-6.2
ii libstdc++6 4.8.1-10
ii libudev0 175-7.2
ii libx11-6 2:1.6.1-1
ii libxcomposite1 1:0.4.4-1
ii libxdamage1 1:1.1.4-1
ii libxext6 2:1.3.2-1
ii libxfixes3 1:5.0.1-1
ii libxml2 2.9.1+dfsg1-3
ii libxrender1 1:0.9.8-1
ii libxslt1.1 1.1.28-2
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-7
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
pgptFzfXs9c2e.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, Sep 13, 2013 at 8:30 AM Julian Andres Klode wrote:
> This is caused by sqlite3 (spell the prefix backwards). Exporting
> TMPDIR=/tmp when starting chromium works around it. Basically patching
> src/os_unix.c of the sqlite3 code to list /tmp before /var/tmp fixes
> this.
Upstream closed your report without doing anything about it. Since
this bug can be worked around and a fix should go into sqlite first
(#722699), where nothing is happening too, I am closing the chromium
at this time. If upstream or sqlite activity starts happening, please
feel free to reopen.
As for the workaround itself, I am reluctant to add it to the chromium
launcher script since overriding the users TMPDIR preferences can be
error prone. However, I could be convinced otherwise with a well
tested patch.
Best wishes,
Mike
--- End Message ---
