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
My system if Fedora 20, with the kde, kde-testing, and kde-unstable
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.
pam-kwallet brings to kde what gnome-keyring-pam is for gnome. It offers
the ability to automatically open your kwallet using your login password.
Builds are available in kde-testing repo, package review is at:
1. install pam-kwallet
2. set kwallet password to be the same as your login password
3. make sure kwallet is configured to *not* autoclose wallets under any
circumstances (pam-kwallet only functions once on initial login, it will not
reopen closed wallets)
4. configure pam accordingly. in short, add
-auth optional pam_kwallet.so
-session optional pam_kwallet.so
(near similar pam-gnome-keyring entries) in your loginmanager pam
configuration. I added these to /etc/pam.d/kdm for example, since I'm
On 04/26/2014 09:56 AM, Timothy Murphy wrote:
> I'm trying to "KDE connect" my Fedora-20/KDE laptop
> and my Samsung Galaxy S2 phone (Android version 4.1.2).
> I've followed the instructions in
> Every thing works fine, but at the final step (Pairing)
> Launch KDE Connect on Android.
> You should see the hostname of your KDE desktop listed
> under "Not paired devices".
> I do not see my desktop, or anything else, listed.
> Wireshark shows that the phone sends an identifying packet,
> but I don't see any evidence that the laptop sends anything.
As hinted in the other followup, the firewall is getting in the way.
I usually just set the network to the "trusted" zone (though I'm having
trouble getting kde-connect to actually do anything since upgrading the
phone to 0.6)
On 04/28/2014 07:13 PM, Rex Dieter wrote:
> pam-kwallet brings to kde what gnome-keyring-pam is for gnome. It offers
> the ability to automatically open your kwallet using your login password.
> Builds are available in kde-testing repo, package review is at:
> To test,
> 1. install pam-kwallet
> 2. set kwallet password to be the same as your login password
> 3. make sure kwallet is configured to *not* autoclose wallets under any
> circumstances (pam-kwallet only functions once on initial login, it will not
> reopen closed wallets)
> 4. configure pam accordingly. in short, add
> -auth optional pam_kwallet.so
> -session optional pam_kwallet.so
> (near similar pam-gnome-keyring entries) in your loginmanager pam
> configuration. I added these to /etc/pam.d/kdm for example, since I'm
> testing kdm.
> 5. profit!
Sorry, failed to mention, I think only kde-4.13.0 supports this yet, so
I think I'll move those builds to kde-unstable
On 04/29/2014 07:13 PM, Peter Gueckel wrote:
> Rex Dieter wrote:
>> pam-kwallet brings to kde what gnome-keyring-pam is for gnome.
> 2 Questions:
> 1. I am using gdm, not kdm, so where would I put those pam -auth and -
> session configurations? You mentioned that you put yours in /etc/pam.d/kdm.
> Would I add them to a gdm file (if there is one)?
I'm guessing gdm uses /etc/pam.d/gdm-password, though rule of thumb is
to put pam_kwallet.so entries wherever you see pam_gnome_keyring.so
> 2. I am really confused by all of this password stuff. There is also an
> application called ksshaskpass. I have that installed and I added a script,
> exactly as shown in the directions, to ~/.kde/Autostart. Does pam-kwallet
> make ksshaskpass redundant? Must I/Can I/Should I leave the script in
> Autostart intact?
ksshaskpass unrelated to pam or kwallet, as far as I know. So, to answer
your questions specifically: no, yes, respectively.
I think there may not be a way around this unless I run a separate "DISPLAY" for each monitor....but here goes.
I'm running KDE in F20 with 2 monitors. Chrome or Firefox will open a new window when viewing a baseball game on mlb.com (for example). I move that window to my "second" screen and place it in "full screen" mode. All is well and good until I move my mouse back to my "primary" screen and a window there take focus. At that point the window on my "second" screen exits full screen.
Anyway to keep that from happening?
Getting tired of non-Fedora discussions and self-serving posts
On 04/27/2014 02:49 AM, Eli Wapniarski wrote:
> I get this when trying update
> Error: Package: kde-workspace-ksplash-themes-4.11.8-1.fc20.noarch
> Requires: kde-workspace = 4.11.8-1.fc20
> Removing: kde-workspace-4.11.8-1.fc20.x86_64
> kde-workspace = 4.11.8-1.fc20
> Updated By: kde-workspace-4.11.9-1.fc20.x86_64
> kde-workspace = 4.11.9-1.fc20
hrm, looks like I missed copying/linking the noarch content from i686
repo to x86_64. should be fixed now (when mirrors sync).
I get this when trying update
Error: Package: kde-workspace-ksplash-themes-4.11.8-1.fc20.noarch
Requires: kde-workspace = 4.11.8-1.fc20
Removing: kde-workspace-4.11.8-1.fc20.x86_64 (@kde-redhat-testing)
kde-workspace = 4.11.8-1.fc20
Updated By: kde-workspace-4.11.9-1.fc20.x86_64 (kde-redhat-testing)
kde-workspace = 4.11.9-1.fc20
Thanks for looking into this
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
On 04/26/2014 09:16 AM, Colin J Thomson wrote:
> I see there are some updates for kde-workspace but notice the updates also
> want to install nepomuk-core* and virtuoso-opensource. I thought nepomuk was
> not not required now we have Baloo?
Yes and no. I'd done a nepomuk-free build for kde-unstable before, I'll
do it again for 4.11.9 (building now).