Hi! So, after having krunner broken for some time (the shortcut would only print a black square on the screen)
i just tried to start it from konsole and i seen this:
"Error loading QML file.\n25: module \"org.kde.milou\" is not installed\n"
i installed plasma-milou and krunner worked again..
so, is this a krunner bug? (as it should not depend on milou)?
or a packaging bug? (as kf5-krunner should require plasma-milou)
Last week I did my usual command-line upgrade, from F33 to F34.
Most things still work, and some (like the KDE clipboard) work better.
But of course the Applications menu changed radically. It took time for
me to find the new places for things, and one thing I never found:
I now find it impossible to start a new session with another registered
user. Now the only way to use a secondary user account is to log out,
then log in as the secondary. And do the same in reverse when I'm done.
The biggest reason I abandoned GNOME, years ago, was that GNOME did not
provide, in its Graphical User Interface, a convenient way to switch
users, and have two users logged on at once. KDE did.
It used to be on a menu called "Leave." Along with options labeled "Log
off", "Sleep," "Hibernate," "Restart," and "Shut Down."
Today all those options, other than "Switch User," appear at the bottom
of the applications menu screen. Which is mighty convenient for those
other options, but not for Switch User, which is gone.
What am I missing? If Switch User is still there, where did it go?
Sorry if this is the wrong place for this question... I've installed
Fedora 34 KDE Spin on a Lenovo P73, then I Installed VMWare Workstation
16 Pro, I then installed a Fedora 33 guest, and it works fine except it
refuses to resize / fit the guest display. I have both 'View -> Autosize
-> Autofit Guest' and 'View -> Autosize ->Autofit Window' checked
Thanks in advance
I installed Fedora 34 - KDE spin on a Lenovo P73, if I plug in an
external monitor it shows up but the external monitor is blank and I
cannot use it... changing the resolution for the external monitor has no
affect. In some cases it makes the whole system slow to a crawl, I move
the mouse wait 30sec for the move to happen, etc
I have been using a login task for a number of years with KDE.
After the upgrade to F34 KDE is no longer running my login script.
I added some logging to the script to leave evidence that it has run
and no logs are recorded.
I tried deleting the existing entry in
System Settings/Startup and Shutdown/autostart
then I added the script back in.
But that did not work.
Is there something special I need to do to make this work?
Is there a log somewhere that I can check for errors?
I installed Fedora 34, the KDE spin on a Levovo P73. If I go to "System
Settings -> Display and Monitor -> Display configuration" I see the
pulldown for the screen size which is set to 1920 x 1080, if I click on
the pulldown there are no other screen resolutions, only the 1920x1080
I noticed that when I run apps that are build with
PyQt5 under KDE wayland the app icon is a W icon and
not the apps icon as it is under KDE X11.
Is this a known issue? How do I get the app icon to be shown?
After updating to F34, I was unpleasantly surprised by the new Plasma update
notifier (plasma-discover-notifier). Even though the previous plasma-pk-updates
thing had its quirks and Apper also wasn't the most featureful of package
managers, I still ran into a handful of issues with Discover that make it
pretty much useless for me:
– There seems to be no way to select which updates to install. All I can see
is a list of available updates with a button to install all of them, but no
way to pick and choose a subset. (Yes, I could use commandline DNF with a
whole bunch of "-x" arguments to get the job done, but the point of a GUI is
to make things more user friendly, isn't it?)
– I can't seem to find the description of individual package updates (the short
changelog that plasma-pk-updates shows when you click a particular package,
together with Bugzilla or Bodhi links). Again, getting these any other way
than through the GUI updater is a real hassle.
– The tray notifier doesn't let me actually do anything directly, I have to
wait for it to open a full Discover window and spend a long while loading the
updates, which is much more disruptive than the few seconds needed to trigger
updating through plasma-pk-updates.
I can see how many people nowadays might prefer the "app store" feel of
Discover to more traditional package managers, so I'm not saying Discover
shouldn't be the default. However, can't we keep plasma-pk-updates as an
alternative for those whose needs aren't covered by Discover?
Right now, one can install f34 build of plasma-pk-updates from Koji and
everything works fine, but plasma-discover-notifier comes with Obsoletes:
plasma-pk-updates < 0.5, which I find a tad aggressive (forcing replacement of
not only any current version of plasma-pk-updates, but also any versions to
come). What about changing that to only obsolete whatever the highest version
is in F33 (so that everyone still gets the new default on upgrades), but still
letting people manually install plasma-pk-updates on F34? It's not like
plasma-pk-updates has a lot of dependencies or receives many new features, so
future maintenance burden should be minimal to negligible.
Unless there's a better solution, I'll just build plasma-pk-updates on Copr
with a bumped epoch (and Conflicts: plasma-discover-notifier). That should get
the job done, but it would be nicer (and more discoverable) to keep it in the
When I login as KDE Plasma Wayland the mouse and screen freezes.
When I look in dmesg there are lots of errors from the kernel for the nouveau driver
This is a sample of the errors there where 562 for nouveau and plasmashell:
2021-04-30T09:53:16+0100 kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD] ch 5 [017f003000 plasmashell] subc 0 class c197 mthd 2380 data 80c0091c
2021-04-30T09:53:16+0100 kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD] ch 5 [017f003000 plasmashell] subc 0 class c197 mthd 2384 data 80d0091c
2021-04-30T09:53:16+0100 kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 00000004 [INVALID_VALUE] ch 5 [017f003000 plasmashell] subc 0 class c197 mthd 2388 data 80e0091c
2021-04-30T09:53:16+0100 kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 0000000c [INVALID_BITFIELD] ch 5 [017f003000 plasmashell] subc 0 class c197 mthd 238c data 80300924
2021-04-30T09:53:16+0100 kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 00040000 [PBENTRY] ch 5 [017f003000 plasmashell] subc 0 mthd 0000 data 00000000
2021-04-30T09:53:29+0100 kernel: nouveau 0000:01:00.0: gr: TRAP ch 5 [017f003000 plasmashell]
2021-04-30T09:53:29+0100 kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 00200000 [METHOD] ch 5 [017f003000 plasmashell] subc 0 mthd 000c data 3a800000
I have a GTX 1060 6GiB card aka NVIDIA GP106 (136000a1).
Do I need to use the binary nvidia drivers from rpmfusion to have wayland work?
I updated my laptop from Fedora 33 to Fedora 34 at the weekend. Generally no
problems, and using plasma/wayland was not too bad. Sound seems to work fine
with pipewire - tested with Zoom, Teams and Amarok.
I found that the KDE 'saved sessions' wasn't working, but I gather that is
being worked on.
However, I have noticed some things with 'Konsole' which I cannot seem to
resolve. The below issues all work fine using plasma/X11 (under F33 and F34).
The issues are:
1) Konsole seems to have a thick black 'frame' around each window. This occurs
when using my laptop with the docking station, but oddly does not occur when
using the laptop as-is. I did find 'Konsole configuration -> Process and window
- Remove window titlebar and frame'. This removes the black frame, but also
removes the titlebar which I do not want to do.
2) In the 'System settings -> Window management -> Window behaviour -> Titlebar
actions (tab)' I have set the 'Maximise Button Actions' so that a middle click
will vertically maximise, and a right click will horizontally maximise the
window. Now, this works fine with firefox and (gnome) evolution, but does
nothing with Konsole. A shame as I use these two options quite a bit. Again, it
works under Plasma/X11.
3) Any idea how to set mouse buttons with wayland? When using my laptop with
the docking station, I have a (2 button) Logitech MX mouse. With plasma/X11 I
set the mouse buttons using the 'xmodmap -e pointer...' command. The mouse
settings allow me to use the centre mouse wheel for copy/paste functions -
again, used a lot with Konsole. I have installed xmodmap as it seems to be a
separate package, but under wayland it doesn't seem to do anything
(understandable I suppose since it isn't X11!).
Anyone any ideas about the above? I will carry on looking to see if I can find
anything else out to try and resolve these (I'm currently cooking tea, so it's
a bit intermittent at the moment!), but I suspect I may have to report some of
them just so that the problems are recorded/known.
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.