May 2015 - openSUSE KDE - openSUSE Mailing Lists

[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