Logitech mouse
by Emmett Culley
I have a logitech mouse that has been working well for a long time. Except that every once in a while it suddenly won't scroll one line at a time and instead requires multiple turns of the wheel to move a page.
I've been putting up with this as I am able to fix it by running solaar and toggling scroll wheel resolution off then on again. Only a couple of mouse clicks.
Now it seems to have gotten worse, or I am finally tired of having to stop my workflow to fix it. It seems to be related to the mouse going to sleep during inactivity, though it is random enough so I cannot be sure.
I am on the latest fedora 34 code, and I have been seeing issue since before 32.
Any ideas where to look for a solution?
Emmett
1 year, 1 month
Fedora 36: KDE blockers and priorities
by Adam Williamson
Hey folks! Just wanted to sync up on the Fedora 36 Final process.
First, some key dates:
2022-04-05 (1400 UTC): Final freeze starts
2022-04-14: Go/No-Go meeting
We would want to have all known blockers addressed by 2022-04-11 at the
latest in order to have sufficient time for validation testing.
Any update that wants to go stable after 2022-04-05 1400 UTC will need
to be a fix for a blocker or FE bug, so if there are updates you folks
want included in Final that are *not* blocker/FE fixes, please ensure
they're submitted in good time. If there's an issue getting sufficient
karma for an update, please let us know on the test@ list or the QA
IRC/Matrix channel.
Quick note, I'm mostly on PTO from Saturday (April 2) to April 17. I
will be checking in periodically but won't be anywhere near as around
as I usually am. Please treat pings/pokes from the rest of my team with
as much priority as you do or don't usually treat pings/pokes from me.
:D coremodule (Geoffrey Marr) and Frantisek Zatloukal will be handling
blocker herding duties.
There's currently only one outstanding blocker for KDE, but it's been
sitting for a while:
https://bugzilla.redhat.com/show_bug.cgi?id=2057563
https://bugs.kde.org/show_bug.cgi?id=447958 , was marked as dupe of:
https://bugs.kde.org/show_bug.cgi?id=448784
It's a bug where hitting the About button in Discover causes the app to
stop responding, apparently due to some kind of loop in the UI code.
Aleix seems to have diagnosed the problem in upstream #448784, but that
was last month and I don't see a fix yet.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 2 months
Building from a Kickstart file - out of space error
by Philip Rhoades
People,
I am trying to build from a ks file but I keep getting errors about not
enough space on / - but there is plenty of space:
/dev/sda3 183G 31G 143G 18% /
Is the error about / on the image that is being created? I have tried
removing all non-critical packages - which reduces the number in the
error message but I don't understand why I am getting it all . .
Here is what I get:
[lots of errors like this]:
installing package
NetworkManager-config-connectivity-fedora-1:1.37.3-1.fc37.noarch needs
296MB more space on the / filesystem
Error Summary
-------------
Disk Requirements:
At least 296MB more space needed on the / filesystem.
Unable to unmount /var/tmp/imgcreate-krx68kda/install_root/var/cache/dnf
normally, using lazy unmount
lazy umount succeeded on
/var/tmp/imgcreate-krx68kda/install_root/var/cache/dnf
lazy umount succeeded on
/var/tmp/imgcreate-krx68kda/install_root/var/cache/dnf
Unable to unmount /var/tmp/imgcreate-krx68kda/install_root/sys normally,
using lazy unmount
lazy umount succeeded on /var/tmp/imgcreate-krx68kda/install_root/sys
lazy umount succeeded on /var/tmp/imgcreate-krx68kda/install_root/sys
Unmounting directory /var/tmp/imgcreate-krx68kda/install_root
Losetup remove /dev/loop0
How to fix?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
1 year, 2 months
2022-03-28 @ 16:00 UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-03-28
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 6 proposed Final blockers and 2 proposed Final freeze
exception issues to review, so let's have a review meeting on Monday.
Remember, Europeans, if DST kicks in for you this weekend, the meeting
time will change for you this week, back to the time it usually is
except for this one weird intermission every year. :D
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F36 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 2 months
Dpi in libreoffice on Wayland
by Jan Simonson
Hello,
I use Fedora 35 fully up to date. My monitor is 32 inch with a resolution of
4k.
When I try to use libreoffice on a Wayland session everything becomes very
tiny. Almost all other programs adapt well to the rather high dpi. When I try
X11 instead the libreoffice display is normally sized. I have searched for a
dpi setting in libreoffice without finding any.
Why is the result so different in X11 and Wayland using the same settings?
What can I do to solve the problem?
Best regards
Jan
1 year, 2 months
2022-03-21 @ ** 16:00 ** UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-03-21
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 1 proposed Beta blocker, 1 proposed Beta freeze
exception issue, and 4 proposed Final blockers to review, so let's
have a review meeting on Monday.
Remember DST started in North America last week, and check the meeting
time carefully! If you're in North America it's at the same time as
always, if you're anywhere else it's likely earlier (when DST starts in
Europe it'll be back to the 'usual' time there).
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F36 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 2 months
2022-03-14 @ ** 16:00 ** UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson
# F36 Blocker Review meeting
# Date: 2022-03-14
# Time: ** 16:00 ** UTC
# Location: #fedora-blocker-review on irc.libera.chat
Hi folks! We have 2 proposed Beta blockers, 1 proposed Beta freeze
exception issue, and 4 proposed Final blockers to review, so let's
have a review meeting on Monday.
Note that DST starts in North America on Sunday, so the meeting time in
UTC is now an hour earlier than before. If your region uses daylight
savings time and it starts this weekend, the meeting will be at the
same local time as usual. If your region does not use DST, or it
doesn't kick in yet, the meeting will be an hour earlier in local time
than usual. Use `date -u` to check the current UTC time if you're
unsure.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F36 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 2 months