April 2010 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] Call for testing: on-demand package installation
by Lubos Lunak 28 Jun '10

28 Jun '10

Hello, in OBS in home:llunak:ksuseinstall there are packages branched from KDE:KDE4:Factory:Desktop that have one experimental feature added: When a needed package is not installed, the user is offered its installation. Currently there is support for debuginfo packages, applications that can open a specific file type if none is installed and multimedia codecs for Amarok. The plan is that this feature makes it into 11.3, so please test and provide feedback. The things I'm especially interested in: - the UI and the workflow could quite possibly be improved (currently it uses Yast modules to save me a lot of work, and it's also done this way because of a certain catch mentioned below). So, imagine you are Joe User the Clueless who's just installed 11.3 and think about how this would or would not work and how it could be improved. The catch here is that this is not only a technical problem but also a legal :(. This can quite easily help with the problem of installing packages that cannot be shipped as a part of openSUSE because of various stupid patent stuff etc. The problem is that we should not even encourage too much usage of such packages. Don't ask what that means exactly, because I don't know, and probably not even lawyers know for sure, but something like "MP3 support is missing, press Yes to install it from Packman" is simply very unlikely to make it past our lawyers. I think the guideline could be that the user has to know it's an extra and that it's not part of openSUSE, and thus has to make at least some effort, not just confirm a dialog. There is a reason why adding community repositories in Yast fetches a list of those from a 3rd party site and knows nothing else than the URL of that list. Yes, this all sucks. - there could be more places where this could help a lot, either by saving the default installation size by not installing packages that most users wouldn't use, or by handling something where such on-demand installation would be helpful to many users. From 11.2 the Nepomuk/Strigi config module comes to mind - we had it disabled by default and some parts were not installed, so enabling it required not only flipping the checkbox but also installing something. I am not going to patch every single place in KDE where an optional package could be possibly missing, but it shouldn't be difficult to handle some mores places where it makes a difference, if you know such cases. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak(a)suse.cz , l.lunak(a)kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

8 22

[opensuse-kde] KDE repo structure proposal
by Lubos Lunak 28 May '10

28 May '10

Hello, I have the AI from the last meeting to sum up the new structure and naming here before we do a poll about the choices, so here it goes. According to the discussion the repositories should be reorganized this way, with the following names and purpose: (note: KKFD = KDE:KDE4:Factory:Desktop, o:F = openSUSE:Factory) - backports repository - name KDE:Backports, it contains latest versions of KDE applications that are usable of any supported openSUSE release and do not require newer KDE platform. In other words, all applications from the factory development repo (current KKFD) but built against the distributions instead of against KKFD. This repository is offered in repositories list in YaST. Technically, this repo will only contain links to openSUSE:Factory for the packages. Maintainers of the repository shouldn't need to do more than enable/disable build and 'osc linkrev' to update to newer versions (the links will point to specific revisions of o:F packages to avoid beta packages appearing in KDE:Backports when they get submitted to o:F). - unstable repository - name KDE:UNSTABLE, currently KDE:KDE4:UNSTABLE:Desktop. Basically, SVN upstream snapshots, that's it. - development repository - current KDE:KDE4:Factory:Desktop, suggested name KDE:Distribution:Factory or others (see below). This repository contains all packages maintained by the KDE team that are in o:F. Note that KDE team does not mean just Will and me. - stable repository - current KDE:KDE4:STABLE:Desktop, suggested name KDE:Distribution:STABLE or others (see below). Contains all packages maintained by the KDE team that are in the latest stable openSUSE release. In other words, when there is a new distribution release, contents of the above (~KKFD) repo get copied here and the repo is used for preparing online updates and similar. - additional packages repository - suggested name KDE:Extra or others (see below), for packages which are not in o:F (like current KDE:KDE4:Community but hopefully without the random state of things). This repository is offered in repositories list in YaST. Only stable releases of packages are allowed here, or a reasonably stable beta release if an official stable release is not available. Repository-wide maintaners are only people who maintain the repository as a whole. People willing to contribute packages will do submit requests that will be reviewed by maintainers, when trusted enough they get maintainership only for their package(s). Current KDE:KDE4:Community will be eventually deleted after packages are moved to this new repository (not necessarily all of them). - playground repository - name KDE:Playground, contains any KDE packages without any guarantee (alpha versions, whatever). Not as strongly reviewed and maintained as the other repositories (I don't know what the best way to handle this in practice would be, depends also on manpower, but I think there still should be only few repo-wide maintainers who would give package maintainership to others). That's all as far as the reorganization goes. This will be done before 11.3 is released, we will try to keep links for backwards compatibility for some (unknown time). Please review and comment/fix/etc. Also please raise your hand again if you'd be willing to do a repository maintainer for any of these. There were several people for KDE:Backports (where it should be pretty simple) and KDE:Extra stepping up during the meeting, so I'd like just to have a written overview here. Naming: Since we are already going to do repository renaming to e.g. remove 'Community' from the name of the repository with additional packages to avoid suggesting that it is the only repository where community can contribute, we decided to do it all at once and also do other renaming to fix other problems with repository naming. For example, in KDE:KDE4:Factory:Desktop the 'KDE4' is superfluous and 'Desktop' is just a part of the contents, and we could use a better word than 'Factory' to suggest that it is packages that will be in the distribution. Therefore, here is a list of names that were proposed during the meeting. For some the consensus seemed clear, so there is just one, but feel free to suggest other options there too. - backports: - KDE:Backports - unstable: - KDE:UNSTABLE - KDE:Unstable - development: - KDE:Distribution:Factory - KDE:Distro:Factory - KDE:Base:Factory - (KDE:SC:Factory is not listed as the contents are not just KDE Software Compilation) - ? - stable: - KDE:Distribution:STABLE - replace 'Distribution' with all choices above for it, and STABLE can again get different capitalization - ? - additional: - KDE:Extra - KDE:Contrib (this is not very liked, as it has similar implications like 'Community') - playground: - KDE:Playground After feedback (or if there is none :) ), I will create polls for the possibilities and best names will be chosen. After that, we will create the new structure, setup maintainers for the repos and start moving contents. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak(a)suse.cz , l.lunak(a)kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

9 30

[opensuse-kde] No Sound after Installing KDE 4 Live
by Andi Sugandi 22 May '10

22 May '10

Hi Listmates, I successfully installed KDE 4 Live (x86-64) [0] on ASUS EEEPC 1201T[1], but no sound on login (and other applications). Running: > speaker-test -Dplug:front -c2 -l5 -twav speaker-test 1.0.21 Playback device is plug:front Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Playback open error: -16,Device or resource busy Playback open error: -16,Device or resource busy Playback open error: -16,Device or resource busy But fine when testing through: YaST / Hardware / Sound , Other / Play Test Sound . It took me to read the troubleshooting page[2] , they said it is probably because the user was not in audio group yet. I added my user to be in, then it solved the issue. Is it known (bug) of (only) KDE 4 Live issue or because running x86-64 version? I never found this issue on other openSUSE 11.2 installation (no need to be in audio group). Thanks in advance. [0] http://download.opensuse.org/repositories/KDE:/Medias/images/iso/ [1] 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) [2] http://en.opensuse.org/SDB:AudioTroubleshooting#STEP-8:__KDE4_Phonon_Audio_… Best regards, -- Andi Sugandi (Bandung) openSUSE Ambassador http://en.opensuse.org/User:Andisugandi -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 2

[opensuse-kde] KKFD NetworkManager-kde4 broken on 11.2
by Tejas Guruswamy 18 May '10

18 May '10

Hi guys, As I started my machine after the latest zypper up, I found the following recent commit has broken NetworkManager for KDE:KDE4:Factory 11.2 users for obvious reasons (we got the updated NetworkManager-kde4 from KKFD, but not NetworkManager, so no dbus conf) +Fri Apr 23 10:20:23 UTC 2010 - bili(a)novell.com + +- Add a general frontend dbus configuration in NetworkManager + so delete the conf in knetworkmanager, bili(a)novell.com(bnc#476502). Since a lot of people use 11.2 + KKFD I thought it would be best to publicise the workaround as soon as I experienced this. Put the new dbus conf from factory NetworkManager [ http://pastebin.com/5X7x9JHY ] in /etc/dbus-1/system.d as NetworkManager-frontend.conf also available on build.oo from the Factory NetworkManager package I know that backwards compatibility shouldn't hold back development, but it would be nice if this change was made in a way that didn't kill 11.2 users. Solutions might be an ugly specfile hack or to somehow provide new NetworkManager to 11.2 users. I know its in GNOME:Factory, but I'd rather not add that massive repo if I didn't have to. Is it sensible to have KKFD aggregating factory NetworkManager as a sort of backport for 11.2 users? Anyway there will probably be quite a few surprised users, knetworkmanager pops up a really scary dialog on reboot after this change, saying sth like "Knetworkmanager cannot provide user settings ... Knetworkmanager will not start on startup ever again", so here's your heads up. Regards, Tejas -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

3 2

[opensuse-kde] Bug Triaging Guide
by Will Stephenson 30 Apr '10

30 Apr '10

Dario Andres. upstream bug triager par excellence, has written this comprehensive guide to effective bug triaging: http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

1 0

[opensuse-kde] KDE:KDE4:Factory:Desktop disabled from publishing
by Dirk Müller 30 Apr '10

30 Apr '10

Hi, KDE:KDE4:Factory:Desktop and related projects have been disabled from publishing due to preparation of KDE 4.4.3 update . Greetings, Dirk -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

1 0

[opensuse-kde] openSUSE KDE meeting 20100429
by Lubos Lunak 29 Apr '10

29 Apr '10

See http://en.opensuse.org/KDE/Meetings/ for futher details. == Old action items == * wstephenson add generic repeating meeting event ** not done (?) * llunak summing repo structure up, asking for comments and then posting it somewhere and doing a poll ** work in progress, polls will be set up soon * wstephenson ask adrian about transitional measures for repo renaming ** there will be symlinks added to map old structure to the new structure * lunak,wstephenson document how-to-maintain Extra ** not done == Action items == * wstephenson add generic repeating meeting event * lunak,wstephenson document how-to-maintain Extra -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 1

[opensuse-kde] kio_sysinfo crashes in openSUSE 11.3 M6 Build 577 x86_64
by Roman Bysh 29 Apr '10

29 Apr '10

After getting kio_sysinfo fixed April 23, 2010 and working in openSUSE 11.2 KDE 4.4.2. Now kio_sysinfo crashes in build 577 openSUSE 11.3 M6 x86_64. A bug report has been reopened today. Cheers! Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 3

[opensuse-kde] Fwd: New dependency for kdelibs and kdebase: dbusmenu-qt
by todd rme 29 Apr '10

29 Apr '10

Hi, you are probably already aware of this but I thought it would be worthwhile to bring it to your attention. There is a new dependency for KDE starting with KDE 4.5, for dbusmenu-qt. Below is the announcement from the KDE mailing list, which includes more information. -Todd ---------- Forwarded message ---------- From: Aurélien Gâteau <aurelien.gateau(a)canonical.com> Date: 2010/4/25 Subject: New dependency for kdelibs and kdebase: dbusmenu-qt To: kde-core-devel(a)kde.org Hi, I just committed support for DBusMenu in kdelibs and kdebase. - In kdelibs, DBusMenu is used by KStatusNotifierItem to export their menus over DBus. - In kdebase, DBusMenu is used by the Plasma SystemTray applet to render the KStatusNotifierItem menus. The advantage of this new system is that the visualisation gets more control over the rendering of its items, compared to the previous implementation which asked the application to show their menu at a give position. It is also nice for users of libappindicator-enabled [1] GNOME applications, because the SystemTray menus of these applications will be rendered using a native KDE menu. This means to build kdelibs and kdebase you now need to install dbusmenu-qt. dbusmenu-qt tarballs are available here: http://people.canonical.com/~agateau/dbusmenu/ You can also get the code from Gitorious: http://gitorious.org/dbusmenu/ I am on holidays next week, but will check my mail from time to time in case there is any problem with this new dependency. I committed it now because dependency-freeze is tomorrow. Aurélien [1]: libappindicator is a GTK+ implementation of the StatusNotifieItem protocol -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 1

[opensuse-kde] Kdevelop4 & plugins
by Daniele 29 Apr '10

29 Apr '10

Hi all, I'd like to try kdevelop4 with php plugin but: Problem: nothing provides kdevelop4 = 3.10.0 needed by kdevelop4- plugins-php-3.10.0svn1112681-3.2.i586 This since weeks, with both kde-4.3.* and kde-4.4.2 on 11.2 So what about kdevelop4 plugins and factory ? Bye. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 1