[Bug 1727842] Re: Volume and Mute buttons on keyboard not doing anything in Unity after upgrade to 17.10

2018-03-25 Thread aproposnix
After a recent (the last since posting this) update of Ubuntu 18.04, this issue has appeared. When I try to use the keyboard to change the volume, nothing happens. I logged into Ubuntu Desktop and it works. I have uninstalled gnome shell + Ubuntu dekstop, leaving only Unity Desktop but the

[Bug 1609242] Re: All Kernels since 4.2.8 result in a black screen on boot

2017-07-24 Thread aproposnix
Thanks Kai-Heng! Just a noob question - Is it OK to compile the kernel on a different computer than the one impacted by the issue? I assume it'll be OK to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2017-07-24 Thread aproposnix
Yeah, we tried to do the bisect (see the history). For whatever reason it wasn't successful. Unfortunately I haven't the knowledge to do the bisect on my own. ** Summary changed: - Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge + All Kernels since 4.2.8 result in a black screen on boot

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2017-07-23 Thread aproposnix
Yes. It happens on 4.13-rc1. Black Screen. The last good version of the kernel was 4.2.8 - all others since give me the black screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title:

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2017-07-22 Thread aproposnix
Could we give this a try again? The issue still exists even with the newest mainline kernels. I'm still stuck with Linux 4.2.9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-11-09 Thread aproposnix
As expected, the 4.9 kernel gives me the black screen on boot. In addition, I'm getting all kinds of screen tearing when I boot into the desktop (blindly of course) with this kernel, unlike the others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-11-06 Thread aproposnix
@jsalisbury Unfortunately none of the builds I could use compiled correctly. I'll have to wait until there's a successful build. Could I use the mainline 4.9? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-11-01 Thread aproposnix
Sorry for the delay I was on holiday over the past week. I've tested linux- image-4.1.0-040100rc6-generic_4.1.0-040100rc6.201610211158_amd64.deb It gives me the second issue where it get's stuck in the console (with the blinking cursor in the upper left corner) before booting into Plymouth.

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-21 Thread aproposnix
linux- image-4.2.0-040200rc6-generic_4.2.0-040200rc6.201610191537_amd64.deb This kernel works fine. I do not get the blackscreen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title:

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-18 Thread aproposnix
linux- image-4.2.0-040200rc7-generic_4.2.0-040200rc7.201610181505_amd64.deb This kernel works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels 4.3-4.8 result in blackscreen -

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-18 Thread aproposnix
This one is just like the other kernels. I get a blackscreen on boot but can blindly 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/1609242 Title: Kernels 4.3-4.8 result in blackscreen -

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-18 Thread aproposnix
maybe on comments 45-46? I wasn't sure what to test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609242 Title: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge To manage notifications

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-15 Thread aproposnix
Hi Again. I decided to try something new today. As I mentioned previously, when I boot it goes directly into a blackscreen - but I believed I could blindly log in. So today I did the following: 1. Cleared my syslog (just wanted to see if there were obvious errors going forward) 2. Rebooted my

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-15 Thread aproposnix
Please disregard my previous post. I didn't see the "revert" folder before. I assume now that this is the correct folder. >From the "revert" folder I installed the following: linux-headers-4.4.0-43_4.4.0-43.63~lp1609242Commitb1b38278Reverted_all.deb

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-15 Thread aproposnix
@jsalisbury Sorry for my ignorance but could you help me understand something? In the past you were putting the kernels in the root folder. This time there were no kernels in the root folder. I assumed that I should go to the folder with the same commit number

[Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

2016-10-06 Thread aproposnix
Same issue as before. As with all of the 4.1 kernels, the screen freezes before going into Plymouth. Only the cursor is visible and I have to manually restart the computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.