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
4 years, 1 month
Kate not installed by default on Fedora 16
by Sonic
Hi..
I just found out that Kate was not installed by default on Fedora 16
even though I had selected 'KDE Software Development' during
installation. KDevelop is installed, but not Kate.
Was this a concious decision or a mistake?
regards,
Syam
11 years, 9 months
Nightmare in PIM-land
by Timothy Murphy
I'm trying to make sense of the setup in kdepim-4.8.2-1.fc16.i686.
I can say at once that this facility is in a terrible mess,
The documentation is either non-existent (KAddressBook),
out-of-date (<http://userbase.kde.org/KAddressBook>),
or utterly confused and confusing (The Kontact Handbook).
The best place to start seems to be f=>System Settings=>Personal
Information.
Clicking on this lists a number of Akonadi "resources".
I have 4 entries here which seem to be relevant to my present purpose:
Address Book
Personal Contacts
LDAP Address Book
akonadi_googledata_resource_0
Let me call these my four Contact Lists.
On highlighting any of the first three, and clicking on Modify,
I get some information about the entry.
Address Book points to ~/.kde/share/apps/kabc/std.vcf
Personal Contacts points to ~/.local/share/contacts/
LDAP Address Book points to the OpenLDAP database on my server
akonadi_googledata_resource_0 points to my Google email address.
Now I've left System Settings, and gone to f=>Office=>Personal Information
Manager.
(I can get to the same place in many ways.)
My 4 Contact Lists appear, together with a Search folder,
which I shall ignore for the moment.
I've highlighted Address Book, which is empty at the moment,
and added a New Contact, "Anne Murphy",
and a New Group, "Knapton Court Residents Association".
Checking, I see that the contact is indeed added to
~/.kde/share/apps/kabc/std.vcf
The group appears in the file ~/.kde/share/apps/kabc/distlists
However, I can see no way to add the contact to the group.
According to <http://userbase.kde.org/KAddressBook>
-------------------------------
Groups will replace Distribution Lists.
Auto completion makes it quite easy to add entries to the group.
In KDE SC <= 4.4.2 you can't use the group quite like a distribution list,
typing the name and expecting it to be expanded into a list of names.
You can, though, copy and paste the list of names from the right-hand panel.
-------------------------------
I don't really understand what this means,
but I don't see any way of associating or adding a contact
to a group.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin
11 years, 10 months
warning: "/usr/lib/debug/usr/lib64/libicudata.so.46.0.debug": separate debug info file has no debug info
by Brad Hubbard
Hi all,
Before we start, I know this is a system library and not part of KDE and
I'm more than happy to create BZs for the affected packages but given
this is effecting the debugging of kmix I thought someone might have
some input.
While looking at a core from a kmix segfault I found this warning.
warning: "/usr/lib/debug/usr/lib64/libicudata.so.46.0.debug": separate
debug info file has no debug info
So I looked further...
(gdb) info shared
From To Syms Read Shared Object Library
0x0000003c480004b0 0x0000003c480005b8 Yes (*)
/usr/lib64/libicudata.so.46
(*): Shared library is missing debugging information.
Further investigation shows the debuginfo is actually statically linked?
$ file /usr/lib/debug/usr/lib64/libicudata.so.46.0.debug
/usr/lib/debug/usr/lib64/libicudata.so.46.0.debug: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), statically linked, not stripped
nm shows few symbols exported and the following shows it is not alone.
$ for file in `ls /usr/lib/debug/usr/lib64/lib*`
> do
> file $file |grep static
> done
/usr/lib/debug/usr/lib64/libcdda_interface.so.0.10.2.debug: ELF 64-bit
LSB shared object, x86-64, version 1 (SYSV), statically linked, not stripped
/usr/lib/debug/usr/lib64/libHalf.so.6.0.0.debug: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), statically linked, not stripped
/usr/lib/debug/usr/lib64/libicudata.so.46.0.debug: ELF 64-bit LSB shared
object, x86-64, version 1 (SYSV), statically linked, not stripped
/usr/lib/debug/usr/lib64/libQt3Support.so.4.8.1.debug: ELF 64-bit LSB
shared object, x86-64, version 1 (SYSV), statically linked, not stripped
/usr/lib/debug/usr/lib64/libvorbisenc.so.2.0.9.debug: ELF 64-bit LSB
shared object, x86-64, version 1 (SYSV), statically linked, not stripped
Is this by design?
Cheers,
Brad
11 years, 10 months
lightdm in kde-testing
by Rex Dieter
Thanks to the efforts of several folks (namely Christoph Wickert), we're
getting close to bringing lightdm to fedora.
Per http://www.freedesktop.org/wiki/Software/LightDM, LightDM is a
cross-desktop display manager. In short, it's an alternative to gdm or
kdm for example.
Want to try it out? If you're comfortable with switching login managers
and being able to back out and fix things if things go awry... :) ...
we've some experimental builds in kde-testing repos (f16/f17):
yum --enablerepo=kde-testing install lightdm lightdm-gtk-greeter
and edit /etc/sysconfig/desktop to include:
DISPLAYMANAGER=/usr/sbin/lightdm
(and reboot)
and later if you're daring,
yum --enablerepo=kde-testing install lightdm-kde
and edit /etc/lightdm/lightdm.conf to include:
greeter-session=lightdm-kde-greeter
We're currently gathering feedback and a bit more testing before
submitting this for formal review to be included in fedora.
To forestall the inevitable question: Do we have plans to replace kdm?
No, not right now, but depending on how well lightdm works, maybe
sometime in the not-too-distant future (f18/f19+).
-- rex
11 years, 10 months
Updating Amarok's database
by Patrick O'Callaghan
When I rip a CD I want to add the contents to Amarok's database. It
would appear that the way to do this is by rescanning the entire system.
1) Is this true? Is there no way to simply add the newly-ripped material
without rescanning everything?
2) Even if it is true, it simply doesn't work. I can visit the new
folder via the Files view, and Amarok duly sees it, but on returning to
the Local Music view, nothing. The problem is that I want to add the new
stuff to my media player (a Galaxy Nexus), but the GN is only visible in
the Local Music view, not the Files view, so there's no way to achieve
this. Very frustrating.
<rant>
I used to like Amarok back in the KDE 3 days. I have no wish to return
to KDE 3, but I'm afraid Amarok got too ambitious and buggy. For one
thing, I find the UI really quite hard to understand, so the above
problems might just be PEBKAC.
</rant>
poc
11 years, 10 months
PackageKit-0.7.4-1 downgrades PackageKi-qt, huh?
by Martin Kho
Hi,
The latest PackageKit provides libpackagekit-qt2.so.1. The previous version
contains libpackagekit-qt2.so.2. The new version breaks apper.
Does anyone know why PackageKit-qt is downgraded?
Thanks,
Martin Kho
11 years, 10 months
Distribution list facility
by Timothy Murphy
Is there a facility in KMail/Kontacts/KAddressBook
to set up a small distribution list?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin
11 years, 11 months
strigi
by Peter G.
When I installed Fedora 17ßrc, I noticed that strigi is not
installed by default. nepomuk appears to be working properly
(given that I don't use it for anything I am aware of).
Can I continue without strigi? Since I already have
virtuoso, what would strigi give me?
11 years, 11 months