[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
Update: running 'unity' seems to make it work for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
Although a month has passed since 17 Jan 2018, this compiz segfault surface up today on 21 February 12:20 pm GMT +8 on my lenovo T400. I am sorry if i have necroposted now, but this bug is annoying and i seek all of your kind assistance. Details are: $sudo lshw -c video *-display description: VGA compatible controller product: RV620/M82 [Mobility Radeon HD 3450/3470] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:d000-dfff ioport:2000(size=256) memory:cfff-cfff memory:cff0-cff1 $lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.7 Candidate: 2:1.18.4-0ubuntu0.7 Version table: *** 2:1.18.4-0ubuntu0.7 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2:1.18.3-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages $apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1 Candidate: 17.2.8-0ubuntu0~16.04.1 Version table: *** 17.2.8-0ubuntu0~16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 11.2.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages $dmesg | grep compiz compiz: segfault at 38 ip 7f98dd4ac240 sp 7ffc01ba0410 error 4 in libmove.so[7f98dd4a1000+15000] >From what i have read above about ppa purge and adding ppa/proposed, does it still apply to my system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699637] Re: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1699637 Title: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Status in Light Display Manager: New Status in lightdm package in Ubuntu: New Bug description: lightdm work fine with xfce4(arch linux),but when i check it's status by systemd,it show this message. Jun 21 15:55:38 archlinux systemd[1]: Starting Light Display Manager... Jun 21 15:55:38 archlinux systemd[1]: Started Light Display Manager. Jun 21 15:55:38 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:38 archlinux lightdm[465]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid Jun 21 15:55:47 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 21 15:55:47 archlinux lightdm[607]: pam_unix(lightdm:session): session opened for user jaken by (uid=0) Jun 21 17:58:33 archlinux lightdm[417]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1699637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
It seems it is a harmless message due to NetworkManager not having connection to any network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1568560 Title: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3 My WiFi connection is very unstable and I have to often restart NetworkManager service (~ a dozen times every day...): sudo systemctl -l status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago Main PID: 27832 (NetworkManager) Memory: 13.8M CPU: 1.729s CGroup: /system.slice/NetworkManager.service ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ├─27832 /usr/sbin/NetworkManager --no-daemon └─30448 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: keyfile: add connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0") avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 34) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1): bridge port virbr1-nic was attached avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): enslaved to virbr1 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Also, each time I restart my desktop, NetworkManager generates a crash report: cf. attached screenshots. I have tried an Ubuntu VM with the same packages related to networking and the exact same releases (same repositories), the crash never happens; the difference appears to be only the type of network connection: WiFi for the desktop vs Ethernet for the VM. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1568560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1231550] Re: battery status indicator shows 'estimating'
** Branch linked: lp:~unity-api-team/indicator-power/16.04-lp1559731 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1231550 Title: battery status indicator shows 'estimating' Status in indicator-power: New Status in indicator-power package in Ubuntu: Confirmed Bug description: Sometime in saucy my battery icon started showing '(estimating...)' for the 'time' in the menu bar. This could be because I: a.) am plugged into power b.) have used the thinkpad 'tp-smapi-dkms' packages to control my battery, telling it to not charge even though its plugged in I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Thu Sep 26 12:09:50 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (708 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-05-20 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1231550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1277608] Re: hostnamed should not print warning about nss-myhostname
** Also affects: systemd (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1277608 Title: hostnamed should not print warning about nss-myhostname Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: New Bug description: Currently hostnamed prints the following error in syslog: systemd-hostnamed[24508]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Since nss-myhostname was rejected as being the right approach in https://bugs.launchpad.net/ubuntu/+source/libnss- myhostname/+bug/1162478/comments/6 , we should not print the warning message in the LTS release, even if hostnamed doesn't currently modify /etc/hosts (LP: #1162475). Can we please patch this warning out to prevent users from thinking something is wrong on their system and leading them to install libnss- myhostname? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 7 12:12:20 2014 InstallationDate: Installed on 2013-11-26 (72 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-01-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1277608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
