[Bug 608182] Re: problems with ups (mge pulsar es 8+)
I'm running now manually a script after reboot to start nut, because scripts run during boot can't start nut, don't know why -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 609055] Re: problems with using parallel port
now I've changed the rights for /dev/parport0 with chmod to 777 and run qemu out of the terminal, and now it works fine -- problems with using parallel port https://bugs.launchpad.net/bugs/609055 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 608182] Re: problems with ups (mge pulsar es 8+)
/var/log/boot.log says nothing about failed drivers or so after changing /etc/init.d/nut and rebooting there is no /tmp/mge-utalk.log, I've tried it several times regards wolfgang -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
there are no results for mge-utalk in /var/log/messages if I don't start nut manually with /etc/init.d/nut start, I always get the following message: Broadcast Message from n...@l4 (somewhere) at 10:40 ... UPS mge...@localhost is unavailable so, I think, nut starts not completly, or nut starts and the driver doesn't start, or something like this wolfgang -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 478527] Re: Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed
oh I'm sorry, I should have read what's really meant by confirmed and incomplete ;) ** Changed in: virt-manager (Ubuntu) Status: Incomplete => Confirmed -- Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed https://bugs.launchpad.net/bugs/478527 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 478527] Re: Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed
** Changed in: virt-manager (Ubuntu) Status: Confirmed => Incomplete -- Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed https://bugs.launchpad.net/bugs/478527 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 478527] Re: Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed
I also have exactly the same problem: I'm running a win xp 64 guest-system on a ubuntu 10.04 server I had problems with adding a parallel port to the vm and so had to do several reboots, and suddenly rebooting wasn't possible anymore does anyone know, what to do? regards wolfgang -- Unable to create a new VM when selecting PXE boot and kvm-pxe is not installed https://bugs.launchpad.net/bugs/478527 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 608182] Re: problems with ups (mge pulsar es 8+)
I think I've detected another problem: If I start NUT-Monitor immediately after running /etc/init.d/nut start it starts not correctly, I can't do anything, so I have to reboot the system -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
nut monitor works now, I forgot to reboot thank you very much! -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
I still get the same outputs with NUT-Monitor. my nut.conf looks now the following: MODE=standalone ps -efl | grep mge-utalk: 0 S root 2066 2002 0 80 0 - 1907 pipe_w 08:37 pts/000:00:00 grep --color=auto mge-utalk upsc mgeups: Error: Driver not connected ls -la /var/run/nut: insgesamt 8 drwxrwx--- 2 root nut 80 2010-07-26 08:32 . drwxr-xr-x 22 root root 760 2010-07-26 08:32 .. -rw-r--r-- 1 nut nut5 2010-07-26 08:32 upsd.pid -rw-r--r-- 1 root root 5 2010-07-26 08:32 upsmon.pid regards, Wolfgang -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 609055] Re: problems with using parallel port
What do you mean with "confirmed"? Maybe the problem with the parallel port is configuration problem, but that I can't boot the vm (as I've written in post #4) is at least quite strange. :( Can you help me, please? ;) -- problems with using parallel port https://bugs.launchpad.net/bugs/609055 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 609055] Re: problems with using parallel port
oops, I'm sorry, at the moment the vm doesn't want to boot at all, although
I've removed the serial port from it
but this may be also a bug or strange behavior ;)
P.S.: now I get the following output:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: Connection refused
regards wolfgang
--
problems with using parallel port
https://bugs.launchpad.net/bugs/609055
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 609055] Re: problems with using parallel port
this is the output after starting and before getting the error-message (I fear this isn't the complete output of dmseg, but my terminal doesn't want to give me more :( ): [0.363348] system 00:06: iomem range 0xfed2-0xfed3 has been reserved [0.363350] system 00:06: iomem range 0xfed4-0xfed8 has been reserved [0.363354] system 00:09: iomem range 0xffc0-0xffef has been reserved [0.363358] system 00:0a: iomem range 0xfec0-0xfec00fff could not be reserved [0.363360] system 00:0a: iomem range 0xfee0-0xfee00fff has been reserved [0.363364] system 00:0c: ioport range 0xa00-0xadf has been reserved [0.363365] system 00:0c: ioport range 0xae0-0xaef has been reserved [0.363371] system 00:0d: iomem range 0xe000-0xefff has been reserved [0.363375] system 00:0e: iomem range 0x0-0x9 could not be reserved [0.363376] system 00:0e: iomem range 0xc-0xc has been reserved [0.363378] system 00:0e: iomem range 0xe-0xf could not be reserved [0.363380] system 00:0e: iomem range 0x10-0xbddf could not be reserved [0.363382] system 00:0e: iomem range 0xfed9-0x could not be reserved [0.368054] pci :00:1c.0: PCI bridge, secondary bus :01 [0.368057] pci :00:1c.0: IO window: 0xb000-0xbfff [0.368060] pci :00:1c.0: MEM window: 0xc000-0xc01f [0.368064] pci :00:1c.0: PREFETCH window: 0x00c020-0x00c03f [0.368068] pci :00:1c.1: PCI bridge, secondary bus :02 [0.368070] pci :00:1c.1: IO window: 0x1000-0x1fff [0.368074] pci :00:1c.1: MEM window: 0xfe90-0xfe9f [0.368077] pci :00:1c.1: PREFETCH window: 0x00c040-0x00c05f [0.368081] pci :00:1c.3: PCI bridge, secondary bus :03 [0.368083] pci :00:1c.3: IO window: 0xc000-0xcfff [0.368087] pci :00:1c.3: MEM window: 0xfea0-0xfeaf [0.368090] pci :00:1c.3: PREFETCH window: 0x00c060-0x00c07f [0.368094] pci :00:1c.5: PCI bridge, secondary bus :04 [0.368096] pci :00:1c.5: IO window: 0xd000-0xdfff [0.368100] pci :00:1c.5: MEM window: 0xfeb0-0xfebf [0.368103] pci :00:1c.5: PREFETCH window: 0x00fdf0-0x00fdff [0.368107] pci :00:1e.0: PCI bridge, secondary bus :05 [0.368109] pci :00:1e.0: IO window: 0xe000-0xefff [0.368113] pci :00:1e.0: MEM window: disabled [0.368115] pci :00:1e.0: PREFETCH window: disabled [0.368124] pci :00:1c.0: enabling device (0105 -> 0107) [0.368128] alloc irq_desc for 17 on node -1 [0.368130] alloc kstat_irqs on node -1 [0.368134] pci :00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [0.368138] pci :00:1c.0: setting latency timer to 64 [0.368144] pci :00:1c.1: enabling device (0106 -> 0107) [0.368146] alloc irq_desc for 16 on node -1 [0.368147] alloc kstat_irqs on node -1 [0.368149] pci :00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16 [0.368152] pci :00:1c.1: setting latency timer to 64 [0.368157] alloc irq_desc for 19 on node -1 [0.368158] alloc kstat_irqs on node -1 [0.368161] pci :00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19 [0.368163] pci :00:1c.3: setting latency timer to 64 [0.368169] pci :00:1c.5: PCI INT B -> GSI 16 (level, low) -> IRQ 16 [0.368172] pci :00:1c.5: setting latency timer to 64 [0.368176] pci :00:1e.0: setting latency timer to 64 [0.368179] pci_bus :00: resource 0 io: [0x00-0x] [0.368181] pci_bus :00: resource 1 mem: [0x00-0x] [0.368183] pci_bus :01: resource 0 io: [0xb000-0xbfff] [0.368185] pci_bus :01: resource 1 mem: [0xc000-0xc01f] [0.368186] pci_bus :01: resource 2 pref mem [0xc020-0xc03f] [0.368188] pci_bus :02: resource 0 io: [0x1000-0x1fff] [0.368189] pci_bus :02: resource 1 mem: [0xfe90-0xfe9f] [0.368191] pci_bus :02: resource 2 pref mem [0xc040-0xc05f] [0.368193] pci_bus :03: resource 0 io: [0xc000-0xcfff] [0.368194] pci_bus :03: resource 1 mem: [0xfea0-0xfeaf] [0.368196] pci_bus :03: resource 2 pref mem [0xc060-0xc07f] [0.368198] pci_bus :04: resource 0 io: [0xd000-0xdfff] [0.368199] pci_bus :04: resource 1 mem: [0xfeb0-0xfebf] [0.368201] pci_bus :04: resource 2 pref mem [0xfdf0-0xfdff] [0.368202] pci_bus :05: resource 0 io: [0xe000-0xefff] [0.368204] pci_bus :05: resource 3 io: [0x00-0x] [0.368206] pci_bus :05: resource 4 mem: [0x00-0x] [0.368229] NET: Registered protocol family 2 [0.368353] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes) [0.369224] TCP established hash table entries: 524288 (order: 11,
[Bug 609055] Re: problems with using parallel port
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52355463/Dependencies.txt -- problems with using parallel port https://bugs.launchpad.net/bugs/609055 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 609055] [NEW] problems with using parallel port
Public bug reported:
Binary package hint: virt-manager
1)
Description:Ubuntu 10.04 LTS
Release:10.04
2)
Installiert: 0.8.2-2ubuntu8
Kandidat: 0.8.2-2ubuntu8
Versions-Tabelle:
*** 0.8.2-2ubuntu8 0
500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
3) I expected to can use a old parallel dongle (on parallel port) in my
guest system (Win XP)
4) When I add my parallel port (I'm not sure if it is /dev/lp0 or
/dev/parport0) I can't boot the guest system and get the following output:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
self._backend.create()
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 300, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: monitor socket did not show up.: Connection refused
The dongle is connected to the parallel port and libvirt-qemu has the
permission to use this port. I've looked this issue up in google for
hours, but didn't find much.
I'm not sure if this is a real bug, but to my mind it's at least a
"strange behavior" of virt mangater/qemu/kvm.
regards wolfgang
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: virt-manager 0.8.2-2ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-server x86_64
Architecture: amd64
Date: Fri Jul 23 10:02:59 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64
(20100427)
PackageArchitecture: all
ProcEnviron:
LANG=de_AT.utf8
SHELL=/bin/bash
SourcePackage: virt-manager
** Affects: virt-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lucid
--
problems with using parallel port
https://bugs.launchpad.net/bugs/609055
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 608182] Re: problems with ups (mge pulsar es 8+)
this is the output for upsc mgeups: device.mfr: MGE UPS SYSTEMS device.model: Pulsar ES8+ device.type: ups driver.name: mge-utalk driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.4.3 driver.version.internal: 0.89 ups.firmware: 0 ups.id: Pulsar ES8+ 0 ups.mfr: MGE UPS SYSTEMS ups.model: Pulsar ES8+ ups.status: OL CHRG upsrw mgeups doesn't give any output I think there is a bug or something like this in PyNUT-rw-except.diff, because when I run cd /usr/lib/pymodules/python2.6 && sudo patch --dry-run -p0 https://bugs.launchpad.net/bugs/608182 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 242434] Re: QEMU guest doesn't start with no CD in the drive
now I've got exactly the same problem I'm using virt-manager with qemu/kvm and WIN XP as guest and ubuntu 10.04 server as host regards wolfgang -- QEMU guest doesn't start with no CD in the drive https://bugs.launchpad.net/bugs/242434 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 608182] Re: problems with ups (mge pulsar es 8+)
and there is another thing I don't really understand: these "ups-things" aren't started completely, after reboot I get "UPS mge...@localhost is unavailable", so I have to run /etc/init.d/nut start and then it works. This is my /etc/default/nut: # start upsd START_UPSD=yes # start upsmon START_UPSMON=yes -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
sorry for bothering you again autoshutdown works fine, thank you :) but a graphical tool would be nice too, and nut-monitor doesn't work up to now: if I start it from terminal, I get the following: Traceback (most recent call last): File "/usr/bin/NUT-Monitor", line 883, in gui = interface() File "/usr/bin/NUT-Monitor", line 208, in __init__ self.connect_to_ups() File "/usr/bin/NUT-Monitor", line 690, in connect_to_ups self.__ups_rw_vars = self.__ups_handler.GetRWVars( self.__current_ups ) File "/usr/lib/pymodules/python2.6/PyNUT.py", line 208, in GetRWVars data = current[ offset: ].split( '"' )[1] IndexError: list index out of range What must I change? (I've looked it up in the internet, but didn't find much) -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
oops, doesn't work like I expected :) nut.conf: MODE=none ups.conf: [mgeups] driver = mge-utalk port = /dev/ttyS0 desc = "MGE Pulsar ES 8+" pollinterval=20 upsd.conf: LISTEN 127.0.0.1 3493 MAXAGE 25 upsd.users: [admin] password = mgepass allowfrom = localhost actions = SET instcmds = ALL [monuser] password = mgepass allowfrom = localhost upsmon master upsmon.conf: MONITOR mge...@localhost 1 monuser mgepass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 25 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG COMMOK IGNORE NOTIFYFLAG COMMBAD IGNORE RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 upssched.conf: CMDSCRIPT /usr/sbin/upssched-cmd PIPEFN /var/run/nut/upssched.pipe LOCKFN /var/run/nut/upssched.lock AT ONBATT * START-TIMER ups-on-battery-timer 10 AT ONLINE * CANCEL-TIMER ups-on-battery-timer AT ONBATT * EXECUTE ups-on-battery AT ONLINE * EXECUTE ups-back-on-line wizard.conf: bIsNutConfigured=true shutdownBatteryLevel=-1 shutdownBatteryRuntime=-1 displaySystray=true -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
** Attachment added: "nut.conf" http://launchpadlibrarian.net/52259831/nut.conf -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
these are my conf-files: ** Attachment added: "nut.conf" http://launchpadlibrarian.net/52259768/nut.conf -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] Re: problems with ups (mge pulsar es 8+)
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52254514/Dependencies.txt -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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 608182] [NEW] problems with ups (mge pulsar es 8+)
Public bug reported: Binary package hint: nut 1) Description:Ubuntu 10.04 LTS Release:10.04 2) Installiert: 2.4.3-1ubuntu3.1 Kandidat: 2.4.3-1ubuntu3.1 Versions-Tabelle: *** 2.4.3-1ubuntu3.1 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.4.3-1ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 3) I expected my usp to work with mgeops-psp. ;) 4) - After rebooting mgeops-psp tells me "communication failure". upsdrvctl start tells me that it wasn't possible to chdir to /var/run/nut. So I have to mkdir /var/run/nut and change the rights. - When there is finally communication with the ups (mge pulsar es 8+) the battery status is given totally wrong (-1%) and after switching off the power for the ups this is noticed but no shutdown happens. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nut 2.4.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.32-21.32-server 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-server x86_64 Architecture: amd64 Date: Wed Jul 21 12:25:52 2010 InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: LANG=de_AT.utf8 SHELL=/bin/bash SourcePackage: nut ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- problems with ups (mge pulsar es 8+) https://bugs.launchpad.net/bugs/608182 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
