kde December 2021

kde@lists.fedoraproject.org

17 participants
15 discussions

Logitech mouse
by Emmett Culley 08 Apr '22

08 Apr '22

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

5 11

Release criteria proposal: networking requirements
by Adam Williamson 01 Mar '22

01 Mar '22

Hi folks! So at this week's blocker review meeting, the fact that we don't have explicit networking requirements in the release criteria really started to bite us. In the past we have squeezed networking-related issues in under other criteria, but for some issues that's really difficult, notably VPN issues. So, we agreed we should draft some explicit networking criteria. This turns out to be a big area and quite hard to cover (who'd've thought!), but here is at least a first draft for us to start from. My proposal would be to add this to the Basic criteria. I have left out some wikitext stuff from the proposal for clarity; I'd add it back in on actually applying the proposed changes. It's just formatting stuff, nothing that'd change the meaning. Anyone have thoughts, complaints, alternative approaches, supplements? Thanks! === Network requirements === Each of these requirements apply to both installer and installed system environments. For any given installer environment, the 'default network configuration tools' are considered to be those the installer documents as supported ways to configure networking (e.g. for anaconda-based environments, configuration via kernel command line options, a kickstart, or interactively in anaconda itself are included). ==== Basic networking ==== It must be possible to establish both IPv4 and IPv6 network connections using DHCP and static addressing. The default network configuration tools for the console and for release-blocking desktops must work well enough to allow typical network connection configuration operations without major workarounds. Standard network functions such as address resolution and connections with common protocols such as ping, HTTP and ssh must work as expected. Footnote titled "Supported hardware": Supported network hardware is hardware for which the Fedora kernel includes drivers and, where necessary, for which a firmware package is available. If support for a commonly-used piece or type of network hardware that would usually be present is omitted, that may constitute a violation of this criterion, after consideration of the [[Blocker_Bug_FAQ|hardware-dependent- issues|normal factors for hardware-dependent issues]]. Similarly, violations of this criteria that are hardware or configuration dependent are, as usual, subject to consideration of those factors when determining whether they are release-blocking ==== VPN connections ==== Using the default network configuration tools for the console and for release-blocking desktops, it must be possible to establish a working connection to common OpenVPN, openconnect-supported and vpnc-supported VNC servers with typical configurations. Footnote title "Supported servers and configurations": As there are many different VPN server applications and configurations, blocker reviewers must use their best judgment in determining whether violations of this criterion are likely to be encountered commonly enough to block a release, and if so, at which milestone. As a general principle, the more people are likely to use affected servers and the less complicated the configuration required to hit the bug, the more likely it is to be a blocker. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

4 7

Dolphin ignores umask
by Emmett Culley 10 Jan '22

10 Jan '22

I first discovered this issue when a user complained she could not access a file I created on an NFS4 share. I don't see this issue if I use fish:// to access any directory, local or remote. We are on fully updated KDE fedora 34 and 35 systems, and this has been a problem for quite awhile, through many Fedora updates, possibly as far back as fedora 18 (arbitrary number). Until now I've usually just run chmod -R g+w on the share on the file server or locally when it matters, then went about my business. I have put it off too long and so did a bit of investigation. This happens every time on both Konqueror and Dolphin. It never happens in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs share), and create a file or directory, the permissions are set to 664 and 2775 (SGID is set for all directories) as expected, with a umask of 002 for all users. Note that the umask on both servers and clients are set to 002. So only Dolphin and Konqueror ignore the umask=0002 setting, and only when not accessing a file system via fish. This happen on both remote NFS shares and locally. Emmett

3 8

KDE is almost using all the latest packages
by Reon Beon 28 Dec '21

28 Dec '21

Nice.

4 6

F35: Plasma/X11: Manual session save broken
by Terry Barnaby 28 Dec '21

28 Dec '21

It appears that something has broken the KDE/Plasma/X11 manual session restore system again. When I try this with my setup (Intel Graphics, dual monitor, 10 virtual desktops) and with Thunderbird, Firefox, Dolphin and about 12 kconsoles opened on various virtual desktops they reappear mainly on the first screen of the first desktop but with various manual session save appear on what seems to be random desktops and screens. Playing around with a test user it sometimes works and sometimes fails, quite flaky. I believe this worked after the first F35 install a week or so ago, but it seems like some update has broken this system. Is there some work going on on the session management and where would be the best place to submit bug reports for this ?

4 6

Maybe OT DMARC issues
by Emmett Culley 27 Dec '21

27 Dec '21

Every time I send a message to this list I receive four emails. Three are DMARC forensic reports: DMARC Forensic Report for webengineer.com from IP 85.25.209.148 from no-reply(a)se2.hostedcloud.me DMARC Forensic Report for webengineer.com from IP 38.145.60.11 from no-reply(a)semfq03.mfg.siteprotect.com DMARC Forensic Report for webengineer.com from IP 38.145.60.11 from no-reply(a)filter13.premiumantispam.nl And a forth from opendmarc(a)mail.mgoodwin.net saying This is an authentication failure report for an email message received from IP 38.145.60.11 on Mon, 27 Dec 2021 10:17:22 -0500 (EST). I assume this is a mail list email server issue for this list as it never happen on other mailing lists. Where should I report this issue? Emmett

2 1

[Fedocal] Reminder meeting : KDE SIG
by ngompa＠fedoraproject.org 26 Dec '21

26 Dec '21

Dear all, You are kindly invited to the meeting: KDE SIG on 2021-12-27 from 13:00:00 to 14:00:00 US/Eastern At https://meet.kde.org/b/ale-swq-39j The meeting will be about: Regular meeting for the KDE SIG Current Topics: https://pagure.io/fedora-kde/SIG/issues?status=Open&tags=meeting More information available at: [https://fedoraproject.org/wiki/SIGs/KDE](https://fedoraproject.org/wiki/SIG… Source: https://calendar.fedoraproject.org//meeting/9876/

1 0

Libreoffice - menu and tools very small
by Klaus Kolle 25 Dec '21

25 Dec '21

Hi, after upgrading my Fedora to 35 from 33 the menus and toolbar in Libreoffice are very small, I can't read the text or see the icons clearly. All other program, I've tried, works all right. I run this Fedroa on a Lenovo Yoga Y920, which has a 4K screen resolution. I have scaled it in the Settings -> Display Configuration to HD size (200%) in order to read the text on the screen. Maybe this has an influence on Libre Office. Do you know where to correct this problem? |< -- Med venlig hilsen Klaus Kolle Teknikumingeniør, B.Sc.EE., e-mail : klaus(a)kolle.dkLibre Master of IT www : www.kolle.dk Asger Jorns Vej 17 Telephone : +4522216044 DK-8600 Silkeborg, Denmark "Leave me alone, I know what I'm doing!" Kimi Räikönen, Abu Dhabi F1 race 2012. Planlægning er tanker om noget man agter at gøre en gang i fremtiden, hvis omstændighederne tillader det. Klaus Kolle 2006 Perfection is achieved not when nothing more to add, but when there is nothing more left to take away. Antoine de Saint-Exupery

1 0

KDE, Android Studio & window corruption
by Mark ＠ GMail 20 Dec '21

20 Dec '21

Is anyone else (still) seeing this? Opening AS almost always starts off with the window being corrupt and the window items being un-clickable. Closing and re-opening AS once (or sometimes twice) generally resolves the issue. I have been pointed to the link https://www.reddit.com/r/xmonad/comments/abvvai/rename_wm/ To help with this window corruption. It has sort-of worked, improving, but mostly not entirely fixing the problem. Very occasionally the AS opens correctly first time, more often it still requires closing and re-opening to function correctly. Recently it's been worse to be point of hardly being usable, half a dozen close/open cycles being required to get to a usable window. The fix is a little odd since it refers to a Java 7 (* previous) shortcoming, and I'm using the AS embedded version, which is 11. However, since it's not really fixing things now, I'm wondering if someone here has something more reliable?

1 0

After upgrade F33->F34, I get a black screen when logging in to Plasma (both Wayland and X11)
by Frédéric 20 Dec '21

20 Dec '21

Hi all, Today, I eventually upgrading my F33 to F34. Everything looks fine until I get teh sddm login screen. Here if I choose Plasma, either Wayland or X11, I get a black screen with mouse, nothing else. In the journal, I can see these errors: sddm-helper[3227]: pam_systemd(sddm-greeter:session): Failed to release session: Transport endpoint is not connected dbus-broker-launch[3352]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'. dbus-broker-launch[3352]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'. dbus-broker-launch[3352]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored dbus-broker-launch[3352]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored dbus-broker-launch[3352]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. ... kernel: nouveau 0000:01:00.0: Enabling HDA controller kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 619444 [ PRIVRING ] I get this last error multiple times. There is no error (EE) in /var/log/Xorg.0.log, just 1 warning: (WW) Falling back to old probe method for fbdev Thanks for help! F

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde December 2021