[Desktop-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor.
I believe I have the same issue. Dell XPS 13 9360 laptop connected to a Dell U3011 monitor using a CableMatters USB-C to Displayport adapter. When I plug my laptop the GNOME shell is almost completely unresponsive. I can use the active window but I cannot switch windows. The only reproducible way I have found to get out of it, other than to reboot, is to unplug the USB-C adapter, logout of the session, re-plug the USB-C adapter and login again. This behavior was not present with Ubuntu 21.10 and it started after updating to Ubuntu 22.04. I use an X11 session type: $ echo $XDG_SESSION_TYPE x11 Using journalctl, output attached, there are many logs from the gnome-shell binary, such as this: gnome-shell[###]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed gnome-shell[###]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed ** Attachment added: "journalctl -b0 > journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970495/+attachment/5585970/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor. Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970495/+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 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 Desktop 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/~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 1796265] Re: Ubuntu Dock is missing after unlocking screen
I have what looks like the same issue. When I lock my screen with "Super+L" the first time it goes into a flickering screen and the second time it locks the session. Then I login again, one of my shell extensions does not work anymore (PutWindows), and to make it work again I have to uninstall and install it again. I also have the issue that the Ubuntu dock does not auto-hide anymore unless I restart the session. I am not sure whether these problems are all connected. I use Xorg on Ubuntu 18.10. All these problems arose after updating from Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796265 Title: Ubuntu Dock is missing after unlocking screen Status in gnome-shell package in Ubuntu: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: After locking the screen, unlocking it again does not return me to a properly working gnome-shell. I can see the desktop background and the top panel (which is responsive). However I cannot access the activities overview, and the Ubuntu dock is missing. One time I noticed that the search field from the activities overview was visible, and it was possible to search for an application. The search did return results, and it was possible to start applications, but they did not show up on the screen. In some cases I could run gnome-shell -r, but this would end the whole session and return me to the login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 12:44:13 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-03 (458 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796265/+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 1725081] Re: Clipboard support broken in Ubuntu 17.10
Not sure whether this is the same issue. Since I moved to Ubuntu 17.10 I cannot copy and paste from gedit anymore. If I open gedit, write something, and then try to paste it in Firefox it does not work. When I try to paste, I get the following line in the stderr of gedit: (gedit:#): Gdk-WARNING **: Error writing selection data: Error writing to file descriptor: Broken pipe Copying and paste from and among other applications works just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1725081 Title: Clipboard support broken in Ubuntu 17.10 Status in mono package in Ubuntu: Confirmed Bug description: Mono apps can no longer modify system clipboard. For example, KeePass 2.x (https://keepass.info/). It was working perfect in Ubuntu 17.04. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mono-complete 4.6.2.7+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 04:13:09 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: mono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1725081/+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 1584740] Re: Libreoffice impress hanging and high cpu on slide operations
Same problem with LibreOffice Impress version 5.3.1.2. Thank you @mcnichol for figuring out that removing libreoffice-gtk3 solves the issue. Does anybody know whether the issue persists with Ubuntu 17.10? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1584740 Title: Libreoffice impress hanging and high cpu on slide operations Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: - Create a presentation in libreoffice impress, 30-100 slides with or without images - Add, copy or delete slides - On those operations LO Impress hangs a lot; sometimes 5 mins or more - Opening and saving works quick Tested on 2 different laptops, both had the same issue. Both did have Intel Graphics, but different ones. It works fine on the same laptop with LO 5.1 on Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 23 12:55:08 2016 InstallationDate: Installed on 2016-04-29 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1584740/+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 1685292] [NEW] Zesty: network-manager-applet VPN 17.04 Cisco AnyConnect fails with Duo Authentication
Public bug reported: Since I have updated to Ubuntu Zesty 17.04 I have had problems with connecting through VPN. I did not understand at first what was causing the issue. Now I think I have figured it out and explaining the issue might help other people with the same problem understanding what is going on. I login to my work VPN network using Cisco AnyConnect (available through package openconnect) and Duo Authentication. Because of Duo Authentication, there are always two passwords to fill in, one is my regular password and the other one is a 6 numeric password generated every few seconds that I need to ascertain from my smartphone. If I click on the option dialogue box "Save passwords", I think the applet manager will save both passwords and the next time I try to connect through VPN it will use both passwords (one of which will be expired) multiple times until my work account will be locked out. By the time the dialogue appears allowing me to include the correct passwords, it seems to be already too late. The login will fail no matter what because now I have been locked out and I could understand what was going on because there was no way for me to know that at that point I had been irrevocably locked out of the ability to VPN. I do not know if this is a network-manager issue, a network-manager- applet issue, or an openconnect issue, but this is definitely a completely new annoying behaviour resulting from the update to Ubuntu Zesty 17.04. Also, of notice buy maybe unrelated, if I select in the network-manager- applet "VPN Connections", the option "Configure VPN..." is greyed out and cannot be selected anymore. This is also a new behaviour of Ubuntu Zesty 17.04. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- 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/1685292 Title: Zesty: network-manager-applet VPN 17.04 Cisco AnyConnect fails with Duo Authentication Status in network-manager-applet package in Ubuntu: New Bug description: Since I have updated to Ubuntu Zesty 17.04 I have had problems with connecting through VPN. I did not understand at first what was causing the issue. Now I think I have figured it out and explaining the issue might help other people with the same problem understanding what is going on. I login to my work VPN network using Cisco AnyConnect (available through package openconnect) and Duo Authentication. Because of Duo Authentication, there are always two passwords to fill in, one is my regular password and the other one is a 6 numeric password generated every few seconds that I need to ascertain from my smartphone. If I click on the option dialogue box "Save passwords", I think the applet manager will save both passwords and the next time I try to connect through VPN it will use both passwords (one of which will be expired) multiple times until my work account will be locked out. By the time the dialogue appears allowing me to include the correct passwords, it seems to be already too late. The login will fail no matter what because now I have been locked out and I could understand what was going on because there was no way for me to know that at that point I had been irrevocably locked out of the ability to VPN. I do not know if this is a network-manager issue, a network-manager- applet issue, or an openconnect issue, but this is definitely a completely new annoying behaviour resulting from the update to Ubuntu Zesty 17.04. Also, of notice buy maybe unrelated, if I select in the network- manager-applet "VPN Connections", the option "Configure VPN..." is greyed out and cannot be selected anymore. This is also a new behaviour of Ubuntu Zesty 17.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1685292/+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 1677198] Re: OpenVPN not Working in 17.04
Okay, nevermind, in my case it was enough to delete the VPN connections and then add them again with the "Edit Connection..." option in the nm- applet menu (somehow "VPN Connections -> Configure VPN..." is grayed out and cannot be called). Once created again, the VPN connection work just fine as they used to. Maybe mine is a completely different problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1677198 Title: OpenVPN not Working in 17.04 Status in NetworkManager: New Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: I can definitely confirm that Network Manager's OpenVPN is not working yet in Ubuntu 17.04. I set up my configuration via import: http://neartalk.com/ss/2017-03-29_001_633x332.png On all earlier versions of Ubuntu, after importing the configuration, I'm able to connect to the VPN. However, in 17.04, connection attempts always give this error immediately: "The VPN Connection disconnected because the VPN Service has stopped" Clearly the VPN Service has NOT stopped. I've confirmed that this error is false by taking the exact same import-file and I imported it into an Ubuntu 16.04 computer and then the VPN connected without issue. Also, with this same import-file I've had no issues in Ubuntu 16.10. So I've thoroughly confirmed that there is no issue with the VPN service. The issue is with the client in Ubuntu 17.04. I cannot upgrade to 17.04 until this is fixed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 05:25:14 2017 InstallationDate: Installed on 2017-01-30 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1677198] Re: OpenVPN not Working in 17.04
I confirm the issue. I cannot login through VPN anymore since I updated from 16.10 to 17.04. I will also add to that it is impossible now to configure the VPN connections. The "Configure VPN..." option in the menu is grayed out and cannot be selected anymore from the NetworkManager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1677198 Title: OpenVPN not Working in 17.04 Status in NetworkManager: New Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: I can definitely confirm that Network Manager's OpenVPN is not working yet in Ubuntu 17.04. I set up my configuration via import: http://neartalk.com/ss/2017-03-29_001_633x332.png On all earlier versions of Ubuntu, after importing the configuration, I'm able to connect to the VPN. However, in 17.04, connection attempts always give this error immediately: "The VPN Connection disconnected because the VPN Service has stopped" Clearly the VPN Service has NOT stopped. I've confirmed that this error is false by taking the exact same import-file and I imported it into an Ubuntu 16.04 computer and then the VPN connected without issue. Also, with this same import-file I've had no issues in Ubuntu 16.10. So I've thoroughly confirmed that there is no issue with the VPN service. The issue is with the client in Ubuntu 17.04. I cannot upgrade to 17.04 until this is fixed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Mar 29 05:25:14 2017 InstallationDate: Installed on 2017-01-30 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1409032] Re: gvfsd-smb: very high CPU utilisation
I have noticed the same problem for the first time today at work (so no commercial USA ISP). I tried to strace the process to see what it does: sudo strace -T -p 13921 strace: Process 13921 attached restart_syscall(<... resuming interrupted poll ...> But I got no insight. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1409032 Title: gvfsd-smb: very high CPU utilisation Status in gvfs package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in samba package in Fedora: Unknown Bug description: Example: I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb (browsing within Gnome to find the share), gvfsd-smb uses up to 50% CPU which slows down the entire system when accessing the network share. Mounting using sudo ($ sudo mount -t smbfs -o guest,nounix,noperm //server/share /media/share) so that cifs is used uses around 8% CPU. The difference is dramatic! If I didn't have sudo access my machine would grind to a halt when trying to use the remote share. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gvfs-backends 1.12.1-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.8 Architecture: i386 Date: Fri Jan 9 14:32:20 2015 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 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 Desktop 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/~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 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 Desktop 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/~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 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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~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 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 Desktop 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/~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 1437091] Re: xrandr --delmode unable to remove incorrectly detected video resolution modes
With Ubuntu 15.04 and the newest 4.1.0-040100rc1-generic kernel, the system now correctly identifies the available resolutions. ** Changed in: x11-xserver-utils (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1437091 Title: xrandr --delmode unable to remove incorrectly detected video resolution modes Status in x11-xserver-utils package in Ubuntu: Fix Released Bug description: I own an HP LP3065 monitor (http://www.amazon.com/dp/B000KB6E3G/) with a BizLink displayport adapter (http://www.amazon.com/dp/B003XYBA72/). The command sudo get-edid -b 6 | parse-edid correctly identifies the available resolutions of the screen as 2560x1600 and 1280x800. However, the Ubuntu system incorrectly identifies instead the resolutions 1024x768, 800x600, 848x480, and 640x480 which all don't work with the monitor. While I have to add manually the correct resolutions with xrandr using the command xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync xrandr --addmode DP1 2560x1600, I occasionally have the system attempting to use the 1024x768 resolution leading to an empty black screen. One potential solution would be to remove the rogue resolutions so that they could not be automatically chosen. I tried the command xrandr --delmode DP1 1024x768 but this is to no avail with the following output: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 42 Current serial number in output stream: 43 My understanding is that the system thinks to know better than the user and disallows from removing native resolutions. However, it is clear that the system is not designed well enough to know what the correct native resolutions are. This is tremendously frustrating and ultimately it is combination of a bug in properly detecting the native resolutions (gone unfixed for the last five years) and a flawed design assuming detected resolutions would never need to be removed. I am at a loss with regard who to and where to file this bug. I would be tremendously grateful to anybody who could provide some directions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1437091/+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 1437091] [NEW] xrandr --delmode unable to remove incorrectly detected video resolution modes
Public bug reported: I own an HP LP3065 monitor (http://www.amazon.com/dp/B000KB6E3G/) with a BizLink displayport adapter (http://www.amazon.com/dp/B003XYBA72/). The command sudo get-edid -b 6 | parse-edid correctly identifies the available resolutions of the screen as 2560x1600 and 1280x800. However, the Ubuntu system incorrectly identifies instead the resolutions 1024x768, 800x600, 848x480, and 640x480 which all don't work with the monitor. While I have to add manually the correct resolutions with xrandr using the command xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync xrandr --addmode DP1 2560x1600, I occasionally have the system attempting to use the 1024x768 resolution leading to an empty black screen. One potential solution would be to remove the rogue resolutions so that they could not be automatically chosen. I tried the command xrandr --delmode DP1 1024x768 but this is to no avail with the following output: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 42 Current serial number in output stream: 43 My understanding is that the system thinks to know better than the user and disallows from removing native resolutions. However, it is clear that the system is not designed well enough to know what the correct native resolutions are. This is tremendously frustrating and ultimately it is combination of a bug in properly detecting the native resolutions (gone unfixed for the last five years) and a flawed design assuming detected resolutions would never need to be removed. I am at a loss with regard who to and where to file this bug. I would be tremendously grateful to anybody who could provide some directions. ** Affects: x11-xserver-utils (Ubuntu) Importance: Undecided Status: New ** Tags: xrandr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1437091 Title: xrandr --delmode unable to remove incorrectly detected video resolution modes Status in x11-xserver-utils package in Ubuntu: New Bug description: I own an HP LP3065 monitor (http://www.amazon.com/dp/B000KB6E3G/) with a BizLink displayport adapter (http://www.amazon.com/dp/B003XYBA72/). The command sudo get-edid -b 6 | parse-edid correctly identifies the available resolutions of the screen as 2560x1600 and 1280x800. However, the Ubuntu system incorrectly identifies instead the resolutions 1024x768, 800x600, 848x480, and 640x480 which all don't work with the monitor. While I have to add manually the correct resolutions with xrandr using the command xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync xrandr --addmode DP1 2560x1600, I occasionally have the system attempting to use the 1024x768 resolution leading to an empty black screen. One potential solution would be to remove the rogue resolutions so that they could not be automatically chosen. I tried the command xrandr --delmode DP1 1024x768 but this is to no avail with the following output: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 42 Current serial number in output stream: 43 My understanding is that the system thinks to know better than the user and disallows from removing native resolutions. However, it is clear that the system is not designed well enough to know what the correct native resolutions are. This is tremendously frustrating and ultimately it is combination of a bug in properly detecting the native resolutions (gone unfixed for the last five years) and a flawed design assuming detected resolutions would never need to be removed. I am at a loss with regard who to and where to file this bug. I would be tremendously grateful to anybody who could provide some directions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1437091/+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 1415536] [NEW] nm-applet does nothing when attempting to open a VPN connection
Public bug reported: I have a VPN connection configured. When I go on the network manager and click on VPN Connections - MyVPN, I would expect a dialog to open and allow me to connect to the VPN, but instead nothing happens. No error message is given. Just nothing at all. If I instead click on VPN Connections - Configure VPN..., the Network Connections dialog shows and I am able to edit the parameters of the VPN connection, but I am still not able to open the VPN dialog to initiate the connection. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- 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/1415536 Title: nm-applet does nothing when attempting to open a VPN connection Status in network-manager-applet package in Ubuntu: New Bug description: I have a VPN connection configured. When I go on the network manager and click on VPN Connections - MyVPN, I would expect a dialog to open and allow me to connect to the VPN, but instead nothing happens. No error message is given. Just nothing at all. If I instead click on VPN Connections - Configure VPN..., the Network Connections dialog shows and I am able to edit the parameters of the VPN connection, but I am still not able to open the VPN dialog to initiate the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1415536/+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 1415536] Re: nm-applet does nothing when attempting to open a VPN connection
Somehow, after changing the name of the VPN connection, the corresponding file in /etc/NetworkManager/system-connections/ got recreated and now I am unable to reproduce the bug as unfortunately I have not made a copy of the previous file. My best guess is that something went wrong with the previous configuration file and nm-applet was failing to open the correct dialog form. If I encounter the bug again, I will try to dig more deeply into the issue. -- 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/1415536 Title: nm-applet does nothing when attempting to open a VPN connection Status in network-manager-applet package in Ubuntu: New Bug description: I have a VPN connection configured. When I go on the network manager and click on VPN Connections - MyVPN, I would expect a dialog to open and allow me to connect to the VPN, but instead nothing happens. No error message is given. Just nothing at all. If I instead click on VPN Connections - Configure VPN..., the Network Connections dialog shows and I am able to edit the parameters of the VPN connection, but I am still not able to open the VPN dialog to initiate the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1415536/+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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
I guess it is way to late for me to figure that out now. However, you might try to run your computer from a USB pen, installing Ubuntu 14.04 with unetbootin and then see what behavior you get. That is what I did and made me realize that the problem likely relied in some settings. Maybe try removing the .compiz directory? If you figure out which one it is, let me know. Also, the behavior I have now is slightly different from the behavior I had with Ubuntu 13.10. Before I would add the resolution with xrandr and then change display again with xrandr. Now, instead, as soon as I add the resolution with xrandr the display changes automatically. I believe that Unity 14.04 responds automatically to some changes, while Unity 13.10 did not, and for some reasons this was leading to the crashes before. I have also noticed that my laptop used to run some dbus program after boot that would make the hard drive spin for several minutes before coming to a rest. Since I deleted all my configuration files, that is not happening anymore. Overall, the update from 13.10 to 14.04 was the worst Ubuntu update I have ever experienced (I also had experienced this: http://askubuntu.com/questions/449680/upgrading- from-13-10-to-14-04-broke-grub). -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in “xorg” package in Ubuntu: Confirmed 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/~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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
For some weird reasons, by deleting all configuration files in my home directory, the behavior reverted to what it was with Ubuntu 13.10. I cannot reproduce the crash anymore. I still need to add the correct resolution with xrandr as it is not detected correctly. Somehow there is a lurking bug in i915, but this must have been triggered by some weird settings I had in Unity. This is my best guess. -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in “xorg” package in Ubuntu: Confirmed 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/~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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
It is a Dell BIZLINK DisplayPort to DVI Dual Link Adapter (see here: http://www.amazon.com/dp/B003XYBA72/) -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in “xorg” package in Ubuntu: New Bug description: Since upgrade to 14.04, 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/~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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
The problem is possibly related to this bug: https://bugs.freedesktop.org/show_bug.cgi?id=56834 ** Bug watch added: freedesktop.org Bugzilla #56834 https://bugs.freedesktop.org/show_bug.cgi?id=56834 -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in “xorg” package in Ubuntu: New Bug description: Since upgrade to 14.04, 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/~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 1314213] Re: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04
I have some new information. Apparently, I tried a different external monitor with the displayport and the same 2560x1600 resolution and the laptop worked just fine. I can run xrandr or unity-control-center while the monitor is connected and there are no issues. The monitor that does not work correctly has a display port-dvi adapter and the resolution is not detected correctly. Because of that, I manually add the resolution each time the computer boots with the following command: xrandr --newmode 2560x1600 268.00 2560 2608 2640 2720 1600 1603 1609 1646 -hsync +vsync; xrandr --addmode DP1 2560x1600; xrandr --newmode 1280x800 71.00 1280 1328 1360 1440 800 803 809 823 -hsync +vsync; xrandr --addmode DP1 1280x800 And then I set the output to the monitor with the following command: xrandr --output LVDS1 --off --output VGA1 --off --output HDMI1 --off --output DP1 --mode 2560x1600 Therefore it is likely that this is a bug related to the display port-dvi adapter. -- 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/1314213 Title: [Lenovo ThinkPad X220] External DP1 monitor extremely unstable since upgrade to 14.04 Status in “xorg” package in Ubuntu: New Bug description: Since upgrade to 14.04, 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/~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 1263681] Re: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging
I wonder if this is the same as bug https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314213 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1263681 Title: 8086:0126 [Lenovo a ThinkPad X220] DisplayPort-2-DVI not hotplugging Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: WIth my Lenovo ThinkPad X220 I am unable to hotplug a DisplayPort-2-DVI cable, plug the DVI end into a monitor (Samsung SyncMaster 193p+), and plug the DP end into the ThinkPad, and it is detected within a reasonable time, with GNOME automatically extending my desktop. If I *unplug* the DP cable, the unplug is detected instantly. I once waited ~5 minutes without running xrandr, and it actually detected the monitor and reconfigured. WORKAROUND: If I run 'xrandr' in an xterm, the monitor is detected instantly and GNOME reconfigures the screen. WORKAROUND: if I open System Preferences - Display, it does an xrandr probe and instantly detects/reconfigures the screen. WORKAROUND: if I plug the DP cable before I open the laptop lid to wake it up from S3 sleep, the external monitor is detected. WORKAROUND: if I use a VGA cable instead of the DP - DVI one, hotplug is detected within seconds. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-extra-3.11.0-15-generic 3.11.0-15.23 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mg 2722 F pulseaudio Date: Mon Dec 23 14:33:12 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bf592a79-5f4e-486d-b69d-7525d492dcc6 InstallationDate: Installed on 2012-07-25 (515 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4291WJF MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=36079681-53fc-4ca2-80ac-98321c07e8d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-17 (66 days ago) WifiSyslog: dmi.bios.date: 05/31/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET47WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291WJF 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:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4291WJF:pvrThinkPadX220:rvnLENOVO:rn4291WJF:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4291WJF dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO --- ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2713 F pulseaudio CasperVersion: 1.336ubuntu1 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4291WJF MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 RelatedPackageVersions: linux-restricted-modules-3.13.0-1-generic N/A linux-backports-modules-3.13.0-1-generic N/A linux-firmware1.119 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 3.13.0-1-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/18/2013 dmi.bios.vendor:
Re: [Desktop-packages] [Bug 368187] Re: [HD3650] Kubuntu: garbage screen
I am sorry, but I have moved away from ATI and NVIDIA graphic cards. I have had enough of their faulty drivers. Life is much better with Intel. As far as I am concerned, the bug can be closed. -Giulio On Tue, Jan 7, 2014 at 7:11 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: pureblood, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com /daily-live/current/ . If it remains an issue, could you please run the following command in the development release from a Terminal (Applications-Accessories-Terminal), as it will automatically gather and attach updated debug information to this report: apport-collect -p xserver-xorg-video-ati REPLACE-WITH-BUG-NUMBER Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** Changed in: xserver-xorg-video-ati (Ubuntu) Importance: Undecided = Low ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Confirmed = Incomplete ** Attachment removed: iomem_ioports.tar.gz https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+attachment/716880/+files/iomem_ioports.tar.gz ** Attachment removed: 18-08-2009 tests.tar.gz https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+attachment/677023/+files/18-08-2009%20tests.tar.gz ** Attachment removed: bug_368187.tar https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+attachment/647921/+files/bug_368187.tar ** Attachment removed: karmic_etc.tar.gz https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+attachment/714617/+files/karmic_etc.tar.gz -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/368187 Title: [HD3650] Kubuntu: garbage screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/368187 Title: [HD3650] Kubuntu: garbage screen Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: I am not sure if my problem has already been reported or not, but it is pretty nasty, so I am reporting it. Basically, the radeon driver completely hangs my computer when the X server starts. The mouse seems working but the keyboard is completely irresponsive and the screen shows garbage as if the memory had not been initialized and still contains pieces from previous sessions. Connecting through ssh works though, so I can tell that kde 4.2 started fine and everything works ok. There is no sign of errors in the Xorg.0.log file. This happens as well with the installer cd for Jaunty. I am using a fresh installation of Jaunty, and according to lspci, my graphic card identifier is VGA compatible controller: ATI Technologies Inc RV635 PRO AGP [Radeon HD 3650] There are a lot of forums describing different problems, and it took me a long time and tries to find a workaround. What worked was to disable DRI adding the line Option DRI off to the Device section of the /etc/X11/xorg.conf file. I am still confused about it though. I could not find any meaningful log in dmesg or in Xorg.0.log and the system does not seem to notice something is wrong while being basically completely locked. This problem was not present with the Intrepid version of Ubuntu. I also needed desperately to get the radeon driver to work since both radeonhd and fglrx do not support my dual monitor setup. Bottom line, Jaunty does not work on my machine without very specific tweaking. I wish I could help more. Does this feel like an Xorg bug or a kernel bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/368187/+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 1175656] Re: nm-applet freezes
I also report having the same issue. The applet not only becomes completely unresponsive, but the sub-menus do not show up anymore. The VPN Connections sub-menu shows as completely empty and that is how I usually realize it is frozen. I do not know of any way for how to reproduce this issue. The following command restores the use: (killall nm-applet nm-applet ) -- 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/1175656 Title: nm-applet freezes Status in “network-manager” package in Ubuntu: Confirmed Bug description: nm-applet sometimes freezes for an unknown reason. I've not yet figured out a systematic way to recreate it - it's seems to be rather random. When it freezes I'm unable to ckick on any of the entries in its drop down menu. Let's say I want to change wifi network: I click on the indicator, find my other wifi abd click it - nothing. Kill nm-applet and then start it again, try to change wifi as above - works. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: country SE: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Thu May 2 17:39:39 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-02-09 (81 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 192.168.1.100 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.138 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-04-25 (6 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 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.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1175656/+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 1040885] Re: gnome-terminal auto-restores its size
I can confirm the problem still exist in the final release of Ubuntu Raring and it is indeed very annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1040885 Title: gnome-terminal auto-restores its size Status in GNOME Terminal: Fix Released Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Occurs on Quantal and Raring TEST CASE 1. Press CTRL+ALT+T to launch a terminal 2. Press CTRL+SHIFT+T to open a new tab 3. Make sure the second tab is active and resize the window (Alt+Middle mouse button or Windows handles) 4. Click on the desktop ACTUAL RESULT Size of the terminal is restored to its initial size. It doesn't occur if the window is resized while first tab is active. EXPECTED RESULT The terminal doesn't autoresize with the user clicks on the desktop ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Thu Aug 23 23:21:07 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-01-31 (204 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1040885/+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 1044657] Re: [regression] Missing LO menus when not run in Unity
I have the same issue. Sometimes the menu would not show up at all, sometimes it would show up but any selection would be completely unresponsive. The workaround was to run sudo apt-get remove libreoffice-gtk. I don't get the Unity menu anymore, but at least I can get work done. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1044657 Title: [regression] Missing LO menus when not run in Unity Status in “libreoffice” package in Ubuntu: Fix Released Status in “libreoffice” source package in Quantal: Fix Released Bug description: i've upgraded with latest packages from quantal-proposed. And now when i'm using calc, there is no more menu, only icons. Its with quantal session logged as gnome-classic. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-calc 1:3.6.1~rc2-1ubuntu1 Uname: Linux 3.6.0-030600rc3-generic i686 ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 Date: Sat Sep 1 10:47:01 2012 SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1044657/+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 1031350] Re: [quantal] no network resolution after latest upgrade of network-manager
I confirm that I have the same issue since upgrading today to the stable version Ubuntu Quantal. Manual creation of a correct resolv.conf file fixes the problem temporarily. But as soon as I connect to a different network, this operation needs to be repeated. This seems a very serious bug, it needs high priority. I don't know how to debug it. I had dnsmasq installed prior to upgrading. Could this be related in any way? -- 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/1031350 Title: [quantal] no network resolution after latest upgrade of network- manager Status in “network-manager” package in Ubuntu: Fix Released Bug description: After latest upgrade of network manager on Quantal, the system cannot do DNS resolution. ProblemType: BugDistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0~git201207271115.edb85e9-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Tue Jul 31 09:32:47 2012 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.4 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: noSourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dnsmasq.d.network.manager: [deleted] nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.5.96 connected enabled enabled enabledenabled disabled WORKAROUND: sudo mkdir /etc/NetworkManager/dnsmasq.d sudo shutdown -r now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1031350/+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
