Re: Regarding behaviour of Gnome and Fedora members
by Ty Young
On 6/12/20 6:33 AM, Bastien Nocera wrote:
> On Fri, 2020-06-12 at 05:50 -0500, Ty Young via desktop-devel-list
> wrote:
>> So, could anything be done about any of this?
> You said you were leaving 8 months ago:
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1661#note_609870
>
> I think it might be a good idea if you did.
>
> You can use this link to ask for your gitlab account to be closed:
> https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/new?issue...
>
That was in regards to Gitlab, not Reddit and in general is irrelevant.
Reddit is a website not owned or controlled by GNOME. I have posted
positive content on said forum:
https://www.reddit.com/r/gnome/comments/gyjrbk/hell_has_frozen_over_mutli...
Your reply violates the Code of Conduct, IMO, namely be respectful,
empathetic, considerate, patient and generous and friendly sections of
the community guidelines. If you don't have anything constructive to say
or, at the very least, can't say it in a polite way, I'd ask that you
don't reply. Thanks.
3 years, 10 months
Regarding behaviour of Gnome and Fedora members
by Ty Young
Hi all,
Gnome recently has stirred up controversy lately and aren't taking other
people's opinions very well, to say the least. So far they've locked
three threads:
https://www.reddit.com/r/gnome/comments/gz6fks/we_must_all_speak_up/
https://www.reddit.com/r/gnome/comments/h107as/i_agree_with_the_we_all_mu...
https://www.reddit.com/r/gnome/comments/h0ml37/distrotube_has_posted_a_di...
They have engaged in racism and censorship in their subreddit's comment
sections and, just recently, banned me for posting this article, which
I've made:
https://medium.com/@youngty1997/gnome-needs-to-be-better-2151965fd663
You may read it for yourself. In it I cite violations of Gnome's Code of
Conduct by members of the GNOME foundation or the GNOME
foundation(gnome.org email address), both on their subreddit and from
fedora-devel list. I tried to cite as much as possible but Gnome
moderators refused to hand over the moderation logs for when they locked
a thread for reporting a bug when asked. I'm confident that they know
what I'm talking about but just refuse to hand it over.
Keep in mind that, in Gnome's subreddit rules, it's perfectly OK to
criticize GNOME in GNOME's subreddit. It's even in the sidebar, which
you cannot see on old reddit(something I've told them about multiple
times, but they've ignored repeatedly to fix):
"We do not shy away from criticism, in fact, we encourage it!"
GNOME members have recently said that "This mixing of ideas from a wide
range of backgrounds is something that has improved free and open source
software, and it should be highly valued."
However, their actions by locking threads and now banned me for sharing
an article I had made goes against this statement. To be crystal clear
here, the opinions shared in the article are not *just* my own. You may
also read people who agree with my opinions in comment sections of the
GNOME subreddit and Fedora subreddit which I shared it to:
https://www.reddit.com/r/Fedora/comments/h7de62/gnome_needs_to_be_better/
https://www.reddit.com/r/gnome/comments/h7ddom/gnome_needs_to_be_better/
Gnome did not say that any new threads on the topic could be made nor
was there any rule breakage that I could find. I would have loved to
cite more things but alas, I don't have access to the information.
Sadly the moderators of each respective subreddits have censored the
threads, and not even snew shows them for some reason. I've tried
contacting the fedora subreddit moderators but I have a feeling they
won't ever answer.
I was planning on fileing a Code of Conduct violation, but GNOME refused
to turn over the requested moderation logs, so I couldn't do so and,
Gnome's Code of Conduct hints as what the result will be anyway. I have
zero confidence that anything will be done, so here I am sending an email.
So, could anything be done about any of this?
3 years, 10 months
Btrfs out of space - but plenty of space is available
by Konstantin Svist
Looks like I'm having a problem with my btrfs partition, it thinks it's out
of space.
Thing is, the drive is 500G and usage according to df and btrfs df is ~250G
I removed a couple of snapshots as a workaround but hit the problem again
pretty quickly..
I also ran fstrim & btrfs check --clear-space-cache (both v1 and v2) and
still no luck.
Is there some limitation on number of files? I'm not doing anything crazy
there, just haven't checked yet
3 years, 10 months
keeping debuginfo in sync?
by Tom Horsley
Is there a trivial way to insure debuginfo files I have installed
stay in sync with the libraries when they get updated?
I manually updated all my debuginfo packages, then found
I also needed to update debugsource packages.
3 years, 10 months
Interfaces
by Beartooth
In another thread, Bob Marcan wrote:
> Seems almost nobody is using the command line.
> GUI for everything.
> I like to see how will they solve the repetitive task.
Well, what follows seems typical enough to be of possible interest.
I've been around long enough to know only too well that the CLI is
preferable when feasible. The problem is remembering the commands, to the
point where your fingers know them. I began with a prodigious memory, and
ran it flat out for decades; so now in old age it's way full.
But visual spatial memory, fortunately, seems to occupy a
different register. It's slower and less sharp. To answer what I has
clicked on, I was not able to rattle off a list, but had to go back and
reconstruct it -- including recovering a couple times from errors. But I
got there. The first false fork with the CLI'd've lost me.
--
Beartooth Implacable, Double Retiree
Historian of Tongues from Way Back
3 years, 11 months
Mount options for mostly-offline drives
by Patrick O'Callaghan
I have a powered USB dock with a couple of SATA drives configured as
RAID1, and used only for nightly backups. The (minimal) manual for the
dock tells me it will power down after 30 minutes idle time, however I
don't see this happening. I presume that something (such as the md
system) is touching the drives periodically.
What is the fstab option to have the drives mounted only when accessed?
This used to be automount (or autofs) but with systemd getting its
fingers into everything I know longer know how to do this.
Can the drive be automatically unmounted if not in use? I presume this
would stop md from trying to check it and hence prevent the dock from
keeping it powered on.
poc
3 years, 11 months
RPM Fusion GPG not Found
by Stephen Morris
Hi,
As part of upgrading F31 to F32 using 'dnf system-upgrade download
--releasever=32', dnf downloaded all packages and downloaded and
installed the gpg for rpmfusion-free, but it was not able to download
and install the gpg for rpmfusion-nonfree, and hence would not recognise
the system as being rebootable to do the upgrade until I manually
downloaded and imported the rpmfusion-nonfree gpg data. Has anyone else
encountered this situation?
regards,
Steve
3 years, 11 months
Re: Hourly Error Message of Unknown Provenance
by R. G. Newbury
On Mon, 08 Jun 2020 16:02:02 -0400 "Garry T. Williams"
> <gtwilliams(a)gmail.com> wrote
> On Monday, June 8, 2020
> 12:41:03 PM EDT R. G. Newbury wrote:
>> On 2020-06-07 4:46 p.m., From: Samuel Sieb<samuel(a)sieb.net> wrote:
>>> On 6/7/20 10:31 AM, R. G. Newbury wrote:
>>>> It was apparently something to do with selinux. I usually disable
>>>> selinux as the first or second thing I do to a new install. I
>>>> forgot to do that.
>>> That should never be necessary.
>> Well obviously, it WAS necessary in order to get rid of an
>> objectionable and annoying message, which was otherwise impossible
>> to get rid of.
> I imagine that he meant that restoring some file context that was
> modified incorrectly by the root user would be a better way to solve
> the problem, thus disabling was not necessary.
Unfortunately Samuel did not add anything about restoring the file
context and I took his response to contain a modicum of 'Karen'. My bad(?)
> Obviously I cannot know what the problem really is, but it has been
> many years since I even came close to disabling selinux. It is hard
> to belive that a brand new system was created with an invalid file
> context. Those kinds of bugs don't get past updates-testing these
> days. So whatever was going on as the root user is almost certainly
> to blame.Well on reflecting, I cannot see anything which I could have done. As
noted, it was a bare metal install (actually the second to the new
SSD,as after the first go-around, I realized I needed more room on one
of the partitions, so I re-booted with a rescue disk, used gparted to
change the partition structure and installed. After the installation
re-boot, I upgraded some 527 packages, and re-re-booted into a new kernel.
I then started transferring (by rsync) the data for the /home, /misc and
/usr/local partitions. Somewhere in there, the error started popping up.
I have, since then, tracked down a certain slowness in the login, to the
lack of an xorg.conf file. It is possible that xinit was trying to
report that it was having trouble connecting, as I found that message in
the Xorg.0.log. But, why would xinit be unauthorized? The mystery
continues. I don't think I did anything wrong or bad. Most of my
interactions involved long wait periods while processes processed....
Geoff
3 years, 11 months
Re: Hourly Error Message of Unknown Provenance
by R. G. Newbury
On 2020-06-08 2:42 p.m.>Samuel Sieb<samuel(a)sieb.net> wrote> On 6/8/20
9:41 AM, R. G. Newbury wrote:>> On 2020-06-07 4:46 p.m., From: Samuel
Sieb<samuel(a)sieb.net> wrote:>>> On 6/7/20 10:31 AM, R. G. Newbury
wrote:>>>> Oddly 1) I was running as root... so*who/what* was the
'unauthorized>>>> sender'? and>>> That sounds like a likely cause right
there. Why are you doing that?>> Wow! So running as root causes error
messages? Pull the other leg, it>> has bells on it!> Yes, running a
graphical interface as root is likely to cause error> messages.
I find that concept very intriguing. I would be interested in learning
exactly how
or when running as root in a graphical session can *cause* an error.
Root is uid 0 (zero).
There are no gradations or ranks within root. It seems completely
irrational to me, that linux would be designed and implemented in a
manner such that the ultimate power that is, does things 'wrong' by default.
This is entirely apart from the question of running things as root,
which in general terms, I consider 'a good thing' as distinct to 'a bad
thing'. YMMV. The only time which I can remember where I inadvertently
deleted something in bulk, that I had not intended, I was running as a
regular user, and deleted things *on the laptop*, forgetting that I was
ssh'd into the laptop in that console. Would not have mattered if I was
root. It wasn't boken but I frixed it anyway.
Geoff
3 years, 11 months
e: Hourly Error ,> Message of Unknown Provenance
by R. G. Newbury
On 2020-06-08 2:42 p.m.,Jonathan Billings <billings(a)negate.org> wrote
>On Mon, Jun 08, 2020 at
> 12:41:03PM -0400, R. G. Newbury wrote:
>> Wow! So running as root causes error messages? Pull the other leg, it has
>> bells on it!
>>
>> And why? Because this was immediately after a clean install to a brand new
>> drive, while I was still running upgrades and transferring files from
>> backup. Much easier to do that as root, so that is what I do. If you want to
>> type sudo a hundred times, go right ahead.
>>
>> Running as root is not a disaster. Get over it.
> Were you logging into the graphical session as root, or logging in as
> a normal user and starting a root shell with sudo? Or were you using
> root at the console login instead of the graphical login?
At the time I was logging into the graphical session as root. 'Who' the
unauthorized sender is/was is the conundrum. Seems to be related to
selinux, since disabling that killed the error message. But why it
happened in the first place, I have no idea. And at this point, as
someone said, what difference does it make?
Geoff
3 years, 11 months
