[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen

2018-04-14 Thread Erich E. Hoover
** Summary changed: - intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic) + intel-microcode 3.20180312.0 causes lockup at login screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-09 Thread Erich E. Hoover
@kleber-souza I don't think that I have anything running trusty that I can test with, but I can easily test on xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title:

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-04-01 Thread Erich E. Hoover
By any chance, do all of you have sssd installed? One of my colleagues (Kyle Etsler) has established a relationship between this problem and having that package installed. I've verified this on my own machine now, and it makes some sense given that sssd is involved in the login process. -- You

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-03-30 Thread Erich E. Hoover
That's very interesting John, that could also explain why we had a system: 1) get updated 2) fail on 4.4.0-116-generic 3) work on 4.4.0-112-generic 4) install 4.13.0-36-generic and 4.13.0-37-generic 5) fail on 4.13.0-36-generic and 4.13.0-37-generic 6) get intel-microcode downgraded to

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-03-30 Thread Erich E. Hoover
I've identified a couple more systems that are affected by this issue: iucode-tool: system has processor(s) with signature 0x00040651 iucode-tool: system has processor(s) with signature 0x000806e9 That second one was actually having trouble with 4.4.0-116-generic (boots fine with

[Kernel-packages] [Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

2018-03-30 Thread Erich E. Hoover
** Summary changed: - intel-microcode 3.20180312.0 causes locks up at login screen(w/ linux-image-4.13.0-37-generic) + intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic) -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0

2018-03-29 Thread Erich E. Hoover
> Does the lockup happen as soon as you reach the login screen or does it happen once you put in your password and hit enter? It sometimes happens as soon as the login screen shows up, sometimes it happens after you hit enter, and roughly 1:8 tries it will make it all the way to the desktop. >

[Kernel-packages] [Bug 1759920] Re: linux-image-4.13.0-37-generic locks up at login screen with intel-microcode 3.20180312.0

2018-03-29 Thread Erich E. Hoover
** Project changed: linux => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: linux-image-4.13.0-37-generic locks up at login screen with intel- microcode

[Kernel-packages] [Bug 1327753] Re: FTBFS: hwloc-contrib 1.9-1 build-depends on unavailable package libxnvctrl-dev

2015-03-11 Thread Erich E. Hoover
Wow, thanks Alberto - that would be great! We (wine-staging) would like to link to libXNVCtrl and having it be a dynamic library removes the ambiguity about what we're supposed to do license-wise (and it dramatically simplifies our configure check!). -- You received this bug notification

[Kernel-packages] [Bug 1429974] Re: Outdated/wrong copyright/license data

2015-03-09 Thread Erich E. Hoover
Hi Hans, Yes, this would fix the issue (provided that the copyright file gets updated with the version from upstream). We (wine staging tree) would greatly prefer that this package get merged with upstream since upstream has the lib provided dynamically. Is there a time-table on this happening

[Kernel-packages] [Bug 1429974] [NEW] Outdated/wrong copyright/license data

2015-03-09 Thread Erich E. Hoover
Public bug reported: The nvidia-settings package has a significant problem with the copyright file. It is either significantly out of date or plain wrong, neglecting a variety of files that have different licenses from the main binary. This is most significant in the portion of the package