1 |
2018-07-27 23:02 GMT+03:00 Mick <michaelkintzios@×××××.com>: |
2 |
> On Friday, 27 July 2018 19:49:45 BST gevisz wrote: |
3 |
>> 2018-07-27 18:29 GMT+03:00 Mick <michaelkintzios@×××××.com>: |
4 |
>> > On Friday, 27 July 2018 14:00:43 BST gevisz wrote: |
5 |
>> >> 2018-07-27 15:44 GMT+03:00 gevisz <gevisz@×××××.com>: |
6 |
>> >> > Updating world without global -pam, -polkit and -consolekit use flags |
7 |
>> >> > in /etc/portage/make.conf have not changed the behaviour of Fireforx |
8 |
>> >> > described above: it is still cannot display the page |
9 |
>> >> > https://www.privat24.ua/ and shows "Gah. Your tab just crashed." |
10 |
>> >> > message. |
11 |
>> >> > |
12 |
>> >> > So, I will probably revert changes tomorrow. |
13 |
>> >> > |
14 |
>> >> > Playing with strace has been put on todo list. |
15 |
>> >> |
16 |
>> >> Last lines of the log file after runnig the following command |
17 |
>> >> |
18 |
>> >> $ strace -o strace.log qupzilla https://www.privat24.ua/ |
19 |
>> >> QupZilla: 0 extensions loaded |
20 |
>> >> [15707:15725:0727/155144.939329:ERROR:nss_util.cc(808)] After loading |
21 |
>> >> Root Certs, loaded==false: NSS error code: -8018 |
22 |
>> >> [15707:15719:0727/155145.900259:ERROR:nss_ocsp.cc(591)] No |
23 |
>> >> URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com |
24 |
>> > |
25 |
>> > Mozilla is using libnss to check the validity of the website certificate |
26 |
>> > with the OCSP of the CA issuer of the certificate (digicert.com). For |
27 |
>> > some reason it seems the connection is interrupted. See lines 605 to 621 |
28 |
>> > here: |
29 |
>> > |
30 |
>> > https://code.woboq.org/qt5/qtwebengine/src/3rdparty/chromium/net/cert_net/ |
31 |
>> > nss_ocsp.cc.html |
32 |
>> > |
33 |
>> > The connection may be interrupted because the browser/tab crashes (see |
34 |
>> > below).> |
35 |
>> >> r300 FP: Compiler Error: |
36 |
>> >> /var/tmp/portage/media-libs/mesa-17.3.9/work/mesa-17.3.9/src/gallium/driv |
37 |
>> >> ers /r300/compiler/r300_fragprog_emit.c::translate_rgb_opcode(): |
38 |
>> >> translate_rgb_opcode: Unknown opcode DDY |
39 |
>> >> Using a dummy shader instead. |
40 |
>> >> QupZilla: Crashed :( Saving backtrace in |
41 |
>> >> /home/gevis/.config/qupzilla/crashlog ... |
42 |
>> >> Backtrace successfully saved in |
43 |
>> >> /home/gevis/.config/qupzilla/crashlog/Crash-2018-07-27T15:51:49.txt |
44 |
>> >> zsh: abort strace -o strace.log qupzilla https://www.privat24.ua/ |
45 |
>> >> |
46 |
>> >> are the following: |
47 |
>> >> |
48 |
>> >> clock_gettime(CLOCK_MONOTONIC, {tv_sec=1167, tv_nsec=68524671}) = 0 |
49 |
>> >> ioctl(8, DRM_IOCTL_RADEON_GEM_MMAP, 0x7ffd31773280) = 0 |
50 |
>> >> mmap(NULL, 6868992, PROT_READ|PROT_WRITE, MAP_SHARED, 8, 0x107616000) |
51 |
>> >> = 0x7f22f5650000 |
52 |
>> >> +++ killed by SIGABRT +++ |
53 |
>> > |
54 |
>> > This looks like a radeon video driver problem. You could go into a loop |
55 |
>> > of |
56 |
>> > rebuilding xorg, mesa, dev-libs/nss, what-ever and see if things improve, |
57 |
>> > or you could wait for/keyword later versions of these packages. |
58 |
>> |
59 |
>> Thank you for the tip. In this case, I should first try reconfigure the |
60 |
>> kernel. |
61 |
>> > Alternatively, you could try reporting this to the application devs and |
62 |
>> > see |
63 |
>> > what they say. |
64 |
>> |
65 |
>> Do you mean developpers of FF/QZ? |
66 |
> |
67 |
> Yes, although unless this is a known bug they may point you to the devs of the |
68 |
> radeon drivers. I've been around this loop a couple of times (sigh ...) |
69 |
|
70 |
Ok. Thank you. |
71 |
|
72 |
It even more strengthens my impression than I should first |
73 |
play with reconfiguring the kernel. |
74 |
|
75 |
I will do it a bit later, when the summer heat becames more tolerable. :) |