openSUSE KDE January 2009

kde@lists.opensuse.org

52 participants
40 discussions

[opensuse-kde] List of some packages of kde-maintainers
by Stephan Binner 10 Feb '09

10 Feb '09

Hello, below a list of packages currently assigned to kde-maintainers(a)suse.de which - if I made no mistake - are not required by any product pattern. They IMHO do not have to be part of the core distro and could be maintained by someone in Contrib repository[1], KDE:Community repositories or dropped without pain. So far I discussed this with nobody yet, so any opinion about this package list or how to proceed? :-) Bye, Steve [1] http://en.opensuse.org/Contrib basket celestia datakiosk eric fuse_kio hk_classes katalog katapult kbarcode kbiff kcall kcfgcreator kconfigeditor kdbg kdesvn kdiff3 kdissert kile kinternet kio-locate kio_slp klamav kmobiletools kmymoney knoda konserve kover kphotoalbum kpl kradio krecord krename krpmbuilder krusader ksimus kst ksystemlog ktranslator kvpnc kwatch kxmleditor pgcalc pwmanager qscintilla qtc rekall rsibreak scribus smb4k speedcrunch viki -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

9 16

[opensuse-kde] First experiences with KDE 4.2
by Stefan Kunze 05 Feb '09

05 Feb '09

On Tuesday evening i updated to 4.2 on my Opensuse 11.1. I will just note a few experiences. 1. Dependency Issues when updating. Some KDE 4.1.3 packages just will refuse to be replaced and complain but if you look closely you can find a n easy solution to the dependency issues 2. Performance - Holy Cow - after the reboot after updating (logout - login was not enough) - i just couldn't believe my eyes. The System was flying. It is highly reactive and just showed me how slow KDE 4.1 and 3.5 were in comparison. I never really missed the performance before because i never had it but i dont want to go back. Great Job. 3. The visual Impression is pleasing - although i would suggest before update go back to the default theme - because my theme/color combination looked horrible right after the update - because it just did not fit anymore. 4. So far no problems with programms running and the startup Time of programms is greatly reduced on my system. My heartfelt Congratulations to all the KDE Devs - keep up the good work and KDE 4.3 will be close to World Domination. Deeply Impressed Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

8 9

[opensuse-kde] thinkpad volume buttons in 11.1
by Michal Hlavac 04 Feb '09

04 Feb '09

Hello, I have latest KDE 4.2 with 11.1 and thinkpad r60. But behavior I am describing is same with KDE 4.1.3. Thinpad volume buttons worked for some time. I don't know what happens when it stopped working. Strange think is that it works when I create new user. But also after some time it crashes. Stop working means there are no alsa volume changes and no "OSD" when I push these buttons. It changes only system volume. thanks, m. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

2 4

[opensuse-kde] Which bug reports go upstream?
by Marc Benstein 04 Feb '09

04 Feb '09

In one of my latest bug reports Lubos Lunak said, "Please report problems with unstable versions upstream unless they're SUSE-specific." This was a report from the Factory, (KDE: 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101)) "release 78.4") which I thought was SUSE specific and not considered exactly UNSTABLE. If Factory is not considered SUSE specific then what is? Is it branding, packaging, patches, and backports only? I use KDE and openSUSE for work around ten hours every single day. I really only have time to report bugs to one location if I even manage to get around to reporting them. Should the beta-customer be deciding what reports go upstream from factory? It seems reasonable to me that all Factory reports should go to bugzilla.novell.com and that all UNSTABLE reports should go to bugs.kde.org. This way Factory can become SUSE specific due to the KDE Team deciding what goes upstream and what gets patched. -- Marc Benstein -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

4 8

[opensuse-kde] correct update path KDE 4.2
by Günther J. Niederwimmer 03 Feb '09

03 Feb '09

Hello, can any tell the correct update path with all other updates pathes for KDE 4.2 and openSUSE-11.1 ? I read all Emails and search on o.o, but have big problem to understand this Philosophie ? I mean I am not allone ;) The best i mean, is a 1Click install in a opensuse.org Site, please ! -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

10 19

[opensuse-kde] Akregator for KDE4 crashing
by Rick Friedman 31 Jan '09

31 Jan '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm running opensuse 11.0 and KDE 4.2. I have the package kde4-akregator 4.2.0-86.3 installed. When I try to run akregator, it crashes. When I run it from konsole, I get the following: rick@chisum:~> akregator Object::connect: No such signal Akregator::SubscriptionListView::signalContextMenu(K3ListView*,Akregator::TreeNode*,QPoint) Object::connect: (sender name: 'feedtree') Object::connect: (receiver name: 'akregator_view') Object::connect: No such signal Akregator::SubscriptionListView::signalDropped(KUrl::List&,Akregator::TreeNode*,Akregator::Folder*) Object::connect: (sender name: 'feedtree') Object::connect: (receiver name: 'akregator_view') akregator(4834): Communication problem with "akregator" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " rick@chisum:~> KCrash: Application 'akregator' crashing... sock_file=/home/rick/.kde4/socket-chisum/kdeinit4__0 Has anyone seen this? Anyone have any ideas what maybe causing this? Thanks, Rick - -- Rick's Law: What cannot be imagined will be accomplished by a fool. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkmEr0UACgkQPIcjS54RJeAb7QCfWI3vzGUXmip8TkMmuLVhmsyF e0MAn2eYBOfhrv0/W7ujeUhI3YXIEeET =Y/de -----END PGP SIGNATURE----- -- 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] Helping with bugzilla screening
by Lubos Lunak 30 Jan '09

30 Jan '09

Hello, as discussed in the last KDE openSUSE community meeting, we currently have (and keeping receiving) many KDE bugreports in our bugzilla. There are community members who already help with them and some people have expressed interest in doing so. For these people I've written http://en.opensuse.org/Bugs:KDE/Screening as a page explaining how you can help. Currently we (KDE developers working on openSUSE) spend quite a lot of time just handling the bugreports and we are therefore very grateful to people who help with it. If you would like to help KDE on openSUSE and don't know how, you would be very welcome. It is not really very difficult and helping this way would also mean that us developers would have more time for further improving of the KDE provided by openSUSE. I currently consider the page to be a working version, presented here to ask for comments (especially from other developers and people who already have been helping with bugzilla screening). If there is anything unclear, wrong or missing, please comment or simply fix. PS: The page is written as guidelines, not strict rules, and using common sense is occassionally required ;). Especially if you are new to this, please try to be careful until you gain some experience, some bugreports may have complex consequences that are not simple to understand, so when unsure, better leave a bugreport as it is or ask. If the reporter will be questioning your resolution of the bugreport (may happen e.g. with @novell.com reporters), just ping us and we will either back up your decision or change it. -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak(a)suse.cz , l.lunak(a)kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- 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] Can't enable strigi service in kde 4.2 RC1, opensuse 11.1
by Danilo Luvizotto 30 Jan '09

30 Jan '09

Hi, Is there any trick to enable strigi service in kde 4.2 RC1 in opensuse 11.1? I just can't enable it. Thanks -- 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] [11.0] Error when installing kdesvn_1.2.2-3.8.x86_64.rpm
by Werner Flamme 26 Jan '09

26 Jan '09

Hi, when I try to update kdesvn-1.0.2-2.4 with the newer kdesvn_1.2.2-3.8, I get an error: error: unpacking of archive failed on file /usr/share/doc/kde/HTML/en/kdesvn/hi128-filesys-kdesvnupdates.png;49782cc2: cpio: link failed - Invalid cross-device link I tried downloading another copy, but it's the same error. Where's my fault? It seems a problem that /usr/share/doc is on another filesystem on my box, right? Is it possible to use a symlink instead of a hardlink? Regards, Werner -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

1 1

[opensuse-kde] 4.2 problems
by Bob S 25 Jan '09

25 Jan '09

Hello SuSE KDE people. I installed 11.1 shortly after it was released and elected to install KDE4.1 as a test bed and to see how I liked it. It was OK but lt lacked many features. So I waited until 4.2 was released, The other night I did the "one click" install and came up with a huge amount of dependencies. I kind of expected that from following the mailing list. On many of the dependencies the only option was to uninstall the package. Kmail was one of them. I OK'd that (and others) thinking they would be reinstalled. Wrong !! The actual message on the dependency was "Nothing provides libical0>=0.43 Needed by kdepimlibs4-4.1.96-1.5x86_64" and was the same for many other apps. Now, kdepimlibs4-4.1 ???? Why ? And the other apps with dependencies were designated 4.1 also. No upgrades on those packages? And what the heck is, or where do I find libical0 ? Not only that, when the upgrade was done doing it's thing, the next time I booted up 11.1 the whole desktop had changed, theme, everything. AND the taskbar kicker or whatever it is called now was missing. Gone! I couldn't figure out how to bring it back or find a way to bring up the menu or log out. So, bottom line, if someone could explain the libical thing so I can get Kmail back it would be good. Then maybe I can find out how KDE4.2 is. Bob S -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde+help(a)opensuse.org

8 10

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 January 2009