** Changed in: chromium-browser (Debian)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading
Version 61.0.3163.100 (Developer Build) built on Debian 9.1, running on
Debian 9.2 (64-bit)
Linux - 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64
GNU/Linux
Debian GNU/Linux 9 \n \l
Received signal 11 SEGV_MAPERR 0010
#0 0x55f1d1943cc6
#1 0x55f1cfeddef4
#2 0x55f1d194406d
#3
I have just reported bug #1717473 with version
60.0.3112.113-0ubuntu0.16.04.1298, where the original bug reported here
is happening again except that I get "SEGV_MAPERR 0028" instead
of "SEGV_MAPERR 0010"
--
You received this bug notification because you are a member of Desktop
Pa
Oh,got it, sorry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/xenial/yakkety
Status in chromium-
@kingsting: then that's not the right place to ask for help or report
issues, this is a bug report for the chromium-browser package in ubuntu.
You might be able to get help from the QtWebengine team.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
The browser is an example demo from QtWebengine 5.9.1. I cross compile
it and run it on my arm linux board. The version of the linux kernel is
3.6.5 ,which not support sandbox ,so i disabled it. The browser's build
arguments is march=armv7a, mfpu=vfpv3, mfloat-abi=softfp. But the linux
kernel was b
@kingsting: can you please elaborate? Which version of chromium? On
which version of Ubuntu? Which CPU architecture?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Titl
I got a similar problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/xenial/yakkety
Status in ch
@Jean-Marc & Patrik: Yakkety (Ubuntu 16.10) has recently reached its end
of life, it is no longer supported. You are strongly encouraged to
upgrade to Zesty (17.04). Chromium for yakkety won't receive further
updates.
--
You received this bug notification because you are a member of Desktop
Packa
Also experiencing this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/xenial/yakkety
Status in chr
I'm still having the exact same problem with chromium-browser
(59.0.3071.109-0ubuntu0.16.10.1357).
Received signal 11 SEGV_MAPERR 0010
#0 0x7fbf377680c6 base::debug::StackTrace::StackTrace()
#1 0x7fbf377684ab
#2 0x7fbf37a95630
#3 0x560ced1a6fd8
#4 0x560ced1a9866
#5 0x560ced1aa00e
#6 0
This bug was fixed in the package chromium-browser -
59.0.3071.109-0ubuntu0.16.04.1291
---
chromium-browser (59.0.3071.109-0ubuntu0.16.04.1291) xenial; urgency=medium
* debian/patches/fix-argument-evaluation-order.patch: added (LP:
#1702407)
-- Olivier Tilloy Fri, 07 Jul 2017
10
This bug was fixed in the package chromium-browser -
59.0.3071.109-0ubuntu0.14.04.1188
---
chromium-browser (59.0.3071.109-0ubuntu0.14.04.1188) trusty; urgency=medium
* debian/patches/fix-argument-evaluation-order.patch: added (LP:
#1702407)
-- Olivier Tilloy Fri, 07 Jul 2017
10
PPA fix in #30 worked for me in xenial.
Thanks osomon
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty
I was experiencing the same big and chromium fix update in #30 worked
for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 5
Depends which release and update model you mean, in Debian
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
t
Nathan,
The linked Debian bug is unrelated to this crash. It disabled the
internal media router component, which was initially broken on Linux and
conflicted with the external cast plugin. With the fixes here, Debian
should be able to re-enable the internal media router component in their
packag
Is there a particular reason Ubuntu takes longer to patch than Debian?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.307
Confirm fixed for me too - Ubuntu Gnome 16.04.2 LTS
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/x
@Olivier, re #7,33,36 I see my mistake thanks to further posts and
replies. I had spotted chromium-browser-dbg in synaptic and then had
this package name in mind while misreading the more detailed
instructions in the wiki link - it makes perfect sense on a calm
reading!
Anyway thanks again.
--
@osomon: Fix confirmed (Xenial) and casting works. Thanks! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
@David: please continue this discussion on bug #1702633.
If you don't manage to install the dbgsym package, you can still
download it manually and install it (with `sudo dpkg -i`) from there:
https://launchpad.net/~canonical-chromium-
builds/+archive/ubuntu/stage/+build/12789789
--
You received
ok I have the debug package installed. Thank you all I will continue on
the other bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash aft
@julian I tried to install the symbol package and it said it wouldn't
install the correct version of chrome so it stopped. I think I will try
to remove the osomon repo all together remove chrome, install the debug
package. Have it install chrome than upgrade it. See where I end up.
Thanks.
--
Seems like a new chromium-browser-dbgsym needs to be release for the
version of chromium I installed. Does that make sense?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/17024
@osomon : The most obvious "patch" (the one requiring the least
verification), is to have Ubuntu's Software Updater roll back Chromium
to the version prior to the current version.
Comment 19 was the work-around that helped me:
https://askubuntu.com/a/932799/256054
--
You received this bug notifi
@julian I tried you suggestion and still nothing. I will keep monkeying
with it. Any other thoughts? Appreciate the help.
@olivier I did update the bug you referenced with the current trace I
have. Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, wh
@David: In order to avoid that conflict you need to disable the
'backport' packages archive (it often introduce hidden conflicts).
Using GUI: 'Software & Updates' -> Updates -> Unsupported Updates
Then try installing chromium-browser-dbgsym. It worked for me.
--
You received this bug notificati
@David: Or perhaps is because osomom PPA installed a new version and it
does not have a symbol package for that version.
What if you install symbols package first and then upgrade chromium from
PPA?
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
@olivier I tried that too and it gave me the same issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
tru
@David: the link I provided mentions dbgsym ddebs. So you need to
install chromium-browser-dbgsym.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash
@olivier : Thank you. I tried installing the debug symbols but I get an
error saying the package requires an earlier version of chromium-
browser. I saw somebody else had the issue earlier but I didn't see the
fix. I think it was @garth that had the issue.
liveview@liveview-pi-2:~$ sudo apt-get
@David: indeed that’s most likely a separate issue, maybe bug #1702633 ?
Could you please try to install debug symbols (see
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Getting_-
dbgsym.ddeb_packages) for chromium-browser and see if you get a more
complete stacktrace? If you do, please update
David,
That looks to be totally unrelated to the issue addressed in this bug
report. You should start a new one.
Olivier,
I've had the same chromium process running for several hours now,
intermittently messing with the cast extension and cycling wifi. Still
going strong. I think this one is
Alright I added a couple other flags.
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 76219f76
#0
I just updated and I am getting this crash. I am running on a Raspberry
Pi using Ubuntu Mate 16.04.2 LTS
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
Rec
PPA packages work for me on 16.04.02. Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/xeni
Thanks for the feedback Björn. That seems to confirm that clang builds
are not affected. At the moment only zesty and artful chromium packages
are built with clang. Once clang 4.0 gets SRU’d to xenial (bug #1687981)
and yakkety is EOL'd that will leave only trusty builds with gcc.
--
You received
Fix works fine here too, Xenial
Thank you
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
trusty/xenial/yakk
39 matches
Mail list logo