nntp (aka, usenet) client in kde?
by Gene Smith
I currently use t-bird with an nntp account pointing to gmane to read
this list and sereral others. Does kde have an nntp client program of
any sort? I don't see it as a possible new account type in kmail. Also,
search with kpackagekit yields nothing with "usenet" or "nntp" that is
kde specific.
-gene
3 years, 3 months
KDE Telepathy Bonjour account: This IM Account cannot be created - a
Telepathy Connection Manager named 'salut' is missing or it cannot
handle
protocol 'local-xmpp'. Please try installing salut with your package manager.
by Dennis Schridde
Hi!
I was trying to setup a Bonjour (local XMPP) account in KDE Plasma System Settings for KDE Telepathy. In `System Settings > Online Accounts > Create`, I clicked "Bonjour" in the list on the right. This action was answered with an error dialogue box: "This IM Account cannot be created - a Telepathy Connection Manager named 'salut' is missing or it cannot handle protocol 'local-xmpp'. Please try installing salut with your package manager." However, `telepathy-salut` is already installed on my machine. Does anyone have an idea how to debug this, or where I would find the actual error message that led to this?
I am using Fedora 27 KDE, with telepathy-salut currently being at version 0.8.1 (release 12.fc27), telepathy-mission control at version 5.16.4 (epoch 1, release 4.fc27) and ktp-accounts-kcm at version 17.12.1(release 1.fc27).
Best regards,
Dennis
3 years, 11 months
time to orphan/retire unmaintained uncommon kde4 language bindings?
by Rex Dieter
Looking over some broken deps reports, I came across some old packages:
kdebindings
smokeqt
smokekde
qyoto (csharp/mono)
kimono (csharp/mono)
ruby-qt
ruby-korundum
perl-Qt
Of these, the only one that's not a pure leaf package is perl-Qt (debconf-
kde depends on it).
any comment or objection to considering orphaning most (all minus
smokeqt/perl-Qt) or all of these ?
-- Rex
4 years
Emacs key binding in KDE Plasma 5?
by Sherman Grunewagen
Just moved from Fedora 21 to F25. Under F21 I had a file ~/.gtkrc-2.0 which contained
gtk-key-theme-name = "Emacs"
This enabled basic Emacs cursor motion keyboard commands in text input boxes throughout KDE,
Firefox, &c. (Outside of input boxes, KDE shortcuts ruled.)
How can I get this same behaviour for Plasma 5 w/in F25? From reading around, I've created
~/.config/gtk-3.0/settings.ini
and inserted
[Settings]
gtk-key-theme-name = Emacs
in this empty file. This has given the desired result in Firefox and Thunderbird,
but not w/in arbitrary text boxes in KDE (e.g. Alt-F2). The ~/.gtkrc-2.0 file is still
intact, by the way. It seems to have no effect. Any ideas?
-Sherman
4 years
SDDM Themes not working
by Gerald B. Cox
I find that I now cannot select themes - and I'm getting either a solid
white or blue background when SDDM starts.
When I tried to test, this is what I received:
sddm-greeter --theme /usr/share/sddm/themes/01-fedora-breeze
[11:43:09.032] (II) GREETER: High-DPI autoscaling not Enabled
[11:43:09.108] (EE) GREETER: Socket error: "QLocalSocket::connectToServer:
Invalid name"
[11:43:09.109] (EE) GREETER: Cannot connect to the daemon - is it running?
[11:43:09.317] (II) GREETER: Loading
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml...
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER: Fallback to embedded theme
Wanted to see if there was a quick fix or if this is known before I create
a bug report.
I didn't see anything on bugzilla, but might have missed it.
Thanks!
4 years, 2 months
Release blocking status and *so many* default applications
by Matthew Miller
As everyone knows, the KDE Plasma desktop is a release-blocking
artifact for Fedora releases. KDE is important to us, and we don't want
to go out the door with it broken.
But, there's a problem that's coming up more and more. One of the
release criteria is that all of the default applications need to have
their basic functionality tested.* This is particularly a problem with
KDE, because the SIG has decided to ship so many applications
(apparently three web browswers, now).
I'd like to propose that we either:
1) significantly reduce the number of default apps to a more managable
number, or
2) remove this particular blocking test from KDE in particular.
In either case, it would really be helpful to have more release-time
validation of shipped applications from the KDE sig.
* https://fedoraproject.org/wiki/Fedora_28_Final_Release_Criteria#Default_a...
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4 years, 11 months
Problems with upgrade path for kajongg
by José Abílio Matos
In another system I get this:
# dnf upgrade
Problem 1: cannot install the best update candidate for package kajongg-16.12.3-2.fc27.noarch
- nothing provides python3-twisted >= 16.6.0 needed by kajongg-17.12.2-2.fc28.noarch
...
Skipping packages with broken dependencies:
kajongg noarch 17.12.2-2.fc28 fedora 4.7 M
Regards,
--
José Abílio
4 years, 11 months
update target size of KDE image
by Kamil Páral
Hello,
QA is trying to consolidate target sizes for all images built by Fedora into a single document that we can easily check, in a response to one of blocking images being oversize again [1]. The document of choice is this wiki page [2]. In a newly added column, the target size of each release-blocking image will be documented. (It can also contain target sizes of non-blocking images, but our major focus is on the blocking ones, of course). The target size will be a blocker for Fedora Final releases.
The target sizes for KDE image are currently considered [3] as follows:
KDE Live 2 GB
We'd like you to think over whether this is still correct, decide on new numbers if needed, and then write it down into the document [2]. (If you decide to change it in the future, notifying us at the same time is very appreciated.)
We'd like to avoid the situation when the image goes oversize and the target size is simply bumped, because it adds delays to the release process. So please think ahead and choose a size that you really want to keep and block on it (You can of course also choose to have no=unlimited target size).
QA suggests you choose a 4.7 GB target size (single-layer single-side DVD). The current 2 GB size was chosen probably because 2 GB flash drives were common for giveaways in the past. The technology has moved on and such small sizes are probably not common anymore.
Thank you.
[1] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.or...
[2] https://fedoraproject.org/wiki/Releases/28/ReleaseBlocking
[3] https://fedoraproject.org/wiki/QA:Testcase_Mediakit_ISO_Size#Expected_Res...
5 years
Restoring manually saved sessions
by Patrick O'Callaghan
I use the above because my session is fairly complex, involving 6
virtual desktops and a bunch of apps I like to keep open. However some
(but not all) Gnome apps don't remember which desktop they are supposed
to be on. An example of one that works is Evolution, which always
starts up on the correct desktop. A couple that don't are Firefox and
Chrome. This may be because I keep multiple tabs open on several
desktops at once. On restarting the session I get the tabs back, but
all piled up on one desktop, so I then have to move them around.
Is there a work-around for this behaviour, or am I wasting my time even
trying to do something that can't be done?
poc
5 years