All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104762] Various segfaults/problems in qt/plasma
Date: Wed, 24 Jan 2018 09:26:53 +0000	[thread overview]
Message-ID: <bug-104762-502-jfGxaPT241@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104762-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Christoph Haag <haagch@frickel.club> ---
Created attachment 136932
  --> https://bugs.freedesktop.org/attachment.cgi?id=136932&action=edit
systemsettings black

I think I have tried running with valgrind before. I tried valgrind with -Og
mesa rendering the black window, but no (relevant) errors comes up.

To describe one case:
I just tried a mesa debug build and everything worked normal.
Then with the same options, but a release build with additionally CFLAGS=-Og
CXXFLAGS=-Og renders systemsettings5 and plasmashell completely black. No
segfaults this time. Starting plasmashell and systemsettings with
MESA_EXTENSION_OVERRIDE=-GL_ARB_get_program_binary makes it display normally.
But starting it without the variable after that makes it black again. Deleting
the shader cache does not help in this case.

But after starting systemsettings5 with another mesa installation once, it
starts working normally with the mesa build that produced the black window just
before too.

It's possible the segfaults and the black windows are different problems but
they started happening at the same time.

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

[-- Attachment #1.2: Type: text/html, Size: 2170 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

  parent reply	other threads:[~2018-01-24  9:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24  8:51 [Bug 104762] Various segfaults/problems in qt/plasma bugzilla-daemon
2018-01-24  9:00 ` bugzilla-daemon
2018-01-24  9:26 ` bugzilla-daemon [this message]
2018-01-24 10:33 ` bugzilla-daemon
2018-01-24 14:59 ` bugzilla-daemon
2018-01-25  1:31 ` bugzilla-daemon
2018-01-25  3:59 ` bugzilla-daemon
2018-01-25  8:36 ` bugzilla-daemon
2018-01-25 10:33 ` bugzilla-daemon
2018-01-25 10:56 ` bugzilla-daemon
2018-01-26  0:58 ` bugzilla-daemon
2018-01-26 23:11 ` bugzilla-daemon
2018-01-30  9:25 ` bugzilla-daemon
2018-01-30 10:13 ` bugzilla-daemon
2018-01-31  1:18 ` bugzilla-daemon
2018-02-05  7:07 ` bugzilla-daemon
2018-02-05  8:43 ` bugzilla-daemon
2018-02-05  9:41 ` bugzilla-daemon
2018-02-12  9:00 ` bugzilla-daemon
2018-02-14 22:41 ` 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-104762-502-jfGxaPT241@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.