Your message dated Sun, 23 Aug 2015 18:27:11 -0400
with message-id
<CANTw=MNE=VW-TWUmHqrbT=mua3dug26ppfvvzj-nc9q6ete...@mail.gmail.com>
and subject line Re: [Pkg-chromium-maint] Bug#686625: chromium: Must be able to
get user data directory!
has caused the Debian Bug report #686625,
regarding chromium: Must be able to get user data directory!
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.)
--
686625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686625
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 21.0.1180.89~r154005-1
Severity: normal
Already reported at
https://code.google.com/p/chromium/issues/detail?id=144802
but I feel this *might* be a Debian-specific issue, as chromium seems to be
having difficulty with the local
file system.
What steps will reproduce the problem?
1. Create a new linux account, ie. adduser dummy
2. Open terminal, execute "sux dummy"
3. Start chromium in terminal: "chromium&"
What is the expected result?
chromium starts
What happens instead?
chromium does not start, and pukes this error instead:
$ chromium&
[1] 11026
dummy@x60s:/home/ckoen$
[11026:11026:6734994198:FATAL:chrome_browser_main.cc(1214)] Check failed:
PathService::Get(chrome::DIR_USER_DATA, &user_data_dir_). Must be able to get
user data directory!
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages chromium depends on:
ii chromium-inspector 20.0.1132.57~r145807-1
ii gconf-service 3.2.5-1+build1
ii libasound2 1.0.25-4
ii libatk1.0-0 2.4.0-2
ii libbz2-1.0 1.0.6-4
ii libc6 2.13-35
ii libcairo2 1.12.2-2
ii libcups2 1.5.3-1
ii libdbus-1-3 1.6.0-1
ii libevent-2.0-5 2.0.19-stable-3
ii libexpat1 2.1.0-1
ii libflac8 1.2.1-6
ii libfontconfig1 2.9.0-7
ii libfreetype6 2.4.9-1
ii libgcc1 1:4.7.1-2
ii libgconf-2-4 3.2.5-1+build1
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libgnome-keyring0 3.4.1-1
ii libgtk2.0-0 2.24.10-2
ii libjpeg8 8d-1
ii libnspr4 2:4.9.1-1
ii libnss3 2:3.13.5-1
ii libnss3-1d 2:3.13.5-1
ii libpango1.0-0 1.30.0-1
ii libpng12-0 1.2.49-1
ii libpulse0 2.0-6
ii libspeex1 1.2~rc1-6
ii libstdc++6 4.7.1-2
ii libudev0 175-7
ii libx11-6 2:1.5.0-1
ii libxcomposite1 1:0.4.3-2
ii libxext6 2:1.3.1-2
ii libxfixes3 1:5.0-4
ii libxml2 2.8.0+dfsg1-5
ii libxrender1 1:0.9.7-1
ii libxslt1.1 1.1.26-13
ii libxss1 1:1.2.2-1
ii xdg-utils 1.1.0~rc1+git20111210-6
ii zlib1g 1:1.2.7.dfsg-13
chromium recommends no packages.
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Unfortunately upstream tagged this wontfix. If you still experience
the problem, please reopen the discussion there.
Best wishes,
Mike
--- End Message ---
