[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
I can also confirm the same bug is present in Ubuntu 19.10 with package network-manager 1.20.4-2ubuntu2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1787374] [NEW] resolvconf fails to update DNS server after resuming laptop from suspend
Public bug reported: This bug has been present since I have updated to Ubuntu 17.10 and it is still present in Ubuntu 18.04. It seems pretty simple to understand and a solution should be straightforward, but I lack understanding for what application is failing to update the right configuration file. When I go to work and I start my laptop, my /run/resolvconf/interface/systemd-resolved is filled with this: nameserver 127.0.0.53 search broadinstitute.org plc.hootoo.com When I come back home, DNS resolution does not work or works very slowly, most likely because my work DNS server broadinstitute.org is not reachable anymore, or maybe it is reachable but it is excruciatingly slow at responding. The solution is for me to edit /run/resolvconf/interface/systemd-resolved and remove the work DNS server: nameserver 127.0.0.53 search plc.hootoo.com And then update /etc/resolv.conf with the following command: $ sudo /etc/init.d/resolvconf restart Alternatively, another solution is to reboot the laptop. Then everything works fine. This is clearly a bug, but I am not sure whether it is a NetworkManager's bug, a resolvconf's bug, or a systemd bug. Please help! :-) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu) -- 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/1787374 Title: resolvconf fails to update DNS server after resuming laptop from suspend Status in resolvconf package in Ubuntu: New Bug description: This bug has been present since I have updated to Ubuntu 17.10 and it is still present in Ubuntu 18.04. It seems pretty simple to understand and a solution should be straightforward, but I lack understanding for what application is failing to update the right configuration file. When I go to work and I start my laptop, my /run/resolvconf/interface/systemd-resolved is filled with this: nameserver 127.0.0.53 search broadinstitute.org plc.hootoo.com When I come back home, DNS resolution does not work or works very slowly, most likely because my work DNS server broadinstitute.org is not reachable anymore, or maybe it is reachable but it is excruciatingly slow at responding. The solution is for me to edit /run/resolvconf/interface/systemd-resolved and remove the work DNS server: nameserver 127.0.0.53 search plc.hootoo.com And then update /etc/resolv.conf with the following command: $ sudo /etc/init.d/resolvconf restart Alternatively, another solution is to reboot the laptop. Then everything works fine. This is clearly a bug, but I am not sure whether it is a NetworkManager's bug, a resolvconf's bug, or a systemd bug. Please help! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1787374/+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 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
I have had the same exact problem since I have upgraded to 17.10. In my case it does not even involve the VPN. When I come back from work, if I had suspended the laptop without restarting it, then I cannot connect to the computers from work. If I restart resolvconf with: $ sudo /etc/init.d/resolvconf restart The problem persists. If I edit the file /run/resolvconf/interface/systemd-resolved with $ sudo emacs -nw /run/resolvconf/interface/systemd-resolved ... remove the work computer name in the line starting with search ... $ sudo /etc/init.d/resolvconf restart Then it works fine. I hope this bug is well understood and the fix is on its way. It seems like a bit of a corner case, but it is indeed a serious bug. -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Touch-packages] [Bug 1426490] Re: cups 2.0.2-1 100% cpu usage
Same problem here. This is the content of my /var/log/cups/error_log file: W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... W [26/May/2015:14:10:58 -0400] Max clients reached, holding new connections... E [26/May/2015:14:14:54 -0400] [Client 310] Local authentication certificate not found. W [26/May/2015:14:14:54 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:14:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... W [26/May/2015:14:17:21 -0400] Max clients reached, holding new connections... E [26/May/2015:14:19:55 -0400] [Client 599] Local authentication certificate not found. W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:55 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:56 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... W [26/May/2015:14:19:57 -0400] Max clients reached, holding new connections... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1426490 Title: cups 2.0.2-1 100% cpu usage Status in cups package in Ubuntu: Incomplete Bug description: upgraded from xubuntu 14.10 to 15.04 and now it uses cups 2.x after every print cupsd starts using 100% cpu and don't close. have to kill it every time with sudo pkill cupsd printing still works fine Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 cups: Installiert: 2.0.2-1ubuntu3 Installationskandidat: 2.0.2-1ubuntu3 Versionstabelle: *** 2.0.2-1ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1426490/+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 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
@jderose, @tagrain, as mdeslaur mentioned in post #12, the metric is correctly set for the gateway route, but it is incorrectly set for the local area network route. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Fix Committed Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) 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/network-manager/+bug/1436330/+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 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues
After installing Ubuntu 15.04 my routing table looked like: $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.10.100.3 0.0.0.0 UG1024 00 eth0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlan0 After installing network-manager_0.9.10.0-4ubuntu16_amd64.deb and libnm- util2_0.9.10.0-4ubuntu16_amd64.deb my routing table looked like: $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.10.100.3 0.0.0.0 UG10000 eth0 0.0.0.0 10.10.100.3 0.0.0.0 UG40000 wlan0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 wlan0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlan0 However, my DNS servers are: $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.10.100.11 nameserver 10.10.100.12 So, if I understand correctly, even with version 0.9.10.0-4ubuntu16 of the network manager, there is still a metric issue which could cause the system to attempt to connect to my DNS servers through the wireless connection even when perfectly connected through the ethernet cable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436330 Title: Network Manager doesn't set metric for local networks any more, causing connection issues Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Vivid: Fix Committed Bug description: [Impact] NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss. Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric. [Test Case] 1- Connect to a wireless network. 2- Connect to the same network over Ethernet both connections should come up on the same subnet. 3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'. [Regression Potential] Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to. --- With Vivid, having two connections to the same network subnet is unstable due to missing metrics for local networks. Example: Being connected to 192.168.1.0/24 via both wired and wireless will cause connectivity issues as sent packets hop between the two interfaces. It used to be that this wasn't an issue. I would go between work and home and plug in and my machine would automatically connect to wireless and it would use the lower metric ethernet interface for all communications, while the wlan interface would remain connected but unused. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 25 09:17:27 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-25 (58 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago) 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/network-manager/+bug/1436330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1423546] Re: [vivid] unable to manage vpn after vpn goes down
I think I might have the same issue. This is the route -n output of my computer: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.10.100.3 0.0.0.0 UG1024 00 eth0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 eth0 This is the route -n output of my computer after connecting to the VPN: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 1024 00 vpn0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 69.173.118.00.0.0.0 255.255.254.0 U 0 00 vpn0 69.173.127.310.10.100.3 255.255.255.255 UGH 1 00 eth0 69.173.127.30.0.0.0 255.255.255.255 UH1024 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 eth0 This is the route -n output of my computer after disconnecting from the VPN: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.10.100.3 0.0.0.0 UG1024 00 eth0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 69.173.127.30.0.0.0 255.255.255.255 UH1024 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 eth0 As you can see, after disconnection from the VPN, this extra line remains: 69.173.127.30.0.0.0 255.255.255.255 UH1024 00 eth0 Which seems to be what is causing the problem, as it makes it impossible to reach IP address 69.173.127.3 which is exactly the IP address of the VPN server. By manually removing this extra line with the following command: sudo route delete 69.173.127.3 The routing table reverses to its original configuration: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.10.100.3 0.0.0.0 UG1024 00 eth0 10.10.96.0 0.0.0.0 255.255.248.0 U 0 00 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 eth0 And I am now able again to initiate the VPN connection. This issue was not present before upgrading to vivid vervet, so I am not sure what the original behavior in utopic unicorn was. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1423546 Title: [vivid] unable to manage vpn after vpn goes down Status in network-manager package in Ubuntu: Confirmed Bug description: Just upgraded from utopic to vivid and this is a regression How to reproduce: 1. Use Wi-Fi that requires (pptp) VPN 2. Wait until VPN goes down What happens: I cannot manage VPN, that is re-enable the downed VPN. Disconnecting the Wi-Fi does not help either, it seems the VPN is in a 'stuck' state What should have happened: Like before, the UI should allow me to re-enable the VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1423546/+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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
With Ubuntu 15.04 and the newest 4.1.0-040100rc1-generic kernel, the bug is completely fixed. ** Changed in: xorg (Ubuntu) Status: Invalid = Fix Released -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in xorg package in Ubuntu: Fix Released Bug description: Since upgrade to 14.04, using my Dell BIZLINK DisplayPort to DVI Dual Link Adapter the external display on DP1 is extremely unstable. I get constant [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up messages over dmesg. I used to get those with 13.10, but there was no stability issue. Once the laptop (Lenovo X220) is connected to the monitor (resolution is 2560x1600), if I run any program like xrandr or unity-control-center, the system immediately reverts from the external display to the laptop display, and often crashes becoming unresponsive. Every time I run xrandr or unity-control-center, it triggers 20 [drm:intel_dp_i2c_aux_ch] *ERROR* too many retries, giving up messages in dmesg and if I am using the external monitor it further triggers a reproducible crash. It is possible that this might be related to the DVI-DP adapter I am using. Due to an unresolved bug, the correct EDID for the monitor is not recognized, and I have to manually add that after each boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 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: genovese 2538 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 29 10:00:31 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-21 (463 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: LENOVO 42872WU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=1f880233-e827-4c00-b11a-2c7a4eb76497 ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-04-18 (10 days ago) dmi.bios.date: 08/31/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET64WW (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 42872WU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET64WW(1.34):bd08/31/2012:svnLENOVO:pn42872WU:pvrThinkPadX220:rvnLENOVO:rn42872WU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42872WU dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213/+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
