I see this fairly often, I use spectacle to grap screenshots of grapgs
for a report I create weekly. Often after several screen grabs I click
"take new screenshot" and I get the cursor to draw a rectangle but I
cannot get it to go away with enter or esc so I end up hard powering off
the laptop which sometimes causes other havoc
Forwarding this here, since I was rightly told it's a better place for
-------- Original Message --------
Subject: Re: KDE toolbar frozen in F25, was: Cannot choose window
manager at login, and keyboard problem
Date: 2017-01-04 23:40
From: Patrick O'Callaghan <pocallaghan(a)gmail.com>
Reply-To: Community support for Fedora users
On Wed, 2017-01-04 at 17:23 +0100, M. Fioretti wrote:
> On 2017-01-04 16:22, M. Fioretti wrote:
> > The other problem
> > in my original post does exist though, i.e. the keyboard switching,
> > without possibility to revert it. In addition to this, now that I am
> > working in a KDE session, I have to report that the toolbar at the
> > bottom
> > does NOT responds to mouse clicks. My mouse works perfectly. It does
> > what
> > I want, as usual, in any part of the screen, except the bottom toolbar.
> > If I click on the fedora icon, it does not open the menu (it only did
> > once,
> > right after I logged in). If I click on the hour, it does not show the
> > calendar,
> > etc...
> > No idea of what is happening, and if this and the keyboard thing are
> > related.
> > How could I debug this better?
> I have noticed only now that the KDE toolbar is REALLY frozen: if I
> "date" in
> a terminal, I get the current date (5:17pm as I write this). But the
> clock widget
> is stuck at 1:58pm
You're almost certainly going to get more feedback by asking on the KDE
Fedora list rather than the general Users list.
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
On Fri, 2017-01-20 at 17:33 +0000, Fedora compose checker wrote:
> x86_64 Workstation-boot-iso memory_check peak memory: 717MiB
> x86_64 Workstation-boot-iso memory_check@uefi peak memory: 715MiB
So this is another shiny new openQA / check-compose feature: there's
now a test which just runs an install with the `debug` kernel param,
which triggers anaconda to record memory usage throughout the install
process, then uploads the usage data file.
check-compose then notices jobs which do this, grabs the memory usage
data file, and includes the peak usage during installation in the
report. Tomorrow, it should include a comparison to today's usage (we
don't get the comparison today, because today's the first compose we
have the data for). If the usage changes significantly and we want to
know why, we can go check the raw data file for more information (I
guess I should enhance check-compose to link to it).
For the moment we're just running this test on the Workstation boot
ISO, as it's likely to be the most memory-intensive install in openQA's
set (network installs use more memory than DVD installs, and the
Workstation network install has more packages than the Server network
As for the test results, there is a whole bunch of stuff going on, too
much to break out test-by-test. Here are the highlights:
1) There is some kind of systemd bug which essentially means that
occasionally, the system boots to emergency mode instead of booting
properly. This affects about a half dozen tests every day, on average -
never the same ones, the bug is quasi-random, it just...happens
sometimes. That's https://bugzilla.redhat.com/show_bug.cgi?id=1414904 .
I'm currently trying to pin that one down.
2) There is an AVC that appears on boot on just about all installs of
Rawhide at present:
this causes the large number of soft failures, because many openQA
tests now run a check for any AVCs or crash notifications after
installation, and if any are found, it's considered a soft failure.
3) All i686 installs (and live image boots...really, Rawhide is just
entirely broken on i686) are broken and have been since (IIRC) systemd
v232. I think someone pointed me to a bug which may be the cause of
this, but I've lost the reference. It's on my list to figure out soon.
4) KDE upgrades are running into a dependency issue: 'kde-runtime-
drkonqi-16.08.3-3.fc24.x86_64 requires kde-runtime = 16.08.3-3.fc24,
but none of the providers can be installed'. I haven't reported this
properly yet, sorry, I should.
5) Russian installs are failing because of an anaconda bug:
6) The desktop_browser test needs a needle update, I'll take care of
7) All the 'check if all services start correctly' tests for various
images fail because of this SELinux/systemd issue:
It occurs to me that we have kind of a recurring story: 'new systemd
release lands in Rawhide, stuff breaks because it does stuff SELinux
doesn't expect it to'. It might be nice if we could organize some kind
of co-ordination between systemd and SELinux folks such that the
appropriate SELinux permissions get added *before* the new systemd
release lands. Of course, it would make things easier if we could
provide upstream systemd with a nice easy way to test their git master
on Fedora Rawhide, I guess.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
I have a pretty old machine with ATI R4850 in it using open source drivers. It
runs F25, and until recently was booting fine.
I have changed my old monitor to an UHD monitor, and that's where the problems
started. I simply can't get screen to display anything, it seems, unless :
1. I connect old monitor. It shows Plymouth, then it is only active screen in
SDDM, and then it turns off, leaving UHD display working. That last feature is
I think thanks to fact that I've disabled it in System Settings -> Display and
Monitor -> Display Configuration, as before it stayed on.
2. I set grub to use a theme. UHD screen is flashing through Plymouth run
(trying to find correct resolution ?), then SDDM is shown, fully working. Upon
login I can see KDE loading screen, and I'm back to blank screen presumably
cycling through resolutions, as screen goes off, then on, then off and displays
My assumption is that the monitor's preferred resolution is way more than my
old machine can display, and it struggles with it. Any ideas on how to set the
correct resolution for it KDE, and maybe for Plymouth ?
I've tried setting modelines and resolution in xorg.conf file
(/etc/X11/xorg.conf.d/00-video.conf to be precise), as well as presumably
disabling EDID. It seems to have no effect.
For Plymouth, I'm not too concern about it, I can live with text boot, but it
was nice thing to have. I would prefer to have text based grub, rather than a
Any ideas I could try ? Any specific settings for this ? As said, tried to set
up modelines and specific resolution, but maybe this was not picked up
Thanks in advance.
Solutions Engineer (LPIC 3, Novell CLA, AWS SAA certified)
Tel: 0845 4210444
Should it be possible to run KDE plasma in a VNC session?
When I try starting it I get the dialog box...
Plasma is unable to start as it could not correctly use OpenGL2. Please check that your
graphic drivers are set up correctly.
You're Welcome Zachary Quinto
Currently I am running, and have been running for sometime, ktorrent-5.0.1-1.fc24 which I
believe comes from rdieter-ktorrent's repo.
Well, today there is an update to kf5-libktorrent that can't be installed due to
[root@meimei ~]# dnf --best update
Error: package ktorrent-5.0.1-1.fc24.x86_64 requires libKF5ktorrent.so.6()(64bit), but
none of the providers can be installed
(try to add '--allowerasing' to command line to replace conflicting packages)
I currently have kf5-libktorrent-2.0.1-2.fc23 installed.
Is ktorrent-5.0 going to go into the F25 release/update repos soon?
You're Welcome Zachary Quinto