November 2011 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] KDE bug crashing plasma when adding system tray is fixed in upstream.
by Andre Massing 24 Nov '11

24 Nov '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! The subject says it all :) I filed a bug at https://bugzilla.novell.com/show_bug.cgi?id=732454 with more detailed information, including a link to the KDE bug, hoping that the patch might result in an updated package in openSUSE 12.1 :) Cheers, Andre -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOzXEUAAoJEA79ggnbq9dmYNQIAL45TV86EBqpRb9jEf+i9VHu EbDj/vIYtTwSlzaln5+YgP1ElXTY6nkXiTFc+IrPnQOnDgRlPEyGRiPY5SeYmR3L XT1Lvhd5pNrl7Ny9x0kimm6REceH9ECtlUV+H/34b8wBL97NTqJC+/8yEKaLqEv7 TKFIFjfVjp8mafWv54K5oiyhDoZ6V3VTYVJXLPXEwBIm1saoVwPXD+q2SVYzitep p92MAywsElORjorWCWVU9PeUSA8yAk1LQduDJkixkXCcsEpP+exQwkl9wgNO0nXs JMzrJjzc5fbhrwcS00u5MJCbGLiMWwfpFHxhz5OTjKlO5a7xXxRAORhGjarzKho= =DDhb -----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

2 3

[opensuse-kde] Fwd: Check out our Guide for new KDE developers
by Javier Llorente 23 Nov '11

23 Nov '11

---------- Mensaje Reenviado ---------- Asunto: Check out our Guide for new KDE developers Fecha: Sábado, 19 de noviembre de 2011, 00:19:39 De: Valorie Zimmerman <valorie.zimmerman(a)gmail.com> %ODIRECCIÓNDIREC -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, last month a team of three young developers and one non-devel were sponsored by Google to Google's first documentation sprint, along with 3 other teams: OpenMRS, OpenStreetMaps, and Sahana Eden. Each team wrote a book that week which was published on the Flossmanuals.org site, and each of use got a copy of the book we had written, which was just amazing! Printed copies are available for purchase from Lulu.com [0]. The beauty of the process is that the text, layout, artwork and other aspects of the book can be edited and updated, then published whenever we like. In our case, we wrote a short manual for new KDE developers to get all set up to create patches, dive into application development, or even start work on our KDE base framework. While we think what we produced is pretty good, we know that it can be improved, and maybe even needs some corrections. We’ve assigned the e.V. ownership of the book, and they will set the pricing for printed copies. It is available as an ePub as well as PDF, and is readable on the web at [1]. It was quite a thrill to see our book on my Kindle! If you are interested, please read through it, and if you want to edit, create an account at flossmanuals and edit the book here [2]. To get in touch with people already involved in editing and publishing process of the book , you may send an email to <kde-book-creation(a)googlegroups.com> or find us on irc-freenode channel #kde-doc-sprint. All the best, Valorie, Karan, Supreet, and Rohan [0] http://www.lulu.com/product/paperback/kde- guide/18173477?productTrackingContext=search_results/search_shelf/center/1 [1] http://en.flossmanuals.net/kde-guide/ [2] http://booki.flossmanuals.net/kde-guide/_edit/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJOx2aIAAoJEOmkidVOeO2BeboIAJJ5y0gwx9OuGEDyoJ8A248V sqBA499MM7p81FDI0pDKXOST8gfwQyALUmwzBZq7bSD+HfTDSwFf45bfztk5NUZd /5AhCyCdKNfyzE1QyYgcNoTrvEtW9uKQVeflZ83YNTim0mEPPRMt1pClKQkTIG9L Htkq8L/lQID3LWOJ8YZdasFTqJ7N7bi76wqhFQ3xW4pGc68ulMdgFcMEToTWkdV6 yzumTm44+OSVnWiarpFtQGV9mEhrmOdGyYGERX0sQGvTi6+ZtSOBdU20O1v59nxs 9jMS4FdmmIul8ZJ9yrFAxFObIlt1v68N4v6YO4lnZAB5TmPKvCsNS+/7rv0wq+8= =Fiy+ -----END PGP SIGNATURE----- >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << -------------------------------------------------------

2 3

Re: [opensuse-kde] Zypper not pulling in KDE package... looks like wrong behavior.
by Cristian Morales Vega 23 Nov '11

23 Nov '11

On 23 November 2011 10:16, Roger Luedecke <roger.luedecke(a)gmail.com> wrote: > On Wednesday, November 23, 2011 09:34:51 AM you wrote: >> On 23 November 2011 08:04, Roger Luedecke <roger.luedecke(a)gmail.com> wrote: >> > sudo zypper in chromium >> > root's password: >> > Loading repository data... >> > Reading installed packages... >> > Resolving package dependencies... >> > >> > The following NEW packages are going to be installed: >> > chromium chromium-desktop-gnome chromium-suid-helper libv8-3 >> > >> > The following recommended package was automatically selected: >> > chromium-desktop-gnome >> > >> > The following package is recommended, but will not be installed: >> > chromium-desktop-kde >> > >> > 4 new packages to install. >> > Overall download size: 24.2 MiB. After the operation, additional 86.9 >> > MiB will be used. >> > Continue? [y/n/?] (y): y >> > >> > >> > So, yeah. It pulled in the Gnome helpythingy but not the KDE, despite it >> > being installed and that KDE is the active desktop. Seems strange. Not >> > sure if its a bug though. >> >> %package desktop-kde >> >> Summary: Update to chromium to use KDE's kwallet to store passwords >> Group: Productivity/Networking/Web/Browsers >> Supplements: packageand(chromium:kdebase4-session) >> Conflicts: chromium-desktop-gnome >> Provides: Chromium-password = %{version} >> Requires: chromium = %{version} >> >> %description desktop-kde >> By using the openSUSE update-alternatives the password store for >> Chromium is changed to utilize >> KDE's kwallet. Please be aware that by this change the old password >> are no longer accessible and >> are also not converted to kwallet. >> >> %package desktop-gnome >> >> Summary: Update to chromium to use Gnome keyring to store passwords >> Group: Productivity/Networking/Web/Browsers >> Supplements: packageand(chromium:gnome-session) >> Conflicts: chromium-desktop-kde >> Provides: Chromium-password = %{version} >> Requires: chromium = %{version} >> >> >> ---- >> >> So do you had gnome-session and/or kdebase4-session installed? > I have KDE and GNOME installed. This new GNome is worse than the preview in Then the behaviour is the expected one. There are two option, any of them is valid and ZYpp selects one randomly. ZYpp doesn't have any infrastructure to select one package or the other depending on the running environment. Feel free to ask for it to ZYpp devs if you really think it makes sense, but IMHO doesn't, at least for this case. ps: the real fix would be to create another freedesktop standard so the password stores of KDE and Gnome are compatible... I would not hold my breath. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 7

[opensuse-kde] Weekly News Issue 203 is coming soon...
by Sascha Manns 23 Nov '11

23 Nov '11

Hello Mates, don't worry about this mail. I just would like to remind that our next openSUSE Weekly News 203 comes out at Saturday evening (UTC +2). Until Saturday 08:00:00 (CEST) +0200 UTC you can propose Articles, Links and all such stuff for integrating into the Weekly News. For people who don't want to write it in XML, you can use our Pad: https://osweeklynews.publishwith.me/1. I've planned to send this Mail each Wednesday to remind on the Weekly News. Have a lot of fun -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de This mail is written with Balsam Professional 12.1

1 0

[opensuse-kde] kde and console screens
by Edward F. Howson 23 Nov '11

23 Nov '11

Hi All I have recently upgraded to opensuse 12.1 and am using kde 4.7.2. In previous version I could keypress crtl+alt+F1 or any of the function keys to get various console screens. This was helpful if I wanted to take a quick glance at the system messages or if there was a problem with the desktop I could use the keypress combination to switch to a console, investigate and resolve. Has this been removed by design and is there a way to get back to the former functionality? Perhaps it is just my system, I notice that despite the fact that F2 is listed as a short cut to renaming a file, when I press F2 nothing happens. My apologies if this has already been discussed. I've just joined this list today. Thanks Eddie -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

7 12

[opensuse-kde] Zypper not pulling in KDE package... looks like wrong behavior.
by Roger Luedecke 23 Nov '11

23 Nov '11

sudo zypper in chromium root's password: Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: chromium chromium-desktop-gnome chromium-suid-helper libv8-3 The following recommended package was automatically selected: chromium-desktop-gnome The following package is recommended, but will not be installed: chromium-desktop-kde 4 new packages to install. Overall download size: 24.2 MiB. After the operation, additional 86.9 MiB will be used. Continue? [y/n/?] (y): y So, yeah. It pulled in the Gnome helpythingy but not the KDE, despite it being installed and that KDE is the active desktop. Seems strange. Not sure if its a bug though. -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- 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] Re: How do root applications get their theme data?
by dh 23 Nov '11

23 Nov '11

On Tuesday, November 22, 2011, Roger Luedecke wrote: > On Tuesday, November 22, 2011 12:12:50 PM dh wrote: > > On Tuesday, November 22, 2011, Roger Luedecke wrote: > > > On Tuesday, November 22, 2011 10:45:44 AM Peter Vollebregt wrote: > > > > Op 21-11-11 22:26, Roger Luedecke schreef: > > > > > On Monday, November 21, 2011 01:17:57 PM Peter Vollebregt wrote: > > > > >> On 11/21/2011 12:33 AM, Steven Sroka wrote: > > > > >>>> 2011/11/20 dh <mesamoo115(a)comcast.net>: > > > > >>>> > > > > >>>> On Sunday, November 20, 2011, Steven Sroka wrote: > > > > >>>>>> 2011/11/20 Krzysztof Żelechowski <giecrilj(a)stegny.2a.pl>: > > > > >>>> ----------snip------------ > > > > >> > > > > >> Linux is also different here, Root is a user and not an > > > > >> administrative mode. > > > > >> > > > > >> Peter > > > > > > Right. But if we can't make apps launched as root honor any of the > > > desktop users settings then it makes sense to make sure it is looking > > > out of place on purpose. > > > > I'm not sure what you mean here. It seems that you are saying that when > > running an application as su (kdesu someapp) that the users preferences > > should take precedence. If this is what you are saying then I disagree. > > > > When user1 runs an application as user2, they "become" user2 and > > user2's preferences should be in effect for that instance as much as > > possible. Except for window borders that seems to be what we currently > > have. Or am I missing something? > > > > see ya > > dh > > I think you are missing something. > As we currently have it, it is set to all default oxygen. So 'kdesu > someapp' will look just like everything else... until you change your > preferences. I guess it's been so long since I changed my root users prefs that I just assumed the defaults looked somewhat similar to a regular users defaults. > My primary point here is that it should either take the desktop users > settings so it will be able to adapt appropriately from default and not > look broken, or if it must look different from the users normal apps > then make it very very deliberate. As it currently stands, it looks like > a bug. And if the goal is to express the utility and danger of running a > program as root, then why was it themed with Oxygen in the first place? > ANd if themeing with Oxygen was to make it look native, then why the > insistence that it shouldn't take the users changes? "why the insistence that it shouldn't take the users changes?" Because it is not the regular user, it is root. Beyond this point I believe we are in agreement. I see your point about the conflict between consistancy and awareness. In the pre kdesu (sux) days, it was more difficult to run gui programs as su, when you logged in as root, you were greeted w/ a nice red bomb background. A background that was completely different from the default user themes. I don't want a "fuggly" root theme that I need to fix. I think your second option "it must look different from the users normal apps", "make it very very deliberate". I totally agree that the look should be different enough that it does not appear to be a mistake. I think this could be achieved with just a change in the default color schemes. I want consistant widgets, but that's just me. I kind of like the look of the Windows Server 2008 (administrator) gui, but I don't want my linux (admin) box to look like that. (at least by default) See ya dh -- 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] How do root applications get their theme data?
by Roger Luedecke 23 Nov '11

23 Nov '11

I'm trying to understand why root apps won't take the theme of the user environment. SO, how do root applications get their theme data? Does the root user have its own theme stuff like a normal user? -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

8 25

[opensuse-kde] Policy Kit modules in System Settings broken
by Roger Luedecke 22 Nov '11

22 Nov '11

I discovered in the course of another thread that the Policy Kit modules are broken. I don't fully understand how that is, and whats wrong. So I would like more information before I file a bug-report. Could you take a look and fill me in? Or write a fix. Whichever. At the the minumum I want to be able to file a good bug-report. -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 4

[opensuse-kde] Doubts KDE 47 Upstream in openSUSE 12.1
by Hernan_ 21 Nov '11

21 Nov '11

Greetings. I'm trying to upgrade KDE (openSUSE 12.1 fresh install) to latest stable changing packages to Upstream repo (KR47) but some conflicts with openSUSE branding packages makes me hesitate to continue or not... Conflicts (translated from spanish): 1) kwin-4.7.3-9.1.i586 requires kdebase4-workspace-branding = 4.7.3, but can't be done. providers needed: kdebase4-workspace-branding-upstream-4.7.3-9.1.i586[KR47] kdebase4-workspace-branding-basedonopensuse-12.1-6.1.2.i586[repo-oss] 2) kdelibs4-4.7.3-10.2.i586 requires kdelibs4-branding = 4.7, but can't be done. providers needed: kdelibs4-branding-upstream-4.7.3-10.2.i586[KR47] kdelibs4-branding-basedonopensuse-12.1-6.1.2.i586[repo-oss] kdelibs4-branding-upstream-4.7.2-5.2.2.i586[repo-oss] 3) kdm-4.7.3-9.1.i586 requires kdm-branding = 4.7, but can't be done. providers needed: kdm-branding-upstream-4.7.3-9.1.i586[KR47] kdm-branding-basedonopensuse-12.1-6.1.2.i586[repo-oss] kdm-branding-upstream-4.7.2-6.4.1.i586[repo-oss] --------------------------------------------------------------------------------------------------- How can I upgrade keeping the great openSUSE appearance? Or these branding packs doesn't have anything to do with it? Thanks in advance! -- Hernán Thiers Garcia Ingeniero Informático Santiago, Chile. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 3