From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Graphical Corruption on Chromium Apps with Mesa 19.0.5
Date: Wed, 05 Jun 2019 00:10:04 +0200 [thread overview]
Message-ID: <20190604221004.0W5iNklsi13-dYVWjudjHPFwF0rDxy_KTWVG7BqLdeQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
New comment by Syndicate6690 on void-packages repository
https://github.com/void-linux/void-packages/issues/11907#issuecomment-498862151
Comment:
I do kind of agree with the idea that if it's broken and you can fix it with xbps-src and git you should do that yourself. But, as a new user just switching to Void, this is a real turn-off. Most people who have this issue just blame the distribution and switch away. Not everyone has the time to narrow it down to mesa's ATI driver (radeonsi), find the package and go compile a old version. People use their systems in their daily lives, and yes you could argue that issues happen and if you care about stability maybe rolling distros aren't for you, but when there is an issue, why not roll it back for everyone and fix it?
next prev parent reply other threads:[~2019-06-04 22:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
2019-05-30 15:30 ` voidlinux-github
2019-05-30 22:15 ` voidlinux-github
2019-06-01 12:10 ` voidlinux-github
2019-06-01 18:56 ` voidlinux-github
2019-06-01 19:20 ` voidlinux-github
2019-06-01 22:00 ` voidlinux-github
2019-06-02 0:23 ` voidlinux-github
2019-06-02 0:26 ` voidlinux-github
2019-06-02 0:29 ` voidlinux-github
2019-06-02 4:11 ` voidlinux-github
2019-06-02 15:32 ` voidlinux-github
2019-06-02 20:55 ` voidlinux-github
2019-06-03 0:21 ` voidlinux-github
2019-06-03 1:36 ` voidlinux-github
2019-06-03 1:42 ` voidlinux-github
2019-06-03 1:44 ` voidlinux-github
2019-06-04 9:05 ` voidlinux-github
2019-06-04 9:11 ` voidlinux-github
2019-06-04 11:30 ` voidlinux-github
2019-06-04 22:10 ` voidlinux-github [this message]
2019-06-04 23:02 ` voidlinux-github
2019-06-06 11:06 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190604221004.0W5iNklsi13-dYVWjudjHPFwF0rDxy_KTWVG7BqLdeQ@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).