My "akonadi_nepomuktag_resource" is offline since KDE-4.13
by Laurent Rineau
Hi,
My system if Fedora 20, with the kde, kde-testing, and kde-unstable
repositories enabled.
In Kmail, I have virtual mail directories, under "Tags". Since the update to
KDE-4.13 (with Baloo), that "Tags" directory is marked as "Offline", and I do
not have any way of toggle it online. In the Akonadi Console, that set of
virtual directories is governed by a resource named
"akonadi_nepomuktag_resource", but I do not see which Akonadi agent is
responsible for it. Probably it is gone since the upgrade.
How can I handle that issue? That is probably a bug in the migration agent.
--
Laurent Rineau
http://fedoraproject.org/wiki/LaurentRineau
9 years, 9 months
Re: Advice needed on dealing with kicad, kipi-plugins and kdepim
by Rex Dieter
On 07/15/2014 11:17 AM, Syam Krishnan wrote:
> On 07/15/2014 05:39 PM, Daniel Vrátil wrote:
>> speaking with my KDE PIM developer hat on, I think it makes a lot of
>> sense to
>> actually split the package per-app, so we would have
>>
>> kdepim-akonadiconsole (I'd actually prefer if this was not installed by
>> default, so that people would not be tempted to play with it :P)
>> kdepim-akregator
>> kdepim-blogilo
>> kdepim-kaddressbook
>> kdepim-kjots
>> kdepim-kleopatra
>> kdepim-kmail
>> kdepim-knode
>> kdepim-knotes
>> kdepim-kontact
>> kdepim-korganizer
>> kdepim-libs (libs shared by multiple PIM apps)
>> kdepim-common (?) (shared executables, like incidenceeditor-ng, Akonadi
>> agents, etc)
>
> One suggestion (apologies in advance if I've not understood it
> correctly). Why "kdepim-*" naming for applications?
It's a convention to highlight the originating module where the subpkg
comes from. We *usually* follow this in split kde packaging,
kde-baseapps being a recent exception. I think I'd prefer to follow
that here too, but I won't insist on it.
> I think we had something like this for kate, okteta etc. which was
> sometimes irritating since one had to yum search for "*kate*" to figure
> out the package name for installation. Anyway, nowadays, its just kate
> and okteta, and I'm liking it.
Indeed, we had kdesdk- prefix for these once, but that was prior to
upstream doing split tarballs for us.
-- Rex
9 years, 9 months
Panel freezing
by Timothy Murphy
I'm running Fedora-20 with KDE 4.12
(not quite sure how one defines the KDE version now?)
Every hour or so the panel does not take any input,
eg I cannot change virtual desktop by clicking on them,
although I can change them by eg Ctrl-F3 or Ctrl-F5.
I haven't found any way to cure this
except to log out and login again.
Has anyone else experienced this?
There are various other misfeatures allied to this, I think,
eg slabs of text get highlighted in a curious way.
But the panel freezing is the most obvious symptom.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
9 years, 9 months
KDE Connect firewall rules
by Richard Z
Hi,
perhaps these firewall rules are useful to someone, works for me
when "192.168.2.0/8" is the local network where the Android device
connects.
# firewall-cmd --permanent --add-rich-rule 'rule family="ipv4" source address="192.168.2.0/8" port port="1714-1764" protocol="udp" accept'
# firewall-cmd --permanent --add-rich-rule 'rule family="ipv4" source address="192.168.2.0/8" port port="1714-1764" protocol="udp" accept'
Richard
---
Name and OpenPGP keys available from pgp key servers
9 years, 9 months
Re: PyQt5 missing from KF5 packaging?
by Rex Dieter
On 07/12/2014 10:42 AM, Markus Slopianka wrote:
> Hi.
> Is PyQt5 missing from F21's KF5 packaging or does PyQt5 just have a different
> name and I'm too stupid to find it? ;-)
PyQt5 is not part of KF5, it's in the main repo(s), as python-qt5 (but
'yum install PyQt5' will get it too).
-- Rex
9 years, 9 months
PyQt5 missing from KF5 packaging?
by Markus Slopianka
Hi.
Is PyQt5 missing from F21's KF5 packaging or does PyQt5 just have a different
name and I'm too stupid to find it? ;-)
Markus
9 years, 9 months
SSH Key Management on KDE
by Sudhir Khanger
Hello,
I am wondering how you guys manage multiple ssh keys on your system.
This is how I got to manage multiple keys on my system.
Generate keys
ssh-keygen -t rsa -f ~/.ssh/test_ssh_key_1 -C "yours(a)yours.com"
ssh-keygen -t rsa -f ~/.ssh/test_ssh_key_2 -C "yours(a)yours.com"
ssh-keygen -t rsa -f ~/.ssh/test_ssh_key_3 -C "yours(a)yours.com"
ksshaskpass came already installed and SSH_ASKPASS set to /usr/bin/ksshaskpass.
Moving on these keys can be added to ssh-agent using following command.
ssh-add ~/.ssh/test_ssh_key_1
I ran these commands through KRunner so it triggers ksshaskpass and
not password prompt on the terminal. This way Kwallet will save the
password and I will not be asked to enter passphrase every time I am
accessing anything over ssh.
In order to automatically load these keys at system start I created
following script.
~/.kde/Autostart/ksshaskpass
#!/bin/sh
export SSH_ASKPASS=/usr/bin/ksshaskpass
ssh-add ~/.ssh/test_ssh_key_1 < /dev/null
ssh-add ~/.ssh/test_ssh_key_2 < /dev/null
ssh-add ~/.ssh/test_ssh_key_3 < /dev/null
chmod 755 ~/.kde/Autostart/ksshaskpass
The problem is if KWallet is not opened as soon as system is started
KDE will start the script triggering ksshaskpass to ask to enter
password for the first ssh key. This is a working setup but not
perfect.
I was wondering if there is a way to ssh-add the key to ssh-agent
on-demand or maybe trigger to open KWallet instead of ksshaskpass.
What is wrong with my setup? How do you manage your ssh keys?
--
Regards,
Sudhir Khanger.
sudhirkhanger.com
https://github.com/donniezazen
9 years, 9 months
KDE cpu usage pop-up?
by Gene Smith
Since installing f20 I now see a pop-up that appears when, it seems, cpu
usage has dropped below a certain point, typically when not typing or
moving the mouse after maybe a minute. The same pop-up appears
immediately when cpu usage increases, like after moving the mouse or
resuming typing.
The pop-up appears for only a about a second and is a small bar-graph
with cpu usage in percent and a square "monitor" icon on the left.
I have looked at KDE setting and see nothing that relates to this. Also,
have searched online and found nothing about it. I have not installed
plasma widgets that might cause this, AFAIK.
I don't see it when running Gnome (which I rarely do) so I assume it is
coming from KDE, but not sure.
Can someone tell me what this is?
-gene
9 years, 9 months
Re: 2014-07-09 @ **17:00 UTC** - F21 Blocker Review #1
by Dan Mossor
On 07/09/2014 02:07 PM, Igor Gnatenko wrote:
> Hi,
> On Wed, Jul 9, 2014 at 4:20 AM, Mike Ruckman <roshi(a)fedoraproject.org> wrote:
>> # F21 Blocker Review meeting #1
>> # Date: 2014-07-09
>> # Time: 17:00 UTC (13:00 EST, 10:00 PST)
>> # Location: #fedora-blocker-review on irc.freenode.neteria
>> ...
>> ==
>> // Mike
>> Fedora QA
>> irc: roshi | twitter: roshi_fedora
>> blog: roshi.fedorapeople.org
> Why this msg not going to the test-announce@? :P
>
It did go to test-announce - well, to test@, anyhow. But because this is
a blocker review meeting discussing bugs that will block the release of
fedora.next, roshi was inviting the interested WGs and SIGs since they
have skin in the game.
--
Dan Mossor, RHCSA
Systems Engineer at Large
Fedora QA Team | Fedora KDE SIG | Fedora Server SIG
Fedora Infrastructure Apprentice
FAS: dmossor IRC: danofsatx
San Antonio, Texas, USA
9 years, 9 months
Re: 2014-07-09 @ **17:00 UTC** - F21 Blocker Review #1
by Bruno Wolff III
On Wed, Jul 09, 2014 at 23:07:12 +0400,
Igor Gnatenko <ignatenkobrain(a)fedoraproject.org> wrote:
>Hi,
>On Wed, Jul 9, 2014 at 4:20 AM, Mike Ruckman <roshi(a)fedoraproject.org> wrote:
>> # F21 Blocker Review meeting #1
>> # Date: 2014-07-09
>> # Time: 17:00 UTC (13:00 EST, 10:00 PST)
>> # Location: #fedora-blocker-review on irc.freenode.neteria
>> ...
>> ==
>> // Mike
>> Fedora QA
>> irc: roshi | twitter: roshi_fedora
>> blog: roshi.fedorapeople.org
>Why this msg not going to the test-announce@? :P
I don't think the meeting log needs to go to test-announce. If the complaint
is really about the meeting notice, then that is arguably a reasonable
suggestion.
9 years, 9 months
