[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms
1.2.2-0ubuntu13.1.21 Having 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/1393842 Title: libvirt does not grant qemu-guest-agent channel perms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Is this gonna be fixed in official Ubuntu 17.04 repos ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1682744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Not exactly the same problem, but also a firmware bug that happens every time the machine wakes up from suspend (the network is 2.5GHz) [156613.591071] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [156613.593630] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.594645] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.634984] Bluetooth: hci0: read Intel version: 370710018002030d00 [156613.636114] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [156613.802489] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.803084] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.831206] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [156613.844398] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.845047] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156613.847005] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated [156614.054828] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156614.055507] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [156614.077241] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [156614.140494] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [156616.413449] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [156616.492565] wlan0: authenticate with e4:8d:8c:61:7d:04 [156616.495338] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. [156616.495344] iwlwifi :02:00.0: CSR values: [156616.495346] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [156616.495377] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X40489204 [156616.495441] iwlwifi :02:00.0: CSR_INT_COALESCING: 0X8040 [156616.495582] iwlwifi :02:00.0: CSR_INT: 0X [156616.495637] iwlwifi :02:00.0:CSR_INT_MASK: 0X [156616.495692] iwlwifi :02:00.0: CSR_FH_INT_STATUS: 0X [156616.495747] iwlwifi :02:00.0: CSR_GPIO_IN: 0X [156616.495803] iwlwifi :02:00.0: CSR_RESET: 0X [156616.495858] iwlwifi :02:00.0:CSR_GP_CNTRL: 0X080403cd [156616.495912] iwlwifi :02:00.0: CSR_HW_REV: 0X0144 [156616.495967] iwlwifi :02:00.0: CSR_EEPROM_REG: 0X [156616.496023] iwlwifi :02:00.0: CSR_EEPROM_GP: 0X8000 [156616.496078] iwlwifi :02:00.0: CSR_OTP_GP_REG: 0X803a [156616.496134] iwlwifi :02:00.0: CSR_GIO_REG: 0X001f0042 [156616.496189] iwlwifi :02:00.0:CSR_GP_UCODE_REG: 0X [156616.496244] iwlwifi :02:00.0: CSR_GP_DRIVER_REG: 0X [156616.496299] iwlwifi :02:00.0: CSR_UCODE_DRV_GP1: 0X [156616.496355] iwlwifi :02:00.0: CSR_UCODE_DRV_GP2: 0X [156616.496410] iwlwifi :02:00.0: CSR_LED_REG: 0X0060 [156616.496475] iwlwifi :02:00.0:CSR_DRAM_INT_TBL_REG: 0X88211e3b [156616.496615] iwlwifi :02:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [156616.496670] iwlwifi :02:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 [156616.496725] iwlwifi :02:00.0: CSR_MONITOR_STATUS_REG: 0X3d0801bd [156616.496780] iwlwifi :02:00.0: CSR_HW_REV_WA_REG: 0X0001001a [156616.496835] iwlwifi :02:00.0:CSR_DBG_HPET_MEM_REG: 0X [156616.496837] iwlwifi :02:00.0: FH register values: [156616.496892] iwlwifi :02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X21266b00 [156616.496947] iwlwifi :02:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X02126550 [156616.497002] iwlwifi :02:00.0: FH_RSCSR_CHNL0_WPTR: 0X0070 [156616.497057] iwlwifi :02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [156616.497112] iwlwifi :02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [156616.497167] iwlwifi :02:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [156616.497223] iwlwifi :02:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [156616.497278] iwlwifi :02:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [156616.497333] iwlwifi :02:00.0: FH_TSSR_TX_ERROR_REG: 0X [156616.497486] iwlwifi :02:00.0: Start IWL Error Log Dump: [156616.497489] iwlwifi :02:00.0: Status: 0x, count: 6 [156616.497491] iwlwifi :02:00.0: Loaded firmware version: 17.459231.0 [156616.497494] iwlwifi :02:00.0: 0x14FD | ADVANCED_SYSASSERT [156616.497496] iwlwifi :02:00.0: 0x02E0 | trm_hw_status0 [156616.497498] iwlwifi :02:00.0: 0x | trm_hw_status1 [156616.497500] iwlwifi :02:00.0: 0x0B30 | branchlink2 [156616.497503] iwlwifi :02:00.0: 0x000164C0 | interruptlink1 [156616.497505] iwlwifi :02:00.0: 0x | interruptlink2 [156616.497507] iwlwifi :02:00.0: 0xDEADBEEF | data1 [156616.497509] iwlwifi :02:00.0: 0xDEADBEEF | data2 [156616
[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Related: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1673344 Related: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1674159 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260
Same machine booted into Widows 10 works well with this wireless 5GHz network -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682744] Re: Connecting to wifi 5GHz network causes iwlwifi driver error
On the same wifi 5GHz network another linux machine (with Intel® Centrino® Advanced-N 6235 adapter) running Zesty works fine. Other mobile devices (including windows computers) work well with this network. ** Summary changed: - Connecting to wifi 5GHz network causes iwlwifi driver error + Connecting to wifi 5GHz network causes iwlwifi driver error. Intel Wireless 7260 ** Summary changed: - Connecting to wifi 5GHz network causes iwlwifi driver error. Intel Wireless 7260 + Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682744 Title: Connecting to wifi 5GHz network causes iwlwifi firmware/driver error. Intel Wireless 7260 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1682744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682744] [NEW] Connecting to wifi 5GHz network causes iwlwifi driver error
Public bug reported: Only happens when connecting to 5GHz network, 2.5 GHz work fine. Network controller: Intel Corporation Wireless 7260 (rev 6b) iwlwifi :02:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4289] device (wlan0): Activation: starting connection 'NewHibernia5' (104460fe-9e5b-4a8c-8735-cfe48dec488e) апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4290] audit: op="connection-activate" uuid="104460fe-9e5b-4a8c-8735-cfe48dec488e" name="NewHibernia5" pid=7054 uid=1000 result="success" апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4291] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4293] manager: NetworkManager state is now CONNECTING апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4339] device (wlan0): set-hw-addr: set-cloned MAC address to E8:2A:EA:D4:16:6F (permanent) апр 14 10:32:34 liasus kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4381] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4383] device (wlan0): Activation: (wifi) access point 'NewHibernia5' has security, but secrets are required. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4384] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4433] device (wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4438] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0] апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4450] device (wlan0): Activation: (wifi) connection 'NewHibernia5' has security, and secrets exist. No new secrets needed. апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'ssid' value 'NewHibernia5' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4451] Config: added 'scan_ssid' value '1' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'key_mgmt' value 'WPA-PSK' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'auth_alg' value 'OPEN' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4452] Config: added 'psk' value '' апр 14 10:32:34 liasus NetworkManager[1435]: [1492155154.4654] sup-iface[0x55900cef86c0,wlan0]: config: set interface ap_scan to 1 апр 14 10:32:34 liasus wpa_supplicant[1923]: wlan0: SME: Trying to authenticate with e4:8d:8c:61:7d:04 (SSID='NewHibernia5' freq=5280 MHz) апр 14 10:32:34 liasus kernel: wlan0: authenticate with e4:8d:8c:61:7d:04 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR values: апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_IF_CONFIG_REG: 0X40489204 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_COALESCING: 0X8000ff40 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_INT_MASK: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_FH_INT_STATUS: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GPIO_IN: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_RESET: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GP_CNTRL: 0X080403cd апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_HW_REV: 0X0144 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_REG: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_EEPROM_GP: 0X8000 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_OTP_GP_REG: 0X803a апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GIO_REG: 0X001f0042 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GP_UCODE_REG: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_GP_DRIVER_REG: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_UCODE_DRV_GP1: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_UCODE_DRV_GP2: 0X апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_LED_REG: 0X0060 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0: CSR_DRAM_INT_TBL_REG: 0X882142c7 апр 14 10:32:34 liasus kernel: iwlwifi :02:00.0:
[Bug 1274320] Re: Error: diskfilter writes are not supported
I ended up with the following workaround: When setting up the server i configured the following: 0. RAID 10 on /sda /sdb /sdc /sdd 1. /boot / and swap partition are on RAID but NOT IN LVM VOLUME 2. Rest of the RAID space - LVM partition At the end of install, when you get error message: Install grub manually on /sda1 and /sda2 (/sda3 and /sda4 will not let you, cause they're striped) use console to run: # update-grub # grub-install /dev/sda1 # grub-install /dev/sda2 Return to setup and skip installation of grub (you installed it manally) Hope that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274320 Title: Error: diskfilter writes are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524016] Re: Xorg crash
Christopher, thanks for reply. Unfortunately, I don't have the original system the bug was reported for anymore, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524016 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1524016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1274320] Re: Error: diskfilter writes are not supported
Problens with installing latest 14.04.3 I Have tried every solution mentioned in this thread and no luck. Grub would not install... HP server with 4 SATA disks, RAID 10 (md0) with /boot and / on it, No LVM installing with: update-grub - works fine grub-install /dev/md0 - fails Went up to grub version 2.02~beta2-32ubuntu1 latest from XENIAL still getting diskfilter error ... nothing helps. Any ideas, anyone ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274320 Title: Error: diskfilter writes are not supported To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1274320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524016] [NEW] Xorg crash
Public bug reported: Trusty under KVM ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9 Uname: Linux 3.19.0-39-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Dec 8 17:25:39 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic root=UUID=a22fcb14-fd0c-4f7f-8d95-67434d8c2e47 ro console=tty1 console=ttyS0 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-trusty:cvnBochs:ct1:cvr: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-trusty dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Dec 8 17:24:33 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: cirrus: The PCI device 0xb8 at 00@00:02:0 has a kernel module claiming it. cirrus: This driver cannot operate until it has been unloaded. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: modesetting ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524016 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1524016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Martin Pitt, I've commented the tmpfs lines in /etc/fstab and now the system starts perfectly with systemd. Thanks a lot for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: boot failure when mounting /var/lock as a tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
** Attachment added: "fstab" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399332/+files/fstab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+attachment/4399331/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Martin Pitt, Attaching files that you requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Christopher M. Penalver, I used a spare HDD to install a clean Vivid and it works well. I works well even after installation of proprietary Nvidia driver. So, is there anything that can be done to repair the upgraded system, or using upstart configuration is the only option ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] Re: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Christopher M. Penalver, that's something I cannot test ATM, as it would require reformating my laptop and installing a fresh Vivid from scratch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452717] [NEW] Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd
Public bug reported: Problem happens when choosing a normal boot. Works ok when choosing upstart. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 16:05:34 2015 DistUpgraded: 2015-05-04 19:38:58,878 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-36-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-16-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-16-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1742] InstallationDate: Installed on 2011-11-22 (1261 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. K43SJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=a53c1bea-08c0-42d6-89f3-c243463ce80f ro quiet splash elevator=noop SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-04 (2 days ago) dmi.bios.date: 12/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SJ.313 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K43SJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SJ.313:bd12/14/2011:svnASUSTeKComputerInc.:pnK43SJ:pvr1.0:rvnASUSTeKComputerInc.:rnK43SJ:rvr1.0:cvnASUSTeKComputerInc.:ct9:cvr1.0: dmi.product.name: K43SJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu May 7 15:41:03 2015 xserver.configfile: default xserver.errors: Failed to load module "nouveau" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452717 Title: Xorg doesn't start after upgrade from utopic to vivid, starts ok when chosen to boot upstart instead of systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects
Having disconnects with this kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/ And this firmware http://wireless.kernel.org/en/users/Drivers/iwlwifi?action=AttachFile&do=get&target=iwlwifi-7260-ucode-25.228.9.0.tgz seeing this a lot in my dmesg: [91059.976451] wlan0: deauthenticated from d4:ca:6d:0d:e3:ad (Reason: 16=GROUP_KEY_HANDSHAKE_TIMEOUT) [91060.007299] cfg80211: Calling CRDA to update world regulatory domain [91060.009159] cfg80211: World regulatory domain updated: [91060.009162] cfg80211: DFS Master region: unset [91060.009163] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [91060.009165] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [91060.009166] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [91060.009168] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm), (N/A) [91060.009169] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [91060.009170] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) [91060.009185] cfg80211: Calling CRDA for country: RU [91060.011209] cfg80211: Regulatory domain changed to country: RU [91060.011212] cfg80211: DFS Master region: unset [91060.011213] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [91060.011215] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [91060.011217] cfg80211: (5735000 KHz - 5835000 KHz @ 2 KHz), (N/A, 3000 mBm), (N/A) [91061.344818] wlan0: authenticate with d4:ca:6d:0d:e3:ad [91061.346860] wlan0: send auth to d4:ca:6d:0d:e3:ad (try 1/3) [91061.348595] wlan0: authenticated [91061.352076] wlan0: associate with d4:ca:6d:0d:e3:ad (try 1/3) [91061.359677] wlan0: RX AssocResp from d4:ca:6d:0d:e3:ad (capab=0x431 status=0 aid=2) [91061.361415] wlan0: associated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354975 Title: iwlwifi Intel 7260 Wifi disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/unitylinux/+bug/1354975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354879] [NEW] icinga-web 1.11.1-1 trusty package depends on icinga-idoutils and icinga-doc
Public bug reported: icinga-idoutils and icinga-doc are irrelevant for icinga-web when used with icinga2. icinga-idoutils depnends on icinga-common, so bacically when I install icinga-web for icinga2 I also install a part of old icinga. ** Affects: icinga-web (Ubuntu) Importance: Undecided Status: New ** Package changed: icinga (Ubuntu) => icinga-web (Ubuntu) ** Package changed: icinga-web (Ubuntu) => icinga (Ubuntu) ** Package changed: icinga (Ubuntu) => icinga-web (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354879 Title: icinga-web 1.11.1-1 trusty package depends on icinga-idoutils and icinga-doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icinga-web/+bug/1354879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
