Check boxes in crash reporter window are not visible

UNCONFIRMED
Unassigned

Status

SeaMonkey
General
UNCONFIRMED
2 years ago
2 years ago

People

(Reporter: Martin Mokrejs, Unassigned)

Tracking

SeaMonkey 2.43 Branch
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

2 years ago
Created attachment 8731892 [details]
crash-reporter1.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39
Build ID: 20151103174305

Steps to reproduce:

You should have filed two crash reported submitted by me through your seamonkey-2.43a1.en-US.linux-x86_64 official build. Let me add two screen snapshots showing the crash reporter's window does not show any black contour around the checkboxes to be ticked. I just accidentally enabled one of them because the window was just all in grey.

The window cannot be resized (I use Xfce4 window manager). Also, I cannot paste any text from my xterm into it.
(Reporter)

Comment 1

2 years ago
Created attachment 8731893 [details]
crash-reporter2.png

Comment 2

2 years ago
Do you have the same problem if you use GNOME or KDE?

To Triage people (Linux) go to http://people.mozilla.org/~tmielczarek/crashme/ and install the crashme extension. Go to addons manager and look for "Crash Me Now Advanced"
Select Options. Click on the crash me button.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
(Reporter)

Comment 3

2 years ago
Created attachment 8737746 [details]
checkboxes_in_wordpress_admin.png

OK, let me add this is a general issue with the browser core and not just a seamonkey issue. Here is a snapshot from a webpage rendered by Firefox 48.0a1 nightly:

Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0




Built from https://hg.mozilla.org/mozilla-central/rev/55d557f4d73ee58664bdf2fa85aaab555224722e

Build platform
target
x86_64-pc-linux-gnu
Build tools
Compiler 	Version 	Compiler flags
/usr/bin/ccache /builds/slave/m-cen-l64-ntly-000000000000000/build/src/gcc/bin/gcc 	4.8.5 	-Wall -Wempty-body -Wignored-qualifiers -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pthread -pipe
/usr/bin/ccache /builds/slave/m-cen-l64-ntly-000000000000000/build/src/gcc/bin/g++ 	4.8.5 	-Wall -Wc++11-compat -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=coverage-mismatch -Wno-error=free-nonheap-object -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -D_GLIBCXX_USE_CXX11_ABI=0 -pipe -g -fprofile-use -fprofile-correction -Wcoverage-mismatch -O3 -fno-omit-frame-pointer -Werror
Configure arguments

--enable-crashreporter --enable-elf-hack --enable-release --enable-rust --enable-stdcxx-compat --enable-update-channel=nightly --enable-update-packaging --enable-verify-mar --enable-warnings-as-errors --with-branding=browser/branding/nightly --with-google-api-keyfile=/builds/gapi.data --with-google-oauth-api-keyfile=/builds/google-oauth-api.key --with-mozilla-api-keyfile=/builds/mozilla-desktop-geoloc-api.key --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --enable-js-shell --disable-sm-promise --disable-shared-js --disable-export-js --disable-instruments --disable-callgrind --enable-profiling --enable-vtune --without-compiler-wrapper --with-ccache --without-toolchain-prefix
(Reporter)

Comment 4

2 years ago
(In reply to Philip Chee from comment #2)
> Do you have the same problem if you use GNOME or KDE?

I cannot log off but provided old seamonkey-2.39 renders fine I don't think it is anyhow related to window manager (and why should it be?).
You need to log in before you can comment on or make changes to this bug.