What did you do? (steps to reproduce) ------------------------------------- -untick the checkbox "Title Bar" at "Customize Firefox" What happened? (actual results) ------------------------------- - Firefox crashes What should have happened? (expected results) --------------------------------------------- - the title bar should be hidden, when it is supported - when it isn't supported, the checkbox should be grey-out - Firefox shouldn't crash Further information: ------------------- - operating system: Debian Jessie(8.10), with KDE4 - crash report: https://crash-stats.mozilla.com/report/index/92e5e3f0-10bd-49dc-b697-9a0881180521
I see you report that from 60.0.1 build according to the Build ID 20180516032328. Can you please try latest nightly from https://www.mozilla.org/en-US/firefox/channel/desktop/ ?
Assignee: nobody → stransky
Also, which Gtk+ version do you have installed?
The crash somes from oxygen-gtk - I suspect we pass some wrong arguments to some widget rendering (at moz_gtk_button_paint like zero with/height or so) which can cause the crash.
(In reply to Martin Stránský [:stransky] from comment #1) > I see you report that from 60.0.1 build according to the Build ID > 20180516032328. Can you please try latest nightly from > https://www.mozilla.org/en-US/firefox/channel/desktop/ ? The Problem does exist in 62.0a1 too. And my Gtk+ version is: Package: libgtk-3-0 State: installed Automatically installed: yes Multi-Arch: same Version: 3.14.5-1+deb8u1
Ondrej, can you look at it please?
Assignee: stransky → ozoder
I tried to reproduce this bug on Debian 8.10, gtk 3.14.5-1, Firefox 61/62 with the oxygen theme and everything works well for me. Could you please try to run Firefox with a fresh profile/in a safe mode, if this problem persists? If it does, could you please capture a video of the crash happening?
Please reopen if you still see that, Thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → WORKSFORME
I just got this problem myself. Everything happens just like in dheddicke's report. I started having this problem after updating the following packages on my archlinux system: gtk-update-icon-cache (3.24.1+8+g220f77d8c1-1 -> 3.24.1+155+g4c8fcd6a6f-1) gtk3 (3.24.1+8+g220f77d8c1-1 -> 3.24.1+155+g4c8fcd6a6f-1) firefox (63.0.3-1 -> 64.0-1) libteam (1.27-2 -> 1.28-1) If I run Firefox from a terminal after a crash I get some warnings: (firefox:5760): Gtk-WARNING **: 20:30:08.346: Theme parsing error: <data>:1:34: Expected ')' in color definition (firefox:5760): Gtk-WARNING **: 20:30:08.346: Theme parsing error: <data>:1:77: Expected ')' in color definition (firefox:5760): Gdk-WARNING **: 20:30:24.568: Can't set ParentRelative background for window 0x2c00079, depth of parent doesn't match And then, when I untick the checkbox I get this: (firefox:5760): Gdk-ERROR **: 20:30:34.471: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 56114 error_code 8 request_code 7 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 6016 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Trace/breakpoint trap (core dumped) I hope this helps.
After today's system upgrade I no longer have this issue. Updated packages: [2018-12-13 17:24] [ALPM] upgraded gtk-update-icon-cache (3.24.1+155+g4c8fcd6a6f-1 -> 3.24.2+1+g2905fc861a-1) [2018-12-13 17:24] [ALPM] upgraded gtk3 (3.24.1+155+g4c8fcd6a6f-1 -> 3.24.2+1+g2905fc861a-1) [2018-12-13 17:24] [ALPM] upgraded electron (3.0.10-1 -> 3.0.11-1) [2018-12-13 17:24] [ALPM] upgraded libatomic_ops (7.6.6-1 -> 7.6.8-1)
You need to log in before you can comment on or make changes to this bug.