Linux print with browser.tabs.remote.autostart true yields "Loading content to print, preparation ..." but without reaching the print window
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: antdev66, Unassigned)
Details
(Whiteboard: [closeme 2024-01-04])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
open a mail and press print button on toolbar
Actual results:
thunderbird crash
Expected results:
note: if I press the print button from the print preview form then everything works
release: 60.5.3 (64 bit) linux version
Comment 1•7 years ago
|
||
Do you get a crash ID?
see https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
(In reply to Wayne Mery (:wsmwk) from comment #1)
Do you get a crash ID?
see https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
mar 6 08:30 bp-5035f3d2-0289-4b66-9721-fe0540190306.txt
mar 6 09:08 bp-a9a56a38-4cc8-4ba8-a1fc-e38860190306.txt
Comment 3•7 years ago
|
||
Are those the only two?
(In reply to Wayne Mery (:wsmwk) from comment #3)
Are those the only two?
There are three in total (one was a few days ago)
mar 1 13:43 bp-da049d8a-5758-40a4-ab36-777b90190301.txt
mar 6 08:30 bp-5035f3d2-0289-4b66-9721-fe0540190306.txt
mar 6 09:08 bp-a9a56a38-4cc8-4ba8-a1fc-e38860190306.txt
Comment 5•7 years ago
|
||
Please start in safe mode https://support.mozilla.org/en-US/kb/safe-mode-thunderbird#w_how-to-start-thunderbird-in-safe-mode
Does crash go away?
(In reply to Wayne Mery (:wsmwk) from comment #5)
Please start in safe mode https://support.mozilla.org/en-US/kb/safe-mode-thunderbird#w_how-to-start-thunderbird-in-safe-mode
Does crash go away?
Yes, crash again (I clicked "Print" from File menu)
Comment 7•7 years ago
|
||
Please post that last crash ID
(In reply to Wayne Mery (:wsmwk) from comment #7)
Please post that last crash ID
mar 7 12:12 bp-29e97e0a-8ba1-496d-a2b0-6ddd90190307.txt
can help?
root@OFFICE:~$ gdb --args thunderbird --safe-mode
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 http://gnu.org/licenses/gpl.html
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:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from thunderbird...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/local/workspace/bin/thunderbird --safe-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 26516]
[New Thread 0x7fffebaba700 (LWP 26517)]
[Thread 0x7fffebaba700 (LWP 26517) exited]
[Detaching after fork from child process 26518]
[New Thread 0x7fffebaba700 (LWP 26520)]
[New Thread 0x7fffe80ff700 (LWP 26521)]
[New Thread 0x7fffe78fe700 (LWP 26522)]
[New Thread 0x7fffe6eff700 (LWP 26523)]
[New Thread 0x7fffe66fe700 (LWP 26524)]
[New Thread 0x7fffe64fd700 (LWP 26525)]
[New Thread 0x7fffe62fc700 (LWP 26526)]
[New Thread 0x7fffe60fb700 (LWP 26527)]
[New Thread 0x7fffe58ff700 (LWP 26528)]
[New Thread 0x7fffe56fe700 (LWP 26529)]
[New Thread 0x7fffe54fd700 (LWP 26530)]
[New Thread 0x7fffe4aff700 (LWP 26531)]
[New Thread 0x7fffe42fe700 (LWP 26532)]
[New Thread 0x7fffe3afd700 (LWP 26533)]
[New Thread 0x7fffe2fff700 (LWP 26534)]
[Detaching after fork from child process 26535]
[New Thread 0x7fffe27fe700 (LWP 26536)]
[New Thread 0x7fffe1ffd700 (LWP 26537)]
[New Thread 0x7fffe70fd700 (LWP 26538)]
[New Thread 0x7fffe14ff700 (LWP 26539)]
[New Thread 0x7fffe04ff700 (LWP 26543)]
[Thread 0x7fffe2fff700 (LWP 26534) exited]
[New Thread 0x7fffe2fff700 (LWP 26548)]
[New Thread 0x7fffdeeff700 (LWP 26553)]
[New Thread 0x7fffde6fe700 (LWP 26554)]
[New Thread 0x7fffddefd700 (LWP 26555)]
[New Thread 0x7fffe0c4b700 (LWP 26556)]
[New Thread 0x7fffdcf46700 (LWP 26557)]
(thunderbird:26504): Gtk-WARNING **: 20:08:40.381: Theme parsing error: <data>:1:34: Expected ')' in color definition
(thunderbird:26504): Gtk-WARNING **: 20:08:40.381: Theme parsing error: <data>:1:77: Expected ')' in color definition
[New Thread 0x7fffdc238700 (LWP 26558)]
[New Thread 0x7fffdba37700 (LWP 26559)]
[New Thread 0x7fffdb236700 (LWP 26560)]
[New Thread 0x7fffdaa35700 (LWP 26561)]
[New Thread 0x7fffda234700 (LWP 26562)]
[Thread 0x7fffe1ffd700 (LWP 26537) exited]
[New Thread 0x7fffd97ff700 (LWP 26563)]
[New Thread 0x7fffdd346700 (LWP 26564)]
[New Thread 0x7fffdc745700 (LWP 26565)]
[New Thread 0x7fffd8ffe700 (LWP 26566)]
[New Thread 0x7fffe1ffd700 (LWP 26567)]
[Thread 0x7fffe04ff700 (LWP 26543) exited]
[New Thread 0x7fffe04ff700 (LWP 26568)]
[New Thread 0x7fffd82ff700 (LWP 26569)]
[New Thread 0x7fffd6fff700 (LWP 26570)]
[Thread 0x7fffdaa35700 (LWP 26561) exited]
[Thread 0x7fffdba37700 (LWP 26559) exited]
[Thread 0x7fffdc238700 (LWP 26558) exited]
[New Thread 0x7fffdc238700 (LWP 26606)]
[New Thread 0x7fffdaa35700 (LWP 26607)]
[New Thread 0x7fffdba37700 (LWP 26608)]
[New Thread 0x7fffd607b700 (LWP 26609)]
[New Thread 0x7fffd56ff700 (LWP 26610)]
[Thread 0x7fffdc238700 (LWP 26606) exited]
[New Thread 0x7fffdc238700 (LWP 26619)]
[New Thread 0x7fffd6f4b700 (LWP 26620)]
[Thread 0x7fffe1ffd700 (LWP 26567) exited]
[New Thread 0x7fffe1ffd700 (LWP 26637)]
[New Thread 0x7fffd0bff700 (LWP 26638)]
[New Thread 0x7fffd03fe700 (LWP 26639)]
[New Thread 0x7fffcfbfd700 (LWP 26640)]
[New Thread 0x7fffcdeff700 (LWP 26641)]
[New Thread 0x7fffcd6fe700 (LWP 26642)]
[New Thread 0x7fffccefd700 (LWP 26643)]
[New Thread 0x7fffcc4ff700 (LWP 26644)]
[New Thread 0x7fffcbcfe700 (LWP 26645)]
[New Thread 0x7fffcf3fc700 (LWP 26646)]
[New Thread 0x7fffcb0ff700 (LWP 26647)]
[New Thread 0x7fffca6ff700 (LWP 26648)]
[New Thread 0x7fffc97ff700 (LWP 26649)]
[New Thread 0x7fffc8cff700 (LWP 26650)]
[New Thread 0x7fffc81ff700 (LWP 26656)]
[New Thread 0x7fffc32ff700 (LWP 26668)]
[New Thread 0x7fffbe1ff700 (LWP 26725)]
[New Thread 0x7fffbd9fe700 (LWP 26726)]
[New Thread 0x7fffbcb8c700 (LWP 26727)]
[Thread 0x7fffbcb8c700 (LWP 26727) exited]
[Thread 0x7fffbd9fe700 (LWP 26726) exited]
[Thread 0x7fffdb236700 (LWP 26560) exited]
[New Thread 0x7fffbcb8c700 (LWP 26736)]
when print:
Thread 1 "thunderbird" received signal SIGSEGV, Segmentation fault.
0x00007ffff7fe723d in _dl_update_slotinfo (req_modid=10) at ../elf/dl-tls.c:727
727 ../elf/dl-tls.c: File o directory non esistente.
(gdb) bt
#0 0x00007ffff7fe723d in _dl_update_slotinfo (req_modid=10) at ../elf/dl-tls.c:727
#1 0x00007ffff7fe729c in update_get_addr (ti=0x7ffff299d7d0) at ../elf/dl-tls.c:799
#2 0x00007ffff7fec188 in __tls_get_addr () at ../sysdeps/x86_64/tls_get_addr.S:55
#3 0x00007fffecc0bf70 in () at /usr/local/thunderbird/libxul.so
#4 0x00007fffee969f4d in () at /usr/local/thunderbird/libxul.so
#5 0x00007fffed3391b3 in () at /usr/local/thunderbird/libxul.so
#6 0x00007fffed33b8cd in () at /usr/local/thunderbird/libxul.so
#7 0x00007fffed318fbd in () at /usr/local/thunderbird/libxul.so
...
Comment 10•7 years ago
|
||
Walt, does this reproduce for you?
Comment 11•7 years ago
|
||
Not for me using Thunderbird 60.5.3 on Linux Mint 19.1 or Ubuntu 18.04.2 using the Linux 4.15.0-46-generic kernel.
The crash reports indicate the reporter is using "OS Version 0.0.0 Linux 5.0.0-custom #1" as the kernel for GNU gdb (Debian 8.2.1-2) 8.2.1.
I can only find kernel information for Debian 9 and it is using the 4.9 kernel version.
I can't speculate on how the reporter is using Debian 8.2.1-2 with kernel 5.0.0-custom. Possible cause of the problem?
Comment 12•7 years ago
|
||
FWIW Linux Kernel 5.0 was released on March 3, 2019.
| Reporter | ||
Comment 13•7 years ago
|
||
After some tests I realized that the problem was in the prefs.js file.
Comparing it with a previously saved file, I found that by removing this line in the current prefs.js, everything works fine:
user_pref ("browser.tabs.remote.autostart", true);
Now when I press the Print button the print dialog box appears correctly.
Thank you,
Antonio
Comment 14•7 years ago
|
||
(In reply to WaltS48 [:walts48] from comment #11)
Not for me using Thunderbird 60.5.3 on Linux Mint 19.1 or Ubuntu 18.04.2 using the Linux 4.15.0-46-generic kernel.
How about if you change browser.tabs.remote.autostart to true?
Comment 15•7 years ago
|
||
With browser.tabs.remote.autostart set to true TB 60.5.3 on Linux Mint 19.1 crashed when I used the Print button after restarting TB.
https://crash-stats.mozilla.com/report/index/2e7a2f83-1761-4f3d-946c-8bc810190311
Updated•7 years ago
|
Updated•6 years ago
|
Comment 16•6 years ago
|
||
Does that crash printing in FF? What does that pref do?
Comment 17•6 years ago
|
||
(In reply to Jorg K (GMT+2) from comment #16)
Does that crash printing in FF? What does that pref do?
Printing does not crash in Firefox.
The "browser.tabs.remote.autostart" pref is set to "true" in Firefox by default, and "false" in Thunderbird by default.
It enables Electrolysis in Firefox.
Comment 18•6 years ago
|
||
(In reply to WaltS48 [:walts48] from comment #15)
With browser.tabs.remote.autostart set to true TB 60.5.3 on Linux Mint 19.1 crashed when I used the Print button after restarting TB.
https://crash-stats.mozilla.com/report/index/2e7a2f83-1761-4f3d-946c-8bc810190311
Also still with 68?
And does browser.tabs.remote.autostart exist with true in the default Thunderbird config?
| Reporter | ||
Comment 19•6 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #18)
(In reply to WaltS48 [:walts48] from comment #15)
With browser.tabs.remote.autostart set to true TB 60.5.3 on Linux Mint 19.1 crashed when I used the Print button after restarting TB.
https://crash-stats.mozilla.com/report/index/2e7a2f83-1761-4f3d-946c-8bc810190311
Also still with 68?
And does browser.tabs.remote.autostart exist with true in the default Thunderbird config?
- the current version is 68.2.0
- browser.tabs.remote.autostart is present in my configuration and is setted to false
- I tried to put it on true, restarted and repeated the text: now thunderbird does not crash but locks on the dialog box "Loading content to print, preparation ..." but without reaching the print window (however thunderbird continues to work); if I set the flag to false (and restart) it works fine again.
Comment 20•6 years ago
•
|
||
(In reply to Wayne Mery (:wsmwk) from comment #18)
(In reply to WaltS48 [:walts48] from comment #15)
With browser.tabs.remote.autostart set to true TB 60.5.3 on Linux Mint 19.1 crashed when I used the Print button after restarting TB.
https://crash-stats.mozilla.com/report/index/2e7a2f83-1761-4f3d-946c-8bc810190311
Also still with 68?
And does browser.tabs.remote.autostart exist with true in the default Thunderbird config?
browser.tabs.remote.autostart is false by default.
No crash with 68.2.0 on Linux Mint 19.2, but none of the message bodies show in the Message pane, new tab or new window.
If I click the print button I get a "(Loading content for Printing.) Preparing..." dialog window and the printer dialog window doesn't open.
I get the same behavior with 68.2.0 on Ubuntu 18.04.3 LTS with browser.tabs.remote.autostart set to true.
Comment 21•6 years ago
|
||
For simplicity, let's just morph this
Comment 22•2 years ago
|
||
Does this reproduce with a newer version? 102 or (preferably) 115?
| Reporter | ||
Comment 23•2 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #22)
Does this reproduce with a newer version? 102 or (preferably) 115?
I currently use the 115.5.2 (64 bit) version and the problem seems to have been resolved
("browser.tabs.remote.autostart" is set to "true" by default)
Comment 24•2 years ago
|
||
Great. Thanks for the update.
Description
•