From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Couple of issues with NVIDIA and ibus
Date: Mon, 16 Sep 2019 10:44:40 +0200 [thread overview]
Message-ID: <20190916084440.DV5tMRVsSeXuzSYX7CVPreSKTX20DCHvUCHgxjOkwiM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14464@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/14464#issuecomment-531689789
Comment:
> Ok! I'll try Void next year again, if I be alive, to see the progress of Void team in mitigating these issues.
You know, all here are just volunteers, so if you want to see issues fixed, the least minimum is to make a half decent bug report, a Video is always only a addition to a bug report if visualizing helps, but never the bug report itself.. I did take a look at the first minute of the vid, yep systemsttings5 is chrashing, why? IDK. There is no helpful indication and everything that would help resolving this is missing, no information at what it is printing to stdout/stderr, not backtrace, nothing that would help at all.
next prev parent reply other threads:[~2019-09-16 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 0:23 [ISSUE] " voidlinux-github
2019-09-15 13:26 ` voidlinux-github
2019-09-15 18:53 ` voidlinux-github
2019-09-15 18:54 ` voidlinux-github
2019-09-15 18:55 ` voidlinux-github
2019-09-15 19:03 ` voidlinux-github
2019-09-15 19:03 ` [ISSUE] [CLOSED] " voidlinux-github
2019-09-15 19:15 ` voidlinux-github
2019-09-16 8:44 ` voidlinux-github [this message]
2019-09-16 11:39 ` voidlinux-github
2019-09-16 11:40 ` voidlinux-github
2019-09-16 11:40 ` voidlinux-github
2019-09-16 11:41 ` voidlinux-github
2019-09-16 11:41 ` voidlinux-github
2019-09-16 11:46 ` 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=20190916084440.DV5tMRVsSeXuzSYX7CVPreSKTX20DCHvUCHgxjOkwiM@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).