I just noticed that, while I have time in System Settings set to
Default (C), which means that time should be displayed in 24-hour
format without the AM/PM indications, and I have knode set to use
localized format, it is not honouring my system settings and is
using the old AM/PM format.
Is anyone seeing this and what is to be done?
This has happened to me frequently over the past year, but is difficult
to pin down. I thought I'd mention it here in case anyone else has seen
it. What happens is this:
1) I run "sudo dnf update".
2) The tracer plugin says I need to restart my session, usually because
some library has changed.
3) I log out (this often crashes kdeinit5).
4) I log in again. This takes longer than usual, giving the impression
that some stuff is still being cleaned up from the previous session.
5) I start working.
6) A minute or so later, I am suddenly thrown out and am back at the
7) I log in again and everything is fine.
The journal shows several lines reading:
Attempted to re-run an already running session
These are associated with konsole and kdeinit5. Also yakuake which most
people probably don't have.
It's notable that a) this never happens if I've rebooted the system
between sessions, and b) it seems not to happen if I've delayed a few
minutes before logging in again, even without rebooting.
I haven't poked around further in the journal (too much information)
but I conjecture this may be related to a bad systemd recipe, where
some component is not waiting for a previous instance to terminate.
Any thoughts on what to look for?
About a week ago, k3b-1:17.04.1-1 came out. Going by the
numbering, this is an older version (?), but it is presented
as an update to 2.0.3.
It does not update because of a missing freeworld and other
What is this new k3b? Does it reflect the new licensing, by
incorporating the codecs into the main package so that
freeworld has become obsolete? Or are we waiting for a
freeworld partner package?
Every now and then I try again wayland on plasma (intel graphics). It still
doesn't give good results here. The display is HiDPI, and many elements
(e.g. fonts) are too large. (Yes, too large, you'd expect them to be too
Just tried to update to frameworks 5.35.0 from Bhodi and dnf shows me this
Problem: cannot install the best update candidate for package kf5-
- nothing provides libexiv2.so.26()(64bit) needed by kf5-
rpm -qa |grep exiv
Fedora 26 (Twenty Six) Alpha/Beta
Registered Linux user number #342953
I've setup a Fedora 25 VM in vmware Workstation sitting in a CentOS 7
host behind an untangle firewall. After running for what seems like a
few hours the VM becomes unreachable via the port forward rules, I get
"Connection timed out" while my other VM's (CentOS 6 & CentOS 7) remain
accessible. I've disabled firewalld and enabled sshd on the Fedora 25 VM,
Any thoughts on what might be causing this?
Thanks in advance
I'm Eduard Lucena, and I'm here in the behalf of the Marketing team. As you
should know, we prepare a lists of highlights about each release, called
Talking points are key highlights of the new release. There are different
> types of talking points for different types of people: general desktop
> users/everyone, developers, and sysadmins. They are meant to provide a
> short, effective answer to the question "What cool stuff is in the latest
> release of Fedora?" They are compelling, not necessarily comprehensive
This points help us, as Marketing team, as well to Ambassadors, to
publicize each release with the news and cool stuff.
For this matter and this release, we have this wiki page:
https://fedoraproject.org/wiki/Fedora_26_talking_points and we will be
happy to include the new things in the KDE Spin.
You can help us in both ways:
1. Editing the wiki directly with the points.
2. Throwing us the list, and we will put them in the wiki.
Thanks in advance for your help and for your efforts.
GNU/Linux User #589060
Ubuntu User #8749
Fedora Ambassador Latam
It's been a good run, but it's probably time to call it quits on providing a
kde/kde-redhat/kdeforge package repository, which comes in many forms and
names, but they all basically point to the same place:
This is for various reasons, but mostly due to the fact that it is hosted
primarily at my current employer, and that relationship will be ending soon.
This post serves as notice that you should stop using it, and I will most
likely turn it off in a few weeks, let's target: June 23, 2017