[Bug 1909383] [NEW] Upstream links changed
Public bug reported: Hi, I am the author of pngtools. After prompting from Arch Linux, I've recovered the source code for pngtools from a backup and placed it on github at https://github.com/mikalstill/pngtools. I'd be happy enough to accept patches and bug reports there, and will do my best to service them -- noting that this code is nearly 20 years old. I'm not sure what the correct Ubuntu process is for such things, so I am just filing this bug. As best as I can tell the upstream package is unmaintained in Debian. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pngtools 0.4-1.3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 27 14:27:54 2020 InstallationDate: Installed on 2020-08-29 (119 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pngtools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pngtools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909383 Title: Upstream links changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pngtools/+bug/1909383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893538] [NEW] No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04
Public bug reported: Hi, my Dell XPS 7390 worked just fine with Ubuntu 19.10, but after clean-install upgrading to 20.04 I don't have working bluetooth any more. The machine has an Intel AX200 installed. I'm not sure what details are helpful to provide, so here are some random things, happy to provide more if people can provide hints... # uname -a Linux marvin 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux # lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:15.1 Serial bus controller [0c80]: Intel Corporation Comet Lake Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:1c.0 PCI bridge: Intel Corporation Device 02bc (rev f0) 00:1c.6 PCI bridge: Intel Corporation Device 02be (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 02:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) 03:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 04:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 3b:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) 71:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5410 (rev 01) # dmesg | grep iwl [8.578338] iwlwifi :02:00.0: enabling device ( -> 0002) [8.594306] iwlwifi :02:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2 [8.594320] iwlwifi :02:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2 [8.597017] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [8.597019] iwlwifi :02:00.0: Found debug destination: EXTERNAL_DRAM [8.597020] iwlwifi :02:00.0: Found debug configuration: 0 [8.597192] iwlwifi :02:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [8.650489] iwlwifi :02:00.0: Detected Killer(R) Wi-Fi 6 AX1650w 160MHz Wireless Network Adapter (200D2W), REV=0x340 [8.663161] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [8.663495] iwlwifi :02:00.0: Allocated 0x0040 bytes for firmware monitor. [8.829671] iwlwifi :02:00.0: base HW address: 04:ed:33:c0:85:78 [8.846912] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 [9.459653] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [9.626499] iwlwifi :02:00.0: FW already configured (0) - re-configuring ** Affects: linux-firmware (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/1893538 Title: No bluetooth on Dell XPS 7390 with AX200 after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1893538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 435550] Re: scrollwheel should scroll not browse
Is there a way we can fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/435550 Title: scrollwheel should scroll not browse To manage notifications about this bug go to: https://bugs.launchpad.net/gthumb/+bug/435550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I've tried this from pop!_os 20.04, nVidia 2060 super GTX, 4k monitor. Starting off in 100% scaling, I select 125% scaling. Before enabling proposed, this resulted in the screen switching off. Since enabling proposed and installing the updated packages, this now doesn't switch the screen off, but the behaviour is still not correct. I believe I'm now experiencing https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285 and https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593 (the latter of which is marked as fixed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827410] [NEW] Error in combination with z-push/ Kopano with attachment-names in Outlook
Public bug reported: Error only happens with the packages from ubuntu repos, when installing the nightly-packages from Kopano-Community, with their own libvmime-Package, it works fine. (libvmime-kopano1) The problem shows up, when using Kopano from repos with z-push, to connect Win Outlook over ActiveSync. When receiving a mail in this setup, from another Outlook sender with more than one attachment, all attachments show up as Unnamed Attachment.X (Unbenannte Anlage.X) It seems possible to me, that this only applys to german users, because of all forum posts faceing this issue, are german users. Through some Kopano-dev forum posts, i came to the suspicion, that it could be related to the vmime package. If you need any further information, please let me know, i would be happy if i could help. Description:Ubuntu 18.04.2 LTS Release:18.04 libvmime1:amd64 0.9.2-5build2 amd64C++ mail library (runtime library) kopano-core 8.5.5-0ubuntu1 all Metapackage to install the Kopano Core stack Thanks in advance Best regards ** Affects: libvmime (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/1827410 Title: Error in combination with z-push/ Kopano with attachment-names in Outlook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvmime/+bug/1827410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567807] Re: nova delete doesn't work with EFI booted VMs
Your fix looks reasonable to me, but we'd need a test as well I think. I've tagged this as being of possible backport interest to mitaka as well. ** Changed in: nova (Ubuntu) Status: New => Confirmed ** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Status: New => Triaged ** Changed in: nova Importance: Undecided => Low ** Tags added: libvirt mitaka-backport-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1567807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209092] Re: network : gnome-control-center crashed with SIGABRT in g_assertion_message
I am experiencing this problem as well. Any news on your testing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209092 Title: network : gnome-control-center crashed with SIGABRT in g_assertion_message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1209092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
** Tags added: libvirt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- 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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
Hi! There seem to be two issues here in the one bug -- DHCP refreshes are causing problems, and pain with windows instances because of how they handle timezones and that causing extra DHCP refreshes. I'll talk about each of those separately. Windows timezones = I'm sorry to hear you're having pain with Windows instances. Unfortunately I don't know a lot about windows, but it sounds as though if we could change the bios timezone for Windows instances to the timezone of the compute node that would alleviate your issue. Is that correct? Looking at the code, each instance has an os_type field, which is inherited from the image the instance is based off (there is an image property called os_type). Xen expects this value to be windows for windows instances. So, libvirt could do the same thing here and treat the timezone for instances with os_type == windows differently. I'm going to create a new bug to track this windows issue, so that I can leave this bug focussed on the DHCP timeout issue. This isn't because Windows is less important as a guest, but because I don't want it to be missed in the DHCP discussion that's happening here. DHCP refreshes == It also sounds as if we could bear in increase the default DHCP interval, although you can configure that yourself as well. It might also make sense to ping an IP before we delete its lease. Cheers, Michael ** Changed in: nova Importance: Undecided = High ** Changed in: nova Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- 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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
The bug for the windows timezone issues is 1231254. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- 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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
** Tags added: libvirt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
The bug for the windows timezone issues is 1231254. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
Hi! There seem to be two issues here in the one bug -- DHCP refreshes are causing problems, and pain with windows instances because of how they handle timezones and that causing extra DHCP refreshes. I'll talk about each of those separately. Windows timezones = I'm sorry to hear you're having pain with Windows instances. Unfortunately I don't know a lot about windows, but it sounds as though if we could change the bios timezone for Windows instances to the timezone of the compute node that would alleviate your issue. Is that correct? Looking at the code, each instance has an os_type field, which is inherited from the image the instance is based off (there is an image property called os_type). Xen expects this value to be windows for windows instances. So, libvirt could do the same thing here and treat the timezone for instances with os_type == windows differently. I'm going to create a new bug to track this windows issue, so that I can leave this bug focussed on the DHCP timeout issue. This isn't because Windows is less important as a guest, but because I don't want it to be missed in the DHCP discussion that's happening here. DHCP refreshes == It also sounds as if we could bear in increase the default DHCP interval, although you can configure that yourself as well. It might also make sense to ping an IP before we delete its lease. Cheers, Michael ** Changed in: nova Importance: Undecided = High ** Changed in: nova Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832507] Re: console.log grows indefinitely
** Changed in: nova Status: In Progress = Triaged ** Changed in: nova Assignee: Michael Still (mikalstill) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- 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 832507] Re: console.log grows indefinitely
** Changed in: nova Assignee: Michael Still (mikalstill) = (unassigned) ** Changed in: nova Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- 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 832507] Re: console.log grows indefinitely
** Changed in: nova Status: In Progress = Triaged ** Changed in: nova Assignee: Michael Still (mikalstill) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832507] Re: console.log grows indefinitely
** Changed in: nova Assignee: Michael Still (mikalstill) = (unassigned) ** Changed in: nova Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190086] Re: empty console log output with grizzly on centOS distribution
Does the console log file exist at all? ** Summary changed: - empty console log output with grizzley on centOS distribution + empty console log output with grizzly on centOS distribution ** Changed in: nova Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1190086 Title: empty console log output with grizzly on centOS distribution To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1190086/+subscriptions -- 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 1190086] Re: empty console log output with grizzly on centOS distribution
Does the console log file exist at all? ** Summary changed: - empty console log output with grizzley on centOS distribution + empty console log output with grizzly on centOS distribution ** Changed in: nova Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190086 Title: empty console log output with grizzly on centOS distribution To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1190086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832507] Re: console.log grows indefinitely
** Changed in: nova Assignee: (unassigned) = Michael Still (mikalstill) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- 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 832507] Re: console.log grows indefinitely
** Changed in: nova Assignee: (unassigned) = Michael Still (mikalstill) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182624] Re: Uncached instance builds fail with non-zero root disk sizes
** Changed in: nova Status: New = Confirmed ** Changed in: nova Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1182624 Title: Uncached instance builds fail with non-zero root disk sizes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1182624/+subscriptions -- 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 1182624] Re: Uncached instance builds fail with non-zero root disk sizes
** Changed in: nova Status: New = Confirmed ** Changed in: nova Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182624 Title: Uncached instance builds fail with non-zero root disk sizes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1182624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170832] Re: Facebook Requires Authorization when already authorized
You can check that solution: Login to your fb page. Go to Account Settings Apps https://www.facebook.com/settings?tab=applications. Edit Ubuntu and change When to notify you? to Never. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170832 Title: Facebook Requires Authorization when already authorized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1170832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155458] Re: 500 response when trying to create a server from a deleted image
@Matthew -- are you still working on this one? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1155458 Title: 500 response when trying to create a server from a deleted image To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155458/+subscriptions -- 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 1155458] Re: 500 response when trying to create a server from a deleted image
@Matthew -- are you still working on this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155458 Title: 500 response when trying to create a server from a deleted image To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158563] Re: After grizzly upgrade, EC2 API requests fail:Could not find: credential
@Adam -- can we therefore remove the upstream tasks from this bug? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1158563 Title: After grizzly upgrade, EC2 API requests fail:Could not find: credential To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1158563/+subscriptions -- 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 1158563] Re: After grizzly upgrade, EC2 API requests fail:Could not find: credential
@Adam -- can we therefore remove the upstream tasks from this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158563 Title: After grizzly upgrade, EC2 API requests fail:Could not find: credential To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1158563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158563] Re: After grizzly upgrade, EC2 API requests fail:Could not find: credential
** Tags added: ec2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1158563 Title: After grizzly upgrade, EC2 API requests fail:Could not find: credential To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1158563/+subscriptions -- 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 1158563] Re: After grizzly upgrade, EC2 API requests fail:Could not find: credential
** Tags added: ec2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158563 Title: After grizzly upgrade, EC2 API requests fail:Could not find: credential To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1158563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155458] Re: 500 response when trying to create a server from a deleted image
** Changed in: nova Assignee: (unassigned) = Matthew Sherborne (msherborne+openstack) ** Changed in: nova Status: New = Triaged ** Changed in: nova Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1155458 Title: 500 response when trying to create a server from a deleted image To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155458/+subscriptions -- 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 1155458] Re: 500 response when trying to create a server from a deleted image
** Changed in: nova Assignee: (unassigned) = Matthew Sherborne (msherborne+openstack) ** Changed in: nova Status: New = Triaged ** Changed in: nova Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155458 Title: 500 response when trying to create a server from a deleted image To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1155458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028718] Re: nova volumes are inappropriately clingy for ceph and similar drivers
nova-volumes is gone now, so this is just a cinder bug. ** No longer affects: nova -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1028718 Title: nova volumes are inappropriately clingy for ceph and similar drivers To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1028718/+subscriptions -- 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 833519] Re: lxc in nova will happily attempt to run x86_64 container on i686 arch
Closing from lack of activity. ** Changed in: nova Status: Confirmed = Won't Fix ** Changed in: nova Importance: Low = Undecided -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/833519 Title: lxc in nova will happily attempt to run x86_64 container on i686 arch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/833519/+subscriptions -- 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 1028718] Re: nova volumes are inappropriately clingy for ceph and similar drivers
nova-volumes is gone now, so this is just a cinder bug. ** No longer affects: nova -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028718 Title: nova volumes are inappropriately clingy for ceph and similar drivers To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1028718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 833519] Re: lxc in nova will happily attempt to run x86_64 container on i686 arch
Closing from lack of activity. ** Changed in: nova Status: Confirmed = Won't Fix ** Changed in: nova Importance: Low = Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/833519 Title: lxc in nova will happily attempt to run x86_64 container on i686 arch To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/833519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances
Yes, if there are more device files than that they will now be used as well. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/861504 Title: nova-compute-lxc limited by available nbd devices to 16 instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/861504/+subscriptions -- 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 1024207] Re: php5-ps segmentation fault on ps_setfont (64bit)
I have the same problem, and I'm happy to see that a fix has been released by Debian, but will this fix be released on either the PECL package page or through the Ubuntu repositories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1024207 Title: php5-ps segmentation fault on ps_setfont (64bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-ps/+bug/1024207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861504] Re: nova-compute-lxc limited by available nbd devices to 16 instances
Yes, if there are more device files than that they will now be used as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861504 Title: nova-compute-lxc limited by available nbd devices to 16 instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/861504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832507] Re: console.log grows indefinitely
It certainly seems like we should only send the last N lines of the console to the user (although that might be computationally expensive to generate on such a large file). That's a separate bug though I suspect. I've filed bug 1081436 for that. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- 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 832507] Re: console.log grows indefinitely
It certainly seems like we should only send the last N lines of the console to the user (although that might be computationally expensive to generate on such a large file). That's a separate bug though I suspect. I've filed bug 1081436 for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/832507 Title: console.log grows indefinitely To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/832507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000710] Re: Attaching volume during instance boot doesn't work
What release was this canonistack region running at the time the problem was seen? ** Changed in: nova Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1000710 Title: Attaching volume during instance boot doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1000710/+subscriptions -- 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 1000710] Re: Attaching volume during instance boot doesn't work
What release was this canonistack region running at the time the problem was seen? ** Changed in: nova Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000710 Title: Attaching volume during instance boot doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1000710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064835] Re: [SRU] keystoneclient fails on SSL certificates that work for other services
** Changed in: python-keystoneclient Importance: Undecided = Critical ** Changed in: python-keystoneclient (Ubuntu) Importance: Undecided = Critical ** Changed in: python-keystoneclient (Ubuntu Quantal) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064835 Title: [SRU] keystoneclient fails on SSL certificates that work for other services To manage notifications about this bug go to: https://bugs.launchpad.net/python-keystoneclient/+bug/1064835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072329] Re: Application 'compiz.desktop' killed by signal 6
Hi guys! This bug is affecting me too. I can't use my system anymore. I have tried the command ubuntu-bug /var/crash/_usr_bin_compiz.1000.crash, but it's not working and is asking to send. It simply stops. What can I do? Kind regards, Still -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072329 Title: Application 'compiz.desktop' killed by signal 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1072329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072329] Re: Application 'compiz.desktop' killed by signal 6
Hi guys! I guess I have figured out how to solve the problem. After I have removed ~/.compiz, ~/.config/compiz*, ~/.gconf* and rebboted, my system works like a charm. What have caused the bug, I have no clue. []'s, Still -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072329 Title: Application 'compiz.desktop' killed by signal 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1072329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072597] Re: open-iscsi has a bug with ubuntu
** Project changed: nova = open-iscsi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072597 Title: open-iscsi has a bug with ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1072597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
** Changed in: nova Importance: Undecided = High ** Changed in: nova/essex Importance: Undecided = High ** Changed in: nova/essex Importance: High = Medium ** Changed in: nova/folsom Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- 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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
** Changed in: nova Importance: Undecided = High ** Changed in: nova/essex Importance: Undecided = High ** Changed in: nova/essex Importance: High = Medium ** Changed in: nova/folsom Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Upstream has chosen not to backport this fix to essex. Can we please consider carrying this patch ourselves? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- 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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
Upstream has chosen not to backport this fix to essex. Can we please consider carrying this patch ourselves? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) = Michael Still (mikalstill) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- 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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
** Also affects: nova Importance: Undecided Status: New ** Changed in: nova Assignee: (unassigned) = Michael Still (mikalstill) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1062314] [NEW] do_refresh_security_group_rules in nova.virt.firewall is very slow
Public bug reported:
This is a bug against stable essex. I have made no attempt to determine
if this is still a problem in Folsom at this stage.
During a sprint this week we took a nova region which was previously
relatively idle and started turning up large numbers of instances using
juju. We started to experience very slow instance starts, which I dug
into. I should note that juju seems to trigger this behaviour by
refreshing security groups when ports are exposed, but other openstack
users will probably experience problems if they are trying to do non-
trivial things with security groups.
It appears that do_refresh_security_group_rules can sometimes take a
very long time to run, and it holds the iptables lock while doing
this. This is a problem because launching a new instance needs to take
the iptables lock, and can end up being blocked. An example slow
instance start (nova logs editted for clarity):
(logs from scheduler node)
2012-10-05 08:06:28 run_instance
2012-10-05 08:06:29 cast to compute node
(logs from compute node)
2012-10-05 08:07:21 Starting instance...
2012-10-05 08:07:34 Starting toXML method
2012-10-05 08:07:43 Finished toXML method
2012-10-05 08:07:43 Called setup_basic_filtering in nwfilter
2012-10-05 08:07:43 Ensuring static filters
2012-10-05 08:08:48 Attempting to grab semaphore iptables for method
_do_refresh_provider_fw_rules...
2012-10-05 08:24:00 Got semaphore iptables for method
_do_refresh_provider_fw_rules...
2012-10-05 08:24:01 Creating image
2012-10-05 08:24:06 Instance is running
2012-10-05 08:25:28 Checking state
2012-10-05 08:25:30 Instance spawned successfully.
I instrumented utils.synchronized to include lock wait and help times
like this (patch against essex):
diff --git a/nova/utils.py b/nova/utils.py
index 6535b06..2e01a15 100644
--- a/nova/utils.py
+++ b/nova/utils.py
@@ -926,10 +926,16 @@ def synchronized(name, external=False):
LOG.debug(_('Attempting to grab semaphore %(lock)s for method '
'%(method)s...') % {'lock': name,
'method': f.__name__})
+started_waiting = time.time()
+
with sem:
LOG.debug(_('Got semaphore %(lock)s for method '
-'%(method)s...') % {'lock': name,
- 'method': f.__name__})
+'%(method)s after %(wait)f second wait...'),
+ {'lock': name,
+ 'method': f.__name__,
+ 'wait': time.time() - started_waiting})
+started_working = time.time()
+
if external and not FLAGS.disable_process_locking:
LOG.debug(_('Attempting to grab file lock %(lock)s for '
'method %(method)s...') %
@@ -945,6 +951,12 @@ def synchronized(name, external=False):
else:
retval = f(*args, **kwargs)
+LOG.debug(_('Released semaphore %(lock)s for method '
+'%(method)s after %(wait)f seconds of use...'),
+ {'lock': name,
+ 'method': f.__name__,
+ 'wait': time.time() - started_working})
+
# If no-one else is waiting for it, delete it.
# See note about possible raciness above.
if not sem.balance 1:
Taking a look at the five longest lock holds in my logs after this patch
is applied, I get:
# grep Released semaphore /var/log/nova/nova-compute.log | grep iptables |
awk '{print$15, $13}' | sort -n | tail -5
192.134270 do_refresh_security_group_rules
194.140478 do_refresh_security_group_rules
194.153729 do_refresh_security_group_rules
201.135854 do_refresh_security_group_rules
297.725837 do_refresh_security_group_rules
So I then instrumented do_refresh_security_group_rules to try and see
what was slow. I used this patch (which I know is horrible):
diff --git a/nova/virt/firewall.py b/nova/virt/firewall.py
index f0f1594..99f580a 100644
--- a/nova/virt/firewall.py
+++ b/nova/virt/firewall.py
@@ -17,6 +17,8 @@
#License for the specific language governing permissions and limitations
#under the License.
+import time
+
from nova import context
from nova import db
from nova import flags
@@ -167,16 +169,35 @@ class IptablesFirewallDriver(FirewallDriver):
self.iptables.ipv6['filter'].add_rule(chain_name, rule)
def add_filters_for_instance(self, instance):
+start_time = time.time()
network_info = self.network_infos[instance['id']]
+LOG.debug(_('Get network info took %f seconds'),
+ time.time() - start_time)
+
+start_time = time.time()
chain_name = self._instance_chain_name(instance)
+LOG.debug(_('Get chain name took %f seconds'),
+ time.time() - start_time)
+
+start_time = time.time
[Bug 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
I think the issue here is that nova.virt.firewall.py IptablesFirewallDriver.instance_rules() is calling get_instance_nw_info() which is causing rpcs to be fired off _while_still_holding_the_iptables_lock. I suspect that the rpcs need to happen outside the lock. From yet more instrumented code: A synchronous RPC call is being made while a lock is held. This is probably a bug. Please report it. Include lines following this that start with ** please. ** multicall ** call ** call ** call ** get_instance_nw_info ** instance_rules ** add_filters_for_instance ** do_refresh_security_group_rules ** inner_while_holding_lock ** refresh_security_group_members ** refresh_security_group_members ** refresh_security_group_members ** wrapped ** _process_data ** wrapped ** _spawn_n_impl ** end of stack trace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1062314/+subscriptions -- 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 1062314] [NEW] do_refresh_security_group_rules in nova.virt.firewall is very slow
Public bug reported:
This is a bug against stable essex. I have made no attempt to determine
if this is still a problem in Folsom at this stage.
During a sprint this week we took a nova region which was previously
relatively idle and started turning up large numbers of instances using
juju. We started to experience very slow instance starts, which I dug
into. I should note that juju seems to trigger this behaviour by
refreshing security groups when ports are exposed, but other openstack
users will probably experience problems if they are trying to do non-
trivial things with security groups.
It appears that do_refresh_security_group_rules can sometimes take a
very long time to run, and it holds the iptables lock while doing
this. This is a problem because launching a new instance needs to take
the iptables lock, and can end up being blocked. An example slow
instance start (nova logs editted for clarity):
(logs from scheduler node)
2012-10-05 08:06:28 run_instance
2012-10-05 08:06:29 cast to compute node
(logs from compute node)
2012-10-05 08:07:21 Starting instance...
2012-10-05 08:07:34 Starting toXML method
2012-10-05 08:07:43 Finished toXML method
2012-10-05 08:07:43 Called setup_basic_filtering in nwfilter
2012-10-05 08:07:43 Ensuring static filters
2012-10-05 08:08:48 Attempting to grab semaphore iptables for method
_do_refresh_provider_fw_rules...
2012-10-05 08:24:00 Got semaphore iptables for method
_do_refresh_provider_fw_rules...
2012-10-05 08:24:01 Creating image
2012-10-05 08:24:06 Instance is running
2012-10-05 08:25:28 Checking state
2012-10-05 08:25:30 Instance spawned successfully.
I instrumented utils.synchronized to include lock wait and help times
like this (patch against essex):
diff --git a/nova/utils.py b/nova/utils.py
index 6535b06..2e01a15 100644
--- a/nova/utils.py
+++ b/nova/utils.py
@@ -926,10 +926,16 @@ def synchronized(name, external=False):
LOG.debug(_('Attempting to grab semaphore %(lock)s for method '
'%(method)s...') % {'lock': name,
'method': f.__name__})
+started_waiting = time.time()
+
with sem:
LOG.debug(_('Got semaphore %(lock)s for method '
-'%(method)s...') % {'lock': name,
- 'method': f.__name__})
+'%(method)s after %(wait)f second wait...'),
+ {'lock': name,
+ 'method': f.__name__,
+ 'wait': time.time() - started_waiting})
+started_working = time.time()
+
if external and not FLAGS.disable_process_locking:
LOG.debug(_('Attempting to grab file lock %(lock)s for '
'method %(method)s...') %
@@ -945,6 +951,12 @@ def synchronized(name, external=False):
else:
retval = f(*args, **kwargs)
+LOG.debug(_('Released semaphore %(lock)s for method '
+'%(method)s after %(wait)f seconds of use...'),
+ {'lock': name,
+ 'method': f.__name__,
+ 'wait': time.time() - started_working})
+
# If no-one else is waiting for it, delete it.
# See note about possible raciness above.
if not sem.balance 1:
Taking a look at the five longest lock holds in my logs after this patch
is applied, I get:
# grep Released semaphore /var/log/nova/nova-compute.log | grep iptables |
awk '{print$15, $13}' | sort -n | tail -5
192.134270 do_refresh_security_group_rules
194.140478 do_refresh_security_group_rules
194.153729 do_refresh_security_group_rules
201.135854 do_refresh_security_group_rules
297.725837 do_refresh_security_group_rules
So I then instrumented do_refresh_security_group_rules to try and see
what was slow. I used this patch (which I know is horrible):
diff --git a/nova/virt/firewall.py b/nova/virt/firewall.py
index f0f1594..99f580a 100644
--- a/nova/virt/firewall.py
+++ b/nova/virt/firewall.py
@@ -17,6 +17,8 @@
#License for the specific language governing permissions and limitations
#under the License.
+import time
+
from nova import context
from nova import db
from nova import flags
@@ -167,16 +169,35 @@ class IptablesFirewallDriver(FirewallDriver):
self.iptables.ipv6['filter'].add_rule(chain_name, rule)
def add_filters_for_instance(self, instance):
+start_time = time.time()
network_info = self.network_infos[instance['id']]
+LOG.debug(_('Get network info took %f seconds'),
+ time.time() - start_time)
+
+start_time = time.time()
chain_name = self._instance_chain_name(instance)
+LOG.debug(_('Get chain name took %f seconds'),
+ time.time() - start_time)
+
+start_time = time.time
[Bug 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
I think the issue here is that nova.virt.firewall.py IptablesFirewallDriver.instance_rules() is calling get_instance_nw_info() which is causing rpcs to be fired off _while_still_holding_the_iptables_lock. I suspect that the rpcs need to happen outside the lock. From yet more instrumented code: A synchronous RPC call is being made while a lock is held. This is probably a bug. Please report it. Include lines following this that start with ** please. ** multicall ** call ** call ** call ** get_instance_nw_info ** instance_rules ** add_filters_for_instance ** do_refresh_security_group_rules ** inner_while_holding_lock ** refresh_security_group_members ** refresh_security_group_members ** refresh_security_group_members ** wrapped ** _process_data ** wrapped ** _spawn_n_impl ** end of stack trace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1062314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059899] Re: nova fails to configure dnsmasq, resulting in DNS timeouts in instances
** Tags added: ops -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1059899 Title: nova fails to configure dnsmasq, resulting in DNS timeouts in instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1059899/+subscriptions -- 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 1059899] Re: nova fails to configure dnsmasq, resulting in DNS timeouts in instances
** Tags added: ops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059899 Title: nova fails to configure dnsmasq, resulting in DNS timeouts in instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1059899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020313] Re: openstack-dashboard hijacks the web root
Another option would be to create a vhost for the dashboard. ** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1020313 Title: openstack-dashboard hijacks the web root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1020313/+subscriptions -- 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 1036918] [NEW] Switching between regions causes login form to appear at the bottom of the page
Public bug reported: I have to regions configured in /etc/openstack- dashboard/local_settings.py. If I switch between them in the drop down at the top right of the screen, a login dialog appears at the bottom of the page which is quite confusing. Some thoughts: - credentials from the previous region should be retried in the new region. They might be the same. - the login form should be a popup as if the page is long you don't notice it appearing at the bottom of the screen. I'll attach a screenshot to this bug report. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1036918 Title: Switching between regions causes login form to appear at the bottom of the page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036918/+subscriptions -- 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 1036918] Re: Switching between regions causes login form to appear at the bottom of the page
** Attachment added: login-bug.png https://bugs.launchpad.net/bugs/1036918/+attachment/3261487/+files/login-bug.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1036918 Title: Switching between regions causes login form to appear at the bottom of the page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036918/+subscriptions -- 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 1036919] [NEW] Region drop down showing incorrect region
Public bug reported: Hi. We have two regions configured in /etc/openstack- dashboard/local_settings.py. A user changed regions with the drop down, logged into the new region, and started an instance. The instance started in the _previous_ region. I'm not sure what debugging information to provide here, as I didn't see anything obvious in the logs. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1036919 Title: Region drop down showing incorrect region To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036919/+subscriptions -- 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 1020313] Re: openstack-dashboard hijacks the web root
Another option would be to create a vhost for the dashboard. ** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020313 Title: openstack-dashboard hijacks the web root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1020313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036918] [NEW] Switching between regions causes login form to appear at the bottom of the page
Public bug reported: I have to regions configured in /etc/openstack- dashboard/local_settings.py. If I switch between them in the drop down at the top right of the screen, a login dialog appears at the bottom of the page which is quite confusing. Some thoughts: - credentials from the previous region should be retried in the new region. They might be the same. - the login form should be a popup as if the page is long you don't notice it appearing at the bottom of the screen. I'll attach a screenshot to this bug report. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036918 Title: Switching between regions causes login form to appear at the bottom of the page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036918] Re: Switching between regions causes login form to appear at the bottom of the page
** Attachment added: login-bug.png https://bugs.launchpad.net/bugs/1036918/+attachment/3261487/+files/login-bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036918 Title: Switching between regions causes login form to appear at the bottom of the page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036919] [NEW] Region drop down showing incorrect region
Public bug reported: Hi. We have two regions configured in /etc/openstack- dashboard/local_settings.py. A user changed regions with the drop down, logged into the new region, and started an instance. The instance started in the _previous_ region. I'm not sure what debugging information to provide here, as I didn't see anything obvious in the logs. ** Affects: horizon (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036919 Title: Region drop down showing incorrect region To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1036919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 904532] Re: Provide a script to automate cleanup of _base
Bolke -- that's not currently the case. If you want this functionality you should file a separate bug for it. However, with a shared instances directory you're best off disabling the cache manager entirely at the moment. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/904532 Title: Provide a script to automate cleanup of _base To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/904532/+subscriptions -- 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 1018244] Re: When keystone is enabled, the ec2 API returns uuids instead of tenant names
Looking at the ec2 api code, this is pretty consistent for all these calls -- you'll get the uuid (with keystone) or the project id (without keystone) in all cases. This is consistent with the ec2 api specification, which says this field should be: ownerId The ID of the AWS account that owns the reservation. They examples have large numbers as values, so this isn't meant to be a human readable value. That's unfortunate, given euca2ools doesn't try to do the lookup to turn this into one. I'm going to close this bug as invalid though, as it is what the spec intends for this call. ** Changed in: nova Status: Confirmed = Invalid ** Changed in: nova (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1018244 Title: When keystone is enabled, the ec2 API returns uuids instead of tenant names To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1018244/+subscriptions -- 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 904532] Re: Provide a script to automate cleanup of _base
Bolke -- that's not currently the case. If you want this functionality you should file a separate bug for it. However, with a shared instances directory you're best off disabling the cache manager entirely at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904532 Title: Provide a script to automate cleanup of _base To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/904532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1018244] Re: When keystone is enabled, the ec2 API returns uuids instead of tenant names
Looking at the ec2 api code, this is pretty consistent for all these calls -- you'll get the uuid (with keystone) or the project id (without keystone) in all cases. This is consistent with the ec2 api specification, which says this field should be: ownerId The ID of the AWS account that owns the reservation. They examples have large numbers as values, so this isn't meant to be a human readable value. That's unfortunate, given euca2ools doesn't try to do the lookup to turn this into one. I'm going to close this bug as invalid though, as it is what the spec intends for this call. ** Changed in: nova Status: Confirmed = Invalid ** Changed in: nova (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1018244 Title: When keystone is enabled, the ec2 API returns uuids instead of tenant names To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1018244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1018586] Re: cleanup_file_locks does not remove stale sentinel files
** Tags added: canonistack ops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1018586 Title: cleanup_file_locks does not remove stale sentinel files To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1018586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006671] Re: swift command has unhelpful manpage
** Tags added: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006671 Title: swift command has unhelpful manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1006671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019913] Re: Lazy load of attribute fails for instance_type.rxtx_factor
We have now observed this error on two testing clusters, so I don't think this is because we're running precise-proposed in one any more. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1019913 Title: Lazy load of attribute fails for instance_type.rxtx_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1019913/+subscriptions -- 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 1019913] Re: Lazy load of attribute fails for instance_type.rxtx_factor
We have now observed this error on two testing clusters, so I don't think this is because we're running precise-proposed in one any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019913 Title: Lazy load of attribute fails for instance_type.rxtx_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1019913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019913] [NEW] Lazy load of attribute fails for instance_type.rxtx_factor
Public bug reported: Running proposed on one of our clusters, I see the following with instances started via juju. I have been unable to re-create the problem with raw ec2 commands. [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Ensuring static filters [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Instance failed to spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Traceback (most recent call last): [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 598, in _spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self._legacy_nw_info(network_info), block_device_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return f(*args, **kw) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 921, in spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self.firewall_driver.prepare_instance_filter(instance, network_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 136, in prepare_instance_filter [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self.add_filters_for_instance(instance) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 178, in add_filters_for_instance [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] ipv4_rules, ipv6_rules = self.instance_rules(instance, network_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 335, in instance_rules [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] instance) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/network/api.py, line 213, in get_instance_nw_info [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] 'rxtx_factor': instance['instance_type']['rxtx_factor'], [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/models.py, line 75, in __getitem__ [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return getattr(self, key) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/attributes.py, line 168, in __get__ [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return self.impl.get(instance_state(instance),dict_) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/attributes.py, line 453, in get [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] value = self.callable_(state, passive) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/strategies.py, line 485, in _load_for_state [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] (mapperutil.state_str(state), key) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] DetachedInstanceError: Parent instance Instance at 0x45f6350 is not bound to a Session; lazy load operation of attribute 'instance_type' cannot proceed [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1019913 Title: Lazy load of attribute fails for instance_type.rxtx_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1019913/+subscriptions -- 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 1019913] [NEW] Lazy load of attribute fails for instance_type.rxtx_factor
Public bug reported: Running proposed on one of our clusters, I see the following with instances started via juju. I have been unable to re-create the problem with raw ec2 commands. [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Ensuring static filters [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Instance failed to spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] Traceback (most recent call last): [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 598, in _spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self._legacy_nw_info(network_info), block_device_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return f(*args, **kw) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 921, in spawn [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self.firewall_driver.prepare_instance_filter(instance, network_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 136, in prepare_instance_filter [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] self.add_filters_for_instance(instance) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 178, in add_filters_for_instance [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] ipv4_rules, ipv6_rules = self.instance_rules(instance, network_info) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/virt/firewall.py, line 335, in instance_rules [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] instance) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/network/api.py, line 213, in get_instance_nw_info [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] 'rxtx_factor': instance['instance_type']['rxtx_factor'], [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/models.py, line 75, in __getitem__ [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return getattr(self, key) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/attributes.py, line 168, in __get__ [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] return self.impl.get(instance_state(instance),dict_) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/attributes.py, line 453, in get [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] value = self.callable_(state, passive) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] File /usr/lib/python2.7/dist-packages/sqlalchemy/orm/strategies.py, line 485, in _load_for_state [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] (mapperutil.state_str(state), key) [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] DetachedInstanceError: Parent instance Instance at 0x45f6350 is not bound to a Session; lazy load operation of attribute 'instance_type' cannot proceed [instance: d6c8c7e9-aa9d-461c-b7a5-92b993382bb0] ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019913 Title: Lazy load of attribute fails for instance_type.rxtx_factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1019913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1018244] [NEW] When keystone is enabled, the ec2 API returns uuids instead of tenant names
Public bug reported: Before we turned on keystone, euca-describe-instances used to include the names of user's projects in its output. It now lists the uuid of the tenant instead, which isn't super helpful when trying to work out who owns what. Can we please translate this back to a human readable name? An example: RESERVATION r-x2tdg0ga c519923c921a404c96ebc8210a4ec67a juju-canonistack2, juju-canonistack2-2 INSTANCEi-0083 ami-00bfserver-131 server-131 running None (BANANAc921a404c96ebc8210a4ec67a, alce)0 m1.small 2012-06-27T04:12:42.000Znova BANANAc921a404c96ebc8210a4ec67a is the UUID of a tenant. ** Affects: keystone (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1018244 Title: When keystone is enabled, the ec2 API returns uuids instead of tenant names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1018244/+subscriptions -- 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 1018244] [NEW] When keystone is enabled, the ec2 API returns uuids instead of tenant names
Public bug reported: Before we turned on keystone, euca-describe-instances used to include the names of user's projects in its output. It now lists the uuid of the tenant instead, which isn't super helpful when trying to work out who owns what. Can we please translate this back to a human readable name? An example: RESERVATION r-x2tdg0ga c519923c921a404c96ebc8210a4ec67a juju-canonistack2, juju-canonistack2-2 INSTANCEi-0083 ami-00bfserver-131 server-131 running None (BANANAc921a404c96ebc8210a4ec67a, alce)0 m1.small 2012-06-27T04:12:42.000Znova BANANAc921a404c96ebc8210a4ec67a is the UUID of a tenant. ** Affects: keystone (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1018244 Title: When keystone is enabled, the ec2 API returns uuids instead of tenant names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1018244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973941] [NEW] Recommend the correct package for the glance client
Public bug reported: I went to run the glance command line client on one of my machines, but it wasn't installed. I got: $ glance index 'The program 'glance' is currently not installed. You can install it by typing: apt-get install glance-common However, glance-common was installed. It turns out that the glance command line client is in the glance-client package. Can you please update the package recommender? ** Affects: glance (Ubuntu) Importance: Undecided Status: New ** Tags: canonistack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973941 Title: Recommend the correct package for the glance client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/973941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] Re: Virtualbox reboots system after precise upgrade
The process of trying both univere and virtualbox.org versions involved uninstalling the package, which removed the kernel module virtualbox needs to work. Now I am having trouble getting the kernel module for oneiric's kernel back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] Re: Virtualbox reboots system after precise upgrade
I've been using virtualbox for a while under oneiric and it hasn't had problems, so I do suspect this is a precise kernel issue. I ran stress for 40 minutes, and the machine was clearly working hard... The fans were going full. sensors at the end said: $ sensors k10temp-pci-00c3 Adapter: PCI adapter temp1:+43.4°C (high = +70.0°C) No machine reboot though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] Re: Virtualbox reboots system after precise upgrade
** Package changed: ubuntu = virtualbox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] Re: Virtualbox reboots system after precise upgrade
And here's the syslog from that period. The inverter entries are from my solar panels, you can ignore them. ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+attachment/2715499/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] Re: Virtualbox reboots system after precise upgrade
$ sudo apt-get install lm-sensors [sudo] password for mikal: Reading package lists... Done Building dependency tree Reading state information... Done lm-sensors is already the newest version. The following packages were automatically installed and are no longer required: python-mox dnsmasq-utils Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 108 not upgraded. $ sudo modprobe coretemp FATAL: Error inserting coretemp (/lib/modules/3.2.0-12-generic-pae/kernel/drivers/hwmon/coretemp.ko): No such device Instead of a watch, I wrote a simple script which wrote the temperature out to a file. The output is attached. The virtual machine was started at 15:02:35... ** Attachment added: temps https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+attachment/2715498/+files/temps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926526] [NEW] Virtualbox reboots system after precise upgrade
Public bug reported: I upgraded my workstation (an AMD64 machine with virtualization extensions) to precise. Now when I run virtualbox virtual machines, the workstation reboots within about a minute of starting the virtual machine. This happens with both the virtualbox from universe, as well as the one from virtualbox.org. ** Affects: 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/926526 Title: Virtualbox reboots system after precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/926526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915977] [NEW] Add policy.json to packages
Public bug reported: Nova now requires a policy.json file in /etc/nova/. Update the packages to install this file which is in the source tree. (This is an attempt to move https://bugs.launchpad.net/nova/+bug/915614 to the right place). ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/915977 Title: Add policy.json to packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/915977/+subscriptions -- 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 915971] [NEW] New command guestmount
Public bug reported: The latest nova-compute adds a new command which needs sudo privs: 2012-01-13 22:24:27,385 DEBUG nova.utils [-] Running cmd (subprocess): sudo guestmount --rw -a /var/lib/nova/instances/instance-000c/disk -m /dev/sda1 /tmp/tmpXrLkev from (pid=2743) execute /data/backups- meta/linux/x220/data/src/openstack/nova/nova/utils.py:201 This command is not set up in /etc/sudoers.d/nova_sudoers, and therefore my test instance prompts for the password. Interestingly I can't find the command guestmount packaged anywhere, so I'm not sure what its meant to be doing. The code to call guestmount seems to have been around for a while, so I'm not sure why this is only just coming up now. Perhaps I only just noticed it. I see that guestmount is packaged for precise, but not for oneiric. ** Affects: nova (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/915971 Title: New command guestmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/915971/+subscriptions -- 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 915977] [NEW] Add policy.json to packages
Public bug reported: Nova now requires a policy.json file in /etc/nova/. Update the packages to install this file which is in the source tree. (This is an attempt to move https://bugs.launchpad.net/nova/+bug/915614 to the right place). ** Affects: nova (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/915977 Title: Add policy.json to packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/915977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 915971] [NEW] New command guestmount
Public bug reported: The latest nova-compute adds a new command which needs sudo privs: 2012-01-13 22:24:27,385 DEBUG nova.utils [-] Running cmd (subprocess): sudo guestmount --rw -a /var/lib/nova/instances/instance-000c/disk -m /dev/sda1 /tmp/tmpXrLkev from (pid=2743) execute /data/backups- meta/linux/x220/data/src/openstack/nova/nova/utils.py:201 This command is not set up in /etc/sudoers.d/nova_sudoers, and therefore my test instance prompts for the password. Interestingly I can't find the command guestmount packaged anywhere, so I'm not sure what its meant to be doing. The code to call guestmount seems to have been around for a while, so I'm not sure why this is only just coming up now. Perhaps I only just noticed it. I see that guestmount is packaged for precise, but not for oneiric. ** Affects: nova (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/915971 Title: New command guestmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/915971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 904532] Re: Provide a script to automate cleanup of _base
I have just send a patch for review which implements the _base cleanup aspects of the blueprint. Its integrated into the nova compute manager, as opposed to being a separate script. https://review.openstack.org/#change,2902 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/904532 Title: Provide a script to automate cleanup of _base To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/904532/+subscriptions -- 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 904532] Re: Provide a script to automate cleanup of _base
I have just send a patch for review which implements the _base cleanup aspects of the blueprint. Its integrated into the nova compute manager, as opposed to being a separate script. https://review.openstack.org/#change,2902 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904532 Title: Provide a script to automate cleanup of _base To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/904532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907533] [NEW] URLs fail to appear in logs and desktop notifications
Public bug reported: Hi. I've just noticed that URLs are not logged for IRC sessions correctly (they are skipped entirely). They also don't appear in gnome notifications. This problem appears to be fixed in upstream, with commit 370f2550ba89ba01ad396e0fd7967a4fd0414a49. This commit is nearly a year old. I have confirm that the current source package for smuxi lacks this diff. Could this package please be updated? Thanks, Mikal ** Affects: smuxi (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/907533 Title: URLs fail to appear in logs and desktop notifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smuxi/+bug/907533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 904532] [NEW] Provide a script to automate cleanup of _base
Public bug reported: The nova base instance directory $instances_path/_base is never cleaned up. This caused one of my compute nodes to run out of disk recently, even though a bunch of the images there were no longer in use. There appear to be homebrew cleanup scripts online, such as https://github.com/Razique/BashStuff/blob/master/SCR_5008_V00_NUAC- OPENSTACK-Nova-compute-images-prunning.sh . Please provide a script to perform cleanup in the package. ** Affects: nova (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/904532 Title: Provide a script to automate cleanup of _base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/904532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813342] [NEW] does not import stream from DVD media; Internal GStreamer problem; file a bug
Public bug reported: I imported music from a removable media, to rhythmbox. this error cam back on over half of the selections, all of which are in MP3 format. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libgstreamer0.10-0 0.10.32-3ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Wed Jul 20 02:12:16 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813342 Title: does not import stream from DVD media; Internal GStreamer problem; file a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/813342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813342] Re: does not import stream from DVD media; Internal GStreamer problem; file a bug
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813342 Title: does not import stream from DVD media; Internal GStreamer problem; file a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/813342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614176] Re: [855gm] 2.6.35-14: Invisible Cursor
same problem on Thinkpad X40 last good kernel was 2.6.35-13-generic. 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) -- [855gm] 2.6.35-14: Invisible Cursor https://bugs.launchpad.net/bugs/614176 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 57315] Re: loading hdaps fails on a Thinkpad Z60m (and W500)
I'm running Lucid Beta, on at T400, and this script: http://homepage.univie.ac.at/s.hammer/install_hdapsd worked absolutely flawlessly for me. I installed tp_smapi before, I don't know if that'd make a difference, but things are currently working beautifully. It even installed the panel applet for me. -- loading hdaps fails on a Thinkpad Z60m (and W500) https://bugs.launchpad.net/bugs/57315 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 524454] Re: Networking is disabled on boot
My Network Manager is disabled on boot, and I can gonfirm that in NetworkManager.state NetworkingEnabled is set to true. I still have to right click- enable networking on boot. -- Networking is disabled on boot https://bugs.launchpad.net/bugs/524454 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 395932] Re: [i855] No Xv support for 82852/855GM (KMS bug)
Hello, on my Thinkpad X40 I have same problem. Jut for information, I am using latest 2.6.32 kernel from kernel-ppa and latest intel drivers from xorg- edgers ppa. (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor=X.Org Foundation (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, (II) intel(0): Creating default Display subsection in Screen section Builtin Default intel Screen 0 for depth/fbbpp 24/32 (==) intel(0): Depth 24, (--) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 855GME (--) intel(0): Chipset: 852GM/855GM (==) intel(0): video overlay key set to 0x101fe (II) intel(0): Output VGA1 has no monitor section (II) intel(0): Output LVDS1 has no monitor section (II) intel(0): found backlight control interface /sys/class/backlight/thinkpad_screen (II) intel(0): EDID for output VGA1 (II) intel(0): EDID for output LVDS1 (II) intel(0): Output VGA1 disconnected (II) intel(0): Output LVDS1 connected (II) intel(0): Using exact sizes for initial modes (II) intel(0): Output LVDS1 using initial mode 1024x768 (==) intel(0): Using gamma correction (1.0, 1.0, 1.0) (==) intel(0): DPI set to (96, 96) (II) intel(0): [DRI2] Setup complete (**) intel(0): Tiling enabled (**) intel(0): SwapBuffers wait enabled (==) intel(0): VideoRam: 131072 KB (II) intel(0): Attempting memory allocation with tiled buffers. (II) intel(0): Tiled allocation successful. (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): No memory allocations (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (II) intel(0): DPMS enabled (WW) intel(0): Disabling Xv because no adaptors could be initialized. (II) intel(0): direct rendering: DRI2 Enabled And second bug, with new Intel driver nomodeset option cause failing of Xserver start: ... (II) LoadModule: intel (II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor=X.Org Foundation (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, (EE) intel(0): No kernel modesetting driver detected. (II) UnloadModule: intel (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found -- [i855] No Xv support for 82852/855GM (KMS bug) https://bugs.launchpad.net/bugs/395932 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
