openSUSE KDE February 2010

kde@lists.opensuse.org

51 participants
42 discussions

[opensuse-kde] Call for testing: Cross-distro building of KDE packages in OBS
by Lubos Lunak 07 Mar '10

07 Mar '10

Hello, I'm looking for people who'd be interested in testing a tool that helps packaging applications in the build service. If you have no experience with packaging, that's not an excuse but a perfect qualification :). Comments from people who do have experience are valued too. http://en.opensuse.org/KDE/Build_Service/Cross-distro has a HOWTO explaining the process. It is not very extensive, it's right to the point, but I hope it's sufficient. In case there are problems, try consulting http://en.opensuse.org/Build_Service or other wiki pages, or ask. I have packaged a couple of various KDE apps in home:llunak:kdetest, including the tool used for this itself, so it is possible to use those as a reference. There are no manual modifications to any of those packages besides providing INFO file if necessary. If you are interested, follow the HOWTO and try to package e.g. something from kde-apps.org or kde-look.org . I'd be especially interested in: - various build and packaging errors caused by the tool (there is also the possibility that the application tarball itself is broken) - wrong or missing mapping of package names (e.g. from the tarball to package names or between distributions) - any other problems that would hinder the usage of the tool for easy packaging of KDE apps Please mention the project and package name if you report any problems (report them simply as replies here). The tool is not perfect (nor can it be), so it is aimed to be used only for the initial package creation. It is possible to manually modify the generated files afterwards. I intend to create another tool to also help doing e.g. version updates. Thanks -- 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

3 6

Re: [opensuse-kde] New working and existing! icon for myComputer.desktop
by Johannes Obermayr 01 Mar '10

01 Mar '10

Am Samstag 27 Februar 2010 22:13:08 schrieb Tejas Guruswamy: > On 27/02/10 21:03, Johannes Obermayr wrote: >> Am Samstag 27 Februar 2010 21:36:58 schrieb Markus: >> >>> "mycomp" is a SUSE-specific icon which, btw, isn't even placed in the oxygen >>> folder, but in highcolor: >>> file:///usr/share/icons/hicolor/64x64/apps/mycomp.png >>> (if you use openSUSE right now, you should be able to open it) >>> >> Which package? >> >> $ /usr/share/icons> find -name *mycomp* >> $ /usr/share/icons> >> >> On all my systems "myComputer" (= "Arbeitsplatz" -> German) are without icons >> ... >> >> And dependencies are also OK ... >> <snip> >> tejas@hobbes:/usr/share/icons> find . -name "*mycomp*" | xargs rpm -qf | >> sort -u >> kdebase4-workspace-branding-openSUSE-11.2-60.4.x86_64 >> >> make sure you've not got branding-upstream installed instead That is it. I have *-branding-upstream installed for all packages and prefer it because of "ksnapshotting" for upstream translations (docs) ... But in this case we have only two possibilities: 1. Changing http://gitorious.org/opensuse/kdebase4-opensuse/blobs/master/config-files/u…: - Icon=mycomp + Icon=computer 2. Set a dependency in kdebase4-opensuse (spec-file): + Requires: kdebase4-workspace-branding-openSUSE I prefer first solution. Thanks. Johannes

2 1

Re: [opensuse-kde] New working and existing! icon for myComputer.desktop
by Johannes Obermayr 27 Feb '10

27 Feb '10

Am Samstag 27 Februar 2010 21:36:58 schrieb Markus: >Am Samstag 27 Februar 2010 20:36:20 schrieb Johannes Obermayr: > >> Hi, >> >> Icon "mycomp" have not existed (for a long time!) ... >> >> > "mycomp" is a SUSE-specific icon which, btw, isn't even placed in the oxygen folder, but in highcolor: > file:///usr/share/icons/hicolor/64x64/apps/mycomp.png > (if you use openSUSE right now, you should be able to open it) Which package? $ /usr/share/icons> find -name *mycomp* $ /usr/share/icons> On all my systems "myComputer" (= "Arbeitsplatz" -> German) are without icons ... And dependencies are also OK ... So: > > >> Please change: >> >> http://gitorious.org/opensuse/kdebase4-opensuse/blobs/master/config-files/u… >> >> - Icon=mycomp >>+ Icon=computer >> Icon "computer" is in package "oxygen-icon-theme". >> So we can usually guarantee that the icon works ... Thanks. Johannes -- 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] New working and existing! icon for myComputer.desktop
by Johannes Obermayr 27 Feb '10

27 Feb '10

Hi, Icon "mycomp" have not existed (for a long time!) ... Please change: http://gitorious.org/opensuse/kdebase4-opensuse/blobs/master/config-files/u… - Icon=mycomp + Icon=computer Icon "computer" is in package "oxygen-icon-theme". Thanks. Johannes -- 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] Amarok is now broken
by Andre Malin 27 Feb '10

27 Feb '10

Since my last zypper up this morning amarok refuse to load with the following message: amarok(31505)/kdecore (KSycoca): Trying to open ksycoca from "/var/tmp/kdecache-andre/ksycoca4" <unknown program name>(31503)/: Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name org.kde.amarok was not provided by any .service files" " My setup is: kde 4.4.0 release 224 Amarok package info: Name : amarok Relocations: (not relocatable) Version : 2.2.90 Vendor: obs://build.opensuse.org/KDE Release : 57.4 Build Date: mer. 24 févr. 2010 21:15:12 EST Install Date: jeu. 25 févr. 2010 13:13:22 EST Build Host: build31 Group : Productivity/Multimedia/Sound/Players Source RPM: amarok-2.2.90-57.4.src.rpm Size : 26807669 License: GPLv2+ Signature : DSA/SHA1, mer. 24 févr. 2010 21:16:32 EST, Key ID 58d8ff412e1efa87 URL : http://amarok.kde.org Note that I got the same error with amarok 2.2.1 Any clue? Andre. -- 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] Re: [opensuse] Can someone tell me what this is all about?
by Marc Chamberlin 26 Feb '10

26 Feb '10

Thanks Carlos, Han for your suggestions.. I will look further in the log files next time it happens and report what I find.. Be a little while though, going on vacation... Marc... On 2/25/2010 4:19 PM, Carlos E. R. wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > On Wednesday, 2010-02-24 at 17:04 -0800, Marc Chamberlin wrote: > >> I am running SuSE11.2 x86-64 and every so often I get the following >> spattered across all of my shells along with a pop up message. Doesn't >> seem to correlate with what I am doing at the moment, but I could be >> wrong on that... Last time I just did an ls of a dir that I had auto >> mounted... but it has occurred when I am doing other things as well... >> What is it and what do I do about it? Thanks.. >> >> Marc Chamberlin >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965309] ------------[ cut here ]------------ >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965332] invalid opcode: 0000 [#1] PREEMPT SMP >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965345] last sysfs file: >> /sys/devices/system/cpu/cpu1/cache/index1/shared_cpu_map >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965673] Stack: >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965725] Call Trace: >> >> Message from syslogd@bigbang at Feb 24 16:56:37 ... >> kernel:[ 4510.965861] Code: 50 30 4c 8b 0a 31 d2 48 85 f6 74 04 48 8b >> 56 40 48 05 88 02 00 00 48 89 de 48 c7 c7 58 be 6e 81 48 89 04 24 31 c0 >> e8 7a f8 3e 00<0f> 0b eb fe 0f 0b eb fe e8 3b 79 f0 ff 66 66 2e 0f 1f >> 84 00 00 > > Kernel problem. An alarm message gets posted to all terminals to make > sure you see it. The full report should be in the log. > > - -- Cheers, > Carlos E. R. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > > iEYEARECAAYFAkuHE5YACgkQtTMYHG2NR9VXvQCfZo7/6xj3639H677IX8DFggRN > QEYAoIUHEuJUi9hHfsPzh0gRxKT/t65C > =r1WL > -----END PGP SIGNATURE----- -- Marc Chamberlin www.marcchamberlin.com A man said unto the universe - "Sir I Exist!" "However" replied the universe "I do not see where that creates in me a sense of an obligation" S Crane.

1 0

[opensuse-kde] Kommander for kde 4.4
by Hans Krueger 26 Feb '10

26 Feb '10

is Kommander out for kde 4.4 suse 11 ? registered Linux user 289023 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

3 3

[opensuse-kde] eric 4 crash on exit with KDE4 from K:K:S:D on 11.1
by Hans-Peter Jansen 25 Feb '10

25 Feb '10

Hi, I suffer from a 100% reproducible crash on eric shutdown. All it takes is running eric, load a file, split the view "New view (with new split)" via context menu, and quit. Since neither Phil Thompson nor Detlev Offenbach is able to reproduce this, it's probably due to the Qt/KDE integration. The offending line is this: painting/qwindowsurface_x11.cpp:84 84 XFreeGC(X11->display, gc); I guess, it's X11 being NULL at that time. For PyQt, it's nearly impossible to control the order of d'tors during tear down due to the Python garbage collector behavior. Would it be enough to check for X11 != NULL at this point? Would such a check be accepted from openSUSE Qt4 maintainers, if it's successfully avoiding this crash? Could other reasons influence this behavior? My environment: openSUSE 11.1 (all packages from build service) qscintilla-2.4 qt4-4.5.3 python-sip-4.10 python-qt4-4.7 eric-4.4.1 TIA, Pete Application: eric4 (eric4.py), signal: Segmentation fault [Current thread is 1 (Thread 0xb74276c0 (LWP 25102))] Thread 2 (Thread 0xafdffb90 (LWP 25121)): #0 0xb6c5cebc in operator delete (ptr=0xad228430) at ../../../../libstdc++-v3/libsupc++/del_op.cc:49 #1 0xb56eac6d in QList<QPair<unsigned int, unsigned int> >::free(QListData::Data*) () from /usr/lib/libqscintilla2.so.5 #2 0xb56e74f7 in QsciAPIsWorker::run() () from /usr/lib/libqscintilla2.so.5 #3 0xb6f13592 in QThreadPrivate::start (arg=0x99050d0) at thread/qthread_unix.cpp:188 #4 0xb75bd1b5 in start_thread (arg=0xafdffb90) at pthread_create.c:297 #5 0xb74f93ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb74276c0 (LWP 25102)): [KCrash Handler] #6 0xb5d7cb22 in ~QX11WindowSurface (this=0xa6c4578) at painting/qwindowsurface_x11.cpp:84 #7 0xb5d75a46 in ~QWidgetBackingStore (this=0x83d28a8) at painting/qbackingstore.cpp:832 #8 0xb5bd6346 in QWidgetPrivate::deleteExtra (this=0xa601730) at kernel/qwidget.cpp:1503 #9 0xb5bd6b25 in ~QWidgetPrivate (this=0xa601730) at kernel/qwidget.cpp:227 #10 0xb5fc16da in ~QMenuPrivate (this=0xa601730) at widgets/qmenu_p.h:151 #11 0xb701e531 in ~QObject (this=0xa6016e0) at kernel/qobject.cpp:857 #12 0xb5bdc7bf in ~QWidget (this=0xa6016e0) at kernel/qwidget.cpp:1380 #13 0xb5fb6750 in ~QMenu (this=0xa6016e0) at widgets/qmenu.cpp:1380 #14 0xb678e62c in ~sipQMenu (this=0xa6016e0) at sipQtGuiQMenu.cpp:311 #15 0xb6789180 in release_QMenu (sipCppV=0xa6016e0, sipState=262) at sipQtGuiQMenu.cpp:2777 #16 0xb67891d7 in dealloc_QMenu (sipSelf=0x19) at sipQtGuiQMenu.cpp:2791 #17 0xb7121a9b in forgetObject () from /usr/lib/python2.6/site-packages/sip.so #18 0xb7121ad1 in sipWrapper_dealloc () from /usr/lib/python2.6/site-packages/sip.so #19 0xb764f65d in subtype_dealloc (self=0xa5056ac) at Objects/typeobject.c:1018 #20 0xb76326c1 in dict_dealloc (mp=0xa4b5934) at Objects/dictobject.c:911 #21 0xb711fa7b in sipSimpleWrapper_clear () from /usr/lib/python2.6/site-packages/sip.so #22 0xb712034f in sipWrapper_clear () from /usr/lib/python2.6/site-packages/sip.so #23 0xb7650ed2 in subtype_clear (self=0xa4f3eec) at Objects/typeobject.c:893 #24 0xb76b5fb6 in collect (generation=2) at Modules/gcmodule.c:714 #25 0xb76b6582 in PyGC_Collect () at Modules/gcmodule.c:1289 #26 0xb76a7db2 in Py_Finalize () at Python/pythonrun.c:420 #27 0xb76a7f47 in Py_Exit (sts=0) at Python/pythonrun.c:1689 #28 0xb76a8060 in handle_system_exit () at Python/pythonrun.c:1111 #29 0xb76a80ed in PyErr_PrintEx (set_sys_last_vars=1) at Python/pythonrun.c:1121 #30 0xb76a83fe in PyErr_Print () at Python/pythonrun.c:1030 #31 0xb76a859e in PyRun_SimpleFileExFlags (fp=0xbfc14f36, filename=0xbfc14f36 "/usr/lib/python2.6/site-packages/eric4/eric4.py", closeit=1, flags=0xbfc13438) at Python/pythonrun.c:930 #32 0xb76a8818 in PyRun_AnyFileExFlags (fp=0x805ecd8, filename=0xbfc14f36 "/usr/lib/python2.6/site-packages/eric4/eric4.py", closeit=1, flags=0xbfc13438) at Python/pythonrun.c:731 #33 0xb76b4e12 in Py_Main (argc=1, argv=0xbfc13504) at Modules/main.c:597 #34 0x08048692 in main (argc=) at Modules/python.c:23 -- 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] FYI: oxygen-molecule package
by Lubos Lunak 25 Feb '10

25 Feb '10

From the last meeting's minutes: * AI: package oxygen-molecule somewhere and announce (llunak) * AI: test oxygen-modulecule (everybody) It turns out oxygen-molecule has been already packaged in KDE:KDE4:Community by Pavol Rusnak, so this is only the announcement :). -- 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

1 0

[opensuse-kde] patterns-openSUSE-kde4 from 11.2-20.22.1 to 11.3-1.1.1
by CP Hennessy 25 Feb '10

25 Feb '10

Sorry, I'm sure that this is not only openSUSE KDE related but I'm wondering about a set of updates that I'm getting from the repository "openSUSE-11.2- Update". The version of the opensuse patterns are changing from 11.2-20.22.1 to 11.3-1.1.1 where I'm really wondering about the 11.2 to 11.3 change. e.g. from patterns-openSUSE-kde4 from 11.2-20.22.1 to 11.3-1.1.1 Is this change expected for a system that should only be based on openSUSE 11.2 ? Thanks, CPH -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE KDE February 2010