[Desktop-packages] [Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
** Project changed: dell-sputnik => unity-control-center -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues Status in OEM Priority Project: Confirmed Status in Unity Control Center: New Status in unity-control-center package in Ubuntu: Confirmed Bug description: This issue is related to sound not working properly on Ubuntu when switching between an external display using HDMI with 4K resolution and the standard laptop display. Issue 1 - Sound only works on laptop when plugged into 4k HDMI display Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display When you plug in a 4k Display that supports sound to the Dell XPS 15 2016 model the sound only works on the laptop. Only when you go to Sound Settings and manually select the HDMI output for sound does the sound start to work on the display itself instead of the laptop. When you unplug the HDMI 4k display the sound doesn't work on the laptop. When you go to the Sound Settings dialog it only shows one output that is selected - if you select the same output thats already selected the sound starts to work again on the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1649763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
@frail-knight, the right people are already subscribed to this bug. Please *stop* changing bugs to affect dell-sputnik ** Changed in: dell-sputnik Status: New => Incomplete ** Changed in: dell-sputnik Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Invalid Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688317] Re: PCI/internal sound card not detected
You're running a non-OEM version of Ubuntu 16.04.1, which is too old to fully support this platform. Canonical maintains driver backports for this platform only for factory-installed Ubuntu 16.04, and that includes backport DKMS packages. Either wait until this is backported to a later Ubuntu 16.04 point release, use a later version of Ubuntu or purchase with Ubuntu pre-installed instead of Windows. ** Changed in: dell-sputnik Status: New => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1688317 Title: PCI/internal sound card not detected Status in Dell Sputnik: Invalid Status in alsa-driver package in Ubuntu: Invalid Bug description: No sound card detected at all, no sound for laptop/bluetooth headphones ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu May 4 10:41:20 2017 InstallationDate: Installed on 2017-01-25 (98 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1688317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack
Have you checked in the system settings GUI whether the headphone jack shows as an output option? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1650259 Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack Status in Dell Sputnik: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: The problem is that there is no sound at the jack for the headphones. Internal speaker are silenced when inserted a headphone jack but there is no sound output. Tested a live MS windows and sound worked! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 15 12:41:55 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-25 (173 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-09-07 (98 days ago) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0H67KH dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1650259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649763] Re: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues
It sounds to me like issue 1 should be opened as a separate bug report as a feature request. I think it makes sense to at least prompt the user whether they want to switch to external audio. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1649763 Title: Dell XPS 15 2016 with Ubuntu 16 Sound HDMI issues Status in unity-control-center package in Ubuntu: Confirmed Bug description: This issue is related to sound not working properly on Ubuntu when switching between an external display using HDMI with 4K resolution and the standard laptop display. Issue 1 - Sound only works on laptop when plugged into 4k HDMI display Issue 2 - Sound doesn't work when plugged removed from 4k HDMI display When you plug in a 4k Display that supports sound to the Dell XPS 15 2016 model the sound only works on the laptop. Only when you go to Sound Settings and manually select the HDMI output for sound does the sound start to work on the display itself instead of the laptop. When you unplug the HDMI 4k display the sound doesn't work on the laptop. When you go to the Sound Settings dialog it only shows one output that is selected - if you select the same output thats already selected the sound starts to work again on the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1649763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551516 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551518 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550504] Re: lightdm unresponsive after suspend
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551514 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
Note that trying to turn on and off the wireless card using the wireless hotkey did not help. As can be seen from the logs, NM reports wifi's killswitch status change but still does not see any APs or try reconnecting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate
The failure was seen with WPA2 Personal with an Aruba access point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
This occurred about every five to ten reboots. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
The failure was seen with WPA2 Personal with an Aruba access point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1550490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550504] Re: lightdm unresponsive after suspend
I can't reproduce on a system with the FHD panel. It may be restricted to the UHD model. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550538] [NEW] periodically after suspend/resume wpasupplicant fails to authenticate
Public bug reported: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550504] [NEW] lightdm unresponsive after suspend
Public bug reported: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1550490] [NEW] network-manager unresponsive after suspend
Public bug reported: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8
[Desktop-packages] [Bug 1510339] Re: 5GHz network is not available after suspend by closing lid
** Also affects: dell-sputnik Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1510339 Title: 5GHz network is not available after suspend by closing lid Status in Dell Sputnik: New Status in network-manager package in Ubuntu: New Bug description: Model: Dell XPS 13 - 9343 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) Action: close lid of laptop to suspend, open lid to resume Expected behavior: Wireless would resume with access to 2.4Ghz and 5Ghz networks Actual Behavior: Wireless resumes, but 5Ghz networks are not detected ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.3 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 21:08:17 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-25 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 6c91668c-4496-4a76-b636-2aba7ee0fdac 802-3-ethernet 1445907849 Mon 26 Oct 2015 09:04:09 PM EDT yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/3 Nexus 4 Network 4c6152f2-6c3a-425e-a91d-13faad5ed602 bluetooth 0 neverno no /org/freedesktop/NetworkManager/Settings/3 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 6c91668c-4496-4a76-b636-2aba7ee0fdac /org/freedesktop/NetworkManager/ActiveConnection/3 98:D6:F7:2E:39:53 btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- -- -- wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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:
[Desktop-packages] [Bug 1421408] Re: login screen scaling issue M3800 (factory image plus apt-get upgrade)
Thanks Robert. See the attached log. This seems to be relevant from there: [+0.45s] DEBUG: main-window.vala:185: Screen is 3840x2160 pixels [+0.45s] DEBUG: main-window.vala:193: Monitor 0 is 3840x2160 pixels at 0,0 [+0.45s] DEBUG: main-window.vala:185: Screen is 1920x1080 pixels [+0.45s] DEBUG: main-window.vala:193: Monitor 0 is 1920x1080 pixels at 0,0 [+0.47s] DEBUG: menubar.vala:538: Adding indicator object 0x1097450 at position 2 ** Attachment added: x-0-greeter.log https://bugs.launchpad.net/dell-sputnik/+bug/1421408/+attachment/4318355/+files/x-0-greeter.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1421408 Title: login screen scaling issue M3800 (factory image plus apt-get upgrade) Status in Dell Sputnik: New Status in unity-greeter package in Ubuntu: New Bug description: I just imaged a Dell Precision M3800 Developer Edition with UHD (4K) display. After installation, I apt-get update'd and apt-get upgrade'd and now see an issue with the login screen. (See attached picture.) No customization was done other than doing a standard upgrade (none of the used repositories were changed). To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1421408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1010349] Re: Evolution address book inaccessible without killing one time e-addressbook-factory
I see the same issue when using Evolution 3.2.3 on Ubuntu 12.04 with the MAPI connector to an Exchange server. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1010349 Title: Evolution address book inaccessible without killing one time e -addressbook-factory Status in “evolution-data-server” package in Ubuntu: Confirmed Bug description: After a fresh boot of my system, Evolution is not able to access my work address book on LDAP and my personnal address book on Google. With Google address book I get the error Cannot open book: Source already loaded! After shutting down Evolution and killing by hand : /usr/lib/evolution/e-addressbook-factory. I relaunch Evolution and everything go right. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution-data-server 3.2.3-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jun 8 09:07:18 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1010349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962587] [NEW] When using ifnet plugin and biosdevname is enabled, NetworkManager may treat wired interfaces as wireless interfaces
Public bug reported:
From the source for network-manager-0.9.3.995+git201203152001.04b2a74, I
see that NM would treat any NIC names resulting from having biosdevname
enabled (of the form em* and p*p*) as wireless interfaces. This is
apparent from src/settings/plugins/ifnet/net_parser.c and
src/settings/plugins/ifnet/connection_parser.c.
init_block_by_line in src/settings/plugins/ifnet/net_parser.c:
if ((conn = get_connection_config (pos)) == NULL) {
if (g_ascii_strncasecmp (pos, eth, 3) == 0
strlen (pos) == 4)
/* wired connection */
conn = add_new_connection_config (wired, pos);
else if (g_ascii_strncasecmp (pos, ppp, 3) == 0
strlen (pos) == 4)
/* pppoe connection */
conn = add_new_connection_config (ppp, pos);
else if (ignore_connection_name (pos)) {
/* ignored connection */
conn = add_new_connection_config (ignore, pos);
} else
/* wireless connection */
conn = add_new_connection_config (wireless, pos);
}
get_wired_name in src/settings/plugins/ifnet/connection_parser.c:
gchar *conn_name = g_strdup_printf (eth%d, i);
It is not clear to me if any wireless interfaces would be named of the
forms em* or p*p*, so I do not know if it would be sufficient to check
the name of an interface to determine what type it is. However, it at
least would usually be incorrect to label an interface called, say, em1
as a wireless interface.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/962587
Title:
When using ifnet plugin and biosdevname is enabled, NetworkManager may
treat wired interfaces as wireless interfaces
Status in “network-manager” package in Ubuntu:
New
Bug description:
From the source for network-manager-0.9.3.995+git201203152001.04b2a74,
I see that NM would treat any NIC names resulting from having
biosdevname enabled (of the form em* and p*p*) as wireless interfaces.
This is apparent from src/settings/plugins/ifnet/net_parser.c and
src/settings/plugins/ifnet/connection_parser.c.
init_block_by_line in src/settings/plugins/ifnet/net_parser.c:
if ((conn = get_connection_config (pos)) == NULL) {
if (g_ascii_strncasecmp (pos, eth, 3) == 0
strlen (pos) == 4)
/* wired connection */
conn = add_new_connection_config (wired, pos);
else if (g_ascii_strncasecmp (pos, ppp, 3) == 0
strlen (pos) == 4)
/* pppoe connection */
conn = add_new_connection_config (ppp, pos);
else if (ignore_connection_name (pos)) {
/* ignored connection */
conn = add_new_connection_config (ignore, pos);
} else
/* wireless connection */
conn = add_new_connection_config (wireless, pos);
}
get_wired_name in src/settings/plugins/ifnet/connection_parser.c:
gchar *conn_name = g_strdup_printf (eth%d, i);
It is not clear to me if any wireless interfaces would be named of the
forms em* or p*p*, so I do not know if it would be sufficient to check
the name of an interface to determine what type it is. However, it at
least would usually be incorrect to label an interface called, say,
em1 as a wireless interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/962587/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962587] Re: When using ifnet plugin and biosdevname is enabled, NetworkManager may treat wired interfaces as wireless interfaces
I forgot to add that information on biosdevname can be found here:
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.
It is not enabled by default on Ubuntu but has been available as an
option since 11.04. It is also enabled by default in the latest Fedora
and RHEL releases and an option in SLES.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/962587
Title:
When using ifnet plugin and biosdevname is enabled, NetworkManager may
treat wired interfaces as wireless interfaces
Status in “network-manager” package in Ubuntu:
New
Bug description:
From the source for network-manager-0.9.3.995+git201203152001.04b2a74,
I see that NM would treat any NIC names resulting from having
biosdevname enabled (of the form em* and p*p*) as wireless interfaces.
This is apparent from src/settings/plugins/ifnet/net_parser.c and
src/settings/plugins/ifnet/connection_parser.c.
init_block_by_line in src/settings/plugins/ifnet/net_parser.c:
if ((conn = get_connection_config (pos)) == NULL) {
if (g_ascii_strncasecmp (pos, eth, 3) == 0
strlen (pos) == 4)
/* wired connection */
conn = add_new_connection_config (wired, pos);
else if (g_ascii_strncasecmp (pos, ppp, 3) == 0
strlen (pos) == 4)
/* pppoe connection */
conn = add_new_connection_config (ppp, pos);
else if (ignore_connection_name (pos)) {
/* ignored connection */
conn = add_new_connection_config (ignore, pos);
} else
/* wireless connection */
conn = add_new_connection_config (wireless, pos);
}
get_wired_name in src/settings/plugins/ifnet/connection_parser.c:
gchar *conn_name = g_strdup_printf (eth%d, i);
It is not clear to me if any wireless interfaces would be named of the
forms em* or p*p*, so I do not know if it would be sufficient to check
the name of an interface to determine what type it is. However, it at
least would usually be incorrect to label an interface called, say,
em1 as a wireless interface.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/962587/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 954661] Re: backlight brightness not adjustable by default on Dell XPS 13
Thank you. I wasn't entirely sure what package to report the bug against. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/954661 Title: backlight brightness not adjustable by default on Dell XPS 13 Status in “gnome-power-manager” package in Ubuntu: New Bug description: The backlight brightness is not changeable by default on a Dell XPS 13 running Precise beta 1 (or later). If I run the following command as root, I can adjust the brightness: /bin/echo 0 /sys/class/baclight/intel_backlight/brightness However, I must do this whenever I turn on the computer or resume it from suspend. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Tue Mar 13 20:56:36 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:052e] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: Dell Inc. Dell System XPS L321X ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=6a0a6c9c-fb29-446a-8806-e431d38c95e8 ro quiet splash i915.i915_enable_fbc=1 i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 085X6F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd01/30/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L321X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/954661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
