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
6 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
6 months, 1 week
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
6 months, 2 weeks
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!
9 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
1 year, 5 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
1 year, 6 months
Notice: Latest update killed sddm for nVidia driver users
by Ed Greshko
This is just a notice to others who may run into this....
I just updated a system where I use the nVidia drivers from rpmfusion. After the
update I could not get a login screen. Just a mouse cursor on a black background. I
found there to be an selinux AVC.
type=AVC msg=audit(1527130068.596:164): avc: denied { map } for pid=1205
comm="sddm-greeter" path="/dev/nvidiactl" dev="devtmpfs" ino=17300
scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=system_u:object_r:xserver_misc_device_t:s0 tclass=chr_file permissive=0
Ran...
ausearch -c 'sddm-greeter' --raw | audit2allow -M my-sddmgreeter
semodule -X 300 -i my-sddmgreeter.pp
to fix the problem.
The transaction of the update was for the following.
Upgraded gstreamer1-1.14.0-1.fc28.x86_64
Upgrade 1.14.1-1.fc28.x86_64
Upgraded ibus-table-1.9.18-2.fc28.noarch
Upgrade 1.9.20-1.fc28.noarch
Upgraded ibus-table-devel-1.9.18-2.fc28.noarch
Upgrade 1.9.20-1.fc28.noarch
Erase kernel-4.16.7-300.fc28.x86_64
Install kernel-4.16.10-300.fc28.x86_64
Erase kernel-core-4.16.7-300.fc28.x86_64
Install kernel-core-4.16.10-300.fc28.x86_64
Erase kernel-devel-4.16.7-300.fc28.x86_64
Install kernel-devel-4.16.10-300.fc28.x86_64
Upgraded kernel-headers-4.16.9-300.fc28.x86_64
Upgrade 4.16.10-300.fc28.x86_64
Erase kernel-modules-4.16.7-300.fc28.x86_64
Install kernel-modules-4.16.10-300.fc28.x86_64
Erase kernel-modules-extra-4.16.7-300.fc28.x86_64
Install kernel-modules-extra-4.16.10-300.fc28.x86_64
Erase kmod-nvidia-4.16.7-300.fc28.x86_64-3:390.48-1.fc28.x86_64
Upgraded libepoxy-1.5.1-1.fc28.x86_64
Upgrade 1.5.2-1.fc28.x86_64
Upgraded libgnomekbd-3.26.0-4.fc28.x86_64
Upgrade 3.26.0-5.fc28.x86_64
Upgraded libidn2-2.0.4-7.fc28.x86_64
Upgrade 2.0.5-1.fc28.x86_64
Upgraded libipa_hbac-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libkworkspace5-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded libsss_autofs-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libsss_certmap-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libsss_idmap-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libsss_nss_idmap-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libsss_simpleifp-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libsss_sudo-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded libwacom-0.28-3.fc28.x86_64
Upgrade 0.30-1.fc28.x86_64
Upgraded libwacom-data-0.28-3.fc28.noarch
Upgrade 0.30-1.fc28.noarch
Upgraded nodejs-1:8.11.0-1.fc28.x86_64
Upgrade 1:8.11.2-1.fc28.x86_64
Upgraded npm-1:5.6.0-1.8.11.0.1.fc28.x86_64
Upgrade 1:5.6.0-1.8.11.2.1.fc28.x86_64
Upgraded pam-1.3.0-10.fc28.x86_64
Upgrade 1.3.1-1.fc28.x86_64
Upgraded plasma-discover-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-2.fc28.x86_64
Upgraded plasma-discover-flatpak-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-2.fc28.x86_64
Upgraded plasma-discover-libs-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-2.fc28.x86_64
Upgraded plasma-lookandfeel-fedora-5.12.5-1.fc28.noarch
Upgrade 5.12.5-3.fc28.noarch
Upgraded plasma-workspace-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded plasma-workspace-common-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded plasma-workspace-geolocation-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded plasma-workspace-geolocation-libs-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded plasma-workspace-libs-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded plasma-workspace-wayland-5.12.5-1.fc28.x86_64
Upgrade 5.12.5-3.fc28.x86_64
Upgraded python3-sss-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded python3-sssdconfig-1.16.1-4.fc28.noarch
Upgrade 1.16.1-8.fc28.noarch
Upgraded qt-1:4.8.7-36.fc28.x86_64
Upgrade 1:4.8.7-40.fc28.x86_64
Upgraded qt-common-1:4.8.7-36.fc28.noarch
Upgrade 1:4.8.7-40.fc28.noarch
Upgraded qt-x11-1:4.8.7-36.fc28.x86_64
Upgrade 1:4.8.7-40.fc28.x86_64
Upgraded sddm-breeze-5.12.5-1.fc28.noarch
Upgrade 5.12.5-3.fc28.noarch
Upgraded selinux-policy-3.14.1-24.fc28.noarch
Upgrade 3.14.1-25.fc28.noarch
Upgraded selinux-policy-targeted-3.14.1-24.fc28.noarch
Upgrade 3.14.1-25.fc28.noarch
Upgraded sssd-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-ad-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-client-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-common-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-common-pac-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-dbus-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-ipa-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-kcm-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-krb5-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-krb5-common-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-ldap-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-nfs-idmap-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-proxy-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded sssd-tools-1.16.1-4.fc28.x86_64
Upgrade 1.16.1-8.fc28.x86_64
Upgraded volume_key-libs-0.3.9-19.fc28.x86_64
Upgrade 0.3.10-1.fc28.x86_64
Upgraded vte-profile-0.52.1-1.fc28.x86_64
Upgrade 0.52.2-1.fc28.x86_64
Upgraded vte291-0.52.1-1.fc28.x86_64
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.
1 year, 6 months
Okular defaults to A4 paper size
by PropAAS DBA
Okular always defaults to A4 paper size, cannot find any way to
permanently change it, other than clicking on options and changing the
paper size every time I print
Anyone know how to fix this?
1 year, 6 months