Gentoo Archives: gentoo-user

From: gevisz <gevisz@×××××.com>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system
Date: Fri, 27 Jul 2018 08:16:42
Message-Id: CA+t6X7eP=6eGW8O==gmMBLc99TUNDdcM09Q=VS2MFGS1dxpHcA@mail.gmail.com
1 I have two Gentoo systems on the same AMD Athlon 64 X2 computer.
2
3 The old one was installed in July 2013 with
4 default/linux/amd64/13.0/desktop/gnome (stable)
5 profile and was updated till the middle of
6 July 2017. Initially it hosted Gnome2
7 but later I have switched to XFCE4.
8
9 The new one was installed in January-February 2018
10 with default/linux/amd64/17.0/desktop (stable)
11 profile and was last updated yesterday. From the
12 very beginning it hosted no DE, only Awesome WM
13 and dbus.
14
15 The home directory is the same and still remembers
16 Ubuntu 6.04 installation in 2006.
17
18 On the old system, I had the problem that chromium
19 very often (but not always!) asked me for some
20 (keyring?) password when I opened a new www-page.
21
22 Recompilation of it with different user flags did not help.
23
24 I thought that that was because of the gnome-keyring,
25 consolekit or policykit packages but without any proof.
26
27 So, while installing the new Gentoo system, I decided
28 to avoid installing any package that needs gnome-keyring,
29 consolekit or policykit packages.
30
31 I have also set -pam -consolekit and -policykit in my
32 /etc/portage/make.conf
33
34 Chromium indeed never asked me for the mentioned
35 above password on the new Gentoo system.
36
37 But I get another problem on the new Gentoo system:
38 Firefox and Qupzilla both crash on some (login) www-pages.
39
40 Namely, Firefox shows the "Gah. Your tab just crashed"
41 when I try to log into my Yahoo e-mail account.
42
43 This happens only after entering login and password,
44 so not good enough to reproduce.
45
46 However, it shows the same message just after staying
47 about 3-5 seconds on the following internet banking
48 login page: https://www.privat24.ua/#login
49 No login or password needed. :)
50
51 The last error messages sent to terminal by FF while I
52 try to open the last www-page are the following:
53
54 [Parent 4099] WARNING: pipe error (56): Connection reset by peer: file
55 /var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
56 line 322
57 [Parent 4099] WARNING: pipe error (57): Connection reset by peer: file
58 /var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
59 line 322
60
61 ###!!! [Parent][MessageChannel] Error:
62 (msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
63 send/recv
64
65 [Parent 4099] WARNING: pipe error (44): Connection reset by peer: file
66 /var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
67 line 322
68
69 ###!!! [Parent][MessageChannel] Error:
70 (msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
71 send/recv
72
73 [Parent 4099] WARNING: pipe error (47): Connection reset by peer: file
74 /var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
75 line 322
76 [Parent 4099] WARNING: pipe error (49): Connection reset by peer: file
77 /var/tmp/portage/www-client/firefox-52.8.0/work/firefox-52.8.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
78 line 322
79
80 ###!!! [Parent][MessageChannel] Error:
81 (msgtype=0x2C0083,name=PBrowser::Msg_Destroy) Channel error: cannot
82 send/recv
83
84 tabs.onUpdated event fired after context unloaded.
85 tabs.onUpdated event fired after context unloaded.
86 tabs.onUpdated event fired after context unloaded.
87 ...
88
89 As to the Qupzilla, it crashes on the page https://www.privat24.ua/#login
90 completely, with the following messages sent to terminal:
91
92 [4376:4387:0727/105105.178569:ERROR:nss_ocsp.cc(591)] No
93 URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
94 [4376:4387:0727/105105.178676:ERROR:nss_ocsp.cc(591)] No
95 URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
96 [4376:4387:0727/105105.178734:ERROR:nss_ocsp.cc(591)] No
97 URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
98 [4376:4387:0727/105105.182973:ERROR:nss_ocsp.cc(591)] No
99 URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
100 [4376:4387:0727/105105.183033:ERROR:nss_ocsp.cc(591)] No
101 URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
102 [4376:4387:0727/105105.183086:ERROR:nss_ocsp.cc(591)] No
103 URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
104 r300 FP: Compiler Error:
105 /var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/drivers/r300/compiler/r300_fragprog_emit.c::translate_rgb_opcode():
106 translate_rgb_opcode: Unknown opcode DDY
107 Using a dummy shader instead.
108 QupZilla: Crashed :( Saving backtrace in
109 /home/user/.config/qupzilla/crashlog ...
110 Backtrace successfully saved in
111 /home/user/.config/qupzilla/crashlog/Crash-2018-07-27T10:51:11.txt
112
113 The mentioned above crashlog file contains only the following:
114
115 Time: Fri Jul 27 10:51:11 2018
116 Qt version: 5.9.6 (compiled with 5.9.4)
117 QupZilla version: 2.2.5
118 Rendering engine: QtWebEngine
119
120 ============== BACKTRACE ==============
121 #0: qupzilla(+0x355b) [0x55691e37055b]
122 #1: /lib64/libc.so.6(+0x35c60) [0x7f3a568c3c60]
123 #2: [0x7f3a3c18d2c9]
124
125 Strange enough, but on the old Gentoo system Firefox does not crash on
126 the said www-pages.
127
128 I initially thought that all that because
129 I have set -consolekit and -policykit use
130 flags in my /etc/portage/make.conf on my
131 new Gentoo system but unsetting them
132 does not lead to any recompilation while running
133 # emerge --update --deep --with-bdeps=y --newuse --backtrack=100 --ask world
134
135 Any thoughts about this?

Replies

Subject Author
Re: [gentoo-user] Firefox crashes on some www-pages on a newer Gentoo system Mick <michaelkintzios@×××××.com>