May 2015 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] unsubscribe
by Stefan Kunze 28 May '15

28 May '15

unsubscribe

1 0

[opensuse-kde] unsubscribe
by Stefan Kunze 28 May '15

28 May '15

unsubscribe

2 1

[opensuse-kde] Plasma 5.3 update for openSUSE 13.2
by Todd Rme 27 May '15

27 May '15

Just a clarification: is a plasma 5.3 update through the normal update channels planned for openSUSE 13.2? This isn't a request, I fully understand if it isn't planned. I am just trying to find out whether I should be waiting for it or should go ahead and enable the KDE:Frameworks5 repo. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

5 7

[opensuse-kde] needless dep: *KF5NetworkManagerQt* ???
by Felix Miata 21 May '15

21 May '15

# rpm -qa | grep ager yast2-services-manager-3.1.39-2.1.noarch yast2-packager-3.1.66-1.1.x86_64 # zypper ll | grep ager 57 | *ModemManager* | package | (any) 58 | *NetworkManager* | package | (any) # zypper dup Warning: ... Computing distribution upgrade... 2 Problems: Problem: plasma5-workspace-5.3.0-1.1.x86_64 requires libKF5NetworkManagerQt.so.6()(64bit), but this requirement cannot be provided Problem: plasma5-session-5.3.0-1.1.noarch requires plasma-nm5 >= 5.3.0, but this requirement cannot be provided Problem: plasma5-workspace-5.3.0-1.1.x86_64 requires libKF5NetworkManagerQt.so.6()(64bit), but this requirement cannot be provided uninstallable providers: libKF5NetworkManagerQt6-5.10.0-1.1.x86_64[OSS] libKF5NetworkManagerQt6-5.10.0-1.1.x86_64[openSUSE-20150425-0] Solution 1: Following actions will be done: install plasma5-workspace-5.3.0-1.1.i586 despite the inferior architecture install cln-1.3.4-1.2.i586 despite the inferior architecture install libqalculate5-0.9.7-18.2.i586 despite the inferior architecture install libavutil54-2.6.2-1.1.i586 despite the inferior architecture install libavcodec56-2.6.2-1.1.i586 despite the inferior architecture Solution 2: keep obsolete plasma5-workspace-5.2.2-3.1.x86_64 Solution 3: remove lock to allow installation of libKF5NetworkManagerQt6-5.10.0-1.1.x86_64[openSUSE-20150425-0] Solution 4: remove lock to allow installation of libKF5NetworkManagerQt6-5.10.0-1.1.x86_64[OSS] Solution 5: break plasma5-workspace-5.3.0-1.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/4/5/s/r/c] (c): c TW has Wicked as default nw "manager". Many people need no network management at all. Others like keeping installations lean, which as a bonus conserves bandwidth at update times. Why are these K5 NM packages unlikely ever to be of use hard dependencies? -- "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

5 7

[opensuse-kde] kmail indexing problem - regression - again??
by stakanov＠freenet.de 20 May '15

20 May '15

Hello, before I am going to post the kmail bug number....xxxx million I want to have a feedback on what could happen here. All what I am going to say is POP3 (as I am not even considering trying IMAP for security but also for functionality reasons...simply does never work as it should, which would be another issue but these days I consider "IMAP" dead anyway). So let us see: Open a local folder for one of your contacts. Define a filter for this contact define a preferred folder for this contact. receive a pgp encrypted mail (in the case RSA/RSA 4096) What the new mail will do, but not regularly, just "now and then" but once it happens it is unfortunately stable: if you have the preview window you will be able to decrypt the mail, and to read it...in the preview window. When you try to open the very same mail you will get the eternal "retriving the resource" and it will never open. That means AFAIK and AFAIU that the index is broken ...AGAIN? I had to reinstall kmail this year about 4 times (and here even shift to a news user because of impossibility of opening Kontact. Now AGAIN that index thing begins Up to yesterday I have a working backup archive that I have to perform EVERY DAY because of the hilarious vulnerability of these indexes. However now the archive adverts me of broken index and stops to work, so that is how I discover it all the time when another time another index is broken. This also means, if one of the subfolders in local has an index problem, either you have to define a hundred of archive procedures or you are stuck as "local" interrupts when it hits the borked index of that folder. Question: Time ago there was a function "rebuild indexes", you would loose some mail but then the problem was done. Unfortunately that is not the case any more. Is there a way to erase the index hit by this bug, where can I find it? Is there a way to achieve this on the CLI or by hand? Is there a way to debug this? I am happy to help. Otherwise is there a way to migrate to another email program that does not uses "indexes" for whatever relational database without loosing my data and mail?? (I know that everybody is migrating to thunderbird but that program seems to be on a dead end. What format is the most easy solution to migrate and is it possible to migrate pgp encrypted mail anyway? Is it possible to migrate back to kmail3? At least locally and with POP that worked well, up to excellent and I think the rpms are still available. Sorry for asking that, but with this regression with the indexes we are returning to the reliability of kmail that it had with 4.0. Another question that does not want to be polemic but I think would deserve an answer: This is a very, very, very basic install on a laptop, about 6 POP accounts and not a "incredible" amount of mail. It has not power-blackouts (as it is a laptop), it has had no crashes of the OS, it is a recent install from the scratch. Still it brakes like nothing. The question is: what are you wanting to achieve with kmail as developers? A enterprise solution (IMO cannot be, it fails already on a laptop). An end-user solution - cannot be, because it is not reliably saving the emails. Seriously, I know that I am irritated to the blood, thus I would rather like to understand the deeper meaning of this, so at least I can put my anger in a locker. Thank you and sorry for the despair. A short time it seamed that KDE4 was stable, but is seams for kmail that is still not true. --- 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] crashing - > missing dep?
by Felix Miata 19 May '15

19 May '15

Since today's zypper dup, https://bugs.kde.org/show_bug.cgi?id=347006 looks like what was happening on the first system installation I ever made to include K5. It wouldn't let me switch in alternatives from default to Kicker (Application Menu) style, always crashing after clicking on "switch". In trying to investigate, I found all of kactivities* not installed. Installing kactivities5 solved the inability to make the switch. Shouldn't kactivities5 be a dependency of plasma5-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/ -- 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] ffmpeg in KDE:Extra
by Cor Blom 14 May '15

14 May '15

Hi, Can one of the maintainers of KDE:Extra replace libffmpeg-devel by a link to multimedia:libs:ffmpeg (at least for 13.2 and 13.1)? Then it is again in sync with packman. (I would do a SR for this, but is this of thing possible to do in a submitrequest?) Thanks, Cor -- 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] Duplicate Places Entries in Dolphin
by Sam M. 14 May '15

14 May '15

Hi, Multiple updates came in yesterday for Plasma5, and now I have duplicate places entries in Dolphin. I can delete them, but they come right back after logging out and back in. I'm on 13.2 x64 with the following repos added: http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.2/ http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_13.2/ http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.2/ "Home, Network, Root, and Trash" all show up twice. Thanks. -- 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] Re: [packman] kdenlive crashes
by Olaf Hering 13 May '15

13 May '15

On Wed, May 13, jdd wrote: > openSUSE 13.2. Kdenlive 15.04.1-6.1-w86_64 from packman By accident I linked the package to the devel project of openSUSE:Factory. But this version is broken, it supports nothing but Factory. So I linked it back to the original OBS prj. Since that package needs an update the build did not start yet. Too bad, during the short period of time where the _link pointed to the wrong OBS prj the pkg was built and published. Sory for that. Olaf -- 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] Plasma Failure
by ianseeks 12 May '15

12 May '15

Hi At least once a week my log into a desktop fails with a Plasma error unable to talk to Klaunch(er?). It gives me a desktop but i cannot launch anything, not even a logout. I have to resort for Ctrl Alt Backspace to exit. I'm not sure where to look for a this error to see what the problem is but i did get these 3 lines from the journal - does anyone know what the issue could be? I can log back in okay and then it works fine May 12 13:58:04 Bigmachine kdm[5773]: :0[5773]: pam_unix(xdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=zips May 12 13:58:04 Bigmachine unknown[5773]: <audit-1100> pid=5773 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="zips" exe="/usr/bin/kdm" hostname=? addr=? terminal=:0 res=failed' May 12 13:58:04 Bigmachine kernel: audit: type=1100 audit(1431435484.406:1872): pid=5773 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="zips" exe="/usr/bin/kdm" hostname=? addr=? terminal=:0 res=failed' regards Ian -- 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] Critical Qt Bug
by Klaas Freitag 05 May '15

05 May '15

Hi, I just filed https://bugzilla.opensuse.org/show_bug.cgi?id=929688 about a critical Qt bug. I understand that this hopefully results in a maintenance update of Qt on the supported platforms, which would be great. However, I wonder what about the Qt's in other repositories such as KDE:* or KDE:Qt* and friends. Do they have to be updated separately or are they derived from the "main" ones? I am happy to help with sumbit requests if somebody tells me which ones need an update. Thanks, Klaas -- 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] Overview of current Staging I wrt Plasma 5 transition
by Max Lin 04 May '15

04 May '15

Hi All, Many of you may already know I'm working on a pre-integration work relate to Plasma 5 in Staging Project - Switch Plasma 5 to default KDE desktop. The goal is make sure we can smoothly move to Plasma 5 as default KDE desktop before those changes get into Factory(Tumbleweed). This mail is a short report, give you a quick overview of the current status, and understand where we are now. All works is in Staging I[1] currently, so it would not effect the rest of stagings or even Factory. Thanks openSUSE KDE Team, the packages are almost ready, and few issues also got fixed when we observed it in openQA, now, what things already done(or almost done)? * PLasma 5 packages and its deps are ready[1] * update patterns[2] * skelcd-control update been submitted, waiting for merge[3] * a fresh installation can pass openQA test[4] - all green now! Everything looks quite well. But during adjusting openQA tests, I discover we still have some more work need to do to get this transition pass Staging Project, * Update test can not pass openQA: it tested update from a Tumbleweed snapshot to current Staging I, according to the result[5], it seems still need some more work, 1) kdm still there! and since DISPLAYMANAGER param doesn't change, system is launch kdm indeed. 2) per above, if user enabled autologin, kdm may bring user to whatever desktop session after update, because kdebase4-session got removed already, and if more than one desktop session(eg. icewm) installed there, it may boot into wrong session than what you expect - plasma5 session. So I think we need a better way to handle update. * Improve sddm: sddm may better to handle with AUTOLOGIN, the installer provides a autologin option there, but it will not work with sddm. This is the current status of Staging I. If you checked Staging I and think I'm missing something there, please let me know! And any feedback welcome :) Note: I'll random rebase Staging I, ie. re-build Staging I with the latest souce from Factory at some point, make sure Staging I not so far from current Tumbleweed snapshot. Best regards, Max [1] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:I [2] https://build.opensuse.org/request/show/304878 [3] https://github.com/yast/skelcd-control-openSUSE/pull/31 [4] https://openqa.opensuse.org/tests/60112 [5] https://openqa.opensuse.org/tests/60110 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 5

Re: [opensuse-kde] Strange error on Kontact
by stakanov＠freenet.de 03 May '15

03 May '15

p, li { white-space: pre-wrap; }In data domenica 3 maggio 2015 12:36:21, Luca Beltrame ha scritto: > > This bug happens always when I use Kontact with some more functions like a > > task (todo, within a date) and I complete it..... Or when I set up a diary > > Do you mean you see this error when you try to use korganizer inside > Kontact in todo mode? That may be the clue to see why it's broken. This is correct, it happens exactly when I try to use Korganizer with todo mode. You create a task. No problem. The problem arrives when you complete it. I think it happens when you decide to eliminate the task once completed --- 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

1 0

[opensuse-kde] Strange error on Kontact
by stakanov＠freenet.de 03 May '15

03 May '15

I would like to seek some opinion of anybody more knowledgeable to KDE than I am. I am getting an abort on start of Kontact. This is not the first time. The last time I fiddled around with the present files, but this time I simply do not find a work around. The bug has been reported to kde some time ago but I assume that all development goes now to KDE5 so I will have to go on my own. Bug number was: https://bugs.kde.org/show_bug.cgi?id=340867 Now here we go again, I try to start Kontact and when from terminal I get: kontact Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) json_parser - syntax error found, forcing abort, Line 1 Column 0 kontact(3093)/kdeui (kdelibs): No such XML file "/home/hermes/.kde4/share/apps/kontact/default-.rc" But there was never a "default-.rc" to begin with. Nor has there been ever in any other of my installations on other PCs. There are however all normal rcs.... present when this happens. So I tried if renaming the kontact folder with the rc files and starting over would have helped. A new folder kontact is created, with the default kmail.rc inside but: abort with the very same error message. If I create a fake default.-rc then of course he complains about error in line one position one because that file is empty. But I do not get what he expects and I do not understand where the reference to default-.rc may be made to get rid of it. This bug happens always when I use Kontact with some more functions like a task (todo, within a date) and I complete it..... Or when I set up a diary ...same thing happens. All single programs work fine, I can start kmail, all filter work i can start notes, organizer, everything. But when trying kontact ..bumm. I am grateful for any hint especially to explain me where I could search for some value set wrongly. I searched all kontact references within the / that I was able to get hold of but not reference to that value "default-.rc" 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] Plasma 5: Configuring Window Shadows
by Uzair Shamim 02 May '15

02 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I just wrote this for two things, first of all great work on Plasma 5, I just switched over to it last night and have really enjoyed it so far! Second, I was wondering if it was possible to change the window shadows in Plasma 5? Back in KDE 4 there was an option in System Settings that let you mess with a bunch of glow and shadow settings (eg. make the shadow darker, lighter, or "bigger"). Apologies if this was discussed before but my search showed nothing on the topic. PS. sent another mail earlier, wasnt subscribed to the mailing list and forgot it was mandatory now. Ignore it when it gets through, sorry! - -- Regards, Uzair Shamim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVQEoZAAoJEM66EOTZRH6+jRYQAI2CNRUm+uKbvYd0+K0WlAu8 V88CTS5d8vZDf/Yi/BkbGmhu3fik6yX0YajW96onq1kiemyz92pxGV8cxna2Z43S LfHaumsih0pt42oljwlMv7tkyes8Hx4jtqqOqUFaQy1QvC5ITkKWjDw3HCdcl/IT moHKbpQfMkVxBy3T9vM3feKMorB2Q6N7+P4r/aKRJ06RZCBwICXNGyWWVgAajx6m nloKDR+KWkHzPezc9MxiRL0m+rsOSWW32VzCh1lLYN6BLMDcILPyojfWPU+jrNu0 hAlxjF2+SAxsNBk+xfudUaM9USkHuRM0+SXgQkfHoVjsiI8mZX61CXe6gHl6Z2c3 3JY9Xp74+sN9qa+B0h5vXRPAq7jxYjpKtHY9L1ifMa2ysZp2nBYFyTe6lqsNUpDc OqYEESWeblDUVylQyFc3guGasFMvIK/XoeiVE2dI51RiC7Rp2nMOXiJ8bjxkVlp+ je+5x+Ibk7wv+0R3G3WDSfCkiAH8tavheIz8ZKR4eJ/5f+HT0d4Z2Vu+bHWGxpDD lCgg8H2faKtxOzQvmGQwIc4Mt+s8WtrhbiUlyM9De0DySKk4d+nkx/qM7W274XGW HyBLdz2iHVzWPy+7c+pyX4WZ/2HUFv9e7iwjHdwSrhCrSa/DsoBCqBW1ehsqLCu+ N2LGrNPEUr6mAwlaXFAo =9Cvi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 10

[opensuse-kde] sddm logout error on 13.2
by Cor Blom 01 May '15

01 May '15

Hi, After updating to KDE:Frameworks on 13.2 with sddm as displaymanager, logout did not return to sddm, but stayed black with cursor. After googling I found this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1407152 Update to gnome-keyring seems to solve this, but that is not an option on 13.2. I removed the gnome-keyring-pam package and now logout is working again as it should. I don't know if there will be negative side-effects to this removal (I am not aware I am using gnome-keyring), but maybe this helps someone. I had trouble finding a solution. Regards, Cor -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0