[Bug 1785351] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I'm not sure why I received this error, but it could be because I'm running btrfs-tools v4.17. (I'm running btrfs on imsm mdadm raid1.) The btrfs hooks script has this line in it: copy_exec /bin/btrfs-zero-log but this program isn't a part of btrfs-progs anymore, replaced by "btrfs rescue zero-log" Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.17.4-041704-generic E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-4.17.4-041704-generic with 1. dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for menu (2.1.47ubuntu1.16.04.1) ... Errors were encountered while processing: initramfs-tools ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.11 Uname: Linux 4.17.4-041704-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Aug 3 20:52:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-30 (795 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785351 Title: package initramfs-tools 0.122ubuntu8.11 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/initramfs-tools/+bug/1785351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Hi Dimitri, > On Feb 22, 2018, at 8:32 AM, Dimitri John Ledkov <launch...@surgut.co.uk> > wrote: > > john-center - I believe mdadm is used by default, instead of dmraid. > However, I'm not sure if we do correctly activate Intel Raids with > mdadm. I have not done an install with either 16.04 or 18.04. Or I guess > at least start the install up to the partitioning screen. My expectation > is, if one has raid arrays pre-setup in BIOS (ctrl+I on boot) already, > they should show up as assembled and offered to be autopartitioned. With > both 16.04 and 18.04. > I know with 16.04 it wasn’t used by default. I had to do a lot of manipulation to set up the raid array before I could do the install. It used dmraid once it detected the imsm raid. I removed dmraid completely, then installed mdadm, assembled the array & ran the installation program again. I was hoping that mdadm would just do it all instead. -John > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1587142 > > Title: > Shutdown hangs in md kworker after "Reached target Shutdown." > > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I'm booting a fully patched 16.04 from an Intel Rapid Storage > Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA > ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). > > If the RAID volume is recovering or resyncing for whatever reason, then > `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to > `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in > order to consistently get that). However, once the recovery/resync is > complete and clean, the reboot and poweroff commands above hang forever after > "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand > (suggested in the bug #1464917) does not help. > [EDIT]Actually, the shutdown also hangs from time to time during a resync. > But I've never seen it succeed once the resync is complete.[/EDIT] > > Then, if the server has been forcibly restarted with the power button, > the Intel Matrix Storage Manager indicates a "Normal" status for the > RAID1 volume, but Ubuntu then resyncs the volume anyway: > > [1.223649] md: bind > [1.228426] md: bind > [1.230030] md: bind > [1.230738] md: bind > [1.232985] usbcore: registered new interface driver usbhid > [1.233494] usbhid: USB HID core driver > [1.234022] md: raid1 personality registered for level 1 > [1.234876] md/raid1:md126: not clean -- starting background > reconstruction > [1.234956] input: CHESEN USB Keyboard as > /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 > [1.236273] md/raid1:md126: active with 2 out of 2 mirrors > [1.236797] md126: detected capacity change from 0 to 1000202043392 > [1.246271] md: md126 switched to read-write mode. > [1.246834] md: resync of RAID array md126 > [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. > [1.247503] md126: p1 p2 p3 p4 > [1.248269] md: using maximum available idle IO bandwidth (but not more > than 20 KB/sec) for resync. > [1.248774] md: using 128k window, over a total of 976759940k. > > Note that the pain of "resync upon every (re)boot" cannot even be a > bit relieved thanks to bitmaps because mdadm does not support them for > IMSM containers: > > $ sudo mdadm --grow --bitmap=internal /dev/md126 > mdadm: Cannot add bitmaps to sub-arrays yet > > I also get this in syslog during boot when the individual drives are > detected, but this seems to be harmless: > > May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm > --incremental /dev/sdb --offroot' failed with exit code 1. > May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed > with exit code 1. > > May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm > --incremental /dev/sda --offroot' failed with exit code 1. > May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed > with exit code 1. > > During a resync, `sudo sh -c 'echo idle > > /sys/block/md126/md/sync_action'` actually stops it as expected, but > it restarts immediately though nothing seems to have triggered it: > > May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. > May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of > md126. > May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 > May 30 18:17:02 wssrv1 kernel: [ 3106.8
[Bug 1608495] Re: IMSM fakeraid handled by mdadm: unclean mounted volumes on shutdown/reboot
I don't think it's used by default for IMSM raid installation. That's why your devices were likely set up by dmraid first. When you mentioned in a previous comment about installing dracut-core, this automatically installs dmraid with kpartx. Mdadm never gets involved. When I've manually installed mdadm for IMSM raid, I first remove dmraid. That's the only way I was able to install Ubuntu 16.04 on top of IMSM raid1 via mdadm reliably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608495 Title: IMSM fakeraid handled by mdadm: unclean mounted volumes on shutdown/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I added a comment about this new fix on https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495. One thing I wanted to add here, for the first time shutdown completed successfully. In fact, I was a little startled when it happened. :-) It powered off at the end of shutdown, instead of hanging at the "Reached target Shutdown" message. One question: Does this mean that Ubuntu 18.04 will use mdadm by default during installation instead of dmraid? I really hope so. It's a real pain to do it manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1587142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608495] Re: IMSM fakeraid handled by mdadm: unclean mounted volumes on shutdown/reboot
I saw this fix & installed it before your update went out. I did it by
hand, so I didn't know about the dracut-core package or
enabling/starting the mdadm-shutdown.service. Even without dracut-core,
it worked for me.
I did make some changes to 64-md-raid-assembly.rules. I commented out
the ENV{ANACONDA}=="?*", GOTO="md_inc_end" line, because I didn't think
this applied to Ubuntu. I also made the following change:
ACTION=="add|change", IMPORT{program}="/sbin/mdadm --incremental
--export $devnode --offroot $env{DEVLINKS}"
I saw this was updated on the linux-raid list:
[PATCH 2/4] Use correct syntax for passing DEVLINKS to mdadm from udev
I also did 2 reboots & everything seems to be working correctly. One
question: Does this mean that Ubuntu 18.04 will use mdadm by default
during installation instead of dmraid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1608495
Title:
IMSM fakeraid handled by mdadm: unclean mounted volumes on
shutdown/reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320402] Re: mdadm resyncs imsm raid in "Normal" state
Since I upgraded to 16.04, the mdadm resync has started again. How do these changes map to the new systemd configuration? What is the process that systemd uses to start up mdadm? Will this change going forward to 16.10, etc.? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320402 Title: mdadm resyncs imsm raid in "Normal" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570227] Re: Open Recent Items show as always empty in Gedit
I've had the same problem since upgrading to 16.04. It looks like the dropdown list from the Open tab is showing the recent files, but not the File->Open Recent menu item. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570227 Title: Open Recent Items show as always empty in Gedit To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1570227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1028677] Re: mdadm should be used for fakeraid (instead of dmraid)
Here are a set of notes I made for myself because I did this often
enough I didn't want to forget. I hope this helps.
-John
New procedure for using Ubuntu Desktop installer (until they fix it)
1) Launch UEFI setup at startup:
* Disable Legacy BIOS
* Turn on RAID & SMART
2) Boot Ubuntu CD:
1) Pick "Try Ubuntu" & edit kernel command line.
2) Add "nodmraid" to kernel line to prevent dmraid from
assembling the disks.
3) Hit F10 to start session.
3) Start 2 terminals & increase scrolling buffer.
4) sudo to root in one of the windows.
5) Do the following before starting installation:
1) apt-get purge dmraid
2) apt-get install mdadm
3) mdadm --assemble --scan --verbose
6) Partition the raid drive:
1) gdisk /dev/md126
1G EFI partition (EF00)
1T EXT4 partition (FD00) <-- change md126p2 to type FD00
128G swap partition (8200)
600G NTFS partition (0700)
7) Do the following before starting installation:
1) apt-get install grub-efi-amd64
2) apt-get update
apt-get upgrade
8) Run installer until it fails on bootloader.
9) Mount & chroot raid disk:
1) mkdir /target (if not still mounted)
2) mount /dev/md126p2 /target
3) mount /dev/md126p1 /target/boot/efi
4) for i in /dev /dev/pts /proc /sys /run; do mount -B $i
/target$i; done
5) chroot /target
10) Do the following again on the chroot volume:
apt-get purge dmraid
apt-get install mdadm
apt-get install grub-efi-amd64
apt-get update
apt-get upgrade
11) Run grub-install to fix the bootloader:
* grub-install --boot-directory=/boot --bootloader-id=ubuntu
--target=x86_64-efi --efi-directory=/boot/efi --recheck
[--verbose|--debug] /dev/md126
12) Unmount the raid disk:
* for i in /dev /dev/pts /proc /sys /run; do umount /target$i;
done
* umount /target/boot/efi
umount /target/boot
13) Find all the places that may try to stop mdadm/mdmon from starting &
disable them:
* find /etc -name "*" -type f -exec grep 'nomdmonisw' {} \; -print
* find /lib -name "*" -type f -exec grep 'nomdmonisw' {} \; -print
* find /usr -name "*" -type f -exec grep 'nomdmonisw' {} \; -print
* Comment out dmraid2mdadm.cfg at /etc/default/grub.d/
14) Fix up the mdadm configuration:
* cp /lib/udev/rules.d/63-md-raid-arrays.rules /etc/udev/rules.d/
* cp /lib/udev/rules.d/64-md-raid-assembly.rules /etc/udev/rules.d/
* cp /usr/share/initramfs-tools/hooks/mdadm /etc/initramfs-tools/hooks/
* cp /usr/share/initramfs-tools/scripts/mdadm-functions
/etc/initramfs-tools/scripts/
* Edit rules if need be.
* See mdadm.patch file from bug# 1320402 & fix up files.
* Create /etc/initramfs-tools/conf.d/mdadm:
## mdadm boot_degraded configuration
##
BOOT_DEGRADED=true
* Create /boot/efi/EFI/ubuntu/grub.cfg:
search.fs_uuid 9b5a6959-7df1-4455-a643-d369487d24aa root
set prefix=($root)'/@/boot/grub'
configfile $prefix/grub.cfg
* update-grub
15) reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028677
Title:
mdadm should be used for fakeraid (instead of dmraid)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1028677/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
** Attachment added: "IMG_0766.JPG" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4537645/+files/IMG_0766.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'
My Dell workstation is a fresh install of 15.04, also. I'm having the same problem. I've attached some screen shots that show the last messages typically seen after I try REISUB. ** Attachment added: "IMG_0765.JPG" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4537644/+files/IMG_0765.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464917 Title: reboot hangs at 'Reached target Shutdown' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482268] [NEW] 15.04 Installer crashes, can't handle mdadm imsm raid1
Public bug reported: Using the desktop installer, had to manually purge dmraid install mdadm with the grub-efi support. This always fails on the bootloader. Please fix this, we don't need dmraid for IMSM, only mdadm! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubiquity 2.21.25 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 Date: Thu Aug 6 11:36:51 2015 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper nodmraid quiet splash --- LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) ProcEnviron: PATH=(custom, no user) 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 ubiquity-2.21.25 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482268 Title: 15.04 Installer crashes, can't handle mdadm imsm raid1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1482268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478686] [NEW] 15.04 installer crashed installing to uefi IMSM raid1
Public bug reported: Installing 15.04 on UEFI IMSM raid1 system (2TB disks). At the end, the installer crashed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubiquity 2.21.25 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 Date: Mon Jul 27 16:07:29 2015 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper nodmraid quiet splash --- LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) ProcEnviron: PATH=(custom, no user) 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 ubiquity-2.21.25 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1478686 Title: 15.04 installer crashed installing to uefi IMSM raid1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1478686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186662] Re: isc-dhcp-server fails to renew lease file
There are a number of things that need to be addressed with the isc-
dhcp-server package. I think I've worked through most of the issues,
based on items here ones I've researched; maybe the maintainer or
someone else could review this?
1) /etc/default/isc-dhcp-server needs to be updated to enable several
env variables include one more:
diff -Nru /etc/default/isc-dhcp-server isc-dhcpd-4.2.4/isc-dhcp-server.default
--- /etc/default/isc-dhcp-server2015-06-19 17:32:49.849591118 -0400
+++ isc-dhcpd-4.2.4/isc-dhcp-server.default 2015-06-19 17:17:36.537576347
-0400
@@ -7,10 +7,13 @@
#
# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
-#DHCPD_CONF=/etc/dhcp/dhcpd.conf
+DHCPD_CONF=/etc/dhcp/dhcpd.conf
+
+# Path to dhcpd's leases file (default: /var/lib/dhcp/dhcpd.leases).
+DHCPD_LEASES=/var/lib/dhcp/dhcpd.leases
# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
-#DHCPD_PID=/var/run/dhcpd.pid
+DHCPD_PID=/var/run/dhcp-server/dhcpd.pid
# Additional options to start dhcpd with.
# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
@@ -18,4 +21,4 @@
2) /etc/init/isc-dhcp-server.conf sources the default isc-dhcp-server file,
but does not include the correct env variable to find dhcpd.conf. It should
also set the extended file attributes as mentioned earlier. Finally, it should
use the env variables defined in the default isc-dhcp-server file when starting
the service:
diff -Nru /etc/init/isc-dhcp-server.conf
isc-dhcpd-4.2.4/isc-dhcp-server.conf.init
--- /etc/init/isc-dhcp-server.conf 2014-04-03 17:51:15.0 -0400
+++ isc-dhcpd-4.2.4/isc-dhcp-server.conf.init 2015-06-19 18:38:04.661654434
-0400
@@ -13,22 +13,17 @@
fi
. /etc/default/isc-dhcp-server
-if [ -f /etc/ltsp/dhcpd.conf ]; then
-CONFIG_FILE=/etc/ltsp/dhcpd.conf
-else
-CONFIG_FILE=/etc/dhcp/dhcpd.conf
-fi
-if [ ! -f $CONFIG_FILE ]; then
-echo $CONFIG_FILE does not exist! - Aborting...
-echo Please create and configure $CONFIG_FILE to fix the problem.
+if [ ! -f $DHCPD_CONF ]; then
+echo $DHCPD_CONF does not exist! - Aborting...
+echo Please create and configure $DHCPD_CONF to fix the problem.
stop
exit 0
fi
-if ! dhcpd -user dhcpd -group dhcpd -t -q -4 -cf $CONFIG_FILE /dev/null
21; then
+if ! dhcpd -user dhcpd -group dhcpd -t -q -4 -cf $DHCPD_CONF /dev/null
21; then
echo dhcpd self-test failed. Please fix the config file.
echo The error was:
-dhcpd -user dhcpd -group dhcpd -t -4 -cf $CONFIG_FILE
+dhcpd -user dhcpd -group dhcpd -t -4 -cf $DHCPD_CONF
stop
exit 0
fi
@@ -36,12 +31,6 @@
respawn
script
-if [ -f /etc/ltsp/dhcpd.conf ]; then
-CONFIG_FILE=/etc/ltsp/dhcpd.conf
-else
-CONFIG_FILE=/etc/dhcp/dhcpd.conf
-fi
-
. /etc/default/isc-dhcp-server
# Allow dhcp server to write lease and pid file as 'dhcpd' user
@@ -50,10 +39,8 @@
# The leases files need to be root:root even when dropping privileges
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases
-chown root:root /var/lib/dhcp /var/lib/dhcp/dhcpd.leases
-if [ -e /var/lib/dhcp/dhcpd.leases~ ]; then
-chown root:root /var/lib/dhcp/dhcpd.leases~
-fi
+setfacl -dm u:dhcpd:rwx /var/lib/dhcp
+setfacl -m u:dhcpd:rwx /var/lib/dhcp
-exec dhcpd -user dhcpd -group dhcpd -f -q -4 -pf
/run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES
+exec dhcpd -user dhcpd -group dhcpd -f -4 $OPTIONS -pf $DHCPD_PID -cf
$DHCPD_CONF -lf $DHCPD_LEASES $INTERFACES
end script
3) Checks for upstart should be added to the sysvinit script:
diff -Nru /etc/init.d/isc-dhcp-server isc-dhcpd-4.2.4/isc-dhcp-server.initd
--- /etc/init.d/isc-dhcp-server 2014-04-03 17:51:15.0 -0400
+++ isc-dhcpd-4.2.4/isc-dhcp-server.initd 2015-06-19 18:20:49.873637698
-0400
@@ -31,6 +31,13 @@
. /lib/lsb/init-functions
+check_for_upstart()
+{
+ if init_is_upstart; then
+ exit $1
+ fi
+}
+
# Read init script configuration
[ -f $DHCPD_DEFAULT ] . $DHCPD_DEFAULT
@@ -38,15 +45,18 @@
DESC=ISC DHCP server
# fallback to default config file
DHCPD_CONF=${DHCPD_CONF:-/etc/dhcp/dhcpd.conf}
-# try to read pid file name from config file, with fallback to
/var/run/dhcpd.pid
+# try to read pid file name from config file, with fallback to
+/var/run/dhcpd.pid
if [ -z $DHCPD_PID ]; then
- DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*(.*)[
\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
+ DHCPD_PID=$(sed -n -e 's/^[ \t]*pid-file-name[ \t]*\(.*\)[
+\t]*;.*$/\1/p' $DHCPD_CONF 2/dev/null | head -n 1)
fi
DHCPD_PID=${DHCPD_PID:-/var/run/dhcpd.pid}
test_config()
{
- if ! /usr/sbin/dhcpd -t $OPTIONS -q -cf $DHCPD_CONF /dev/null 21;
then
+ if ! /usr/sbin/dhcpd -t $OPTIONS -q -cf $DHCPD_CONF /dev/null 21;
+then
[Bug 1186662] Re: isc-dhcp-server fails to renew lease file
We're having the same problem running dhcpd under trusty. As a workaround, if we make the file attribute changes in #25, is this the only thing that needs to be done? Can we also change chown root:root to dhcpd:dhcpd for /var/lib/dhcp/* in isc-dhcp-server.conf, too? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368688] Re: Inconsistence between /etc/init and /etc/init.d files
This just bit us, also. We migrated from Solaris to Ubuntu 14.04 for our dhcp server. Please fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368688 Title: Inconsistence between /etc/init and /etc/init.d files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1368688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424747] Re: findmnt only displays /dev/pts on Trusty w/ Utopic Kernel (14.04.2)
Hi, I've been trying to build snapper on 14.04 x64, but the old version of util-linux is tripping me up. I get the following error: In file included from Btrfs.cc:34:0: /usr/include/libmount/libmount.h:345:28: error: expected ',' or '...' before 'new' struct libmnt_table *new); ^ Btrfs.cc: In constructor 'snapper::MntTable::MntTable()': Btrfs.cc:1386:40: error: 'mnt_table_enable_comments' was not declared in this scope mnt_table_enable_comments(table, 1); ^ Btrfs.cc: In member function 'void snapper::MntTable::replace_file()': Btrfs.cc:1402:52: error: 'mnt_table_replace_file' was not declared in this scope if (mnt_table_replace_file(table, /etc/fstab) != 0) ^ The old version of libmount.h using the C++ keyword new as a variable name. This was fixed in the upstream version 2.22.1 of util-linux. It looks like a later version of util-linux is available for Utopic. Please backport this to Trusty. Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424747 Title: findmnt only displays /dev/pts on Trusty w/ Utopic Kernel (14.04.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1424747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1402769] [NEW] udisks tries to create degraded/sync_action watch files for mdadm IMSM containers
Public bug reported: I'm running Ubuntu 14.04 with the 3.17.5 kernel. I have 3 IMSM RAID1 arrays set up I noticed the following syslog messages: Dec 15 09:49:06 mariposa udisksd[3255]: udisks daemon version 2.1.3 starting Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md123/md/sync_action: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md123/md/degraded: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md125/md/sync_action: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md125/md/degraded: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md127/md/sync_action: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md127/md/degraded: No such file or directory (g-file-error-quark, 4) Dec 15 09:49:06 mariposa dbus[1230]: [system] Successfully activated service 'org.freedesktop.UDisks2' The files (degraded,sync_action) don't exist in the container (md127, etc.) directories, but do exist in the array (md126, etc.) directories themselves. I posted this to the linux-raid list as I suspected, was told those files are not created in the container directories. I recently ran software updates, but udisks was not one of the packages patched. ** Affects: udisks (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/1402769 Title: udisks tries to create degraded/sync_action watch files for mdadm IMSM containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1402769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320402] Re: mdadm resyncs imsm raid in Normal state
I have suffered under the same problem, running 12.10, 13.10 now 14.04. I just tried your patches, Matthew, they appeared to work. I only rebooted once, however. I'll test some more later. Thanks! -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320402 Title: mdadm resyncs imsm raid in Normal state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1320402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830915] Re: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file
Thanks for the info. I followed your instructions the message went away. I had had a lockup of my system, probably caused by the old kernel modules were stilled being loaded. Hopefully this clears it up. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830915 Title: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/830915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830915] Re: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file
The same thing happened to me on trusty, amd64 with the latest version of virtualbox 4.3.18. The strange thing is, dkms.conf was located in /var/lib/dkms/vboxhost/4.3.18/build/, but locate couldn't find it. It found the previous one, v4.3.16, but not the latest one. Only with find could I locate it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830915 Title: [Oneiric] Error during kernel upgrade: Could not locate dkms.conf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/830915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1131738] Re: VBoxSVC crashed with SIGABRT in __libc_message()
This just happened to me on trusty, amd64, virtualbox 4.3.16. I wasn't using the vmat the time, I had stepped away for about an hour returned to see the apport message. ** Attachment added: Virtualbox crash file https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1131738/+attachment/4231788/+files/_usr_lib_virtualbox_VirtualBox.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1131738 Title: VBoxSVC crashed with SIGABRT in __libc_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1131738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311725] Re: Installation crashed after grub setup on md array
The message logged when the grub-installer failed: ubuntu grub-installer: grub-install: error: disk 'md126,1' not found. ubuntu grub-installer: error: Running 'grub-install --force failed. This was mdadm configured raid1 (imsm). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311725 Title: Installation crashed after grub setup on md array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1311725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341209] Re: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04?
Originally, I posted a question (#251577), then followed up with a bug report. I was asked to run sudo apt-get upgrade on 7/15 I got the following answer: jcenter@avanti-due:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Just on a chance, I ran sudo apt-get upgrade again today now I see the following: jcenter@avanti-due:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apt apt-transport-https apt-utils compiz compiz-core compiz-gnome compiz-plugins-default compizconfig-settings-manager dput file file-roller gir1.2-nautilus-3.0 gir1.2-nmgtk-1.0 gir1.2-pango-1.0 google-chrome-stable gufw libapt-inst1.5 libapt-pkg4.12 libavformat54 libavutil52 libcompizconfig0 libdecoration0 libmagic1 libminiupnpc8 libnautilus-extension1a libnm-gtk-common libnm-gtk0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-0 libpango1.0-0:i386 libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 libpangoxft-1.0-0:i386 libswscale2 libunity-core-6.0-9 linux-firmware linux-headers-3.13.0-32 linux-headers-3.13.0-32-generic linux-image-3.13.0-32-generic linux-image-extra-3.13.0-32-generic linux-libc-dev linux-signed-image-3.13.0-32-generic nautilus nautilus-data network-manager-gnome pm-utils python-compizconfig python3-magic shotwell shotwell-common transmission-common transmission-gtk unity unity-services virtualbox-4.3 59 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 213 MB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] When I ran this before, everything was up to date. Now, not only do 59 packages need to be upgraded, but I see many of the core 14.04 installation needs to be upgraded! For example, the kernel version is the same as what I'm running: Linux avanti-due 3.13.0-32-generic #56-Ubuntu SMP Mon Jul 7 11:32:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Why would this happen? Should I do the upgrade? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341209 Title: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341209] Re: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04?
I've been having freeze ups since the upgrade. After a day or so, everything is frozen except the mouse. Thunderbird freezes up grays out after a few minutes when started. I'm also having a problem with one of my monitors staying blank after the screen saver kicks in, though I'm having it checked/replaced. (I didn't have a problem with it before this, but stranger things have been known to happen.) Could any of these issues be related? What should I do to confirm these problems are related and/or repair this? And, why would the upgrade say there was a fatal error that it had to fall back, but it then apparently completed the upgrade? I greatly appreciate any help! Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341209 Title: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1341209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312456] Re: Thunderbird 24.4 freezes very frequently with grey screen under Ubuntu 14.04
I'm having the same problem with thunderbird, but not with firefox. What compiz update fixes this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312456 Title: Thunderbird 24.4 freezes very frequently with grey screen under Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1312456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341209] [NEW] Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04?
Public bug reported: I upgraded from 12.10 to 13.10 w/o a problem. I rebooted several times ok. I then tried to upgrade to 14.04. The files downloaded successfully it was about half way through the install when I received a fatal error was told it would have to fallback to the previous version. I could not tell what the error was from. I had seen 2 error messages previously, one on the libpostproc52 error the other on a problem with apport-gtk - MaxReports reached. I let it back out. I thought I would see messages that it had restored the old files, but instead it looked like it was partially continuing. It definitely did not take very long before it said it was ready to restart. I restarted the PC eventually came up in 14.04!!: jcenter@avanti-due:~$ uname -a Linux avanti-due 3.13.0-32-generic #56-Ubuntu SMP Mon Jul 7 11:32:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux How do I determine what condition my system is in? How do I complete the installation? I'm writing this from the upgraded system! Thanks. -John ** Affects: 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/1341209 Title: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1341209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341209] Re: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04?
I saw a reference to this log file in another bug report. It has the particular parts of the upgrade that failed. ** Attachment added: Upgrade log file https://bugs.launchpad.net/ubuntu/+bug/1341209/+attachment/4151422/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341209 Title: Upgrade from 13.10 to 14.04 did not complete, but booted into 14.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1341209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184925] Re: Libreoffice shows empty menus when clicking them and then crashes
I just tried this removed the libreoffice-gtk package it appears to work. Hope this gets fixed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184925 Title: Libreoffice shows empty menus when clicking them and then crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1184925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092345] [NEW] Installer crashes trying to install grub on mdadm imsm raid1
Public bug reported: I had a feeling this would happen, installer only understands dmraid, not mdadm imsm raid. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity 2.12.16 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CasperVersion: 1.328 Date: Wed Dec 19 18:33:13 2012 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- nodmraid LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=unknown 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 quantal ubiquity-2.12.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092345 Title: Installer crashes trying to install grub on mdadm imsm raid1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1092345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061648] [NEW] fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build
Public bug reported: I just applied the latest patches this error appeared. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx-updates 2:8.982-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 DKMSKernelVersion: 3.2.0-30-generic Date: Thu Oct 4 10:19:49 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) PackageVersion: 2:8.982-0ubuntu0.1 SourcePackage: fglrx-installer-updates Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build UpgradeStatus: Upgraded to precise on 2012-08-22 (43 days ago) ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061648 Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1061648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061648] Re: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061648 Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1061648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045164] [NEW] ubuntu 12.04 executing grub-install dummy failed
Public bug reported: I installed the mdadm proposed update. I'm trying to install to an imsm raid1 array, using a btrfs filesystem on gpt partitions. My computer's BIOS can handle larger than 2TB drives, though it is not UEFI (Gigabyte x58a-ud3r rev 2 MB). I mounted the / partition afterwards noticed that it installed to /, not @, though my user directory was installed to @home. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.20 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CasperVersion: 1.315 Date: Sun Sep 2 23:10:37 2012 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper nodmraid quiet splash -- LiveMediaBuild: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) ProcEnviron: TERM=unknown PATH=(custom, no user) 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 precise ubiquity-2.10.20 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045164 Title: ubuntu 12.04 executing grub-install dummy failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1045164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045164] Re: ubuntu 12.04 executing grub-install dummy failed
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045164 Title: ubuntu 12.04 executing grub-install dummy failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1045164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957494] Re: Missing added utility 'mdmon'
I'm using mdadm to activate an Intel array. Dmraid is disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957494 Title: Missing added utility 'mdmon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/957494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957494] Re: Missing added utility 'mdmon'
I did build mdadm from source later installed over top of the distribution copy of mdadm. But, I did have it working before I did this. I decided to do that because the later version did have better support for the Intel matrix storage BIOS. I do have Windows 7 running with IMSM, so I would like to have this working since there will be limited future support for dmraid. As you're aware, Intel recommends using mdadm with kernel v2.6.27 or later. I think it would be a good idea to include mdmon in future builds, especially 12.04, if possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957494 Title: Missing added utility 'mdmon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/957494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957494] Re: Missing added utility 'mdmon'
You're right, I could have sworn that it was part of that package. I didn't have the read-only problem with 3.1.4, could it have been that mdmon wasn't needed in that version? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957494 Title: Missing added utility 'mdmon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/957494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920324] Re: Please merge mdadm 3.2.3-2 from Debian unstable (main) (multiple regressions)
mdmon is included with the Oneiric mdadm package. I'm testing Precise beta1 via the live cd saw my array coming up readonly after installing it. It took me awhile to figure out what was wrong. (Google is your friend, sometimes... ;-)) Sonny? I haven't been called that since the '60's. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920324 Title: Please merge mdadm 3.2.3-2 from Debian unstable (main) (multiple regressions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/920324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957494] Re: Missing added utility 'mdmon'
mdmon its man page are included with the Oneiric mdadm package. It's only missing in the Precise package. Note that the mdmon page is missing from the online manpages, see http://manpages.ubuntu.com/manpages/precise/man8/mdmon.8.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957494 Title: Missing added utility 'mdmon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/957494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920324] Re: Please merge mdadm 3.2.3-2 from Debian unstable (main) (multiple regressions)
I just installed this package it appears mdmon is missing. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920324 Title: Please merge mdadm 3.2.3-2 from Debian unstable (main) (multiple regressions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/920324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737027] Re: kpartx udev rule is broken
But, dmraid can't activate the partitions on GPT disks, so how will this work? Also, could you send me a link to the changes? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 737027] Re: kpartx udev rule is broken
Ok, I'll look see if there is a ticket for the GPT disk problem, or I'll open a new ticket tomorrow. Thanks Philip. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 737027] Re: kpartx udev rule is broken
But, dmraid can't activate the partitions on GPT disks, so how will this work? Also, could you send me a link to the changes? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737027] Re: kpartx udev rule is broken
Ok, I'll look see if there is a ticket for the GPT disk problem, or I'll open a new ticket tomorrow. Thanks Philip. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737027] Re: kpartx udev rule is broken
What is the status of the proposed changes made by Jesse? I found that 11.10 did not include kpartx the changes he proposed. Doing it by hand myself, it worked, but as soon as any change is made that would rebuild initrd.img, the kpartx files the changes have to be redone. I'm trying to figure out how to modify the initranfs-tools configuration to do this automatically, but I'm a novice at this. Having kpartx handle the partitions instead of dmraid as Philip suggests seems to be the way to go. (I think Fedora includes kpartx in the initramfs, also.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 737027] Re: kpartx udev rule is broken
What is the status of the proposed changes made by Jesse? I found that 11.10 did not include kpartx the changes he proposed. Doing it by hand myself, it worked, but as soon as any change is made that would rebuild initrd.img, the kpartx files the changes have to be redone. I'm trying to figure out how to modify the initranfs-tools configuration to do this automatically, but I'm a novice at this. Having kpartx handle the partitions instead of dmraid as Philip suggests seems to be the way to go. (I think Fedora includes kpartx in the initramfs, also.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/737027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737027] Re: kpartx udev rule is broken
While there is no explanation, the man page for dmraid has this:
dmraid {-a|--activate} {y|n|yes|no}
[-d|--debug]... [-v|--verbose]... [-i|--ignorelocking]
[-f|--format FORMAT[,FORMAT...]]
[{-P|--partchar} CHAR]
[-p|--no_partitions]
[--separator SEPARATOR]
[-t|--test]
[RAID-set...]
I think you would want to use -p or --no_partitions.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/737027
Title:
kpartx udev rule is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/737027/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 737027] Re: kpartx udev rule is broken
While there is no explanation, the man page for dmraid has this:
dmraid {-a|--activate} {y|n|yes|no}
[-d|--debug]... [-v|--verbose]... [-i|--ignorelocking]
[-f|--format FORMAT[,FORMAT...]]
[{-P|--partchar} CHAR]
[-p|--no_partitions]
[--separator SEPARATOR]
[-t|--test]
[RAID-set...]
I think you would want to use -p or --no_partitions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737027
Title:
kpartx udev rule is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/737027/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 737027] Re: kpartx udev rule is broken
Has there been any additional work done on this? This bug has affected me also, because of the point raised in comment #9 about using dmraid with GPT partitions. Will this be resolved for 11.10? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/737027/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 737027] Re: kpartx udev rule is broken
Has there been any additional work done on this? This bug has affected me also, because of the point raised in comment #9 about using dmraid with GPT partitions. Will this be resolved for 11.10? Thanks. -John -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/737027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 190227] Re: ia32 apps look for libs on the wrong place
I'm having the same problem. I'm running Ubuntu 10.04 X86_64. I upgraded to Thunderbird 3.1 (32-bit), when it starts I get the following errors: $ /opt/thunderbird/thunderbird -profilemanager /usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64 Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so LoadPlugin: failed to initialize shared library /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/amd64/libnpjp2.so [/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/amd64/libnpjp2.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-cone-plugin.so [/usr/lib/mozilla/plugins/libtotem-cone-plugin.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-gmp-plugin.so [/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-mully-plugin.so [/usr/lib/mozilla/plugins/libtotem-mully-plugin.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so [/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/nspluginwrapper/plugins/npwrapper.nppdf.so [/usr/lib/nspluginwrapper/plugins/npwrapper.nppdf.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so [/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so: wrong ELF class: ELFCLASS64] LoadPlugin: failed to initialize shared library /var/lib/flashplugin-installer/npwrapper.libflashplayer.so [/var/lib/flashplugin-installer/npwrapper.libflashplayer.so: wrong ELF class: ELFCLASS64] This caused a number of problems with TB 3.1, creating multiple files directories under ../Mail/ImapMail/mail.villanova.edu/* in the form of foldername-index.*, each with a different size. Also, TB 3.1 would constantly download messages. I then installed TB 3.2pre (64-bit), created a new profile removed all of the extraneous files directories. This seemed to resolve the immediate problem with TB, but not the actual problem with the libraries. -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 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 293970] Re: bonobo-activation-server : could not associate with desktop session
I'm having the same problem, usually after running an NX session remotely to my workstation. I come in the next day, my screen saver is locked. A hard reset is the only thing that will allow me to get back in. In messages I see: bonobo-activation-server (jcenter-31686): could not associate with desktop session: Failed to connect to socket /tmp/dbus-GjZOjel1tD: Connection refused I'm running Ubuntu 9.04. -- bonobo-activation-server : could not associate with desktop session https://bugs.launchpad.net/bugs/293970 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
