[Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error
** Changed in: juju Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805129] Re: glade crash: drawable is not a native X11 window
I can also add that this issue maybe due to Ubuntu/Debian specific patches in lower levels of the stack (eg. gtk or even gdk) because downloading the upstream source for 3.22.2 and building it outside of a deb package still results in this same crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805129 Title: glade crash: drawable is not a native X11 window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1805129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805129] Re: glade crash: drawable is not a native X11 window
Same issue on Ubuntu MATE 20.04 LTS with glade 3.22.2-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805129 Title: glade crash: drawable is not a native X11 window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1805129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807529] Re: Attempting to add any widget causes the app to crash. It doesn't seem to matter if I drag the widget or use the keyboard (I'm an orca screen reader user).
I'm also getting this bug on Ubuntu MATE 20.04 LTS with the exact same error message -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807529 Title: Attempting to add any widget causes the app to crash. It doesn't seem to matter if I drag the widget or use the keyboard (I'm an orca screen reader user). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glade/+bug/1807529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756040] Re: bionic: LXD containers don't get fan network IP addresses
** Changed in: juju Milestone: 2.5.1 => 2.5.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756040 Title: bionic: LXD containers don't get fan network IP addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1756040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811807] [NEW] fingerprint scanner not working
Public bug reported: I have a new Thinkpad Carbon X1 Extreme and the fingerprint scanner does not appear to be supported. $ fprintd-enroll $USER list_devices failed: No devices available ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ian6133 F pulseaudio /dev/snd/controlC0: ian6133 F pulseaudio CurrentDesktop: KDE Date: Tue Jan 15 21:29:38 2019 MachineType: LENOVO 20MF000BUS ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=f198f923-1cae-439c-aab1-aa886fdddf29 ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MF000BUS dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MF000BUS:pvrThinkPadX1Extreme:rvnLENOVO:rn20MF000BUS:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MF000BUS dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811807 Title: fingerprint scanner not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798117] Re: juju sends "network" top level key to user.network-config in lxd containers
** Changed in: juju Milestone: 2.5-beta2 => 2.5-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798117 Title: juju sends "network" top level key to user.network-config in lxd containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1798117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315856] Re: No System Sounds
Attached is an AbiWord document that shows step by step how to enable sound events in Lubuntu 17.10 AMD64. Hopefully it will be helpful for other platforms as well. ** Attachment added: "Uses existing Lubuntu Software and Configuration Files" https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1315856/+attachment/5099383/+files/Lubuntu%20Sound%20Events%20Guide.abw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315856 Title: No System Sounds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1315856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739973] [NEW] HDMI doesn't work with kernel 4.4
Public bug reported: I recently upgraded my Ubuntu version from 15.10 to 16.04. I know, I should have done this earlier, but whenever I upgrade there's always something that doesn't work afterwards. This time it's HDMI. I first noticed the problem when trying to use the projector at work. Weirdly, if I go to display settings the projector is detected there it's just that nothing shows up. Even more weirdly, using a HDMI to VGA adaptor works fine and similarly using a HDMI to DVI adaptor with my monitor also works fine. So I initially put it down to a fault with the cable or the projector. But then I found the same issue with my TV using other cables. Upon restarting my laptop, I noticed that grub displays fine. I then tried loading up using kernel 4.2.0-42-generic and that works fine so it seems that this is just a problem with kernel 4.4. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1619 F pulseaudio /dev/snd/controlC0: mark 1619 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Sun Dec 24 18:18:00 2017 HibernationDevice: RESUME=UUID=cc779117-d74d-49bd-b047-1cc9611bd0d5 InstallationDate: Installed on 2015-09-16 (830 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20266 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=d7285501-2881-4b24-a1c7-cf0692d314ff ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2017-11-08 (46 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug hdmi kernel-bug wily xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739973 Title: HDMI doesn't work with kernel 4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Yes, you are 100% correct. We can determine from distro info if the labelled LTS release is ready or not. Juju 2.2.6 does do this check now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727355 Title: Juju attempts to bootstrap bionic by default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
Although the effect of Juju using the series flagged by distro data as latest LTS means that it will attempt to use bionic before it is ready. We could change Juju code to hard code the preferred LTS as one we know works but this means we need to change Juju each time we want to update the preferred LTS. But I'm guessing we don't want to defer flaging bionic as the LTS in distro info until release day? Even though until bionic is released it could be a case of false advertising? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727355 Title: Juju attempts to bootstrap bionic by default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
This issue is not that Juju breaks when a new series is released. The problem is that Juju defaults to using the latest LTS as the series for which to bring up machines if none is specified by the user. If bionic becomes the latest LTS, Juju will try and find agent binaries to match. And if we are yet to publish those binaries in streams, we will get the error referenced in this bug. So it's just a case of a small window where distro-info was updated but the streams publication lagged behind a little. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727355 Title: Juju attempts to bootstrap bionic by default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702402] [NEW] package nginx-full (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I says it cannot install dependencies, I try to install dependencies (nginx-core, nginx) but I can't install them because of the same error. ProblemType: Package DistroRelease: Ubuntu 16.04.2 LTS Package: nginx-core, nginx (not installed) Architecture: intel i5 Date: Tues July 4 2:15:32 2017 When I input apt-cache policy pkgname: N: Unable to locate package pkgname Error: Setting up nginx-core (1.10.3-0ubuntu0.16.04.1) ... Job for nginx.service failed because the control process exited with error code. See "systemctl status nginx.service" and "journalctl -xe" for details. invoke-rc.d: initscript nginx, action "start" failed. ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-07-05 00:52:25 EDT; 8ms ago Process: 26345 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE) Jul 05 00:52:24 brandon-Inspiron-5521 systemd[1]: Starting A high performance... Jul 05 00:52:25 brandon-Inspiron-5521 nginx[26345]: nginx: [emerg] unknown di... Jul 05 00:52:25 brandon-Inspiron-5521 nginx[26345]: nginx: configuration file... Jul 05 00:52:25 brandon-Inspiron-5521 systemd[1]: nginx.service: Control proc... Jul 05 00:52:25 brandon-Inspiron-5521 systemd[1]: Failed to start A high perf... Jul 05 00:52:25 brandon-Inspiron-5521 systemd[1]: nginx.service: Unit entered... Jul 05 00:52:25 brandon-Inspiron-5521 systemd[1]: nginx.service: Failed with ... Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package nginx-core (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of nginx: nginx depends on nginx-core (>= 1.10.3-0ubuntu0.16.04.1) | nginx-full (>= 1.10.3-0ubuntu0.16.04.1) | nginx-light (>= 1.10.3-0ubuntu0.16.04.1) | nginx-extras (>= 1.10.3-0ubuntu0.16.04.1); however: Package nginx-core is not configured yet. Package nginx-full is not installed. Package nginx-light is not installed. Package nginx-extras is not installed. nginx depends on nginx-core (<< 1.10.3-0ubuntu0.16.04.1.1~) | nginx-full (<< 1.10.3-0ubuntu0.16.04.1.1~) | nginx-light (<< 1.10.3-0ubuntu0.16.04.1.1~) | nginx-extras (<< 1.10.3-0ubuntu0.16.04.1.1~); however: Package nginx-core is not configured yet. Package nginx-full is not installed. Package nginx-light is not installed. Package nginx-extras is not installed. dpkg: error processing package nginx (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: nginx-core nginx ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nginx-full (not installed) ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: nginx-common: Install nginx-full: Install nginx-common: Configure nginx-full: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 3 12:01:52 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-02 (244 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: nginx Title: package nginx-full (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nginx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702402 Title: package nginx-full (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1702402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636395] Re: dnsmasq not working with OpenVPN
Hi, I'm having exactly the same problem as described by @raffraffraff - after connection to the VPN the dnsmasq instance handled by NetworkManager no longer makes DNS queries for addresses outside the VPN (eg. google.com) but it can resolve ones internal to the VPN (eg. web- dev.myorg.private). Using DIG to make a direct DNS query to any remote DNS server works fine, so it looks like dnsmasq has got in a tizz. To add a little more info... I'm able to add a file /etc/NetworkManager/dnsmasq.d/debug containing the line "log-queries" and I can see lines in syslog like: ... dnsmasq[25056]: forwarded www.google.com to 129.215.205.191 So obviously dnsmasq is trying to process the requests but failing. I can also see dnsmasq picking up new configurations from DBUS as I connect/disconnect but there are no errors reported. I also note that dnsmasq is trying to make queries via the public DNS servers, but when connected to the VPN all the queries should go to the trusted DNS server provided on the VPN (this is discussed in bug 1639776) but I think this is a separate issue. Ubuntu 16.04.2 LTS dnsmask-base 2.75-1ubuntu0.16.04.2 network-manager 1.2.6-0ubuntu0.16.04.1 Cheers, TIM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636395 Title: dnsmasq not working with OpenVPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1636395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643911] Re: libvirt randomly crashes on xenial nodes with "*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption:"
Is this the same bug we saw the other week? I thought Dan B had found a couple of patches missing from the libvirt shipped in Ubuntu which are likely candidates for fixing this. Kashyap, do you have those to hand? I don't think we're likely to get much traction on this from upstream libvirt because: * This is not the latest stable release of libvirt. * They looked anyway, and they think it's fixed in the latest stable release of libvirt. IOW it's a downstream Ubuntu issue. We need to report this as a bug to Canonical in their package, providing the 2 patches recommended by upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643911 Title: libvirt randomly crashes on xenial nodes with "*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption:" To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1643911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
+1, same configuration, same behavior, 16.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Changed in: juju Milestone: 2.1-rc1 => 2.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
One possible root cause may be that if the machine running the unit is loaded, the time between checking for leadership and the lease expiring may have passed before the hook gets to write the leadership settings. It's very unusual that the unit leader changes so often as seen in the logs. This fact points to a possible load issue because the leader should only change if the current leader did not to get update its lease before it expired; if it doesn't that is likely due to load. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
I'm thinking also that a controller log (at debug or even trace level) may be useful to see how the controller is handling leadership changes. Just the part of the log around the time of the issue and what leads up to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
Looking at the rabbitmq logs, it appears to me (I could be misinterpreting): At 21:39:23 -> unit 2 becomes the leader (the leader-elected hook is run) At 21:47:25 -> unit 0 becomes the leader (the leader-elected hook is run) At 22:01:27 -> unit 1 becomes the leader (the leader-elected hook is run) At 22:13:54 -> unit 1 thinks it is the leader and updates leader settings but Juju thinks it is not At 22:17:06 -> unit 0 becomes the leader (the leader-elected hook is run) At 22:22:57 -> unit 0 thinks it is the leader and updates leader settings but Juju thinks it is not So it appears that Juju ran the leader elected hook on both unit 0 and unit 1 and these units tried to do stuff as leader. But Juju thinks unit 2 is leader. Curiously, at 22:17:06 and 22:17:58, unit 2 successfully updates leader settings, even though it should not have been the leader anymore. The charm doesn't appear to use leader elected or deposed hooks - it just symlinks to a common Python file. Juju still thinks that there are hooks though, so it runs the leader-elected hook and logs that. But I can't see any logs of where Juju runs the leader-deposed hook. Perhaps that's a clue? Perhaps that indicates that Juju is getting confused as to who the leader is? It would be useful to have a mongo dump to see what state the model is in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654116] Re: Attempts to write leadership settings when not the leader during relation-changed hooks
** Changed in: juju Assignee: Menno Smits (menno.smits) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654116 Title: Attempts to write leadership settings when not the leader during relation-changed hooks To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1654116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju Assignee: Alexis Bruemmer (alexis-bruemmer) => Ian Booth (wallyworld) ** Changed in: juju Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612116] Re: please remove juju-core-1 and juju-mongodb packages from yakkety
+1 from me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612116 Title: please remove juju-core-1 and juju-mongodb packages from yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core-1/+bug/1612116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570650] Re: Use juju-mongodb2.6 for 1.25 on xenial
We are only doing *critical* fixes for 1.25. Upgrading mongo version is not a critical fix as far as I know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570650 Title: Use juju-mongodb2.6 for 1.25 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610778] Re: please remove this package from yakkety
We do not need juju-mongodb2.6 on yakkety. This package was to allow direct upgrades from Juju 1.25 to 2.x, since upgrading mongo 2.4 to 3.x needed to go via 2.6. However, Juju upgrades from 1.25 will be implemented via model migration so this mongo upgrade step is no longer necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610778 Title: please remove this package from yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb2.6/+bug/1610778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581284] Re: --sslPEMKeyPassword parameter must be passed with = on yakkety
** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Importance: Undecided => Critical ** Changed in: juju-core Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson) ** Changed in: juju-core Milestone: None => 2.0-beta7 ** Changed in: juju-core Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581284 Title: --sslPEMKeyPassword parameter must be passed with = on yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1581284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] Re: Backlight brightness keys not working
I have just tried again with the latest 4.5 kernel downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ No luck. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.5 ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Progress - using the next intel kernel works *with* nvidia installed also. ie prime-select intel | nvidia works. It hangs on shutdown, but at least I can log in now. A 4.4.x kernel is not scheduled for inclusion in xenial is it. The 4.4.x is the only one that works for me from what I can tell. Thanks for the help :-D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4553111/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
I totally purged nvidia drivers and blacklisted nouveau. Everything was straight intel. The machine would boot to the greeter and attempts to login would result in a freeze; console was not obtainable. Attached is the dmesg log, and to follow the Xorg log. I couldn't see any obvious errors. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4553110/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
The login screen shows ok. But when I type the password and hit enter, the cursor freezes. I can't even switch to a console login at that point. I got the logs by going straight to a console login instead of attempting to login normally. When trying to install wily direct from a USB stick, I also got freezes as it was trying to display the install dialog. But the vivid install worked (as it was using a 3.9 kernel maybe?). But after install I still had to install the nvidia drivers from the console to get X working properly I think. And from there I could upgrade to wily. And from there I installed the 4.4.0 kernel to get wireless networking happy. I don't understand why the login screen can show and then not the desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Attached is dmesg as requested ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4551811/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Also lsmod | grep 915 parport49152 3 lp,ppdev,parport_pc i915 1204224 3 i2c_algo_bit 16384 1 i915 drm_kms_helper135168 1 i915 drm 360448 5 i915,drm_kms_helper,nvidia video 40960 1 i915 Yes, I have image-extra installed. I tried removing nvidia-261 but this resulted in a freeze at boot just after the graphics drivers were loaded. Using the nvidia drivers is the only way I can get a functioning system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Sorry, meant to say nvidia-361 in last comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
I've never run gpu-manager. I use prime-select to choose between nvidia and intel. I could not install wily on this laptop from a usb stick as the install process locked up trying to load the graphics drivers. I had to start with vivid as the older kernel did work. Upgrading to wily, the only way I could get things to work is to use a recent kernel with the binary nvidia drivers. I need a recent kernel to support the Intel 8260 wireless chipset. I'd prefer just to use the Intel graphics to get better battery life. But so far attempts to do that and have a working machine have failed. If I try and boot after uninstalling the nvidia drivers, the I can't get a graphical login to work (see comment #33). Is there anything I can do to resolve the above error with switching to Intel using prime-select? Or ideally, I'd not install the nvidia drivers at all. But no luck so far doing that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552209/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552213/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
And the dmesg output. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4552204/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Attached is the X log after adding the debug line. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4552203/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] [NEW] Backlight brightness keys not working
Public bug reported: Originally described in bug 1533221. This is a new bug to track this additional issue separately. The above bug has h/w info attached etc. This is a new skylake chipset. Backlight function keys are not working. I have tried various combinations of: acpi_osi=Linux acpi_backlight=native acpi_osi=Linux acpi_backlight=vendor acpi_osi=! acpi_backlight=vendor etc, etc with no luck. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552211/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552210/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552217/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552214/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552212/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552215/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] Re: Backlight brightness keys not working
apport information ** Tags added: apport-collected wily ** Description changed: Originally described in bug 1533221. This is a new bug to track this additional issue separately. The above bug has h/w info attached etc. This is a new skylake chipset. Backlight function keys are not working. I have tried various combinations of: acpi_osi=Linux acpi_backlight=native acpi_osi=Linux acpi_backlight=vendor acpi_osi=! acpi_backlight=vendor etc, etc with no luck. + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ian2218 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4 + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 5986:066d Acer, Inc + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Notebook P65_P67RGRERA + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0-generic root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro acpi_osi=Linux acpi_backlight=native drm.debug=14 + ProcVersionSignature: Ubuntu 4.4.0-0.12-generic 4.4.0 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-0-generic N/A + linux-backports-modules-4.4.0-0-generic N/A + linux-firmware 1.155 + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 4.4.0-0-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/20/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.05.10 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: P65_P67RGRERA + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.name: P65_P67RGRERA + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552208/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552220/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552218/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552216/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552221/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535470] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1535470/+attachment/4552219/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535470 Title: Backlight brightness keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
Using the latest 4.4.0 kernel, I can now boot. But only with nvidia graphics card enabled. Intel graphics is still broken. Backlight function keys are still not working. I have tried various combinations of: acpi_osi=Linux acpi_backlight=native acpi_osi=Linux acpi_backlight=vendor etc with no luck. ian@wallyworld:~$ apt-cache policy linux-image-4.4.0 linux-image-4.4.0-0-generic: Installed: 4.4.0-0.12 Candidate: 4.4.0-0.12 Version table: *** 4.4.0-0.12 0 500 http://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/ xenial/main amd64 Packages 100 /var/lib/dpkg/status linux-image-4.4.0-040400-generic: Installed: 4.4.0-040400.201601101930 Candidate: 4.4.0-040400.201601101930 Version table: *** 4.4.0-040400.201601101930 0 100 /var/lib/dpkg/status linux-image-4.4.0-0-lowlatency: Installed: (none) Candidate: 4.4.0-0.12 Version table: 4.4.0-0.12 0 500 http://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/ xenial/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
I have the nvidia binary drivers installed from the graphics-drivers ppa. I use prime-select to choose either "nvidia" or "intel". Using nvidia boots fine. When intel is selected: - lightdm greeter screen displays in low res (maybe 640x480, not sure) - logging in simply returns to the greeter screen Using this latest kernel, I have not seen any blank screens trying to boot with intel. But as per above, I can't log in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549801/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549790/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549794/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549787/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549797/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549789/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Booting with intel graphics enabled results in a lockup
The only kernel I can get to work at all in terms of allowing lightdm to run and me to log in is 3.19.x All Ubuntu kernels I have tried - 4.2.0-23 - 4.3.0-6 - 4.4.0-0 cause boot to lock up. It's not just lightdm that fails. You can't even Alt-Shift F1 to a console. The only 4.x kernel that works (which also allows networking) in mainline 4.4. ** Description changed: - Booting with intel graphics enabled results in a lockup loading lightdm - or logging in results in the greeter screen appearing again. The laptop - has a Nvidia GTX730 graphics card which can be switched off via - bumblebee or prime. + Booting with intel graphics enabled results in a lockup loading lightdm or logging in results in the greeter screen appearing again. The laptop has a Nvidia GTX730 graphics card which can be switched off via bumblebee or prime. + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ian2045 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4 + MachineType: Notebook P65_P67RGRERA + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-43-generic N/A + linux-backports-modules-3.19.0-43-generic N/A + linux-firmware 1.155 + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/20/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.05.10 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: P65_P67RGRERA + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: + dmi.product.name: P65_P67RGRERA + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549791/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549793/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549798/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549795/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549799/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549800/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549796/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549792/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4549788/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Booting with intel graphics enabled results in a lockup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] [NEW] Issues with new Skylake hardware
Public bug reported: I have various hardware issues on a new Skylake laptop. The laptop has a Nvidia GTX730 graphics card which can be switched off via bumblebee or prime 1. Intel HD graphics Booting with intel graphics enabled results in a lockup loading lightdm or logging in results in the greeter screen appearing again. 2. Intel 8260 wireless I have to run a recent mainline kernel (4.4 or similar) to get wireless. 3. nvidia card Trying to install wily from a USB stick results in a splash screen lock up before it gets to the install screen. This appears related to the noveau drivers. I have to use the graphics ppa to install the nvidia drivers. But it is not an issue in the 3.9 kernel because to install what I have to do is: i. install vivid (everything works except wireless) ii. use wired network to install nvidia drivers iii. use wired network to upgrade to wily iv. use wired network to install mainline 4.4 kernel 4. Display brightness function keys These don't work. Other function keys do. The other keys show output in acpi_listen but the brightness keys don't The settings applet can be used to adjust brightness, as can writing a value to /proc/blah 5. lshw shows other unclaimed hardware eg I think fingerprint scanner? output attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lshw.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4548582/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Issues with new Skylake hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] Re: Issues with new Skylake hardware
apport information ** Tags added: apport-collected wily ** Description changed: I have various hardware issues on a new Skylake laptop. The laptop has a Nvidia GTX730 graphics card which can be switched off via bumblebee or prime 1. Intel HD graphics Booting with intel graphics enabled results in a lockup loading lightdm or logging in results in the greeter screen appearing again. 2. Intel 8260 wireless I have to run a recent mainline kernel (4.4 or similar) to get wireless. 3. nvidia card Trying to install wily from a USB stick results in a splash screen lock up before it gets to the install screen. This appears related to the noveau drivers. I have to use the graphics ppa to install the nvidia drivers. But it is not an issue in the 3.9 kernel because to install what I have to do is: i. install vivid (everything works except wireless) ii. use wired network to install nvidia drivers iii. use wired network to upgrade to wily iv. use wired network to install mainline 4.4 kernel 4. Display brightness function keys These don't work. Other function keys do. The other keys show output in acpi_listen but the brightness keys don't The settings applet can be used to adjust brightness, as can writing a value to /proc/blah 5. lshw shows other unclaimed hardware eg I think fingerprint scanner? output attached. + --- + ApportVersion: 2.19.1-0ubuntu5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + Tags: wily + Uname: Linux 4.4.0-040400-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4548583/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Issues with new Skylake hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533221] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1533221/+attachment/4548584/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533221 Title: Issues with new Skylake hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] Re: Broken juju LXC deployments
Stephane, Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query for that. So this utility will need to be changed. It is in the cloud-image-utils package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+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 1515463] Re: Broken juju LXC deployments
Stephane, you are right. We can change Juju to use mangle the output of the cloud-image-query to add "root.tar.xz". Is this guaranteed to always work for all series / arch? Are there the correct root.tar.xz files on cloud-image.ubuntu.com ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] Re: Broken juju LXC deployments
Stephane, you are right. We can change Juju to use mangle the output of the cloud-image-query to add "root.tar.xz". Is this guaranteed to always work for all series / arch? Are there the correct root.tar.xz files on cloud-image.ubuntu.com ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+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 1515463] Re: Broken juju LXC deployments
Stephane, Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query for that. So this utility will need to be changed. It is in the cloud-image-utils package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361646] Re: Atheros wireless AR9285 keeps disconnecting
My problem is worse than described Jim's previous comment - I don't need to suspend or bring the interface down to see the issue. It happens randomly, sometimes at very short intervals. Each time requires a reboot to reset the network card/chipset so that it starts working again (for an indeterminate time). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361646 Title: Atheros wireless AR9285 keeps disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1361646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507232] [NEW] Mangler mangling hostname/port information in wily
Public bug reported: Mangler was working fine for me in 15.04. I'd upgraded to 15.10 (along with adding a skylake chip/board/ddr4) things were broken, mostly due to hardware. After I finally sorted it all out (bios update, linux 4.3 rc5 for either video or e1000 freeze), mangler is still broken. Steps to reproduce: install mangler. Launch from the command line. Choose the 'settings' button on the left, choose the 'debug' tab and check all the debug tabs. Use 'server list' button on the left to add a server -- it doesn't need to be a real vent server. I used www.yahoo.com, port 1234, username anonymous. Save it, hit connect -- debugging claims invalid server name: libventrilo3: 19:02:51.447335: ---> v3_login() libventrilo3: 19:02:51.447417: v3_login: invalid server name format. expected: 'name:port' libventrilo3: 19:02:51.447439: <--- v3_login() Repeat the process, but using 'quick connect' and you'll see it do dns lookup, etc, then fail in a normal "no server there." Hit 'quick connect' again and now the normal text is replaced with what looks like garbage; unicode boxes of "000E", "0004", and "000E". I can 'quick connect' to my real clan server successfully -- but not via the saved entry in the server list. Trying the server list, debug produces: libventrilo3: 19:08:29.594633: ---> v3_login() libventrilo3: 19:08:29.594673: parsed server name: �*`[0002] libventrilo3: 19:08:29.594677: parsed server port: [0004] libventrilo3: 19:08:29.594708: ---> v3_queue_event() libventrilo3: 19:08:29.594712: queued event type 1. now have 1 event in queue libventrilo3: 19:08:29.594716: <--- v3_queue_event() libventrilo3: 19:08:29.594720: Looking up hostname for �*`[0002] libventrilo3: 19:08:29.624959: Hostname lookup failed. libventrilo3: 19:08:29.624994: <--- v3_login() ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: mangler 1.2.5-2build1 Uname: Linux 4.3.0-040300rc5-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 17 18:56:38 2015 InstallationDate: Installed on 2015-10-17 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: mangler UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mangler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507232 Title: Mangler mangling hostname/port information in wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mangler/+bug/1507232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361646] Re: Atheros wireless AR9285 keeps disconnecting
Any update on this? It's still happening quite regularly on wily on kernel 4.2.0-15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361646 Title: Atheros wireless AR9285 keeps disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1361646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482644] Re: Can't deploy charm directly after bootstrap
*** This bug is a duplicate of bug 1459912 *** https://bugs.launchpad.net/bugs/1459912 This issue is supposed to be fixed in the latest Juju 1.24 release https://launchpad.net/juju-core/+milestone/1.24.5 Please re-open if the issue is still observed. ** This bug has been marked a duplicate of bug 1459912 juju agent opens api when upgrade is pending -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482644 Title: Can't deploy charm directly after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482644] Re: Can't deploy charm directly after bootstrap
*** This bug is a duplicate of bug 1459912 *** https://bugs.launchpad.net/bugs/1459912 This issue is supposed to be fixed in the latest Juju 1.24 release https://launchpad.net/juju-core/+milestone/1.24.5 Please re-open if the issue is still observed. ** This bug has been marked a duplicate of bug 1459912 juju agent opens api when upgrade is pending -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1482644 Title: Can't deploy charm directly after bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1482644/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
@Seth, with the user mode containers - lxc didn't support that when the local provider feature was first developed. And now we have lxd on the horizon so we will be re-tooling local provider to use lxd and this will be delivered for Juju 1.26 around end of January 2016. We don't plan on making any further changes to local provider / lxc in the meantime as any work there will be imminently obsolete by the lxd stuff. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
@Seth, with the user mode containers - lxc didn't support that when the local provider feature was first developed. And now we have lxd on the horizon so we will be re-tooling local provider to use lxd and this will be delivered for Juju 1.26 around end of January 2016. We don't plan on making any further changes to local provider / lxc in the meantime as any work there will be imminently obsolete by the lxd stuff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
RE: some of the issues raised in comment 48 - juju-backup shell script uses incorrect quoting method needlessly Juju no longer uses a shell script for backup. That was a short term implementation which has now been replaced by server side functionality written in go. - The local environment hardcodes use of 'sudo' to raise privileges Juju's behaviour has changed in this area, I am not sure if what is done now is sufficient to consider the above issue addressed. Juju requires sudo when using the local provider because user mode lxc did/does not exist in all supported series. What Juju does now is to allow the user to execute bootstrap without first being root, and prompts to elevate privileges as needed to start the lxc containers. This is different to the original behaviour which was to require sudo juju bootstrap thus elevating the entire bootstrap process. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+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 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
RE: some of the issues raised in comment 48 - juju-backup shell script uses incorrect quoting method needlessly Juju no longer uses a shell script for backup. That was a short term implementation which has now been replaced by server side functionality written in go. - The local environment hardcodes use of 'sudo' to raise privileges Juju's behaviour has changed in this area, I am not sure if what is done now is sufficient to consider the above issue addressed. Juju requires sudo when using the local provider because user mode lxc did/does not exist in all supported series. What Juju does now is to allow the user to execute bootstrap without first being root, and prompts to elevate privileges as needed to start the lxc containers. This is different to the original behaviour which was to require sudo juju bootstrap thus elevating the entire bootstrap process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
mgo.RoleUserAdminAny,
mgo.RoleClusterAdmin,
mgo.RoleReadWriteAny},
Why do we need RoleClusterAdmin and RoleReadWriteAny (in particular,
because they don't seem to be defined in the database)?
They are not in 2.4 but are in 2.6+. Some time back, Juju was ported to be
compatible with mongo 2.6+ as a pre-requisite to allowing upgrading to a more
recent mongo (there are bugs not fixed in 2.4). However, the effort to get Juju
on mongo 2.6 was then stalled because of the tokumx evaluation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
mgo.RoleUserAdminAny,
mgo.RoleClusterAdmin,
mgo.RoleReadWriteAny},
Why do we need RoleClusterAdmin and RoleReadWriteAny (in particular,
because they don't seem to be defined in the database)?
They are not in 2.4 but are in 2.6+. Some time back, Juju was ported to be
compatible with mongo 2.6+ as a pre-requisite to allowing upgrading to a more
recent mongo (there are bugs not fixed in 2.4). However, the effort to get Juju
on mongo 2.6 was then stalled because of the tokumx evaluation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1349949
Title:
Juju's mongodb does not need to log every command in syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1355813] Re: Interface MTU management across MAAS/juju
Marked as Fixed Released, does it still occur? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1355813] Re: Interface MTU management across MAAS/juju
Marked as Fixed Released, does it still occur? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418568] Re: cloud-image-utils should Break, not Conflict with cloud-utils
I have run up a precise instance in EC2 and added the cloud-tools- proposed repo. The apt install of cloud-image-utils works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418568 Title: cloud-image-utils should Break, not Conflict with cloud-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1418568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1418568] Re: cloud-image-utils should Break, not Conflict with cloud-utils
Hi Brian and Scott, The issue itself only appears on precise. On trusty, apt-get install cloud-image-utils works fine. So would we not need to test with a fix to the debs in precise-proposed in order to validate that things will now work on precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418568 Title: cloud-image-utils should Break, not Conflict with cloud-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1418568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407699] Re: Precise services cannot be deployed
As per the cloud init output log in comment #2, on a precise system, if you do: apt-get install cloud-image-utils apt-decides it needs to remove the cloud-init package (amongst others). Suggested fix along the lines of: smoser we can fix that with a packaging change to cloud-init in precise. smoser to depend on cloud-image-utils | cloud-utils ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1407699 Title: Precise services cannot be deployed To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1407699/+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 1407699] Re: Precise services cannot be deployed
For now, I've worked around in Juju by not explicitly installing cloud- image-utils. Where tis matter, in local providers, I've added a check to ensure that cloud-image-utils is installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1407699 Title: Precise services cannot be deployed To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1407699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407699] Re: Precise services cannot be deployed
As per the cloud init output log in comment #2, on a precise system, if you do: apt-get install cloud-image-utils apt-decides it needs to remove the cloud-init package (amongst others). Suggested fix along the lines of: smoser we can fix that with a packaging change to cloud-init in precise. smoser to depend on cloud-image-utils | cloud-utils ** Also affects: cloud-init (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/1407699 Title: Precise services cannot be deployed To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1407699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1407699] Re: Precise services cannot be deployed
For now, I've worked around in Juju by not explicitly installing cloud- image-utils. Where tis matter, in local providers, I've added a check to ensure that cloud-image-utils is installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1407699 Title: Precise services cannot be deployed To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1407699/+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 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core Milestone: 1.22 = 1.21-beta4 ** Changed in: juju-core Assignee: (unassigned) = Ian Booth (wallyworld) ** Changed in: juju-core Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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
