Re: HEADS UP: sgtty removal this weekend
Hello everyone, Heads down: http://lists.freebsd.org/pipermail/cvs-src/2008-June/092121.html I've also increased the __FreeBSD_version to 800039, which could be useful for you folks. I'd like to thank several people, especially miwi@ for committing most of my patches and pav@ for performing an experimental ports build with my patchset. Thanks! -- Ed Schouten [EMAIL PROTECTED] WWW: http://80386.nl/ pgpCfAK1R2f8U.pgp Description: PGP signature
FreeBSD Port: atunes-1.9.0
Dear aTunes maintainer, I have a problem starting aTunes. I have verified the used VM does basically work and starts other java applications. Help would be very appreciated, please tell me how i can help you. Here is output from my shell, that illustrates the problem and environment: elgrande:/home/elgrande# uname -a FreeBSD freebsdangel.local 7.0-STABLE FreeBSD 7.0-STABLE #1: Sat Jun 14 16:28:34 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/elgrande i386 elgrande:/home/elgrande# setenv JAVA_HOME /usr/local/jdk1.6.0 elgrande:/home/elgrande# java -version java version 1.6.0_03-p4 Java(TM) SE Runtime Environment (build 1.6.0_03-p4-elgrande_14_jun_2008_16_00-b00) Java HotSpot(TM) Client VM (build 1.6.0_03-p4-elgrande_14_jun_2008_16_00-b00, mixed mode) elgrande:/home/elgrande# atunes INFO: aTunes is listening for other instances on port INFO[START ] Starting aTunes 1.8.3 Ostwind (Build 355 [08/05/2008]) INFO[START ] Running in Java Virtual Machine 1.6.0_03-p4 INFO[START ] Arguments = [] INFO[START ] Debug mode = false INFO[START ] Execution path = /usr/local/share/atunes INFO[HANDLER ] Could not read application state ERROR [INTERNAL ERROR] -- Logger.internalError [1] java.lang.reflect.InvocationTargetException ERROR [INTERNAL ERROR] -- Logger.internalError [1] java.awt.EventQueue.invokeAndWait(EventQueue.java:997) ERROR [INTERNAL ERROR] -- Logger.internalError [1] javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1323) ERROR [INTERNAL ERROR] -- Logger.internalError [1] net.sourceforge.atunes.kernel.Kernel.startKernel(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [1] net.sourceforge.atunes.Main.main(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [2] null ERROR [INTERNAL ERROR] -- Logger.internalError [3] java.lang.reflect.InvocationTargetException ERROR [INTERNAL ERROR] -- Logger.internalError [3] java.awt.EventQueue.invokeAndWait(EventQueue.java:997) ERROR [INTERNAL ERROR] -- Logger.internalError [3] javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1323) ERROR [INTERNAL ERROR] -- Logger.internalError [3] net.sourceforge.atunes.kernel.Kernel.startKernel(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [3] net.sourceforge.atunes.Main.main(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] java.lang.NullPointerException ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.MultiUIDefaults.getUIError(MultiUIDefaults.java:117) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.UIDefaults.getUI(UIDefaults.java:741) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.UIManager.getUI(UIManager.java:1012) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JPanel.updateUI(JPanel.java:109) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JPanel.init(JPanel.java:69) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JPanel.init(JPanel.java:92) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JPanel.init(JPanel.java:100) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JRootPane.createGlassPane(JRootPane.java:527) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JRootPane.init(JRootPane.java:347) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JFrame.createRootPane(JFrame.java:260) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JFrame.frameInit(JFrame.java:241) ERROR [INTERNAL ERROR] -- Logger.internalError [4] javax.swing.JFrame.init(JFrame.java:164) ERROR [INTERNAL ERROR] -- Logger.internalError [4] net.sourceforge.atunes.gui.views.controls.CustomFrame.init(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] net.sourceforge.atunes.gui.StandardFrame.init(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] net.sourceforge.atunes.kernel.handlers.VisualHandler.init(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] net.sourceforge.atunes.kernel.handlers.VisualHandler.clinit(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] net.sourceforge.atunes.kernel.Kernel$2.run(Unknown Source) ERROR [INTERNAL ERROR] -- Logger.internalError [4] java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:199) ERROR [INTERNAL ERROR] -- Logger.internalError [4] java.awt.EventQueue.dispatchEvent(EventQueue.java:597) ERROR [INTERNAL ERROR] -- Logger.internalError [4] java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) ERROR [INTERNAL ERROR] -- Logger.internalError [4]
nvidia-driver: KDE screen corruption
Hi, I just upgraded the nvidia-driver to the latest version 173.14.05 and now I find that the task bar in KDE is corrupted - the rest of the screen is OK, just the task bar is affected. This didn't happen with the previous version I was running (169.x.x I think, not sure exactly). Screenshot here - http://www.magichamster.com/pics/snapshot2.png Is this a known problem? Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: atunes-1.9.0
Tino Engel [EMAIL PROTECTED] wrote: I have a problem starting aTunes. Before debugging any further, have you tried deleting the .aTunes config folder in your home directory as suggested here: http://sourceforge.net/forum/forum.php?thread_id=2027068forum_id=656585 -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia-driver: KDE screen corruption
On Saturday 14 June 2008, Mark Ovens wrote: I just upgraded the nvidia-driver to the latest version 173.14.05 and now I find that the task bar in KDE is corrupted - the rest of the screen is OK, just the task bar is affected. This didn't happen with the previous version I was running (169.x.x I think, not sure exactly). Screenshot here - http://www.magichamster.com/pics/snapshot2.png Is this a known problem? I use kde and latest nvidia-driver but I have no such a problem. Max ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
New version for unmaintained port www/nanoblogger
Hi all. Today version 3.4RC1 was released for the currently unmaintained port www/nanoblogger. As I use this software I would like to prepare a port for nanoblogger 3.4. I just wanted to make sure there's no one else doing the same thing in parallel. So if someone is working on porting nanoblogger 3.4 please drop me a line. Regards Tobias ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: atunes-1.9.0
Sahil Tandon wrote: Tino Engel [EMAIL PROTECTED] wrote: I have a problem starting aTunes. Before debugging any further, have you tried deleting the .aTunes config folder in your home directory as suggested here: http://sourceforge.net/forum/forum.php?thread_id=2027068forum_id=656585 Yes, I did delete the config dir. Did not solve the issue. Nevertheless I found out, how to fix this issue temporarily: aTunes 1.8.0 works fine with jdk-1.6.0.3p4_2 from ports. The problem starts to occur with 1.8.1. I did some research that could point to the problem: Maybe the source of the problem is, that jdk16 from ports does not have the AWTUtilities class yet (that at least is the reason, why aTunes 1.9.0 does not work). But I could not confirm on 1.8.3. Actually it seems that the newer aTunes versions require a higher update level of jdk. Regards, Tino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: quagga-0.99.9_7
Hi Boris, I would like to turn your attention on one little bug in quagga on FreeBSD. Why don´t we user groupname quaggavty from the beginning when the quagga had been ported to FreeBSD ? What do I mena ? I will show you the diffrence between quagga on Debian and on our FreeBSD. They use group quaggavty for command vtysh and they help themself with pam.d/quagga file. [EMAIL PROTECTED] ls -l /etc/pam.d/quagga -rw-r--r-- 1 root root 162 2007-09-26 08:20 /etc/pam.d/quagga user$ cat /etc/pam.d/quagga # Any user may call vtysh but only those belonging to the group quaggavty can # actually connect to the socket and use the program. authsufficient pam_permit.so [EMAIL PROTECTED] whoami user [EMAIL PROTECTED] ls -l /etc/quagga/vtysh.conf -rw-rw 1 quagga quaggavty 63 2008-01-10 01:28 /etc/quagga/vtysh.conf [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] cat /etc/quagga/vtysh.conf username user nopassword username root nopassword log syslog [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] egrep quaggavty /etc/group quaggavty:x:106:user [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] vtysh Hello, this is Quagga (version 0.99.5). Copyright 1996-2005 Kunihiro Ishiguro, et al. server# exit [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] So here it works, now FreeBSD: whoami resu ls -l /etc/pam.d/quagga ls: /etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/pam.d/quagga ls: /usr/local/etc/pam.d/quagga: No such file or directory ls -l /usr/local/etc/quagga/vtysh.conf -rw-rw-r-- 1 quagga quagga 129 10 led 01:52 /usr/local/etc/quagga/vtysh.conf cat /usr/local/etc/quagga/vtysh.conf username resu nopassword username root nopassword log syslog pw group show quagga quagga:*:101:resu vtysh Exiting: failed to connect to any daemons. Is possible to repair it ? How can I assit you ? It would be good if new version 0.99.10 will count with vtysh like on Debian. Thank you. Bye. Daniel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
qpopper update
I am in the final stages of updating the qpopper port from version 4.0 to 4.1. However, there are a number of patches that have been incorporated into qpopper in the past that raise some questions. qpopper alters the names of all the binaries from popper* to qpopper*. I first thought that was done to avoid name conflicts with the port popper. However, upon investigating, the popper port is an older version of qpopper. Is there a reason to maintain two different versions of qpopper? Could we just have the current version as popper and use the original names for things? Is there a reason the qpopper binary is stored in /usr/local/libexec where the default qpopper installation is in /usr/local/sbin? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
package db information
I was just looking at starting to writing a Perl module to read it. For the most part it is easy enough to make out what everything is, but does any one know if there is any official documentation or the like actually describing it? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [maintainer] ghostscript-gpl - jasper
Hi, Running jasper configure script... checking build system type... configure: error: cannot guess build type; you must specify one configure: error: jasper configure script failed This seems your configure program failed to guess your system type. Please send the result of work/ghostscript-8.62/jasper/acaux/config.guess script as well as the contents of work/ghostscript-8.62/jasper/config.log file. -- Hiroto Kagotani [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: net-snmp5.4.x unusable, PR times out, what should I do next?
On Fri, 2008-05-23 at 13:17 +0200, Helmut Schneider wrote: Hi, I don't blame anyone, I'm sure all of the maintainers have a lot of things to. Rather I would like to know what I should do/can do next. As I'm using If it makes you feel any better, we can get it to segfault with SIGHUP at the top of the hour. (Although we realized that we don't need to HUP it from newsyslog since we're using syslog(3)) OpenBSD's snmpd(8) has HOST-RESOURCES, UCD-MIB, PF-MIB (well, Sensors), and DISKIO-MIB support, supposedly. ~BAS IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
