[Bug 1971954] Re: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1
After thinking a while about this, and having a look at our configuration for focal I thik the reason for this issue during the upgrade is that the `multipathd.service` and `multipathd.socket` were already masked in our focal setup. The `multipath-tools` packet is nevertheless attempting to restart them and this obviously fails. We had diskussed to remove/purge the `multipath-tools` due to a massive amount of the following messages in focal: ``` multipathd[696]: sda: add missing path multipathd[696]: sda: failed to get udev uid: Invalid argument multipathd[696]: sda: failed to get sysfs uid: Invalid argument multipathd[696]: sda: failed to get sgio uid: No such file or directory multipathd[696]: sdb: add missing path multipathd[696]: sdb: failed to get udev uid: Invalid argument multipathd[696]: sdb: failed to get sysfs uid: Invalid argument multipathd[696]: sdb: failed to get sgio uid: No such file or directory ``` And due to the dependency of the `ubuntu-servers` metapackage we decided to mask the `multipathd.service` and `multipathd.socket` units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971954 Title: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1971954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971954] Re: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1
Afterwards the unit is masked: ``` root@resolver-test:~# systemctl status multipath-tools ○ multipathd.service Loaded: masked (Reason: Unit multipathd.service is masked.) Active: inactive (dead) ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971954 Title: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1971954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971954] Re: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1
The interessting part of the Error message is:
```
Failed to restart multipath-tools.service: Unit multipath-tools.service failed
to load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status multipath-tools.service' for details.
invoke-rc.d: initscript multipath-tools, action "restart" failed.
○ multipath-tools.service
Loaded: [0;1;31merror[0m (Reason: Unit multipath-tools.service failed to
load properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
[0;1;31mWarning:[0m The unit file, source configuration file or drop-ins of
multipath-tools.service changed on disk. Run 'systemctl daemon-reload' to
reload units.
```
After reboot this is still the case:
```
root@resolver-test:~# systemctl status multipath-tools.service
Warning: The unit file, source configuration file or drop-ins of
multipath-tools.service changed on disk. Run 'systemctl daemon-reload' to
reload units.
○ multipath-tools.service
Loaded: error (Reason: Unit multipath-tools.service failed to load
properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
root@resolver-test:~# systemctl restart multipath-tools.service
Failed to restart multipath-tools.service: Unit multipath-tools.service failed
to load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status multipath-tools.service' for details.
root@resolver-test:~# journalctl -u multipath-tools.service
-- No entries --
root@resolver-test:~# systemctl status multipath-tools.service
Warning: The unit file, source configuration file or drop-ins of
multipath-tools.service changed on disk. Run 'systemctl daemon-reload' to
reload units.
○ multipath-tools.service
Loaded: error (Reason: Unit multipath-tools.service failed to load
properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
root@resolver-test:~# systemctl daemon-reload
root@resolver-test:~# systemctl restart multipath-tools.service
Failed to restart multipath-tools.service: Unit multipath-tools.service failed
to load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status multipath-tools.service' for details.
root@resolver-test:~# systemctl status multipath-tools.service
Warning: The unit file, source configuration file or drop-ins of
multipath-tools.service changed on disk. Run 'systemctl daemon-reload' to
reload units.
○ multipath-tools.service
Loaded: error (Reason: Unit multipath-tools.service failed to load
properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
```
multipath-tools is depended by ubuntu-server but not really used.
Even purging it fails:
```
root@resolver-test:~# aptitude purge multipath-tools
The following packages will be REMOVED:
multipath-tools{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 1,256 kB will be freed.
Do you want to continue? [Y/n/?] y
(Reading database ... 182822 files and directories currently installed.)
Removing multipath-tools (0.8.8-1ubuntu1) ...
Failed to stop multipath-tools.service: Unit multipath-tools.service not loaded.
invoke-rc.d: initscript multipath-tools, action "stop" failed.
dpkg: error processing package multipath-tools (--remove):
installed multipath-tools package pre-removal script subprocess returned error
exit status 1
dpkg: too many errors, stopping
multipathd.socket is a disabled or a static unit, not starting it.
Failed to start multipath-tools.service: Unit multipath-tools.service failed to
load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status multipath-tools.service' for details.
invoke-rc.d: initscript multipath-tools, action "start" failed.
○ multipath-tools.service
Loaded: error (Reason: Unit multipath-tools.service failed to load
properly, please adjust/correct and reload service manager: File exists)
Active: inactive (dead)
Warning: The unit file, source configuration file or drop-ins of
multipath-tools.service changed on disk. Run 'systemctl daemon-reload' to
reload units.
dpkg: error while cleaning up:
installed multipath-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
multipath-tools
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
Processing triggers for libc-bin (2.35-0ubuntu3) ...
```
Commenting out
```
if [ -z "${DPKG_ROOT:-}" ] && [ "$1" = remove ] && [ -x
"/etc/init.d/multipath-tools" ] ; then
invoke-rc.d multipath-tools stop || exit 1
fi
```
in /var/lib/dpkg/info/multipath-tools.prerm, allows me to purge
`multipath-tools` and install `ubuntu-server` including the `multipath-to
[Bug 1971954] [NEW] package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Bug-Report suggested by mechanism during `do-release-upgrade -d` from 20.04 focal to 22.04 jammy on a test machine. First upgrade attempt. | Extra debug information will be added to the bug report automatically. Haven't seen this information, yet. ;-) #1928374 does'nt really match, since that was on upgrade von 20.10 to 21.04, but might be related. The Error message displayed "multipath- tools package post-installation script subprocess returned error exit status 1" is the same, but not saying much. Kind regards, Lars ProblemType: Package DistroRelease: Ubuntu 22.04 Package: multipath-tools 0.8.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri May 6 10:10:37 2022 ErrorMessage: installed multipath-tools package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: multipath-tools Title: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-05-06 (0 days ago) ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971954 Title: package multipath-tools 0.8.8-1ubuntu1 failed to install/upgrade: installed multipath-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1971954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
Steve Arnolds package for bionic from https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/comments/25 works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
I also think CVE-2021-20230 and this bug are probably two different things. But Steve Arnold is also addressing CVE-2021-20230 in Comment#25, and it's still considered unfixed on https://ubuntu.com/security/CVE-2021-20230. So there is a a relation to this CVE, but CVE-2021-20230 is not describing this bug. This Bug should be worth a CVE, but I did't find one really describing this, yet. I'm trying one of Steves Arnolds Packages, now. Since I was experiencing crashes due this bug almost every day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20230 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917298] Re: dbus-daemon not started after reboot
** Description changed: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On - January 19th there were updates for systemd (systemd:amd64 - 245.4-4ubuntu3.4) installed. - + January 19th there were updates for systemd (systemd:amd64 from + 245.4-4ubuntu3.3 undated to 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus - Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) - Active: inactive (dead) + Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) + Active: inactive (dead) TriggeredBy: ● dbus.socket -Docs: man:dbus-daemon(1) + Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. - - When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. + When rebooting the affected machine again, this does'nt occur again, and + the dbus-daemon is started and working again. We experienced this on 4 + rather different machines on 6 reboot cycles across all Ubuntu 20.4 + (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917298] [NEW] dbus-daemon not started after reboot
Public bug reported: In the past weeks we experienced few systems coming up without started dbus-daemon after reboots due to updates. The first occurrence happens on January 21th 2021, since this time we were experiencing 0 up to 2 machines with this issue on each reboot cycle affecting all (approx 20) Ubuntu 20.4 (Focal Fossa) LTS machines. On January 21th the machines were rebooted due to a kernel update. On January 19th there were updates for systemd (systemd:amd64 245.4-4ubuntu3.4) installed. The Symptoms seem to be: ``` root@es1:~# systemctl status dbus ● dbus.service - D-Bus System Message Bus Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● dbus.socket Docs: man:dbus-daemon(1) ``` There is no `dbus-daemon` process running any more after reboot. The messages in /var/log/syslog: ``` Feb 24 09:21:52 runner1 kernel: [ 11.005391] systemd[1]: sockets.target: Found ordering cycle on dbus.socket/start [...] Feb 24 09:21:52 runner1 kernel: [ 11.012386] systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start ``` Jounalctl output ends with the dbus-Shutdown before reboot, and it is not updated any more. When rebooting the affected machine again, this does'nt occur again, and the dbus-daemon is started and working again. We experienced this on 4 rather different machines on 6 reboot cycles across all Ubuntu 20.4 (Focal Fossa) LTS machines till now. We are not experiencing this on other LTS releases than 20.4. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917298] Re: dbus-daemon not started after reboot
This affects dbus, but the last change that could probably have caused this was in systemd. ** Package changed: dbus (Ubuntu) => systemd (Ubuntu) ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917298 Title: dbus-daemon not started after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1917298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829987] Re: phpldapadmin incompatible with php-7.2 in bionic
Hi David, on Mittwoch, 11. September 2019 12:53:37 CEST you wrote: > A fix is also discussed here: > > https://github.com/leenooks/phpLDAPadmin/issues/61 > I already mentioned this in my initial bug report. It's the source where I got the hint to the commits, the patch is build from. The commit from Pull Request #62 got additional commits. > Can we expect a fixed version to be available soon on Ubuntu? > I'd hate to have to wait till 20.04! I opened this because I would like to have this fix (from the patch) in bionic and hopefully something like this in newer versions. I'm running a patched version from our internal repo. It's build by just appending the patch to the patch sequence. So I of course can't say anything to this. > ** Bug watch added: github.com/leenooks/phpLDAPadmin/issues #61 >https://github.com/leenooks/phpLDAPadmin/issues/61 Obviously References to external bugs are handled differently in comments, than in the initial bug description. But that's not our topic here. Does this also happen with the (as far as I can see) still unresolved Debian Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890127 ? It's in the same state as the bug here, an I understand it as an upstream bug report. Kind regards, Lars -- Lars Kollstedt Telefon: +49 6151 16-71027 E-Mail: l...@man-da.de man-da.de GmbH Dolivostraße 11 64293 Darmstadt Sitz der Gesellschaft: Darmstadt Amtsgericht Darmstadt, HRB 9484 Geschäftsführer: Andreas Ebert ** Bug watch added: Debian Bug tracker #890127 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829987 Title: phpldapadmin incompatible with php-7.2 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1829987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829987] phpldapadmin incompatible with php-7.2 in bionic
Hi again, for Ubuntu 18.4 bionic LTS I cherry picked the following three commits from https://github.com/leenooks/phpLDAPadmin and build the appended php-7.2-compat.patch from that: 1. https://github.com/leenooks/phpLDAPadmin/commit/49ef60f26b78a81dbaa9727be11ee3fb8db0b5bb 2. https://github.com/leenooks/phpLDAPadmin/commit/73b7795bc0b232491de35dd91ad9ea86ad34eae8 3. https://github.com/leenooks/phpLDAPadmin/commit/e37b498de19a5301188bc8d93b0b67d7ce717d3a That works for me on bionic. On newer releases this should also apply but you might need additional commits/patches e.g. Fix for PHP 7.3 - deprecated continue in switch https://github.com/leenooks/phpLDAPadmin/commit/7b1f6b5132204836a75674045309edb7005b87d2 For Ubuntu 19.10 Eoan I would suggest to upgrade to a newer upstream version from <https://github.com/leenooks/phpLDAPadmin>. As far as I can see this moved from sourceforge to github not long ago, and the code base of phpldapadmin you're relaying on seems to be quite old. ;-) I'm also crossposting this patch suggestion to the debian bug, since the debian packages are still containing the same issue as far as I can see. My launchpad Bug for this is on <https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1829987>. Kind regargs, Lars -- Lars Kollstedt Telefon: +49 6151 16-71027 E-Mail: l...@man-da.de man-da.de GmbH Dolivostraße 11 64293 Darmstadt Sitz der Gesellschaft: Darmstadt Amtsgericht Darmstadt, HRB 9484 Geschäftsführer: Andreas Ebert ** Patch added: "php-7.2-compat.patch" https://bugs.launchpad.net/bugs/1829987/+attachment/5265600/+files/php-7.2-compat.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829987 Title: phpldapadmin incompatible with php-7.2 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1829987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829987] [NEW] phpldapadmin incompatible with php-7.2 in bionic
Public bug reported:
Hi,
on Ubuntu 18.4 LTS bionic phpldapadmin prints the following messages:
Deprecated: Function create_function() is deprecated in
/usr/share/phpldapadmin/lib/functions.php on line 1083
Notice: Undefined variable: _SESSION in
/usr/share/phpldapadmin/lib/session_functions.php on line 100
Warning: Cannot modify header information - headers already sent by
(output started at /usr/share/phpldapadmin/lib/functions.php:1083) in
/usr/share/phpldapadmin/lib/page.php on line 65
Error
E_WARNING: Cannot modify header information - headers already sent by (output
started at /usr/share/phpldapadmin/lib/functions.php:1083)
PHP Debug Backtrace
File/usr/share/phpldapadmin/lib/functions.php (184)
Functionerror (a:5:{i:0;s:136:"E_WARNING: Cannot modify header
in...)
File/usr/share/phpldapadmin/lib/functions.php ()
Functionapp_error_handler (a:5:{i:0;i:2;i:1;s:125:"Cannot
modify header infor...)
File/usr/share/phpldapadmin/lib/common.php (270)
Functionheader (a:2:{i:0;s:38:"Content-type: text/html;
charset=UT...)
File/usr/share/phpldapadmin/htdocs/common.php (13)
Functionrequire_once
(a:1:{i:0;s:38:"/usr/share/phpldapadmin/lib/common)
File/usr/share/phpldapadmin/htdocs/cmd.php (13)
Functionrequire_once
(a:1:{i:0;s:41:"/usr/share/phpldapadmin/htdocs/comm...)
File/usr/share/phpldapadmin/htdocs/index.php (146)
Functioninclude
(a:1:{i:0;s:38:"/usr/share/phpldapadmin/htdocs/cmd)
Printing warnings to the HTML output is deactivated in my servers php
configuration. So this must be turned on again somewhere in the code of
phpldapadmin.
As far as I can see Ubuntu 18.10 Cosmic, 19.4 Disco and the upcoming
(19.10) Eoan should be also affected, but I'm experiencing this on
Ubuntu 18.4 bionic.
This issues were already discussed in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890127
and
https://github.com/leenooks/phpLDAPadmin/issues/61
Logging in to phpldapadmin isn't possible due to that.
Kind regards,
Lars
** Affects: phpldapadmin (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829987
Title:
phpldapadmin incompatible with php-7.2 in bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1829987/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817358] Re: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb
Hi, I also ran into this also on xenial. For me also taking the files under xenial-updates instead of xenial (as far as possible) fixed this for me. Thanks to buntix for the hint. But as the message "for unknown reasons" said, this can happen for different reasons. In my case the libc6-udeb was probably simply newer and incompatible to the initrd and/or installer binaries. And this was fixed by taking the other path with the compatible binaries. But this message might also have other reasons. The occurence is syncronized because on this date probably the newer version of libc6-udeb for xenial came out. So I won't mark Bug#1816876 or this one as duplicate, as far as not all people having this two are coming to the same results. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817358 Title: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817358] Re: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817358 Title: Ubuntu 16.04 netboot installation failed during loading of installer component libc6-udeb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826534] Re: Pix workaround should be (partially?) disabled when DANE is in use
Hi Scott, thanks. Done so far: http://postfix.1071664.n5.nabble.com/Pix-workaround-should-be-partially-disabled-when-DANE-is-in-use-td101264.html Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826534 Title: Pix workaround should be (partially?) disabled when DANE is in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1826534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826534] Re: Pix workaround should be (partially?) disabled when DANE is in use
Hi again, the 500second threshold is probably only trigggered when the server greeting is replaced by stars, Which is still done (by default) by newer Cisco ASAs, that at least support ESMTP and in the case we ran into this also let the STARTTLS pass properly. Combining PIXes which are not ESMTP ready, and DANE or other ways to enforce STARTTLS would be deadly for SMTP anyway. So leaving ESMTP activiated if STARTTLS is enforced would fix this in any case. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826534 Title: Pix workaround should be (partially?) disabled when DANE is in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1826534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826534] [NEW] Pix workaround should be (partially?) disabled when DANE is in use
Public bug reported: Hi, Postfix by default enables the pix workarround for an server after a message has been queued for more than 500s. http://www.postfix.org/postconf.5.html#smtp_pix_workaround_threshold_time If the server with an downtime of more than 500s has DANE enabled. And we're respecting DANE this leads tho the messages, when the server gets reachable again: Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: enabling PIX workarounds: disable_esmtp delay_dotcrlf for []:25 Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: TLS is required, but was not offered by host [] And the mail won't be delivered any more, and it seems like also any further mail to this server is affected. My workarround is to set smtp_pix_workarounds = delay_dotcrlf in the main.cf and leave ESMTP enabled this way. And hoping nobody is using Cisco PIXes without ESMTP today anymore. Disabling ESMTP breaks the STARTTLS support, which is necessary for DANE. If it's really neccessary there are also ways to configure exceptions, but this is OT. My suggestion for a real fix is to disable the pix workaround detection if DANE or TLS enforcement is enabled, or not to disable ESMTP in that case. This is Postfix not Ubuntu specific, and in my case occured with a postfix 3.1.0-3ubuntu0.3, but I would expect this to happen with all versions, from the documented behavior. Kind regards, Lars ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, Postfix by default enables the pix workarround for an server after a message has been queued for more than 500s. http://www.postfix.org/postconf.5.html#smtp_pix_workaround_threshold_time If the server with an downtime of more than 500s has DANE enabled. And - we're respecting dane this leads tho the messages, when the server gets + we're respecting DANE this leads tho the messages, when the server gets reachable again: - - Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: enabling PIX + Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: enabling PIX workarounds: disable_esmtp delay_dotcrlf for []:25 - Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: TLS is required, but + Apr 26 09:39:46 postfix/smtp[22908]: E7CD35F79E: TLS is required, but was not offered by host [] And the mail won't be delivered any more, and it seems like also any further mail to this server is affected. - My workarround is to set + My workarround is to set smtp_pix_workarounds = delay_dotcrlf in the main.cf and leave ESMTP enabled this way. And hoping nobody is using Cisco PIXes without ESMTP today anymore. Disabling ESMTP breaks the STARTTLS support, which is necessary for DANE. If it's really neccessary there are also ways to configure exceptions, but this is OT. + My suggestion for a real fix is to disable the pix workaround detection + if DANE or TLS enforcement is enabled, or not to disable ESMTP in that + case. - My suggestion for a real fix is to disable the pix workaround detection if DANE or TLS enforcement is enabled, or not to disable ESMTP in that case. - - - This is Postfix not Ubuntu specific, and in my case occured with a postfix 3.1.0-3ubuntu0.3, but I would expect this to happen with all versions, from the documented behavior. + This is Postfix not Ubuntu specific, and in my case occured with a + postfix 3.1.0-3ubuntu0.3, but I would expect this to happen with all + versions, from the documented behavior. Kind regards, -Lars + Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826534 Title: Pix workaround should be (partially?) disabled when DANE is in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1826534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key
Hi Markus, this was originally a Bug about SHA-1 signed repositories in local0 breaking the entire installation. The Error messages displayed, where/are not really good, changing to the shell of the install system, and having a look at /var/log/syslog there shows more. This was in 2016 and mainly a topic for xenial. But if you are still using SHA1 signed repositories this will affect you in some way in any newer release, too. Bionic removes any repositories that have invalid keys, whereas xenial fails to install the base system because all repositories where not loaded. The missing gnupg tools are affecting bionic, I would wonder if this will affect artful, too. For xenial this is definitely working. The missing gnupg tools are discussed in Bug #1754075 for bionic. There are two ways to fix. As far as I know none of them has been applied, yet. This bug is not duplicated and IMHO not really solved, but it has lost importance since SHA-1 signed repositories are getting rarer. Kind regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553121 Title: Xenial preseed fails to load key for 3rd party repo with apt- setup/local0/key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Of course only if they're inheriting special repositories this way. But the bugs referenced here IMHO are showing lot's of examples representing different reasons and ways to do this. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hello again, I don't really have an opinion if this should be solved by - changing the priority of gnupg or gnupg2 (if that wasn't only another unrelated side effect of the change described in Comment #7) - adding a dependency to gnupg2 | gnupg to apt-setup-udeb if that would be possible. - using the patch from Comment #12 As far as I can see there was no progress in the upstream bug ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 ), yet. But they're not releasing on April 26th 2018. ;-) This might be a bug affecting only advanced admins using depoyment via preseed, but it will IMHO affect everyone of them. If they haven't deactivated key verification at all. ;-) Kind regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hello, Bug #1761030 indeed describes the same issues. I've also a modified udeb in use, now. And it's working for me, but the setup is almost the same. d-i apt-setup/local0/source boolean false d-i apt-setup/local0/key string http://software.ubuntu.man-da.de/software/key.gpg d-i apt-setup/local0/repository string deb http://software.ubuntu.man-da.de/software bionic extras d-i apt-setup/local0/comment string local server After the installation completed the key was in /etc/apt/trusted.gpg.d/local_server.asc since our internal repository key was also ASCII-Armored. But I used the overlay_host configuration to get the udeb in: apt-mirror-setupapt-setup/overlay_host string software.ubuntu.man-da.de apt-mirror-setupapt-setup/overlay_directory string /software/ apt-mirror-setupapt-setup/overlay boolean true The repository key was also integrated into our modified initrd to get this working, but this alone didn't resolve the issues. With the patched udeb in http://software.ubuntu.man-da.de/software/dists/bionic/main /debian-installer/binary-amd64/Packages it works for me. Kind regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761030] Re: bionic 20101020ubuntu535: netboot installer fails with local repository
*** This bug is a duplicate of bug 1754075 *** https://bugs.launchpad.net/bugs/1754075 ** This bug has been marked a duplicate of bug 1754075 apt-setup uses apt-key but probably should not anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761030 Title: bionic 20101020ubuntu535: netboot installer fails with local repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1761030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
On Monday, 9 April 2018 12:56:12 CEST Lars Kollstedt wrote:
[...]
> This patch should IMHO work, but I have no opportunity to test it without
> your help, since we're in udeb and testing preseed issues. ;-)
Hi again,
20 times looked at it and still overlooked one detail.
This must of course be 'echo "$comment"'.
Kind regards,
Lars
--
Lars Kollstedt
Telefon: +49 6151 16-71027
E-Mail: l...@man-da.de
man-da.de GmbH
Dolivostraße 11
64293 Darmstadt
Sitz der man-da.de GmbH: Darmstadt
Amtsgericht Darmstadt, HRB 9484
Geschäftsführer: Andreas Ebert
** Patch added: "replace_apt_key_add.patch"
https://bugs.launchpad.net/bugs/1754075/+attachment/5107746/+files/replace_apt_key_add.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754075
Title:
apt-setup uses apt-key but probably should not anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi, by the way apt-key belongs to the package apt: root@bionic-test:/home/kollstedt# apt-file search apt-key [...] apt: /usr/bin/apt-key [...] It is installed when the error occurs and is exitting with the error mentioned above. But there is indeed another way to add the public key without using "apt-key add". They can simply be copied to /etc/apt/trusted.gpg.d, with the ending *.gpg if it's binary format. With the ending *.asc for ASCII-amored format. Please find a patch attached that use this way to add instead of the old way with apt-key. The two following Debian Bugs for this lead me tho this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886473 I also sent this message to the first one I considered to be the main one. For the ones reading the debian bug, this was mainly send to https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1754075 Since this also found it's way to Ubunut 18.4 bionic (unreleased LTS). But there is some (more or less) usefull disscussion but as far as I can see no patch, yet. So I prepared one. Thanks to Marga Manterola and Philipp Kern for the idea. One of the most important errors in stuff discussed there is IMHO the lack of "-- " which is necessary to prevent grep from interpreding the leading --. I also decided not to filter for things that are not relevant. Since comments describing the Publickey or it's origin might be placed above the -BEGIN PGP PUBLIC KEY BLOCK- (without hitting gpgv), and we would not be able to prevent all possible syntax evil here, without having gpg to import and export the public key to and from a temporary keyring. I'm also trying to assign a useful name to the key added this way. This patch should IMHO work, but I have no opportunity to test it without your help, since we're in udeb and testing preseed issues. ;-) Kind regards, Lars -- Lars Kollstedt Telefon: +49 6151 16-71027 E-Mail: l...@man-da.de man-da.de GmbH Dolivostraße 11 64293 Darmstadt Sitz der man-da.de GmbH: Darmstadt Amtsgericht Darmstadt, HRB 9484 Geschäftsführer: Andreas Ebert ** Bug watch added: Debian Bug tracker #851774 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 ** Bug watch added: Debian Bug tracker #886473 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886473 ** Patch added: "replace_apt_key_add.patch" https://bugs.launchpad.net/bugs/1754075/+attachment/5107719/+files/replace_apt_key_add.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
In apt-setup-0.104ubuntu5/generators/60local there is an call $chroot $ROOT apt-key add "/tmp/key$i.pub" which would be the origin of this message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi again, switching to installation shell, and doing a chroot /target apt install gnupg2 exit exit allows me to complete the installation, when continuing with the installation step preparing installation sources after this. The /var/log/syslog from the installation system shows the following messages before doing this: Apr 5 19:09:46 main-menu[2796]: (process:23507): 2018-04-05 19:09:37 URL:http://software.ubuntu.man-da.de/software/key.gpg [3121/3121] -> "/target/tmp/_fetch-url_key0.pub.24311" [1] Apr 5 19:09:46 main-menu[2796]: (process:23507): E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation A few lines above there is also the message: Apr 5 19:09:38 apt-setup: warning: /usr/lib/apt-setup/generators/60local returned error code 255; discarding output Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi again, on March 2nd we were already on 2.2.4-1ubuntu1 so there obviously was something fixing this. Since the package already wasn't marked as important this time. On this time adding the keys still worked fine. The last days it didn't on bionic. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi, looks like this has happened when changing the source of gnupg to gnupg2 with 2.2.4-1ubuntu1. The old source svn://anonscm.debian.org/pkg-gnupg/gnupg/trunk/ contains the Package as important. The new source https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git contains the Package as optional. gnupg2 was present before, but the did not build a gnupg-Package. Kind regards, ** Also affects: gnupg2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Didn't want to throw out apt-setup. ** Package changed: gnupg (Ubuntu) => apt-setup (Ubuntu) ** Also affects: gnupg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
apt-key complains about missing necessary gnupg or gnupg2 package. ** Package changed: apt-setup (Ubuntu) => gnupg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi again, https://ubuntuforums.org/showthread.php?t=2387570 may be about the same thing. But I can't see what #1553147 should have to do with this, this is referering to Xenial, we and also gregster is talking about bionic. On Xenial I stumbled in to #1553121 which had another reason, the SHA1-Deprecation. And also stumbled into #1512347 which was due to a unclean generated sources.list for the installation of the base system. Here we're talking about installing "normal" normal packages after the base system was successfully installed. But I haven't found out at which time gnupg was changed from important to optional, and if there was another mechanism letting it work afterwards. Manual packages selection will not have any effect because, the entries for local0 are commented out when preparing the regular install sources. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Repeating Comment to make the Bugs clickable (can't edit): Hi again, https://ubuntuforums.org/showthread.php?t=2387570 may be about the same thing. But I can't see what Bug #1553147 should have to do with this, this is referering to Xenial, we and also gregster is talking about bionic. On Xenial I stumbled in to Bug #1553121 which had another reason, the SHA1-Deprecation. And also stumbled into Bug #1512347 which was due to a unclean generated sources.list for the installation of the base system. Here we're talking about installing "normal" normal packages after the base system was successfully installed. But I haven't found out at which time gnupg was changed from important to optional, and if there was another mechanism letting it work afterwards. Manual packages selection will not have any effect because, the entries for local0 are commented out when preparing the regular install sources. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hi, This also seems to affect me. But with a completely local repository within the preseed-File, and a local key download using http. d-i apt-setup/local0/key string http://software.ubuntu.man-da.de/software/key.gpg But I'm not sure add-apt-key has anything to do with this, since this package hasn't been touched for a long time. I experienced apt-key was complaining about missing gnupg. But the last change there (Thu, 11 Jan 2018 13:33:17 +) is still to long ago. If this didn't stay within proposed for almost a month. ;-) And there is nothing about changing priority from important to optional mentioned in the changelog. On Xenial this was Priority Important, on bionic it's only optional. But adding it manually within the preeseed file IMHO wont help, since this will cause problems to early. This was still working on March 2nd 2018 with bionic. Kind Regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560804] Re: kscreen reports change of primary screen without apparent reason
Hello together, this seems to affect me, too. On Ubuntu 16.4 LTS. Lots off Syslog lines with: Feb 2 12:44:01 ws-kollstedt org.kde.KScreen[1925]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) Feb 2 12:44:01 ws-kollstedt org.kde.KScreen[1925]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) Changes from and to seems to be the same. Possible side effect, but Im not sure it correlates: Sometimes the Screen freezes, and after appox 30 seconds the System reboots. Usually it still works. The toggeling Screen was something i experienced on 2016-11-07, I resolved this by switching to the nvidia-367 package. root@ws-kollstedt:/home/kollstedt# lshw [...] product: GF119 [GeForce GT 610] vendor: NVIDIA Corporation [...] root@ws-kollstedt:/home/kollstedt# aptitude search nvidia | egrep '^i' i nvidia-367 - Transitional package for nvidia-375 i A nvidia-375 - Transitional package for nvidia-384 i A nvidia-384 - NVIDIA binary driver - version 384.111 i nvidia-modprobe - utility to load NVIDIA kernel modules and i A nvidia-opencl-icd-384 - NVIDIA OpenCL ICD i A nvidia-prime- Tools to enable NVIDIA's Prime i nvidia-settings - Tool for configuring the NVIDIA graphics d root@ws-kollstedt:/home/kollstedt# uname -a Linux ws-kollstedt 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Not sure obout the reasons, this looks for me only like the symptoms. ;-) Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560804 Title: kscreen reports change of primary screen without apparent reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1560804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928024] Re: apt-rdepends cannot follow correct version
Hi, I stumbled into something very similar when using apt-rdepends on Ubunutu 16.4 LTS (xenial). I think it's the same Bug. It felt like apt-rdepends used dependencies of the eldest or alphabetically first package available. Obviously not the dependencies from the latest one. This is also described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841207 This behavior also would match to the behavior described above. I can confirm this to be fixed in apt-rdepends 1.3.0-6 and would suggest a backport. Kind regards, Lars ** Bug watch added: Debian Bug tracker #841207 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841207 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928024 Title: apt-rdepends cannot follow correct version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-rdepends/+bug/928024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928024] Re: apt-rdepends cannot follow correct version
** Description changed: #apt-rdepends xuggler xuggler - Depends: ffmpeg (>= 0.7.2) - ... + Depends: ffmpeg (>= 0.7.2) + ... ffmpeg <--this dependencies is for ffmpeg 0.5.1 - Depends: libavcodec-extra-52 (>= 4:0.5.1-1) - Depends: libavcodec52 (>= 4:0.5.1-1) - Depends: libavdevice-extra-52 (>= 4:0.5.1-1) - Depends: libavdevice52 (>= 4:0.5.1-1) - Depends: libavfilter-extra-0 (>= 4:0.5.1-1) + Depends: libavcodec-extra-52 (>= 4:0.5.1-1) + Depends: libavcodec52 (>= 4:0.5.1-1) + Depends: libavdevice-extra-52 (>= 4:0.5.1-1) + Depends: libavdevice52 (>= 4:0.5.1-1) + Depends: libavfilter-extra-0 (>= 4:0.5.1-1) ... #apt-cache showpkg ffmpeg Package: ffmpeg - Versions: + Versions: 4:0.7.2-1~bpo60+1 (/var/lib/apt/lists/backports.debian.org_debian-backports_dists_squeeze-backports_main_binary-i386_Packages) (/var/lib/apt/lists/update.orangeuce.com_root_dpkg_dists_orangeuce_main_binary-i386_Packages) (/var/lib/dpkg/status) - Description Language: - File: /var/lib/apt/lists/backports.debian.org_debian-backports_dists_squeeze-backports_main_binary-i386_Packages - MD5: df399191b595483d47bdb9d233b67661 + Description Language: + File: /var/lib/apt/lists/backports.debian.org_debian-backports_dists_squeeze-backports_main_binary-i386_Packages + MD5: df399191b595483d47bdb9d233b67661 4:0.5.6-3 (/var/lib/apt/lists/ftp.us.debian.org_debian_dists_squeeze_main_binary-i386_Packages) (/var/lib/apt/lists/security.debian.org_dists_squeeze_updates_main_binary-i386_Packages) - Description Language: - File: /var/lib/apt/lists/ftp.us.debian.org_debian_dists_squeeze_main_binary-i386_Packages - MD5: 738da973fca45bd2aa160518608db0b3 + Description Language: + File: /var/lib/apt/lists/ftp.us.debian.org_debian_dists_squeeze_main_binary-i386_Packages + MD5: 738da973fca45bd2aa160518608db0b3 - - Reverse Depends: - xuggler,ffmpeg 0.7.2 - clive,ffmpeg - zoomer,ffmpeg - zoneminder,ffmpeg - xwax,ffmpeg - winff,ffmpeg - libsynfig0,ffmpeg - stopmotion,ffmpeg - soundkonverter,ffmpeg - python-scitools,ffmpeg - rtmpdump,ffmpeg - pacpl,ffmpeg - motion,ffmpeg - lives,ffmpeg - kmplayer,ffmpeg - kino,ffmpeg - kdenlive,ffmpeg - jsymphonic,ffmpeg - imagination,ffmpeg - imagemagick,ffmpeg - idjc,ffmpeg - gvb,ffmpeg - get-iplayer,ffmpeg - libavcodec52,ffmpeg 4:0.5.1-1 - ffmpeg-dbg,ffmpeg 4:0.5.6-3 - education-desktop-other,ffmpeg - clive,ffmpeg - bitpim,ffmpeg - libavbin0,ffmpeg - libav-dbg,ffmpeg 4:0.7.2-1~bpo60+1 - Dependencies: - 4:0.7.2-1~bpo60+1 - libavcodec53 (18 4:0.7.2-1~bpo60+1) libavcodec-extra-53 (2 4:0.7.2) libavcodec53 (19 4:0.7.2-99) libavcodec-extra-53 (3 4:0.7.2.99) libavdevice53 (18 4:0.7.2-1~bpo60+1) libavdevice-extra-53 (2 4:0.7.2) libavdevice53 (19 4:0.7.2-99) libavdevice-extra-53 (3 4:0.7.2.99) libavfilter2 (18 4:0.7.2-1~bpo60+1) libavfilter-extra-2 (2 4:0.7.2) libavfilter2 (19 4:0.7.2-99) libavfilter-extra-2 (3 4:0.7.2.99) libavformat53 (18 4:0.7.2-1~bpo60+1) libavformat-extra-53 (2 4:0.7.2) libavformat53 (19 4:0.7.2-99) libavformat-extra-53 (3 4:0.7.2.99) libavutil51 (18 4:0.7.2-1~bpo60+1) libavutil-extra-51 (2 4:0.7.2) libavutil51 (19 4:0.7.2-99) libavutil-extra-51 (3 4:0.7.2.99) libc6 (2 2.7) libpostproc52 (18 4:0.7.2-1~bpo60+1) libpostproc-extra-52 (2 4:0.7.2) libpostproc52 (19 4:0.7.2-99) libpostproc-extra-52 (3 4:0.7.2.99) libsdl1.2debian (2 1.2.10-1) libswscale2 (18 4:0.7.2-1~bpo60+1) libswscale-extra-2 (2 4:0.7.2) libswscale2 (19 4:0.7.2-99) libswscale-extra-2 (3 4:0.7.2.99) ffprobe (0 (null)) libavcodec-extra-53 (3 4:0.6~) libavcodec53 (3 4:0.7.2-1~bpo60+1) - 4:0.5.6-3 - libavcodec52 (18 4:0.5.1-1) libavcodec-extra-52 (2 4:0.5.1-1) libavdevice52 (18 4:0.5.1-1) libavdevice-extra-52 (2 4:0.5.1-1) libavfilter0 (18 4:0.5.1-1) libavfilter-extra-0 (2 4:0.5.1-1) libavformat52 (18 4:0.5.1-1) libavformat-extra-52 (2 4:0.5.1-1) libavutil49 (18 4:0.5.1-1) libavutil-extra-49 (2 4:0.5.1-1) libc6 (2 2.7) libpostproc51 (18 4:0.5.1-1) libpostproc-extra-51 (2 4:0.5.1-1) libsdl1.2debian (2 1.2.10-1) libswscale0 (18 4:0.5.1-1) libswscale-extra-0 (2 4:0.5.1-1) libavcodec-extra-52 (3 4:0.5.1-3) libavcodec52 (3 4:0.5.2-1) - Provides: - 4:0.7.2-1~bpo60+1 - - 4:0.5.6-3 - + Reverse Depends: + xuggler,ffmpeg 0.7.2 + clive,ffmpeg + zoomer,ffmpeg + zoneminder,ffmpeg + xwax,ffmpeg + winff,ffmpeg + libsynfig0,ffmpeg + stopmotion,ffmpeg + soundkonverter,ffmpeg + python-scitools,ffmpeg + rtmpdump,ffmpeg + pacpl,ffmpeg + motion,ffmpeg + lives,ffmpeg + kmplayer,ffmpeg + kino,ffmpeg + kdenlive,ffmpeg + jsymphonic,ffmpeg + imagination,ffmpeg + imagemagick,ffmpeg + idjc,ffmpeg + gvb,ffmpeg + get-iplayer,ffmpeg + libavcodec52,ffmpeg 4:0.5.1-1 + ffmpeg-dbg,ffmpeg 4:0.5.6-3 + education-desktop-other,ffmpeg + clive,ffmpeg + bit
[Bug 1577596] Re: ntpd not started when using ntpdate
*** This bug is a duplicate of bug 1575572 *** https://bugs.launchpad.net/bugs/1575572 Send to fast. :-( Tab, Enter wasn't a good idea, in the Bugtrackers WebGUI. :-( ;-) The differences between the versions and platforms are probably just timing. But this happens deterministically on xenial, might be the time difference was large enough. Kind regards, Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577596] Re: ntpd not started when using ntpdate
*** This bug is a duplicate of bug 1575572 *** https://bugs.launchpad.net/bugs/1575572 Hi Martin, the fix for Bug #1575572 released yesterday turns the situation from bad to worse from my experience. Since I saw this on i686 only before, I am experiencing this also on amd64 since installing the init-system-helpers update today. | yellow Other updates (2): apt-get install init init-system-helpers | init (1.29ubuntu1 1.29ubuntu2) | init-system-helpers (1.29ubuntu1 1.29ubuntu2) >From my experience this is something that happens when ntpdate isn't ready when systemd tries to start ntpd and ntpd wasn't started before /etc/network/if-up.d/ntpdate is started. As far as I can see this is because /etc/network/if-up.d/ntpdate from ntpdate and /etc/init.d/ntp from ntp try to handle each other's locks but don't do that properly. The init.d script simply breaks the locks from ntpdate, even if ntpdate is still running. My workarround I had already used on Ubuntu 12.4 LTS (precise), but it was unnecessary on Ubuntu 14.4 LTS (trusty), and now it's in again for 16.4 LTS (xenial) was to let the ifup-Script wait for the ntpd. But that's possibly not the best solution. ;-) For the Question why to use ntpdate *and* ntpd: We do this to immediately sync the clocks of physical test servers (which are not always on, to save energy) on boot, whereas during normal operation the slow drift of ntpd is the wished behavior. So it possibly would be a much better solution (for me) to remove /etc/network/if-up.d/ntpdate, and start the ntpdate before ntpd from /etc/init.d/ntp if it's present, and of course wait until it's ready before starting ntpd. Kind regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1512347] Re: invalid sources.list generated from reading apt-setup/local0/repository
Hi Adam, hi Schlomo, for me it works with the package that has been put into proposed on the evening of May 11th 2016. Sorry for the late reply. On Wednesday, 11. Mai 2016, 16:42:12 Adam Conrad wrote: > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Your feedback will aid us getting this update > out to other Ubuntu users. https://wiki.ubuntu.com/Testing/EnableProposed: [...] | | Installation testing using -proposed |-- | | Sometimes you may be asked to test a netboot installer image from trusty- | proposed. The images may be found here (replace "i386" with your | architecture as necessary): | | http://archive.ubuntu.com/ubuntu/dists/trusty-proposed/main/installer-i386/ | | In order to install successfully from these images, you will normally need | to tell the installer to fetch its own components from -proposed as well, | which is not the default. To do this, add the following boot parameter: | | apt-setup/proposed=true | | You must make sure that the mirror you are installing from contains packages | from -proposed. All official mirrors will do so; if you operate your own | mirror or use a site-local mirror, it may need to be modified to pull from | -proposed. Make sure that you do not simply use a loopback mount of a CD or | DVD image as an installation source; this is one of the cases where such | mirrors will not work, since they do not contain the updated kernel packages | required by the new installer. | | [...] Tests I've done: 1. First I compared the versions between archive.ubuntu.com and our mirror, to make sure the Cronjob running at night took over all the changes, and the upstream mirror also did. 2. In the second step I added the "proposed" option to our PXE-Environment, to the preseed-File, and to our automation script creating and updating the directory structure for PXE (including the initrd with the) and the Customized Netboot-ISO-Image. 3. Then I removed the "deb" workaround from our preseed-File, and called the automation script to put our new preeseed-File into initrd. It is now containing: - the apt-setup/proposed=true - and the local0/repository *without* the manually prepended "deb" 4. Now I installed the testing machine with proposed. The installation was successfully done, this failed before (with 1.158ubuntu2). All selected packages were installed, the proposed-Repository was also included after installation and "debconf-get-selections --installer" shows the local0/repository without the prepended deb. This looks fine, now. 5. Then I added the Workarround "deb" again, and called the automation script to put our new preeseed-File into initrd. It is now containing: - the apt-setup/proposed=true - and the local0/repository *with* the manually prepended "deb" Workarround. 6. Now I installed the testing machine with proposed, again. Installation was also successful. All selected packages were installed, the proposed-Repository was also included after installation and "debconf-get-selections --installer" shows the local0/repository without the prepended deb. Also still worked. 7. Now, thuesday (12th) was over, since I of course had some other work this day. ;-) On Friday morning i've read Colins post. To be sure I also added the apt-setup/proposed=true to the kernel command line, and repeated the steps above (within the next past days). The results were the same. We are not distributing self build kernels or something like this via local0/repository at the moment. So the local0 isn't really used at this early point in the installation process, but the installation failed before (with 1.158ubuntu2) due to the syntax error in sources.list, and printed an error that no kernel could be installed. This doesn't happen any more with the packages from xenial-proposed. The not started ntpd in xenial-proposed amd64 (after fully completing the installation) i've ignored as unrelated to this. Looks a bit like something I only experienced on i386/i686 before. Yes, there were changes on other packages in proposed (also mentioned in Bug #1577596) that probably cause this, but I didn't really hunt this down, yet. ;-) Did all the tests above with amd64 only. Tested i386/i686 proposed only with the workarround "deb" in, till now. Since we're only changing something interpreted by Shell, I don't expect any surprises at this point. ;-) The fix works fine (as expected) from my side. Kind regards Lars -- man-da.de GmbH, AS8365 Phone: +49 6151 16-71027 Mornewegstraße 30 Fax: +49 6151 16-71198 D-64293 Darmstadt e-mail: l...@man-da.de Geschäftsführer Marcus Stögbauer
[Bug 1512347] Re: invalid sources.list generated from reading apt-setup/local0/repository
Hi Collin, oops, missed the deb again. :-( ;-) Thank you for correcting. :-) :-) Attached the corrected one for completeness. ;-) base-installer (1.158ubuntu3) already contains the corrected. Obviously you have also corrected the indentation matching the lines above in 1.158ubuntu3. :-) As far as I can see 1.158ubuntu3 is only availabe for Yakkety Yak (active development) at the moment, hope it will get into Xenial Xerus as a bugfix within the next weeks also. ;-) Most people affected by this would be LTS users. Thank you. :-) Kind regards, Lars ** Patch added: "MissingDeb-2016-05-04.patch" https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+attachment/4655258/+files/MissingDeb-2016-05-04.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512347 Title: invalid sources.list generated from reading apt- setup/local0/repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key
On Monday, 2. May 2016, 16:13:37 I wrote: > As far as I know ~anders-kaseorg should be right in Bug #155. The > keys are statically imported to the trusted-Keychain. The SHA-1 o > signature isn't used for any verification in any apt mechanisms I know. > For this reason the warning in the output of apt-get update should be > more than enough. On Monday, 2. May 2016, 18:14:00 I wrote: > | W: [...] > | Signature by key 882F7199B20F94BD7E3E690EFADD8D64B1275EA3 uses > | weak digest algorithm (SHA1) On Monday, 2. May 2016, 18:14:00 I wrote: > IMHO for nothing! Hi all, another correction to the backgrounds of the SHA-1 stuff. Someting missleads me the SHA-1 signature on the key to be the security issue. It's the signature in the Release.gpg / InRelease file that causes the issue. For more details: http://www.cs.umd.edu/~jkatz/papers/pgp-attack.pdf Exchanging the Key would be usefull to make old signatures worthless for future attacks. But the key itself is not / or at least should not be the cause of this message. ;-) That would mean that the lines in gpg.conf should probably fix that, if exchanging the key is not an option. If you're doing this, you must hope nobody can find old signatures of your key. An hash collision atack (the length attack is a special case of this) isn't an easy attack, but for distributing malware as security update via an compromised or malvious mirror server this isn't impossible someone does. For this it's reasonable to warn or disable this by default with an error message. Now, from background informations back to the bug... Of course this does'nt change the following... On Monday, 2. May 2016, 16:13:37 I wrote: > In our case netboot install failed with a "no suitable kernel found with > your apt settings" (message text written down from memory), when our > internal software repository was included to bootstrap our deployment > environment. [...] > IMHO this should at least be catched with a propper error message. On Monday, 2. May 2016, 18:14:00 I wrote: > Or people are simply > deploying the repository URL via preseed and get weired errors, now. > > At least the last case *should* be fixed, since this will burn a lot of > time. And I didn't mean my time, I know this Bug, now. ;-) :-D As mentioned in my previos messages, I tried to find the lines causing this but without success, or at least without being able to reproduce this with the eqations of the binarys in an usual xenial installation (the scripts would IMHO run with the udeb eqations of gpgv and apt-get - I asummed they're behaving equally but do they?). This is'nt really easy to trobleshoot because there are mutiple special packages for installation and bootstraping playing together. ;-) Kind regards, Lars -- man-da.de GmbH, AS8365 Phone: +49 6151 16-71027 Mornewegstraße 30 Fax: +49 6151 16-71198 D-64293 Darmstadt e-mail: l...@man-da.de Geschäftsführer Marcus StögbauerAG Darmstadt, HRB 94 84 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553121 Title: Xenial preseed fails to load key for 3rd party repo with apt- setup/local0/key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key
Hi all, to clarify somthing that might be missunderstood in my previous post. Of course the hpe stuff is OT. What I meant to say with this, is that the list on https://wiki.debian.org/Teams/Apt/Sha1Removal is still incompletely reflecting the repositories affected, and will probably always be. There are plenty of additional repositories. Workaround in some cases might be to inherit the repository by adding it after installation. "apt-get update" only displays a warning. We were already doing this because, not all our servers were from HPE, and this works so far with the mentioned warning. ;-) But in some cases such workarrounds aren't wanted. Or people are simply deploying the repository URL via preseed and get weired errors, now. At least the last case *should* be fixed, since this will burn a lot of time. IMHO for nothing! As far as I can see, neither apt-setup and base-installer are dealing with the keys themselves the verification done in debootstrap (used by base-installer) doesn't look like there is anything done with the HASH-Algorithm. Both are dealing with apt-get, but: | root@xenial-test2:/home/kollstedt# apt-get -o APT::Get::List-Cleanup=false update; echo "return code = $?" [...] | Ign:7 http://downloads.linux.hpe.com/SDR/repo/mcp/ubuntu trusty/current InRelease | Hit:8 http://downloads.linux.hpe.com/SDR/repo/mcp/ubuntu trusty/current Release | Reading package lists... Done | W: http://downloads.linux.hpe.com/SDR/repo/mcp/ubuntu/dists/trusty/current/Release.gpg: Signature by key | 882F7199B20F94BD7E3E690EFADD8D64B1275EA3 uses weak digest algorithm (SHA1) | return code = 0 Used the HPE for test, since our internal reposiory has a SHA-2-256 now. I don't see them dealing with any output. ;-) Any ideas so far? Kind regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553121 Title: Xenial preseed fails to load key for 3rd party repo with apt- setup/local0/key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key
Sorry, was the old name: > The SHA1 warnings/errors also affects the repositories on > http://downloads.linux.hp.com, but they don't offically support > Ubuntu 16.4 LTS (xenial), yet. Of course this is http://downloads.linux.hpe.com/, now. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553121 Title: Xenial preseed fails to load key for 3rd party repo with apt- setup/local0/key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key
Hi all, first thanks to ~juliank, this lead me to an workaround for this in my case. In our case netboot install failed with a "no suitable kernel found with your apt settings" (message text written down from memory), when our internal software repository was included to bootstrap our deployment environment. Switching from the ncurses-installer to a shell showed up, that /target/etc/apt/sources.list contains only a invalid placeholder for the main repository, when this error occurs. From my memory this was xenial.invalid but might also have been debootstrap.invalid. Replacing the signing key by one with SHA-2-256 solved this, then I stumbled into Bug #1512347 which was already mentioned above. That IMHO means Bug #1553121 is definitely a SHA-1 issue. Because first I missed the lines | personal-digest-preferences SHA256 | cert-digest-algo SHA256 | default-preference-list SHA512 SHA384 SHA256 SHA224 AES256 AES192 AES CAST5 ZLIB BZIP2 ZIP Uncompressed in ~/.gnupg/gpg.conf (on a Machine with Ubuntu 12.04 LTS (precise)) and created key signed with SHA-1 again (as visible with pgpdump). With this mistake the error still occurs. ;-) As far as I know ~anders-kaseorg should be right in Bug #155. The keys are statically imported to the trusted-Keychain. The SHA-1 o signature isn't used for any verification in any apt mechanisms I know. For this reason the warning in the output of apt-get update should be more than enough. IMHO this should at least be catched with a propper error message. I didn't find the lines causing this, yet. The gpgv calls in the debootstrap Package file functions should work, at least from the output on a fully installed xenial system. Another place doing similar stuff I haven't found. The SHA1 warnings/errors also affects the repositories on http://downloads.linux.hp.com, but they don't offically support Ubuntu 16.4 LTS (xenial), yet. Kind regards Lars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553121 Title: Xenial preseed fails to load key for 3rd party repo with apt- setup/local0/key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512347] Re: invalid sources.list generated from reading apt-setup/local0/repository
Hi all, I also stumbled into this Bug in Ubuntu 16.4 LTS (xenial). I can't really confirm this for ubuntu 14.4 (trusty) so far. I can confirm the the line causing this to be already in 1.144ubuntu1 but it doe'snt seem to have effect (at least for me and our pxe install environment). My last 14.4 installation ist about 3 weeks ago, now. But I added the workarrounds, when starting our tests for Xenial-Deploment. From the dates I've seen, this should be already in use on 14.4 (even with a netboot initrd, created in march 2015) but perhaps the file created here is never used in some cases, because it is already overwritten or overridden by another udeb (e.g. apt-setup(-udeb) itself). The appended patch should fix this, but keep the workarrounds working. ;-) All lines above in library.sh function configure_apt are containing the leading deb and since apt-setup ignores and adds the deb here this should IMHO be also done here. ;-) The way to do this was borrowed from apt-setup generators/60-local. Kind regards, Lars ** Patch added: "MissingDeb-2016-05-02.patch" https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+attachment/4653600/+files/MissingDeb-2016-05-02.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512347 Title: invalid sources.list generated from reading apt- setup/local0/repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1512347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1103428] Re: Xymon history page does not work
Dear Mr. Brun, on Friday, 4. April 2014, 18:07:05 you wrote: > Just installed xymon on ubuntu server used the apt-get install to > get the latest, so I'm at 4.3.0-0.beta2. I have the exact problem as > titusx described. The history works if I manually edit the URL.I > see the patch, but my question is what do I do with it...how do I apply > it to my system? Thanks. The patches discussed here have not been taken into the offical ubuntu repositories yet. The bug is now in for more than a year and destroys some important features of the xymon webfrontend. The Bug is fixed in the xymon packages of Ubuntu 13.4 (raring) and later, by modifying much more code than the patches showed here. But this packages also are containing modifications not suitable for a bugfix version of packages and are requiring lots of modifications when upgrading in a complex xymon environment. The most importent changes are taking: /etc/hobbit to /etc/xymon /etc/hobbit/hobbitlauch.d to /etc/launch.d /etc/hobbit/bb-hosts to /etc/xymon/hosts /usr/lib/hobbit to /usr/lib/xymon /var/lib/hobbit to /var/lib/xymon All Config-Variables in hobbitserver.cfg and hobbit-client.cfg formerly containing the word HOBBIT are changed to XYMON. There might be some more changing, since I had a look at this new packages, but I'm still using only the old ones. If you are installing a new xymon server this packages or even the ubuntu versions using it might be a good choice. Starting with one of these newer packages might prevent you from changing all the stuff mentioned above. But I think it should be clear to everyone what this means to existing installations. How to use the patches: The Patches from #29 an #30 are applied to the packages for precise and lucid by copying them into the debian/patches of the source code and appending them to debian/patches/serial. The Packages resulting from this, including the source-code can be found in my ppa: https://launchpad.net/~lk-x/+archive/ppa Hope this was helpful. Kind regards, Lars -- Achtung: Seit 28. August 2013 neue Rufnummern! man-da.de GmbH, AS8365 Phone: +49 6151 16-71027 Mornewegstraße 30 Fax: +49 6151 16-71198 D-64293 Darmstadt e-mail: l...@man-da.de Geschäftsführer Marcus StögbauerAG Darmstadt, HRB 94 84 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/hobbit-mon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
And as I already said. I did get the version dependency out. So here is the patch file without whitespace garbage for lucid. ** Patch added: "lk2013-05-24_historybutton_lucid.patch" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3685570/+files/lk2013-05-24_historybutton_lucid.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Posting a modified version of my last mail to Axel Beckert... with some
updates:
On Thuesday, 23. May 2013, 22:32:33 Axel Beckert wrote:
[...]
> I rather expected that it was fixed in another way, but I haven't
> found any evidence.
Indeed they did:
| web/history.c: fprintf(htmlrep, "%s",
|xgetenv("XYMONPAGEROWFONT"), htmlquoted(displayname));
| web/history.c: fprintf(htmlrep, " - %s\n",
|htmlquoted(service));
| web/history.c: sprintf(p, "&IP=%s", htmlquoted(ip))
They seperated all calls to htmlquoted, and called the function each time a
variable from the HTTP-Request is inserted into the HTML-Code. The code using
the htmlqouted-Function looks quite different from the code I read in January.
The old code did this when the code was passed to the output funtion. And it
did many calls before copying the strings out of the buffer.
Things like this:
| sethostenv(htmlquoted(displayname), htmlquoted(ip), htmlquoted(service),
| colorname(color), htmlquoted(hostname));
And this example results in the hostname beeing inserted as color, service, ip
and displayname also.
I had a look to xymon-4.3.11, and found 94 different calls to "htmlquoted".
The old code of 4.3.0~beta2.dfsg-5ubuntu0.1 and 4.3.0~beta2.dfsg-9.1ubuntu0.1
contains only a few, about 8 ... 10 calls when I remember this correct.
This changes of course would also fix the bug. And it fixes it in a more clean
way. But is much more modification to the Code than Ulric's fix in the
htmlqouted function itself.
I think the new fix would be much better to debug for future releases of
xymon. But I'm not sure it is a good idea to port it back to a stable release
or even to a LTS release, since many scattered lines of change are IMHO many
possibilities for mistakes.
>
> I can apply that patch for the upcoming 4.3.11-1 experimental package
> if wanted.
I don't think it makes sense to integrate it there under this circumstances.
I'm more interessted to get a patch for this issue into the packages for
precise and lucid. At least into future patched versions.
The version 4-3-7 already contains the new bugfix code. I didn't have a
look at the packages for quantal yet.
> I though never ran into that issue (running
> 4.3.0~beta2.dfsg-6+squeeze1 on Squeeze and a 4.3.10 packaging snapshot
> on Squeeze and Wheezy) and hence can't check if it works. (I also ran
> 4.3.7-1 for a while on Squeeze and didn't notice it there, but also
> didn't use history a lot there.)
The error is absolutely reproduceable. My very first quickfix was some
javascript-Code in the page footer. But this didn't fix the headlines on the
details and history pages. It only made the history button working again,
by filling the forms again with corrected values.
This was on Thu, 17 Jan 2013, one day after the bug has also reached
lucid.
>
> > The Bug came in with the 2011-1716 Patch.
>
> I guess you mean CVE-2011-1716.
Yes, I cut the leading 7 since it has a different number in this place for
lucid/precis and also cut the CVE by mistake.
> I didn't understand that sentence. Did you mean "And all should be
> affected by this bug"?
Yes. This was english with a bit of german grammar, sorry for this. And they
also aren't as clarified above.
>
> This patch though has, as the one before, unnecessary whitespace
> changes in it, which makes it hard to see the real functional changes.
> I had to check every single line manually to actually see the
> functional changes. Could you please post a patch without changing the
> indentation of unchanged lines? TIA!
Ok, let's try with fewer, Whitespace-Garbage. But I'didn't get rid the Version
dependency. Looks like this is caused by different whitespaces in
7-CVE2011-1716 and 9-CVE2011-1716. In lines the diff uses to find the right
code. ;-) :-(
| $ diff lucid/lk2013-05-24_historybutton_lucid.patch
precise/lk2013-05-24_historybutton_precise.patch
| 2,7c2,7
| < --- xymon-4.3.0-beta2.orig/lib/strfunc.c 2013-05-24 09:24:35.0
+0200
| < +++ xymon-4.3.0-beta2.patched/lib/strfunc.c 2013-05-24 08:58:34.0
+0200
| < @@ -183,29 +183,36 @@ char *htmlquoted(char *s)
| <* This routine converts a plain string into an html-quoted string
| <*/
| <
| ---
| > --- xymon-4.3.0-beta2.orig/lib/strfunc.c 2013-05-24 09:27:43.0
+0200
| > +++ xymon-4.3.0-beta2.patched/lib/strfunc.c 2013-05-24 09:29:00.0
+0200
| > @@ -182,29 +182,37 @@ char *htmlquoted(char *s)
| > /*
| > * This routine converts a plain string into an html-quoted string
| > */
| 8a9
| > +
| 25c26
| < inp= s;
| ---
| > inp = s;
Kind regards,
Lars
** Patch added: "lk2013-05-24_historybutton_precise.patch"
https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3685569/+files/lk2013-05-24_historybutton_precise.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
[Bug 1103428] Re: Xymon history page does not work
Hi Axel, I can't find Ulric's patch in neither in 4.3.10 and 4.3.11 from http://xymon.sourceforge.net/ nor in 4.3.7-1. They all still contain the bug in strfunc.c: | static strbuffer_t *result = NULL; | char *inp, *endp; | char c; | | if (!result) result = newstrbuffer(4096); | clearstrbuffer(result); Might be the patch was in in for a short time. But they all use /var/lib/xymon and /etc/xymon which is not suitable to the very complex installations of Xymon Servers running Ubuntu 10.04LTS (lucid) and 12.04LTS (precise). Speaking from the Admin's view. They are using /etc/hobbit at the moment, and might loose their whole configuration and data when this is changed withing the stable release. The Bug came in with the 2011-1716 Patch. And should be all affected by this Bug. The buffer result is reused before the code is copied out of it. There are two ways to fix: - One way would be to remove the static. Which was set to prevent memory leaks. When doing this the memory must be freed in the calling functions again, at least when they are used in long running daemons. - Ulric choses the other one. This fixes the bug for a maximum amount of 10 concurrently used arguments, but is aware of producing memory leaks at all. I'm using packages containing a modified Version of Ulric's Patch since 2013-01-29 (some days after Peters post I've put them in my PPA). They does'nt contain the |#if 0 |static strbuffer_t *result = NULL; |#else and the #endif of course. This if IMHO assumes that the fix could be disabled by turning the if to 1, which wouldn't work. I'm sorry I selected the wrong patch file in #22. I'll corect it, now. Kind regards, Lars ** Patch added: "This is what I wanted to post in #22 (Patch for lucid for the patch dir)." https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3685152/+files/lk1103428-lucid_2013-01-29.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Patch from #21 (for lucid) included via debian/patches folder. ** Patch added: "Patch to xymon_4.3.0~beta2.dfsg-5ubuntu0.1 using Patch from #21" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658624/+files/historybutton_lucid4.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Patch from #22 included via debian/patches folder. ** Patch added: "Patch to xymon_4.3.0~beta2.dfsg-9.1ubuntu0.1 using Patch from #22" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658615/+files/historybutton_precise4.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
And here the patch for the ones who only like to have the Increment to 7-CVE-2011-1716, as it is needed for 12.04LTS precise. ** Patch added: "Increment to 7-CVE-2011-1716" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658611/+files/lk1103428-precise_2013-01-29.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
For the ones who only like to have the Increment to 9-CVE-2011-1716, as it is needed for 10.04LTS Lucid. ** Patch added: "Increment to 9-CVE-2011-1716" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658610/+files/lk1103428-lucid_2013-01-29.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
And of course the Lucid patch the should be also posted as Unique Patch. ** Patch added: "Unique Format Patch of historybutton_lucid2.patch" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658589/+files/historybutton_lucid3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Hmm... can't really reproduce this. The history_button2.patch does't really apply because it was an old-style diff -r patch, which seems to be deprecated. But that results in the patch beeing threaded as empty, not in the errors displayed above. My steps are: tar xzf xymon_4.3.0~beta2.dfsg.orig.tar.gz gunzip xymon_4.3.0~beta2.dfsg-9.1ubuntu0.1.diff.gz cd xymon-4.3.0-beta2/ cp ../xymon_4.3.0~beta2.dfsg-9.1ubuntu0.1.diff . patch -p1 < xymon_4.3.0~beta2.dfsg-9.1ubuntu0.1.diff cp ../historybutton_precise3.patch . patch -p1 < historybutton_precise3.patch fakeroot debian/rules clean debuild -us -uc Find the Patch from #15 in Unique Patch Format atached. ** Patch added: "Unique Format Patch of history_button2.patch" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3658555/+files/historybutton_precise3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Here also the one for Lucid. They are to understand as patch for the sourcecode of the last package (4.3.0~beta2.dfsg-5ubuntu0.1) for lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
** Patch added: "Patch for 10.04 LTS (based on Code posted by Ulric Eriksson)" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3505736/+files/historybutton_lucid2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Now I'm running another patch on the "in preparation" machine. It is based on the code you (Ulric Eriksson) provided above. But i've removed the pragma if. Internaly I use 4.3.0~beta2.dfsg-9.1ubuntu0.1-0.3 so don't wonder it has the same version number as the old patch above. It of course replaces the other one. Thank you Ulric, the one for Lucid will follow. ** Patch added: "Patch for 12.04 LTS (based on Code posted by Ulric Eriksson)" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3505697/+files/historybutton_precise2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
But setting the pragma if to 1 would lead to an error beause rn is used below, and not declared any more. So the pragma if should IMHO better be removed, leaving in the fixed code permanently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
> FWIW, here's how I "solved" the problem when I found it. It's ugly, but > running in production and works. Indeed ughly. ;-) The multiple buffers solution with a static counter with a static rolling over counter. Of course this works. Until there is one value not copied out of the buffer until the 10th time htmlqouted is called. When used to preprocess arguments for functions generating html-code this should'nt happen so fast. Then you'll have the wrong arguments in the buffers again. This solves the problem to, and it's of course more a chose your poison question. But I would like to have it as a simple bugfix within the LTS packages. Not inheriting things like "moving configuration to /etc/xymon" which is a real challenge I would like to face on a testing machine when upgrading to 14.04 LTS. And not as a bugfix package within 10.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
This works for me on Ubuntu 12.04 LTS Precise. The htmlquoted funtion comes in via a patch in the debian/patches dir, so patching the patch. ;-) :-( ** Patch added: "Patch for 12.04 LTS" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3505543/+files/historybutton_precise.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Yes, of course. An old C++ chalenge. No automatic free when the last pointer to the dynamicaly allocated memory is removed. :-( Since this is passed as an argument the free if neecessary must come from outside of the function. Other possible solutions should be: - To use mulitple static buffers, identified by a index passed to the function. - Taking the calls out of the argument lists, and copy the buffer imdiately in another one allocated by the function. The first solution is IMHO "very crazy" and when using the second one you'll get a performance increase and shorter code by simply freeing within the function calling "htmlquoted". The code where it is patched in 9-CVE-2011-1716 or 7-CVE-2011-1716 looks like this is only used in the cgi code. I'm running an patched package on an "in preparation" machine with 618 status icons since yesterday approx 14:00h. Memory usage does't look like a memory leak until now. I don't know what workers, channels and the hobbitd or hobbitlaunch should do with this function. Since HTML-Code from the status messages is included in the site and this behavior is widely used as a feature, it does'nt make sense to escape this chars. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-1716 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Now providing, more specific patches for the 10.04 LTS and 12.04 LTS packes. When using this withing daemons, you'll need to look where you can free the buffer again, but since this is only used within the cgi- scripts I did'nt try. We are now using the patched packages and it looks good, until now. ** Patch added: "Patch for 10.04 (lucid) LTS" https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3505496/+files/historybutton_lucid.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Ulric Eriksson on 2013-01-23 wrote: [...] > The bug is fixed in the current version of xymon, so simply upgrading the > version used to build the xymon package in ubuntu > would suffice. [..] I think this is not what I want, since there are some heavy weithed changes in configuration behavior, I don't really want to have as bugfix within a LTS. I can't find any reason for using "result" as a static variable so my suggestion is, to make it a usual local variable. ** Patch added: "Making "result" a usual local variable." https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+attachment/3504374/+files/strcfunc.c-larskoll.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
Yes. It was my mistake. I downgraded the virtual package hobbit. And that of course has not effect. Downgrading the xymon-Package fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103428] Re: Xymon history page does not work
This bug also affects 10.04 (lucid) LTS, but 8.04 (hardy) is not affected yet. The history form looks like this: | | | | | | | Also the macros/variables for the header templates are affected. Most of them are containing the value of &BBHOST. Also in the &BBSVC and &BBIP Macros. >From my point of view this came with the last upgrade to >4.3.0~beta2.dfsg-9.1ubuntu0.1 on 12.04TLS and 4.3.0~beta2.dfsg-5ubuntu0.1 on 10.04 LTS. But I wondered that downgrading did not fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103428 Title: Xymon history page does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1103428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
