April 2014 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] Updating to KDE SC 4.13 from KDE:Current
by Raymond Wooninck 16 May '14

16 May '14

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

13 28

[opensuse-kde] KDE update, some observations
by stakanov＠freenet.de 02 May '14

02 May '14

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

16 85

[opensuse-kde] Firefox 29 (Australis)
by Wolfgang Rosenauer 28 Apr '14

28 Apr '14

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

8 11

[opensuse-kde] About packages in Extra
by Daniele 28 Apr '14

28 Apr '14

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

2 4

[opensuse-kde] Missing language support for Calligra 2.9
by Vojtěch Zeisek 28 Apr '14

28 Apr '14

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/

2 4

[opensuse-kde] Fwd: Updates to KDE:Current
by Raymond Wooninck 28 Apr '14

28 Apr '14

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

3 2

Re: [opensuse-kde] KDE update, some observations
by stakanov＠freenet.de 28 Apr '14

28 Apr '14

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

3 2

Re: [opensuse-kde] KDE update, some observations
by stakanov＠freenet.de 28 Apr '14

28 Apr '14

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

2 1

[opensuse-kde] after upgrade to kde4-13 kmail does not work anymore
by Daniele 28 Apr '14

28 Apr '14

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

6 18

[opensuse-kde] konsole started stealing F11
by tooth pik 28 Apr '14

28 Apr '14

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

2 5

[opensuse-kde] wastebin-trashcan problem
by Hans de Faber 27 Apr '14

27 Apr '14

Using: Linux 3.11.10-7-desktop openSUSE 13.1 (Bottle) (x86_64) KDE 4.13.0 Hi Everybody, I have a long existing problem. If I login as root i can select in the kde-plasmoids the trashcan. This trashcan works as expected. If I login as user i can only select the wastebin, this wastebin V 1.0 doesn't work. Error "Mallformed URL Trash:/" I renamed my .kde4 directory, a fresh .kde4 dir was then created, logout login, the same problem. How can I remove this wastebin v1.0 ? Thanks, Hans -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 3

[opensuse-kde] Questiin about the new 'Weet Babboo'
by Basil Chupin 27 Apr '14

27 Apr '14

The new search engine which replaced Nepopuke, when a file is deleted is it and its contents purged from the database of 'Sweet Babboo'? BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

Re: [opensuse-kde] Updating to KDE SC 4.13 from KDE:Current
by Raymond Wooninck 25 Apr '14

25 Apr '14

On Friday 25 April 2014 12:10:49 David Alston wrote: > > Does this mean that the krunner and dolphin searches will no longer work? Those are also still working and you can search for emails within Kmail. However in Kmail you can not search for files, in dolphin you don't see emails, etc :) So this is where Milou comes in. The krunner is based on Milou, so that one also works. > Thank you so much for the heads up on the changes, btw. The extra > information was very helpful to me. Great to hear. It was the first time that we created a kind of release note as that we believed it was important to set the right expectations for baloo and to make sure that the Nepomuk -> Baloo migration would be done correctly. But given the positive feedback, I think we will do this with every major update (e.g. KDE 4.14). Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] KDE Desktop Session Locked, unable to unlock: no password entry fields!
by Philip Amadeo Saeli 25 Apr '14

25 Apr '14

I am locked out of my desktop session and the screen locker will not diaplay the user/password entry fields to I can unlock it. After applying the latest updates on my otherwise stock openSUSE-13.1 system via YOU, prior to rebooting the system (by clicking the YaST2 popup which states "These updates require a system reboot to function properly. ... Reboot the system as soon as possible."), I clicked the icon to lock the screen since I had to leave for a while and wanted to wait until I returned to perfrom the systme reboot. The problem is that the screen locker does not display the login dialog at all, but only shows the background image. I've tried every sensible mouse click and keyboard input I could think of with no response. I also tried logging in to a cmdline session and sending various signals and cmdline incantations to the kscreenlocker_greet process (which appears to be the culprit). The only result I was able to achieve was that it would die then quickly respawn in the exact same situation (!?!). What to do? How can I now get back in to my desktop session so I can complete the cleanup of the remaining running interactive processes and preform a graceful reboot of my system? Is there any to kill the screen locker and get back to a normal desktop session? Any ideas (short of a shutdown from another login to the system). I have verified the the Xorg server and related GUI processes for the apps I'd left running (GVim, Konsoles, etc.) are indeed still running BTW, prior to the updates, everything had been working just fine, including the KDE screen locker. Thanks, --Phil -- Philip Amadeo Saeli psaeli(a)zorodyne.com -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] How to configure Konsole to start up with multiple tabs?
by Philip Amadeo Saeli 24 Apr '14

24 Apr '14

Hi, I am running stock openSUSE-13.1 using the KDE desktop. I am rather new to KDE 4 and am still getting used to it and have a number of questions WRT setting it up and using it. This is the first of my questions. I would like to be able to configure Konsole to be able to start up Konsole instances with multiple tabs and other specific attributes. I've investigated Konsole Profiles and the "Manage Profiles" settings, but can't seem to be able to find what settings I will need to accomplish this. With previous versions of KDE (esp KDE 3.x), I was able to create Konsole profiles such that I could start up Konsoles by using a command something like, "konsole --profile MyProfile", and get what I needed. IIRC, I may have had to manually edit some of the files involved to get things just right, but I was able to make it work as desired. Does anything like this (or, at least functionally equivalent, however, it is implemented and configured) in the KDE 4 in openSUSE-13.1? Thanks! --Phil -- Philip Amadeo Saeli psaeli(a)zorodyne.com -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 2

[opensuse-kde] mixed versions of kdebase4-* packages in KDE:Current for oS 12.3
by mararm 24 Apr '14

24 Apr '14

Hi, I just noticed that I have a mixture of 4.11 ands 4.12 versions in my KDE packages. $ rpm -qa | grep kde | grep 4.11 libproxy1-config-kde4-0.4.11-2.1.1.x86_64 kdeartwork4-sounds-4.11.2-5.1.noarch flash-player-kde4-11.2.202.350-2.68.1.x86_64 kdebase4-workspace-4.11.8-3.1.x86_64 kdebase4-workspace-plasma-calendar-4.11.8-3.1.x86_64 python-kdebase4-4.11.8-3.1.x86_64 kdebase4-workspace-ksysguardd-4.11.8-3.1.x86_64 kdebase4-workspace-liboxygenstyle-4.11.8-3.1.x86_64 kde4-kgreeter-plugins-4.11.8-3.1.x86_64 whereas most of the other are KDE 4.12 as expected, e.g. $ rpm -qa | grep kdebase4 | grep 4.12 kdebase4-nsplugin-4.12.4-1.2.x86_64 kdebase4-wallpaper-default-4.12.4-1.1.noarch kdebase4-wallpapers-4.12.4-1.1.noarch kdebase4-artwork-4.12.4-1.1.noarch kdebase4-session-4.12-1.1.noarch kdebase4-libkonq-4.12.4-1.2.x86_64 kdebase4-runtime-4.12.4-1.2.x86_64 opensuse is $ lsb_release -a LSB Version: n/a Distributor ID: openSUSE project Description: openSUSE 12.3 (x86_64) Release: 12.3 Codename: Dartmouth my repositories are KDE:Current URL: http://download.opensuse.org/repositories/KDE:/Current/openSUSE_12.3/ KDE:Extra/Current URL: http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_1… and there are 4.11-packages in the repository, so I don't think this is a local problem, e.g: http://download.opensuse.org/repositories/KDE:/Current/openSUSE_12.3/x86_64… Is this intended? Maybe I should notice that I do not have noticed any problems, the system runs fine so far. Regards, mararm -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 3

Re: [opensuse-kde] mixed versions of kdebase4-* packages in KDE:Current for oS 12.3
by mararm 24 Apr '14

24 Apr '14

Am 24.04.2014 15:39 schrieb Luca Beltrame: > In data giovedì 24 aprile 2014 15:34:41, mararm ha scritto: > Hello, > >> I just noticed that I have a mixture of 4.11 ands 4.12 versions in my >> KDE packages. > The workspace part of KDE software (the packages you have at 4.11.x) > has no > new major releases as it's been put into long term support mode. I see. > Did you do an update to KDE:Current using zypper dup? No. I changed the repositories to Current and did the update via yast -> Package-> All Packages -> Update if newer version available What is zypper dup doing differently? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] 4.12.97/4.13 bad mouse pointer on window edges
by Felix Miata 23 Apr '14

23 Apr '14

There should be a double arrow, but on a lot of installations lately, the normal pointer remains, and it's difficult to tell when grabbing the edge is possible. Is this happening to others? What package(s) is/are responsible for the available pointers? Installed branding packages here: branding-openSUSE-13.2-1.35.noarch firefox-esr-branding-upstream-17.0.11-1.4.x86_64 gfxboot-branding-openSUSE-13.2-1.35.noarch gio-branding-openSUSE-13.1-5.5.noarch gtk2-branding-upstream-2.24.23-2.2.noarch gtk3-branding-upstream-3.10.7-1.2.noarch hicolor-icon-theme-branding-openSUSE-13.1-3.6.noarch kdebase4-runtime-branding-upstream-4.13.0-1.1.x86_64 kdebase4-workspace-branding-upstream-4.11.8-2.1.x86_64 kdelibs4-branding-upstream-4.13.0-1.1.x86_64 kdm-branding-upstream-4.11.8-2.1.x86_64 ksplashx-branding-openSUSE-13.2-1.35.noarch susegreeter-branding-openSUSE-13.2-1.35.noarch systemd-presets-branding-openSUSE-0.3.0-9.1.noarch wallpaper-branding-openSUSE-13.2-1.35.noarch yast2-qt-branding-openSUSE-13.2-1.35.noarch -- "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/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 3

[opensuse-kde] kate ghost process
by Malte Gell 22 Apr '14

22 Apr '14

Hello, when I log into KDE a kate process wants to start. There is no kate window appearing, but when I use ctrl-f1 I see a kate process. This "ghost process" even avoids starting other programs! I always have to kill it using ctrl-f1. I looked with find ~/.kde4/ -name "*kate*" but I see nothing that gives a hint what or where kate is being started from... At what point could kate be started from the system? When I leave KDE there is no kate process left, so there is no reason to start a forgotten kate process when logging in again. Any hints on that? Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] KDE and power saving
by Malte Gell 21 Apr '14

21 Apr '14

Hello, recently I had severe trouble to resume my machine from suspending when I suspended from within the K menu. The Nvidia graphics driver went mad after resuming and I had to kill the X server. And hibernating did not work correctly, the machine did not go down correctly, had to shut it down hard. I used the K menu entries for powersaving. Now I found out something very interesting, when I use the command line tools pm-suspend or pm-hibernate, everything is fine! The Nvidia graphics resumes properly and the machine hibernates perfectly! This leads me to 2 questions, first, what power saving method is used when you use the powersaving entries from within K menu? Second, how can I tell KDE to use the command lind tools pm-suspend and pm-hibernate for powersavin? Pm-suspend and pm-hibernate has only one drawback, it does not lock the KDE session screen, thus anyone who wakes up the machine can get into my KDE session. I´m on openSUSE 13.1 Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] Update of kdebase4
by Constant Brouerius van Nidek 21 Apr '14

21 Apr '14

With the last update (zypper dup) on my Tumbleweed version I found that the update hangs at kdebase4-openSUSE-13.1-2.9.i586.rpm and two other kdebase4 files. Reason "Digest verification failed etc.." Further study found that the versions which failed are of a earlier version than installed (version 13.1-6.9.11. Seems something is amiss in Tumbleweed standard.. Somebody else with this problem? -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.14.1-24.geafcebd-default KDE Development Platform: 4.12.4 12:11pm up 3:06, 4 users, load average: 1.04, 1.02, 1.04 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] Re:
by Roman Bysh 17 Apr '14

17 Apr '14

On Thu 17 Apr 2014 02:18:54 PM EDT, Raymond Wooninck wrote: > Dear All, > > As you might have read on the KDE website or through blogposts, KDE 4.13 was > officially released yesterday evening. > > As indicated KDE 4.13 is currently only available through KDE:Distro:Factory, > however the target is to have KDE:Current delivering the KDE 4.13 packages > around Friday 25th April. This would allow us to validate if there are any > major breakages and to properly prepare the packages for a wider audience. > > For those that are considering to switch to KDE:Distro:Factory, please keep in > mind that this repo will be disabled for oS 13.1 as soon as the KDE 4.13 > packages are available through KDE:Current. In first instance we will just > disable the builds, however the packages itself will be deleted around 30 > April. So if you are currently running KDE:Current it would be wise to wait > just a little more than to switch repositories now. > > Regards > > Raymond Right on my Birthday ;-) Any bug reports should be submitted upstream first? -- Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] Availability of KDE 4.13
by Raymond Wooninck 17 Apr '14

17 Apr '14

Dear All, As you might have read on the KDE website or through blogposts, KDE 4.13 was officially released yesterday evening. As indicated KDE 4.13 is currently only available through KDE:Distro:Factory, however the target is to have KDE:Current delivering the KDE 4.13 packages around Friday 25th April. This would allow us to validate if there are any major breakages and to properly prepare the packages for a wider audience. For those that are considering to switch to KDE:Distro:Factory, please keep in mind that this repo will be disabled for oS 13.1 as soon as the KDE 4.13 packages are available through KDE:Current. In first instance we will just disable the builds, however the packages itself will be deleted around 30 April. So if you are currently running KDE:Current it would be wise to wait just a little more than to switch repositories now. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] New Problem with krunner
by Manu Gupta 16 Apr '14

16 Apr '14

Hey All I am trying to run krunner on plasma-next, however I get the following errors : "manugupt1@hawk:~> krunner "Unexpected reply signature: got "no signature", expected "i" (int)" " on the terminal However, when I try to launch it via root, it successfully runs. "Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... I/O warning : failed to load external entity "/usr/share/qalculate/prefixes.xml" I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml" I/O warning : failed to load external entity "/usr/share/qalculate/units.xml" I/O warning : failed to load external entity "/usr/share/qalculate/functions.xml" I/O warning : failed to load external entity "/usr/share/qalculate/datasets.xml" I/O warning : failed to load external entity "/usr/share/qalculate/variables.xml" I/O warning : failed to load external entity "/usr/share/qalculate/currencies.xml" I/O warning : failed to load external entity "/root/.qalculate/eurofxref-daily.xml" I/O warning : failed to load external entity "/root/.qalculate/eurofxref-daily.xml" QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6' hawk:~ # Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) " I am not sure what is the problem with this now. Is this known? -- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] An appropriate applet for Sound Control
by Manu Gupta 16 Apr '14

16 Apr '14

Hey All I was not able to find any widgets for sound, if there are any recommendations on KDE5, please let me know. -- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] Installing plasma-next on openSUSE KDE 13.1
by Manu Gupta 12 Apr '14

12 Apr '14

Hey All I am trying to install plasma-next-session with kde and get KDE5 running on 13.1. When I choose the plasma-next desktop option and login, I get the following error " Could not start D-Bus. Can you Call qdbus? Error please help " I found only Xorg logs, " HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200 [ 58.466] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 58.466] (II) FBDEV: driver for framebuffer: fbdev [ 58.466] (II) VESA: driver for VESA chipsets: vesa [ 58.466] (++) using VT number 7 [ 58.467] (EE) open /dev/dri/card0: No such file or directory [ 58.467] (WW) Falling back to old probe method for modesetting [ 58.467] (EE) open /dev/dri/card0: No such file or directory [ 58.467] (II) Loading sub module "fbdevhw" [ 58.467] (II) LoadModule: "fbdevhw" " However, the latest KDE SC works perfectly fine on my system. Any hints? -- Regards Manu Gupta -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 6

[opensuse-kde] KDE SC 4.13 availability for openSUSE
by Raymond Wooninck 11 Apr '14

11 Apr '14

Dear openSUSE KDE users, As you might know, KDE Upstream is planning to release the new 4.13 release around Wednesday 16 April. The openSUSE KDE Community team is planning to have the openSUSE KDE packages ready by that time, however the update will not become directly available for all users. As promised with the release of the KDE:Current repository, major updates will first be tested for a period of 1 to 2 weeks before they will become available in the KDE:Current repository. This is not to pester the users, but to ensure that nothing is forgotten, no sudden major bug, etc. When you are using the KDE:Current repository then upgrades should go smooth to ensure the best experience. As that the new 4.13 release already had quite some testing by openSUSE users brave enough to use the KDE:Distro:Factory, I am pretty sure that the KDE:Current repository will have the KDE SC 4.13 release available around Saturday 26 April. This would give us time enough to prepare the packages (and ensuring a smooth upgrade) as well to test the 4.13 release itself by a number of people for major regressions. I am sure that all of you are anxious to try out the new KDE SC 4.13 release, but I guess one week more wouldn't make that much difference if we can prevent. My assumptions are that those that couldn't wait already switched to KDE:Distro:Factory and are testing now the 4.13 RC. As that I am not subscribed to the openSUSE mailinglist, I would like to ask you to copy me directly on your replies. Thank you Regards Raymond openSUSE KDE Community team member -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] KDE in Tumbleweed just died a horrible death
by Greg KH 09 Apr '14

09 Apr '14

So, with the recent reorg of packages in the KDE repos, KDE in Tumbleweed is horribly confused. What should I do? Link everything I previously was in the 412 repo with something else? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

9 38

[opensuse-kde] LXDE-Qt
by Shawn W Dunn 08 Apr '14

08 Apr '14

Not specifically KDE, but it seems like this would be the best place to get some people bashing on and breaking things..... I've got git snapshots of LXDE-Qt packaged up in devel:cloverleaf:lxqt, built for 13.1 and Factory. Those of you that used, or gave Razor-Qt a testdrive in the past will pretty much recognize everything. As a default, it will pull in openbox for the default window manager, but I have confirmed that it works fine with KWin if that's your preference. I've also put together a pattern, lxde-qt that will install everything you need (except lightdm, and lxqt-lightdm-greeter, I've left those as recommends, instead of requires, as I didn't feel like changing display managers for my own stuff, and it gets along fine with kdm and sddm) Anyway, give it a look if you like, and kick it a bit, see if anything breaks. I've not done much more than get it installed in a vm, and confirm that it plays nice with kwin

2 4

[opensuse-kde] Is it safe to update KDE4 Current today?
by Roman Bysh 07 Apr '14

07 Apr '14

Hi, Is it safe to update from 4.12.4 "Current" to 4.12.4-1.2 today Monday, April 7 or wait till Thursday? I see that not all of the packages have been uploaded. And, Is there an OBS Current test repository? Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 4

Re: [opensuse-kde] Is it safe to update KDE4 Current today?
by Roman Bysh 07 Apr '14

07 Apr '14

On Mon 07 Apr 2014 03:46:39 PM EDT, Roman Bysh wrote: > On 04/07/2014 03:41 PM, Vojtěch Zeisek wrote: >> Dne Po 7. dubna 2014 15:34:21, Roman Bysh napsal(a): >>> Hi, >>> >>> Is it safe to update from 4.12.4 "Current" to 4.12.4-1.2 today >>> Monday, April 7 or wait till Thursday? >>> >>> I see that not all of the packages have been uploaded. >>> And, Is there an OBS Current test repository? >> >> I upgraded to KDE:Current from former repository for KDE 4.12 >> immediately >> after it was released and I have no issue with it. Works fine. >> >>> >>> Cheers! >>> >>> Roman >>> -------------------------------------------- >>> openSUSE -- Get it! Discover it! Share it! >>> -------------------------------------------- >>> http://linuxcounter.net/ #179293 >> >> Bye, >> Vojtěch >> Thank you. Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

Re: [opensuse-kde] Re: KDE in Tumbleweed just died a horrible death
by Greg KH 07 Apr '14

07 Apr '14

On Mon, Apr 07, 2014 at 09:11:01PM +0200, Raymond Wooninck wrote: > On Monday 07 April 2014 11:51:48 you wrote: > > > Odd, I wonder why I have that in the Tumbleweed repo, let me disable it > > and see if something else breaks... > > Hi Greg, > > I noticed that you disabled this package, but that alone will not do the > trick. Please either run from the console the following: > > osc wipebinaries -a openSUSE:Tumbleweed branding-openSUSE > > Or go to the package details in the webui and click on standard. Then you see > the binaries it has build. There you have to delete for both i586 and x86_64. > Without these binaries being deleted, the issue will remain Ah, nice, I never knew about that. But it fails: $ osc wipebinaries -a openSUSE:Tumbleweed branding-openSUSE Server returned an error: HTTP Error 404: Not Found wipe command failed for project branding-openSUSE arch openSUSE:Tumbleweed branding-openSUSE Hm, ah, --all is the correct option, that worked. Or at least it gave me an "ok". But nothing changed in the build gui screen :( And the files are still in the standard download repo. Do I just need to wait for the latest round of files to build? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] repository KDE 4.12 is empty
by Günther J. Niederwimmer 06 Apr '14

06 Apr '14

Hello, my zypper is crying for empty repository in KDE 13.1 will this fill up again with a new Version? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

9 26

[opensuse-kde] opensuse KDE live image with Kiwi - problem
by Martin Koller 06 Apr '14

06 Apr '14

Hi, hope that is the right list to ask. I want to create an openSuse KDE live iso image with kiwi but when doing the "kiwi --prepare" step using the example config.xml delivered with kiwi I get the following error: Problem: package-lists-openSUSE-KDE-cd-11.4-32.1.x86_64 requires branding-openSUSE, but this requirement cannot be provided uninstallable providers: branding-openSUSE-13.1-10.4.13.noarch[http:__download.opensuse.org_distribution_13.1_repo_oss] branding-openSUSE-13.1-10.4.13.noarch[mnt] Solution 1: Following actions will be done: deinstallation of branding-basedonopensuse-13.1-3.1.4.x86_64 deinstallation of systemd-presets-branding-basedonopensuse-13.1-3.1.4.x86_64 Solution 2: do not install package-lists-openSUSE-KDE-cd-11.4-32.1.x86_64 Solution 3: break package-lists-openSUSE-KDE-cd-11.4-32.1.x86_64 by ignoring some of its dependencies any hints ? -- Best regards/Schöne Grüße Martin A: Because it breaks the logical sequence of discussion Q: Why is top posting bad? () ascii ribbon campaign - against html e-mail /\ - against proprietary attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Re: [opensuse-factory] pulsaudio, broken after kernel update
by C. Brouerius van Nidek 05 Apr '14

05 Apr '14

On Friday, April 04, 2014 06:13:38 PM you wrote: > At Thu, 03 Apr 2014 15:34:31 +0700, > > C. Brouerius van Nidek wrote: > > After the last zypper dup in Tumbleweed which mainly got me the latest > > kernel (see signature) my sound has gone. > > Pulseaudio is there, uses a lot of my cpu (22 to 60%). > > On my KDE desktop I have standard running kmail, chromium and skype (which > > of course is also not working) > > > > Remembering from the past i played around with Yast, sound and alsaconf. > > alsactl kill and alsactl start did nothing. > > > > A reboot with the second last kernel ( 3.14.0-22.g79de0a7-default) gave me > > my sound back and pulseaudio without cpu use. > > > > Am I the only one with this problem? A bug report? > > I've got a report bnc#871957, but I wasn't sure about whether it's > really a kernel issue. > https://bugzilla.novell.com/show_bug.cgi?id=871957 > > So, please double-check that it's a kernel regression. Switch between > two kernels multiple times, and confirm that the problem is triggered > only with the new kernel, and the old kernel always works as expected. Switching the kernels multiple times I found that kernel 3.13.xxx always gave me sound. There was always sound when I came from a session with another kernel. At the second boot of the same 3.14 kernel sound was gone until I had a reboot with another kernel version. My question to you, does this phenomena also happen at your setup? Seems that the boot with another kernel version does leave something that helps to boot the system (with kernel 3.14) with sound at the next boot. > > Once when it's confirmed, join the bug report there. Describe the > working and broken kernel version numbers. Here, the git SHA ID > embedded in the version string is important. Also, describe about > your environment, especially attach the output of alsa-info.sh output > (run it with --no-upload option). If above reported behavior is much different from yours, does it still fit in the bug report? > > Looking at the kernel git commits since the commit 79de0a7, the only > significant change is about the update of XEN patches. If any, this > is the likely culprit. > > > thanks, > > Takashi -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 13.1 (i586) Kernel: 3.14.0-23.gfa168d7-default KDE Development Platform: 4.12.3 14:02pm up 1:12, 3 users, load average: 1.94, 1.21, 1.16 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Factory: nothing to grab, no pointer, cannot resize windows
by Felix Miata 02 Apr '14

02 Apr '14

Is this the case for everyone running 4.12.97 in Factory? -- "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/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] subscribe
by Eloy Cuadra 02 Apr '14

02 Apr '14

subscribe -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 3