[Bug 1933139] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
I seem to have fixed this by adding ConditionPathExists=/etc/fstab ConditionVirtualization=!container to the end of the [Unit] section of /lib/systemd/system/systemd-remount- fs.service. I'm not a maintainer, so this should be reviewed by someone who knows what they are doing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933139 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1933139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933139] [NEW] package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Public bug reported: I was do-release-upgrade of a Bionic container to Focal. When I reboot I have a systemd unit systemd-remount-fs.service. Error:can't find LABEL=cloudimg-rootfs ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 21 14:24:25 2021 ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-21 (0 days ago) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933139 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1933139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865382] [NEW] after pressing 'reboot' no reboot
Public bug reported: After pressing 'reboot' the installer didn't prompt me to remove install medium (USB stick) and didn't reboot. I had to hold down the power button to power off laptop and then restart the laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 1 14:22:13 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-03-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865382 Title: after pressing 'reboot' no reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1865382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702793] Re: Full backport SRU for unattended-upgrades
lukasz, After a kernel update yesterday I can confirmed that the old kernel was removed and the was no reboot today. apt-cache policy unattended-upgrades unattended-upgrades: Installed: 1.1ubuntu1.18.04.7~16.04.1 Candidate: 1.1ubuntu1.18.04.7~16.04.1 Also installed from xenial-proposed: apt-cache policy update-notifier-common update-notifier-common: Installed: 3.168.10 Candidate: 3.168.10 My system: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial tag:verification-done ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702793 Title: Full backport SRU for unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been installed and a reboot was performed, as it should, but today I received no email stating the old kernel had been removed. I expected one. Is this a new bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
@tjaalton My 16.04 server doesn't have update-notifier installed but does have update-notifier-common installed. If I install update-notifier from propose it will install a slew of other packages. If I install update- notifier-common from propose it just installs the new update-notifier- common version 3.168.10. So should i test update-notifier-common instead of update-notifier? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
Brian, On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0. On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should. Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and then rebooted which it shouldn't do. I have attached unattended-upgrades.log for the relevant days. On a side note unattended-upgrades emailed me after it installed the new kernel on Dec 4th, as it should, but did not email me after removing old kernels on Dec 5th. It should have. Let me know if I can provide any other information or do any further testing. My system is Ubuntu 16.04.5 LTS server. Barry ** Attachment added: "unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/5219447/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776012] Re: Sync rkhunter 1.4.6-2 (universe) from Debian unstable (main)
Lukasz, I just installed the proposed version and it ran fine. I didn't see that error message. I will be using this version daily and will let you know if something else pops up, but it seems to be fine. Thanks to all for the work on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776012 Title: Sync rkhunter 1.4.6-2 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/1776012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784191] Re: smartd sends mail before network is up on boot
Andreas, Thanks for your response. I agree with your assessment, this is a corner case. I use ssmtp instead of a MTA because I just want to send an email from a script. As in the case of smartd,I have smartd call my script which sends the test message and also the output of smartctl -H which reports the health of the hard drive. So upon start up I get an email reporting the health of my drives. So this is defiantly a local preference. For completeness I have modified my work around to be more inline with systemd's philosophy. Instead of coping /lib/systemd/system/smartd.service to /etc/systemd/system, I created the directory /etc/systemd/system/smartd.service.d. In that directory I created the file extend.conf with the folowing contents: [Unit] # Added to make sure networking is up before sending mail. # This covers a local corner case during boot. After=network-online.target I wanted to add my change in case someone else had this problem. Thanks again for your help with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784191 Title: smartd sends mail before network is up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1784191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
After a few purges and re-installs I have some insight into this. My goal was to use clamav with Thunderbird's plugin clamrib. In order to do that I need to add to lines two to clamav-daemon.conf. So I thought I needed use dpkg-reconfigure clamav-daemon and pick no for manually configure. That is what added .dpkg.old to extend.conf. So I did a purge and re-install and just added my two lines to clamav-daemon.conf and all is working as expected. According to the first dialog box in dpkg- reconfigure, see the third picture in my attachment notes.txt,I shouldn't have to worry about future upgrades removing my additions to clamav-daemon.conf. As a side note, I tried using dpkg-reconfigure and pick yes to handle the configuration automatically. I picked all the default values until it started looping between the two dialog boxes shown at the top of my attachment. I don't think I need to use dpkg-reconfigure. At this point I'm not sure if I have discovered a bug or just didn't understand what I was doing. In any case thank you for your help and time. ** Attachment added: "Notes.txt" https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+attachment/5170165/+files/Notes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
Andreas, In /etc/systemd/system/clamav-daemon.service.d I have extend.conf.dpkg.old instead of extend.conf. That is where I got the two lines ExecStartPre=-/bin/mkdir /run/clamav ExecStartPre=/bin/chown clamav /run/clamav from. Tjat would explain why i don't have the Drop-in line. The packages I have are ii clamav 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - command-line interface ii clamav-base0.100.1+dfsg-1ubuntu0.18.04.2 all anti-virus utility for Unix - base package ii clamav-daemon 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - scanner daemon ii clamav-freshclam 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - virus database update utility ii libclamav7:amd64 0.100.1+dfsg-1ubuntu0.18.04.2 amd64anti-virus utility for Unix - library Which appear to be the same as yours. Looking in /var/log/apt/term file I see the line id:'clamav': no such user, but no other errors. I would be glad to uninstall and re-install to see if /etc/systemd/system/clamav-daemon.service/extend.conf.dpkd.old has the right file name if you like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] Re: clamav-daemon fails to start
I was able to fix this by copying /lib/systemd/system/clamav-daemon.service to /etc/systemd/system/clamav.service and adding the two lines: ExecStartPre=-/bin/mkdir /run/clamav ExecStartPre=/bin/chown clamav /run/clamav to the top of the [Service] section. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784193] [NEW] clamav-daemon fails to start
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy clamav clamav: Installed: 0.100.1+dfsg-1ubuntu0.18.04.2 Expected clamav-daemon to be running. What happens: clamav-daemon fails to start sudo systemctl status clamav-daemon ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2018-07-28 19:53:14 CDT; 6s ago Docs: man:clamd(8) man:clamd.conf(5) https://www.clamav.net/documents/ Process: 3589 ExecStart=/usr/sbin/clamd --foreground=true (code=exited, status=1/FAILURE) Main PID: 3589 (code=exited, status=1/FAILURE) Jul 28 19:53:04 Bionic-Desktop systemd[1]: Started Clam AntiVirus userspace daemon. Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !LOCAL: Could not create socket directory: /var/run/clamav: Permission denied Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !LOCAL: Socket file /var/run/clamav/clamd.ctl could not be bound: No such file or directory Jul 28 19:53:14 Bionic-Desktop clamd[3589]: Sat Jul 28 19:53:14 2018 -> !Can't unlink the socket file /var/run/clamav/clamd.ctl Jul 28 19:53:14 Bionic-Desktop systemd[1]: clamav-daemon.service: Main process exited, code=exited, status=1/FAILURE Jul 28 19:53:14 Bionic-Desktop systemd[1]: clamav-daemon.service: Failed with result 'exit-code'. What other information can I provide? ** Affects: clamav (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/1784193 Title: clamav-daemon fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1784193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784191] [NEW] smartd sends mail before network is up on boot
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy smartmontools smartmontools: Installed: 6.5+svn4324-1 Candidate: 6.5+svn4324-1 Version table: *** 6.5+svn4324-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior: smartd sends a test email on boot. What happens: No mail is recieved. sSMTP logs "Unable to locate Mail server" and "cannot open mailserver:25". I'm using the same smartd.conf and my script smartd calls that I used on 14.04, which worked flawlessly. Work around: I had my script sleep 5 seconds before sending the mail. This worked fine leading me to believe smartd is calling my script before networking is up. But this is not an elegant solution. So I copied /lib/systemd/system/smartd.service to /etc/systemd/system/smartd.service and add the line "After=network-online.target"This worked fine. So the full smartd.sevice unit is: [Unit] Description=Self Monitoring and Reporting Technology (SMART) Daemon Documentation=man:smartd(8) man:smartd.conf(5) After=network-online.target [Service] EnvironmentFile=-/etc/default/smartmontools ExecStart=/usr/sbin/smartd -n $smartd_opts ExecReload=/bin/kill -HUP $MAINPID StandardOutput=syslog [Install] WantedBy=multi-user.target I haven't got any other machines to test this on. So I hope the report will help some one else ** Affects: smartmontools (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/1784191 Title: smartd sends mail before network is up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1784191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783632] Re: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled"
Marc, I manually changed clamd.conf. There was no indication from the installer that there was any changes to clamd.conf. The only indication I had was when the Thunderbird extension, clamrib, complained it couldn't connect to clamd. I checked clamd and indeed it was not running. I tried to restart it using the System V init script. It complained about an unknown option StatsEnabled. So I commented out StatsEnabled. and tried to start clamd. It compained about the option StatsTimeout. So I commented it out and repeated this process until clamd started. Releasing an update warning about changes for user modified clamd.conf should be a good solution. Thanks for the prompt work on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783632 Title: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1783632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783632] Re: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled"
I can confirm this in 14.04.5 Trusty. Attached is the apt log /var/log/apt/term. A quick work around was to comment out these lines in /etc/clamav/clamd.conf #StatsEnabled false #StatsPEDisabled true #StatsHostID auto #StatsTimeout 10 As a side note, I use the Thunderbird extension clamrib to scan my emails. Clamrib requires these lines in /etc/clamav.clamd.conf TCPSocket 3310 TCPAddr localhost I have these lines added at the bottom of clamd.conf. I'm not sure if this had anything to do with the bug but include it for completeness. ** Attachment added: "/var/log/apt/term" https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1783632/+attachment/5168104/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783632 Title: clamav-daemon won't start after upgrade to 0.100.1+dfsg, complaining of "Unknown option StatsEnabled" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1783632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589508] Re: New mail notification no longer plays sound in Trusty
G, It works now. This issue can be closed. Barry ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589508 Title: New mail notification no longer plays sound in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1589508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733857] Re: package lxcfs 2.0.8-0ubuntu1~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Stéphane, It installed correctly just now. Thanks for the quick response. Barry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733857 Title: package lxcfs 2.0.8-0ubuntu1~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1733857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733857] [NEW] package lxcfs 2.0.8-0ubuntu1~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This happened on a normal update. This was a automatic bug report. Barry ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lxcfs 2.0.8-0ubuntu1~14.04.1 ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39 Uname: Linux 3.13.0-135-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Wed Nov 22 06:42:55 2017 DuplicateSignature: package:lxcfs:2.0.8-0ubuntu1~14.04.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1313 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: lxcfs Title: package lxcfs 2.0.8-0ubuntu1~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxcfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733857 Title: package lxcfs 2.0.8-0ubuntu1~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1733857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] Re: After rebooting for updates, reboot is still required.
And the after autoremove log ** Attachment added: "after_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760020/+files/after_history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] Re: After rebooting for updates, reboot is still required.
Brian, Yesterday we had kernel updates. My server, which is set to automatically reboot, reboot fine and no /var/run/reboot-required. This morning there was no second reboot, so everything was as expected. The I ran autoremove to remove the stale kernel. Then I had /var/run/reboot- required and /var/run/reboot-required.pkgs contained linux-base. So I wouldn't think removing a kernel should require a reboot. So is this a bug or am I not understand how this should work? I confirmed this on a second 16.04 server Attached are the /var/log/apt/history.logs from before autoremove and after. ** Attachment added: "before_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760019/+files/before_history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] Re: After rebooting for updates, reboot is still required.
Brian, This weekend we had updates for libssl and a libssl regression. Both required a reboot and no second reboot. In other words worked as expected. Perhaps the bug only occurs for kernel updates. I have had this happen a few times in the past. So the next time it happens I will not run autoremove manually, to see what happens. What files and logs can I provide at that time that will help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] Re: After rebooting for updates, reboot is still required.
Brian, I don't have that file as it was removed by the reboot, but I do believe it said "Linux base", same as the day before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] Re: After rebooting for updates, reboot is still required.
Brian, File attached. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4746383/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626345] [NEW] After rebooting for updates, reboot is still required.
Public bug reported: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: reboot ** Attachment added: "apport.unattended-upgrades.x41_ij8b.apport" https://bugs.launchpad.net/bugs/1626345/+attachment/4745785/+files/apport.unattended-upgrades.x41_ij8b.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot
Can't seem to edit my own post. Disregard the last paragraph about reboot-required, I need to look into that a little further, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541730 Title: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot
I have noticed this too, at least with logrotate not running. I thought this was because the reboot happens right after, or during, unattended-upgrades. So I set the time to reboot to 7:30 AM in /etc/apt/apt.conf/50unattended-upgrades to give the rest of cron.daily time to run. However logrotate still did not run. And I assume neither did the rest of cron.daily. I believe unattended-upgrades issues shutdown -r 07:30 in my case. So I wondered if the impending shutdown was blocking logrotate, and the rest of cron.daily. However searching the Internet I could not confirm that theory. So I too think cron.daily/apt should be the last thing run in cron.daily. One more issue that may be related. After the reboot /var/run/reboot-required and /var/run/reboot-required.pkgs still exist and the "*System restart required" message appearers at logoin. ** Attachment added: "Apport report and 50unatended-upgrades file" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+attachment/4692505/+files/apport.unattended-upgrades.fttw5049.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541730 Title: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589508] [NEW] New mail notification no longer plays sound in Trusty
Public bug reported:
New mail sound no longer plays. Navigating, in Thunderbird, to
Edit->Preferences on the General tab in the "When new message arrive:" section,
hitting the play button produces no sound. If I select "Use the following sound
file" and browse to /usr/share/sounds/ubuntu/stereo/message.ogg and hit play
still no sound. If, using the file manager, I navigate to
/usr/share/sounds/ubuntu/stereo/message.ogg and double click the file it does
play a sound, so the sound system does work outside of Thunderbird. Also today
I noticed the envelope in the notification area is not turning blue on a new
mail.
Running Thunderbird in safe-mode does not solve the problem.
If I can provide any other information please let me know.
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunderbird 1:38.8.0+build1-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
Uname: Linux 3.13.0-87-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: barry 2242 F pulseaudio
/dev/snd/controlC1: barry 2242 F pulseaudio
BuildID: 20160511162442
Channel: Unavailable
CurrentDesktop: Unity
Date: Mon Jun 6 08:11:17 2016
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2014-04-18 (779 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IpRoute:
default via 192.168.0.1 dev eth0 proto static
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2 metric 1
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=38.8.0/20160511162442 (In use)
RelatedPackageVersions:
browser-plugin-lightspark 0.7.2-3ubuntu1
totem-mozilla 3.10.1-1ubuntu4
rhythmbox-mozilla 3.0.2-0ubuntu2
RfKill:
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0703
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/28/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589508
Title:
New mail notification no longer plays sound in Trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1589508/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581892] [NEW] Download fails on already athenticated site
Public bug reported: I have a personal website that I use Apache's AuthType Basic to authenticate. >From my phone ( Nexas 4 Mako OTA10 ) I can access the page and login OK. When >I download a file I get a HttpError: 401-Unathorized. More in depth: When I press the "GetFile" link Apache logs (in access.log): 192.168.0.67 - barry [14/May/2016:17:47:11 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 154936 "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" On my phone the the Download Dialog pops up and I press download apache logs 192.168.0.67 - - [14/May/2016:17:47:33 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 401 728 "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" The difference is the first has my user name "barry" in it and the second doesn't. In comparison when doing the same thing from my desktop (14.04) and FireFox Apache logs 192.168.0.2 - barry [14/May/2016:18:04:49 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 492086 "http://192.168.0.101/briefcase/index.php?tab=search; "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0" and displays the "What should FireFox do with this file" dialog and Apache logs nothing further. On my phone this behavior is the same whether I press "Download" or "Choose an application" from the Download dialog. Also if I long press the link and choose "Save link" the download fails also. When I tried to download a file from a commercial site I have to log into, the download succeeded. I suspect the difference is the commercial site probably uses something beside "AuthType Basic". I'm happy to provide any logs or to do more testing. Thanks ** Affects: webbrowser-app (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/1581892 Title: Download fails on already athenticated site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1581892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265402] Re: Trying to install saucy on a kvm vm. always crashes installing the bootloader.
I found this on the Archwiki
https://wiki.archlinux.org/index.php/Btrfs#GRUB
Missing root
Users experiencing the following: error no such device: root when
booting from a RAID style setup then edit /usr/share/grub/grub-
mkconfig_lib and remove both quotes from the line echo search --no-
floppy --fs-uuid --set=root ${hints} ${fs_uuid}. Regenerate the config
for grub and the system should boot without an error.
From the Saucy live-cd i used gparted to create the files system with
/dev/vda1 btrfs and swap on /dev/vda and /dev/vdb1 btrfs o /dev/vdb. I
set /dev/vda as the boot device. I then exited gparted and opened a
terminal and ran
sudo mkfs.btrfs -L RAID1 -m raid1 -d raid1 /dev/vda1 /dev/vdb1
sudo btrfs device scan
I then exited the terminall and installed Saucy. When the partitioner
starts chose Something else. Mount / on /dev/vda1 but do not format or
you will destroy the raid. When the installer complains it can't install
the boot loader choose Continue without installing boot loader.
When the installer is through, click on Continue to try rather than
restart. Open up a terminal and
sudo mount /dev/vda1 /mnt
sudo gedit
When gedit launches navigate to/usr/share/grub and open grub-mkconfig_lb
and remove the quotes from
echo search --no-floppy --fs-uuid --set=root ${hints} ${fs_uuid}
save the file and exit gedit. Now back in the terminal type
sudo grub-install --root-directory=/mnt/@ /dev/vda
/mnt/@ because the Saucy installer mount / on subvolume @ and mounts
/home on subvolume @home.
When that is done you should be able to reboot into the system.
I'm using /dev/vda instaed of /dev/sda because I installed this on a KVM
virtual machine. Also this is my first experience with btrfs and
installing Grub from scratch and post my experience as maybe helpful in
fixing Ubiquity.
Barry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265402
Title:
Trying to install saucy on a kvm vm. always crashes installing the
bootloader.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1265402/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265402] Re: Trying to install saucy on a kvm vm. always crashes installing the bootloader.
I've been trying to install grub2 manually but no luck. This is the first time I have tried to install grub2 manually so I'm no grub expert. However I have changed my filesystem from btrfs to ext4 mounting / on one disk and /home on the other and it installs flawlessly. So it must have something to do with btrfs. The installer does create a subvolume for / called @ and a subvolume for /home called @home. I think this is where I was having trouble with grub and possibly this is where the installer was having trouble. Hope this helps, Barry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265402 Title: Trying to install saucy on a kvm vm. always crashes installing the bootloader. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1265402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265402] [NEW] Trying to install saucy on a kvm vm. always crashes installing the bootloader.
Public bug reported: Trying to install Saucy on a KVM vm. The filesystem is /vda1 mounted on /boot, vda2 and vdb1 ate btrfs raid1 swap is on vda. Installer always says it can't install bootloader on vda, pick another device. But no device works. I'v tried many time with different configurations of the virtual disks, always ends the same. Thanks, Barry ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.26 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Date: Wed Jan 1 19:19:46 2014 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubiquity-2.15.26 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265402 Title: Trying to install saucy on a kvm vm. always crashes installing the bootloader. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1265402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265087] [NEW] Suacy install fails to install bootloader
Public bug reported: I'v been trying to install Saucy on a btrfs file system. This latest attemp was with /boot mounted on vda1 ext2. I previously have tried to install to btrfs raid1 made up from /dev/vda1 and /dev/vb1. I'm not sure if the problem is with btrfs or kvm. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity 2.15.26 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CasperVersion: 1.336ubuntu1 Date: Mon Dec 30 17:20:43 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubiquity-2.15.26 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265087 Title: Suacy install fails to install bootloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1265087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378200] Re: collectd's sensor plugin not loading
** Description changed: Binary package hint: collectd lsb_release -rd Description: Ubuntu 8.04.2 Release: 8.04 uname -a Linux wu 2.6.24-23-server #1 SMP Wed Apr 1 22:14:30 UTC 2009 x86_64 GNU/Linux apt-cache policy collectd collectd: Installed: 4.3.0-1 Candidate: 4.3.0-1 Version table: *** 4.3.0-1 0 500 http://us.archive.ubuntu.com hardy/universe Packages 100 /var/lib/dpkg/status Problem: collectd -t -C /etc/collectd/collectd.conf lt_dlopen failed: libsensors.so.3: cannot open shared object file: No such file or directory Unable to load plugin sensors. locate sensors.so /usr/lib/libsensors.so.4 /usr/lib/libsensors.so.4.0.0 /usr/lib/collectd/sensors.so Collectd is looking for libsensors.so.3 but libsensors.so.4 is installed on this machine with lm-sensors so the sensors plugin does not work. It does not create a sensors directory in the RRD directory so it doesn't collect any statistics Please contact me if you need some more information. Thanks, Barry + + Updated information: + + Upon further investigation I discovered on my 32 bit Hardy I have both + libsensors.so.3 and libsensors.so.4 + + uname -a + Linux test-server 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i586 GNU/Linux + + lsb_release -rb + Description: Ubuntu 8.04.2 + Release: 8.04 + + locate sensors.so + /usr/lib/libsensors.so.3 + /usr/lib/libsensors.so.3.1.4 + /usr/lib/libsensors.so.4 + /usr/lib/libsensors.so.4.0.0 + /usr/lib/collectd/sensors.so + + Apparently my 32 bit, which started out at version 8.04 and upgraded to + 8.04.2, updated to libsensors.so.4 and my 64 bit which started at + version 8.04.2 never had libsensors.so.3. + + So is it possibly to have the package updated to a newer version of + collectd? If possibly could collectd be upgraded to a version that + includes the Notify Email plugin? According to collectd website Notfiy + Email was introduced in version 4.5. I realize I could compile the + newest version myself but I prefer to use deb packges for Ubuntu to keep + things 'tidy'. Unfortunately I am still new enough at this that I don't + know how to make my own deb packages yet. + + Thanks, + Barry -- collectd's sensor plugin not loading https://bugs.launchpad.net/bugs/378200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 378200] [NEW] collectd's sensor plugin not loading
Public bug reported: Binary package hint: collectd lsb_release -rd Description:Ubuntu 8.04.2 Release:8.04 uname -a Linux wu 2.6.24-23-server #1 SMP Wed Apr 1 22:14:30 UTC 2009 x86_64 GNU/Linux apt-cache policy collectd collectd: Installed: 4.3.0-1 Candidate: 4.3.0-1 Version table: *** 4.3.0-1 0 500 http://us.archive.ubuntu.com hardy/universe Packages 100 /var/lib/dpkg/status Problem: collectd -t -C /etc/collectd/collectd.conf lt_dlopen failed: libsensors.so.3: cannot open shared object file: No such file or directory Unable to load plugin sensors. locate sensors.so /usr/lib/libsensors.so.4 /usr/lib/libsensors.so.4.0.0 /usr/lib/collectd/sensors.so Collectd is looking for libsensors.so.3 but libsensors.so.4 is installed on this machine with lm-sensors so the sensors plugin does not work. It does not create a sensors directory in the RRD directory so it doesn't collect any statistics Please contact me if you need some more information. Thanks, Barry ** Affects: collectd (Ubuntu) Importance: Undecided Status: New -- collectd's sensor plugin not loading https://bugs.launchpad.net/bugs/378200 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
