Configuring the Recently Used tab
by Patrick O'Callaghan
The Recently Used tab in the Kicker is divided between a top half for
applications and a bottom half for documents. Can this be changed
without editing a config file? I want to see more apps and fewer (or no)
docs.
poc
9 years, 7 months
GPG not working with K-Softwares
by Sudhir Khanger
Hello,
I am unable to sign or encrypt using gpg on any of the KDE softwares.
KMail complains about "invalid passphrase" and provides passphrase prompt.
Kgpg tells me "signing not possible or bad passphrase" but wouldn't give me
prompt to enter the passphrase.
I am on Fedora 20 running Plasma 5. I have pinentry and gpg-agent installed.
Running gpg -c encryptFile in terminal with either no pinentry-program in gpg-
agent.conf or pinentry-qt or pinentry-qt4 works just fine.
Trying to sign/encrypt on any K-application with any pinentry will give some
error.
--
Regards,
Sudhir Khanger,
http://sudhirkhanger.com
http://github.com/donniezazen
Fingerprint: 49DD C204 6035 CD92 6949 3BFD EE67 D28C 9F14 497B
9 years, 7 months
Fwd: [owncloud-devel] Resend: Announcement: Dolphin plugin v0.1
by Sudhir Khanger
---------- Forwarded Message ----------
Subject: [owncloud-devel] Resend: Announcement: Dolphin plugin v0.1
Date: Wednesday, September 10, 2014, 02:47:16 PM
From: Brüns, Stefan <Stefan.Bruens(a)rwth-aachen.de>
To: devel(a)owncloud.org <devel(a)owncloud.org>
Hi,
I have finished a first simple version of a ownCloud plugin for KDEs Dolphin.
It is able to retrieve the sync status from the ownCloud client, although it
is somewhat limited compared with e.g. the Nautilus emblems/overlays.
The limitation is due to the differences between Nautilus and Dolphin.
Nautilus is able to show arbitrary icons as emblems, whereas my plugin uses
the KVersionControlPlugin2 class. This limits the sync state to untracked,
current and syncing, sharing state is not reflected.
The current code can be retrieved from
https://github.com/StefanBruens/dolphin-plugin-owncloud
Binary packages are available for openSUSE 12.3 and 13.1:
http://download.opensuse.org/repositories/home:/StefanBruens:/branches:/K...
The code depends on KDE4 libraries and Qt4, but I think it should be trivial
to compile it against KF5/Qt5. This is also the reason for keeping this out of
mirall - it will be useful for distributions to compile it against Qt4 and Qt5
and provide both packages.
Kind regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
work: +49 2405 49936-424
_______________________________________________
Devel mailing list
Devel(a)owncloud.org
http://mailman.owncloud.org/mailman/listinfo/devel
-----------------------------------------
Thought some folks might be interested.
--
Regards,
Sudhir Khanger,
http://sudhirkhanger.com
http://github.com/donniezazen
Fingerprint: 49DD C204 6035 CD92 6949 3BFD EE67 D28C 9F14 497B
9 years, 7 months
KDE on Android?
by Timothy Murphy
I'd like to run KMail on my Android phone (Samsung Galaxy S5)
if it is possible, as I find the standard Android Email app
slightly unsatisfactory, and anyway I am used to KMail.
I see various Android apps that claim to be like KMail,
so I wondered if KMail itself, and other KDE apps like KNode,
have been transferred to Android?
I've tried KDE Connect with moderate success,
but that is just due to failure to read the docs, I expect.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
9 years, 7 months
Report from Akademy Packager BoF
by Kevin Kofler
Hi,
yesterday, we had a packager BoF at Akademy. The Fedora representatives were
me and dvratil (who was sitting around not attending any session, so I asked
him to come with me ;-) ), mostly it was me talking for us. Jgrulich planned
to attend, but did not make it because he had to take Thomas Pfeiffer to the
hospital with a leg injury.
There were not only GNU/Linux distributions represented, but also BSD and
the kdewin project (KDE for that horrible proprietary operating system you'd
want to throw out of the, well, window :-) ), and the Debian folks also
spoke for their bastard GNU/kFreeBSD port and their GNU/Hurd port.
It turns out the main pain points for us all lie in system integration, but
the issues we're having are different. The kdewin folks of course have
problems getting ANYTHING that integrates into the system to work, it always
has to be ported explicitly because their system is totally different. For
*BSD, Hurd and the like, the problems are dependencies that only support the
Linux kernel (ALSA, systemd etc.). And for us in Fedora, it is of course the
shared dependencies getting upgraded under us that KDE does not support yet.
There, the tenor was that KDE really needs to know on an earlier notice
about such changes, and I'd tend to agree with that, so I guess the REAL
problem has to be solved somewhere other than KDE. One big source of pain
was NM 0.9 and how it was dumped into F15 post-freeze on a basically
nonexistent notice. The "compromise" the NM developers came up with (the
hacked NM speaking both APIs) just didn't work out and ended up having to be
replaced in an update. Lamarque (who did the NM 0.9 port of the Plasma NM
stuff upstream) happened to be at the BoF and rightfully pointed out that
they got no notice at all from us that 0.9 support was needed until the
damage was already done, and we Fedora KDE people couldn't give him the
notice because nobody had told *us*, either. Sigh… Others I remember were
PolicyKit 1 (alias "polkit"), where we ended up having to ship the GNOME
auth agent even for KDE for a release, and BlueZ 5, where at least we got a
prerelease of BlueDevil in time.
There was also some discussion about release cycles. (I brought up that
Plasma and Apps releasing a few days after Frameworks as is now being
planned is suboptimal for us because it means we either delay the Frameworks
updates until the other stuff is out, or push Frameworks first and delay the
other stuff until Frameworks reaches stable, which means ~2 weeks.) There
were also some complaints about the monthly Frameworks releases, which are
"Firefox-style" releases, i.e. mixed features and bug fixes with no stable
branch. The kdewin folks were complaining that a release per month was just
too many for them (and also some small GNU/Linux distros) to handle to begin
with, others have the problem (already brought up on the mailing lists) that
they cannot push such releases that are not bugfix-only out to their stable
distro releases. This one is actually not really a problem for Fedora. We're
planning to just push those Frameworks updates in monthly pushes (i.e. one
per upstream release) as long as they don't start doing silly things like
changing the sonames of their libraries. At least that's what the consensus
was in the KDE SIG meetings so far (and what IMHO is the most sensible
plan).
There has also been some discussion about KDE requirements on things like
kernel settings. Somebody from upstream, I think it was Vishesh from Baloo,
asked us whether it'd be helpful for us to have KDE come with a list of
required kernel settings. We packagers pretty much agreed that such
requirements were not acceptable at all to begin with, but Vishesh and (with
his Phonon upstreamer hat on) apachelogger said that the software just can't
always work with the broken settings. There wasn't really a conclusion
reached on that issue, except that it probably has to be decided on a case
by case basis. The case in point was that, in order to be fast at indexing
(10+ times faster than e.g. Tracker) without hogging the HDD and the CPU,
Baloo needs some special scheduler options that only work in the default
Linux scheduler (CFQ) and not in the deadline scheduler Ubuntu is using. We
told them that distro kernels also need to work for GNOME and for non-
desktop use cases (server etc.) and thus we cannot necessarily satisfy every
settings request from KDE. I also compared it with the infamous Oracle
database.
Those were the main topics that have been brought up, the system integration
one having been the biggest one. We would probably have come up with more,
but at that point we ran out of time (we only had a 1-hour slot) and
deferred to mailing lists (most likely kde-packager).
Kevin Kofler
9 years, 7 months
greeter offers no KDE session
by Felix Miata
This is a 32 bit Rawhide kept as such since before F21 branch.
Boot with 3 on cmdline; startx -> Konsole help about reports 4.14.0 on normal
KDE desktop.
Boot with 5 on cmdline:
1-default session type simply opens an xterm on otherwise blank screen
2-greeter's session type offering has only 3 items, none of which are kd*
Greeter is KDM.
Greeter is unthemed.
What's necessary to get KDM greeter to offer a KD* session?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
9 years, 7 months
Plasma 5 boots into a blank black desktop
by Sudhir Khanger
Hello,
I have just upgraded my Fedora 20 box to Plasma 5. I have two problems.
1. I can't use SDDM. System shows booting Fedora 20 - kernel version.
It never reaches desktop. KDM works fine.
2. Time to time I book into black background empty desktop. There is
nothing on the desktop. No panel, etc. I can still use all the
applications using KRunne and window switching Atl-Tab.
Any idea how can I resolve these issues especially the second one.
--
Regards,
Sudhir Khanger.
sudhirkhanger.com
https://github.com/donniezazen
9 years, 7 months
The Plasma Disease
by Timothy Murphy
I see this has struck me again, after a couple of weeks.
Is it generally familiar?
The main symptom, or at least the one that causes most trouble,
is that the desktop panel no longer responds to mouse clicks.
I should say at this point that I am running Fedora-20/KDE
on a Thinkpad T61;
so there is a "TrackPoint" button instead of a mouse.
One consequence of the lack of response is that
it is no longer possible to Restart, or even Logout,
by clicking on the K-button.
Fortunately, it is still possible to change virtual desktop by Ctl-F<n>;
so I can go to a console window, and say "shutdown -h now".
(I usually shutdown rather than re-starting,
as this is more likely - but by no means certain - to cure the symptom.)
I'm sure this can't be healthy, as the shutdown is ten times faster
than the "proper" way, through the K-button.
Another symptom is that a small window open up every few seconds
at the pointer, with Paste, Copy, etc written in it;
and one cannot continue until this window closes after 10 seconds or so.
A third symptom is that rectangular tracts of the screen turn black,
briefly.
A fourth symptom is that even in a konsole screen like this
it is no longer possible to copy and paste.
One curious feature of the disease is that it usually cures itself
after 15 minutes or so.
(No, it hasn't done so in the present case.)
I'm wondering if this is a disease specific to Thinkpads -
maybe something to do with the Synaptics driver -
or if it is a general KDE affliction?
I've asked about this before, and various remedies have been suggested,
which I have religiously followed,
but none of them have cured the affliction.
If anyone knows the answer, or even the cause of the disease,
I should be very grateful to be told.
(I had a cup of coffee, and it is cured - for now.)
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
9 years, 7 months
KDE doesn't seem to see my webcam
by Orion Poplawski
Running F21, go to control center -> multimedia -> Audio and Video
Settings -> Video Recording. No devices are listed. However,
solid-hardware list does report:
udi =
'/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/video4linux/video0'
I believe as a result kamoso does not record anything. Any idea what
could be up?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
9 years, 7 months
