dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100984] QupZilla crashes at startup after mesa upgrade
Date: Wed, 10 May 2017 05:27:22 +0000	[thread overview]
Message-ID: <bug-100984-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2003 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100984

            Bug ID: 100984
           Summary: QupZilla crashes at startup after mesa upgrade
           Product: Mesa
           Version: 17.1
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/i915
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: fturco@fastmail.fm
        QA Contact: dri-devel@lists.freedesktop.org

Since I upgraded media-libs/mesa from version 17.0.4 to version 17.1.0_rc4 I
cannot start QupZilla anymore because it produces a segmentation fault. I have
an Intel GPU (Q35 chipset). My GNU/Linux distribution is Gentoo.

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated
Graphics Controller (rev 02)

# emerge -pv qupzilla mesa

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] www-client/qupzilla-2.1.2::gentoo  USE="dbus -debug
-gnome-keyring -kwallet -libressl -nonblockdialogs" LINGUAS="-ar_SA -bg_BG
-ca_ES -cs_CZ -da_DK -de_DE -el_GR -es_ES -es_MX -es_VE -eu_ES -fa_IR -fi_FI
-fr_FR -gl_ES -he_IL -hr_HR -hu_HU -id_ID -is -it_IT -ja_JP -ka_GE -lg -lt
-lv_LV -nl_NL -nqo -pl_PL -pt_BR -pt_PT -ro_RO -ru_RU -sk_SK -sr -sr@ijekavian
-sr@ijekavianlatin -sr@latin -sv_SE -tr_TR -uk_UA -uz@Latn -zh_CN -zh_HK
-zh_TW" 2,703 KiB
[ebuild   R    ] media-libs/mesa-17.1.0_rc4::gentoo  USE="classic debug dri3
egl gallium gbm nptl -bindist -d3d9 -gles1 -gles2 -llvm -opencl -openmax
-osmesa -pax_kernel -pic (-selinux) -vaapi -valgrind -vdpau -vulkan -wayland
-xa -xvmc" VIDEO_CARDS="i915 intel (-freedreno) -i965 -imx -nouveau -r100 -r200
-r300 -r600 -radeon -radeonsi (-vc4) (-vivante) -vmware" 0 KiB

Total: 2 packages (2 reinstalls), Size of downloads: 2,703 KiB

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3430 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-05-10  5:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  5:27 bugzilla-daemon [this message]
2017-05-10  5:28 ` [Bug 100984] QupZilla crashes at startup after mesa upgrade bugzilla-daemon
2017-05-10  5:29 ` bugzilla-daemon
2017-05-11 15:34 ` bugzilla-daemon
2017-05-11 15:56 ` bugzilla-daemon
2017-05-11 20:50 ` bugzilla-daemon
2017-05-11 21:31 ` bugzilla-daemon
2017-05-14 22:13 ` bugzilla-daemon
2017-05-14 22:14 ` bugzilla-daemon
2017-05-15  9:17 ` bugzilla-daemon
2017-05-20 12:15 ` bugzilla-daemon
2017-08-14 19:43 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-100984-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).