[Desktop-packages] [Bug 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
We're looking forward to getting this implemented, we have many workstations using this driver and we'd like to use the newer kernels. Thank you for your good work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1724871 Title: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-304 source package in Xenial: Incomplete Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1724871/+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 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
This also affects me on Ubuntu 16.04 fresh install I've set this in /etc/default/keyboard: XKBMODEL="pc105" XKBLAYOUT="us" XKBVARIANT="altgr-intl" XKBOPTIONS="" BACKSPACE="guess" And the keyboard layout is most definitively not us/altgr-intl I had this problem also on another laptop with Trusty Tahr 14.04 a few years ago and it caused me to move to Debian. Now i tried Ubuntu again, and the problem is still here (but not on debian). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Fix Released Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 1297849] Re: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files
Me and the users in my company are still seeing this bug on 14.04 We really appreciate the effort to fix this, and we will start testing the proposed package and let you know about the results. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1297849 Title: [SRU] Virtual private network connection fails after distribution upgrade due to outdated Network Manager configuration files Status in One Hundred Papercuts: Triaged Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Triaged Status in network-manager-openvpn package in Ubuntu: Triaged Status in network-manager-vpnc package in Ubuntu: Triaged Status in network-manager-applet source package in Trusty: Fix Committed Status in network-manager-openconnect source package in Trusty: New Status in network-manager-openvpn source package in Trusty: New Status in network-manager-vpnc source package in Trusty: New Bug description: [Impact] * People who are using VPN services (of any kind, using vpnc, openvpn, pptp, etc. [Test Case] HOW TO REPRODUCE 1. Upgrade to a newer Ubuntu release. 2. Using the Network Manager application, try to start a virtual private network connection. EXPECTED BEHAVIOUR - The connection to complete successfully. ACTUAL BEHAVIOUR - The current configuration files, created by a previous network manager installation in the gconf user home folder, makes the application to misbehave; returning a log like this: [Regression Potential] May cause Gnome-Shell detection to give up prematurely. [PPA with a Possible Solution] Please see the https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849/comments/107 on information how to try the PPA with a solution to the bug that has the patch https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849/+attachment/4253965/+files/network-manager-applet-1297849.patch applied. [Additional information] Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Starting VPN service 'vpnc'... Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' started (org.freedesktop.NetworkManager.vpnc), PID 24419 Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' appeared; activating connections Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: [1395840211.74057] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Policy set 'blizzard' (wlan0) as default for IPv4 routing and DNS. Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: [1395840211.74406] [nm-system.c:1266] nm_system_replace_default_ip6_route(): (wlan0): failed to set IPv6 default route: -7 Mar 26 13:23:31 hprem-rmbp NetworkManager[855]: Policy set 'blizzard' (wlan0) as default for IPv6 routing and DNS. Mar 26 13:23:36 hprem-rmbp NetworkManager[855]: VPN service 'vpnc' disappeared ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-vpnc 0.9.8.6-1ubuntu2 Uname: Linux 3.13.0-031300-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 26 13:26:42 2014 InstallationDate: Installed on 2014-01-17 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140115) SourcePackage: network-manager-vpnc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1297849/+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 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)
Still does not work on 14.04. My solution is to disable socket in audio.conf, then I can connect, but not with the default GUI thing. Using the bluetooth icon in the titlebar, I connect, and it shows up as connected. However, using any other tool (blueman-manager, pactl list, pavucontrol) it is obvious it fails to connect, a sink is not established, and the module is not loaded. Sometimes it successfully connects using headset service only, but fails on the A2DP, and still shows up as successful. So it seems it tries to connect, but does not perform any check if it actually succeded or not. This is a problem in Unity i think. Using blueman-manager, I can connect, but get this error from bluetoothd: bluetoothd[14256]: Unable to select SEP This is mentioned here and is a separate bug: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1199059 The fix for that seems to be to manually load module-bluetooth-discover, and things work. Still, it would be nice to get some checks in the default applet if it actually connects or not. -- 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/1181106 Title: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty) Status in Bluez Utilities: New Status in “pulseaudio” package in Ubuntu: Confirmed Status in “pulseaudio” package in Debian: Fix Released Bug description: I upgraded to 13.04 recently and my A2DP profile, which had been working great under 12.10 is suddenly gone. Neither my blueman applet nor the built-in bluetooth manager applet can connect my external bluetooth speaker to the A2DP profile. They can connect to the bluetooth device itself just fine. Steps I'm using: * using blueman, I can connect to the external bluetooth speaker and view the device in the devices listing * I can connect the device to the Audio sink and I get a message saying it is now connected and will "show in the PulseAudio mixer" * After connecting the external speaker to the audio sink, I can also see the device in the "Play sound through" listing in the Sound system control panel, but the icon has a circle with a line through it. * but if I right-click the device and choose "Audio Profile" from the context menu and try to select "High Fidelity Playback (A2DP)" as the new profile, I get an error message stating "failed to change profile to a2dp" I've already added "Enable=Socket" in /etc/bluetooth/audio.conf, without that I can't pair my headset. Now I can pair it, but I can't activate the A2DP profile. When I try to activate it, I see this message in my syslog : pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no transport I tried the kernel 3.9.0 because of a sound problem with my soundcard, this kernel fixed my soundcard problem, but A2DP still doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1181106/+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
