[Touch-packages] [Bug 1500387] Re: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored
** Also affects: dell-sputnik Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1500387 Title: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored Status in Dell Sputnik: New Status in xorg package in Ubuntu: Incomplete Bug description: [Summary] System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored [Reproduce Steps] 1. System boots to a black screen 2. Close the lid and reopen it [Results] Expected: Normal boot Actual: Blank screen [Additional Information] CID: Base Image: Product Name: "Ubuntu 14.04.3 LTS" on Dell XPS 13 9343 BIOS Version: A05 Kernel Version: 3.13.0-63-generic CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GPU: Intel Corporation Broadwell-U Integrated Graphics (rev 09) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1500387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04
** Summary changed: - [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10 + [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1423415 Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04 Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: New Bug description: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423415] [NEW] [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10
Public bug reported: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: dell-sputnik Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: dell-sputnik Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1423415 Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10 Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: New Bug description: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423413] [NEW] [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all
Public bug reported: Note that I am forcing the audio into HDA mode. (It has two modes: HDA and I2S.) In HDA mode, audio out works. The mic is known with a previous version of ALSA (Sept 3 2014 snapshot). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:40:01 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 2 2 : a u d i o o p e n e r r o r : D e v i c e o r r e s o u r c e b u s y Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: dell-sputnik Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: dell-sputnik Importance: Undecided Status: New ** Description changed: Note that I am forcing the audio into HDA mode. (It has two modes: HDA and I2S.) In HDA mode, audio out works. The mic is known with a previous - version of ALSA. + version of ALSA (Sept 3 2014 snapshot). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0c: jared 4299 F...m arecord - /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio - /dev/snd/controlC1: jared 2929 F pulseaudio - /dev/snd/controlC0: jared 2929 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0c: jared 4299 F...m arecord + /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio + /dev/snd/controlC1: jared 2929 F pulseaudio + /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:40:01 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 2 2 : a u d i o o p e n e r r o r : D e v i c e o r r e s o u r c e b u s y Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0c: jared 4299 F...m arecord - /dev/snd/controlC1: jared 2929 F pulseaudio - /dev/snd/controlC0: jared 2929 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0c: jared 4299 F...m arecord + /dev/snd/controlC1: jared 2929 F pulseaudio + /dev/snd/controlC0: jared 2929 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc
[Touch-packages] [Bug 1315770] Re: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise
** Also affects: dell-sputnik Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315770 Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise Status in Dell Sputnik: New Status in “alsa-driver” package in Ubuntu: Confirmed Status in Fedora: New Bug description: When I connect the headphones, there is a strong hissing in both left and right side. It does not amplify or reduce along with the master volume. Instead, if I completely mute the master volume, the hissing disappears. It comes back as soon as I unmute the master volume. The internal speakers of the laptop are not affected: when headphones are not connected, there is no background hissing noise. Standard four questions: 1) Ubuntu release: 14.04 LTS 2) Package affected: kernel? (linux-image-3.13.0-24-generic) or maybe alsa-driver? 3) Unless I play music, I expect no to hear anything in the headphones 4) I get a background hissing noise in the headphones Thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sun1875 F pulseaudio /dev/snd/controlC1: sun1875 F pulseaudio CurrentDesktop: Unity Date: Sun May 4 02:46:01 2014 InstallationDate: Installed on 2014-05-02 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/06/2014:svnDellInc.:pnDellPrecisionM3800:pvrA03:rvnDellInc.:rnDellPrecisionM3800:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1315770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems
** Changed in: biosdevname (Ubuntu) Status: New => Opinion ** Changed in: systemd (Ubuntu) Status: New => Opinion ** Changed in: udev (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1347859 Title: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems Status in “biosdevname” package in Ubuntu: Opinion Status in “systemd” package in Ubuntu: Opinion Status in “udev” package in Ubuntu: Opinion Bug description: Relatively recent linux distribution upgrades have been causing computers' ethernet devices to be unexpectedly renamed. While I understand that consistent device naming solves problems on some systems (mostly multi-NIC servers and a few specialty embedded devices), unilaterally forcing these changes on everyone is causing a lot of frustration. Here are some of the problems I've encountered: Interface names that were easily recognized as abbreviations for their device type have been replaced by cryptic names that have no obvious meaning whatsoever. It's easy to guess that eth0 is short for ethernet #0. What the heck is p4p1 supposed to mean? How is a human supposed to guess that the first p stands for "PCI slot", that the second p stands for "port number", and that the whole mysterious string represents an ethernet interface? This new naming convention is inferior to the old one in at least one significant respect: it makes things more difficult to understand. One of the more useful examples of consistency that unix-like systems have enjoyed for decades has been thrown out: the extremely well-known ethernet device names. This creates yet another hurtle for users and admins when switching between different operating systems or trying to apply general-purpose unix knowledge. A lot of documentation has been broken. I have no idea how many manuals, forum posts, bug reports, printed instructions, email messages, personal notes, books, and other forms of documentation in the world refer to a unix ethernet device as eth0, but I'll bet the number is huge. All that valuable guidance has just been rendered misleading or even useless to anyone who doesn't keep up with the latest distribution-specific device naming experiments; in other words: the people who need it most. Well-established workflows have been broken. The change trips up users and admins who have for years been getting tasks done quickly with commands that they could recall and execute without a second thought. They are suddenly finding that their workflows no longer work. This interrupts tasks that should have been quick and easy, forcing people figure out why known-good procedures are broken, think about how to modify their memorized commands to work on the affected systems, and train their fingers to type those new commands as quickly as they did the old ones. Beyond being irritating, it can eat up a bunch of time that some of us don't have to spare. Working systems have been broken. Tools and automation scripts, especially those developed for site-specific use, often make the difference between a computer that does real work and a useless generic OS installation. Sometimes they even make the difference between a malfunctioning headless box that can be fixed over the network and an expensive brick. It is quite common for such software to make some minimal assumptions about its runtime environment, like assuming that the name of the only network device that has ever been or will ever be present will not suddenly change after being stable for months or years. There are also applications (e.g. Matlab) and configuration files (e.g. smb.conf, dhclient.conf, isc-dhcp-server) that might depend on references to eth0. Renaming a critical and ubiquitous device like this is so very likely to cause problems that it should never, ever be done in an upgrade without the admin's explicit consent. Sufficient warning of the change was not given. On one of my machines, eth0 was renamed to p4p1 when I upgraded to Ubuntu 14.04 (trusty), yet I don't see any mention of it in the Trusty release notes, nor in any of the notes for releases of the previous several years. Is it buried in fine print someplace that I missed? Having to figure out for myself what changed, why, and how to revert it (in multiple ways on each machine) was a significant waste of my time. Multiply that by all the other people who were affected similarly, and I'll bet we'd get an embarrassing number of needlessly wasted person-months that could have been saved with a simple announcement and link to documentation. In short, the way this feature was forced on the world was an irresponsible blunder. It doesn't matter that the change was meant to
