[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-09-20 Thread Joseph Nuzman
The bug has been fixed with this commit upstream drm-tip repository (with cc to stable): https://cgit.freedesktop.org/drm-tip/commit/?id=d81fb7fd9436e81fda67e5bc8ed0713aa28d3db2 Note it also affects Zesty. ** Bug watch added: freedesktop.org Bugzilla #101583 https://bugs.freedesktop.org/show

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-03-18 Thread Joseph Nuzman
I had been trying to cherry-pick patches from the working Xenial kernel to mainline, and got bogged down with build issues. Back to the bisection: This kernel ... http://kernel.ubuntu.com/~jsalisbury/lp1657994/linux-image-4.4.0-040400-generic_4.4.0-040400.201702021530_amd64.deb .. does not work.

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-31 Thread Joseph Nuzman
For this kernel, no audio. Failure mode is like 4.4 mainline. Just to understand: the strategy is to bisect between two mainline kernels with different failure modes (4.4 final and 4.5rc1), with the hope that between the two there will be a good kernel? -- You received this bug notification be

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-31 Thread Joseph Nuzman
Yes, 4.4.0-21 is good, just like 4.4.0-59. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657994 Title: Regression: HDMI audio produces no sound (Skylake NUC) To manage notifications about this bu

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-26 Thread Joseph Nuzman
Both kernels behave like any of the kernels from 4.5: no sound on HDMI. Recapping: Ubuntu 4.4.0-59: HDMI audio works properly Mainline 4.4 (any): i915 drm driver does not seem to support Skylake, HDMI audio not enumerated All of the below kernels exhibit the same problem: HDMI produces no soun

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-24 Thread Joseph Nuzman
Kernel behavior summary: Ubuntu 4.4.0-59: HDMI audio works properly Mainline 4.4 (any): i915 drm driver does not seem to support Skylake, HDMI audio not enumerated All of the below kernels exhibit the same problem: HDMI produces no sound Mainline 4.5rc1 Mainline 4.5 final Mainline 4.6 final M

[Bug 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-24 Thread Joseph Nuzman
** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657994 Title: Regression: HDMI audio produces no sound (Skylake NUC) To manage notifications about this bug

[Bug 1657994] [NEW] Regression: HDMI audio produces no sound (Skylake NUC)

2017-01-19 Thread Joseph Nuzman
Public bug reported: After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no longer produces sound. * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine * Audio from headphone jack works fine * Userspace seems to be happily playing to HDMI audio device

[Bug 1121169] Re: crop temporarily hangs the app since simple-scan uses sqlite

2013-09-08 Thread Joseph Nuzman
Autosave overall seems to give similar results for 3.9.91 and the fix- cropping-slowness branch. In both cases, I scanned a single image and then terminated simple-scan with CTRL-C at the terminal. On restart, both versions found two copies of the scanned image and restored two indentical copies

[Bug 1121169] Re: crop temporarily hangs the app since simple-scan uses sqlite

2013-09-07 Thread Joseph Nuzman
I can confirm that cropping is still unusable with 3.9.91, but works fine with lp:~tkluck/simple-scan/fix-cropping-slowness . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1121169 Title: crop tempor

[Bug 843361] Re: missing signal disconnect: simple-scan crashed with SIGSEGV in g_closure_invoke()

2012-07-25 Thread Joseph Nuzman
With main trunk (rev 589 + commit 581 backed out to ease building in my environment), I can no longer reproduce the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/843361 Title: missing s

Re: [Bug 843361] Re: simple-scan crashed with SIGSEGV in g_closure_invoke()

2012-07-08 Thread Joseph Nuzman
I'm not familiar with launchpad, but I pushed a branch and sent a merge request. Maybe slightly goofy because I worked off the 3.4 series. On Sun, Jul 8, 2012 at 2:32 PM, Michael Nagel wrote: > thank you for your help! joseph, are you familiar with bzr and > launchpad? if so, robert (main develo

[Bug 843361] Re: simple-scan crashed with SIGSEGV in g_closure_invoke()

2012-07-07 Thread Joseph Nuzman
I was suffering from a couple of flavors of this bug. It seems that in all cases callbacks for non-existant PageViews were getting triggered by signals related to Page updates. With the attached patch (against 3.4.2), I have not been able to reproduce any of those segfaults. The patch does two t