[Touch-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Bug is still present in ubuntu 18.04. -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 896836] Re: Segmentation fault when asking help() for the list of modules
I started taskcoach in Ubuntu 18.04 beta and I got these errors: usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_set_qdata: assertion 'node != NULL' failed from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: cannot register existing type 'GtkWidget' from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: cannot register existing type 'GtkBuildable' from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_once_init_leave: assertion 'result != 0' failed from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_register_static: assertion 'parent_type > 0' failed from gtk import _gtk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/896836 Title: Segmentation fault when asking help() for the list of modules Status in PyGTK: New Status in Python: New Status in pygtk package in Ubuntu: Triaged Status in python2.7 package in Ubuntu: Triaged Bug description: Using Python 2.7.2 on Oneiric (package version is 2.7.2-7ubuntu2), I'm getting a consistent segmentation fault when I open the interactive help in a Python shell (i.e. typing "help()" in the shell) and then ask for the list of modules (by typing "modules"). The error code returned is as follows: Please wait a moment while I gather a list of all available modules... /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed from gtk import _gtk ** (python:5116): CRITICAL **: pyg_register_boxed: assertion `boxed_type != 0' failed /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: cannot register existing type `GdkDevice' from gtk import _gtk /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:40: Warning: g_type_get_qdata: assertion `node != NULL' failed from gtk import _gtk Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/pygtk/+bug/896836/+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: ubuntu automatically logs out when hovering sidebar
Ubuntu 17.10 When I use the Unity session I automatically get logged out ot I get a crash of unity under this condition: When I hover with my mouse over the sidebar I can use the top bar without problems instead. I upgraded to latest packages today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: ubuntu automatically logs out when hovering sidebar Status in nux package in Ubuntu: Confirmed Bug description: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over the sidebar or the top-bar. When I press the alt+tab combination. 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] When I log in the first thing I see is an error message showing something like this: Could not apply the configuration stored for the monitors required virtual size does not fit available size: requested=(1,1),minimum=(320,200),maximum=(8192,8192) Sometimes this appears twice. The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
Same error. Ubuntu 17.04 last updated on 23/09/2017.
--
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/1658273
Title:
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
dc.service is masked.
Status in samba package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
On a standalone desktop running zesty with a gnome-shell session, when
upgrading the samba packages, i get:
Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is
masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on
samba-ad-dc.service: No such file or directory
note: ubuntu-bug ask questions about a possible windows relationship,
but there is no option for a standalone system like that one; so as
samba is installed to satisfy qemu, these questions completly ignore
such case and send inappropriate report.
and smbd still crashing on cold boot ( lp:1658293 ) (standalone
desktop)
note2: a more recent Debian version seems workaround that output:
samba (2:4.4.5+dfsg-3)
[ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
Closes: #832352
and samba (2:4.4.6+dfsg-1)
Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
ctdb.service) Closes: #838000.
and samba (2:4.4.6+dfsg-2)
* Remove uses of tevent internals. This fixes segfault.
Closes: #840382, #840298.
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog
... time to get package synced
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization)
At 15th June 2017 under Ubuntu 17.04, upgraded to latest packages, I'm still struggling with wifi. All solutions proposed do not work. I have continuous disconnections. It is a bad bug for a new release. You won't be able to surf without an Ethernet cable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters from working (mac address randomization) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1690525] [NEW] gir1.2-gstreamer-1.0 breaks clementine
Public bug reported: Hello, I upgraded ubuntu 17.04 on the 11/05/2017 installing the mentioned package. I have an external amplifier to which I send music via Bluetooth. The consequence of installing that package is that clementine (the well known music player) stops running giving this error for any song played until the songs collection terminates: Errore di GStreamer: cambio di stato non riuscito, alcuni elementi non sono riusciti a pubblicare un appropriato messaggio di errore con il motivo del fallimento. Furthermore clementine tries to play any song of the song collection giving every time the error and involving high CPU loads. Uninstall is required to bring the situation to previous state. ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1690525 Title: gir1.2-gstreamer-1.0 breaks clementine Status in gstreamer1.0 package in Ubuntu: New Bug description: Hello, I upgraded ubuntu 17.04 on the 11/05/2017 installing the mentioned package. I have an external amplifier to which I send music via Bluetooth. The consequence of installing that package is that clementine (the well known music player) stops running giving this error for any song played until the songs collection terminates: Errore di GStreamer: cambio di stato non riuscito, alcuni elementi non sono riusciti a pubblicare un appropriato messaggio di errore con il motivo del fallimento. Furthermore clementine tries to play any song of the song collection giving every time the error and involving high CPU loads. Uninstall is required to bring the situation to previous state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1690525/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
I add my apt-term.log file. ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+attachment/4864663/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Confirmed Bug description: This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
I booted into recovery to see if there the network was working again. It is a bug of Networkmanager. Probably the username 'power' doesn't affect the connection. Solution: sudo -H gedit /etc/NetworkManager/NetworkManager.conf At the bottom of this file, copy and paste the following: [device] wifi.scan-rand-mac-address=no Restart the networkmanager sudo service network-manager restart -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
Here the same. I upgraded from 16.10 to 17.04. Network is not active. I cannot surf in internet. -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Hello there. I removed old nm package and reinstalled it by enabling the proposed. I can connect to the web but I encounter problems when I switch to another wireless hotspot. Then I see an error related to libnl and the connection crashes. I will try to remove the libnl too. -- 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/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Fix Committed Bug description: [Triage Notes] This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu. If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original Description] Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process (1057) killed by SEGV signal init: network-manager main process ended, respawning init: network-manager main process (1065) killed by SEGV signal init: network-manager respawning too fast, stopped The bug has been fixed in upstream 0.98 with these patches: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Hello I removed all packages and reinstalled the necessary. It seems to work fine yet. -- 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/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Fix Committed Bug description: [Triage Notes] This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu. If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original Description] Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process (1057) killed by SEGV signal init: network-manager main process ended, respawning init: network-manager main process (1065) killed by SEGV signal init: network-manager respawning too fast, stopped The bug has been fixed in upstream 0.98 with these patches: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Confirm the bug in ubuntu 14.04 proposed updates. A workaround is to install the program wicd-gtk or to downgrade some libraries as suggested. It is a bad bug since your connection to the web becomes impossible. To surf in the web and see this bug I used the bluetooth connection of my smartphone. -- 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/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Triaged Bug description: Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process (1057) killed by SEGV signal init: network-manager main process ended, respawning init: network-manager main process (1065) killed by SEGV signal init: network-manager respawning too fast, stopped The bug has been fixed in upstream 0.98 with these patches: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+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 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.
Ubuntu 14.04 LTS. Bug still present. It seems I have too many gpg keys (above 40). None of the reported solutions seems to solve even after deleting the entire gpg folder. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1263540 Title: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg. Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Ubuntu 13.10 apt 0.9.9.1~ubuntu3 'apt-get update' has started showing several warnings like the following, even though the keys are present: W: GPG error: http://us.archive.ubuntu.com saucy Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 'apt-key list' shows the keys in question in its output... pub 1024D/437D05B5 2004-09-12 uid Ubuntu Archive Automatic Signing Key ftpmas...@ubuntu.com sub 2048g/79164387 2004-09-12 pub 4096R/C0B21F32 2012-05-11 uid Ubuntu Archive Automatic Signing Key (2012) ftpmas...@ubuntu.com ...and its output begins with the following: gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa- manager.gpg': resource limit I see the same gpg message when I manually update/remove/add the keys in question. E.g.: $ sudo apt-key update gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': resource limit gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit gpg: key 437D05B5: Ubuntu Archive Automatic Signing Key ftpmas...@ubuntu.com not changed gpg: key FBB75451: Ubuntu CD Image Automatic Signing Key cdim...@ubuntu.com not changed gpg: key C0B21F32: Ubuntu Archive Automatic Signing Key (2012) ftpmas...@ubuntu.com not changed gpg: key EFE21092: Ubuntu CD Image Automatic Signing Key (2012) cdim...@ubuntu.com not changed gpg: Total number processed: 4 gpg: unchanged: 4 I asked about the resource limit message on the gnupg-users mailing list... http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html Based on Werner Koch's (the dev) answer... http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html ...the secure apt related programs might be making gpg use more than the maximum number of keyrings that it can handle. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1263540/+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
