[Bug 1824393] Re: Display corruption with Lenovo T450 and external monitors
I have also opened the following upstream bugreport: https://gitlab.freedesktop.org/xorg/xserver/issues/683 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #683 https://gitlab.freedesktop.org/xorg/xserver/issues/683 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824393 Title: Display corruption with Lenovo T450 and external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824393] Re: Display corruption with Lenovo T450 and external monitors
first video ** Attachment added: "display_corruption_1.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+attachment/5254954/+files/display_corruption_1.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824393 Title: Display corruption with Lenovo T450 and external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824393] Re: Display corruption with Lenovo T450 and external monitors
second video ** Attachment added: "display_corruption_2.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+attachment/5254955/+files/display_corruption_2.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824393 Title: Display corruption with Lenovo T450 and external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824393] [NEW] Display corruption with Lenovo T450 and external monitors
Public bug reported: We are experiencing frequent display corruption and flickering when using Lenovo T450 notebooks with the Lenovo Pro-/Ultra-Docks when external monitors are connected. We first experienced these problems when upgrading 16.04 systems to the HWE stack. The systems are using the integrated Intel graphics card (i915 kernel module) and the modesetting Xorg driver. The problems are mostly appearing when the monitors are woken up from standby (e.g. after coming back from lunch break), or when the system was suspended and is resumed. But we also have reports from users, that experience those problems during normal work, but I couldn't verify this myself yet. Sometimes removing the system from the dock and re-docking it fixes the problem temporarily, but not always. I will attach videos which show the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core-hwe-16.04 2:1.19.6-1ubuntu4.1~16.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37lvm6-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 11 18:12:00 2019 SourcePackage: xorg-server-hwe-16.04 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg-server-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824393 Title: Display corruption with Lenovo T450 and external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1824393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241834/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241832/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241828/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] Re: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station
apport information ** Tags added: apport-collected xenial ** Description changed: The autonegotiation fails sporadically for various Lenovo notebooks (e.g. T450s, T550, W540) when resuming inside the docking station. The speed ethtool reports is 10Mb/s, full duplex, even though that is not the speed the connected switch uses. So the systems are unable to send/receive any packages. Issuing the command "ethtool -r eth0" does not lead to a successful renegotiation. To get a correct link, I have to either undock the notebook for about 15 seconds, and then re-dock it, or disconnect the LAN cable for about 15 seconds, and then reconnect the cable. In my case the problem appears about one time in 10-20 suspend/resume cycles. I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem is still present in kernel 5.0-rc8. I've done a git bisect and the following commit seems to have introduced the problem: commit 04e04009bb01502f8023c707d7569ea42fba903b Author: Rafael J. Wysocki Date: Fri Feb 9 22:55:28 2018 +0100 ACPI / EC: Restore polling during noirq suspend/resume phases BugLink: http://bugs.launchpad.net/bugs/1774063 [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ] Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression) modified the ACPI EC driver so that it doesn't switch over to busy polling mode during noirq stages of system suspend and resume in an attempt to fix an issue resulting from that behavior. However, that modification introduced a system resume regression on Thinkpad X240, so make the EC driver switch over to the polling mode during noirq stages of system suspend and resume again, which effectively reverts the problematic commit. Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression) Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863 Reported-by: Markus Demleitner Tested-by: Markus Demleitner Signed-off-by: Rafael J. Wysocki Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously I have reverted the commit in the Ubuntu Bionic kernel, and cannot reproduce the problem any longer. I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=202675 + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: m5250252871 F pulseaudio + /dev/snd/controlC0: m5250252871 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=/dev/mapper/VolGroup00-swaplv + MachineType: LENOVO 20BWS00V00 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/VolGroup00-rootlv ro net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash usbcore.authorized_default=0 i915.enable_psr=0 i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 + ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-45-generic N/A + linux-backports-modules-4.15.0-45-generic N/A + linux-firmware 1.157.21 + Tags: xenial + Uname: Linux 4.15.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: dvi lapadmins projekt-lap + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 02/27/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: JBET68WW (1.32 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20BWS00V00 + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T450s + dmi.product.name: 20BWS00V00 + dmi.product.version: ThinkPad T450s + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241821/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241822/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241823/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241824/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241827/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241826/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241833/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241829/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241831/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241830/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1817562/+attachment/5241825/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817562 Title: Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817562] [NEW] Autonegotiation fails for various Lenovo notebooks when resuming inside the docking station
Public bug reported: The autonegotiation fails sporadically for various Lenovo notebooks (e.g. T450s, T550, W540) when resuming inside the docking station. The speed ethtool reports is 10Mb/s, full duplex, even though that is not the speed the connected switch uses. So the systems are unable to send/receive any packages. Issuing the command "ethtool -r eth0" does not lead to a successful renegotiation. To get a correct link, I have to either undock the notebook for about 15 seconds, and then re-dock it, or disconnect the LAN cable for about 15 seconds, and then reconnect the cable. In my case the problem appears about one time in 10-20 suspend/resume cycles. I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem is still present in kernel 5.0-rc8. I've done a git bisect and the following commit seems to have introduced the problem: commit 04e04009bb01502f8023c707d7569ea42fba903b Author: Rafael J. Wysocki Date: Fri Feb 9 22:55:28 2018 +0100 ACPI / EC: Restore polling during noirq suspend/resume phases BugLink: http://bugs.launchpad.net/bugs/1774063 [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ] Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression) modified the ACPI EC driver so that it doesn't switch over to busy polling mode during noirq stages of system suspend and resume in an attempt to fix an issue resulting from that behavior. However, that modification introduced a system resume regression on Thinkpad X240, so make the EC driver switch over to the polling mode during noirq stages of system suspend and resume again, which effectively reverts the problematic commit. Fixes: 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a regression) Link: https://bugzilla.kernel.org/show_bug.cgi?id=197863 Reported-by: Markus Demleitner Tested-by: Markus Demleitner Signed-off-by: Rafael J. Wysocki Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously I have reverted the commit in the Ubuntu Bionic kernel, and cannot reproduce the problem any longer. I have also opened a corresponding upstream bugreport on bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=202675 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: The autonegotiation fails sporadically for various Lenovo notebooks (e.g. T450s, T550, W540) when resuming inside the docking station. The speed ethtool reports is 10Mb/s, full duplex, even though that is not the speed the connected switch uses. So the systems are unable to send/receive any packages. Issuing the command "ethtool -r eth0" does not lead to a successful renegotiation. To get a correct link, I have to either undock the notebook for about 15 seconds, and then re-dock it, or disconnect the LAN cable for about 15 seconds, and then reconnect the cable. In my case the problem appears about one time in 10-20 suspend/resume cycles. I found the problem in the 4.15 Ubuntu Bionic kernel, but the problem is still present in kernel 5.0-rc8. - - I've done a git bisect and the following commit seems to have introduced the problem: + I've done a git bisect and the following commit seems to have introduced + the problem: commit 04e04009bb01502f8023c707d7569ea42fba903b Author: Rafael J. Wysocki Date: Fri Feb 9 22:55:28 2018 +0100 - ACPI / EC: Restore polling during noirq suspend/resume phases + ACPI / EC: Restore polling during noirq suspend/resume phases - BugLink: http://bugs.launchpad.net/bugs/1774063 + BugLink: http://bugs.launchpad.net/bugs/1774063 - [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ] + [ Upstream commit 3cd091a773936c54344a519f7ee1379ccb620bee ] - Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a - regression) modified the ACPI EC driver so that it doesn't switch - over to busy polling mode during noirq stages of system suspend and - resume in an attempt to fix an issue resulting from that behavior. + Commit 662591461c4b (ACPI / EC: Drop EC noirq hooks to fix a + regression) modified the ACPI EC driver so that it doesn't switch + over to busy polling mode during noirq stages of system suspend and + resume in an attempt to fix an issue resulting from that behavior. - However, that modification introduced a system resume regression on - Thinkpad X240, so make the EC driver switch over to the polling mode - during noirq stages of system suspend and resume again, which - effectively reverts the problematic commit. + However, that modification introduced a system resume regression on + Thinkpad X240, so make the EC driver switch over to the polling mode + during noirq stages of system suspend and resume again, which + effectively reverts the
[Bug 1758009] Re: Unity not starting: compiz-config crashes on login
I think I found the root cause for the compiz-config-profile-setter segfault. The call "ccsFreeContext(context);" in line 218 in compiz_config_profile_setter.c frees the context object while background event processing still uses the object, which then leads to the segfault. It seems the set_compiz_profile() call returns while a value-changed callback gets called in the background, which then calls ccsObjectGetInterface_() on the context object, but by then the context object already got destroyed. I think the best way so solve this, would be to wait for the event processing to finish before freeing the context object, but I don't know how to do that properly. But not freeing the context object in compiz_config_profile_setter.c fixes the problem for me (the cssFreeContext() is called right before the compiz-config-profile-setter exits, so I think it doesn't really matter much). So with this patch the memory gets freed on exiting of the program after the main loop has stopped. ** Patch added: "compiz-config-profile-setter_segfault.patch" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1758009/+attachment/5212325/+files/compiz-config-profile-setter_segfault.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758009 Title: Unity not starting: compiz-config crashes on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1758009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609303] Re: libbamf: BamfView child cache not reloading
@khurshid-alam Sorry for responding so late. As far as I can see, the patch wasn't applied to the bionic tree of bamf, so I think this should still be a problem in 18.04, but I haven't tested this. I have only experience with Unity and bamf in 16.04 and it seems that there were some Unity changes which mask the problem, or at least make it harder to reproduce. But that doesn't change, that I think that the cache reloading logic is wrong, and that it can lead to problems as described in my initial bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Description changed: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. - Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The - system hangs until it the systemd ShutdownTimeout expires and systemd + system hangs until the systemd ShutdownTimeout expires and systemd forcefully reboots the system. - After the system is rebooted the apport package is in "iHR" state, and + After the system is rebooted the apport package is in "iUR" state, and needs to be reinstalled to fix this. - I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). - The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. - --- + --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: unattended-upgrades 1.1ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1778219/+attachment/5155528/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1778219/+attachment/5155527/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1778219/+attachment/5155529/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] .var.log.unattended-upgrades.unattended-upgrades.log.txt
apport information ** Attachment added: ".var.log.unattended-upgrades.unattended-upgrades.log.txt" https://bugs.launchpad.net/bugs/1778219/+attachment/5155526/+files/.var.log.unattended-upgrades.unattended-upgrades.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
apport information ** Tags added: apport-collected ** Description changed: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until it the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iHR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. + --- + ApportVersion: 2.20.9-0ubuntu7.1 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-22 (0 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: unattended-upgrades 1.1ubuntu1 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: ".var.log.apt.history.log.txt" https://bugs.launchpad.net/bugs/1778219/+attachment/5155525/+files/.var.log.apt.history.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778219] [NEW] unattended-upgrades hangs on shutdown, leaves system in a broken state
Public bug reported: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until it the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iHR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656248] Re: Changing the order of monitors leads to off-screen windows
The patch I provided earlier fixed the described problem, but did also create a new problem leading to off-screen windows when two configure notifies were received (first notify was for the actual size change, while the second one was not), and the second configure notify then lead to a change of mPrevSize, while actions for the first configure notify where still being processed. The new attached patch compiz_fix_monitor_reconfiguration_2.patch fixes this. The new patch introduces mPrevSize2, which holds the actual value that is used to process the configure notify. This value only changes, when a configure notify is received that actually notifies about a change of the desktop size. ** Patch added: "compiz_fix_monitor_reconfiguration_2.patch" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1656248/+attachment/4818225/+files/compiz_fix_monitor_reconfiguration_2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656248 Title: Changing the order of monitors leads to off-screen windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1656248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656248] [NEW] Changing the order of monitors leads to off-screen windows
Public bug reported: The following steps lead to off-screen windows when using compiz on Ubuntu 14.04 (e.g. when using Unity), and having no virtual desktops configured: - Start system and login (with only one monitor connected, or using a laptop) - Connect an additional monitor after logging in, or connect the laptop to a docking station with an external monitor connected to it (which then should be automatically configured to be the right monitor) - Open a window on the additional (right) monitor - Change the order of monitors in the display settings (put the originally left monitor to the right, and vice versa) - Now the window which was opened on the originally right (now left) monitor is now off-screen The problem is, that when the order of monitors get changed, the code that recalculates the window positions, calculates the wrong positions. To calculate the new window positions, the code saves the current desktop resolution (in case the resolution changes), then changes the display configuration (e.g. enables the new monitor and re-configures the desktop) and then uses the saved (now old) desktop resolution to calculate the window positions for the new resolution. The problem is, that when changing the order of monitors, as described above, the code does not actually save the current desktop resolution (the resolution of the both monitors combined), so does not realize that the desktop resolution has actually not changed (just the order of monitors). It then uses the old saved resolution (which was the resolution for the initial single-monitor configuration). It then calculates the wrong new window positions (because it thinks the window was an a non-existing virtual desktop). The fix for the problem is to save the current desktop resolution not only when the resolution changes, but every time the display configuration changes. The problem also exists when using virtual desktops, but then the window might only be pushed to another virtual desktop, or still off-screen, depending on where the windows was placed initially. I will attach a patch that solves the problem. The patch makes sure that the current desktop resolution gets saved every time the display configuration changes, and not only when the actual desktop resolution changes. The patch is against compiz-0.9.11.3+14.04.20160425. But the problem seems still to be present in the latest upstream source. I haven't tested this, but the problematic code is still the same. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "compiz_fix_monitor_reconfiguration.patch" https://bugs.launchpad.net/bugs/1656248/+attachment/4803783/+files/compiz_fix_monitor_reconfiguration.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656248 Title: Changing the order of monitors leads to off-screen windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1656248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609303] Re: libbamf: BamfView child cache not reloading
Hello? Anyone? How can I get you to integrate this obvious and simple fix for a pretty annoying bug? It's nearly 4 months since I opened this bug report. This should most probably fix https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1326903 , which is classed as a high importance bug, and still exists in Yakkety (but more importantly for us in Trusty and Xenial, because we use the LTS releases). And this fixes a usability problem in Unity. From the bug description: "... The application icon in Unity then does not do anything (cannot raise the application window, activate a minimized window or Alt-Tab to the window)." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609303] Re: libbamf: BamfView child cache not reloading
Did anyone look into this? If not, could you please take a look? The attached patch provides an obvious and simple (one line) fix, and it would be great to see this fixed in bamf, to prevent "losing" application windows, because the corresponding Unity icon does not do anything and the windows also don't show up in the task switcher. These basic window handling bugs can really be a pain, and it took me quite some time to find the root cause, so I would really appreciate it getting integrated into the upstream bamf code. And it seems all versions from trusty up to yakkety are affected. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1326903] Re: remmina and mumble windows get lost
This might be fixed using the patch I attached to https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303 We had the same problem, but with the Citrix Receiver. The symptoms were exactly the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1326903 Title: remmina and mumble windows get lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1326903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609303] Re: libbamf: BamfView child cache not reloading
** Tags added: trusty ** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609303] [NEW] libbamf: BamfView child cache not reloading
Public bug reported: When applications close and re-open their window and BamfView changed its path, the child cache of BamfView does not reload its children and continues to work with the old cache, which does not contain any children. The application icon in Unity then does not do anything (cannot raise the application window, activate a minimized window or Alt-Tab to the window). This problem shows up for us mainly when using the Citrix Receiver, but other applications can trigger this too. This problem exists in Trusty and Yaketty (maybe older versions too, I haven't checked those), and the attached patch fixes the problem (fixes the handling of the reload_children boolean). I think the following bug report might be the same problem: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1326903 ** Affects: bamf (Ubuntu) Importance: Undecided Status: New ** Tags: trusty yakkety ** Patch added: "fix_bamf_view_child_caching.patch" https://bugs.launchpad.net/bugs/1609303/+attachment/4712958/+files/fix_bamf_view_child_caching.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609303 Title: libbamf: BamfView child cache not reloading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1609303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302885] Re: Media keyboard shortcuts not working
The bug still exists for us in 14.04 with Unity 7.2.6. We have a lot of users (>1) and this problem gets reported to us daily. I don't know a way to reproduce this, but sporadically media keys, Fn shortcuts (the systems are Lenovo T450s/T550 notebooks) and print screen stops working. The keycodes in xev look right, and the users can still configure shortcuts, as in the corresponding GUI the shortcuts/meadia keys/etc. get recognized correctly, but still don't work afterwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302885 Title: Media keyboard shortcuts not working To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584885] [NEW] Unity (14.04) does not restore modal dialogs correctly after initiating desktop view
Public bug reported: Unity on 14.04 does not restore modal dialogs correctly after switching to desktop view (Ctrl+Super+D), when the user tries to restore a single application and therefore clicks on the application icon, while in desktop view mode. Then only the main window is restored, which (of course) does not react to any mouse or keyboard events, and (at least) confuses users. However, if _NET_WM_STATE_SKIP_TASKBAR is not set on the modal dialog, then a second click on the application icon does restore the modal dialog, but if the dialog has _NET_WM_STATE_SKIP_TASKBAR set, it becomes impossible to restore the modal dialog (it is neither shown in spread view, nor in the context menu of the application icon or when using the application switcher using Alt-Tab). The modal dialog also does not get restored if the user presses Ctrl+Super+D to exit the desktop view, and the dialog has _NET_WM_STATE_SKIP_TASKBAR set. So the user has no "normal" method interact or even to close the application, which then needs to be killed (if the user even knows how to do that), or the user has to log out, with both scenarios possibly leading to loss of unsaved data. Even worse, some applications (i.e. LibreOffice) don't close when a modal dialog is opened and the user tries to log out, so the session does not close and often the only option for a user is to power off the system hard. Example for an application with modal dialog with _NET_WM_STATE_SKIP_TASKBAR not set: nautilus and the about dialog Example for an application with modal dialog with _NET_WM_STATE_SKIP_TASKBAR set: Java Control Panel (ControlPanel binary) and the about dialog (button on the first tab) ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584885 Title: Unity (14.04) does not restore modal dialogs correctly after initiating desktop view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1584885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527663] Re: firefox 43 Accept-Language header does not follow preferences
Some more info: Well I hope this is the same problem. We have the problem with newer Firefox versions right now (e.g. 45.0.1), we are using Ubuntu 14.04 though, but I guess the Firefox packages shouldn't differ much. The only difference I see is, that we don't have this problem with all our users, and a new profile seems to fix it, which is a bit different from the "how to reproduce" steps mentioned above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527663 Title: firefox 43 Accept-Language header does not follow preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1527663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527663] Re: firefox 43 Accept-Language header does not follow preferences
This affect us too. Our accept languages are "de,en-US,en", as provided by the firefox-locale-de package. The accept language configuration shows up right in the configuration dialog in Firefox and in about:config (intl.accept_languages), but still Firefox only sends "en- US,en;q=0.5" in the HTTP header. This doesn't happen for all of our users though. But I have not been able to find out any differences between those installations/configurations yet. It has something to do with the user profile, because when moving it away, and a new profile is generated the problem goes away, and when using the old profile again, the problem reappears. Though moving away/removing prefs.js does not make a difference. In the past this problem often occurred the first time Firefox was started after an update. But now it seems to stick for some users, so even after restarting Firefox many times, the problem still persists. This might not seem like a big issue, but it is for us. The problem is not only the language that is displayed, but also the other localization (dates, time of day, decimal point, etc.), when entering data into web GUIs, when printing, etc.. And this leads to all kinds of consecutive faults, when users don't realize this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527663 Title: firefox 43 Accept-Language header does not follow preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1527663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station
@Francis: This is another bug and you should open another bug report for that one. That being said, I think I haven't seen that one using the Wily kernel (yet). But I have seen one, that is probably the same bug, using newer kernels (4.4/4.5). I have reported the bug against the 4.5.0 kernel on freedesktop.org. In my case the 4.5.0 kernel also crashed in drm_dp_payload_send_msg, but got there via the intel_mst_post_disable_dp call, instead of intel_mst_enable_dp call like in your case, but I think both crashes probably have the same root cause. I have reported it here: https://bugs.freedesktop.org/show_bug.cgi?id=94534 One of the developers, Chris Wilson, raised the bug priority to highest/blocker, so I hope this will get fixed soon, but there are no patches to test yet. ** Bug watch added: freedesktop.org Bugzilla #94534 https://bugs.freedesktop.org/show_bug.cgi?id=94534 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station
@Francis: As far I can tell this is not fixed in 16.04 yet. But you could try the xserver-xorg-video-intel package from the oibaf PPA, which follows the upstream git repo closely (i.e. nightly git snapshots), and should contain the relevant patches/commits. You probably don't want all the other packages from the PPA, only the xserver-xorg-video-intel package, at least if you don't want to test the other things the PPA aims to provide, and want to keep the packages on your system as close to the official 16.04 versions as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555103] [NEW] kdump: does not generate a dump on 14.04, because the reserved memory is too low
Public bug reported: To debug kernel crashes, I have installed and configured the kernel crash dumps on a 14.04 system (with Wily HWE Stack, but the problem exist with older an newer kernels too). I have used the following documentation: https://wiki.ubuntu.com/Kernel/CrashdumpRecipe https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html The default kernel option is: crashkernel=384M-:128M The output of kdump-config show: # kdump-config show USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2400 current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-4.2.0-30-generic root=/dev/mapper/VolGroup00-rootlv ro quiet splash vt.handoff=7 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-4.2.0-30-generic /boot/vmlinuz-4.2.0-30-generic When using the "echo c > /proc/sysrq-trigger" to induce a crash, nothing happens after the Oops gets printed on the console. I have to manually turn the system off an on again, and of course, no crash dump is found in /var/crash. After raising the reserved memory to 256MB (crashkernel=384M-:256M), and triggering the crash using the sysrq, the new kernel gets started shortly after the Oops, and after the following reboot the crash dump is in /var/crash, as expected. The system is a Lenovo T450s with amd64 installation. ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555103 Title: kdump: does not generate a dump on 14.04, because the reserved memory is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1555103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552824] Re: Lenovo T450s/T550 don't switch external monitor on after resuming in docking station
Hmm, seems apport did not attach the logs, so this is the syslog from the system. The interesting suspend/resume cycle is around Mar 3 17:03:38. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-wily/+bug/1552824/+attachment/4587707/+files/syslog.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552824 Title: Lenovo T450s/T550 don't switch external monitor on after resuming in docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-wily/+bug/1552824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552824] [NEW] Lenovo T450s/T550 don't switch external monitor on after resuming in docking station
Public bug reported: After updating 14.04 systems to the Wily HWE stack, the notebooks often fail to switch on external monitors when resuming (after a suspend) them inside the docking station. Here are the steps I did: - dock the notebook in the docking station, with an external monitor connected (they are then in a side-by-side mode, not clone mode) - suspend the notebook (in this case I used the menu entry in the top right Unity menu) - resume the notebook Expected results: On resume the external monitor should be switched on and the display configuration I had before suspending should be restored. Actual result: On resume the external monitor is not switched on, although the kernel seems to think it is switched on (based on the xrandr output, which I will also attach to this bugreport). To get the monitor to switch on, I have to first switch it off, and then switch is on again (using xrandr or the system-settings GUI, both work). After doing that (e.g. xrandr --output DP2-2 --off followed by xrandr --output DP2-2 --mode 1920x1200) the displays are now in "clone" mode (I think it isn't really a clone mode, but the displays don't have any offset to each other). The same happens when using the system-settings GUI. I have reproduced the above steps with drm.debug=0x1e. I hope this helps. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic-lts-wily 4.2.0.30.24 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Mar 3 17:11:52 2016 InstallationDate: Installed on 2016-03-03 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: linux-meta-lts-wily UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-lts-wily (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "xrandr output after resuming" https://bugs.launchpad.net/bugs/1552824/+attachment/4587681/+files/xrandr_output_after_resume.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552824 Title: Lenovo T450s/T550 don't switch external monitor on after resuming in docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-wily/+bug/1552824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552262] [NEW] Compiz freezes when undocking Lenovo T450s
Public bug reported: When undocking my Lenovo T450s from the docking station (with external monitor connected), compiz frequently freezes, especially when an application is running, that does a lot of screen updates (i.e. terminal with top running at a low refresh frequency, or something like glxgears). This happens since updating a 14.04 system to the Wily HWE stack, but it is also reproducible when using Wily or Xenial. When compiz freezes, the screen gets kinda corrupted (will attach an screen shot). The screen does not get updated, only the mouse cursor works. When docking the notebook again, compiz recovers most of the time. Sometimes though, nothing happens and compiz keeps frozen. In this state only a restart of compiz or the X-Server (from the text console) help to get the system usable again. When doing a stack trace on compiz, it hangs in xcb_wait_for_reply / wait_for_reply / _xcb_conn_wait. I will attach the full stack trace. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screen shot of frozen compiz" https://bugs.launchpad.net/bugs/1552262/+attachment/4586565/+files/compiz_screen_shot.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552262 Title: Compiz freezes when undocking Lenovo T450s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1552262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1552262] Re: Compiz freezes when undocking Lenovo T450s
** Attachment added: "stack trace of frozen compiz" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1552262/+attachment/4586566/+files/compiz_stack_trace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552262 Title: Compiz freezes when undocking Lenovo T450s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1552262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station
I have created an upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=94250 The patches mentioned in the bugreport fix the problem for me. Can the Xenial version of the driver be updated, or the patches be backported? ** Bug watch added: freedesktop.org Bugzilla #94250 https://bugs.freedesktop.org/show_bug.cgi?id=94250 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543647] Re: grub-pc gets confused by variables in /etc/default/grub.d/*.cfg files
Some additional information that might be helpful:
The affected systems get installed and updated automatically, and to
have a defined state regarding the configuration files, we have the
following setting in /etc/apt/apt.conf:
DPkg::Options {"--force-confnew";"--force-confmiss";};
So new packages should always install the maintainer version of the
configuration file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543647
Title:
grub-pc gets confused by variables in /etc/default/grub.d/*.cfg files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1543647/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543647] [NEW] grub-pc gets confused by variables in /etc/default/grub.d/*.cfg files
Public bug reported:
I have made a Debian package, that installs a *.cfg file into
/etc/default/grub.d/ with the following contents:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT
usbcore.authorized_default=0"
The package runs update-grub in its postinst script.
The idea is, of course, to add "usbcore.authorized_default=0" to the
kernel command line without having to edit /etc/default/grub. When the
package gets installed after grub-pc is installed, everything seems to
work as expected at first.
But with every grub-pc update, /etc/default/grub gets changed and every
time "usbcore.authorized_default=0" gets added to the
GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub, and the
corresponding debconf variable gets updated to this value too. So with
every update of grub-pc new redundant parameters are added to the kernel
command line, and the kernel command line gets longer and longer.
When my package gets installed before grub-pc (during a complete
re-installation of the system), then /etc/default/grub will contain the
following:
GRUB_CMDLINE_LINUX_DEFAULT="usbcore.authorized_default=0"
So in this case, the default value ("quiet splash") gets discarded
completely.
Is this working as intended? I would assume, that grub-pc should leave
the GRUB_CMDLINE_LINUX_DEFAULT variable and the corresponding debconf
variable unchanged.
I also tried a different approach, that is putting a file in
/etc/default/grub.d/ with the following contents:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.authorized_default=0"
With this approach it is not possible to build multiple packages that
each just add a single parameter to the kernel command line. But for my
use-case this would be sufficient, but the value above ("quiet splash
usbcore.authorized_default=0") still gets populated into
/etc/default/grub and the corresponding debconf variable. So, when my
package gets removed, I still have to modify /etc/default/grub and the
debconf variable, to clean everything up, which I think the whole
/etc/default/grub.d/ mechanism should prevent me from having to do.
So this leads me to believe that the /etc/default/grub.d/ mechanism in
grub-pc is broken.
I think the problem is, that the config maintainer script of the package
grub-pc is sourcing /etc/default/grub AND /etc/default/grub.d/*.cfg, when
trying to find a sensible value for GRUB_CMDLINE_LINUX_DEFAULT, and then writes
it back into the debconf database.
I think the config script should only source /etc/default/grub, but not
/etc/default/grub.d/*.cfg.
Looking at the config maintainer script, the problem seems exist in all Ubuntu
versions from Precise (probably even Quantal, haven't checked that, but IMHO
this was when /etc/default/grub.d was introduced) to Wily. I have tested it
myself in Precise and Trusty.
** Affects: grub (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- grub-pc gets confused by variables /etc/default/grub.d/*.cfg files
+ grub-pc gets confused by variables in /etc/default/grub.d/*.cfg files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543647
Title:
grub-pc gets confused by variables in /etc/default/grub.d/*.cfg files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1543647/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station
** Description changed: I have a Lenovo T450s. When undocking the notebook from the docking - station (Lenovo ProDock, two monitors are connected), Xorg frequently + station (Lenovo UltraDock, two monitors are connected), Xorg frequently crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 2 15:43:35 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:5036] + Â Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Â Â Â Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2016-02-02 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20BWS00V00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=eb42241b-c617-430d-84eb-b21a749fc2ff ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS00V00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS00V00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Tue Feb 2 15:33:03 2016 xserver.configfile: default xserver.errors: - systemd-logind: failed to get session: PID 3028 does not belong to any known session - intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling CRTC:25 + Â systemd-logind: failed to get session: PID 3028 does not belong to any known session + Â intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling CRTC:25 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id4925 - vendor AUO + Â product id4925 + Â vendor AUO xserver.version: 2:1.17.3-2ubuntu2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] [NEW] Xorg crashed when undocking Lenovo T450s from docking station
Public bug reported: I have a Lenovo T450s. When undocking the notebook from the docking station (Lenovo ProDock, two monitors are connected), Xorg frequently crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Feb 2 15:43:35 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2016-02-02 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20BWS00V00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=eb42241b-c617-430d-84eb-b21a749fc2ff ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS00V00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS00V00:pvrThinkPadT450s:rvnLENOVO:rn20BWS00V00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS00V00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151217-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Tue Feb 2 15:33:03 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 3028 does not belong to any known session intel(0): sna_mode_shutdown_crtc: invalid state found on pipe 1, disabling CRTC:25 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4925 vendor AUO xserver.version: 2:1.17.3-2ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540953] Re: Xorg crashed when undocking Lenovo T450s from docking station
This is the stacktrace I got from gdb... ** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540953/+attachment/4562270/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540953 Title: Xorg crashed when undocking Lenovo T450s from docking station To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1540953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414930]
Hi, we have the same issue regarding the firmware ID, as other reported earlier. We have new T550 systems, which have the following firmware ID: # cat /sys/devices/platform/i8042/serio1/firmware_id PNP: LEN002c PNP0f13 When adding a corresponding udev rule for this firmware ID to set the udev tag, the Xorg synaptics driver get configured correctly, and the buttons behave as they should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414930 Title: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417209]
Hi, we have the same issue regarding the firmware ID, as other reported earlier. We have new T550 systems, which have the following firmware ID: # cat /sys/devices/platform/i8042/serio1/firmware_id PNP: LEN002c PNP0f13 When adding a corresponding udev rule for this firmware ID to set the udev tag, the Xorg synaptics driver get configured correctly, and the buttons behave as they should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417209 Title: [x1 carbon gen 3] trackpoint buttons are not left and right click and bios settings are not respected To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1417209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392297] Re: resolvconf 1.69ubuntu1.1 breaks network install
Are there any news regarding this problem? >From my point of view, the problem should be clear. The upstream (Debian) changes, that were introduced in the 1.69ubuntu1.1 version, don't work together with the (Ubuntu) postinst script, which causes the empty /etc/resolv.conf during installation, and then subsequent installation steps fail. So the postinst script needs to be fixed, so network installations are possible again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358762] Re: Included gzip 1.2.4 has several vulnerabilities
Will this security vulnerability get fixed at all? I realize that the impact is pretty small, because someone would have to explicitly use the gzip binary provided with klibc. But even the new klibc package in trusty/utopic/vivid still contains the old 1.2.4 version of gzip. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1358762 Title: Included gzip 1.2.4 has several vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1358762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392297] Re: resolvconf 1.69ubuntu1.1 breaks network install
I have debugged this problem further: The problem seems to be that the postinst script executes "invoke-rc.d resolvconf start", which indeed seems to execute the init script /etc/init.d/resolvconf during the installation of the package. There is no /usr/sbin/policy-rc.d in the target system, so the execution of the init script is not suppressed. When running the postinst script on it's own, it moves the original /etc/resolv.conf file to /run/resolvconf/resolv.conf and links /etc/resolv.conf to it. So far so good. But when "/etc/init.d/resolvconf start" gets called as a result of "invoke-rc.d resolvconf start", the contents of /run/resolvconf get removed (resolvconf ---wipe-runtime- directories), and a new and empty resolv.conf gets created (resolvconf --enable-updates). After that the subsequent installation steps, which try to access the network, fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392297] [NEW] resolvconf 1.69ubuntu1.1 breaks network install
Public bug reported: We are experiencing problems with Ubuntu 14.04 network installations, when using the 1.69ubuntu1.1 version of resolvconf. With this version the file /etc/resolv.conf gets reset to an empty file (does only include just the standard resolvconf comments) during the installation of the resolvconf package. After that the name resolution doesn't work anymore and the subsequent installation steps fail. If we use the 1.69ubuntu1 version, everything works fine. If I make a diff of both package contents, the most significant change seems to be the inclusion of a new Sys-V init script, which (besides other things) removes the contents of the resolvconf runtime directories when called with the option "start", and the postinst script calls "invoke-rc.d resolvconf start" at the end (included by dh_installinit), which I think should do nothing during the installation because of policy-rc.d (right?), but I wonder if it actually get's called and removes the resolv.conf file that got migrated to the runtime directories earlier in the postinst script. At least that would explain our problems, because I don't really see anything else, that could cause this problem. I see that the inclusion of the new init script is coming from debian, and they call the dh_installinit with the option "--no-start" in debian/rules, while the Ubuntu package calls the dh_installinit only with the option "-r". And debian inserts the debhelper code a lot earlier in the postinst script. Could this be what's causing the problem? As soon I have more time, I will try to debug this further and provide more information. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: [Lenovo ThinkPad X220] e1000e problem, system either reboots instead of power off or disables WOL
After reverse bisecting the kernel, the following commit, which seems to be part of a larger patch set for the e1000e driver, fixes the problem for me: commit 63eb48f151b5f1d8dba35d6176d0d7c9643b33af Author: David Ertman Date: Fri Feb 14 07:16:46 2014 + e1000e Refactor of Runtime Power Management -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: [Lenovo ThinkPad X220] e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: [Lenovo ThinkPad X220] e1000e problem, system either reboots instead of power off or disables WOL
I tested the latest kernel using the linux- image-3.16.0-031600rc2-generic_3.16.0-031600rc2.201406220135_amd64.deb package. With this kernel I was unable to reproduce the issue. The x220 System did shutdown, and WOL was still enabled and functioning. I also tested this with one of our T61 systems, because these systems began to show the issue, when I tried out the 2.5.4 e1000e driver. With the new kernel the T61 system did shutdown properly too, and WOL was still enabled. ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.16-rc2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: [Lenovo ThinkPad X220] e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132629/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132626/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132622/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132630/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132627/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132624/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132628/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132621/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132625/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132623/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132620/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132615/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132619/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132614/+files/AplayDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Card0.Codecs.codec.3.txt
apport information ** Attachment added: "Card0.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132618/+files/Card0.Codecs.codec.3.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132616/+files/Card0.Amixer.values.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132617/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] AlsaDevices.txt
apport information ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1261723/+attachment/4132613/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
apport information ** Tags added: apport-collected precise ** Description changed: When trying to shutdown a system, either the system does not power off, but reboots immediately, or Wake-On-LAN gets disabled on power off. This problem is happening on a Lenovo X220, with Ubuntu Precise. But the problem exists with all current Kernels for precise (3.5.0*, 3.8.0*, 3.11.0*). The problem is not reproducible with the current (2.5.4) e1000e driver from sf.net. Steps to reproduce the problem: - Put the powered off noteook in the port replicator - Power on the system - Wait until the system is booted and showing the lightdm login screen - Disconnect the notebook from the port replicator - Wait a couple of seconds - Connect the notebook to the port replicator - Shut the system down from the lightdm menu Expected result: The system should shut down and power off, and Wake-On-LAN should be functioning (when it was activated). Observed result: The system either doesn't power off, but reboots immediately, or in cases it actually does power off, WOL gets disabled. Additional info: It's hard to say what triggers the one or the other behaviour. It might be related to the timing of the above steps. We have some users with the problem, who normally use the notebooks during the day and experience the problems in the evening, when shutting down the system. The above steps are the best way we found to reproduce the problem. It seems that disconnecting the notebook from the port replicator, so it does run on battery, at least for a short time, seems to be a part of what triggers the problem. The 3.5 Kernel might not show the "reboot instead of power off" part of the problem, but WOL is not functioning after power off (ethernet port on the port replicator is disabled, no link). The "reboot instead of power off" part of the problem seems to not happen when WOL gets disabled before the shutdown (using ethtool) or when the e1000e gets unloaded before the shutdown. - In the case the system did power off, and WOL is not functioning, it is - possible to restore the WOL function by taking the notebook out of the - port replicator and putting it back in (while it is switched off). After - that the ethernet port on the port replicator gets enabled again, and - the system wakes up when it gets send a WOL magic packet. + In the case the system did power off, and WOL is not functioning, it is possible to restore the WOL function by taking the notebook out of the port replicator and putting it back in (while it is switched off). After that the ethernet port on the port replicator gets enabled again, and the system wakes up when it gets send a WOL magic packet. + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.11.0-23-generic. + ApportVersion: 2.0.1-0ubuntu17.6 + Architecture: amd64 + ArecordDevices: + List of CAPTURE Hardware Devices + card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] +Subdevices: 1/1 +Subdevice #0: subdevice #0 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1956 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + Card0.Amixer.info: + Card hw:0 'PCH'/'HDA Intel PCH at 0xf262 irq 51' +Mixer name : 'Intel CougarPoint HDMI' +Components : 'HDA:14f1506e,17aa21da,0012 HDA:80862805,80860101,0010' +Controls : 43 +Simple ctrls : 12 + Card29.Amixer.info: + Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' +Mixer name : 'ThinkPad EC (unknown)' +Components : '' +Controls : 1 +Simple ctrls : 1 + Card29.Amixer.values: + Simple mixer control 'Console',0 +Capabilities: pswitch pswitch-joined penum +Playback channels: Mono +Mono: Playback [on] + DistroRelease: Ubuntu 12.04 + HibernationDevice: RESUME=UUID=58b97338-611a-4c05-b5f3-fd857e8261b9 + InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) + MachineType: LENOVO 4291QQ1 + MarkForUpload: True + Package: linux (not installed) + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-23-generic root=UUID=ed1a1a2a-fef2-478a-a951-852b797c4d76 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-23.40~precise1-generic 3.11.10.10 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.11.0-23-generic N/A + linux-backports-modules-3.11.0-23-generic N/A + linux-firmware 1.79.15 + Tags: precise + Uname: Linux 3.11.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + dmi.bios.dat
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
** Also affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317012] Re: Firefox 28 doesn't use intl.accept_languages defined in syspref.js
I have to correct something: It seems older Firefox versions had the same problem, but it wasn't obvious, because the default accept_languages of the firefox-locale-de package were already "de-de,de,en-us,en". In Firefox 28 the default was changed to "de,en-us,en". Nevertheless the problem is still, that Firefox reads the setting from syspref.js and displays this correctly in about:config, but doesn't use this value when constructing the HTTP header. The problem seems to be this test: http://mxr.mozilla.org/mozilla- central/source/modules/libpref/src/nsPrefBranch.cpp#232 So the accept_languages will only be used, when they are set by a user pref, or a locked pref, but not with a "simple" pref in syspref.js. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317012 Title: Firefox 28 doesn't use intl.accept_languages defined in syspref.js To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1317012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317012] [NEW] Firefox 28 doesn't use intl.accept_languages defined in syspref.js
Public bug reported:
We have system-wide settings defined in /etc/firefox/syspref.js, amongst
others the intl.accept_languages option to define the accept languages
for our environment.
Firefox 28 (28.0+build2-0ubuntu0.12.04.1) doesn't use the accept
languages (and maybe others options) defined in syspref.js, when sending
the HTTP header, even though the intl.accept_language value shown in
about:config is correct (same as in syspref.js).
It only works, if the intl.accept_languages is defined as a lockPref in
syspref.js, which we don't want, because the users should be able to
customize the setting. But we need to explicitly set the "de-de" accept
language.
This worked in previous Firefox versions (e.g. 27 or older).
the corresponding line in syspref.js is:
pref("intl.accept_languages", "de-de,de,en-us,en");
about:config shows:
intl.accept_languages ="de-de,de,en-us,en"
accept languages, which are sent in HTTP Header (this is the default from the
firefox-locale-de package) :
"de,en-us,en"
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317012
Title:
Firefox 28 doesn't use intl.accept_languages defined in syspref.js
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1317012/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
Some additional information: I tested the latest e1000e driver from sf.net on other hardware (Lenovo T61), which is in use here too. The T61s didn't show the "reboot instead of power off" before, with the e1000e driver, that is included in the kernels mentioned above. However they do show the problem with the e1000e driver from sf.net (version 2.5.4). Maybe in 1 out of 10 cases the notebook is able to power off, and then WOL works too. But in the other cases the notebook just reboots. So it seems the driver from sf.net doesn't really solve the problem, but somehow only changes some conditions under which the bug is triggered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+attachment/3930891/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+attachment/3930893/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] Re: e1000e problem, system either reboots instead of power off or disables WOL
** Attachment added: "dmidecode.log" https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+attachment/3930892/+files/dmidecode.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261723] [NEW] e1000e problem, system either reboots instead of power off or disables WOL
Public bug reported: When trying to shutdown a system, either the system does not power off, but reboots immediately, or Wake-On-LAN gets disabled on power off. This problem is happening on a Lenovo X220, with Ubuntu Precise. But the problem exists with all current Kernels for precise (3.5.0*, 3.8.0*, 3.11.0*). The problem is not reproducible with the current (2.5.4) e1000e driver from sf.net. Steps to reproduce the problem: - Put the powered off noteook in the port replicator - Power on the system - Wait until the system is booted and showing the lightdm login screen - Disconnect the notebook from the port replicator - Wait a couple of seconds - Connect the notebook to the port replicator - Shut the system down from the lightdm menu Expected result: The system should shut down and power off, and Wake-On-LAN should be functioning (when it was activated). Observed result: The system either doesn't power off, but reboots immediately, or in cases it actually does power off, WOL gets disabled. Additional info: It's hard to say what triggers the one or the other behaviour. It might be related to the timing of the above steps. We have some users with the problem, who normally use the notebooks during the day and experience the problems in the evening, when shutting down the system. The above steps are the best way we found to reproduce the problem. It seems that disconnecting the notebook from the port replicator, so it does run on battery, at least for a short time, seems to be a part of what triggers the problem. The 3.5 Kernel might not show the "reboot instead of power off" part of the problem, but WOL is not functioning after power off (ethernet port on the port replicator is disabled, no link). The "reboot instead of power off" part of the problem seems to not happen when WOL gets disabled before the shutdown (using ethtool) or when the e1000e gets unloaded before the shutdown. In the case the system did power off, and WOL is not functioning, it is possible to restore the WOL function by taking the notebook out of the port replicator and putting it back in (while it is switched off). After that the ethernet port on the port replicator gets enabled again, and the system wakes up when it gets send a WOL magic packet. ** Affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261723 Title: e1000e problem, system either reboots instead of power off or disables WOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1261723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
