KDE SIG members participating upstream?
by Neal Gompa
Hey folks,
I was recently informed that we don't have anyone from the KDE SIG
actively participating in the upstream KDE Plasma projects to
represent Fedora. Is there anyone that could take on that capacity and
help us build better bridges with upstream?
It'd be great to have that so that Fedora's concerns are factored into
the development of KDE projects and that we generally have a better
pulse on things as new KDE software is integrated into Fedora.
As for why not me? I'm stretched more thinly than I want to be as it
is, though I do interact with a few KDE folks myself from time to time
and follow the KDE distributions mailing list.
Best regards,
Neal
--
真実はいつも一つ！/ Always, there's only one truth!
3 years, 11 months
Re: user switching criterion proposal
by Kamil Paral
On Thu, May 7, 2020 at 8:48 AM Lukas Ruzicka <lruzicka(a)redhat.com> wrote:
> Hello,
> I agree, that user switching as described in this proposal is something
> that should work really well, because it can obviously change the user
> experience in some cases.
> I only have a problem with the following statement:
>
> The switching mechanism must correctly attempt the requested operation.
>>
>
> As I understand it, it might be enough if the operation is "attempted"
> only? This sounds vague and weak to me. I think we need something stronger
> here, like "it performs the requested operation" or something similar.
>
It's similar to e.g. shutdown criterion [1] where the "shutdown mechanism
must correctly request a shutdown from the system firmware" or storage
resize criterion [2] where "installer mechanism for resizing storage
volumes must correctly attempt the requested operation".
The important word in all these cases is "correctly". It implies that the
software part, the calling part, must be implemented correctly. But because
it deals with hardware and low level firmware and drivers, it admits that
that part might not work correctly in all configurations. Which is then
expanded in the next sentence.
I simply got my inspiration from our other criteria when writing this one.
It doesn't have to stay this way. But I think the "correctly
attempt/request" wording is quite fitting here and it's not weak (at least
not towards our software stack, which is the part which we can control
reasonably well).
[1]
https://fedoraproject.org/wiki/Fedora_32_Beta_Release_Criteria#Shutdown.2...
[2]
https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#Storage_v...
3 years, 11 months
polkit issues while upgrading
by Georges Schwing
Hello everyone,
Following the upgrading of my Fedora workstation 31 to 32. I cannot
connect to my WIFI network NetworkManager applet says, "not authorized
to control networking".
I've made research and it seems that the polkit configuration does not
allow my user to perform such actions.
When I'm looking for the polkit packets installed all the normal ones
are. (ie the same as the fresh Fedora 32 Workstation install)
[root@laptop georges]# rpm -qa | grep polkit
polkit-qt-0.112.0-18.fc32.x86_64
polkit-qt5-1-0.113.0-2.fc32.x86_64
polkit-kde-5.18.5-1.fc32.x86_64
polkit-0.116-7.fc32.x86_64
polkit-pkla-compat-0.1-16.fc32.x86_64
polkit-libs-0.116-7.fc32.x86_64
If i've made a fresh install of Fedora 32 Workstation everything works.
Does Anyone has the same issue?
Is there a way to auto-configure polkit instead of making specific
configurations files in /etc/polkit-1/... ?
Georges
3 years, 11 months
Logout cancelled by <program>
by Patrick O'Callaghan
Where is the magic setting to stop this happening? Is it specific to
each program or something more general? I'm using KDE on F32, if it
matters, and I'm getting this whenever I log out, either with Ctrl-Alt-
Del or with the menu option. It has started happening with qbittorrent
specifically, but I recently reset its configuration to fix a problem
so that might be the root cause. I have to explicitly exit the program
first.
poc
3 years, 11 months
user switching criterion proposal
by Kamil Paral
Following the previous discussion [1] and the gathered support, here's a
proposal for the user switching criterion. I believe we should put it into
the Final milestone [2].
~~~~~~~~~~~~~~~~~~~~~
User switching
User switching must work using the mechanisms offered (if any) by all
release-blocking desktops in their default configuration.
What is user switching?
User switching is a process of changing the currently presented desktop
session between concurrent sessions of two or more different users. The
user sessions keep running in the background, and users can switch between
them repeatedly without losing any running application state.
For the purpose of this criterion, user switching doesn't include switching
between different sessions of the *same* user.
Work?
The switching mechanism must correctly attempt the requested operation. If
the operation doesn't work on a subset of graphical drivers, the release
blocking decision should be based on the number of affected users, the
problem severity and available workarounds (as is our [standard
procedure](Basic_Release_Criteria#Basic_Release_Requirements)[3]).
~~~~~~~~~~~~~~~~~~~~~~
The "in their default configuration" part is there to cover only cases
where the system hasn't been modified in a substantial (and relevant) way.
This will exclude cases where people e.g. install several desktop
environments, replace their DM for a different one, tweak systemd settings,
or install a non-default graphics driver.
In the last paragraph I explicitly pointed out that we'll use our usual
approach of judging the impact if the issue only affects certain
configurations. I hope that alleviates some hardware-related concerns.
Note: I considered the option to also include user switching in text-only
environments (simultaneous user login on different VTs, as is common on
Server), but it's not completely the same. I concluded it's better to have
a separate and tailored criterion for it, if there's interest.
Please comment, thank you.
[1]
https://lists.fedoraproject.org/archives/list/test%40lists.fedoraproject....
https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject...
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org...
https://pagure.io/fedora-workstation/issue/139
[2] https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria
[3]
https://fedoraproject.org/wiki/Basic_Release_Criteria#Basic_Release_Requi...
3 years, 11 months
Fedora KDE and sound over HDMI/DP
by Alex Gurenko
Hello everyone, I want to re-visit the question that I've raised a year ago here [0]. I'm still running my Lenovo T460p, but we're already in F32 and still same issue presents.
I've just recently got a new Dell monitor that I connect for the lack of USB-C ports over DP and in KDE environments, there is no visible ways to route sound over DP as far as I can tell. I've also tried booting Manjaro KDE and it seems to be missing component in KDE itself?
Other distros (Fedora Gnome, Ubuntu, Linux Mint, Elementary) even live image recognize DP as an output and can successfully route sound there.
What would be the action plan here? Did anyone look into that already maybe? I'm wondering where the problems lies or what part/component is missing?
[0] https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org...
---
Best regards, Alex
3 years, 11 months
KRunner - clicking on PDF result opens in Gnome viewer
by Syam Krishnan
Hi
I have Fedora 31 KDE spin. I have the following problem:
1. Open KRunner by Alt+F2
2. Type "pdf" in the box
3. Click on any PDF file from the search result
4. The file is opened in a Gnome application
I don't know the name of the Gnome application that comes up.
Opening PDF files from Dolphin or by xdg-open correctly opens the file
in Okular. The problem is only when opening from KRunner. And I don't
even have Gnome desktop installed.
Anything I should check before filing a bug report with Fedora or KDE?
Thanks,
Syam
3 years, 11 months
brightness on lenovo ideapad
by Adrian Sevcenco
Hi! I post here as i suspect that it is a kde problem with brightness settings:
while the keyboard special functions modify the setting in the Battery and Brightness tray module,
the actual brightness is not modified, but i actually can modify the brightness using xrandr.
Does anyone have any idea why the kde module does not use the xrandr mechanism?
Thank you!
Adrian
3 years, 11 months
qBittorrent not working in F32
by Patrick O'Callaghan
I updated to F32 (from F31) yesterday with no hiccups or complaints.
However I find that qBittorrent won't download anything. I've tried
several several times with different torrents, including
https://torrent.fedora.org, and each download sits there at zero
percent. I've also tried via a VPN (in case my ISP was blocking me,
though they've never done that before). It made no difference.
Has anyone successfully used qBT with F32?
poc
3 years, 11 months
