[Touch-packages] [Bug 1945887] [NEW] org.bluez.obex.service contains unresolved '@libexecdir@'
Public bug reported: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: focal impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: New Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+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 1819369] Re: When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*
** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen /etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync): # m h dom mon dow user command 00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1 00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2 00 05 15-21 1,3,5,7,9,11 SATsys-maint some-task some-option #host3 00 05 22-28 1,3,5,7,9,11 SATsys-maint some-task some-option #host4 The expectation was that none of the entries is executed in parallel at - any given point in time due to column three (date of month range). - (Note: All other (default) entries work as expected, syntax of all - crontab files has been checked using + any given point in time due to column three (day-of-month range). (Note: + All other (default) entries work as expected, syntax of all crontab + files has been checked using https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki) 4) What happened instead Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1819369 Title: When specifying minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored* Status in cron package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen /etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync): # m h dom mon dow user command 00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1 00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2 00 05 15-21 1,3,5,7,9,11 SATsys-maint some-task some-option #host3 00 05 22-28 1,3,5,7,9,11 SATsys-maint some-task some-option #host4 The expectation was that none of the entries is executed in parallel at any given point in time due to column three (day-of-month range). (Note: All other (default) entries work as expected, syntax of all crontab files has been checked using https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki) 4) What happened instead Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1819369/+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 1819369] [NEW] When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen /etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync): # m h dom mon dow user command 00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1 00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2 00 05 15-21 1,3,5,7,9,11 SATsys-maint some-task some-option #host3 00 05 22-28 1,3,5,7,9,11 SATsys-maint some-task some-option #host4 The expectation was that none of the entries is executed in parallel at any given point in time due to column three (date of month range). (Note: All other (default) entries work as expected, syntax of all crontab files has been checked using https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki) 4) What happened instead Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts. ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 - 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy cron cron: - Installed: 3.0pl1-128ubuntu2 - Candidate: 3.0pl1-128ubuntu2 - Version table: - *** 3.0pl1-128ubuntu2 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status - + Installed: 3.0pl1-128ubuntu2 + Candidate: 3.0pl1-128ubuntu2 + Version table: + *** 3.0pl1-128ubuntu2 500 + 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status 3) What you expected to happen /etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync): # m h dom mon dow user command 00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1 00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2 00 05 15-21 1,3,5,7,9,11 SATsys-maint some-task some-option #host3 00 05 22-28 1,3,5,7,9,11 SATsys-maint some-task some-option #host4 The expectation was that none of the entries is executed in parallel at any given point in time due to column three (date of month range). (Note: All other (default) entries work as expected, syntax of all - crontab files have been checked using + crontab files has been checked using https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki) - 4) What happened instead Yesterday (Saturday, March 9th), the same script was executed in parallel on all four hosts. ** Summary changed: - When specifying specific minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored* + When specifying minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1819369 Title: When specifying minute,hour,day-of-month,month,day-of-week values/ranges, given day-of-month range is *ignored* Status in cron package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' # apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen /etc/crontab contains the following entries (each line lives on a separate host with identical setup, system clocks are in sync): # m h dom mon dow user command 00 05 1-7 1,3,5,7,9,11 SAT sys-maint some-task some-option #host1 00 05 8-14 1,3,5,7,9,11 SAT sys-maint some-task some-option #host2 00 05 15-21 1,3,5,7,9,11 SATsys-maint some-task some-option #host3 00 05 22-28 1,3,5,7,9,11 SATsys-maint some-task some-option #host4 The expectation was that none of the entries is executed in parallel at any given point in time du
[Touch-packages] [Bug 917231] Re: Mutual exclusion for cronjobs
For the record: There's https://github.com/poeml/withlock which can simply be put "between" cron and the applications in question… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/917231 Title: Mutual exclusion for cronjobs Status in cron package in Ubuntu: New Bug description: I'm using Ubuntu 12.04 dev with cron 3.0pl1-120ubuntu2. I encountered in the past a problem which can be solved with a new feature. Here is an example of the problem: 0 0 * * * root /usr/local/share/python/backup_to_media.py 0 0 1 * * root /usr/local/share/python/backup_to_internet.py These cronjobs do backup some data every day to a media and one time a month to the internet. The problem is on the first day of every month both backups are running at the same time. This can cause some problems like the backuped data to the internet is one day older as it should be or there are maybe exceptions because both jobs are accessing the files at the same time. Maybe there could be a priority column which controls this: 0 0 * * * root 0 /usr/local/share/python/backup_to_media.py 0 0 1 * * root 1 /usr/local/share/python/backup_to_internet.py The priority column ensures that jobs which are running at the same time are excuted sequentially (if the priority of every job is the same number we will have the current behaviour). On the first day of every month /usr/local/share/python/backup_to_media.py is executed first because it has a lower number and if it finishes /usr/local/share/python/backup_to_internet.py is executed. This would prevent complicated entries in the crontab or own complex mutual exclusion to solve this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/917231/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)
Just my 2 cents: In general, publishing important security/maintenance related notices by means of https://motd.ubuntu.com sounds like a good idea (especially if you don't use canonical-livepatch in case of critical security hazards), but I'd strongly suggest to allow for client side configuration/filtering by means of tags, e.g., * [16.10][maintenance] Ubuntu 16.10 will reach end of life on […] July 20, 2017 * [16.04][security][<4.4.0-83] Please consider updating your kernel ASAP (The second example would require version based comparisons, but you get the idea.) There's no need to disclose any client specific information, and it won't hurt to transfer a few bytes more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu) Status in base-files package in Ubuntu: Opinion Bug description: In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50 -motd-news that reads https://motd.ubuntu.com/ and displays that text with the rest of the MOTD. Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon Valley which has a reference to Ubuntu. Instead, https://motd.ubuntu.com should show relevant items to those that use Ubuntu Server (relevant security issues, etc), instead of items for desktop users. = Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu == ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 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 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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
