Re: [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I booted the 4.17rc1 kernel. In order to see output I connected an old TV to the DVI output, and that output was successfully detected (through an DVI-HDMI adapter, if that matters). The output of /sys/class/drm/card0-HDMI-A-1 in this case: dpms: Off enabled: disabled modes: (empty) status: disconnected I then tried switching which monitor was connected to which port. Interestingly, in this case both the Dell U2415 and the old TV could show output successfully. // David On 2018-05-02 19:50, Harry Wentland wrote: > Thanks, mind posting the same for the non-working kernel? I'm curious if the > problem is > 1) we don't detect the display > 2) we don't enable the display > 3) we enable the display but wrong > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
I'm not sure if you asked for the contents of these files from a working or non-working kernel, but I'll take the working kernel since that's obviously a lot easier. The monitor, Dell U2415, is connected via its input source "HDMI (MHL) 2". The monitor name "DELL U2415" shows up in the edid file. status: connected enabled: enabled dpms: On modes: 1920x1200 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1600x1200 1280x1024 1280x1024 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x576i 720x480 720x480 720x480i 720x480i 640x480 640x480 640x480 720x400 // David On 2018-05-02 16:11, Harry Wentland wrote: > Is it HDMI from the board to HDMI on the monitor? I'd like to rule out > any use of an adapter or HDMI-to-DVI cable. > > What monitor is this? > > Is the monitor detected? > > What do you see in the 'status', 'enabled', 'dpms', and 'modes' files in > /sys/class/drm/card0-HDMI-A-1/ ? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761751] Re: [REGRESSION] drm/amd/dc: Add dc display driver (v2)
I don't think it is the same bug. I have a card with HDMI and DVI connectors (XFX RX 460). The HDMI connector is connected to the monitor, the DVI connector is unplugged. // David On 2018-04-30 17:40, Harry Wentland wrote: > Replied on the ticket. > > If this is about non-functioning LVDS or VGA I'm aware of it and trying > to find time to find a good solution. > > Harry > > On 2018-04-30 11:14 AM, Joseph Salisbury wrote: >> Hi Harry, >> >> A kernel bug report was opened against Ubuntu [0]. After a kernel >> bisect, it was found the following commit introduced the bug: >> >> >> commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c >> Author: Harry Wentland>> Date: Tue Sep 12 15:58:20 2017 -0400 >> >> drm/amd/dc: Add dc display driver (v2) >> >> >> The regression was introduced as of v4.15-rc1 and still exists in >> current mainline. The commit does not need to be reverted to resolve >> the bug. Disabling the CONFIG_DRM_AMD_DC_PRE_VEGA option makes the bug >> go away. >> >> I was hoping to get your feedback, since you are the patch author. Do >> you think gathering any additional data will help diagnose this issue? >> >> >> Thanks, >> >> Joe >> >> >> [0] http://pad.lv/1761751 >> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 4.15.0-15-generic #16~lp1761751v2: Boots normally -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
The test kernel (4.15.0-15-generic #16~lp1761751) boots normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Yeah, so I doubt it's a whitespace fix in the rxrpc driver. However, a diff between the configs on v415-rc2 and v415-rc3 has lots of differences, the most interesting being this one: $ diff -u config-4.15.0-041500rc2-generic config-4.15.0-041500rc3-generic /* ... snip ... */ @@ -5675,9 +5677,9 @@ # Display Engine Configuration # CONFIG_DRM_AMD_DC=y -# CONFIG_DRM_AMD_DC_PRE_VEGA is not set +CONFIG_DRM_AMD_DC_PRE_VEGA=y # CONFIG_DRM_AMD_DC_FBC is not set -# CONFIG_DRM_AMD_DC_DCN1_0 is not set +CONFIG_DRM_AMD_DC_DCN1_0=y # CONFIG_DEBUG_KERNEL_DC is not set -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 3d7682af228fd78dc46bc: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 5fc62f6a139a7b06b027bf442cd4205619506f59: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 282ef4729195c8503f7101d574acfb5e7c8a8209: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #201804181224: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
There's nothing graphics related here: $ git log v4.15-rc2..a0da456bbf95d2a9294799bb --oneline a0da456 net: phy-micrel: check return code in flp center function c7799c0 tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv() cfac7f8 tcp/dccp: block bh before arming time_wait timer b484d8a Merge branch 'sctp-prsctp-chunk-fixes' 779edd7 sctp: do not abandon the other frags in unsent outq if one msg has outstanding frags e5f6129 sctp: abandon the whole msg if one part of a fragmented message is abandoned d30fc51 sctp: only update outstanding_bytes for transmitted queue when doing prsctp_prune 6fef90c net: dsa: bcm_sf2: Set correct CHAIN_ID and slice number mask f859b4a sit: update frag_off info 3016dad tcp: remove buggy call to tcp_v6_restore_cb() 90a6ec8 act_sample: get rid of tcf_sample_cleanup_rcu() 6c9257a Merge tag 'rxrpc-fixes-20171129' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs 1c08ac0 net: stmmac: dwmac-sun8i: fix allwinner,leds-active-low handling f8821f9 skbuff: Grammar s/are can/can/, s/change/changes/ a154f8e net: mvpp2: allocate zeroed tx descriptors 282ef47 rxrpc: Fix variable overwrite 5fc62f6 rxrpc: Fix ACK generation from the connection event processor 3d7682a rxrpc: Clean up whitespace Yet I have double checked that, according /var/log/kern.log, - I booted this kernel: Apr 18 13:18:29 david-desktop kernel: [0.00] Linux version 4.15.0-041500rc1-generic (jsalisbury@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #20180417120 - I got black screen and the following message: Apr 18 13:18:29 david-desktop kernel: [1.667490] [drm] Cannot find any crtc or sizes And when I last booted this kernel: Apr 17 06:17:34 david-desktop kernel: [0.00] Linux version 4.15.0-041500rc2-generic (kernel@gloin) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #201712031230 SMP Sun Dec 3 17:32:03 UTC 2017 ...it works just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel a0da456bbf95d2a9294799bb05c61bfb24736bb7: Black screen. This is starting to feel a bit fishy but maybe git knows what it's doing. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel af57b7fffaf74ff337e479abb19026d72065673b: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen. Kernel 4.17-rc1: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
> I built the first test kernel, up to the following commit: You mean the second test kernel, I presume? Kernel 6a5e05a47b6cb8e59bfad351444322b1e4012326: 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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Possibly upstream bug found: https://bugs.freedesktop.org/show_bug.cgi?id=105880 ** Bug watch added: freedesktop.org Bugzilla #105880 https://bugs.freedesktop.org/show_bug.cgi?id=105880 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Kernel 4.15rc2+78d9b048446c3c0a83313444fb706f8f3bccdae7: Black screen. Note: I installed the linux-image-...-generic deb only as the header ones seemed to require libssl1.1...? Anyway, I did some research on my own as well. First, I had a look at the commits between 4.15rc2 and 4.15rc3. The only one I could see being relevant is this one: commit a703c55004e1c5076d57e43771b3e7796ea0 Author: Daniel VetterDate: Mon Dec 4 21:48:18 2017 +0100 drm: safely free connectors from connector_iter ...it seems relevant because the error I get is "Cannot find any crtc or sizes", and the code emitting this error message (in drivers/gpu/drm/drm_fb_helper.c) deals with connectors. This commit is then referenced in other commits later on as being required to fix, but since 4.16 is "black screen" too those fixes seems not have helped here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
4.15.0-041500rc2-generic - Boots normally 4.15.0-041500rc3-generic - Black screen 4.15.0-041500rc4-generic - Not tested So something between rc2 and rc3 it is then... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14/ - Boots normally v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ - Boots normally v4.15-rc5: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc5/ - Black screen v4.15-rc9: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/ - Black screen v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ - Black screen v4.16-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ - Not tested I'll try rc2, rc3 and rc4 next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Ok, so I found this message when trying to boot a faulty kernel without workaround, if it helps: [1.797127] [drm] Cannot find any crtc or sizes [1.799000] [drm] Initialized amdgpu 3.23.0 20150101 for :23:00.0 on minor 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
** Description changed: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), - * linux-image-4.16.0-041600-generic (mainline kernel), + * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. + + EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot + parameters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
** Description changed: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. - Known faulty kernel versions are: - * linux-image-4.15.0-041500-generic (mainline kernel), - * linux-image-4.15.0-13-generic (Ubuntu kernel), - * whatever comes with 18.04 daily live USB stick as of 20180404. + Known faulty kernel versions are: + * linux-image-4.15.0-041500-generic (mainline kernel), + * linux-image-4.16.0-041600-generic (mainline kernel), + * linux-image-4.15.0-13-generic (Ubuntu kernel), + * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+attachment/5104013/+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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] [NEW] Black screen on 18.04 + AMD RX460
Public bug reported: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. ** Affects: linux (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/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Lite ubuntuprylar över...
Hej! Det var ett par år sedan jag slutade på Canonical och går inte på så mycket Linuxkonferenser längre. Men jag har en liten kartong med ubuntuprylar över - några T-shirts, några lanyards, en hög klistermärken...är det någon som kommer att göra reklam för Ubuntu på nån konferens el dyl och behöver lite giveaways så kan ni höra av er. // David -- ubuntu-se mailing list ubuntu-se@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-se
[Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
** Changed in: libav (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec
Marking as security; either Firefox is wrong or libavcodec is vulnerable and probably we need security people to look at it to determine which one it is... ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
** Description changed: + Note: Current workaround is to add pci=noaer to your kernel command + line: + + 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: + GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" + 2) run "sudo update-grub" + 3) reboot + + + My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 - [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error + [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 - [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error + [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio - /dev/snd/controlC0: david 1502 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio + /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.2.0-19-generic N/A - linux-backports-modules-4.2.0-19-generic N/A - linux-firmware1.153 + linux-restricted-modules-4.2.0-19-generic N/A + linux-backports-modules-4.2.0-19-generic N/A + linux-firmware1.153 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Btw, I reported mine upstream long ago and got response from upstream that "I've thought about this problem a bit, but realistically I don't have time to do the fix I'd like to do /.../ Anybody else who is interested should feel free to take a crack at it." See http://permalink.gmane.org/gmane.linux.kernel.pci/48697 Also some googling finds me a few other reports with very similar symptoms, e g: https://bugzilla.kernel.org/show_bug.cgi?id=111601 https://lkml.org/lkml/2015/9/2/573 ** Bug watch added: Linux Kernel Bug Tracker #111601 http://bugzilla.kernel.org/show_bug.cgi?id=111601 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Out of curiousity, do all of you have the combination of Skylake + RTL8723BE, and second, do you experience (as I do) that wifi doesn't work very well (often loses connections etc)? ...as the errors seem to indicate some kind of physical error between the Skylake/Sunrise Point host controller and the wifi card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
Just in case it helps someone: This symptom seems to have more than one root cause. For me, I had more than one entry in /etc/crypttab, one being completely wrong. It was probably a left-over from me switching hard drives a while ago, but then the symptom only started to appear after a 14.04 -> 16.04 upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1447282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
> It is unlikely that your patch fix the problem since none of the drivers of those users have a volume control with multi channel I found this: control.15 { iface MIXER name 'Line Capture Route' value.0 false value.1 false value.2 false value.3 false comment { access 'read write' type BOOLEAN count 4 } } -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
@Raymond, sometimes you're absolutely correct, and often your comments are helpful, but this is one of the times when what you're talking about seems unrelated to this particular bug (about PA crashing)...? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
@Fabio, I've just uploaded pulseaudio 1:8.0-0ubuntu3 to xenial, and I've included a patch that *might* fix this issue (the patch in the link, which you say is broken, but I can click on it just fine). I'm not sure, but it's worth a try. Hopefully it'll get through all testing to be relelased in xenial today. Could you check if it resolves the issue? Thanks! ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Anyhow the first thing needed is probably an alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo And if possible to reproduce while logging is on, this would be helpful too: https://wiki.ubuntu.com/PulseAudio/Log Might not be enough to fix the bug, but should provide a few pointers w r t where to start looking.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
Oh, actually this seems fixed with today's latest image, after running a "sudo apt-get update / sudo apt-get dist-upgrade" I can no longer reproduce the problem. Kristin, can you confirm that your problem is fixed in latest xenial? ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
Confirmed and reproduced here. Relevant log message: module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected ** Changed in: pulseaudio (Ubuntu) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Indeed your alsa-info has some four-channel inputs. Which makes me think maybe this patch: https://lists.freedesktop.org/archives/pulseaudio- discuss/2016-March/025659.html ...could solve the problem. Should at least be worth a try ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548844] Re: Inspiron 13-7359: rfkill button has no effect
Hi and thanks for spotting! My BIOS has been updated now. 1) Dmidecode now shows: 01.06.00 02/25/2016 2) The hotkey still does not work, but now there is a message in dmesg when you press it: dell_wmi: Unknown key with scancode 0xe008 pressed or dell_wmi: Unknown key 0xe008 pressed The former is with upstream 4.5rc5, the latter with Ubuntu's 4.4.0-11-generic. ** 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/1548844 Title: Inspiron 13-7359: rfkill button has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)
Hmm, but the log shows exactly what happens if someone changes the last lines of /etc/pulse/default.pa from the below (this is the original): ### Make some devices default #set-default-sink output #set-default-source input to this: ### Make some devices default #set-default-sink output set-default-source 2 ...notice how they should be commented out by default. Or if it loads a copy of default.pa in ~/.config/pulse or ~/.pulse where this change has been done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547585 Title: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1547585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Relevant error in journalerrors.txt: pulseaudio[3130]: [alsa-source-ALC888 Analog] alsa-mixer.c: Assertion 'pa_cvolume_compatible_with_channel_map(v, cm)' failed at modules/alsa /alsa-mixer.c:1214, function pa_alsa_path_set_volume(). Aborting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Hi! You say it appears randomly. It looks like it's related to setting the input gain of the microphone (or line input). This seems to hit several people, so we should try nail it down. Is there anyone here who'd like to take some time and work with me to try to find the bug? (Might require you to get more logs, try test versions of Pulseaudio, etc). ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => David Henningsson (diwic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)
You haven't changed any configuration files (e g such as /etc/pulse/default.pa ) so they now reference a hard-coded "source #2", have you? If not, could you reproduce this with a higher log level (e g by following https://wiki.ubuntu.com/PulseAudio/Log ) and see if you get more information out of this error? Thanks. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547585 Title: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1547585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
(Sorry for late answer) I find it weird that the suggested change does not work; could you submit a pulseaudio verbose log ( https://wiki.ubuntu.com/PulseAudio/Log ) where you select the front mic and try to record from it? And also, one alsa-info from where pulseaudio fails to set front mic input, and one alsa-info from where you have successfully set it (with alsamixer) and confirmed that the audio recording is working? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551610] Re: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread
*** This bug is a duplicate of bug 1539209 *** https://bugs.launchpad.net/bugs/1539209 ** This bug has been marked a duplicate of bug 1539209 pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551610 Title: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536166] Re: Upgrade to 7.99.2 from January 2016
We now have 8.x in the archive for xenial. ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536166 Title: Upgrade to 7.99.2 from January 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1536166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536166] Re: Upgrade to 7.99.2 from January 2016
> The 7.99.2 is sort of final compared to 7.1 Btw, 7.99.x is the same as the release candidates for 8.0 - they are meant for testing, they are not stable releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536166 Title: Upgrade to 7.99.2 from January 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1536166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551610] Re: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread
I tried to look at this, but it looks like a fairly normal volume being set. Anyone who can reproduce this? It looks like the highest crasher for pulseaudio on xenial right now. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551610 Title: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551610] Re: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread
Stack trace copied from errors.ubuntu.com. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551610/+attachment/4585352/+files/stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551610 Title: /usr/bin/pulseaudio:6:pa_alsa_path_set_volume:source_set_volume_cb:pa_source_process_msg:source_process_msg:set_shared_volume_within_thread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549660] Re: Fix speaker volume on a Dell machine
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => David Henningsson (diwic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549660 Title: Fix speaker volume on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549660] Re: [PATCH] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225
On 2016-02-25 09:29, Takashi Iwai wrote: > On Thu, 25 Feb 2016 09:13:21 +0100, > David Henningsson wrote: >> >> On one of the machines we enable, we found that the actual speaker volume >> did not always correspond to the volume set in alsamixer. This patch >> fixes that problem. >> >> This patch was orginally written by Kailang @ Realtek, I've rebased it >> to fit sound git master. >> >> BugLink: https://bugs.launchpad.net/bugs/1549660 >> Co-Authored-By: Kailang <kail...@realtek.com> >> Signed-off-by: David Henningsson <david.hennings...@canonical.com> > > This conflicts with the latest for-linus branch right after I applied > another fixup addition. Could you again rebase to for-linus branch? Ok, done now. Let me know when it's pushed out. Thanks! > Also, I guess it deserves Cc to stable? I guess so too, so added in v2. I'm always a bit scared to do so when 1) we deal with machines that are not released yet 2) there are verbs in there which only Kailang knows the true meaning of... > > > thanks, > > Takashi > >> --- >> sound/pci/hda/patch_realtek.c | 23 +-- >> 1 file changed, 21 insertions(+), 2 deletions(-) >> >> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c >> index efd4980..ab353b0 100644 >> --- a/sound/pci/hda/patch_realtek.c >> +++ b/sound/pci/hda/patch_realtek.c >> @@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec >> *codec, hda_nid_t hp_pin, >> >> static void alc_headset_mode_default(struct hda_codec *codec) >> { >> +static struct coef_fw coef0225[] = { >> +UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10), >> +{} >> +}; >> static struct coef_fw coef0255[] = { >> WRITE_COEF(0x45, 0xc089), >> WRITE_COEF(0x45, 0xc489), >> @@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec >> *codec) >> }; >> >> switch (codec->core.vendor_id) { >> +case 0x10ec0225: >> +alc_process_coef_fw(codec, coef0225); >> +break; >> case 0x10ec0255: >> case 0x10ec0256: >> alc_process_coef_fw(codec, coef0255); >> @@ -4749,6 +4756,7 @@ enum { >> ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE, >> ALC293_FIXUP_LENOVO_SPK_NOISE, >> ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY, >> +ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, >> }; >> >> static const struct hda_fixup alc269_fixups[] = { >> @@ -5368,6 +5376,17 @@ static const struct hda_fixup alc269_fixups[] = { >> .type = HDA_FIXUP_FUNC, >> .v.func = alc233_fixup_lenovo_line2_mic_hotkey, >> }, >> +[ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = { >> +.type = HDA_FIXUP_VERBS, >> +.v.verbs = (const struct hda_verb[]) { >> +/* Disable pass-through path for FRONT 14h */ >> +{ 0x20, AC_VERB_SET_COEF_INDEX, 0x36 }, >> +{ 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 }, >> +{} >> +}, >> +.chained = true, >> +.chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE >> +}, >> }; >> >> static const struct snd_pci_quirk alc269_fixup_tbl[] = { >> @@ -5638,10 +5657,10 @@ static const struct hda_model_fixup >> alc269_fixup_models[] = { >> {0x21, 0x03211020} >> >> static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = { >> -SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", >> ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, >> +SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", >> ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, >> ALC225_STANDARD_PINS, >> {0x14, 0x901701a0}), >> -SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", >> ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, >> +SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", >> ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, >> ALC225_STANDARD_PINS, >> {0x14, 0x901701b0}), >> SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", >> ALC255_FIXUP_DELL2_MIC_NO_PRESENCE, >> -- >> 1.9.1 >> > -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549660 Title: Fix speaker volume on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549660] [PATCH v2] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225
On one of the machines we enable, we found that the actual speaker volume did not always correspond to the volume set in alsamixer. This patch fixes that problem. This patch was orginally written by Kailang @ Realtek, I've rebased it to fit sound git master. Cc: sta...@vger.kernel.org BugLink: https://bugs.launchpad.net/bugs/1549660 Co-Authored-By: Kailang <kail...@realtek.com> Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- sound/pci/hda/patch_realtek.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 72fa58d..7fded69 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec *codec, hda_nid_t hp_pin, static void alc_headset_mode_default(struct hda_codec *codec) { + static struct coef_fw coef0225[] = { + UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10), + {} + }; static struct coef_fw coef0255[] = { WRITE_COEF(0x45, 0xc089), WRITE_COEF(0x45, 0xc489), @@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec *codec) }; switch (codec->core.vendor_id) { + case 0x10ec0225: + alc_process_coef_fw(codec, coef0225); + break; case 0x10ec0255: case 0x10ec0256: alc_process_coef_fw(codec, coef0255); @@ -4750,6 +4757,7 @@ enum { ALC293_FIXUP_LENOVO_SPK_NOISE, ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY, ALC255_FIXUP_DELL_SPK_NOISE, + ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, }; static const struct hda_fixup alc269_fixups[] = { @@ -5375,6 +5383,17 @@ static const struct hda_fixup alc269_fixups[] = { .chained = true, .chain_id = ALC255_FIXUP_DELL1_MIC_NO_PRESENCE }, + [ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = { + .type = HDA_FIXUP_VERBS, + .v.verbs = (const struct hda_verb[]) { + /* Disable pass-through path for FRONT 14h */ + { 0x20, AC_VERB_SET_COEF_INDEX, 0x36 }, + { 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 }, + {} + }, + .chained = true, + .chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE + }, }; static const struct snd_pci_quirk alc269_fixup_tbl[] = { @@ -5646,10 +5665,10 @@ static const struct hda_model_fixup alc269_fixup_models[] = { {0x21, 0x03211020} static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = { - SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, + SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, ALC225_STANDARD_PINS, {0x14, 0x901701a0}), - SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, + SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, ALC225_STANDARD_PINS, {0x14, 0x901701b0}), SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", ALC255_FIXUP_DELL2_MIC_NO_PRESENCE, -- 1.9.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549660 Title: Fix speaker volume on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549660] [PATCH] ALSA: hda - Fixup speaker pass-through control for nid 0x14 on ALC225
On one of the machines we enable, we found that the actual speaker volume did not always correspond to the volume set in alsamixer. This patch fixes that problem. This patch was orginally written by Kailang @ Realtek, I've rebased it to fit sound git master. BugLink: https://bugs.launchpad.net/bugs/1549660 Co-Authored-By: Kailang <kail...@realtek.com> Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- sound/pci/hda/patch_realtek.c | 23 +-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index efd4980..ab353b0 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -3801,6 +3801,10 @@ static void alc_headset_mode_mic_in(struct hda_codec *codec, hda_nid_t hp_pin, static void alc_headset_mode_default(struct hda_codec *codec) { + static struct coef_fw coef0225[] = { + UPDATE_COEF(0x45, 0x3f<<10, 0x34<<10), + {} + }; static struct coef_fw coef0255[] = { WRITE_COEF(0x45, 0xc089), WRITE_COEF(0x45, 0xc489), @@ -3842,6 +3846,9 @@ static void alc_headset_mode_default(struct hda_codec *codec) }; switch (codec->core.vendor_id) { + case 0x10ec0225: + alc_process_coef_fw(codec, coef0225); + break; case 0x10ec0255: case 0x10ec0256: alc_process_coef_fw(codec, coef0255); @@ -4749,6 +4756,7 @@ enum { ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE, ALC293_FIXUP_LENOVO_SPK_NOISE, ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY, + ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, }; static const struct hda_fixup alc269_fixups[] = { @@ -5368,6 +5376,17 @@ static const struct hda_fixup alc269_fixups[] = { .type = HDA_FIXUP_FUNC, .v.func = alc233_fixup_lenovo_line2_mic_hotkey, }, + [ALC225_FIXUP_DELL1_MIC_NO_PRESENCE] = { + .type = HDA_FIXUP_VERBS, + .v.verbs = (const struct hda_verb[]) { + /* Disable pass-through path for FRONT 14h */ + { 0x20, AC_VERB_SET_COEF_INDEX, 0x36 }, + { 0x20, AC_VERB_SET_PROC_COEF, 0x57d7 }, + {} + }, + .chained = true, + .chain_id = ALC269_FIXUP_DELL1_MIC_NO_PRESENCE + }, }; static const struct snd_pci_quirk alc269_fixup_tbl[] = { @@ -5638,10 +5657,10 @@ static const struct hda_model_fixup alc269_fixup_models[] = { {0x21, 0x03211020} static const struct snd_hda_pin_quirk alc269_pin_fixup_tbl[] = { - SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, + SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, ALC225_STANDARD_PINS, {0x14, 0x901701a0}), - SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC269_FIXUP_DELL1_MIC_NO_PRESENCE, + SND_HDA_PIN_QUIRK(0x10ec0225, 0x1028, "Dell", ALC225_FIXUP_DELL1_MIC_NO_PRESENCE, ALC225_STANDARD_PINS, {0x14, 0x901701b0}), SND_HDA_PIN_QUIRK(0x10ec0255, 0x1028, "Dell", ALC255_FIXUP_DELL2_MIC_NO_PRESENCE, -- 1.9.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549660 Title: Fix speaker volume on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549660] [NEW] Fix speaker volume on a Dell machine
Public bug reported: On one of the machines we enable, we found that the actual speaker volume did not always correspond to the volume set in alsamixer. This bug is for tracking purposes; please do not triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (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/1549660 Title: Fix speaker volume on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548844] Re: Inspiron 13-7359: rfkill button has no effect
Verified with mainline kernel 4.5.0-040500rc5-generic, problem present there as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548844 Title: Inspiron 13-7359: rfkill button has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548844] [NEW] Inspiron 13-7359: rfkill button has no effect
Public bug reported: Nothing happens when the button to enable/disable rfkill (a k a "airplane mode" or "wifi/bluetooth disable") is pressed. Most other buttons seems to work according to evtest although some of them has no effect (and the "switch video mode" button generates Alt-P). Some of the buttons generate messages like: [ 335.755925] dell_wmi: Unknown WMI event type 0x00: 0xe00c [ 335.755928] dell_wmi: Unknown WMI event type 0x00: 0x3 ...but the rfkill button is not one of them. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1809 F pulseaudio CurrentDesktop: Unity Date: Tue Feb 23 15:26:41 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (87 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-6-generic N/A linux-backports-modules-4.4.0-6-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548844 Title: Inspiron 13-7359: rfkill button has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135355] Bug 1353355
Hi Kailang, Stanley Hsiao and I have again confirmed the bug of sound coming from speaker even though the "Speaker Playback Switch" is muted, and the amp-out on 0x14 is 0x80 (muted). In addition "Speaker Playback Volume" was also set to the minimum value (see the amp-out on node 0x02) so that should *also* have prevented the speaker from having output. Note that this bug is only present after applying your patch to enable UAJ on the codec. The attached alsa-info is taken while sound was playing back through the speaker even when it was supposed to be muted. I hope it can be of assistance to you. Thanks! -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic ** Attachment added: "alsa-info.txt.q5CzKNx7En" https://bugs.launchpad.net/bugs/135355/+attachment/4575479/+files/alsa-info.txt.q5CzKNx7En -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135355 Title: error on installation of isdnutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isdnutils/+bug/135355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] [PATCH] [xenial] (upstream) HID: multitouch: fix input mode switching on some Elan panels
From: Benjamin Tissoires <benjamin.tissoi...@redhat.com> as reported by https://bugzilla.kernel.org/show_bug.cgi?id=108481 This bug reports mentions 6d4f5440 ("HID: multitouch: Fetch feature reports on demand for Win8 devices") as the origin of the problem but this commit actually masked 2 firmware bugs that are annihilating each other: The report descriptor declares two features in reports 3 and 5: 0x05, 0x0d,// Usage Page (Digitizers) 318 0x09, 0x0e,// Usage (Device Configuration)320 0xa1, 0x01,// Collection (Application)322 0x85, 0x03,// Report ID (3) 324 0x09, 0x22,// Usage (Finger) 326 0xa1, 0x00,// Collection (Physical) 328 0x09, 0x52,// Usage (Inputmode) 330 0x15, 0x00,// Logical Minimum (0) 332 0x25, 0x0a,// Logical Maximum (10) 334 0x75, 0x08,// Report Size (8) 336 0x95, 0x02,// Report Count (2) 338 0xb1, 0x02,// Feature (Data,Var,Abs)340 0xc0, // End Collection 342 0x09, 0x22,// Usage (Finger) 343 0xa1, 0x00,// Collection (Physical) 345 0x85, 0x05,// Report ID (5) 347 0x09, 0x57,// Usage (Surface Switch)349 0x09, 0x58,// Usage (Button Switch) 351 0x15, 0x00,// Logical Minimum (0) 353 0x75, 0x01,// Report Size (1) 355 0x95, 0x02,// Report Count (2) 357 0x25, 0x03,// Logical Maximum (3) 359 0xb1, 0x02,// Feature (Data,Var,Abs)361 0x95, 0x0e,// Report Count (14) 363 0xb1, 0x03,// Feature (Cnst,Var,Abs)365 0xc0, // End Collection 367 The report ID 3 presents 2 input mode features, while only the first one is handled by the device. Given that we did not checked if one was previously assigned, we were dealing with the ignored featured and we should never have been able to switch this panel into the multitouch mode. However, the firmware presents an other bugs which allowed 6d4f5440 to counteract the faulty report descriptor. When we request the values of the feature 5, the firmware answers "03 03 00". The fields are correct but the report id is wrong. Before 6d4f5440, we retrieved all the features and injected them in the system. So when we called report 5, we injected in the system the report 3 with the values "03 00". Setting the second input mode to 03 in this report changed it to "03 03" and the touchpad switched to the mt mode. We could have set anything in the second field because the actual value (the first 03 in this report) was given by the query of report ID 5. To sum up: 2 bugs in the firmware were hiding that we were accessing the wrong feature. Signed-off-by: Benjamin Tissoires <benjamin.tissoi...@redhat.com> Signed-off-by: Jiri Kosina <jkos...@suse.cz> BugLink: https://bugs.launchpad.net/bugs/1540511 (cherry picked from commit 73e7d63efb4d774883a338997943bfa59e127085) Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- drivers/hid/hid-multitouch.c | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c index 351ddd2..4ee7716 100644 --- a/drivers/hid/hid-multitouch.c +++ b/drivers/hid/hid-multitouch.c @@ -357,8 +357,19 @@ static void mt_feature_mapping(struct hid_device *hdev, break; } - td->inputmode = field->report->id; - td->inputmode_index = usage->usage_index; + if (td->inputmode < 0) { + td->inputmode = field->report->id; + td->inputmode_index = usage->usage_index; + } else { + /* +* Some elan panels wrongly declare 2 input mode +* features, and silently ignore when we set the +* value in the second field. Skip the second feature +* and hope for the best. +*/ + dev_info(>dev, +"Ignoring the extra HID_DG_INPUTMODE\n"); + } break; case HI
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
Ok, I've now built and tested a kernel with 4.4 + the below commit and can confirm that this commit fixes the touchpad issue for me. commit 8a7fa6187191f005d4b6d29913de6e128cc778e2 Author: Benjamin TissoiresDate: Tue Dec 1 12:41:38 2015 +0100 HID: multitouch: fix input mode switching on some Elan panels ** Bug watch added: Linux Kernel Bug Tracker #108481 http://bugzilla.kernel.org/show_bug.cgi?id=108481 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
https://bugzilla.kernel.org/show_bug.cgi?id=108481 ** 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/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
it bisect start # new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1 git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d # old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4 git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc # old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863 # new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux git bisect new 984065055e6e39f8dd812529e11922374bd39352 # new: [a016af2e70bfca23f2f5de7d8708157b86ea374d] Merge tag 'sound-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound git bisect new a016af2e70bfca23f2f5de7d8708157b86ea374d # new: [d45187aaf0e256d23da2f7694a7826524499aa31] Merge branch 'dmi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging git bisect new d45187aaf0e256d23da2f7694a7826524499aa31 # new: [c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid git bisect new c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67 # old: [5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05] Merge tag 'devicetree-for-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux git bisect old 5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05 # old: [63f729cb4aa9a224cfd6bb35eab6b4556c29115d] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs git bisect old 63f729cb4aa9a224cfd6bb35eab6b4556c29115d # old: [210c7c1750fdf769647d1d526c9ea34c412c9eee] NFS: Use wait_on_atomic_t() for unlock after readahead git bisect old 210c7c1750fdf769647d1d526c9ea34c412c9eee Looked through remaining commits, I'm going to try this one next, looks promising: commit 73e7d63efb4d774883a338997943bfa59e127085 Author: Benjamin TissoiresDate: Tue Dec 1 12:41:38 2015 +0100 HID: multitouch: fix input mode switching on some Elan panels -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
Tested kernels so far: 4.3.0-7 ubuntu - good (touchpad working) 4.5.0-040500rc3 - good (touchpad working) 4.4.0-4 ubuntu - bad (touchpad not working) 4.4.1-040401 - bad (touchpad not working) 4.5.0-040500rc1 - good (touchpad working) Looks like a temporary regression in 4.4 - maybe we can bisect between 4.4 and 4.5rc1 to see if it's something we can backport? ** Tags added: kernel-fixed-upstream ** 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/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
A few more commits... # new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1 git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d # old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4 git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc # old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863 # new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux git bisect new 984065055e6e39f8dd812529e11922374bd39352 # new: [a016af2e70bfca23f2f5de7d8708157b86ea374d] Merge tag 'sound-4.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound git bisect new a016af2e70bfca23f2f5de7d8708157b86ea374d # new: [d45187aaf0e256d23da2f7694a7826524499aa31] Merge branch 'dmi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging git bisect new d45187aaf0e256d23da2f7694a7826524499aa31 # new: [c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67] Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid git bisect new c2848f2eef4dd08b0fd2a8eba1694fd8e77ddb67 # old: [5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05] Merge tag 'devicetree-for-4.5' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux git bisect old 5339f9d4c2ceccab00b28d65bd5c2b2cd6a3de05 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] Re: Touchpad not working (4.3 -> 4.4 regression)
I'm working on it, here's the result so far: $ git bisect log git bisect start # new: [92e963f50fc74041b5e9e744c330dca48e04f08d] Linux 4.5-rc1 git bisect new 92e963f50fc74041b5e9e744c330dca48e04f08d # old: [afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc] Linux 4.4 git bisect old afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc # old: [1289ace5b4f70f1e68ce785735b82c7e483de863] Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi git bisect old 1289ace5b4f70f1e68ce785735b82c7e483de863 # new: [984065055e6e39f8dd812529e11922374bd39352] Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux git bisect new 984065055e6e39f8dd812529e11922374bd39352 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540970] Re: The BQ 4.5 says I'm roaming when I'm not
** Description changed: + Mobile data does not work, because it says I'm roaming - but I'm not + close to any foreign country, so it shouldn't say that. + + + ~$ system-image-cli -i + current build number: 249 + device name: krillin + channel: ubuntu-touch/rc-proposed/bq-aquaris.en + last update: 2016-02-02 16:45:36 + version version: 249 + version ubuntu: 20160202 + version device: 20160108-efc96d8 + version custom: 20160111-926-36--vivid + + $ nmcli d - DEVICE TYPE STATE CONNECTION - ril_0gsm disconnected -- - ril_1gsm unavailable -- - ifb0 ifb unmanaged -- - ifb1 ifb unmanaged -- - lo loopback unmanaged -- - ip6tnl0 unknown unmanaged -- - sit0 unknown unmanaged -- - tunl0unknown unmanaged -- + DEVICE TYPE STATE CONNECTION + ril_0gsm disconnected -- + ril_1gsm unavailable -- + ifb0 ifb unmanaged -- + ifb1 ifb unmanaged -- + lo loopback unmanaged -- + ip6tnl0 unknown unmanaged -- + sit0 unknown unmanaged -- + tunl0unknown unmanaged -- - $ /usr/share/ofono/scripts/list-contexts + $ /usr/share/ofono/scripts/list-contexts [ /ril_1 ] [ /ril_0 ] - [ /ril_0/context1 ] - Preferred = 0 - Name = Tele2 Internet - Active = 0 - Protocol = ip - Type = internet - Username = - Settings = { } - Password = - AccessPointName = 4g.tele2.se - IPv6.Settings = { } - AuthenticationMethod = chap + [ /ril_0/context1 ] + Preferred = 0 + Name = Tele2 Internet + Active = 0 + Protocol = ip + Type = internet + Username = + Settings = { } + Password = + AccessPointName = 4g.tele2.se + IPv6.Settings = { } + AuthenticationMethod = chap - [ /ril_0/context2 ] - Preferred = 0 - Name = Tele2 MMS - Protocol = ip - Type = mms - MessageProxy = 130.244.202.30:8080 - IPv6.Settings = { } - AuthenticationMethod = chap - Password = - Active = 0 - Username = - Settings = { } - AccessPointName = 4g.tele2.se - MessageCenter = http://mmsc.tele2.se + [ /ril_0/context2 ] + Preferred = 0 + Name = Tele2 MMS + Protocol = ip + Type = mms + MessageProxy = 130.244.202.30:8080 + IPv6.Settings = { } + AuthenticationMethod = chap + Password = + Active = 0 + Username = + Settings = { } + AccessPointName = 4g.tele2.se + MessageCenter = http://mmsc.tele2.se - [ /ril_0/context3 ] - Preferred = 0 - Name = Tele2 Internet 3G - Active = 0 - Protocol = ip - Type = internet - Username = - Settings = { } - Password = - AccessPointName = internet.tele2.se - IPv6.Settings = { } - AuthenticationMethod = chap + [ /ril_0/context3 ] + Preferred = 0 + Name = Tele2 Internet 3G + Active = 0 + Protocol = ip + Type = internet + Username = + Settings = { } + Password = + AccessPointName = internet.tele2.se + IPv6.Settings = { } + AuthenticationMethod = chap - [ /ril_0/context4 ] - Preferred = 0 - Name = Tele2 MMS 3G - Protocol = ip - Type = mms - MessageProxy = 130.244.202.30:8080 - IPv6.Settings = { } - AuthenticationMethod = chap - Password = - Active = 0 - Username = - Settings = { } - AccessPointName = internet.tele2.se - MessageCenter = http://mmsc.tele2.se + [ /ril_0/context4 ] + Preferred = 0 + Name = Tele2 MMS 3G + Protocol = ip + Type = mms + MessageProxy = 130.244.202.30:8080 + IPv6.Settings = { } + AuthenticationMethod = chap + Password = + Active = 0 + Username = + Settings = { } + AccessPointName = internet.tele2.se + MessageCenter = http://mmsc.tele2.se -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540970 Title: The BQ 4.5 says I'm roaming when I'm not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540970] [NEW] The BQ 4.5 says I'm roaming when I'm not
Public bug reported: $ nmcli d DEVICE TYPE STATE CONNECTION ril_0gsm disconnected -- ril_1gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- lo loopback unmanaged -- ip6tnl0 unknown unmanaged -- sit0 unknown unmanaged -- tunl0unknown unmanaged -- $ /usr/share/ofono/scripts/list-contexts [ /ril_1 ] [ /ril_0 ] [ /ril_0/context1 ] Preferred = 0 Name = Tele2 Internet Active = 0 Protocol = ip Type = internet Username = Settings = { } Password = AccessPointName = 4g.tele2.se IPv6.Settings = { } AuthenticationMethod = chap [ /ril_0/context2 ] Preferred = 0 Name = Tele2 MMS Protocol = ip Type = mms MessageProxy = 130.244.202.30:8080 IPv6.Settings = { } AuthenticationMethod = chap Password = Active = 0 Username = Settings = { } AccessPointName = 4g.tele2.se MessageCenter = http://mmsc.tele2.se [ /ril_0/context3 ] Preferred = 0 Name = Tele2 Internet 3G Active = 0 Protocol = ip Type = internet Username = Settings = { } Password = AccessPointName = internet.tele2.se IPv6.Settings = { } AuthenticationMethod = chap [ /ril_0/context4 ] Preferred = 0 Name = Tele2 MMS 3G Protocol = ip Type = mms MessageProxy = 130.244.202.30:8080 IPv6.Settings = { } AuthenticationMethod = chap Password = Active = 0 Username = Settings = { } AccessPointName = internet.tele2.se MessageCenter = http://mmsc.tele2.se ** Affects: ofono (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/1540970 Title: The BQ 4.5 says I'm roaming when I'm not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540970] Re: The BQ 4.5 says I'm roaming when I'm not
list-modems -p (when it says it's roaming) ** Attachment added: "list-modems.whenitsNOTworking.txt" https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+attachment/4562301/+files/list-modems.whenitsNOTworking.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540970 Title: The BQ 4.5 says I'm roaming when I'm not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540970] Re: The BQ 4.5 says I'm roaming when I'm not
For comparison, here's the output of the same commands when it's working ** Attachment added: "whenitsworking.txt" https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+attachment/4562298/+files/whenitsworking.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540970 Title: The BQ 4.5 says I'm roaming when I'm not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1540970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540353] [NEW] xargs: invalid number for -s option
Public bug reported: I ran "sudo apt-get autoremove" and when python3.4 and libpython3.4-minimal:amd64 were removed, the following error was shown on the screen: Removing python3.4-minimal (3.4.4-1) ... Unlinking and removing bytecode for runtime python3.4 Removing libpython3.4-minimal:amd64 (3.4.4-1) ... xargs: invalid number for -s option Usage: xargs [OPTION]... COMMAND [INITIAL-ARGS]... Run COMMAND with arguments INITIAL-ARGS and more arguments read from input. ...followed by instructions on how to use xargs properly. Probably some maintainer scripting errors? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libpython3.4-minimal (not installed) ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 1 13:46:27 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: python3.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540353 Title: xargs: invalid number for -s option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1540353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540406] [NEW] warning: file-aligned section .text extends beyond end of file
Public bug reported: When running a dist-upgrade, I received the following warning: Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ... warning: file-aligned section .text extends beyond end of file warning: checksum areas are greater than image size. Invalid section table? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 1 15:58:45 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540406 Title: warning: file-aligned section .text extends beyond end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540511] [NEW] Touchpad not working (4.3 -> 4.4 regression)
Public bug reported: When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not working. When booting 4.3 kernels, the touchpad is works. Expected: When I move a finger touching the touchpad, an arrow should move accordingly on the screen. What happens instead: nothing. I've tried an upstream 4.4 kernel; problem is present there as well. I've booted with pci=noaer due to another bug that would otherwise spam dmesg. Removing it does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: david 1759 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 1 18:49:25 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-2-generic N/A linux-backports-modules-4.4.0-2-generic N/A linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Description changed: When booting the latest xenial kernel (4.4.0-2.16), my touchpad is not working. When booting 4.3 kernels, the touchpad is works. Expected: When I move a finger touching the touchpad, an arrow should move accordingly on the screen. What happens instead: nothing. + + I've tried an upstream 4.4 kernel; problem is present there as well. + + I've booted with pci=noaer due to another bug that would otherwise spam + dmesg. Removing it does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: david 1759 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: david 1759 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 1 18:49:25 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent pci=noaer quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-2-generic N/A - linux-backports-modules-4.4.0-2-generic N/A - linux-firmware 1.155 + linux-restricted-modules-4.4.0-2-generic N/A + linux-backports-modules-4.4.0-2-generic N/A + linux-firmware 1.155 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540511 Title: Touchpad not working (4.3 -> 4.4 regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540406] Re: warning: file-aligned section .text extends beyond end of file
** Description changed: When running a dist-upgrade, I received the following warning: Setting up linux-signed-image-4.4.0-2-generic (4.4.0-2.16) ... warning: file-aligned section .text extends beyond end of file warning: checksum areas are greater than image size. Invalid section table? + + Note: I've tried booting the kernel with dmesg enabled, it seems to boot + just fine. See https://launchpadlibrarian.net/235948033/CurrentDmesg.txt + for when I booted it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-signed-image-4.4.0-2-generic 4.4.0-2.16 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 1 15:58:45 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (65 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540406 Title: warning: file-aligned section .text extends beyond end of file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1540406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1534157] [NEW] alsamixer controls pulseaudio volume by default
Public bug reported: Hi Luke, Is there a reason you dropped unset_pulse_internal.patch (and two other patches) from the latest version of alsa-utils? Now when one runs alsamixer, it goes to PulseAudio by default. Is this expected behaviour nowadays? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-utils 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 14 14:26:15 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (47 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-utils (Ubuntu) Importance: Undecided Assignee: Luke Yelavich (themuso) Status: New ** Tags: amd64 apport-bug xenial ** Changed in: alsa-utils (Ubuntu) Assignee: (unassigned) => Luke Yelavich (themuso) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534157 Title: alsamixer controls pulseaudio volume by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1534157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529624] Re: Lenovo E50-80 inverted microphone not detected properly
Inform userspace that one channel of the internal mic has reversed polarity, so it does not attempt to add both channels together and end up with silence. Cc: sta...@vger.kernel.org Reported-by: Andrzej Mendel <andrzej.men...@gmail.com> Alsa-info: http://www.alsa-project.org/db/?f=3088f82a0cf977855f92af9db8ad406c04f71efa BugLink: https://bugs.launchpad.net/bugs/1529624 Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- sound/pci/hda/patch_realtek.c | 8 1 file changed, 8 insertions(+) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 3a89d82..2fdda51 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -4666,6 +4666,7 @@ enum { ALC290_FIXUP_SUBWOOFER, ALC290_FIXUP_SUBWOOFER_HSJACK, ALC269_FIXUP_THINKPAD_ACPI, + ALC269_FIXUP_DMIC_THINKPAD_ACPI, ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, ALC255_FIXUP_DELL2_MIC_NO_PRESENCE, ALC255_FIXUP_HEADSET_MODE, @@ -5103,6 +5104,12 @@ static const struct hda_fixup alc269_fixups[] = { .type = HDA_FIXUP_FUNC, .v.func = hda_fixup_thinkpad_acpi, }, + [ALC269_FIXUP_DMIC_THINKPAD_ACPI] = { + .type = HDA_FIXUP_FUNC, + .v.func = alc_fixup_inv_dmic, + .chained = true, + .chain_id = ALC269_FIXUP_THINKPAD_ACPI, + }, [ALC255_FIXUP_DELL1_MIC_NO_PRESENCE] = { .type = HDA_FIXUP_PINS, .v.pins = (const struct hda_pintbl[]) { @@ -5457,6 +5464,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = { SND_PCI_QUIRK(0x17aa, 0x2226, "ThinkPad X250", ALC292_FIXUP_TPT440_DOCK), SND_PCI_QUIRK(0x17aa, 0x2233, "Thinkpad", ALC293_FIXUP_LENOVO_SPK_NOISE), SND_PCI_QUIRK(0x17aa, 0x30bb, "ThinkCentre AIO", ALC233_FIXUP_LENOVO_LINE2_MIC_HOTKEY), + SND_PCI_QUIRK(0x17aa, 0x3902, "Lenovo E50-80", ALC269_FIXUP_DMIC_THINKPAD_ACPI), SND_PCI_QUIRK(0x17aa, 0x3977, "IdeaPad S210", ALC283_FIXUP_INT_MIC), SND_PCI_QUIRK(0x17aa, 0x3978, "IdeaPad Y410P", ALC269_FIXUP_NO_SHUTUP), SND_PCI_QUIRK(0x17aa, 0x5013, "Thinkpad", ALC269_FIXUP_LIMIT_INT_MIC_BOOST), -- 1.9.1 ** Changed in: alsa-driver (Ubuntu) Status: New => In Progress ** Changed in: alsa-driver (Ubuntu) Assignee: (unassigned) => David Henningsson (diwic) ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: David Henningsson (diwic) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529624 Title: Lenovo E50-80 inverted microphone not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477838] Re: [MX4] Crackling sound after playing audio and suspended
I don't think this is PulseAudio. It's probably something in the kernel or the Android HAL. Anyway, after PulseAudio has been playing a sound, there is a five second timeout until PulseAudio closes the hw stream. Or put it another way, PulseAudio plays back five seconds of silence after every sound (assuming there's nothing else that wants to play). So it makes some sense that doing things within five seconds after a sound has stopped may cause a different chain of events. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477838 Title: [MX4] Crackling sound after playing audio and suspended To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1477838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530101] [NEW] Printing SVG image renders wrong
Public bug reported: Not sure this is the right package, but I need to start somewhere. Steps to reproduce: Download https://openclipart.org/download/224778/Green-Floral-Frame.svg Display it with eog, notice that it looks just fine. Click "Print preview" for either a real printer or the PDF printer. Notice that the image is now broken. Something similar happens when trying to print from inkscape (Vector rendering is broken, Bitmap rendering is okay), so I suspect this is somewhere in the printing backend. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.2-1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Wed Dec 30 12:41:07 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (32 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) KernLog: [26189.077761] audit: type=1107 audit(1451375902.050:24): pid=765 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/ColorManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.40" pid=14901 label="/usr/bin/evince-previewer" peer_pid=1091 peer_label="unconfined" Lpstat: device for HP-Officejet-5740-series: hp:/net/Officejet_5740_series?zc=HP645106173E07 MachineType: Dell Inc. Inspiron 13-7359 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Officejet-5740-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Officejet-5740-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: cups UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd09/08/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530101 Title: Printing SVG image renders wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1530101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530101] Re: Printing SVG image renders wrong
** Attachment added: "Broken SVG print preview.png" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1530101/+attachment/4542146/+files/Broken%20SVG%20print%20preview.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530101 Title: Printing SVG image renders wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1530101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
Hi, Indeed booting with pci=noaer (as suggested in the other bug) works around this issue as well. I'll use that for the time being. Thanks for working on it! // David On 2015-12-29 16:58, Bjorn Helgaas wrote: > On Fri, Dec 18, 2015 at 11:30:33AM +0100, David Henningsson wrote: >> Hi Linux PCI maintainers, >> >> My dmesg gets filled with a few lines repeated over and over again: >> >> pcieport :00:1c.0: AER: Corrected error received: id=00e0 >> pcieport :00:1c.0: can't find device of ID00e0 >> pcieport :00:1c.0: AER: Corrected error received: id=00e0 >> pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, >> type=Physical Layer, id=00e0(Receiver ID) >> pcieport :00:1c.0: device [8086:9d14] error >> status/mask=0001/2000 >> pcieport :00:1c.0:[ 0] Receiver Error >> >> This happens 10-30 times per second (!), so dmesg fills up quickly. >> The bug is present in both vanilla and Ubuntu kernels. > > This is a pretty obvious bug in our AER code. We normally clear > correctable errors by writing the PCI_ERR_COR_STATUS register in > handle_error_source(). The execution path looks like this: > >aer_isr_one_error > aer_print_port_info > if (find_source_device()) >aer_process_err_devices > handle_error_source >pci_write_config_dword(dev, PCI_ERR_COR_STATUS, ...) > > In this case, find_source_device() printed "can't find device of > ID00e0" [sic] and returned false, so we don't call > aer_process_err_devices(). The error is never cleared, so > we discover it again and again. > > I'll work on fixing this. Incidentally, there's another report > with similar symptoms here: > >https://bugzilla.kernel.org/show_bug.cgi?id=109691 > > Bjorn > -- David Henningsson, Canonical Ltd. https://launchpad.net/~diwic ** Bug watch added: Linux Kernel Bug Tracker #109691 http://bugzilla.kernel.org/show_bug.cgi?id=109691 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
** Bug watch removed: Linux Kernel Bug Tracker #109691 http://bugzilla.kernel.org/show_bug.cgi?id=109691 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
@simplehuman: Don't worry about this patch for now, it's just to help me remember to upstream it later. ** Patch added: "0001-alsa-mixer-Add-Mic-Source-for-Xonar-STX.patch" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+attachment/4536658/+files/0001-alsa-mixer-Add-Mic-Source-for-Xonar-STX.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
> A new option "Front Mic" in sound settings appeared. But... it is not working. Did you see my update in comment #30? It should be "Front Panel", not "Front Mic". After editing, reboot and restart PulseAudio again. Is it still not working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487141] Re: "wants to record audio" not localized
** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487141 Title: "wants to record audio" not localized To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
Start alsamixer from a terminal. You might need to press F6 to select the Xonar sound card, then F4 to see recording controls. Use arrow keys to find a control named "Mic Source" and change it from "Mic Jack" to "Front Panel". Does this enable recording for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
Could you try the following: Edit this file: /usr/share/pulseaudio/alsa-mixer/paths/analog-input-front-mic.conf And add these lines: [Element Mic Source] enumeration = select [Option Mic Source:Front Mic] name = analog-input-microphone-front required-any = any Then edit this file: /usr/share/pulseaudio/alsa-mixer/paths/analog-input-mic.conf And add these lines: [Element Mic Source] enumeration = select [Option Mic Source:Mic Jack] name = analog-input-microphone required-any = any Now reboot your computer (or restart PulseAudio). You should now have a "Front Microphone" representing the front panel mic and a "Microphone" representing the other mic jack (wherever that is, probably on the rear). I'm also attaching a patch which can be upstreamed once you confirm that this is actually working. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
Sorry, there's a mistake in the above instruction. For the /usr/share/pulseaudio/alsa-mixer/paths/analog-input-front-mic.conf file, instead add these lines: [Element Mic Source] enumeration = select [Option Mic Source:Front Panel] name = analog-input-microphone-front required-any = any (Notice how "Front Mic" should say "Front panel" instead.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526330] [PATCH] ALSA: hda - Fix headphone mic input on a few Dell ALC293 machines
These laptops support both headphone, headset and mic modes for the 3.5mm jack. Cc: sta...@vger.kernel.org BugLink: https://bugs.launchpad.net/bugs/1526330 Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- sound/pci/hda/patch_realtek.c | 17 - 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 8dd2ac1..b745a72 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -4606,6 +4606,7 @@ enum { ALC288_FIXUP_DISABLE_AAMIX, ALC292_FIXUP_DELL_E7X, ALC292_FIXUP_DISABLE_AAMIX, + ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK, ALC298_FIXUP_DELL1_MIC_NO_PRESENCE, ALC275_FIXUP_DELL_XPS, ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE, @@ -5169,6 +5170,12 @@ static const struct hda_fixup alc269_fixups[] = { .chained = true, .chain_id = ALC269_FIXUP_DELL2_MIC_NO_PRESENCE }, + [ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK] = { + .type = HDA_FIXUP_FUNC, + .v.func = alc_fixup_disable_aamix, + .chained = true, + .chain_id = ALC293_FIXUP_DELL1_MIC_NO_PRESENCE + }, [ALC292_FIXUP_DELL_E7X] = { .type = HDA_FIXUP_FUNC, .v.func = alc_fixup_dell_xps13, @@ -5247,11 +5254,11 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = { SND_PCI_QUIRK(0x1028, 0x06c7, "Dell", ALC255_FIXUP_DELL1_MIC_NO_PRESENCE), SND_PCI_QUIRK(0x1028, 0x06d9, "Dell", ALC293_FIXUP_DELL1_MIC_NO_PRESENCE), SND_PCI_QUIRK(0x1028, 0x06da, "Dell", ALC293_FIXUP_DELL1_MIC_NO_PRESENCE), - SND_PCI_QUIRK(0x1028, 0x06db, "Dell", ALC292_FIXUP_DISABLE_AAMIX), - SND_PCI_QUIRK(0x1028, 0x06dd, "Dell", ALC292_FIXUP_DISABLE_AAMIX), - SND_PCI_QUIRK(0x1028, 0x06de, "Dell", ALC292_FIXUP_DISABLE_AAMIX), - SND_PCI_QUIRK(0x1028, 0x06df, "Dell", ALC292_FIXUP_DISABLE_AAMIX), - SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", ALC292_FIXUP_DISABLE_AAMIX), + SND_PCI_QUIRK(0x1028, 0x06db, "Dell", ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK), + SND_PCI_QUIRK(0x1028, 0x06dd, "Dell", ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK), + SND_PCI_QUIRK(0x1028, 0x06de, "Dell", ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK), + SND_PCI_QUIRK(0x1028, 0x06df, "Dell", ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK), + SND_PCI_QUIRK(0x1028, 0x06e0, "Dell", ALC293_FIXUP_DISABLE_AAMIX_MULTIJACK), SND_PCI_QUIRK(0x1028, 0x0704, "Dell XPS 13", ALC256_FIXUP_DELL_XPS_13_HEADPHONE_NOISE), SND_PCI_QUIRK(0x1028, 0x164a, "Dell", ALC293_FIXUP_DELL1_MIC_NO_PRESENCE), SND_PCI_QUIRK(0x1028, 0x164b, "Dell", ALC293_FIXUP_DELL1_MIC_NO_PRESENCE), -- 1.9.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526330 Title: Fix mic-in mode for a few Dell laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1526330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526330] [NEW] Fix mic-in mode for a few Dell laptops
Public bug reported: This is bug is for tracking purposes only, please do not triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: David Henningsson (diwic) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => David Henningsson (diwic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526330 Title: Fix mic-in mode for a few Dell laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1526330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526330] Re: Fix mic-in mode for a few Dell laptops
** Changed in: linux (Ubuntu) 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/1526330 Title: Fix mic-in mode for a few Dell laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1526330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526337] [NEW] Accelerometer does not change orientation
Public bug reported: I have a 2-in-1 laptop with an accelerometer (Inspiron 13-7359). I would like the screen to change orientation automatically when the screen is rotated. I've noticed that the accelerometer works correctly, by installing iio-sensors-proxy and manually executing d-Bus methods. I've also noticed that upstream gnome-settings-daemon uses iio-sensors-proxy whereas unity-settings-daemon does not. That's as far as I've come. Do you think we should add iio-sensors-proxy to main and the default image, and also grab Gnome's patches for orientation? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-settings-daemon 15.04.1+16.04.20151214-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 15 14:59:31 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: - I have a laptop with an accelerometer (Inspiron 13-7359). I would like - the screen to change orientation automatically when the screen is + I have a 2-in-1 laptop with an accelerometer (Inspiron 13-7359). I would + like the screen to change orientation automatically when the screen is rotated. - I've noticed that the accelerometer works correctly, by installing iio-sensors-proxy and manually executing d-Bus methods. - I've also noticed that upstream gnome-settings-daemon uses iio-sensors-proxy whereas unity-settings-daemon does not. + I've noticed that the accelerometer works correctly, by installing iio-sensors-proxy and manually executing d-Bus methods. + I've also noticed that upstream gnome-settings-daemon uses iio-sensors-proxy whereas unity-settings-daemon does not. That's as far as I've come. Do you think we should add iio-sensors-proxy to main and the default image, and also grab Gnome's patches for orientation? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-settings-daemon 15.04.1+16.04.20151214-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 15 14:59:31 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-28 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526337 Title: Accelerometer does not change orientation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1526337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
The spam rate is 150 lines per second. With ~80 characters per line, that's about 50 MB per hour. As a very rough measure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523232] Re: Packard Bell DOTS inverted internal microphone
> Otherwise, the modules are not installed with a message saying that they are included since 3.99 kernel (not sure of the version as I didn't save the results) Oops, a problem with the DKMS packaging. Thanks for the heads up, will be fixed in the next build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523232 Title: Packard Bell DOTS inverted internal microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523232] Re: Packard Bell DOTS inverted internal microphone
On the internal mic of the Packard Bell DOTS, one channel has an inverted signal. Add a quirk to fix this up. Cc: sta...@vger.kernel.org BugLink: https://bugs.launchpad.net/bugs/1523232 Signed-off-by: David Henningsson <david.hennings...@canonical.com> --- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+) diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c index 9bedf7c..ebc5362 100644 --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -6409,6 +6409,7 @@ static const struct hda_fixup alc662_fixups[] = { static const struct snd_pci_quirk alc662_fixup_tbl[] = { SND_PCI_QUIRK(0x1019, 0x9087, "ECS", ALC662_FIXUP_ASUS_MODE2), SND_PCI_QUIRK(0x1025, 0x022f, "Acer Aspire One", ALC662_FIXUP_INV_DMIC), + SND_PCI_QUIRK(0x1025, 0x0241, "Packard Bell DOTS", ALC662_FIXUP_INV_DMIC), SND_PCI_QUIRK(0x1025, 0x0308, "Acer Aspire 8942G", ALC662_FIXUP_ASPIRE), SND_PCI_QUIRK(0x1025, 0x031c, "Gateway NV79", ALC662_FIXUP_SKU_IGNORE), SND_PCI_QUIRK(0x1025, 0x0349, "eMachines eM250", ALC662_FIXUP_INV_DMIC), -- 1.9.1 ** Changed in: alsa-driver (Ubuntu) Status: New => In Progress ** Changed in: alsa-driver (Ubuntu) Assignee: (unassigned) => David Henningsson (diwic) ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523232 Title: Packard Bell DOTS inverted internal microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523232] Re: Packard Bell DOTS inverted internal microphone
** Changed in: linux (Ubuntu) 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/1523232 Title: Packard Bell DOTS inverted internal microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504175]
The easy way out is just to blame the hardware. The harder way is to make sure we don't block other things while waiting for the hardware. Which should be possible - the tricky thing is to avoid creating races at the same time... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504175 Title: Starting pavucontrol creates sound drop-out [related to C270/C910 Logitech webcam] To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1504175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521606] Re: [Inspiron 13-7359, Conexant CX20722, Black Mic, Left] Unreliable jack detection
@Raymond, the pcieport errors are unrelated and already reported as bug 1521173 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521606 Title: [Inspiron 13-7359, Conexant CX20722, Black Mic, Left] Unreliable jack detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1521606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521664] Re: what-did-you-plug-in dialog does not show up
** Branch linked: lp:~diwic/unity-settings-daemon/lp1521664 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521664 Title: what-did-you-plug-in dialog does not show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1521664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521173] Re: AER: Corrected error received: id=00e0
I've tried upgrading BIOS to 1.2.0 (latest version on Dell website) and also with the v4.4-rc3-wily kernel. The dmesg is still spammed with the same error. ** 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/1521173 Title: AER: Corrected error received: id=00e0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521664] Re: what-did-you-plug-in dialog does not show up
Looks like launchpad is working better today, so I just submitted a MP. > Also is the name likely to change again? Could we get an autopkgtest somewhere to let us know that u-s-d needs updating next time? That is a good question and I understand your concern; but I think the likelyhood of the port names changing again is relatively low, and writing a test for it is relatively hard (not sure how to convince PulseAudio that the autopkgtest server has a headset mic). So I think for this case it is better to spend the time fixing more bugs instead :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521664 Title: what-did-you-plug-in dialog does not show up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1521664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521606] Re: [Inspiron 13-7359, Conexant CX20722, Black Mic, Left] Unreliable jack detection
Needs further investigation ** Changed in: alsa-driver (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521606 Title: [Inspiron 13-7359, Conexant CX20722, Black Mic, Left] Unreliable jack detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1521606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs