In the next hours KDE:Current will publish KDE 4.13 SC. As that this release
comes with a big change (Nepomuk -> Baloo), we would like some simple steps in
order to perform the right upgrade.
Before the upgrade
In order to migrate data automatically from the Nepomuk store to the new
format (used by Baloo), you will need Nepomuk up and running, and just for the
time needed for the migration. Ensure that Nepomuk is running before the
update (in System Settings > Desktop Search). This is only necessary in case
Nepomuk is in use on the system.
The upgrade itself
* If you are already using KDE:Current then the upgrade should be a simple
"zypper up" or upgrade packages through YaST Software Management.
* If you are not yet using KDE:Current, then please follow the instructions on
https://en.opensuse.org/KDE_repositories#Current_KDE_SC_release on how to
add the necessary repositories. After adding them, a zypper dup is required to
ensure that all the KDE packages are coming from KDE:Current.
Please do not remove nepomuk, as that otherwise the migration to baloo will
fail !! Also after the upgrade please make sure that the following package is
installed "baloo-file". After this check, log off and back on. The migrator
will then run and move all the data that can be migrated to the new system. It
will also turn off Nepomuk at the end of the migration.
At this moment it would be safe to remove the nepomuk related packages like
nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared-
desktop-ontologies. There are only a few packages left that are still
requiring the nepomuk-framework (like bangarang, kweshtunotes, etc).
Using Baloo
Unlike the 'include folders to be indexed', Baloo prefers to index everything
and exclude unwanted folders explicitly. With the standard setup, Baloo will
index all files and directories below the home-directory. All other
filesystems are indicated as omitted. This can be changed by deleting the
respective entries. Unfortunately it is not possible to switch baloo off
through systemsettings. If baloo is not wanted on the system, then the package
"baloo-file" needs to be removed to prevent files being indexed. The package
"baloo-pim" (only present when kdepim is installed) can be removed if no
search capabilities are required for kmail.
The only search client currently available for baloo, is the package called
milou. Milou can be placed in the panel for easy access and the usage is quite
simple. The search term is indicated and search results are shown for files,
emails, etc. In the Milou settings, the categories from which results are
shown can be selected. Milou can NOT be placed in the systray, as that this
would cause the plasma desktop to crash upon login.
Tags on files are no longer stored inside the database, but stored in the
extended file attributes (xattr), which are stored in separate files on the
filesystem.
Known issues with KDE 4.13
- The initial indexing can be heavy on I/O especially if there are large text
files: either one waits till the indexing is complete (this step is done only
once), or the folder containing such files is excluded using System Settings.
- Some data will be lost during the migration: in particular, emails will have
to be re-indexed, and file<->activity associations, if used, will not be
preserved.
- Milou causes the Plasma-desktop to crash if it is placed in the systray !!
Regards
openSUSE KDE Community Team
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
New search machine: is there any way to see it's settings or is it thought to be all automagical.
After an update from 4.12.4 to 4.13.1 I have noticed the following regressions and bugs:
Kmail: does not honour the settings for "events" and "special dates" any more. This seems a regression that comes in now every second release. A pity because I use it a lot to not forget the dates. So in the summary even if selected, there are no birthdays shown. But events of the calendar i.e. Eastern are shown correctly.
Import function of notes: looses all the notes and imported nothing. Not a big issue for me as they where "loosable" but still, who uses it and does not find his notes afterwards.....
Filters in Kmail did not work correctly before and after the update. But who needs filtering when s(he) has a search function, right? Still it would be nice to have this fixed before "Plasma next". What is positive however, is, that with 12.4 there was a regression of the "filter amnesia bug" that now has vanished again as it seems. So at least filter rules are just "not applied instead of vanishing or of putting mail randomly in some locker. Good.
What is good: the network-management and the functionality of it are finally usable, nice and easy even for non Linux users. The choices of being able to show or unshow Mac address etc. and other features are IMO useful. VPN presence and connection status are now shown throughout all personalities which is safe. Thank you for that.
All the other things seem to run well for now. If anybody shares the problem with the calendar dates I will file a bug-report. If there is an easy solution (like a setting "hidden under sub-menu 233") then thank you for sharing.
Cheers.
PS: if you have a certain "media-plasmoid" installed, this one holds nepomuk packages. So it has to be eliminated as apparently it has a nepomuk requirement.
---
Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi,
I've just published the first Firefox 29 for openSUSE in the mozilla:beta
repository.
Since this version is a major update to the Firefox UI I'm seeking input from
KDE users/developers which UI parts need adjustments when running under KDE.
You probably know that our Firefox switches to a bit of different behaviour when
running under KDE but with the new changes I'm not sure what's wrong now and
what needs to be adapted still.
So in case you are curious and want to give feedback, please feel free to
install the beta package and let me know.
Thanks,
Wolfgang
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi, take a look:
Problem: nothing provides libQt5Sql5-sqlite needed by trojita-0.4.1-7.7.i586
Solution 1: do not install trojita-0.4.1-7.7.i586
Solution 2: break trojita-0.4.1-7.7.i586 by ignoring some of its
dependencies
I'm guessing it requires additional (QT ?) repo..
Is this allowed ?
For me it seems a bit too early to mix qt4/qt5 packages in the same repo.
Daniele.
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hello,
as user of KDE:Current repo I also use KDE:Unstable:Extra as recommended on
KDE_Repositories wiki page. I have lates Calligra. It is version 2.9, but
there is an issue, if I wish to install calligra-l10n-cs, only version 2.8 is
available, which requires a lot of downgrade and install of some packages from
previous versions of KDE, which are otherwise not needed anymore. So that
Calligra lacks support for the Czech language at the moment. I haven't try
other languages. Could someone, please, check it and eventually enable
building of l10n packages for Calligra?
Thank You in advance,
Vojtěch
--
Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux
http://www.opensuse.org/http://trapa.cz/
In the next hour a new update for KDE:Current will be published. This update
contains the following:
* kdebase4-workspace 4.11.9 with the latest bugfixes for plasma.
* Baloo was aligned with the latest upstream patches for more stability with
regards to the cleaner and Xapian connectivity.
* Libxapian was build without SSE support for 32bit builds. It seems that
quite a number of users are using systems that do not support these
instruction sets and this causes crashes. This should now be fixed.
* KDEPIM was updated with the fixes that were created upstream for the bug
report https://bugs.kde.org/show_bug.cgi?id=333640 with regards to the knotes
migration. Now the old notes should become visible after the migration, which
should automatically start if you update from KDE:Current after 2pm CET.
Regards
Raymond
-----------------------------------------
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
p, li { white-space: pre-wrap; }In data lunedì 28 aprile 2014 14:36:50, Luca Beltrame ha scritto:
> In data lunedì 28 aprile 2014 05:22:25, Sam M ha scritto:
>
> Hello,
>
> > I think Anton means that he want to uninstall Baloo compeltely from
> > his system, just like I do. He doesn't want any Baloo code on his
>
> If you remove baloo-file, it won't touch your hard disk at all.
>
> > everybody's throat just because the KDE team thinks that this is way
> > people should be using their computers.
>
> There is no "KDE team". Unless you're referring to the openSUSE KDE team
> here, and in this case you're doing a great disservice to the
> (*volounteers*, every one of them) who package the software *you* are
> using.
>
> And even in the KDE community at large, of which I am part of, there is no
> such team. This is FOSS, not a professional organization.
>
> If Baloo was that toxic to everyone's computer, why people did not test it
> in advance? I can understand that not everyone is supposed to test beta
> software, but the fact that *zero* people, or close to zero did it tells me
> something about how much the FOSS community knows about being good
> citizens.
>
> Since the new search system was introduced, in the first beta, I wrote to
> the mailing list asking the brave to test it to ensure we had a smooth
> experience later on. Aside the openSUSE KDE team and a few others, no one
> did. How can you fix something that you do *not* know it's broken?
>
> It really makes me bitter to think that all that it was tried to do to
> ensure that reports could be caught in time to ensure a better user
> experience was all for *nothing*, and only later the complaints (and
> nothing else, almost) arrived. It makes me wonder at times why do I
> *bother* to give support on the KDE Community Forums.
>
> > was surprised that the GUI offers barely any options, and that it's
> > opt-out and not opt-in.
>
> Again, this GUI change was in since beta 1.
>
> > package be split. I want this, because I want to uninstall it. And if
>
> You could have spared a rant: there is a clear mention of the "baloo-file"
> message in the announcement we made regarding 4.13 availability in
> KDE:Current.
So, a few precisions, as this becomes a bit rough:
a) nobody (especially not me) wants to lower the admirable efforts done by programmers in FOSS, especially from who is finding the time to do this apparently aside a job in tumour research (if I am not mistaken). Chapeau.
b) I do agree that criticism is bound to be useful. So this is what I tried, I reported the one bug that may still be of interest. But I would strongly advise not to get to personal when it comes to "harsh" criticism. Sometimes with our filter on, harsh wasn't meant to be, still it appears to us.
c) a lot of people have like me the problem that they would like to do beta testing but cannot because they are bound to one production critical machine the most of the time.
d) people may get sometimes frustrated because of regressions. This is because steps forward (like the beautiful (seriously) new network management) make you happy so it is very frustrating when a regression occurs because of migration or a change like nepomuk to baloo. I guess in English this has been at the roots of the saying "if it ain't broken don't fix it". The choice of the UI is of course a philosophical one but it is IMO always a good idea to leave a choice to opt out to a service. If not for other reasons than for the baffling heterogeneity of the installations out there. So my suggestion to all programmers of indexing would be to foresee a GUI option to opt in or out of a given service. Make a package optional may make the creation of such services more complex so I would rather prefer a possibility to opt out of the function than a "take off the code right away". Given that the necessities differ so much much between individuals, the latter appears to be counterproductive.
e) Luca, you wrote:
> You could have spared a rant: there is a clear mention of the "baloo-file"
> message in the announcement we made regarding 4.13 availability in
> KDE:Current.
Could you elaborate that? I well understand there is a mailing list for kde:current? Or did you refer to a post. Just to know if I have to subscribe to that mailinglist in case.
So to put it short: thank you to everyone working often gracefully for us, criticism wasn't the aim of the OP but more a "status". And it was mostly positive (everything seems to work "great" with minor regressions, one has been fixed already and of course on services YMMV always). What I would still like to invent is a way to gratify the programmers who do the most daunting and frustrating job: bug fixing of glory-less day by day bugs. One day I will have an idea about it, up to then take my honest admiration for that.
Cheers.
P.S. A question: I have the following security file settings in my opensuse system: secure.
Now that implies that when I do run apper (just to notify me about available tings? Because to some extend this behaviour seems to me not consistent. Anybody who is knowledgeable may brief me on that. Thank you.
---
Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
LOL, so some bad "Guizmo" did eat my question:
P.S. : I have the following security file settings in my opensuse system: secure.
Now that implies that when I do run apper (just to notify me about available fixes) the program asks me for the root password to refresh the repos. But when I start a KDE session, apper will do so regardless, also without root password. Is this desired or a bug? Because to some extend this behaviour seems to me not consistent. Is apper escaping to PAM setting in that particular moment? Anybody who is knowledgeable may brief me on that. It does not appear a problem to me but I do not understand the reason for the difference. Thank you.
---
Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi guys, after upgrade to kde4-kmail does not work (oS 13.1 32bit).
Inside akonadiconsole it seems all fine but kmail starts akonadi again
and again. Unuseable.
I've removed baloo-file. Crash on kde startup with "illegal
instruction".
Any hints ?
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
recently everything I run in konsole (like mutt and vim) never gets a
chance to see F11 -- when I use it konsole maximizes and the app never
sees it
does anyone know how to tell konsole to just stoppit?
openSUSE 12.3, KDE 4.13.0
tia
--
_|_ _ __|_|_ ._ o|
|_(_)(_)|_| ||_)||<
|
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
