Bug#634996: libjogl2-core-java: won't work with trivial example from wikipedia
Package: libjogl2-core-java Version: 2.0-rc2-3 Severity: normal Hi, As a test I downloaded the jogl example from wikipedia. It doesn't work altough I added every .jar-file from the jogl2 packages to my classpath. Maybe you can add some notes to the enclosed readme.debian file telling what to jars/paths to add as a minimum to classpaths/ld paths/etc to get a basic test working. I totally agree to splitting everything up in seperate packages but now it's a bit unclear for the casual JOGL2 user what to do. This is what I tried: java -cp /usr/share/java/jogl.core.jar:/usr/share/java/jogl.util.jar:/usr/share/java/nativewindow.core.jar:/usr/share/java/jogl.awt.jar:/usr/share/java/jogl.util.awt.jar:/usr/share/java/nativewindow.awt.jar:/usr/share/java/jogl.gldesktop.jar:/usr/share/java/gluegen2-2.0-rc2-rt.jar:/usr/share/java/gluegen2-rt.jar:/usr/share/java/nativewindow.awt.jar:. JOGLQuad from http://en.wikipedia.org/wiki/Java_OpenGL which gives: Exception in thread main java.lang.UnsatisfiedLinkError: no nativewindow_awt in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1681) at java.lang.Runtime.loadLibrary0(Runtime.java:840) at java.lang.System.loadLibrary(System.java:1047) ... -- System Information: Debian Release: 6.0.2 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libjogl2-core-java depends on: ii libgluegen2-rt-java 2.0-rc2-7 Tool to automatically generate the libjogl2-core-java recommends no packages. libjogl2-core-java suggests no packages. -- no debconf information __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#558693: eclipse: does not start at all
Package: eclipse Version: 3.4.1-1 Severity: grave Justification: renders package unusable When started, it gives the following output: folk...@weerstationserver:~$ eclipse searching for compatible vm... testing /usr/lib/jvm/default-java...not found testing /usr/lib/jvm/java-gcj...not found testing /usr/lib/kaffe/pthreads...not found testing /usr/lib/jvm/java-6-sun/jre...found ZoneInfo: /usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/zi/ZoneInfoMappings (Too many open files) ZoneInfo: /usr/lib/jvm/java-6-sun-1.6.0.16/jre/lib/zi/ZoneInfoMappings (Too many open files) !SESSION 2009-11-29 22:20:50.155 --- eclipse.buildId=M20080911-1700 java.version=1.6.0_16 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2009-11-29 22:20:54.364 !MESSAGE !STACK 0 java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:114) at java.util.zip.ZipFile.init(ZipFile.java:131) at org.eclipse.osgi.framework.util.SecureAction.getZipFile(SecureAction.java:251) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.basicOpen(ZipBundleFile.java:81) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getZipFile(ZipBundleFile.java:94) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.checkedOpen(ZipBundleFile.java:67) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getEntry(ZipBundleFile.java:239) at org.eclipse.osgi.baseadaptor.BaseData.getEntry(BaseData.java:97) at org.eclipse.osgi.internal.baseadaptor.AdaptorUtil.loadManifestFrom(AdaptorUtil.java:192) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.getGeneratedManifest(EclipseStorageHook.java:371) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.createCachedManifest(EclipseStorageHook.java:367) at org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.getManifest(EclipseStorageHook.java:472) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.loadManifest(BaseStorage.java:297) at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:82) at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:938) at org.eclipse.osgi.framework.internal.core.Framework$2.run(Framework.java:854) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:905) at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:849) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:234) at org.eclipse.update.internal.configurator.ConfigurationActivator.installBundles(ConfigurationActivator.java:197) at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:82) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321) -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages eclipse depends on: ii eclipse-jdt 3.4.1-1Java Development Tools plug-ins fo ii eclipse-pde 3.4.1-1
Bug#549329: after restarting tomcat6, it won't listen on any ports
Ok problem can be closed: it DOES open ports, it only takes a couple of minutes(!) to do so. Package: tomcat6 Version: 6.0.20-5 Severity: normal After restarting tomcat6, it won't listen on any ports. E.g. /etc/init.d/tomcat6 restart Connector port=8880 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / mauer:/usr/local/games/stop# netstat -nap | grep 8880 mauer:/usr/local/games/stop# Not reproducible here. Are you sure tomcat6 was running before doing restart? Thats a prerequesite of restart. mk...@quadriga ~ sudo netstat -tulpen | grep jsvc tcp6 0 0 :::8080 :::*LISTEN 1132874698210433/jsvc mk...@quadriga ~ sudo sed -i -e 's/8080/8280/' /etc/tomcat6/server.xml mk...@quadriga ~ sudo /etc/init.d/tomcat6 restart * Stopping Tomcat servlet engine tomcat6 ...done. * Starting Tomcat servlet engine tomcat6 ...done. mk...@quadriga ~ sudo netstat -tulpen | grep jsvc tcp6 0 0 :::8280 :::*LISTEN 1134184608826653/jsvc mk...@quadriga ~ : Folkert van Heusden -- Ever wonder what is out there? Any alien races? Then please support the s...@home project: setiathome.ssl.berkeley.edu -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#549181: tomcat6: binds to port 8080, this conflicts with other packages on the system
Package: tomcat6 Version: 6.0.20-5 Severity: normal Tomcat6 wants to bind to port 8080. This, in my case, conflicts with other installed software. Solution would be making the tomcat6 bind-port configurable. Preferably with bind to networkcard as well. With which software does it conflict? Is it a Debian packaged software? It is Squid. Debian binds it to 3128 or so but 8080 is a more standard port for proxies so we decided to bind it to that one. Generelly this is a problem. We need to document this in a better way. You mean there's a workaround? Can it be configured somewhere somehow? Folkert van Heusden -- www.vanheusden.com/multitail - win een vlaai van multivlaai! zorg ervoor dat multitail opgenomen wordt in Fedora Core, AIX, Solaris of HP/UX en win een vlaai naar keuze -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#549181: tomcat6: binds to port 8080, this conflicts with other packages on the system
Package: tomcat6 Version: 6.0.20-5 Severity: normal Tomcat6 wants to bind to port 8080. This, in my case, conflicts with other installed software. Solution would be making the tomcat6 bind-port configurable. Preferably with bind to networkcard as well. With which software does it conflict? Is it a Debian packaged software? It is Squid. Debian binds it to 3128 or so but 8080 is a more standard port for proxies so we decided to bind it to that one. Ah, okay. 3128 is indeed the stanard port for web proxies. I would call 8080 non-standard for this. I close the bug because of this for now as the problem is home-brewn and does not exist in default Debian-packages. No no, 3128 is not a standard. 8080 is the standard. Really. Generelly this is a problem. We need to document this in a better way. You mean there's a workaround? Can it be configured somewhere somehow? You can configure this in /etc/tomcat6/server.xml. Just replace 8080 by something you like and restart tomcat. I don't know why that suddenly works but it seems it does (tried it minutes ago, again) so indeed it can be closed. Folkert van Heusden -- www.biglumber.com - site where one can exchange PGP key signatures -- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#549181: tomcat6: binds to port 8080, this conflicts with other packages on the system
Package: tomcat6 Version: 6.0.20-5 Severity: normal Tomcat6 wants to bind to port 8080. This, in my case, conflicts with other installed software. Solution would be making the tomcat6 bind-port configurable. Preferably with bind to networkcard as well. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-pps (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages tomcat6 depends on: ii adduser 3.110 add and remove users and groups ii jsvc 1.0.2~svn20061127-9 wrapper to launch Java application ii tomcat6-common 6.0.20-5Servlet and JSP engine -- common f tomcat6 recommends no packages. Versions of packages tomcat6 suggests: ii tomcat6-admin 6.0.20-5 Servlet and JSP engine -- admin we pn tomcat6-docs none (no description available) pn tomcat6-examples none (no description available) -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#510139: libmysql-java: package not in default java library path so all programs using will fail
Package: libmysql-java Version: 5.1.6+dfsg-1 Severity: normal libmysql-java: package not in default java library path so all programs using will fail one now needs to explicit some environment variable to get it to work which is unfortunate as then one needs scripts specific to the linux distribution it runs on -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libmysql-java depends on: ii gij-4.1 [java2-runtime] 4.1.2-16 The GNU Java bytecode interpreter ii sun-java6-jre [java2-runtime] 6-07-4 Sun Java(TM) Runtime Environment ( libmysql-java recommends no packages. Versions of packages libmysql-java suggests: ii gij [java-virtual-machine]4:4.3.2-2 The GNU Java bytecode interpreter ii gij-4.1 [java-virtual-machine 4.1.2-16 The GNU Java bytecode interpreter ii gij-4.3 [java-virtual-machine 4.3.2-2The GNU Java bytecode interpreter pn libcommons-logging-java none (no description available) pn liblog4j1.2-java none (no description available) ii sun-java6-jre [java-virtual-m 6-07-4 Sun Java(TM) Runtime Environment ( -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
