I want to setup access to a live.com account, but when I click on
"Online Accounts" in System Settings, an error is returned instead of
letting me set it up. The error message follows:
Error loading QML file.
"Ubuntu.OnlineAccounts" is not installed
which is essentially the message given in the journal. I looked at the
file and line 31 is
import Ubuntu.OnlineAccounts 0.1 as OA
The file comes from "kaccounts-integration-19.12.1-1.fc31.x86_64" which
is installed. So it looks to me like I need to find a correct
"Ubuntu.OnlineAccounts" and install it. If that is correct, where do I
find it? If not, what do I do to set up my live.com account?
Lester M Petrie
Long time KDE user. Long time Fedora user.
A while back KDE windows lost distinct visible contrasting borders. So
now if you have two windows overlaying each other of the same color
(usually white) you can't see where one window ends and another begins,
except by viewing the content of the window.
I find this really distracting. I am constantly straining to see the
edges of windows.
Please bring back distinct, visible, contrasting window borders, at least
as an option.
PS... just totally messed up my desktop by messing around trying to fix
Was testing different window styles in System Settings -> Global Theme.
Selected "Use desktop layout from theme", just to get things consistent.
Got the warning "Your desktop layout will be lost and rest to the default
layout provided by the selected theme".
I thought about that for a minute and decided it would be OK if I had to
change folder sizes, etc. No biggie.
But what I didn't realize is that it removed all my widgets and task bars
! It is going to take me a couple hours to get things back to the way
they were widget wise. Please add the words widgets and desktop wallpaper
to the warning. Desktop layout means everything about the desktop, not
just the theme stuff.
Hi KDE team,
Workstation enabled earlyoom by default in Fedora 32. A search of
Bugzilla suggests it has been a pretty well-behaved change. How do we
feel about submitting this as a self-contained change proposal for
Fedora 33 KDE?
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
I just upgraded one of my laptops to version 32. Most seems to work
fine, but a few doesn't work any more.
Starting Calibre I get this:
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in <module>
File "/usr/lib64/calibre/calibre/gui_launch.py", line 72, in calibre
File "/usr/lib64/calibre/calibre/gui2/main.py", line 542, in main
listener = create_listener()
File "/usr/lib64/calibre/calibre/gui2/main.py", line 513, in
File "/usr/lib64/calibre/calibre/utils/ipc/server.py", line 109, in
AttributeError: 'NoneType' object has no attribute 'cancel'
Starting dnfdragora gives after long time updating the repo files this:
Get root backend. Locked (False)
Get root backend. Locked (False)
Unexpected error: <class 'KeyError'>
<_M_> [ui] YUILoader.cc:163 deleteUI(): Shutting down UI
<_M_> [ew] YExternalWidgets.cc:116 ~YExternalWidgetsTerminator():
Shutting down mga External Widgets
<_M_> [ew] YMGAWidgetExtensionFactory.cc:49 ~YMGAWidgetFactory():
From this I guess the there may be something wrong with the Python
installation, but I cannot figure out what to do to fix it.
Can you give me any hints to overcome these problems?
Med venlig hilsen
Teknikumingeniør, B.Sc.EE., e-mail : klaus(a)kolle.dk
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
So, currently Rawhide composes are failing because KDE in Rawhide is
broken: about half of KDE 5.18.90 got built, then kwin failed because
it depends on a new "kwayland" thing that is not yet packaged. See
https://pagure.io/releng/failed-composes/issue/1459 for some notes on
this. This means KDE images don't build, and as some KDE images are
release-blocking they are set as fatal in pungi config, meaning the
compose fails if any of those images fails to build.
KDE team, do we have an ETA for fixing this?
If it's not going to be fixed soon, I'd like to suggest we either
temporarily mark the KDE images as non-fatal in pungi config (so
Rawhide composes can succeed with KDE broken), or untag all the 5.18.90
builds that have been done so far. Thoughts on that?
For the future: can KDE team please consider doing this kind of major
version bump in side tags, rather than just firing the builds off
directly into Rawhide? It would avoid this kind of bear trap: if
something like this shows up halfway through the process, we wouldn't
wind up with Rawhide being broken.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
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.
真実はいつも一つ！/ Always, there's only one truth!
On Thu, May 7, 2020 at 8:48 AM Lukas Ruzicka <lruzicka(a)redhat.com> wrote:
> 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  where the "shutdown mechanism
must correctly request a shutdown from the system firmware" or storage
resize criterion  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
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
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/... ?