Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1003753: chromium: chromium --temp-profile window displays only as a white box
90 views
Skip to first unread message
Karl O. Pinc
Jan 14, 2022, 11:00:07 PM1/14/22
to
Package: chromium
Version: 97.0.4692.71-0.1~deb11u1
Severity: normal
X-Debbugs-Cc: te...@security.debian.org
Hello,
After upgrading chromium (and there were no other updates, only
chromium), chromium fails when started with --temp-profile.
When started with --temp-profile a white box is displayed in X instead
of a window.
I am using X, over a network; the X client and server are 2 different
boxes.
Regardless of whether started with --temp-profile or not, chromium
produces at least 1 "*** stack smashing detected ***: terminated"
messages. These messages are repeated (forever?) every now and then
when started with --temp-profile.
FYI: I suspect that chromium has lately (sometime in the last few
months?) been "running" when left open with a blank window (no url)
after startup. If I switch to a different xfce4 desktop then I get a
dialog every few minutes about a window not responding and do I want
to terminate it or wait. I believe this has been the chromium window.
Now, with the update, I notice (when started without --temp-profile)
that the little spinning icon on the left side of the tab spins
forever, or until I put a url in the address bar and go to a website.
On my system chromium has always displayed some errors when started
with --temp-profile. Here are the before and after errors.
Before the upgrade:
$ chromium --temp-profile
Using temporary profile: /tmp/tmp.rt5PMS7VFH
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[221529:221529:0114/123427.359380:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is desktop
[221529:221529:0114/123427.580913:ERROR:gl_context_glx.cc(172)] Failed to create GL context with glXCreateContextAttribsARB.
[221529:221529:0114/123427.581195:ERROR:gpu_info_collector.cc(81)] gl::init::CreateGLContext failed
[221529:221529:0114/123427.581332:ERROR:gpu_info_collector.cc(285)] Could not create context for info collection.
[221529:221529:0114/123427.581549:ERROR:gpu_init.cc(77)] CollectGraphicsInfo failed.
[221529:221529:0114/123427.586203:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
[221617:221617:0114/123427.635648:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
After the upgrade:
$ chromium --temp-profile&
Using temporary profile: /tmp/tmp.sLkvqeAASq
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[232438:232438:0114/204828.389040:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[232438:232438:0114/204828.389223:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.389300:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[232438:232438:0114/204828.391912:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[232438:232438:0114/204828.391990:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.392033:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[232438:232438:0114/204828.392073:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[232438:232438:0114/204828.394380:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[232506:232506:0114/204828.435430:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[232403:232425:0114/204852.913999:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[232403:232425:0114/204852.914036:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
[232403:232531:0114/204859.116708:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[232403:232531:0114/204859.116739:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[0114/205006.867880:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
(ctrl-c pressed at this point)
Here is the after-upgrade output without --temp-profile:
chromium
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[234674:234674:0114/212647.559505:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[234674:234674:0114/212647.559731:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[234674:234674:0114/212647.559862:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[234674:234674:0114/212647.597981:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[234674:234674:0114/212647.598105:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[234674:234674:0114/212647.598275:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[234674:234674:0114/212647.598414:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[234674:234674:0114/212647.626033:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[234743:234743:0114/212647.670841:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[234631:234689:0114/212652.508944:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[234631:234689:0114/212652.509040:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
[234631:234666:0114/212711.986767:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[234631:234666:0114/212711.986847:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
-- System Information:
Debian Release: 11.2
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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 97.0.4692.71-0.1~deb11u1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libc6 2.31-13+deb11u2
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libharfbuzz0b 2.7.4-1
ii libicu67 67.1-7
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.61-1+deb11u1
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp6 0.6.1-2.1
ii libwebpdemux2 0.6.1-2.1
ii libwebpmux3 0.6.1-2.1
ii libx11-6 2:1.7.2-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-13+deb11u2
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.2-1
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 20.3.5-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
ii xfce4-notifyd [notification-daemon] 0.6.2-1
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-13+deb11u2
-- no debconf information
Version: 97.0.4692.71-0.1~deb11u1
Severity: normal
X-Debbugs-Cc: te...@security.debian.org
Hello,
After upgrading chromium (and there were no other updates, only
chromium), chromium fails when started with --temp-profile.
When started with --temp-profile a white box is displayed in X instead
of a window.
I am using X, over a network; the X client and server are 2 different
boxes.
Regardless of whether started with --temp-profile or not, chromium
produces at least 1 "*** stack smashing detected ***: terminated"
messages. These messages are repeated (forever?) every now and then
when started with --temp-profile.
FYI: I suspect that chromium has lately (sometime in the last few
months?) been "running" when left open with a blank window (no url)
after startup. If I switch to a different xfce4 desktop then I get a
dialog every few minutes about a window not responding and do I want
to terminate it or wait. I believe this has been the chromium window.
Now, with the update, I notice (when started without --temp-profile)
that the little spinning icon on the left side of the tab spins
forever, or until I put a url in the address bar and go to a website.
On my system chromium has always displayed some errors when started
with --temp-profile. Here are the before and after errors.
Before the upgrade:
$ chromium --temp-profile
Using temporary profile: /tmp/tmp.rt5PMS7VFH
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[221529:221529:0114/123427.359380:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is desktop
[221529:221529:0114/123427.580913:ERROR:gl_context_glx.cc(172)] Failed to create GL context with glXCreateContextAttribsARB.
[221529:221529:0114/123427.581195:ERROR:gpu_info_collector.cc(81)] gl::init::CreateGLContext failed
[221529:221529:0114/123427.581332:ERROR:gpu_info_collector.cc(285)] Could not create context for info collection.
[221529:221529:0114/123427.581549:ERROR:gpu_init.cc(77)] CollectGraphicsInfo failed.
[221529:221529:0114/123427.586203:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
[221617:221617:0114/123427.635648:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is disabled
After the upgrade:
$ chromium --temp-profile&
Using temporary profile: /tmp/tmp.sLkvqeAASq
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[232438:232438:0114/204828.389040:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[232438:232438:0114/204828.389223:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.389300:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[232438:232438:0114/204828.391912:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[232438:232438:0114/204828.391990:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.392033:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[232438:232438:0114/204828.392073:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[232438:232438:0114/204828.394380:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[232506:232506:0114/204828.435430:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[232403:232425:0114/204852.913999:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[232403:232425:0114/204852.914036:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
[232403:232531:0114/204859.116708:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[232403:232531:0114/204859.116739:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[0114/205006.867880:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
(ctrl-c pressed at this point)
Here is the after-upgrade output without --temp-profile:
chromium
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[234674:234674:0114/212647.559505:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[234674:234674:0114/212647.559731:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[234674:234674:0114/212647.559862:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[234674:234674:0114/212647.597981:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[234674:234674:0114/212647.598105:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[234674:234674:0114/212647.598275:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[234674:234674:0114/212647.598414:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[234674:234674:0114/212647.626033:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[234743:234743:0114/212647.670841:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
[234631:234689:0114/212652.508944:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
[234631:234689:0114/212652.509040:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
[234631:234666:0114/212711.986767:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[234631:234666:0114/212711.986847:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
-- System Information:
Debian Release: 11.2
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-10-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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 97.0.4692.71-0.1~deb11u1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libc6 2.31-13+deb11u2
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libharfbuzz0b 2.7.4-1
ii libicu67 67.1-7
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.61-1+deb11u1
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp6 0.6.1-2.1
ii libwebpdemux2 0.6.1-2.1
ii libwebpmux3 0.6.1-2.1
ii libx11-6 2:1.7.2-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-13+deb11u2
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.2-1
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 20.3.5-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
ii xfce4-notifyd [notification-daemon] 0.6.2-1
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-13+deb11u2
-- no debconf information
Karl O. Pinc
Jan 23, 2022, 2:50:03 PM1/23/22
to
Hello,
Upgrading to the latest chromium seems to have fixed the
problem of the window being displayed as a white box
without any controls.
Upgrade: chromium-sandbox:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium-common:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2)
Note that I am still getting plenty of error messages
on stdout/stderr when invoking chromium --temp-profile
from the command line. See below.
You may want to close this bug. I would be happy to file
a separate bug report(s) for any of the error messages
below, however you would advise.
----------------
$ chromium --temp-profile
Using temporary profile: /tmp/tmp.60BqxExgbm
[32220:32307:0123/132117.954095:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
[32251:32251:0123/132119.862602:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[32251:32251:0123/132119.862797:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[32251:32251:0123/132119.862878:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[32251:32251:0123/132119.865704:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[32251:32251:0123/132119.865808:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[32251:32251:0123/132119.866036:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[32251:32251:0123/132119.866206:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[32251:32251:0123/132119.870342:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[32343:32343:0123/132119.961357:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
Fontconfig error: Cannot load default config file
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Upgrading to the latest chromium seems to have fixed the
problem of the window being displayed as a white box
without any controls.
Upgrade: chromium-sandbox:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium-common:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2)
Note that I am still getting plenty of error messages
on stdout/stderr when invoking chromium --temp-profile
from the command line. See below.
You may want to close this bug. I would be happy to file
a separate bug report(s) for any of the error messages
below, however you would advise.
----------------
$ chromium --temp-profile
Using temporary profile: /tmp/tmp.60BqxExgbm
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[32220:32307:0123/132117.954017:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(). If you don't see the END: message, this is crbug.com/1216328.
libGL error: failed to load driver: radeonsi
[32220:32307:0123/132117.954095:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)] END: ReportBluetoothAvailability()
[32251:32251:0123/132119.862602:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[32251:32251:0123/132119.862797:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[32251:32251:0123/132119.862878:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[32251:32251:0123/132119.865704:ERROR:angle_platform_impl.cc(44)] Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not create a backing OpenGL context.
[32251:32251:0123/132119.865808:ERROR:gl_surface_egl.cc(783)] EGL Driver message (Critical) eglInitialize: Could not create a backing OpenGL context.
[32251:32251:0123/132119.866036:ERROR:gl_surface_egl.cc(1391)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[32251:32251:0123/132119.866206:ERROR:gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
[32251:32251:0123/132119.870342:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[32343:32343:0123/132119.961357:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is disabled, ANGLE is
Fontconfig error: Cannot load default config file
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
----------------
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
Regards,
Karl <k...@karlpinc.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Andres Salomon
Jan 23, 2022, 4:10:05 PM1/23/22
to
On 1/23/22 14:52, Salvatore Bonaccorso wrote:
> Source: chromium
> Source-Version: 97.0.4692.99-1~deb11u1
> bugs on it for the remaining issues, okay? Andres?
>
Thanks!
Karl, the remaining error messages are either benign (like the "stack
smashing detected" ones, which are due to the older version of clang in
bullseye and don't show up in newer versions of clang), or seem to be
related to lack of hardware support from libgl1-mesa-dri. The next steps
to dealing with the mesa issues are trying out a backport of
libgl1-mesa-dri to see if it works better for you, and also going
through mesa's bug list to see if your specific radeonsi issues have
already been reported and/or solved. Your specific gpu hardware would be
listed in the output of chrome://gpu, if that's helpful for reporting a
mesa bug or following up on an existing one.
For the record, I don't know why the new release fixed your issue with
the --temp-profile window. Seems like an upstream chromium bug that got
fixed, as the debian side of things (for X11 at least) remained the
same. ¯\_(ツ)_/¯
At some point I hope to start including swiftshader with chromium, which
would provide an admittedly slow but functional software fallback for
folks whose GL hardware implementations are lacking or broken.
> Source: chromium
> Source-Version: 97.0.4692.99-1~deb11u1
>
> On Sun, Jan 23, 2022 at 01:30:04PM -0600, Karl O. Pinc wrote:
>> Hello,
>>
>> Upgrading to the latest chromium seems to have fixed the
>> problem of the window being displayed as a white box
>> without any controls.
>>
>>
>> Upgrade: chromium-sandbox:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium-common:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2)
>>
>>
>> Note that I am still getting plenty of error messages
>> on stdout/stderr when invoking chromium --temp-profile
>> from the command line. See below.
>>
>> You may want to close this bug. I would be happy to file
>> a separate bug report(s) for any of the error messages
>> below, however you would advise.
> Doing so now, but leaving it to the maintainers if they want separate
> On Sun, Jan 23, 2022 at 01:30:04PM -0600, Karl O. Pinc wrote:
>> Hello,
>>
>> Upgrading to the latest chromium seems to have fixed the
>> problem of the window being displayed as a white box
>> without any controls.
>>
>>
>> Upgrade: chromium-sandbox:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2), chromium-common:amd64 (97.0.4692.71-0.1~deb11u1, 97.0.4692.99-1~deb11u2)
>>
>>
>> Note that I am still getting plenty of error messages
>> on stdout/stderr when invoking chromium --temp-profile
>> from the command line. See below.
>>
>> You may want to close this bug. I would be happy to file
>> a separate bug report(s) for any of the error messages
>> below, however you would advise.
> bugs on it for the remaining issues, okay? Andres?
>
Thanks!
Karl, the remaining error messages are either benign (like the "stack
smashing detected" ones, which are due to the older version of clang in
bullseye and don't show up in newer versions of clang), or seem to be
related to lack of hardware support from libgl1-mesa-dri. The next steps
to dealing with the mesa issues are trying out a backport of
libgl1-mesa-dri to see if it works better for you, and also going
through mesa's bug list to see if your specific radeonsi issues have
already been reported and/or solved. Your specific gpu hardware would be
listed in the output of chrome://gpu, if that's helpful for reporting a
mesa bug or following up on an existing one.
For the record, I don't know why the new release fixed your issue with
the --temp-profile window. Seems like an upstream chromium bug that got
fixed, as the debian side of things (for X11 at least) remained the
same. ¯\_(ツ)_/¯
At some point I hope to start including swiftshader with chromium, which
would provide an admittedly slow but functional software fallback for
folks whose GL hardware implementations are lacking or broken.
Karl O. Pinc
Jan 23, 2022, 4:50:03 PM1/23/22
to
Thanks for the help.
FWIW, if you didn't notice, in the original bug report
I note that I'm using X over the network -- with
client and server on different boxes.
Video playback stopped working (meaning: I get
maybe a frame a second-ish (with avplay/vlc ?)) somewhere around
Stretch. It worked for years before that.
(But I never tried to play video in a browser,
except perhaps by accident, and can't speak
to what chromium did.)
On Sun, 23 Jan 2022 15:57:38 -0500
Andres Salomon <dili...@queued.net> wrote:
> Karl, the remaining error messages are either benign (like the "stack
> smashing detected" ones, which are due to the older version of clang
> in bullseye and don't show up in newer versions of clang), or seem to
> be related to lack of hardware support from libgl1-mesa-dri. The next
> steps to dealing with the mesa issues are trying out a backport of
> libgl1-mesa-dri to see if it works better for you, and also going
> through mesa's bug list to see if your specific radeonsi issues have
> already been reported and/or solved. Your specific gpu hardware would
> be listed in the output of chrome://gpu, if that's helpful for
> reporting a mesa bug or following up on an existing one.
I will dig into it. (I'm never sure what/how video acceleration
is supposed to work with the client and server on different boxes.)
It may take a while for me to look around. As you may guess,
I don't care much about video.
> For the record, I don't know why the new release fixed your issue
> with the --temp-profile window. Seems like an upstream chromium bug
> that got fixed, as the debian side of things (for X11 at least)
> remained the same. ¯\_(ツ)_/¯
>
> At some point I hope to start including swiftshader with chromium,
> which would provide an admittedly slow but functional software
> fallback for folks whose GL hardware implementations are lacking or
> broken.
FWIW, if you didn't notice, in the original bug report
I note that I'm using X over the network -- with
client and server on different boxes.
Video playback stopped working (meaning: I get
maybe a frame a second-ish (with avplay/vlc ?)) somewhere around
Stretch. It worked for years before that.
(But I never tried to play video in a browser,
except perhaps by accident, and can't speak
to what chromium did.)
On Sun, 23 Jan 2022 15:57:38 -0500
Andres Salomon <dili...@queued.net> wrote:
> Karl, the remaining error messages are either benign (like the "stack
> smashing detected" ones, which are due to the older version of clang
> in bullseye and don't show up in newer versions of clang), or seem to
> be related to lack of hardware support from libgl1-mesa-dri. The next
> steps to dealing with the mesa issues are trying out a backport of
> libgl1-mesa-dri to see if it works better for you, and also going
> through mesa's bug list to see if your specific radeonsi issues have
> already been reported and/or solved. Your specific gpu hardware would
> be listed in the output of chrome://gpu, if that's helpful for
> reporting a mesa bug or following up on an existing one.
is supposed to work with the client and server on different boxes.)
It may take a while for me to look around. As you may guess,
I don't care much about video.
> For the record, I don't know why the new release fixed your issue
> with the --temp-profile window. Seems like an upstream chromium bug
> that got fixed, as the debian side of things (for X11 at least)
> remained the same. ¯\_(ツ)_/¯
>
> At some point I hope to start including swiftshader with chromium,
> which would provide an admittedly slow but functional software
> fallback for folks whose GL hardware implementations are lacking or
> broken.
Karl O. Pinc
Jan 26, 2022, 12:20:04 PM1/26/22
to
Hello,
Looks like this is _not_ fixed. It appears
to be a race condition. Sometimes it happens,
sometimes not.
Let me know if you need a new bug report filed.
I notice that, although window borders and other controls are
not displayed, the cursor still seems to respond
to being over the window controls. I.e., when
hovering over the edge of the "white box" the cursor
(in xfce4) changes to the "arrow with the bar at tip"
and I can grab the edge and resize the box. Likewise,
I can move the box by "grabbing" where I would expect
the title bar to be. And clicking where the close-box
for the window should be makes the application close.
Looks like this is _not_ fixed. It appears
to be a race condition. Sometimes it happens,
sometimes not.
Let me know if you need a new bug report filed.
I notice that, although window borders and other controls are
not displayed, the cursor still seems to respond
to being over the window controls. I.e., when
hovering over the edge of the "white box" the cursor
(in xfce4) changes to the "arrow with the bar at tip"
and I can grab the edge and resize the box. Likewise,
I can move the box by "grabbing" where I would expect
the title bar to be. And clicking where the close-box
for the window should be makes the application close.
0 new messages