Ubuntu
chromium-browser package

Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2

Bug #1702633 reported by rusli
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

[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

Revision history for this message
rusli (mrusliathome) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
David Rodriguez (rodrigda) wrote :

I believe I am experiencing this also. I was sent over from this bug https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407?comments=all and told by @olivier my issue might be related to this.

I have two different traces. I am trying to install the debug syms but that is failing at the moment.

liveview@liveview-pi-2:~$ chromium-browser http://localhost:3000
Gkr-Message: secret service operation failed: Failed to execute program org.freedesktop.secrets: No such file or directory
Received signal 4 <unknown> 00007620af76
#0 0x000076e5ed12 base::debug::StackTrace::StackTrace()
#1 0x000076e5e952 base::debug::StackTrace::StackTrace()
#2 0x000076e5effc <unknown>
#3 0x000072253270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 4 <unknown> 00007620af76
#0 0x000076e5ed12 base::debug::StackTrace::StackTrace()
#1 0x000076e5e952 base::debug::StackTrace::StackTrace()
#2 0x000076e5effc <unknown>
#3 0x000072253270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 4 <unknown> 00007620af76
#0 0x000076e5ed12 base::debug::StackTrace::StackTrace()
#1 0x000076e5e952 base::debug::StackTrace::StackTrace()
#2 0x000076e5effc <unknown>
#3 0x000072253270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[3954:3954:0707/082236.792580:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
[3870:3919:0707/082236.822238:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[3870:3919:0707/082236.823858:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[3870:3919:0707/082236.824314:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[3870:3919:0707/082236.824888:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
[3870:3919:0707/082236.825063:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
Received signal 4 <unknown> 0000761bdf76
#0 0x000076e11d12 base::debug::StackTrace::StackTrace()
#1 0x000076e11952 base::debug::StackTrace::StackTrace()
#2 0x000076e11ffc <unknown>
#3 0x000072206270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
liveview@liveview-pi-2:~$

liveview@liveview-pi-2:~$ chromium-browser http://localhost:3000 --disable-extensions --disable-gpu
Gkr-Message: secret service operation failed: Failed to execute program org.freedesktop.secrets: No such file or directory
Received signal 4 <unknown> 000076219f76
#0 0x000076e6dd12 base::debug::StackTrace::StackTrace()
#1 0x000076e6d952 base::debug::StackTrace::StackTrace()
#2 0x000076e6dffc <unknown>
#3 0x000072262270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Received signal 4 <unknown> 00007621ff76
liveview@liveview-pi-2:~$

Revision history for this message
David Rodriguez (rodrigda) wrote :

I am running on a Raspberry Pi using Ubuntu Mate 16.04.2 LTS

Revision history for this message
David Rodriguez (rodrigda) wrote :

I ran the --debug flag with chromium and this is what I get.

chromium-browser --debug 2>&1 | tee gdb-chromium.txt
# Env:
# LD_LIBRARY_PATH=/usr/lib/chromium-browser
# PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# GTK_PATH=
# CHROMIUM_USER_FLAGS=
# CHROMIUM_FLAGS= --enable-pinch
/usr/bin/gdb /usr/lib/chromium-browser/chromium-browser -x /tmp/chromiumargs.7UrczA
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/chromium-browser/chromium-browser...Reading symbols from /usr/lib/debug/.build-id/1c/447ddfe5801b1e898e275d0a960370b691c768.debug...done.
done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run http://localhost:3000
Starting program: /usr/lib/chromium-browser/chromium-browser http://localhost:3000
Cannot parse expression `.L1185 4@r4'.
warning: Probes-based dynamic linker interface failed.
Reverting to original interface.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
/usr/bin/chromium-browser: line 230: 4342 Killed $GDB "$LIBDIR/$APPNAME" -x $tmpfile

Revision history for this message
David Rodriguez (rodrigda) wrote :

any ideas on this ?

Revision history for this message
Matt Farley (mattfarley) wrote :

Also experiencing this issue on Armbian / Tinkerboard: (started in the last 24 hours)

Received signal 4 <unknown> 0000b627bf76
#0 0x0000b6ecfd12 base::debug::StackTrace::StackTrace()
#1 0x0000b6ecf952 base::debug::StackTrace::StackTrace()
#2 0x0000b6ecfffc <unknown>
#3 0x0000b22c4270 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[1:1:0100/000000.254673:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/000000.254358:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/000000.252931:ERROR:broker_posix.cc(41)] Invalid node channel message
chromium-browser --type=renderer --enable-pinch --touch-events=enabled --field-trial-handle=1 --primordial-pipe-token=4F4CE9017E684C5B2C348A144C447C52 --lang=en-US --extension-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;3,0,3553: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed.
chromium-browser --type=renderer --enable-pinch --touch-events=enabled --field-trial-handle=1 --primordial-pipe-token=5C7F09F5E933838E9FA003036790C6CA --lang=en-US --extension-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;3,0,3553: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed.
Received signal Received signal 44 <unknown> <unknown> 0000b223e3f60000b223e3f6

##00 0x0x0000b6e49d120000b6e49d12 <unknown>
#1 0x0000b6e49952 <unknown>
ile5ErrorE#
2# 10x 0000b6e49ffc0x 0000b6e49952 <unknown>
#2 0x0000b6e49ffc <unknown>peEPi

##33 0x0x0000b223e2700000b223e270 <unknown>
#4 0x0000b223e3f6 <unknown>
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Revision history for this message
David Rodriguez (rodrigda) wrote :

For now I have reverted back to version 58.0.3029.81-0ubuntu0.16.04.1277. This doesn't give me any issues and the browser actually comes up.

Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time.

Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in chromium-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.