[Bug 1529923] [NEW] Save button disabled/gray when importing unified openvpn config file
Public bug reported: Reopening https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/1294899 which expired as it should be fixed and not worked around. Importing a unified openvpn configuration file where the CA certificate is embedded between tags fails: $ sudo nm-connection-editor (nm-connection-editor:7624): GLib-WARNING **: (/build/buildd/glib2.0-2.40.2/./glib/gerror.c:381):g_error_new_valist: runtime check failed: (domain != 0) (nm-connection-editor:7624): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: does not look like a Cisco Compatible VPN (vpnc) VPN connection (parse failed) ** (nm-connection-editor:7624): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:7624): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:7624): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:7624): WARNING **: Invalid setting VPN: ca $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 Examples of a unified openvpn file are available at https://usenetserver.com/vpn/#setup -> https://usenetserver.com/vpn/software/configs/ See https://gist.github.com/trovao/18e428b5a758df24455b for a shell script which creates a unified openvpn file from separate cacert, client_cert, client_key, and tls-auth certificate files. ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529923 Title: Save button disabled/gray when importing unified openvpn config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1529923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315725] [NEW] openjdk-7-jre cannot open Tyan S5512 IPMI remote console
Public bug reported: DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS Firefox 29.0 as included with Ubuntu 14. net.sourceforge.jnlp.LaunchException: Fatal: Read Error: Could not read or parse the JNLP file. You can try to download this file manually and send it as bug report to IcedTea-Web team. at net.sourceforge.jnlp.Launcher.fromUrl(Launcher.java:490) at net.sourceforge.jnlp.Launcher.launch(Launcher.java:285) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:246) at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:58) at java.security.AccessController.doPrivileged(Native Method) at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:213) Caused by: net.sourceforge.jnlp.ParseException: Invalid XML document syntax. at net.sourceforge.jnlp.XMLParser.getRootNode(XmlParser.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at net.sourceforge.jnlp.Parser.getRootNode(Parser.java:1289) at net.sourceforge.jnlp.JNLPFile.parse(JNLPFile.java:751) at net.sourceforge.jnlp.JNLPFile.init(JNLPFile.java:229) at net.sourceforge.jnlp.JNLPFile.init(JNLPFile.java:211) at net.sourceforge.jnlp.JNLPFile.init(JNLPFile.java:196) at net.sourceforge.jnlp.JNLPFile.init(JNLPFile.java:182) at net.sourceforge.jnlp.Launcher.fromUrl(Launcher.java:459) ... 5 more Caused by: net.sourceforge.nanoxml.XMLParseException: XML Parse Exception during parsing of a jnlp element at line 52: Expected: / at net.sourceforge.nanoxml.XMLElement.expectedInput(XMLElement.java:1116) at net.sourceforge.nanoxml.XMLElement.scanElement(XMLElement.java:976) at net.sourceforge.nanoxml.XMLElement.scanElement(XMLElement.java:957) at net.sourceforge.nanoxml.XMLElement.scanElement(XMLElement.java:957) at net.sourceforge.nanoxml.XMLElement.parseFromReader(XMLElement.java:502) at net.sourceforge.nanoxml.XMLElement.parseFromReader(XMLElement.java:454) at net.sourceforge.jnlp.XMLParser.getRootNode(XmlParser.java:113) ... 16 more openjdk-7-jre: Installed: 7u55-2.4.7-1ubuntu1 Candidate: 7u55-2.4.7-1ubuntu1 Version table: *** 7u55-2.4.7-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7u51-2.4.6-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ** Affects: openjdk-7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315725 Title: openjdk-7-jre cannot open Tyan S5512 IPMI remote console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1315725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982436] Re: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory
Another short term fix (in case there are any other library packages that also install to that directory): sudo -s echo /usr/lib/i486-linux-gnu /etc/ld.so.conf.d/librtmp0.conf ldconfig exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982436 Title: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/982436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438226] Re: apt-get install plucker fails assertion.
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/32622819/Dependencies.txt -- apt-get install plucker fails assertion. https://bugs.launchpad.net/bugs/438226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 438226] [NEW] apt-get install plucker fails assertion.
Public bug reported: Binary package hint: plucker $ sudo apt-get install plucker-desktop [sudo] password for rcpao: Reading package lists... Done Building dependency tree Reading state information... Done E: Couldn't find package plucker-desktop rc...@bun:~/News/Pan/dan brown$ sudo apt-get install plucker Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: pilot-link The following NEW packages will be installed: plucker 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 469kB of archives. After this operation, 1327kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com jaunty/universe plucker 1.8-29 [469kB] Fetched 469kB in 3s (121kB/s) Selecting previously deselected package plucker. (Reading database ... 216956 files and directories currently installed.) Unpacking plucker (from .../plucker_1.8-29_amd64.deb) ... Processing triggers for man-db ... Setting up plucker (1.8-29) ... /usr/lib/python2.6/dist-packages/PyPlucker/PluckerDocs.py:2269: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert(len(dataval) == (nwords * 2), Invalid length calculation in marshalling of PluckerMetadataDocument) /usr/lib/python2.6/dist-packages/PyPlucker/PluckerDocs.py:2278: SyntaxWarning: assertion is always true, perhaps remove parentheses? assert(len(dataval) == (nwords * 2), Invalid length calculation in marshalling of PluckerMetadataDocument) $ lsb_release -rd Description:Ubuntu 9.04 Release:9.04 I have not installed pilot-link (yet). It should not hit any assertions either way. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: plucker 1.8-29 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plucker Uname: Linux 2.6.28-15-generic x86_64 ** Affects: plucker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- apt-get install plucker fails assertion. https://bugs.launchpad.net/bugs/438226 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240249] Re: Mailman does not display Unicode member names correctly.
Yes, the problem still persists. I can enter member name 鮑致同 and submit from Membership Management Membership List. The returned page will then show #39825;#33268;#21516;. I am not using the patch currently. The problem persists in the Membership List anyway. If it gets fixed there, it should be fixed after the patch is applied. Mailman version 2.1.9 in DISTRIB_DESCRIPTION=Ubuntu 8.04.3 LTS. All dist-upgrades to date have been applied. -- Mailman does not display Unicode member names correctly. https://bugs.launchpad.net/bugs/240249 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 240249] Re: Mailman does not display Unicode member names correctly.
Yes, the problem still persists. I can enter member name 鮑致同 and submit from Membership Management Membership List. The returned page will then show #39825;#33268;#21516;. I am not using the patch currently. The problem persists in the Membership List anyway. If it gets fixed there, it should be fixed after the patch is applied. Mailman version 2.1.9 in DISTRIB_DESCRIPTION=Ubuntu 8.04.3 LTS. All dist-upgrades to date have been applied. -- Mailman does not display Unicode member names correctly. https://bugs.launchpad.net/bugs/240249 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
Sorry, those two logs are from the wrong system. Is it possible to attach more than one file at a time? ** Attachment added: dmesg http://launchpadlibrarian.net/17921767/dmesg -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
** Attachment added: udev http://launchpadlibrarian.net/17921789/udev -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
** Attachment added: lsusb -v http://launchpadlibrarian.net/17921801/lsusb-v.txt -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
'lsusb -v' will show a unique serial number (iSerial) for each device. I have three SIIG USB Serial adapters. Bus 002 Device 004: ID 0b39:0421 Omnidirectional Control Technology, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0b39 Omnidirectional Control Technology, Inc. idProduct 0x0421 bcdDevice2.00 iManufacturer 1 Generic iProduct2 USB to Serial Converter iSerial 3 OCBAKZ7N ... Bus 002 Device 003: ID 0b39:0421 Omnidirectional Control Technology, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0b39 Omnidirectional Control Technology, Inc. idProduct 0x0421 bcdDevice2.00 iManufacturer 1 Generic iProduct2 USB to Serial converter iSerial 3 OCBQH84W ... Bus 001 Device 008: ID 0b39:0421 Omnidirectional Control Technology, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0b39 Omnidirectional Control Technology, Inc. idProduct 0x0421 bcdDevice2.00 iManufacturer 1 Generic iProduct2 USB to Serial Converter iSerial 3 OCBPJ9HM Currently, after a reboot, only one will be assigned ttyUSB0, the other two will not be assigned anything. I have to manually unplug all three, then plug them using the order I want from 0 to 2. I can live with either a method to fix ttyUSB# to either the iSerial (preferred) and/or the Bus+Device number. -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
Before touching /etc/udev/rules.d, only one USB Serial adapter would be
assigned ttyUSB0. The others would not be mapped in.
After adding the udev rules below, they are now working as expected, but
the computer required a power cycle or the USB Serial adapters required
being unplugged and replugged back in before they would communicate with
their serial devices.
The following was helpful.
http://www.reactivated.net/writing_udev_rules.html#udevinfo
Thank you for the help.
# /etc/udev/rules.d/50-local.rules
# /dev/ttyUSB0
SUBSYSTEMS==usb, ATTRS{manufacturer}==Generic, ATTRS{product}==USB to
Serial Converter, ATTRS{serial}==OCBPJ9HM, KERNEL==ttyUSB[0123],
SYMLINK+=powercom
# /dev/ttyUSB1
SUBSYSTEMS==usb, ATTRS{manufacturer}==Generic, ATTRS{product}==USB to
Serial Converter, ATTRS{serial}==OCBAKZ7N, KERNEL==ttyUSB[0123],
SYMLINK+=smartups, MODE=0660, GROUP=nut
# /dev/ttyUSB2
SUBSYSTEMS==usb, ATTRS{manufacturer}==Generic, ATTRS{product}==USB to
Serial converter, ATTRS{serial}==OCBQH84W, KERNEL==ttyUSB[0123],
SYMLINK+=usrobotics
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
** Attachment added: The three USB Serial adapters are plugged in, but only two are detected. http://launchpadlibrarian.net/17898314/udev -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107208] Re: Two USB serial adapters get different /dev/ttyUSBn names after reboot
The three USB Serial adapters are plugged in, but only two are detected. The previous attachement is /var/log/udev. ** Attachment added: /var/log/dmesg http://launchpadlibrarian.net/17898329/dmesg -- Two USB serial adapters get different /dev/ttyUSBn names after reboot https://bugs.launchpad.net/bugs/107208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239025] Re: usbhid-ups not behaving with Tripplite UPS
Chuck Short: dget http://launchpadlibrarian.net/15690206/nut_2.2.1-2.1ubuntu7.2~ppa1.dsc does not get the orig.tar.gz or diff.gz correctly. Of course, it's not really a repository, so the directory paths being different from the *.dsc file may be unavoidable. [EMAIL PROTECTED]:~/pub/inet/Linux/networkupstools.org$ sh 01-dget.sh dget: retrieving http://launchpadlibrarian.net/15690206/nut_2.2.1-2.1ubuntu7.2~ppa1.dsc % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 1023 100 10230 0 2687 0 --:--:-- --:--:-- --:--:-- 0 dget: retrieving http://launchpadlibrarian.net/15690206/nut_2.2.1.orig.tar.gz % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 dget: curl nut_2.2.1.orig.tar.gz http://launchpadlibrarian.net/15690206/nut_2.2.1.orig.tar.gz failed [EMAIL PROTECTED]:~/pub/inet/Linux/networkupstools.org$ I successfully downloaded nut_2.2.1-2.1ubuntu7.2~ppa1.dsc, the orig.tar.gz, and the diff.gz from https://launchpad.net/~zulcss/+archive manually. dpkg-source -x *.dsc cd nut-2.2.1 dpkg-buildpackage -rfakeroot cd .. successfully built nut-2.2.1/drivers/usbhid-ups. Copying it into /lib/nut/ and replacing the existing file from Ubuntu 8.04.1, works: ... Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, Type: Feature, ReportID: 0x17, Offset: 0, Size: 16, Value: 65535.00 Detected a UPS: Tripp Lite /TRIPP LITE UPS upsdrv_initinfo... upsdrv_updateinfo... Quick update... upsdrv_updateinfo... Quick update... upsdrv_updateinfo... ... [EMAIL PROTECTED]:/etc/nut# upsc [EMAIL PROTECTED] ups.status OL CHRG [EMAIL PROTECTED]:/etc/nut# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/nut# Installing the nut and nut-cgi*_i386.deb from my recompile also works. Bottom line: I can say your PPA fixes the infinite loop problem on this UPS. -- usbhid-ups not behaving with Tripplite UPS https://bugs.launchpad.net/bugs/239025 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 239025] Re: usbhid-ups not behaving with Tripplite UPS
Chuck Short: One thing I noticed with your PPA is that the battery.charge alternates between 100 and 0 quite often: upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 -- usbhid-ups not behaving with Tripplite UPS https://bugs.launchpad.net/bugs/239025 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 239025] Re: usbhid-ups not behaving with Tripplite UPS
Chuck Short: dget http://launchpadlibrarian.net/15690206/nut_2.2.1-2.1ubuntu7.2~ppa1.dsc does not get the orig.tar.gz or diff.gz correctly. Of course, it's not really a repository, so the directory paths being different from the *.dsc file may be unavoidable. [EMAIL PROTECTED]:~/pub/inet/Linux/networkupstools.org$ sh 01-dget.sh dget: retrieving http://launchpadlibrarian.net/15690206/nut_2.2.1-2.1ubuntu7.2~ppa1.dsc % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 1023 100 10230 0 2687 0 --:--:-- --:--:-- --:--:-- 0 dget: retrieving http://launchpadlibrarian.net/15690206/nut_2.2.1.orig.tar.gz % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 dget: curl nut_2.2.1.orig.tar.gz http://launchpadlibrarian.net/15690206/nut_2.2.1.orig.tar.gz failed [EMAIL PROTECTED]:~/pub/inet/Linux/networkupstools.org$ I successfully downloaded nut_2.2.1-2.1ubuntu7.2~ppa1.dsc, the orig.tar.gz, and the diff.gz from https://launchpad.net/~zulcss/+archive manually. dpkg-source -x *.dsc cd nut-2.2.1 dpkg-buildpackage -rfakeroot cd .. successfully built nut-2.2.1/drivers/usbhid-ups. Copying it into /lib/nut/ and replacing the existing file from Ubuntu 8.04.1, works: ... Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, Type: Feature, ReportID: 0x17, Offset: 0, Size: 16, Value: 65535.00 Detected a UPS: Tripp Lite /TRIPP LITE UPS upsdrv_initinfo... upsdrv_updateinfo... Quick update... upsdrv_updateinfo... Quick update... upsdrv_updateinfo... ... [EMAIL PROTECTED]:/etc/nut# upsc [EMAIL PROTECTED] ups.status OL CHRG [EMAIL PROTECTED]:/etc/nut# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/nut# Installing the nut and nut-cgi*_i386.deb from my recompile also works. Bottom line: I can say your PPA fixes the infinite loop problem on this UPS. -- usbhid-ups not behaving with Tripplite UPS https://bugs.launchpad.net/bugs/239025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 239025] Re: usbhid-ups not behaving with Tripplite UPS
Chuck Short: One thing I noticed with your PPA is that the battery.charge alternates between 100 and 0 quite often: upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 100 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 [EMAIL PROTECTED]:/etc/init.d# upsc [EMAIL PROTECTED] battery.charge 0 -- usbhid-ups not behaving with Tripplite UPS https://bugs.launchpad.net/bugs/239025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203195] Re: nautilus does not remove file '_x' from trash
[EMAIL PROTECTED]:~/job/clx$ dpkg-query -s gvfs Package: gvfs Status: install ok installed Priority: optional Section: libs Installed-Size: 1908 Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Architecture: i386 Version: 0.2.5-0ubuntu1 was able to successfully empty _files from my trash can. -- nautilus does not remove file '_x' from trash https://bugs.launchpad.net/bugs/203195 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234688] Re: Plug in USB Drive - Does not automount.
I get a dialog box now (after lots of updates lately): Error The panel encountered a problem while loading OAFIID:GNOM[E_MultiLoadApplet. Do you want to delete the applet from your configuration? [Don't Delete] [Delete] Attached is the hal.log. ** Attachment added: hal.log http://launchpadlibrarian.net/15693762/hal.log -- Plug in USB Drive - Does not automount. https://bugs.launchpad.net/bugs/234688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 240249] [NEW] Mailman does not display Unicode member names correctly.
Public bug reported: Binary package hint: mailman Upgrading from Ubuntu 7.04 to 7.10 to 8.04 broke the displaying of Mailman's member names. Chinese names such as 鮑震 display instead as #39825;#38663;. It used to work. I'm talking about the List's administrative interface Membership Management Membership List member name field. After applying the [ 932383 ] Include FullName in roster views patch at http://sourceforge.net/tracker/?func=detailaid=932383group_id=103atid=300103, I can see the member name is displayed correctly in the roster visible to list members from [Visit Subscriber List] button. The Membership List member field name is still displayed incorrectly however. ** Affects: mailman (Ubuntu) Importance: Undecided Status: New -- Mailman does not display Unicode member names correctly. https://bugs.launchpad.net/bugs/240249 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234688] Re: Plug in USB Drive - Does not automount.
Just to throw another wrench into the pile, a generic MicroSD USB reader with SanDisk 2GB MicroSD does automount just fine in the same laptop and a desktop. [ 2668.560786] usb 2-1: new full speed USB device using uhci_hcd and address 6 [ 2668.721530] usb 2-1: configuration #1 chosen from 1 choice [ 4004.729035] scsi6 : SCSI emulation for USB Mass Storage devices [ 4004.734655] usb-storage: device found at 6 [ 4004.734675] usb-storage: waiting for device to settle before scanning [ 4010.200087] usb-storage: device scan complete [ 4010.205958] scsi 6:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0 [ 4010.393306] sd 6:0:0:0: [sdb] 3932160 512-byte hardware sectors (2013 MB) [ 4010.400480] sd 6:0:0:0: [sdb] Write Protect is off [ 4010.400499] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 4010.400510] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 4010.415425] sd 6:0:0:0: [sdb] 3932160 512-byte hardware sectors (2013 MB) [ 4010.422654] sd 6:0:0:0: [sdb] Write Protect is off [ 4010.422678] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00 [ 4010.422690] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 4010.422745] sdb: sdb1 [ 4010.432149] sd 6:0:0:0: [sdb] Attached SCSI removable disk [ 4010.432486] sd 6:0:0:0: Attached scsi generic sg2 type 0 [EMAIL PROTECTED]:~$ ls /media/ cdrom/ .hal-mtab USD006-2GB/ cdrom0/ .hal-mtab-lock USD006-2GB is the volume name of the MicroSD. All the files are under there. Nautilus popped up a window showing them just fine. -- Plug in USB Drive - Does not automount. https://bugs.launchpad.net/bugs/234688 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237669] Re: trash cannot empty _copy_2.nzb
I have no idea why they do not get deleted while everything else around it gets deleted. There is no error message displayed (no pop ups anyway). A user applet should not be able to syslog, so I didn't check /var/log for anything. Since I can delete them from the terminal from my user account (no need to sudo), it's not a permission problem. It may be due to the fact that I use /.Trash-1000/ for my trash directory. I have a couple of different partitions I use, and I believe I needed to do this to be able to have the trash can work for non-home partitions. So for a test, I created _underline_file_from_Desktop.txt on my Desktop (home partition), _underline_file.txt and deleteme.txt in a non-home partition. Deleting them all in Nautilus will display all three in Trash. Clicking Empty Trash button, two files are erased; however, _underline_file.txt remains in the Trash. No errors occur. I suspect it has something to do with the leading _ in the file name to be emptied. [EMAIL PROTECTED]:/.Trash-1000$ ls -R .: files/ info/ ./files: deleteme.txt _underline_file.txt ./info: deleteme.txt.trashinfo _underline_file.txt.trashinfo [You will note that _underline_file_from_Desktop.txt is not here, I believe it is in ~/.local/share/Trash, but I did not specifically check since it is working. [Empty Trash] button is clicked at this point. [EMAIL PROTECTED]:/.Trash-1000$ ls -R .: files/ info/ ./files: _underline_file.txt ./info: _underline_file.txt.trashinfo [EMAIL PROTECTED]:/.Trash-1000$ -- trash cannot empty _copy_2.nzb https://bugs.launchpad.net/bugs/237669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237669] [NEW] trash cannot empty _copy_2.nzb
Public bug reported: Pan newsreader saves _copy_2.nzb to my directory. I use Nautilus to delete it. The file is visible in my trash can; however, I cannot empty it. I can empty everything else except that file from the trash can using the applet. I can manually delete it from bash. [EMAIL PROTECTED]:/.Trash-1000$ rm files/_copy_2.nzb info/_copy_2.nzb.trashinfo Description:Ubuntu 8.04 Release:8.04 ** Affects: ubuntu Importance: Undecided Status: New -- trash cannot empty _copy_2.nzb https://bugs.launchpad.net/bugs/237669 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235254] [NEW] a: should allow IPv4 addresses
Public bug reported: Binary package hint: postfix-policyd-spf-perl May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: connect from sn16.seed.net.tw[139 .175.54.16] May 12 00:38:47 rolly-dmz policyd-spf[3818]: SPF fail: REMOTEIP=139.175.54.16 HELO=seed.net.tw SENDER=[EMAIL PROTECTED] RECIPIENT=[EMAIL PROTECTED] QUE UEID= REASON=SPF Permanent Error: Use the ip4 mechanism for ip4 addresses: a: 210.68.96.50 May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: NOQUEUE: reject: RCPT from sn16.s eed.net.tw[139.175.54.16]: 550 5.7.1 [EMAIL PROTECTED]: Recipient address reject ed: SPF Reports: SPF Permanent Error: Use the ip4 mechanism for ip4 addresses: a :210.68.96.50; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo =seed.net.tw May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: disconnect from sn16.seed.net.tw[ 139.175.54.16] Using the SPF Wizard at http://old.openspf.org/wizard.html?mydomain=seed.net.twsubmit=Go%21 The SPF record: v=spf1 a:210.68.96.50 a:210.68.96.51 ip4:139.175.54.0/24 ?all can be explained as: [v=spf1]v=spf1 This identifies the TXT record as an SPF string. [a:]a:210.68.96.50 210.68.96.50 is also allowed to send mail from seed.net.tw. [a:]a:210.68.96.51 210.68.96.51 is also allowed to send mail from seed.net.tw. [ip4:] ip4:139.175.54.0/24 Every host in the range 139.175.54.0-139.175.54.255 is allowed to send mail from seed.net.tw. [all] ?allSPF queries that do not match any other mechanism will return neutral. Messages that are not sent from an approved server should still be accepted as if the SPF record did not exist. Note the a: is allowed to be an IP address. It is not an error. And, it is marked as a soft fail (?all), so it should have allowed the e-mail to pass through and not reject. ** Affects: postfix-policyd-spf-perl (Ubuntu) Importance: Undecided Status: New -- a: should allow IPv4 addresses https://bugs.launchpad.net/bugs/235254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235254] Re: a: should allow IPv4 addresses
** Description changed: - Binary package hint: postfix-policyd-spf-perl + Binary package hint: python-policyd-spf May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: connect from sn16.seed.net.tw[139 .175.54.16] May 12 00:38:47 rolly-dmz policyd-spf[3818]: SPF fail: REMOTEIP=139.175.54.16 HELO=seed.net.tw SENDER=[EMAIL PROTECTED] RECIPIENT=[EMAIL PROTECTED] QUE UEID= REASON=SPF Permanent Error: Use the ip4 mechanism for ip4 addresses: a: 210.68.96.50 May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: NOQUEUE: reject: RCPT from sn16.s eed.net.tw[139.175.54.16]: 550 5.7.1 [EMAIL PROTECTED]: Recipient address reject ed: SPF Reports: SPF Permanent Error: Use the ip4 mechanism for ip4 addresses: a :210.68.96.50; from=[EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo =seed.net.tw May 12 00:38:47 rolly-dmz postfix/smtpd[3808]: disconnect from sn16.seed.net.tw[ 139.175.54.16] Using the SPF Wizard at http://old.openspf.org/wizard.html?mydomain=seed.net.twsubmit=Go%21 The SPF record: v=spf1 a:210.68.96.50 a:210.68.96.51 ip4:139.175.54.0/24 ?all can be explained as: [v=spf1] v=spf1 This identifies the TXT record as an SPF string. [a:] a:210.68.96.50 210.68.96.50 is also allowed to send mail from seed.net.tw. [a:] a:210.68.96.51 210.68.96.51 is also allowed to send mail from seed.net.tw. [ip4:]ip4:139.175.54.0/24 Every host in the range 139.175.54.0-139.175.54.255 is allowed to send mail from seed.net.tw. [all] ?allSPF queries that do not match any other mechanism will return neutral. Messages that are not sent from an approved server should still be accepted as if the SPF record did not exist. - Note the a: is allowed to be an IP address. It is not an error. And, - it is marked as a soft fail (?all), so it should have allowed the e-mail - to pass through and not reject. + Note the a: is allowed to be an IP address. It is not marked as an + error. And, the SPF record is marked as a soft fail (?all), so it + should have allowed the e-mail to pass through and not reject. + + + Package and Version information: + + [EMAIL PROTECTED]:/var/log# dpkg --get-selections|grep spf + libmail-spf-perl install + postfix-policyd-spf-perl install + python-policyd-spfinstall + python-spfinstall + + [EMAIL PROTECTED]:/etc/postfix# grep spf * + main.cf:check_policy_service unix:private/policy-spf, + main.cf:spf-policyd_time_limit = 3600s + master.cf:policy-spf unix - n n - 0 spawn + master.cf: user=nobody argv=/usr/bin/policyd-spf + + [EMAIL PROTECTED]:/etc/postfix# more /usr/bin/policyd-spf + #!/usr/bin/python + # + # Check SPF results and provide recommended action back to Postfix. + # + # Tumgreyspf source + # Copyright (c) 2004-2005, Sean Reifschneider, tummy.com, ltd. + # [EMAIL PROTECTED] + # + # pypolicyd-spf + # Copyright (c) 2007, Scott Kitterman [EMAIL PROTECTED] + + [EMAIL PROTECTED]:/etc/postfix# dpkg-query --show python-policyd-spf + python-policyd-spf0.2-0ubuntu2 -- a: should allow IPv4 addresses https://bugs.launchpad.net/bugs/235254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235254] Re: a: should allow IPv4 addresses
Thank you for your prompt reply. I agree with your assessment that a: does not allow IPv4. I will follow up with seed.net.tw. FYI: The wizard at http://www.openspf.org/Project_Overview will forward to http://old.openspf.org/wizard.html?mydomain=seed.net.twsubmit=Go%21. -- a: should allow IPv4 addresses https://bugs.launchpad.net/bugs/235254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189301] [NEW] gfax sort by column other than Sender does not work.
Public bug reported: Binary package hint: gfax If you have a list of faxes in the Received Facsimilies, you can only sort by Sender. Clicking on Status, Page, Arrived, or Filename only results in changing the Sender sort order. ** Affects: gfax (Ubuntu) Importance: Undecided Status: New -- gfax sort by column other than Sender does not work. https://bugs.launchpad.net/bugs/189301 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187357] Re: RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels.
You are correct. Adding :port to Computer: field works. I did not see it in man tsclient. Thank you. -- RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels. https://bugs.launchpad.net/bugs/187357 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187357] Re: RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels.
Then this now becomes a bug report. Using rdesktop as below works perfectly: [EMAIL PROTECTED]:~$ rdesktop -g 1024x768 localhost:23389 Autoselected keyboard map en-us WARNING: Remote desktop does not support colour depth 24; falling back to 16 [EMAIL PROTECTED]:~$ Using tsclient 0.148 as it comes with Ubuntu 7.10 does not work (see attached screenshot): ERROR: connect: Connection refused. ** Attachment added: Screenshot-Terminal Server Client.png http://launchpadlibrarian.net/11702829/Screenshot-Terminal%20Server%20Client.png -- RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels. https://bugs.launchpad.net/bugs/187357 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187357] [NEW] RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels.
Public bug reported: Binary package hint: tsclient rdesktop allows specifying RdpServerNameOrAddress:port, tsclient should also allow the port to be specified. If no one wants to change the GUI, that's fine, but at least add support for changing the port in the ~/.tsclient/*.rdp file and calling rdesktop with the specified port number. As it currently stands, I can only SSH tunnel to a single RDP server at a time using tsclient (due to the fixed 3389 port) then use rdesktop directly for the other non-3389 ports. ** Affects: tsclient (Ubuntu) Importance: Undecided Status: New -- RFE: tsclient 1.48 needs option to change from default port 3389 to support SSH tunnels. https://bugs.launchpad.net/bugs/187357 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 187363] [NEW] tsclient 1.48 select a saved profile should update fields immediately
Public bug reported: Binary package hint: tsclient It would seem the combo-list-menu just above the About button does not update the fields above when the *.rdp is selected. Once I select a *.rdp in the box, the fields above should immediately change to reflect the contents of the *.rdp. I have to click the Open button, select the *.rdp file, then I can see the fields updated. ** Affects: tsclient (Ubuntu) Importance: Undecided Status: New -- tsclient 1.48 select a saved profile should update fields immediately https://bugs.launchpad.net/bugs/187363 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146253] Re: mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese
Looking at the debian/rules shows CONFIGURE_LINE=...--with-extra- charsets=all so my problem lies elsewhere. ** Changed in: mnogosearch (Ubuntu) Status: New = Invalid -- mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese https://bugs.launchpad.net/bugs/146253 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146253] Re: mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese
My solution was to change /etc/mnogosearch/search.htm from LocalCharset iso-8859-1 BrowserCharset iso-8859-1 to LocalCharset utf-8 BrowserCharset utf-8 -- mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese https://bugs.launchpad.net/bugs/146253 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146253] mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese
Public bug reported: Ubuntu 7.04 Feisty Fawn with indexer from mnogosearch-3.2.37-mysql is not compiled with '--with-extra-charsets=all' to support Korean, Chinese, or Japanese. Search some Chinese characters such as 鮑致同 at http://www.paonet.org/ for example. The results are empty. From http://www.mnogosearch.org/doc/msearch-changelog.html, the reason the upstream removed support by default was to reduce binary size. If binary size is such an issue that a pre-built binary --with-extra- charsets=all cannot be included by default, I suggest an alternative pre-built binary package should at least be made available in the package repositories next to the default package. ** Affects: mnogosearch (Ubuntu) Importance: Undecided Status: New -- mnogosearch needs --with-extra-charsets=all to support Korean, Chinese, Japanese https://bugs.launchpad.net/bugs/146253 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
