Public bug reported:
[8278:8278:0706/155805.403422:ERROR:process_singleton_posix.cc(253)]
readlink(/tmp/.org.chromium.Chromium.umUEz3/SingletonCookie) failed: Permission
denied
chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs
(thread->pid) == thread->tid' failed.
Received signal 4 <unknown> 0000722083f6
#0 0x000076e13d12 base::debug::StackTrace::StackTrace()
#1 0x000076e13952 base::debug::StackTrace::StackTrace()
#2 0x000076e13ffc <unknown>
#3 0x000072208270 <unknown>
#4 0x0000722083f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.
chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs
(thread->pid) == thread->tid' failed.
Received signal 4 <unknown> 0000722083f6
#0 0x000076e13d12 base::debug::StackTrace::StackTrace()
#1 0x000076e13952 base::debug::StackTrace::StackTrace()
#2 0x000076e13ffc <unknown>
#3 0x000072208270 <unknown>
#4 0x0000722083f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 4 <unknown> 0000761f8f76
#0 0x000076e4cd12 base::debug::StackTrace::StackTrace()
#1 0x000076e4c952 base::debug::StackTrace::StackTrace()
#2 0x000076e4cffc <unknown>
#3 0x000072241270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs
(thread->pid) == thread->tid' failed.
Received signal 4 <unknown> 0000722083f6
#0 0x000076e13d12 base::debug::StackTrace::StackTrace()
#1 0x000076e13952 base::debug::StackTrace::StackTrace()
#2 0x000076e13ffc <unknown>
#3 0x000072208270 <unknown>
#4 0x0000722083f6 abort
[end of stack trace]
Calling _exit(1). Core file will not be generated.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1289
Uname: Linux 4.9.35-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: armhf
Date: Thu Jul 6 16:04:23 2017
Desktop-Session:
'None'
'None'
'None'
DetectedPlugins:
Env:
'None'
'None'
InstalledPlugins:
Load-Avg-1min: 1.10
Load-Processes-Running-Percent: 0.5%
Lspci:
Error: command ['lspci', '-mmkv'] failed with exit code 1: pcilib: Cannot open
/proc/bus/pci
lspci: Cannot find any working access method.
Lsusb:
Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 004: ID 046d:c315 Logitech, Inc. Classic Keyboard 200
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcKernelCmdLine: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1360
bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc00000
vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyS0,115200
console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline
fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.chromium-browser.default:
CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so
--ppapi-flash-version=25.0.0.148"
modified.conffile..etc.default.chromium-browser: [deleted]
mtime.conffile..etc.chromium-browser.default: 2017-06-03T11:44:06.716779
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug armhf xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702633
Title:
Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702633/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
