[Bug 351463] Re: KDE4 screensaver lock doesn't accept password
Had the same issue with a fresh installation (not upgraded) of Ubuntu 12.04 (Precise). I could also fix it by changing the group of /etc/shadow from root to shadow. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in Ubuntu. https://bugs.launchpad.net/bugs/351463 Title: KDE4 screensaver lock doesn't accept password To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/351463/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 603363] Re: sshd never stops, prevents umount of /usr partition
Test was successful - the /usr partition could be unmounted correctly. One strange thing remains - the /var partition can only be mounted in read-only mode, but that might have nothing to do with this issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- 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 603363] Re: sshd never stops, prevents umount of /usr partition
Test was successful - the /usr partition could be unmounted correctly. One strange thing remains - the /var partition can only be mounted in read-only mode, but that might have nothing to do with this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721108] [NEW] Regression in 4.71-3ubuntu1.1 (lucid) when using macros
Public bug reported: Binary package hint: exim4 exim4 4.71-3ubuntu1.1 (using lucid) completely stopped our mail server working, because we have three queues -DINCOMING, -DOUTGOING and the default one (no -D). Is there any way to configure a whitelist for -D switches (not the WHITELIST_D_MACROS compile time option)? ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Regression in 4.71-3ubuntu1.1 when using macros + Regression in 4.71-3ubuntu1.1 (lucid) when using macros ** Description changed: Binary package hint: exim4 - exim4 4.71-3ubuntu1.1 completely stopped our mail server working, - because we have three queues -DINCOMING, -DOUTGOING and the default one - (no -D). Is there any way to configure a whitelist for -D switches (not - the WHITELIST_D_MACROS compile time option)? + exim4 4.71-3ubuntu1.1 (using lucid) completely stopped our mail server + working, because we have three queues -DINCOMING, -DOUTGOING and the + default one (no -D). Is there any way to configure a whitelist for -D + switches (not the WHITELIST_D_MACROS compile time option)? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in ubuntu. https://bugs.launchpad.net/bugs/721108 Title: Regression in 4.71-3ubuntu1.1 (lucid) when using macros -- 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 721108] [NEW] Regression in 4.71-3ubuntu1.1 (lucid) when using macros
Public bug reported: Binary package hint: exim4 exim4 4.71-3ubuntu1.1 (using lucid) completely stopped our mail server working, because we have three queues -DINCOMING, -DOUTGOING and the default one (no -D). Is there any way to configure a whitelist for -D switches (not the WHITELIST_D_MACROS compile time option)? ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Regression in 4.71-3ubuntu1.1 when using macros + Regression in 4.71-3ubuntu1.1 (lucid) when using macros ** Description changed: Binary package hint: exim4 - exim4 4.71-3ubuntu1.1 completely stopped our mail server working, - because we have three queues -DINCOMING, -DOUTGOING and the default one - (no -D). Is there any way to configure a whitelist for -D switches (not - the WHITELIST_D_MACROS compile time option)? + exim4 4.71-3ubuntu1.1 (using lucid) completely stopped our mail server + working, because we have three queues -DINCOMING, -DOUTGOING and the + default one (no -D). Is there any way to configure a whitelist for -D + switches (not the WHITELIST_D_MACROS compile time option)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721108 Title: Regression in 4.71-3ubuntu1.1 (lucid) when using macros -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 697934] Re: Merge exim4 4.73~rc1-1 (main) from Debian experimental (main)
exim4 4.71-3ubuntu1.1 completely stopped our mail server working, because we have three queues -DINCOMING, -DOUTGOING and the default one (no -D). Is there any way to configure a whitelist for -D switches (not the WHITELIST_D_MACROS compile time option)? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in ubuntu. https://bugs.launchpad.net/bugs/697934 Title: Merge exim4 4.73~rc1-1 (main) from Debian experimental (main) -- 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 697934] Re: Merge exim4 4.73~rc1-1 (main) from Debian experimental (main)
exim4 4.71-3ubuntu1.1 completely stopped our mail server working, because we have three queues -DINCOMING, -DOUTGOING and the default one (no -D). Is there any way to configure a whitelist for -D switches (not the WHITELIST_D_MACROS compile time option)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/697934 Title: Merge exim4 4.73~rc1-1 (main) from Debian experimental (main) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603363] Re: sshd never stops, prevents umount of /usr partition
I hope it will be part of 10.04.2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- 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 603363] Re: sshd never stops, prevents umount of /usr partition
I hope it will be part of 10.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603363] Re: sshd never stops, prevents umount of /usr partition
I think the problem is the upstart configuration for the ssh daemon /etc/init/ssh.conf - stop on runlevel S Shouldn't that be: stop on runlevel [!2345] ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- 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 603363] Re: sshd never stops, prevents umount of /usr partition
I think the problem is the upstart configuration for the ssh daemon /etc/init/ssh.conf - stop on runlevel S Shouldn't that be: stop on runlevel [!2345] ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/603363 Title: sshd never stops, prevents umount of /usr partition -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660596] Re: Black screen after installing Nvidia drivers on 10.10
I've tested two cards. GeForce 6200 TurboCache runs perfectly with the 260.19.06 driver, but I had no luck with a brand new GeForce GT 240 - black screen / system hangs when starting X. Unfortunately that card isn't supported by the 195 driver, so I tried the 256 - system shows login screen (KDM) but freezes when logging in. Using the nouveau driver, the GT 240 card runs fine (but rather slow, and no 3D). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660596 Title: Black screen after installing Nvidia drivers on 10.10 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689411] [NEW] mailscanner died unexpectedly because of eval in taint mode
Public bug reported: Binary package hint: mailscanner After upgrading from jaunty to lucid my mailscanner dies when constructing a warning message. When launching mailscanner with debug enabled, I get this: In Debugging mode, not forking... Trying to setlogsock(unix) Building a message batch to scan... Have a batch of 1 message. Insecure dependency in eval while running with -T switch at /usr/share/MailScanner//MailScanner/Message.pm line 4239, GEN63 line 1. Insecure dependency in eval while running with -T switch at /usr/share/MailScanner//MailScanner/Message.pm line 4239, GEN63 line 1. It is the ConstructWarning sub in /usr/share/MailScanner/MailScanner/Message.pm - line 4239 is: $result = eval \$line\; As soon as a new infected mail is scanned, mailscanner enters an endless loop - no messages are processed anymore. The instance dies and is being respawned over and over again. ** Affects: mailscanner (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:ubuntu/lucid/mailscanner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689411 Title: mailscanner died unexpectedly because of eval in taint mode -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689411] Re: mailscanner died unexpectedly because of eval in taint mode
I could work around this problem by adding a '--chuid Debian-exim' parameter to the start-stop-daemon call in /etc/init.d/mailscanner - start-stop-daemon --start --quiet --nicelevel $run_nice --chuid Debian-exim --exec $DAEMON --name $NAME -- $DAEMON_ARGS \ || return 2 I could also find more people having the same problem: http://ubuntuforums.org/showthread.php?t=1313599 http://www.howtoforge.com/the-perfect-spamsnake-ubuntu-jaunty-jackalope http://www.bluequartz.us/phpBB2/viewtopic.php?t=108939 The problem seems to be, that the mailscanner version used in karmic and lucid is not compatible with Perl 5.10 ** Branch linked: lp:ubuntu/karmic/mailscanner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689411 Title: mailscanner died unexpectedly because of eval in taint mode -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 603363] Re: sshd never stops, prevents umount of /usr partition
Sometimes it is not even possible to remount the filesystem readonly. This can cause damage to the filesystem, thus this issue should get high priority. ** Changed in: openssh (Ubuntu Lucid) Status: New = Incomplete ** Changed in: openssh (Ubuntu Lucid) Status: Incomplete = Confirmed -- sshd never stops, prevents umount of /usr partition https://bugs.launchpad.net/bugs/603363 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 603363] Re: sshd never stops, prevents umount of /usr partition
Sometimes it is not even possible to remount the filesystem readonly. This can cause damage to the filesystem, thus this issue should get high priority. ** Changed in: openssh (Ubuntu Lucid) Status: New = Incomplete ** Changed in: openssh (Ubuntu Lucid) Status: Incomplete = Confirmed -- sshd never stops, prevents umount of /usr partition https://bugs.launchpad.net/bugs/603363 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 592576] [NEW] Parse error for workers.properties
Public bug reported: Binary package hint: libapache-mod-jk I'm running libapache-mod-jk 1.2.28-2 on Ubuntu 10.04 and I have this content in my workers.properties file: worker.list = dev worker.dev.type = ajp13 worker.dev.host = localhost worker.dev.port = 8009 Apache doesn't start and my mod_jk.log shows this error: [Fri Jun 11 10:57:26.414 2010] [4853:2129983296] [error] wc_create_worker::jk_worker.c (139): Unknown worker type aj113 for worker dev [Fri Jun 11 10:57:26.414 2010] [4853:2129983296] [error] build_worker_map::jk_worker.c (262): failed to create worker dev Do you see the aj113 instead of ajp13? When I remove the space char before and after the equal char in the corresponding line, I get this im my logs: [Fri Jun 11 10:59:05.457 2010] [4889:3785144128] [error] ajp_validate::jk_ajp_common.c (2526): worker dev can't resolve tomcat address localhsst [Fri Jun 11 10:59:05.457 2010] [4889:3785144128] [error] wc_create_worker::jk_worker.c (163): validate failed for dev [Fri Jun 11 10:59:05.457 2010] [4889:3785144128] [error] build_worker_map::jk_worker.c (262): failed to create worker dev Do you see the localhsst instead of localhost? When I remove all spaces in my workers.properties, Apache starts without any errors. My config now contains: worker.list=dev worker.dev.type=ajp13 worker.dev.host=localhost worker.dev.port=8009 I haven't changed this config for years and it worked flawlessly with all previous mod_jk versions. This bug could be critical for people updating a production machine from a previous Ubuntu release to lucid lynx, because it takes some time to recognize that you have to remove spaces to get mod_jk up again. ** Affects: libapache-mod-jk (Ubuntu) Importance: Undecided Status: New -- Parse error for workers.properties https://bugs.launchpad.net/bugs/592576 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 484307] Re: Partitions not unmounted correctly
I found a workaround. Before installing the VMware-Tools I rename /sbin/insserv to /sbin/insserv.bak - then the VMware-Tools installer uses update-rc.d as a fallback. After the installation I rename /sbin/insserv.bak back to /sbin/insserv . -- Partitions not unmounted correctly https://bugs.launchpad.net/bugs/484307 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 484307] Re: Partitions not unmounted correctly
I noticed that the installation of VMware-Tools (VMware- Tools-4.0.0-236512 for ESX 4.0 in my case) causes that the sequence numbers of rc0 and rc6 changes. Before the installation halt is linked with S90halt, after the installation it is S01halt. -- Partitions not unmounted correctly https://bugs.launchpad.net/bugs/484307 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 484307] Re: Partitions not unmounted correctly
This is the log when installing the VMware-Tools. There are several lines like this: insserv: warning: current start runlevel(s) (0) of script `halt' overwrites defaults (empty). ** Attachment added: Installation Log of VMware-Tools-4.0.0-236512 http://launchpadlibrarian.net/48882537/vmware-inst.log -- Partitions not unmounted correctly https://bugs.launchpad.net/bugs/484307 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 484307] Re: Partitions not unmounted correctly
OK - here is how you can reproduce this: r...@ubuntutpl:~# cat /etc/init.d/testinit #!/bin/sh ### BEGIN INIT INFO # Provides: test # Required-Start: $local_fs # Required-Stop: $local_fs # X-Start-Before: $network # X-Stop-After: $network # Default-Start: 2 3 5 # Default-Stop: 0 6 ### END INIT INFO r...@ubuntutpl:~# ls -l /etc/rc0.d/ total 1 -rw-r--r-- 1 root root 353 2009-09-07 20:58 README lrwxrwxrwx 1 root root 22 2010-05-21 19:18 S15wpa-ifupdown - ../init.d/wpa-ifupdown lrwxrwxrwx 1 root root 18 2010-05-21 19:16 S20sendsigs - ../init.d/sendsigs lrwxrwxrwx 1 root root 17 2010-05-21 19:16 S30urandom - ../init.d/urandom lrwxrwxrwx 1 root root 22 2010-05-21 19:16 S31umountnfs.sh - ../init.d/umountnfs.sh lrwxrwxrwx 1 root root 20 2010-05-21 19:16 S35networking - ../init.d/networking lrwxrwxrwx 1 root root 18 2010-05-21 19:16 S40umountfs - ../init.d/umountfs lrwxrwxrwx 1 root root 20 2010-05-21 19:16 S60umountroot - ../init.d/umountroot lrwxrwxrwx 1 root root 14 2010-05-21 19:16 S90halt - ../init.d/halt r...@ubuntutpl:~# insserv /etc/init.d/testinit [ alot of insserv warnings ] r...@ubuntutpl:~# ls -l /etc/rc0.d/ total 1 -rw-r--r-- 1 root root 353 2009-09-07 20:58 README lrwxrwxrwx 1 root root 14 2010-05-21 20:01 S01halt - ../init.d/halt lrwxrwxrwx 1 root root 20 2010-05-21 20:01 S01networking - ../init.d/networking lrwxrwxrwx 1 root root 18 2010-05-21 20:01 S01sendsigs - ../init.d/sendsigs lrwxrwxrwx 1 root root 18 2010-05-21 20:01 S01umountfs - ../init.d/umountfs lrwxrwxrwx 1 root root 22 2010-05-21 20:01 S01umountnfs.sh - ../init.d/umountnfs.sh lrwxrwxrwx 1 root root 20 2010-05-21 20:01 S01umountroot - ../init.d/umountroot lrwxrwxrwx 1 root root 17 2010-05-21 20:01 S02urandom - ../init.d/urandom lrwxrwxrwx 1 root root 22 2010-05-21 20:01 S02wpa-ifupdown - ../init.d/wpa-ifupdown -- Partitions not unmounted correctly https://bugs.launchpad.net/bugs/484307 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 531017] Re: Unable to detect VMware's PVSCSI device during installation.
I tried with todays server ISO image (2010-03-10). The good thing is, that the installer contains both, the VMXNET3 and the PVSCSI driver and detects the virtual hardware flawlessly. Unfortunately the system doesn't boot afterwards when installed in minimal virtual machine mode (using the -virtual linux kernel). The system then lacks the PVSCSI driver and drops to a BusyBox shell because no disk could be found. When installing the system in standard mode, I can start the system when using the recovery mode (from the GRUB menu). Standard boot doesn't work (blank screen) - but this seems to be a graphic issue. Shouldn't the VMXNET3 and PVSCSI driver be included in the -virtual linux image? -- Unable to detect VMware's PVSCSI device during installation. https://bugs.launchpad.net/bugs/531017 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 531017] Re: Unable to detect VMware's PVSCSI device during installation.
** Changed in: linux (Ubuntu Lucid) Status: Fix Released = Confirmed -- Unable to detect VMware's PVSCSI device during installation. https://bugs.launchpad.net/bugs/531017 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 531017] Re: Unable to detect VMware's PVSCSI device during installation.
I don't know why this issue is marked as fixed. The Installer of 10.04 Alpha 3 (Server Edition) still lacks support for PVSCSI and VMXNET3 (both - the -server and the -virtual linux kernel image). -- Unable to detect VMware's PVSCSI device during installation. https://bugs.launchpad.net/bugs/531017 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 420320] Re: unhandled vm exit: 0x31
This happened one more time - now with 2.6.28-17.58-server -- unhandled vm exit: 0x31 https://bugs.launchpad.net/bugs/420320 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 420320] [NEW] unhandled vm exit: 0x31
Public bug reported: Binary package hint: kvm One of my virtual machines crashed after weeks of normal operation. I got this in my /var/log/libvirt/qemu/[virtmachine].log file: unhandled vm exit: 0x31 vcpu_id 1 rax 88001deebfd8 rbx rcx rdx rsi 0001 rdi 80a9d008 rsp 88001deebf18 rbp 88001deebf18 r8 r9 0001045e5dc0 r10 r11 r12 r13 r14 r15 rip 8022e856 rflags 0246 cs 0010 (/ p 1 dpl 0 db 0 s 1 type b l 1 g 1 avl 0) ds 0018 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) es 0018 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0018 (/ p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gs (88001f41aa00/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) tr 0040 (880001024480/2087 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt (/ p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt 88000101d000/7f idt 80a99000/fff cr0 8005003b cr2 7f54fdbae000 cr3 1b52b000 cr4 6a0 cr8 0 efer 501 Versions: Ubuntu 9.04 Linux version 2.6.28-15-server (bui...@yellow) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #48-Ubuntu SMP Wed Jul 29 09:38:22 UTC 2009 kvm: Installed: 1:84+dfsg-0ubuntu12.3 Candidate: 1:84+dfsg-0ubuntu12.3 Version table: *** 1:84+dfsg-0ubuntu12.3 0 500 http://de.archive.ubuntu.com jaunty-updates/main Packages 100 /var/lib/dpkg/status 1:84+dfsg-0ubuntu11 0 500 http://de.archive.ubuntu.com jaunty/main Packages libvirt-bin: Installed: 0.6.1-0ubuntu5.1 Candidate: 0.6.1-0ubuntu5.1 Version table: *** 0.6.1-0ubuntu5.1 0 500 http://de.archive.ubuntu.com jaunty-updates/main Packages 100 /var/lib/dpkg/status 0.6.1-0ubuntu5 0 500 http://de.archive.ubuntu.com jaunty/main Packages ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- unhandled vm exit: 0x31 https://bugs.launchpad.net/bugs/420320 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 362288] Re: virsh destroy might also kill another running VM
Bryan, I couldn't apply the event-handling-fix-rh499698-lp362288.patch against libvirt_0.6.1-0ubuntu5 - $ quilt push Applying patch event-handling-fix-rh499698-lp362288.patch patching file libvirt-0.6.1/qemud/event.c Hunk #12 FAILED at 429. Hunk #13 succeeded at 542 (offset -1 lines). Hunk #14 succeeded at 568 (offset -1 lines). Hunk #15 succeeded at 612 (offset -1 lines). Hunk #16 succeeded at 631 (offset -1 lines). 1 out of 16 hunks FAILED -- rejects in file libvirt-0.6.1/qemud/event.c patching file libvirt-0.6.1/qemud/qemud.c patching file libvirt-0.6.1/qemud/qemud.h Patch event-handling-fix-rh499698-lp362288.patch does not apply (enforce with -f) What am I missing? -- virsh destroy might also kill another running VM https://bugs.launchpad.net/bugs/362288 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 362288] Re: virsh destroy might also kill another running VM
Thank's Bryan! Patch is installed and works great (tested save, restore and destroy) so far. -- virsh destroy might also kill another running VM https://bugs.launchpad.net/bugs/362288 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 362288] Re: virsh destroy might also kill another running VM
Please note, that also a 'virsh save domain' destroys other domains. Any updates here? -- virsh destroy might also kill another running VM https://bugs.launchpad.net/bugs/362288 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
