[Touch-packages] [Bug 1622571] Re: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
Not even an adapter present in this pc. -- 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/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() Status in network-manager package in Ubuntu: New Bug description: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) RfKill: Can't open RFKILL control device: No such file or directory Signal: 11 SourcePackage: network-manager StacktraceTop: nm_dns_manager_end_updates () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago) UserGroups: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622571/+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 1622571] [NEW] NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
Public bug reported: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) RfKill: Can't open RFKILL control device: No such file or directory Signal: 11 SourcePackage: network-manager StacktraceTop: nm_dns_manager_end_updates () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago) UserGroups: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace yakkety ** Information type changed from Private to Public -- 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/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() Status in network-manager package in Ubuntu: New Bug description: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true
[Touch-packages] [Bug 1622571] Re: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
I use NO wifi, by the way. -- 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/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() Status in network-manager package in Ubuntu: New Bug description: it appeared right after boot, but I do use a 4.8 kernel.. Linux jaypc 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 8 09:01:03 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-04 (160 days ago) InstallationMedia: It IpRoute: default via 192.168.11.1 dev enp3s0 proto static metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.11.0/24 dev enp3s0 proto kernel scope link src 192.168.11.20 metric 100 IwConfig: lono wireless extensions. enp3s0no wireless extensions. NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) RfKill: Can't open RFKILL control device: No such file or directory Signal: 11 SourcePackage: network-manager StacktraceTop: nm_dns_manager_end_updates () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() UpgradeStatus: Upgraded to yakkety on 2016-05-20 (115 days ago) UserGroups: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da 802-3-ethernet 1473679209 ma 12 sep 2016 13:20:09 CEST yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 NETGEAR74 2508a31f-ca9b-47cc-a9e3-8f5be4686282 802-11-wireless 1463994465 ma 23 mei 2016 11:07:45 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 83b55d9f-56b0-3de7-8781-b60ac02d32da /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622571/+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 1620955] Re: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd w
Issue is not reproducible. No more conflicts at the moment. It seemed to be caused be installing updates through the gui. Maybe some questions were to be asked, but it did not do so, so it was stuck in between the updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1620955 Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920 +dfsg-4ubuntu1) Status in heimdal package in Ubuntu: Incomplete Bug description: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 ErrorMessage: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1620955/+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 1620956] [NEW] package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worde
Public bug reported: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 Dependencies: gcc-6-base 6.2.0-3ubuntu11 libc6 2.24-0ubuntu1 libcomerr2 1.43.1-1 libgcc1 1:6.2.0-3ubuntu11 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libwind0-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libwind0-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1620956 Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libwind0-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 Dependencies: gcc-6-base 6.2.0-3ubuntu11 libc6 2.24-0ubuntu1 libcomerr2 1.43.1-1 libgcc1 1:6.2.0-3ubuntu11 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libwind0-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libwind0-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libwind0-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1620956/+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 1620955] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd
Public bug reported: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 ErrorMessage: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1620955 Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920 +dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 ErrorMessage: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libhcrypto4-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libhcrypto4-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1620955/+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 1620957] [NEW] package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd wor
Public bug reported: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 Dependencies: gcc-6-base 6.2.0-3ubuntu11 libc6 2.24-0ubuntu1 libcomerr2 1.43.1-1 libgcc1 1:6.2.0-3ubuntu11 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libasn1-8-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libasn1-8-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1620957 Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libasn1-8-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) Status in heimdal package in Ubuntu: New Bug description: No clue whatsoever ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 Uname: Linux 4.6.0-040600-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Sep 6 14:32:43 2016 Dependencies: gcc-6-base 6.2.0-3ubuntu11 libc6 2.24-0ubuntu1 libcomerr2 1.43.1-1 libgcc1 1:6.2.0-3ubuntu11 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libasn1-8-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-04-04 (155 days ago) InstallationMedia: It RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc4ubuntu1 SourcePackage: heimdal Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: pakket libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 kan niet geconfigureerd worden, omdat libasn1-8-heimdal:i386 van een andere versie is (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-05-20 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1620957/+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 1452849] Re: initctl cannot find Upstart
*** This bug is a duplicate of bug 1447099 *** https://bugs.launchpad.net/bugs/1447099 Happens now on 16.10 as well, on my system... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1452849 Title: initctl cannot find Upstart Status in upstart : New Status in upstart package in Ubuntu: Triaged Bug description: Please see Apport's automatically generated files (attached) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 19:03:35 2015 DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error ExecutablePath: /sbin/upstart InstallationDate: Installed on 2011-12-08 (1246 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: /sbin/upstart --user SourcePackage: upstart UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data icon_file: (null) is_current_user: false is_logged_in: false real_name: (null) uid: 0 upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused user_name: (null) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1452849/+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
