[Bug 570870] Re: pxe boot doesn't work with kvm
bug 472485 seems a dupiicate of this bug (at least the point 1: wrong directory for rom images), it is marked fix released while it does not seem the case -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
for the second point (pxe rom for e1000 buggy with No IP address), it seems there is the same bug on the redhat bugtracker that solves it: https://bugzilla.redhat.com/show_bug.cgi?id=494541 and the solution (494541 is a duplicate of 507391) https://bugzilla.redhat.com/show_bug.cgi?id=507391 ** Bug watch added: Red Hat Bugzilla #494541 https://bugzilla.redhat.com/show_bug.cgi?id=494541 ** Bug watch added: Red Hat Bugzilla #507391 https://bugzilla.redhat.com/show_bug.cgi?id=507391 -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
** Description changed: Binary package hint: qemu-kvm It seems pxe boot with kvm doesn't work in lucid. When I try to boot with pxe I have this message : Starting SeaBios (version 0.5.1-20100120_010601-rothera) No bootable device. - - It works well in karmic, it seems the bios with qemu-kvm changed, maybe - it's related? -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
** Summary changed: - pxe boot doesn't work + pxe boot doesn't work with kvm ** Description changed: Binary package hint: qemu-kvm - It seems pxe boot doesn't work in lucid. When I try to boot with pxe I - have this message : + It seems pxe boot with kvm doesn't work in lucid. When I try to boot + with pxe I have this message : Starting SeaBios (version 0.5.1-20100120_010601-rothera) No bootable device. It works well in karmic, it seems the bios with qemu-kvm changed, maybe it's related? -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 570870] Re: pxe boot doesn't work with kvm
yes, kvm-pxe is installed, pxe boot works before the upgrade of this server -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 570870] Re: pxe boot doesn't work with kvm
It works again, but not out of the box It seems the kvm-pxe package install the rom in the wrong directory : /usr/share/kvm and qemu-kvm seems to search rom images in /usr/share/qemu I copied /usr/share/kvm/pxe-e1000.bin to /usr/share/qemu/pxe-e1000.bin After that, I have another error message at boot: Searching for server (DHCP)No IP address I remember I had the same problem with karmic. I have generated a new gpxe rom and it works again. So it seems there is 2 problems (but not new): 1. kvm-pxe package install rom images in a wrong directory 2. rom for e1000 packaged in kvm-pxe is buggy -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 570870] [NEW] pxe boot doesn't work
Public bug reported: Binary package hint: qemu-kvm It seems pxe boot doesn't work in lucid. When I try to boot with pxe I have this message : Starting SeaBios (version 0.5.1-20100120_010601-rothera) No bootable device. It works well in karmic, it seems the bios with qemu-kvm changed, maybe it's related? ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- pxe boot doesn't work https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
** Summary changed: - pxe boot doesn't work + pxe boot doesn't work with kvm ** Description changed: Binary package hint: qemu-kvm - It seems pxe boot doesn't work in lucid. When I try to boot with pxe I - have this message : + It seems pxe boot with kvm doesn't work in lucid. When I try to boot + with pxe I have this message : Starting SeaBios (version 0.5.1-20100120_010601-rothera) No bootable device. It works well in karmic, it seems the bios with qemu-kvm changed, maybe it's related? -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
yes, kvm-pxe is installed, pxe boot works before the upgrade of this server -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 570870] Re: pxe boot doesn't work with kvm
It works again, but not out of the box It seems the kvm-pxe package install the rom in the wrong directory : /usr/share/kvm and qemu-kvm seems to search rom images in /usr/share/qemu I copied /usr/share/kvm/pxe-e1000.bin to /usr/share/qemu/pxe-e1000.bin After that, I have another error message at boot: Searching for server (DHCP)No IP address I remember I had the same problem with karmic. I have generated a new gpxe rom and it works again. So it seems there is 2 problems (but not new): 1. kvm-pxe package install rom images in a wrong directory 2. rom for e1000 packaged in kvm-pxe is buggy -- pxe boot doesn't work with kvm https://bugs.launchpad.net/bugs/570870 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 476332] Re: kernel crash (Oops) with kvm
We had 5 vm on this host : - 1 debian lenny 64 bits (virtio is used for the network and the block device with qcow2 format and 256Mo RAM is allocated) - 2 ubuntu jaunty 64bits (virtio is used for the network and the block device with qcow2 format and 512Mo RAM is allocated) - 1 redhat 5 64 bits (virtio is used for the network and the block device with qcow2 format and 12Go RAM is allocated) - 1 windows 2003 32 bits (virtio is used for the network and IDE for the block device with qcow2 format and 512Mo RAM is allocated) The host is a karmic koala with 24Go of physical RAM. We have isolated each vm on a different host (with same config and same harware) last week to find the culprit. We are waiting the Oops... -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 476332] Re: kernel crash (Oops) with kvm
We had 5 vm on this host : - 1 debian lenny 64 bits (virtio is used for the network and the block device with qcow2 format and 256Mo RAM is allocated) - 2 ubuntu jaunty 64bits (virtio is used for the network and the block device with qcow2 format and 512Mo RAM is allocated) - 1 redhat 5 64 bits (virtio is used for the network and the block device with qcow2 format and 12Go RAM is allocated) - 1 windows 2003 32 bits (virtio is used for the network and IDE for the block device with qcow2 format and 512Mo RAM is allocated) The host is a karmic koala with 24Go of physical RAM. We have isolated each vm on a different host (with same config and same harware) last week to find the culprit. We are waiting the Oops... -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 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 476332] Re: kernel crash with kvm
** Package changed: linux (Ubuntu) = qemu-kvm (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 476332] Re: kernel crash (Oops) with kvm
** Summary changed: - kernel crash with kvm + kernel crash (Oops) with kvm -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 476332] Re: kernel crash (Oops) with kvm
this upstream bug looks like the same (even if the trace doesn't match exactly) : http://bugzilla.kernel.org/show_bug.cgi?id=14376 It seems it's a regression between 2.6.30.6 and 2.6.31.2, unfortunately without solution. ** Bug watch added: Linux Kernel Bug Tracker #14376 http://bugzilla.kernel.org/show_bug.cgi?id=14376 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=14376 Importance: Unknown Status: Unknown -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 476332] Re: kernel crash with kvm
** Package changed: linux (Ubuntu) = qemu-kvm (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 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 476332] Re: kernel crash (Oops) with kvm
** Summary changed: - kernel crash with kvm + kernel crash (Oops) with kvm -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 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 476332] Re: kernel crash (Oops) with kvm
this upstream bug looks like the same (even if the trace doesn't match exactly) : http://bugzilla.kernel.org/show_bug.cgi?id=14376 It seems it's a regression between 2.6.30.6 and 2.6.31.2, unfortunately without solution. ** Bug watch added: Linux Kernel Bug Tracker #14376 http://bugzilla.kernel.org/show_bug.cgi?id=14376 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=14376 Importance: Unknown Status: Unknown -- kernel crash (Oops) with kvm https://bugs.launchpad.net/bugs/476332 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 476332] Re: kernel crash with kvm
same crash again today, after that all vm are down, rebooting the host is required -- kernel crash with kvm https://bugs.launchpad.net/bugs/476332 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 413070] Re: karmic cciss: error messages on working device
I have exactly the same logging message and same symptoms on an HP DL360G5 with a p400i controller, but only when I create an lvm snapshot. -- karmic cciss: error messages on working device https://bugs.launchpad.net/bugs/413070 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 328536] Re: confusing scrollbar behavior in gnome-terminal when using screen-profiles
for information, I tested with konsole and the scrollbar works fine (with termcapinfo xterm* ti@:te@), it's a specific gnome-terminal + screen combination bug -- confusing scrollbar behavior in gnome-terminal when using screen-profiles https://bugs.launchpad.net/bugs/328536 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 358836] Re: kvm general protection fault on jaunty
** Changed in: kvm (Ubuntu) Status: New = Confirmed -- kvm general protection fault on jaunty https://bugs.launchpad.net/bugs/358836 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 358836] Re: kvm general protection fault on jaunty
Is it planned to upgrade the kvm kernel module with the version in kvm- source ? -- kvm general protection fault on jaunty https://bugs.launchpad.net/bugs/358836 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
I've read bug #356152, if in addition the new scheme is buggy and unfinished, please, please, go back, revert the gconf variable for jaunty and rethink for karmic. I'm really convinced it's a very critical and visible part of the system, if it's not really clean and clear, it's not a good thing for the whole ubuntu system and it's image. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
a vocal minority... that it's too much for me ! I'm not sure it's ubuntu to treat your alpha/beta/rc testers in this way. How many comments and how many duplicates will it take for you to realize that you are wrong (and jaunty is not yet released)? Many people took the time to argue to prove you that you're wrong, are you deaf ? Don't listen your users/testers/contributers and I'm sure you'll solve bug #1... I'm very disappointed. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 358836] Re: kvm general protection fault on jaunty
I retried today, the panic is 100% reproduceable. As you suggested I have tested with kvm-source and this has solved the problem, no more panics :-) Another problem, but it's not related, after the installation completed, Solaris 10 didn't boot. It's a known problem, see : http://www.linux-kvm.org/page/Guest_Support_Status Note: the grub menu entry for Solaris 10 created by the installer is wrong, to make it work add unix/kernel to the line beginning with kernel ; tested on Ubuntu 8.04.1 by BerndSchemmer Just an error, it's kernel/unix and not unix/kernel. Now Solaris 10 works fine. Thanks -- kvm general protection fault on jaunty https://bugs.launchpad.net/bugs/358836 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 358836] [NEW] kvm general protection fault on jaunty
Public bug reported: Binary package hint: kvm Today I tried to install solaris 10 on a fresh jaunty in kvm and this has triggered a general protection fault. Next week I'll try to install solaris 10 again to see if this is reproduceable. versions : # dpkg -l | grep kvm ii kvm 1:84+dfsg-0ubuntu10 Full virtualization on i386 and amd64 hardwa ii kvm-pxe 5.4.3+dfsg-0.2ubuntu1 PXE ROM's for KVM # uname -a Linux 2.6.28-11-server #41-Ubuntu SMP Wed Apr 8 05:29:01 UTC 2009 x86_64 GNU/Linux panic : [ 2943.731058] general protection fault: [#1] SMP [ 2943.731092] last sysfs file: /sys/devices/virtual/net/vnet0/flags [ 2943.731127] Dumping ftrace buffer: [ 2943.731153](ftrace buffer empty) [ 2943.731176] CPU 6 [ 2943.731197] Modules linked in: tun ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables kvm_intel kvm 8021q garp bridge stp lp parport iTCO_wdt iTCO_vendor_support ipmi_si psmouse ipmi_msghandler i5000_edac edac_core pcspkr serio_raw shpchp hpilo usbhid bnx2 cciss fbcon tileblit font bitblit softcursor [ 2943.731402] Pid: 4200, comm: kvm Not tainted 2.6.28-11-server #41-Ubuntu [ 2943.731431] RIP: 0010:[a0152cf0] [a0152cf0] paging64_shadow_invlpg_entry+0x40/0x80 [kvm] [ 2943.731494] RSP: 0018:880306cb3c08 EFLAGS: 00010246 [ 2943.731519] RAX: 0085 RBX: 000588000428 RCX: 000588000428 [ 2943.731548] RDX: 880306c31f60 RSI: 880306c31f60 RDI: 880306cb3c68 [ 2943.731577] RBP: 880306cb3c18 R08: R09: [ 2943.731606] R10: 8802ee41b000 R11: R12: 000588000428 [ 2943.731635] R13: 000c R14: 0e485000 R15: 880306c31f60 [ 2943.731665] FS: 7f762da91950() GS:88032ef9f780() knlGS: [ 2943.731709] CS: 0010 DS: 002b ES: 002b CR0: 8005003b [ 2943.731736] CR2: ceb27788 CR3: 000321458000 CR4: 26a0 [ 2943.731765] DR0: DR1: DR2: [ 2943.731794] DR3: DR6: 0ff0 DR7: 0400 [ 2943.731824] Process kvm (pid: 4200, threadinfo 880306cb2000, task 88032cd75980) [ 2943.731868] Stack: [ 2943.731888] 880306cb3c24 0001 880306cb3c58 a0151d9e [ 2943.731922] 880306cb3c68 880306c31f60 0e485000 880306c31f60 [ 2943.731973] 000e 000e 880306cb3ca8 a0151e63 [ 2943.732040] Call Trace: [ 2943.732061] [a0151d9e] walk_shadow+0x8e/0xe0 [kvm] [ 2943.732096] [a0151e63] paging64_invlpg+0x33/0x40 [kvm] [ 2943.732131] [a0152cb0] ? paging64_shadow_invlpg_entry+0x0/0x80 [kvm] [ 2943.732186] [8069dd49] ? _spin_lock+0x9/0x10 [ 2943.732220] [a01524bf] kvm_mmu_invlpg+0x2f/0x60 [kvm] [ 2943.732255] [a017835c] handle_invlpg+0x1c/0x30 [kvm_intel] [ 2943.732288] [a0177c25] kvm_handle_exit+0xb5/0x1d0 [kvm_intel] [ 2943.732319] [8069db53] ? __down_read+0xc3/0xce [ 2943.732349] [a014b958] vcpu_enter_guest+0x1f8/0x400 [kvm] [ 2943.732384] [80268890] ? autoremove_wake_function+0x0/0x40 [ 2943.732417] [a014dc29] __vcpu_run+0x69/0x2d0 [kvm] [ 2943.732451] [a01518ea] kvm_arch_vcpu_ioctl_run+0x8a/0x1f0 [kvm] [ 2943.732487] [a0146582] kvm_vcpu_ioctl+0x2e2/0x5a0 [kvm] [ 2943.732522] [802781ed] ? futex_requeue+0xfd/0x2e0 [ 2943.732551] [802f60c1] vfs_ioctl+0x31/0xa0 [ 2943.732580] [802f6475] do_vfs_ioctl+0x75/0x230 [ 2943.732608] [802f66c9] sys_ioctl+0x99/0xa0 [ 2943.732635] [802e8098] ? sys_read+0x88/0x90 [ 2943.732664] [8021253a] system_call_fastpath+0x16/0x1b [ 2943.732693] Code: 48 8b 11 48 3b 15 19 bf 01 00 b8 01 00 00 00 74 0c 31 c0 48 3b 15 11 bf 01 00 0f 94 c0 48 83 c4 08 5b c9 c3 0f 1f 80 00 00 00 00 48 8b 01 48 3b 05 ee be 01 00 74 14 48 3b 05 ed be 01 00 74 0b [ 2943.732889] RIP [a0152cf0] paging64_shadow_invlpg_entry+0x40/0x80 [kvm] [ 2943.732940] RSP 880306cb3c08 [ 2943.733197] ---[ end trace f8ca068ee8691eb3 ]--- ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- kvm general protection fault on jaunty https://bugs.launchpad.net/bugs/358836 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
Just to be more precise, I have nothing against the new notifyosd. But, I think, there is a problem with update-notifier implementation. The permanent reminder for updates available or reboot required is very important for every users (everyone doesn't want to update or reboot immediately), this information is lost in Jaunty and I think it's a very bad thing. Maybe there is other way that icon in notification area, but this information is very useful. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 332945] Re: [Jaunty] Removal of Update Notifier is WRONG
Entirely agree with ruban, the notifier icon for updates (as implemented in Intrepid) is simply perfect. As against, no one like unsolicited windows. Please restore the old behavior. -- [Jaunty] Removal of Update Notifier is WRONG https://bugs.launchpad.net/bugs/332945 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 336712] [NEW] freebsd text screen corruption with kvm
Public bug reported: Binary package hint: kvm I just try and kvm in jaunty is affected by this bug, upstream bug report (with patch) : http://sourceforge.net/tracker/?func=detailatid=893831aid=2556746group_id=180599 FreeBSD is unusable in kvm with jaunty due to this bug, it works in intrepid (kvm version 81) ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- freebsd text screen corruption with kvm https://bugs.launchpad.net/bugs/336712 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 336712] Re: freebsd text screen corruption with kvm
** Bug watch added: SourceForge.net Tracker #2556746 http://sourceforge.net/support/tracker.php?aid=2556746 ** Also affects: kvm via http://sourceforge.net/support/tracker.php?aid=2556746 Importance: Unknown Status: Unknown -- freebsd text screen corruption with kvm https://bugs.launchpad.net/bugs/336712 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
