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