Bug#930469: chromium: Insta-segfault on start

2019-06-17 Thread Gedalya
I got this behavior with "session":{"restore_on_startup":1} in 
~/.config/chromium/{profile}/Preferences.

I only get this on my laptop, for some reason, not my desktop.

I can set that to 0 instead of 1 and everything is OK, except my saved tabs of 
course which are not restored.

Also, I've noticed that having that set to 1, I can sometimes close Chromium 
and open it again. I'm not quite sure on what the condition is, but closing it 
down with Ctrl+W, tab by tab down to the last one, seems to cause the issue, 
and closing all of Chromium with Ctrl+Q actually seems to work better. Again, 
not 100% sure about this.

For some reason, opening with --disable-extensions works around the issue, too.



Bug#930469: chromium: Insta-segfault on start

2019-06-16 Thread Nikita Grishko
Package: chromium
Version: 75.0.3770.90-1
Followup-For: Bug #930469

I tried running it with --temp-profile as Mike suggested and it worked. Any
ideas how can I keep all my profile data such as history and bookmarks?



-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru:en_US (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  75.0.3770.90-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-7
ii  libatspi2.0-02.30.0-7
ii  libavcodec58 7:4.1.3-1
ii  libavformat587:4.1.3-1
ii  libavutil56  7:4.1.3-1
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.2.10-6
ii  libdbus-1-3  1.12.16-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-7
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk-3-0   3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libicu63 63.2-2
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.21-1
ii  libnss3  2:3.44+really3.42.1-2
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+b1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.3.0-7
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  75.0.3770.90-1

Versions of packages chromium suggests:
pn  chromium-driver  
ii  chromium-l10n75.0.3770.90-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-sandbox75.0.3770.90-1
ii  fonts-liberation1:1.07.4-9
ii  libgl1-mesa-dri 18.3.6-2
ii  libu2f-udev 1.1.9-1
ii  notification-daemon 3.20.0-4
ii  plasma-workspace [notification-daemon]  4:5.14.5.1-1
ii  upower  0.99.10-1

Versions of packages chromium-sandbox depends on:
ii  libatomic1  8.3.0-7
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-7
ii  libstdc++6  8.3.0-7

-- no debconf information



Bug#930469: chromium: Insta-segfault on start

2019-06-14 Thread Michael Brade
I can confirm this, I have exactly the same experience, even though I
upgraded from 74 to 75. Now I went back to 73.

Due to chromium's intelligence of saving the tabs on a crash, this crash
makes me lose all my 170 tabs, therefore I won't try it again with
--temp-profile. But maybe this helps: starting it with --debug works.
Maybe this is kind of equivalent to --temp-profile?



Processed: Re: Bug#930469: chromium: Insta-segfault on start

2019-06-13 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 moreinfo
Bug #930469 [chromium] chromium: Insta-segfault on start
Added tag(s) moreinfo.

-- 
930469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#930469: chromium: Insta-segfault on start

2019-06-13 Thread Michael Gilbert
control: tag -1 moreinfo

On Thu, Jun 13, 2019 at 5:36 AM Guillem Jover wrote:
>   [23609:23609:0613/102304.872428:FATAL:render_process_host_impl.cc(4060)] 
> Check failed: render_process_host->InSameStoragePartition( 
> BrowserContext::GetStoragePartition(browser_context, site_instance, false )).

This is the error.  FATAL errors in chromium intentionally abort
execution.  That output should have also been seen without --debug,
although upstream's handling of FATAL messages can be flaky.

My best guess is that there is an incompatibility with profiles
created before 75.  If you start with --temp-profile, does that avoid
the problem?

Best wishes,
Mike



Bug#930469: chromium: Insta-segfault on start

2019-06-13 Thread Guillem Jover
Package: chromium
Version: 75.0.3770.80-1
Severity: serious

Hi!

I was using 73.0.3683.75-1, held due to the problems with later
version. Upgraded to the latest version in unstable, and now I'm
getting insta-segfaults on startup. The output when running normally
(first without --debug) is not very helpful (even with debugging
symbols installed), but including it anyway for reference:

  ,---
  $ chromium

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated 
and shouldn't be used anymore. It will be removed in a future version

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated 
and shouldn't be used anymore. It will be removed in a future version

  (chromium:23107): Gtk-WARNING **: 10:20:56.996: Theme parsing error: 
gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is 
deprecated and shouldn't be used anymore. It will be removed in a future version
  [23144:23144:0613/102057.178209:ERROR:sandbox_linux.cc(368)] 
InitializeSandbox() called with multiple threads in process gpu-process.
  [23107:23338:0613/102057.270516:ERROR:object_proxy.cc(619)] Failed to call 
method: org.freedesktop.Notifications.GetCapabilities: object_path= 
/org/freedesktop/Notifications: org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.Notifications was not provided by any .service files
  Received signal 11 SEGV_MAPERR 0028
  #0 0x55bf99dac109 
  #1 0x55bf99cfd656 
  #2 0x55bf99daa9d3 
  #3 0x55bf99dac095 
  #4 0x7fb29733a730 
  #5 0x55bf9997d6c4 
  #6 0x55bf9997d011 
  #7 0x55bf9997cd00 
  #8 0x55bf9997d293 
  #9 0x55bf99d5864d 
  #10 0x55bf99d644eb 
  #11 0x55bf99d66c51 
  #12 0x55bf99d1df11 
  #13 0x55bf99d62e9f 
  #14 0x55bf99d42987 
  #15 0x55bf99858a77 
  #16 0x55bf97fbe449 
  #17 0x55bf97fbe525 
  #18 0x55bf97faaccc 
  #19 0x55bf9982f217 
  #20 0x55bf9982f2ec 
  #21 0x55bf9982f6dd 
  #22 0x55bf99838faa 
  #23 0x55bf9982da75 
  #24 0x55bf972712bd ChromeMain
  #25 0x7fb28f31a09b __libc_start_main
  #26 0x55bf9727111a _start
r8: 7fff4a01cde8  r9: 0001 r10: 0007c0976a43a815 r11: 
0001
   r12: 55bfa168c680 r13: 7fff4a01cdac r14: 7fff4a01ce20 r15: 

di: 0040  si: 55bfa058f7c0  bp: 7fff4a01cd90  bx: 

dx: 55bfa2046840  ax: 55bfa133beb0  cx: 55bfa2046840  sp: 
7fff4a01cd40
ip: 55bf9997d6c4 efl: 00010202 cgf: 002b0033 erf: 
0004
   trp: 000e msk:  cr2: 0028
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.
  `---

And running with --debug:

  ,---
  $ $ chromium -g
  # Env:
  # LD_LIBRARY_PATH=
  #PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
  #GTK_PATH=
  #  CHROMIUM_FLAGS= --show-component-extension-options 
--enable-gpu-rasterization --no-default-browser-check --disable-pings 
--media-router=0 --enable-remote-extensions 
--load-extension=/usr/share/chromium/extensions/ublock-origin
  /usr/bin/gdb /usr/lib/chromium/chromium -x /tmp/chromiumargs.GqFGjf
  GNU gdb (Debian 8.2.1-2) 8.2.1
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  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 "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/lib/chromium/chromium...Reading symbols from 
/usr/lib/debug/.build-id/c0/a3cca8a6781df2e2abad91c807214f3aad91a4.debug...done.
  done.
  (gdb) run
  Starting program: /usr/lib/chromium/chromium 
--show-component-extension-options --enable-gpu-rasterization 
--no-default-browser-check --disable-pings --media-router=0 
--enable-remote-extensions 
--load-extension=/usr/share/chromium/extensions/ublock-origin --single-process 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe9e05700 (LWP 23613)]
  [Detaching after fork from child process 23614]
  [New Thread 0x7fffe9604700 (LWP 23618)]
  [New Thread 0x7fffe3370700 (LWP 23619)]
  [New Thread 0x7fffe2b6f700 (LWP 23620)]
  [New Thread 0x7fffe1b6d700 (LWP 23622)]
  [New Thread 0x7fffe236e700 (LWP 23621)]
  [New Thread 0x7fffe136c700 (LWP 23623)]
  [New Thread