baloo-kcmadv in f20/kde-unstable repo
by Rex Dieter
An alternative baloo-kcmadv with more features and closer to the nepomuk
kcm is under development, and has been packaged in f20/kde-unstable repo.
Features include:
disable indexing button
whitelist/blacklist
mime/glob filtering
Once installed, you'll see a new item "Desktop Search Advanced" in
systemsettings.
-- rex
4 years, 1 month
Baloo: tags missing
by Piotr Gbyliczek
Hi,
I did the switch to KDE 4.13 and I seem to lost the tags that I've added to my
files. This is most likely due to Nepomuk - > Baloo migration.
Could not find anything useful on the list or in the web, so :
Are the tags lost , or I need to dig deeper into how to attempt to retrieve
them from some data store that Nepomuk had ?
If so, any hints or links on how to do it ?
Before any comments, found and tried some info, but nepomukbaloomigrator
crashes on me, and I can't start nepomuk from my user, only from root (where
tags aren't existing, obviously)
--
Piotr Gbyliczek
Systems Administrator (LPIC 3, Novell CLA certified)
Reconnix Ltd
T: 0845 421 0444
4 years, 1 month
digikam problem
by George Avrunin
I originally sent this message to the Fedora users list, but the only
response I got was a note from Patrick O'Callaghan suggesting it might be
better directed to the KDE on Fedora list. (I had previously posted on the
digikam users list, but got no response.) So here it is:
On a fully updated Fedora 20, I've had the following problems importing
images from a Canon EOS SL1 since the update from digikam 3.5 to 4.0
(which I got July 26):
- The digikam camera window doesn't show thumbnails or previews, just icons
for RAW and/or JPEG. I can't seem to preview the images to select the
ones to import. Digikam does recognize the camera, it just won't show
thumbnails or previews of the images on the camera.
- Digikam gets the date from JPEGs to do renaming as I have specified, but
it seems to think that all of the RAW files were created on 1969-12-31
at 19:00:00, at least from the filenames it's generating. Once the files
are imported (I just import all of them without doing any selection), the
"File properties" in digikam shows the correct date for each image. (Well,
up to time zone issues: my camera is set to Eastern Daylight Time, and
Digikam seems to be interpreting that as Universal Time and then correcting
for my computer's time zone, so things are off by 4 hours--but this was true
before the update, too. Is this a configuration problem on my part?)
- I have digikam set to create a new sub-album with the date; so I have
<root album>/<year>/<month>/<date>. I'm importing into the <month>.
JPEGs are correctly put in a sub-album with the date, but RAW images are
put into the <month>, not into a sub-album. I assume this is connected
to not being able to correctly get the date for the RAW images during the
import.
All of this (except for the time zone stuff) worked fine with 3.5. I
tried downloading the bodhi builds of digikam 4.2 for Fedora 20, but I'm
seeing the same issues as with 4.0. I looked through the digikam mailing
list archives and saw that some other people had problems with previewing
images from the camera with Canon cameras on 4.0, but the only response
was a claim that digikam was using gphoto2, with no details or follow-up.
(I can download the images from the gphoto2 command line, too. The
problem is not seeing thumbnails in the camera window to decide
what to download, or getting the dates on RAW images.) Shotwell seems to
be able to generate thumbnails of images in the camera before downloading
and gets the correct dates on RAW images.
I only started using digikam in early July, so it may well be that this is
pilot error, but I haven't been able to figure it out from the
documentation. I don't think I changed any digikam settings with the
upgrade from 3.5 to 4.0, and nothing about the camera changed at that
time.
Thanks for any help. If nobody's got a solution, should I file it on the
Fedora bugzilla, or upstream?
George
4 years, 2 months
ktorrent and ARP
by Ed Greshko
It appears that ktorrent is causing ARP packets to be sent on the local network. I don't know why, and I don't know how to prevent it.
If I'm not running ktorrent "arp" or "ip neigh show" will only display real devices that exist on my local network. But, a while after starting ktorrent the number of entries will increase and look like this.....
[egreshko@meimei ~]$ arp
Address HWtype HWaddress Flags Mask Iface
transformer.greshko.com ether 78:24:af:24:05:c6 C p128p1
192.168.1.5 (incomplete) p128p1
roku.greshko.com ether dc:3a:5e:55:c0:29 C p128p1
192.168.1.11 (incomplete) p128p1
ds.greshko.com ether 00:11:32:2a:64:e2 C p128p1
192.168.1.74 (incomplete) p128p1
wifi.greshko.com ether ac:22:0b:d1:5d:70 C p128p1
192.168.1.8 (incomplete) p128p1
192.168.1.109 (incomplete) p128p1
--
If you can't laugh at yourself, others will gladly oblige.
4 years, 4 months
what's wrong with plasma-desktop-appletsrc
by Reindl Harald
whats wrong with "plasma-desktop-appletsrc"?
the bkp-file is how it should be
some crap is adding "[Containments][68]" repeatly
until today it was enough to copy "activityId" to
"[Containments][1]", remove the rest and hard restart
X so KDE has no chance to write his crap back
well, now after doing that 3 times i still sit in
front of a empty desktop witout any widgets
4 years, 4 months
Why such an unusual name?
by Ed Greshko
In doing some checking of updates to come I noticed something that I consider "odd".
Currently I have kde-plasma-nm-0.9.3.4-12.fc20.x86_64 installed on my system. I see in updates-testing that the next update will be 0.9.3.4-14.20140916gitf2ca6ae.fc20.
Why all the extra digits?
--
If you can't laugh at yourself, others will gladly oblige.
4 years, 4 months
Ark - 4.14.1 Unar/Unrar
by Colin J Thomson
Hi,
I stumbled across this small issue today when opening a rar file directly
from say Dolphin Ark would fail with an error. Using Unrar from a shell the
file would unpack fine.
Looking at the Ark-4.14 changelog I see support for Unar had been added which
I did not have installed. Since installing Unar all is good now.
Maybe with this new change Unar should be pulled in automatically?
Apart from that no other issues found so far and the usual easy update.
F20/4.14.1
Thanks to all involved,
Colin
--
Fedora 20 - (Heisenbug)
Registered Linux user number #342953
4 years, 4 months
Fedora 21 Alpha RC testing request
by Adam Williamson
Hi, folks!
In case anyone didn't see it elsewhere, we put 21 Alpha RC1 out for
testing today. It still has some kinks, but we really need to make sure
we have a reasonably complete test run on it and catch any remaining
blockers. If folks could help test particularly in their own areas of
interest, that'd be great.
The images can be found at
https://dl.fedoraproject.org/pub/alt/stage/21_Alpha_RC1/ - it's a fairly
big tree and the folder layout is still a bit of a work-in-progress,
sorry if you have to click around until you find something.
The test pages are:
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Install
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_21_Alpha_RC1_Server
to test, basically, pick a test case from (one of) the table(s), run it,
and edit your result into the appropriate table cell using the
{{result}} macro - short version, {{result|pass|adamwill}} is a pass,
{{result|warn|adamwill|123456}} is a warning (aka the compromise between
'pass' and 'fail' - use it for things that aren't exactly critical fails
but are worth noting), and {{result|fail|adamwill|654321}} is a failure.
The number should be a Bugzilla bug #.
Please file bugs for failures; if the bug's serious, propose it as a
release blocker by setting it to block the bug 'AlphaBlocker' or using
the blocker bug webapp at
https://qa.fedoraproject.org/blockerbugs/propose_bug . Each test case
has a link to the release criteria that it enforces at the top - you can
refer to this in proposing the blocker. But please err on the side of
nominating bugs as blockers, we'd rather have a few to reject than miss
one we should have blocked for. Rejections do not go on your permanent
record :)
The test cases have milestones listed alongside them in the tables. Do
the tests marked 'Alpha' first, then the ones marked 'Beta', then the
ones marked 'Final', and the ones with no milestone come last (these are
optional tests that aren't usually expected to encounter release
blocking issues).
Later composes may follow - please do help test those too. We need to
run all the Alpha tests against at least one of the release composes
(ideally we'd run them all against all the RCs).
Thanks a lot folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 5 months
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
4 years, 5 months
