For four decades, I've been copying text by selecting it and then pasting
by clicking the middle mouse button.
It suddenly stopped working, with no announcement that I saw, when I
updated from Fedora 43 to Fedora 44. It was very frustrating. That this
was intentional is quite rude.
There are actually two paste buffers: the ^C / ^V one and
the mouse select / middle button click one.
It turns out that this is a GNOME "improvement". Here's an OK write-up.
<https://discussion.fedoraproject.org/t/can-we-revert-downstream-the-disabli…>
See also <https://bbs.archlinux.org/viewtopic.php?id=313089>
Fix 1:
dconf write /org/gnome/desktop/interface/gtk-enable-primary-paste true
That only affects the current user.
Variants of that command can have system-wide effects (I try not to
understand dconf).
Fix 2:
Use GNOME Tweaks: Mouses & Touchpad: Mouse: Middle Click Paste
This only affects the current user/
I haven't seen an announcement, so I'm just filling a gap.
Online using Nextcloud: https://hub.gtalug.org/call/7m45sf9i
This will be a Q & A session.
It's kind of free-form so if you have a short talk, you can probably
present it. Just ask the audience first.
Hi all,
Where: GoLUG Online: https://meet.jit.si/golug
When: Wednesday, 6/3/2026 7pm sharp Eastern DAYLIGHT time
Arrive at 6:45pm for Microphone check & discussion
Who: Steve Litt, Troubleshooter, Developer, Tech Writer
What: Find out for yourself about Rust
It's coming. You've seen it. You've heard of Rust. You've seen the
evangelism. You've heard the skepticism. At the next GoLUG meeting, you
get to decide for yourself.
First, we'll discuss some Rust essential questions:
* Why use Rust?
* Why not use Rust?
* What is the optimal Rust mindset?
* What do the major Rust terminology terms mean?
- mutability
- ownership
- borrowing
- lifetime
- Cargo
- Crate
- Statements;
- Expressions
* Where does Rust surpass all others?
- Hint, it's not safety or runtime speed.
Using the Rust compiler as your instructor, along with the Rust book
and a little AI thrown in, you'll see (or follow along if you'd like)
the following steps:
* Compile empty.whatever empty file
- To start from absolute zero
* Read and use the error messages
* Read the documentation suggested by the error messages
* Get familiar with using the superior Rust documentation
* Hello World
* Build loops with for, while, loop, break and continue
- Intro to mutability
* Use branching (if, else if, else)
* Handle command line arguments
* Convert strings to integers
* Function intro with types
- Arguments with types
- Return value with types
- Handling references
- Borrowing, ownership and lifetimes
* Multifile projects (time permitting)
* Closures (time permitting)
The final 20 minutes of this 2 hour presentation will get you
comfortable with the Rust's spectacular documentation system. Armed
with this presentation, Rust's documentation, and a little AI, if you
decide that Rust is a fit for your priorities and personality, you can
go as far as you want with Rust.
If you want to code along with the presentation, and this is
nice although not necessary, install Rust on your computer before
the presentation. It's very easy to install on most Linux distros, and I
assume on Windows, Mac, and BSD also.
Hope to see you there.
SteveT
Steve Litt
GoLUG Publicity Coordinator
