Bug#964334: marked as done (segfault repeatedly)

2020-07-17 Thread Debian Bug Tracking System
Your message dated Fri, 17 Jul 2020 16:02:26 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-1~deb10u3 has caused the Debian Bug report #963548, regarding segfault repeatedly to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#964334:

2020-07-13 Thread steve simmons
After running "sudo apt update && sudo apt upgrade && sudo apt dist-upgrade" There was an update to chromium and the issue seems to be resolved.

Bug#964334: marked as done (segfault repeatedly)

2020-07-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Jul 2020 16:04:34 + with message-id and subject line Bug#963548: fixed in chromium 83.0.4103.116-3 has caused the Debian Bug report #963548, regarding segfault repeatedly to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#964334:

2020-07-11 Thread Marco De Donno
Same issue here on Debian 10.4 stable. What surprised me is that this went through up to stable (via the security updates). On 11.07.20 14:03, steve simmons wrote: > I have a similar looking issue. > > I updated Chromium, and since then, every few minutes there is crash. > Happens more often if

Bug#964334:

2020-07-11 Thread steve simmons
I have a similar looking issue. I updated Chromium, and since then, every few minutes there is crash. Happens more often if I have about 10 tabs open (I usually open a folder of bookmarks) I am using version: Version 83.0.4103.116 (Developer Build) built on Debian 10.4, running on Debian 10.4 (64

Bug#964334: crashes in latest chromium

2020-07-10 Thread Julian Sax
Riku Voipio writes: > This should fix it: > > https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d > > We are not building with GCC but this seems to be exactly the place where the > crash happens. > chromium built with this patch has not crashed for t

Bug#964334:

2020-07-10 Thread Bruno Gonçalves Araujo
I have this bug too, in 83.0.4103.116-2 Tested in one pc with nvidia gpu, and two with intel gpu

Bug#964334: crashes in latest chromium

2020-07-09 Thread Riku Voipio
This should fix it: https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d We are not building with GCC but this seems to be exactly the place where the crash happens. chromium built with this patch has not crashed for the last few hours for me, while

Bug#964334: segfault repeatedly

2020-07-07 Thread Martin Hradil
Package: chromium Version: 83.0.4103.116-2 Followup-For: Bug #964334 Dear Maintainer, seeing the same issue in chromium 83.0.4103.116-2, keeps crashing after a few minutes of use. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964362 is a dup of this one, https://bugs.debian.org/cgi-bin

Bug#964334: segfault repeatedly

2020-07-07 Thread Stefano Zacchiroli
I've seen this bug has been marked as "more info" (with no comment), but I'm not clear on which additional info are needed and how I can provide them. Advice on how I can help is welcome :-)

Bug#964334: segfault repeatedly

2020-07-06 Thread Daniil Shchadny
Package: chromium Version: 83.0.4103.116-2 Followup-For: Bug #964334 Also like said before, chromium crashes very soon after starting, usually in few minutes. System is up-to-date, no proprietary software. -- Stacktrace: daniil@apollopc:~$ chromium [34138:34138:0706/222408.794943

Bug#964334: segfault repeatedly

2020-07-05 Thread Julien-Benjamin
Package: chromium Version: 83.0.4103.116-1~deb10u2 Followup-For: Bug #964334 Like said before, Chromium keeps crashing within a few minutes maximum. It has also becomes very very slow since the last update. Happening to me on stable with a few packages from the backports (kernel 5.4 + nvidia

Bug#964334: segfault repeatedly

2020-07-05 Thread Stefano Zacchiroli
Package: chromium Version: 83.0.4103.116-2 Severity: grave I've upgraded chromium to the current version in testing, and it segfaults repeatedly (and very "reliably"! :-)) after usually ~1 minute of runtime, even when not used in foreground, with a stack trace like this one: - $