Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-06-10 Thread Stephen Kitt



On 10 June 2019 06:59:43 CEST, "Jürgen Göricke"  
wrote:
>why don't you create binary packages of chromium and publish them in
>the unstable branch?
>Did I miss something important?

The packages are still being built, see 
https://buildd.debian.org/status/package.php?p=chromium

Regards,

Stephen



Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-06-09 Thread Jürgen Göricke
Dear Maintainer,

why don't you create binary packages of chromium and publish them in the 
unstable branch?
Did I miss something important?

I see this Chromium version as a required bugfix release.

I'm asking for clarification.

Thank you!

best regards


pgpDCbBSWtlER.pgp
Description: Digitale Signatur von OpenPGP


Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-06-04 Thread Jürgen Göricke
Dear Maintainer,

what information is missing to create an bug-free chromium version?
How and when will it continue?
Or will we wait until the next major release to get a bug-free chromium version?

Some feedback wouldn't be bad.

best regards


pgpKj8zbdgszv.pgp
Description: Digitale Signatur von OpenPGP


Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-04-26 Thread Harald Dunkel
metoo

Using upstream's google-chrome 74.0.3729.108 there is no such 
problem.



Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-04-25 Thread Jürgen Göricke
Dear Maintainer,

   * What led up to the situation?

I started a chromium window and wanted to open one more.
This error has occurred since the update to version 74.0.3729.108-1.

   * What exactly did you do (or not do) that was effective (or ineffective)?

As already described, I wanted to open another chromium window.

   * What was the outcome of this action?

The first Chromium window was closed with the following error message.
For error diagnosis I started Chromium via command line interface and could see 
this error message.

[2195:2195:0425/202122.818950:ERROR:vaapi_wrapper.cc(335)] vaInitialize failed: 
unknown libva error
[2195:2195:0425/202122.841660:ERROR:sandbox_linux.cc(368)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[2195:2195:0425/202142.935237:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2195:2195:0425/202211.279588:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2195:2195:0425/202629.954596:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2195:2195:0425/202859.748973:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2195:2195:0425/203531.165889:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2195:2195:0425/203557.201811:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command

   * What outcome did you expect instead?

I expected to be able to open multiple Chromium windows without crashing the 
opened instance.




-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  74.0.3729.108-1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.30.0-5
ii  libatk1.0-0  2.30.0-2
ii  libatomic1   8.3.0-6
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.1-1
ii  libavformat587:4.1.1-1
ii  libavutil56  7:4.1.1-1
ii  libc62.28-8
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6
ii  libdbus-1-3  1.12.12-1
ii  libdrm2  2.4.97-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.6-1
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libgcc1  1:8.3.0-6
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.1-6
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3
ii  liblcms2-2   2.9-3
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.20-1
ii  libnss3  2:3.42.1-1
ii  libopenjp2-7 2.3.0-2
ii  libopus0 1.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libpci3  1:3.5.2-5
ii  libpng16-16  1.6.36-6
ii  libpulse012.2-4
ii  libre2-5 20190101+dfsg-2
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-6
ii  libva2   2.4.0-1
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  74.0.3729.108-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n74.0.3729.108-1
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 74.0.3729.108-1
ii  fonts-liberation 1:1.07.4-9
ii  libgl1-mesa-dri

Bug#927913: Second chromium kills the first one, and we see "Restore pages?"

2019-04-24 Thread 積丹尼 Dan Jacobson
Package: chromium
Version: 74.0.3729.108-1
Severity: important

$ chromium &
$ sleep 22
$ chromium &

The second one kills the first one, and we see "Restore pages?"