[Touch-packages] [Bug 1700590] Re: libmount-dev reports version "2.29."
Found relevant information in util-linux sources: libmount/src/libmount.h: #define LIBMOUNT_VERSION "2.29." #define LIBMOUNT_MAJOR_VERSION 2 #define LIBMOUNT_MINOR_VERSION 29 #define LIBMOUNT_PATCH_VERSION -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1700590 Title: libmount-dev reports version "2.29." Status in util-linux package in Ubuntu: New Bug description: "pkg-config --modversion mount" reports version "2.29." which breaks meson build: Meson encountered an error in file meson.build, line 636, column 0: Invalid version to compare against: '2.29.'; only numeric digits separated by "." are allowed: invalid literal for int() with base 10: '' Actual version of libmount-dev is 2.29-1ubuntu2 It's ubuntu 17.04 (Sorry for posting into util-linux, launchpad thinks that "libmount- dev" does not exist in Ubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libmount-dev 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Mon Jun 26 18:32:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-20 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700590/+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 1700590] [NEW] libmount-dev reports version "2.29."
Public bug reported: "pkg-config --modversion mount" reports version "2.29." which breaks meson build: Meson encountered an error in file meson.build, line 636, column 0: Invalid version to compare against: '2.29.'; only numeric digits separated by "." are allowed: invalid literal for int() with base 10: '' Actual version of libmount-dev is 2.29-1ubuntu2 It's ubuntu 17.04 (Sorry for posting into util-linux, launchpad thinks that "libmount-dev" does not exist in Ubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libmount-dev 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Mon Jun 26 18:32:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-20 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1700590 Title: libmount-dev reports version "2.29." Status in util-linux package in Ubuntu: New Bug description: "pkg-config --modversion mount" reports version "2.29." which breaks meson build: Meson encountered an error in file meson.build, line 636, column 0: Invalid version to compare against: '2.29.'; only numeric digits separated by "." are allowed: invalid literal for int() with base 10: '' Actual version of libmount-dev is 2.29-1ubuntu2 It's ubuntu 17.04 (Sorry for posting into util-linux, launchpad thinks that "libmount- dev" does not exist in Ubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libmount-dev 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Mon Jun 26 18:32:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-20 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700590/+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 1652457] [NEW] cannot disable whoopsie via systemd & polkit authentication
Public bug reported: Hi, today I wanted to disable whoopsie service on boot but could not do it via Polkit authentication in systemd. So command "systemctl disable whoopsie" worked properly only with sudo. I'm using Ubuntu 16.04.1 LTS and whoopsie-0.2.52.2. Here is some console log: ecko@insomnia:~$ systemctl disable whoopsie Synchronizing state of whoopsie.service with SysV init with /lib/systemd/systemd-sysv-install... Executing /lib/systemd/systemd-sysv-install disable whoopsie insserv: fopen(.depend.stop): Permission denied AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: Reverend Homer,,, (ecko) Password: AUTHENTICATION COMPLETE === update-rc.d: error: unable to write /etc/init/whoopsie.override ecko@insomnia:~$ sudo !! sudo systemctl disable whoopsie Synchronizing state of whoopsie.service with SysV init with /lib/systemd/systemd-sysv-install... Executing /lib/systemd/systemd-sysv-install disable whoopsie insserv: warning: current start runlevel(s) (empty) of script `whoopsie' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `whoopsie' overrides LSB defaults (1). ecko@insomnia:~$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sat Dec 24 21:48:44 2016 InstallationDate: Installed on 2016-10-20 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. -- Logs begin at Sat 2016-12-24 21:48:19 MSK, end at Sat 2016-12-24 21:48:19 MSK. -- Dec 24 21:48:19 hostname org.freedesktop.Notifications[1533]: ** (notify-osd:4325): WARNING **: dnd_is_idle_inhibited(): got error "The name org.gnome.SessionManager was not provided by any .service files" RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) upstart.whoopsie.override: manual ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-false xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1652457 Title: cannot disable whoopsie via systemd & polkit authentication Status in whoopsie package in Ubuntu: New Bug description: Hi, today I wanted to disable whoopsie service on boot but could not do it via Polkit authentication in systemd. So command "systemctl disable whoopsie" worked properly only with sudo. I'm using Ubuntu 16.04.1 LTS and whoopsie-0.2.52.2. Here is some console log: ecko@insomnia:~$ systemctl disable whoopsie Synchronizing state of whoopsie.service with SysV init with /lib/systemd/systemd-sysv-install... Executing /lib/systemd/systemd-sysv-install disable whoopsie insserv: fopen(.depend.stop): Permission denied AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Authentication is required to reload the systemd state. Authenticating as: Reverend Homer,,, (ecko) Password: AUTHENTICATION COMPLETE === update-rc.d: error: unable to write /etc/init/whoopsie.override ecko@insomnia:~$ sudo !! sudo systemctl disable whoopsie Synchronizing state of whoopsie.service with SysV init with /lib/systemd/systemd-sysv-install... Executing /lib/systemd/systemd-sysv-install disable whoopsie insserv: warning: current start runlevel(s) (empty) of script `whoopsie' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `whoopsie' overrides LSB defaults (1). ecko@insomnia:~$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sat Dec 24 21:48:44 2016 InstallationDate: Installed on 2016-10-20 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. -- Logs begin at Sat 2016-12-24 21:48:19 MSK, end at Sat 2016-12-24 21:48:19 MSK. -- Dec 24 21:48:19 hostname org.freedesktop.Notifications[1533]: ** (notify-osd:4325): WARNING **: dnd_is_idle_inhibited(): got error "The name org.gnome.SessionManager was not provided by any .service files
[Touch-packages] [Bug 1634855] [NEW] Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting.
Public bug reported: Hi, the net of my PC is configured via systemd-networkd + systemd-resolved. And last two weeks I faced with the problem when my net is down. "journalctl -xe" helped to detect this issue: окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting. окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long When I type "systemctl restart systemd-networkd", nothing happens, net is still down. When I type "systemctl restart systemd-resolved", it's all starting to work fine, as usual. A little bit of googling gave me this bug in systemd bugtracker: https://github.com/systemd/systemd/issues/2228 and this PR: https://github.com/systemd/systemd/pull/3224 Looks like this issue was fixed in systemd-230. So can you backport this patch to systemd package? I can patch it and test it myself, actually, but it would be really nice if there will be no need to. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu11 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 19 13:58:42 2016 InstallationDate: Installed on 2016-09-29 (19 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=1c4d999b-22b7-40c0-b803-7117cc57067a ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1634855 Title: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting. Status in systemd package in Ubuntu: New Bug description: Hi, the net of my PC is configured via systemd-networkd + systemd- resolved. And last two weeks I faced with the problem when my net is down. "journalctl -xe" helped to detect this issue: окт 19 13:36:22 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long окт 19 13:36:22 work-pc kernel: e1000e: enp2s0 NIC Link is Down окт 19 13:36:25 work-pc systemd-networkd[2200]: enp2s0: Gained carrier окт 19 13:36:25 work-pc systemd-networkd[2200]: Assertion 'link->state == LINK_STATE_SETTING_ROUTES' failed at ../src/network/networkd-link.c:697, function link_enter_configured(). Aborting. окт 19 13:36:25 work-pc systemd-resolved[10417]: Failed to read DNS servers for interface enp3s0, ignoring: Argument list too long When I type "systemctl restart systemd-networkd", nothing happens, net is still down. When I type "systemctl restart systemd-resolved", it's all starting to work fine, as usual. A little bit of googling gave me this bug in systemd bugtracker: https://github.com/systemd/systemd/issues/2228 and this PR: https://github.com/systemd/systemd/pull/3224 Looks like this issue was fixed in systemd-230. So can you backport this patch to systemd package? I can patch it and test it myself, actually, but it would be really nice if there will be no need to. ProblemType: Bug DistroRelease: Ubuntu
