October 2010 - openSUSE KDE 3 - openSUSE Mailing Lists

[opensuse-kde3] KDE:KDE3 issues
by Ilya Chernykh 29 Apr '11

29 Apr '11

Hi people. I suggest you all to subscribe to opensuse-kde3(a)opensuse.org so I could send e-mails directly to this mailing list. I have several questions, suggestions and clarifications regarding status of KDE:KDE3. - First of all I have to announce that we completed for the most part moving of packages from KDE:Communitry. It has been done much quicker than by the KDE4 team. Some packages are not moved because they have problems either with build or during runtime. Some packages like ksquirrel have well-known security issues. I do not know should we include them in KDE:KDE3 or not. - It seems that some packages were disabled for Factory. Namely, kdemultimedia3 and anything related to Beagle. Please tell me the actual reason or the disabling. I can add to KDE:KDE3 repository any libraries needed for the build. For example, I can restore kdemultimedi3. Or are there any other reasons for the disabling? Beagle in particular is essential for finding topics in KDE help system. - I am planning to add some soft dependencies to some basic KDE packages to improve user's experience. For example, it would be good in my view if kdebase3-workplace recommended kde3-knemo and desktoptext-config. Also some plugins may be recommended. Please tell me if this is against OpenSUSE packaging policy. - I have long-range plans to include Qt3-based versions of Yast2, VirtualBox and Firefox. If somebody has experience in compiling Firefox for Qt3, any help welcome. - OpenSUSE maintainers, what's your opinion about possibility to include KDE3 option to OpenSUSE? The basic part of KDE3 (including kicker, konq, ksysguard, kcontrol) is already included (to be precise, it was never removed from OpenSUSE), but the ability to logon on KDE3 is disabled. The status of KDE3 repository has improved considerably in recent times, so it may look reasonable to reconsider KDE3's status. To enable a user to install KDE3 on his system we need to include only a tiny package kdebase3-session which takes only 4 kb, this package includes the .desktop file for the session manager so the user could choose KDE3 on the logon screen. - Besides this one can consider including KDE:KDE3 repository in the list of community repositories along with the Education repo etc so a user could be able to install the full version of KDE3 from the community repo. - Some KDE3 packages (koffice, pdfedit) currently experience problems with building for Factory 32-bit architecture. This is not a KDE3 bug, but an issue of brocken zlib in Factory, it was also observed on other distributions. I have reported a bugreport: https://bugzilla.novell.com/show_bug.cgi?id=634995 -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

7 23

[opensuse-kde3] kdebase3 rpmbuild --rebuild error ‘EINTR’ was not declared in this scope
by David C. Rankin 13 Oct '10

13 Oct '10

Guys, Looking at the sftp problem, I was attempting to rebuild kdebase3, but I've run into a snag. Not sure if it is a compiler issue or package issue. The config finishes fine, but then the build dies in kdmlib/dmctl.cpp with the error: dmctl.cpp:156: error: ‘EINTR’ was not declared in this scope The error in context is: configure: WARNING: unrecognized options: --with-pcsc-dir, --with-cdparanoia, --with-motif-libraries, --with-motif-includes, --with-samba-libs Good - your configure finished. Start make now + do_make -j2 makeobj[0]: Entering directory `/usr/src/packages/BUILD/kdebase-3.5.10' Calling /usr/bin/unsermake --no-real-compare VERBOSE=1 --compile-jobs=2 g++ -DHAVE_CONFIG_H -I./kdmlib -I/usr/src/packages/BUILD/kdebase-3.5.10/kdmlib -I. -I/usr/src/packages/BUILD/kdebase-3.5.10/kdm/kfrontend -I/opt/kde3/include -I/usr/lib/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_LARGE_FILES=1 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -fPIC -DPIC -c /usr/src/packages/BUILD/kdebase-3.5.10/kdmlib/dmctl.cpp -o ./kdmlib/.libs/dmctl.o -Wp,-MD,./kdmlib/.deps/dmctl.TUlo g++ -DHAVE_CONFIG_H -I./kwin/clients/keramik -I/usr/src/packages/BUILD/kdebase-3.5.10/kwin/clients/keramik -I. -I/usr/src/packages/BUILD/kdebase-3.5.10/kwin/clients/keramik/../../lib -I/opt/kde3/include -I/usr/lib/qt3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_LARGE_FILES=1 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -c /usr/src/packages/BUILD/kdebase-3.5.10/kwin/clients/keramik/embedtool.cpp -o ./kwin/clients/keramik/embedtool.o -Wp,-MD,./kwin/clients/keramik/.deps/embedtool.TUo creating ./libkonq/konq_undo.kidl creating ./libkonq/konq_historycomm.kidl creating ./libkonq/konq_faviconmgr.kidl creating ./kicker/libkicker/kickerSettings.h creating ./kicker/libkicker/kickerSettings.cpp /usr/src/packages/BUILD/kdebase-3.5.10/kdmlib/dmctl.cpp: In member function ‘bool DM::exec(const char*, QCString&)’: /usr/src/packages/BUILD/kdebase-3.5.10/kdmlib/dmctl.cpp:156: error: ‘EINTR’ was not declared in this scope Error creating ./kdmlib/dmctl.lo. Exit status 1. creating ./kwin/kcmkwin/kwinrules/detectwidgetbase.h makeobj[0]: Leaving directory `/usr/src/packages/BUILD/kdebase-3.5.10' error: Bad exit status from /var/tmp/rpm-tmp.99348 (%build) RPM build errors: InstallSourcePackage: Header V3 DSA signature: NOKEY, key ID 7c99e700 Bad exit status from /var/tmp/rpm-tmp.99348 (%build) I found some old posts that suggested adding the include of <cerrno.h>, but I'm not entirely sure where to add it to insure proper scope. Any ideas? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

1 0

[opensuse-kde3] sftp url parsing (with included port) broken in 11.3 kde3 - fish OK - howto work around?
by David C. Rankin 12 Oct '10

12 Oct '10

Ilya, all, I've run across a strange issue with sftp on 11.3 kde3 after recent updates. Attempting to connect to my server on my LAN with sftp, I get the following error: Unexpected sftp error: 2 - konqueror Error encountered while talking to ssh I don't know what recent update may have caused this (I suspect openssl), but it isn't suse specific. It also broke on Arch. The strange thing with both is 'fish' works fine -- even on a non-standard port. (apparently fish respects ~/.ssh/config) Another data point I have is that sftp still works fine with 11.0. So I guess whatever update 11.3 got that 11.0 didn't is causing the issue. I've checked syslog and nothing gets logged with the failure. It looks like a command line parsing issue. In konqueror, if I enter the url in the following form (as I've done for at least 4 years): sftp://user@host:port/dir1/dir2 sftp gives the error. However in 11.3 if I use the command line and do: sftp -Pport user@host:/dir1/dir2 I connect just fine. So it looks like the string kde3 now sends to ssh isn't working anymore. Ahah!! I just checked another box from 11.3 that uses the default port 22 as the ssh port and I can connect in konqueror in 11.3 via sftp just fine! Bingo. So I guess I need to know where I can try and fix this?? It seems that whatever changed in ssh no longer lets kde3 specify sftp locations as: sftp://user@host:port/dir1/dir2 Any thoughts on how I can work around this problem?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

1 7

[opensuse-kde3] Trinity KDE
by Robert Xu 08 Oct '10

08 Oct '10

Hi all, So, I know my email got forwarded here, so I'm wondering, who's up for this task? :) We're building for all SuSEs and Fedora, and Mandriva is our second priority. PS, can someone register a KDE:Trinity project or something? It might be a starting point. For now, development will stay at home:bravoall1552:trinity. -- later, Robert Xu -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

4 3

[opensuse-kde3] sftp url parsing (with included port) broken in 11.3 kde3 - fish OK - howto work around?
by David C. Rankin 07 Oct '10

07 Oct '10

Ilya, all, I've run across a strange issue with sftp on 11.3 kde3 after recent updates. Attempting to connect to my server on my LAN with sftp, I get the following error: Unexpected sftp error: 2 - konqueror Error encountered while talking to ssh I don't know what recent update may have caused this (I suspect openssl), but it isn't suse specific. It also broke on Arch. The strange thing with both is 'fish' works fine -- even on a non-standard port. (apparently fish respects ~/.ssh/config) Another data point I have is that sftp still works fine with 11.0. So I guess whatever update 11.3 got that 11.0 didn't is causing the issue. I've checked syslog and nothing gets logged with the failure. It looks like a command line parsing issue. In konqueror, if I enter the url in the following form (as I've done for at least 4 years): sftp://user@host:port/dir1/dir2 sftp gives the error. However in 11.3 if I use the command line and do: sftp -Pport user@host:/dir1/dir2 I connect just fine. So it looks like the string kde3 now sends to ssh isn't working anymore. Ahah!! I just checked another box from 11.3 that uses the default port 22 as the ssh port and I can connect in konqueror in 11.3 via sftp just fine! Bingo. So I guess I need to know where I can try and fix this?? It seems that whatever changed in ssh no longer lets kde3 specify sftp locations as: sftp://user@host:port/dir1/dir2 Any thoughts on how I can work around this problem?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

1 0

[opensuse-kde3] Fwd: [opensuse-kde] Trinity KDE
by Will Stephenson 06 Oct '10

06 Oct '10

FYI, triskaphiles. -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex

1 0

[opensuse-kde3] flash dysfunctional with KDE3 konqueror
by Hans-Peter Jansen 06 Oct '10

06 Oct '10

From the "too tired to watch the nsplugin viewer crashing all day long" camp Hi, since $subject nagged me quite some time now, I crawled though the web and found some hints, that may solve the issue. Backported them. Check out home:frispete:KDE3/kdebase3 (when ready..) and let me know about the outcome. I'm able to view http://ti.arc.nasa.gov/destination/iss/flash/index.html successfully ATM, BTW. Enjoy, Pete -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

3 12

[opensuse-kde3] Integration of Trinity KDE into opensuse
by Ernst Kipfmüller 04 Oct '10

04 Oct '10

Hi all, I'm just an enthusiastic KDE 3.5 user, but I read about the new KDE 3.5.12 release at http://trinity.pearsoncomputing.net. The people there are working at rpm builds, and one of their devs asked about the config options and build scripts, see http://trinity-devel.pearsoncomputing.net/?0::609 So I wanted to ask here, are there any plans or negotiations about an trinity based opensuse build? I think it shouldn't be too difficult to adapt their KDE to opensuse. They probably fixed a lot of minor issues since 3.5.10, whilst afaik only few things were fixed in the opensuse repo. From the mailing list I didn't get any information, if there's already some kind of cooperation. kind regards, Ernst -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

2 2