From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] qt5-webengine: broken on musl
Date: Tue, 12 May 2020 01:45:30 +0200 [thread overview]
Message-ID: <20200511234530.rjT7VG0C0ePJC8KsQVqfLRP0K9__9hrzsxMCxk_vXOA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-2368@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
Closed issue by joeblo1 on void-packages repository
https://github.com/void-linux/void-packages/issues/2368
Description:
### System
* xuname: Void 4.18.5_1 x86_64-musl GenuineIntel uptodate rDDDDDF
*output of ``xuname`` (part of xtools)*
* package: falkon
*affected package(s) including the version*
### Expected behavior
...to not flicker? :P
### Actual behavior
flickering black non-stop
### Steps to reproduce the behavior
Happened after update, have cleared mesa shaders & falkon folder in ~/.cache already, don't know if its just me or not. Sorry I'm not super knowledgeable about this stuff. I have tried creating another user to see if that would change anything but it did not.
prev parent reply other threads:[~2020-05-11 23:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-2368@inbox.vuxu.org>
2019-09-24 9:36 ` voidlinux-github
2019-09-24 10:35 ` voidlinux-github
2019-11-09 18:16 ` voidlinux-github
2019-11-09 18:19 ` voidlinux-github
2019-11-10 10:08 ` voidlinux-github
2019-11-11 0:32 ` voidlinux-github
2019-11-12 0:23 ` voidlinux-github
2019-11-12 4:42 ` voidlinux-github
2019-11-12 10:27 ` voidlinux-github
2020-05-11 22:13 ` ericonr
2020-05-11 23:45 ` Johnnynator
2020-05-11 23:45 ` Johnnynator [this message]
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=20200511234530.rjT7VG0C0ePJC8KsQVqfLRP0K9__9hrzsxMCxk_vXOA@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).