[Bug 1473903] Re: parted will generate two devices when adding one partition on mpath device
I'm not sure we are understanding each other correctly. I am not sure what the change you made to multipath-tools has to do with this bug, but the change you made to parted which is still sitting in the -proposed pocket is incorrect and needs to be rejected. Instead of changing parted, it is multipath-tools that needs changed to not use the -part naming scheme. Changing parted to use -part will also break dmraid. -- 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/1473903 Title: parted will generate two devices when adding one partition on mpath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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 1473903] Re: parted will generate two devices when adding one partition on mpath device
Your output there clearly shows that the verification *failed*. This change needs to be reverted as it does completely the wrong thing. The correct name is p1, not -part1. It is multipath-tools that needs changed, not parted. Please revert the parted change immediately. ** Changed in: parted (Ubuntu) Status: Fix Released => Triaged ** Changed in: multipath-tools (Ubuntu) Status: Fix Released => Triaged ** Tags removed: verification-done ** Tags added: verification-failed -- 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/1473903 Title: parted will generate two devices when adding one partition on mpath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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 1532062] Re: Drives mistakenly reported as removable
I'm guessing that this particular scsi controller supports hot plug and so identifies the drives as removable since technically you can yank out the raid bays and replace them while the system is on. The whole concept of whether a drive is "removable" or not is a hand waving best guess that really needs to not be used for anything, so yea, the bug seems to be that curtain is looking at it in the first place. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1532062 Title: Drives mistakenly reported as removable To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1532062/+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
** Changed in: multipath-tools (Ubuntu) Status: In Progress => Fix Released -- 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 1473903] Re: parted will generate two devices when adding one partition on mpath device
We have already spent a lot of effort over the years going with #2, so
turning around at this point isn't the right thing to do. The one place
I still see multipath-tools doing the wrong thing is in its kpartx.rules
file, which still contains this stanza:
ENV{DM_STATE}=="ACTIVE", ENV{DM_UUID}=="mpath-*", \
RUN+="/sbin/kpartx -a -p -part /dev/$name"
That '-p part' simply needs deleted.
** Changed in: parted (Ubuntu)
Status: Triaged => Invalid
** Changed in: multipath-tools (Ubuntu)
Status: Invalid => Triaged
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
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/1473903
Title:
parted will generate two devices when adding one partition on mpath
device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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 1473903] Re: parted will generate two devices when adding one partition on mpath device
sudo /etc/init.d/udev stop -- 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/1473903 Title: parted will generate two devices when adding one partition on mpath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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 1473903] Re: parted will generate two devices when adding one partition on mpath device
I'm not sure why the error from parted's mkpart command, but the fact that there are two different devices is due to the multipath-tools guys deciding to break traddition and configure their udev script to run kpartx and ask it to create the partition with the form base-partX rather than the baseX or basepX ( if base already ends in a digit ), like the rest of linux has done since the dawn of time. They need to come in line with the rest of the world and use the correct naming convention. As for the parted error itself, can you try killing udev while issuing that command and see if it still happens? ** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- 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/1473903 Title: parted will generate two devices when adding one partition on mpath device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1473903/+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 1472549] Re: sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware
** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1472549 Title: sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472549/+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 1472549] Re: sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware
As the error message indicates, your system does not have any supported sensors. ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1472549 Title: sensors command is not getting executed in Ubuntu 14.04.3 on PowerNV 8335-GTA Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1472549/+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 1464875] Re: package fancontrol 1:3.3.5-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Please run grep fancontrol /etc/init.d/* and post the output. ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1464875 Title: package fancontrol 1:3.3.5-2 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/lm-sensors/+bug/1464875/+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 691590] Re: libvirt should not take ownership of ISO images
This really feels like a serious security bug. The whole point of running qemu as non root is to prevent it from accessing files that you haven't given it permission to. By blindly chowning files to the qemu user, you allow for the user who is given permission to run virtual machines to start one with direct access to your /boot partition and hack the host system. Even if you do wish to bypass permissions and allow the vm access to whatever file a vm admin has configured it to ( under the assumption that they are trusted as if root ), you don't do that with the sledge hammer of chowning the file; you open the file while still root, and pass the open file descriptor to qemu. Really, it should assume the identity of the user who is requesting that the vm be started and open the file as them rather than root, thus restricting access only to the files that user has access to, but that may be considered a separate issue. For now I will focus on at least getting rid of the bad behavior of permanently chowning files. ** Changed in: libvirt (Ubuntu) Status: Won't Fix = Triaged ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) = Phillip Susi (psusi) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/691590 Title: libvirt should not take ownership of ISO images To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/691590/+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 1462838] [NEW] libvirt takes away access to my files
Public bug reported: When starting a vm in virt-manager and pointing it to an iso file in my home directory, it changes the permissions so it can only be accessed by the owner, and chowns the file to libvirt-qemu.kvm, so I no longer have access to it. It should not be changing permissions. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1462838 Title: libvirt takes away access to my files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1462838/+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 1453572] [NEW] libvirt-bin's sysv init script references avahi, which no longer exists
Public bug reported: /etc/init.d/libvirt-bin lists Should-Start: avahi. There is no such service. Apparently it has been renamed to avahi-daemon. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1453572 Title: libvirt-bin's sysv init script references avahi, which no longer exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1453572/+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 1453575] [NEW] Package woefully out of date
Public bug reported: libvirt has not been updated since 2013 and upstream has had a number of new releases. Please update. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1453575 Title: Package woefully out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1453575/+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 1426787] Re: the sensors don't show real CPUcore temp
** Changed in: lm-sensors (Ubuntu) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1426787 Title: the sensors don't show real CPUcore temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1426787/+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 1426787] Re: the sensors don't show real CPUcore temp
You can add acpi_enforce_resources=lax to your kernel command line arguments ( edit /etc/default/grub, and run sudo update-grub ) to force the module to load, though there is a chance that doing so may cause problems. ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1426787 Title: the sensors don't show real CPUcore temp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1426787/+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 485899] Re: pwmconfig generates a blank values /etc/fancontrol
Closing due to PEBKAC error ;) ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+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 1406499] Re: AMD Kaveri support needs lm-sensors 3.3.5
** Changed in: lm-sensors (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1406499 Title: AMD Kaveri support needs lm-sensors 3.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1406499/+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 1406499] Re: AMD Kaveri support needs lm-sensors 3.3.5
** Branch linked: lp:~psusi/ubuntu/vivid/lm-sensors/merge -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1406499 Title: AMD Kaveri support needs lm-sensors 3.3.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1406499/+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 945433] Re: Incorrect GPT length should be handled better
If you aren't using gpt then you aren't getting the error message and thus aren't related to this bug. That message again was: Assertion (last_usable = disk-dev-length) at ../../../libparted/labels/gpt.c:718 in function _parse_header() failed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/945433 Title: Incorrect GPT length should be handled better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/945433/+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 945433] Re: Incorrect GPT length should be handled better
It seems the bug on the gdisk side was fixed sometime between 0.5.1 and 0.8.1: the latter version now correctly reports the size error. ** Changed in: gdisk (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to gdisk in Ubuntu. https://bugs.launchpad.net/bugs/945433 Title: Incorrect GPT length should be handled better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdisk/+bug/945433/+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 1389647] Re: lm-sensors don`t recognize fan in the laptop ASUS M50VN
If sensors-detect doesn't detect it then yea, it's not supported. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+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 1389647] Re: lm-sensors don`t recognize fan in the laptop ASUS M50VN
That isn't a bug... ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1389647 Title: lm-sensors don`t recognize fan in the laptop ASUS M50VN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1389647/+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 1378708] Re: VNC based installation does not interpret key strokes correctly.
This doesn't seem to have anything to do with ubiquity what makes you think this isn't simply your keyboard's auto repeat feature and you're holding down the key for too long? ** Package changed: ubiquity (Ubuntu) = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1378708 Title: VNC based installation does not interpret key strokes correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1378708/+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 1359296] Re: Shutting down OpenVPN before umount network shares causes 120 second timeout on shutdown
** Package changed: util-linux (Ubuntu) = openvpn (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1359296 Title: Shutting down OpenVPN before umount network shares causes 120 second timeout on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1359296/+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 1348945] Re: -lsensors doesn't link to libsensors
Probably because redhat has an older version of gcc. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1348945 Title: -lsensors doesn't link to libsensors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1348945/+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 1322625] Re: sensord daemon does not detects chips
What? There doesn't seem to be any such thing as module-init- tools.conf. The modules in /etc/modules are loaded by /etc/init.d/kmod, which runs in rcS.d, before anything in rc2.d. ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1322625 Title: sensord daemon does not detects chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1322625/+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 1322625] Re: sensord daemon does not detects chips
Ahh, you must be still running 12.04. This was fixed after 12.04 by switching from module-init-tools to kmod. ** Changed in: lm-sensors (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1322625 Title: sensord daemon does not detects chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1322625/+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 1322625] Re: sensord daemon does not detects chips
Then you should upgrade to 14.04. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1322625 Title: sensord daemon does not detects chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1322625/+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 1322625] Re: sensord daemon does not detects chips
Sure, but only critical fixes get backported to older releases. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1322625 Title: sensord daemon does not detects chips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1322625/+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 1320415] [NEW] postfix started in single user mode during upgrade
Public bug reported: I shutdown my server to single user mode and ran a dist-upgrade. The postfix postint started the daemon, even though it is not supposed to be running in single user mode. ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1320415 Title: postfix started in single user mode during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1320415/+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 1320415] Re: postfix started in single user mode during upgrade
Just created a fresh install of 13.10 in a vm, swapped /etc/apt/sources.list to trusty, shutdown to single user mode, confirmed with runlevel that the system was in single user mode, and ran apt-get install postfix to upgrade it, and sure enough, it it started postfix. ** Changed in: postfix (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1320415 Title: postfix started in single user mode during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1320415/+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 1320415] Re: postfix started in single user mode during upgrade
It looks like the problem is in invoke-rc.d: manually running invoke- rc.d postfix restart, while in single user mode, starts postfix. ** Package changed: postfix (Ubuntu) = sysvinit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1320415 Title: postfix started in single user mode during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1320415/+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 42376] Re: hibernate should hide grub menu
What does Windows have to do with it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/42376 Title: hibernate should hide grub menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/42376/+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 1078922] Re: Fan runs unnecessary
If the proprietary amd graphics driver is causing excessive heat, you will need to take that up with amd, or stop using the proprietary driver. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 1212492] Re: cc_growpart broken if parted resizefs found
You don't use ---pretend-input-tty in conjunction with --script. The point is to pretend that you are a human, not a script. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212492 Title: cc_growpart broken if parted resizefs found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1212492/+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 1093918] Re: grub-probe auto-detection fails on raid
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1267890] [NEW] assertion failure and hard hang switching resolution
Public bug reported: I booted the 13.10 live cd using -vga std ( since the default cirrus no longer works correctly ) and it comes up using the full resolution of my real screen, which is annoying since the window does not fit no the screen. I went into the display control pannel to switch to a lower resolution, and qemu hung. It printed this to the terminal: ERROR:/build/buildd/qemu-1.5.0+dfsg/ui/gtk.c:420:gd_switch: assertion failed: (surface_stride(surface) == stride) And it would not respond to ctrl-c or ctrl-z, so I had to kill -9 it from another terminal. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1267890 Title: assertion failure and hard hang switching resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1267890/+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 1267890] Re: assertion failure and hard hang switching resolution
The full command line was: qemu-system-x86_64 --enable-kvm -m 1200 -drive if=virtio,file=img,cache=unsafe -drive if=ide,file=Downloads/trusty- desktop-amd64.iso,media=cdrom -vga std -boot d -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1267890 Title: assertion failure and hard hang switching resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1267890/+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 1093918] Re: grub-probe auto-detection fails on raid
** No longer affects: multipath-tools (Ubuntu Quantal) -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1093918] Re: grub-probe auto-detection fails on raid
The backport to precise is still waiting for someone to test and verify it, see comment #56. -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1093918] Re: grub-probe auto-detection fails on raid
** Changed in: multipath-tools (Ubuntu Precise) Milestone: ubuntu-12.04.3 = ubuntu-12.04.4 -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1212444] Re: cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14
Looks like the arguments to parted are backwards. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212444 Title: cc_growpart failed in auto grow mode with Error: Could not stat device resizepart - No such file or directory. with parted 2.3-14 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1212444/+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 1212492] Re: cc_growpart broken if parted resizefs found
You have to not use --script and parse the output for the warning and answer yes. I have been mulling over a --force-things system to allow a script to specify that it expects a specific error and how it should be handled but it isn't easy the way libparted is structured. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212492 Title: cc_growpart broken if parted resizefs found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1212492/+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 1212492] Re: cc_growpart broken if parted resizefs found
IIRC, parted assumes --script mode when stdin is not a tty. There was an undocumented switch that the test suite uses to override this, or I thought that expect allocates a pseudo tty (might need a switch) and that should also do the trick. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212492 Title: cc_growpart broken if parted resizefs found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1212492/+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 1212492] Re: cc_growpart broken if parted resizefs found
Currently the only way to have parted resize a busy partition is to use interactive mode rather than script mode and say yes at the prompt. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1212492 Title: cc_growpart broken if parted resizefs found To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1212492/+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 941874] Re: (fakeraid) root device not activated during boot
Before running dmraid -ay, what does blkid show? -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
If /dev/mapper/pdc_ebdeeaiceb does not exist without you having to run dmraid, then it is unrelated to this bug. Please file a new one. -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 1093918] Re: grub-probe auto-detection fails on raid
** Description changed: kpartx was mapping the entire extended partition then stacking the logical partitions on that device. This exposes a device that otherwise appears to be an entire disk device containing the logical partitions, and this confuses grub. The extended partition is supposed to only expose the first two sectors to allow LILO to be installed. The patch has been applied upstream now, and since this is the only change since quantal, a simple copy to quantal-updates should resolve it there as well. I have done this in my ppa and the reporter has verified it has fixed the issue. + + TEST CASE: + + Use fdisk to create an extended parition either on a fakeraid disk or an + LVM logical volume. Run kpartx -a /dev/mapper/whatever to activate the + partitions on the disk. Assuming the extended partition is number 3, + then sudo blockdev --getsz /dev/mapper/whatever3 will report the + apparent size of the extended partition. The size should only be 2 + sectors regardless of the size of the extended partition. -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1198491] Re: sensors not detect my sensors [ SMSC LPC47M172 ]
As sensors-detect said, there is no driver for this chip, so this is not a bug. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1198491 Title: sensors not detect my sensors [ SMSC LPC47M172 ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1198491/+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 1194390] Re: known issue in current version
I guess I haven't had to modify my sieve scripts in a while since I didn't notice this until I came across this bug report, but yea, since upgrading my server to quantal, I can't modify my sieve scripts as managesieved just crashes every time. ** Tags removed: dovecot managesieved segfault sieve ** Tags added: re ** Tags removed: re ** Tags added: regression-release ** Changed in: dovecot (Ubuntu) Status: New = Triaged ** Changed in: dovecot (Ubuntu) Importance: Medium = High ** Summary changed: - known issue in current version + managesieve crashes, fixed upstream ** Bug watch added: Debian Bug tracker #688197 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688197 ** Also affects: dovecot (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688197 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1194390 Title: managesieve crashes, fixed upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1194390/+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 1194390] Re: managesieve crashes, fixed upstream
Looks like debian already fixed it and that version made it into raring. ** Changed in: dovecot (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1194390 Title: managesieve crashes, fixed upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1194390/+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 242869] Re: dnsmasq's dhcp blocked to clients by firestarter
This package has been removed from Ubuntu. Closing all related bugs. ** Changed in: firestarter (Ubuntu) Status: Fix Committed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/242869 Title: dnsmasq's dhcp blocked to clients by firestarter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/242869/+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 253895] Re: postinst doesn't handle failure of dnshostname
** Summary changed: - upgrading to 8.10 + postinst doesn't handle failure of dnshostname ** Changed in: kerberos-configs (Ubuntu) Status: Confirmed = Triaged ** Changed in: kerberos-configs (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kerberos-configs in Ubuntu. https://bugs.launchpad.net/bugs/253895 Title: postinst doesn't handle failure of dnshostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerberos-configs/+bug/253895/+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 1093918] Re: grub-probe auto-detection fails on raid
** Branch linked: lp:~psusi/ubuntu/precise/multipath-tools/fix-dmraid- extended-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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 1093918] Re: grub-probe auto-detection fails on raid
** Changed in: multipath-tools (Ubuntu Precise) Status: New = In Progress ** Changed in: multipath-tools (Ubuntu Precise) Assignee: (unassigned) = Phillip Susi (psusi) ** Changed in: multipath-tools (Ubuntu Precise) Importance: Undecided = Critical ** Changed in: multipath-tools (Ubuntu Precise) Milestone: None = ubuntu-12.04.3 -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1093918/+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 277648] Re: libdevmapper does not load its kernel modules upon install
I believe the modules are now auto loaded on demand. Is this still an issue for you? ** Package changed: devmapper (Ubuntu) = lvm2 (Ubuntu) ** Changed in: lvm2 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/277648 Title: libdevmapper does not load its kernel modules upon install To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/277648/+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 56235] Re: Postfix fails to start at boot time
Without a way to reproduce the problem, and the fact that the conf file in the package does not look like that, I don't think we have a bug here. Combined with a lack of input for several years, I think it's time this is put to rest. ** Changed in: postfix (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/56235 Title: Postfix fails to start at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/56235/+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 68729] Re: Loses all backups when disk is full
Closing this bug due to lack of input for over a year. ** Changed in: backuppc (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to backuppc in Ubuntu. https://bugs.launchpad.net/bugs/68729 Title: Loses all backups when disk is full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/68729/+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 72944] Re: Always complains about PID file
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: dhcp3 (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/72944 Title: Always complains about PID file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/72944/+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 1163573] Re: Ubuntu 12.10 overheats my laptop until it shutdowns without notice
Unless you have setup fancontrol ( which it seems you have not ) then lm-sensors nor any other component in Ubuntu is in control of your fans. The hardware controls them, and you said they do speed up so it sounds like that hardware control is working properly. You may be able to run the sensors-detect script to get lm-sensors to be able to correctly report the fan speed to verify this. In any event, the CPU automatically throttles its speed to prevent overheating, but this should only happen in dire circumstances. Your logs indicate this has been happening, yet it still overheats. According to Intel's design documents, this points to either a catastrophic failure of the cooling system ( heatsink has come loose ) or its design limits are well under what the cpu requires. Either way, overheating requires a hardware defect. It may be that the hardware simply does not respond to temperature rise fast enough ( due to HP design error ), in which case you may be able to work around the defect by changing bios options to always run the fan at full speed, or to be more aggressive in its use of the fan. Alternatively, if sensors-detect recognizes your fan controller hardware and a proper module can be loaded to manipulate it, you could then force full speed fan mode. You might also check your logs for a line like this: CPU0: Thermal monitoring enabled (TM1) The BIOS has the option to enable TM1 or the much better TM2 mode. If your system is using TM1 then that could be a contributing factor that you would need to report to HP so that they may fix their bios to use the better TM2 mode. ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1163573 Title: Ubuntu 12.10 overheats my laptop until it shutdowns without notice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1163573/+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 1163573] Re: Ubuntu 12.10 overheats my laptop until it shutdowns without notice
You will need to seek support from your hardware vendor since overheating is a hardware defect. ** Changed in: lm-sensors (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1163573 Title: Ubuntu 12.10 overheats my laptop until it shutdowns without notice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1163573/+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 1155403] Re: virtio cdrom detected as hard disk
The current raring version, which appears to be 1.4.0+dfsg-1expubuntu3. Also I guess this should be under just the qemu package now rather than -kvm. The command line is qemu -drive file=whatever.iso,if=virtio,media=cdrom. With or without the media argument seems to make no difference; either way udev thinks the drive is a disk, not a cdrom. ** Package changed: qemu-kvm (Ubuntu) = qemu (Ubuntu) ** Changed in: qemu (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1155403 Title: virtio cdrom detected as hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1155403/+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 1155107] Re: pwmconfig assumes no fan control from fans not stopping
Are you sure it actually speeds up when you set it too low? I have noticed that the Intel stock CPU fans seem to have a minimum speed they will refuse to go below, but when you try, it just refuses to go any lower rather than speeding up. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1155107 Title: pwmconfig assumes no fan control from fans not stopping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1155107/+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 1155403] [NEW] virtio cdrom detected as hard disk
Public bug reported: Trying to install Ubuntu or Debian using virtio to emulate the cdrom fails. This appears to be due to the drive appearing to be a hard disk, rather than a cdrom, despite the media=cdrom argument to qemu. I'm not sure if this is a bug in qemu, or the kernel virtio driver? ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1155403 Title: virtio cdrom detected as hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1155403/+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 1102135] Re: package odbcinst1debian2 2.2.14p2-5ubuntu3 failed to install/upgrade: ErrorMessage: subprocess rm cleanup returned error exit status 127
*** This bug is a duplicate of bug 1103111 *** https://bugs.launchpad.net/bugs/1103111 ** This bug has been marked a duplicate of bug 1103111 Upgrade failure -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unixodbc in Ubuntu. https://bugs.launchpad.net/bugs/1102135 Title: package odbcinst1debian2 2.2.14p2-5ubuntu3 failed to install/upgrade: ErrorMessage: subprocess rm cleanup returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/1102135/+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
Re: [Bug 1093918] Re: grub-probe auto-detection fails on raid
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did the other errors go away? Those were odd... looked like something dmraid might say but AFAIK it isn't run by update-grub. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJQ6KYMAAoJEJrBOlT6nu75ZmUH/R0th/T1IAfPDDLTwAdNjaw5 Ve6Os4/cjdthWt2ZDY1l3RfUmmc5DzNdEdbbNqNYlzquCeydV3BuY5h0Z6Ag/D/l TrObvoFxXSTnGzPcA4SKNAcYcfjV1/pqcX1bmYEwjaxgAcS+6kFD6g/c6Si1L8zm zqmhpFnYzsdJzmrsLejYAsRuGUD4/fYASupsvM4g6jk1f4g4N/wx2ZfPodKGlpwW qr8gKQdJS4wI4tHbDtwSl+LjIFSAIBisbON3t2T44VGELXV4Nut+k0YcMxf7RQkZ fW0H4cTq2lpxYok6mVqkS+AYcAZfFLpvrQVfPH7oVzUlYuxj2qSJrwOjBBBCb8U= =LPPW -END PGP SIGNATURE- -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+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 1093918] Re: grub-probe auto-detection fails on raid
kpartx is incorrectly mapping the entire extended partition, then building the logical partitions on top of the extended. Bad kpartx. ** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New -- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+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 1093918] Re: grub-probe auto-detection fails on raid
I believe I have fixed the problem. Please add my PPA to your sources and update: sudo apt-add-repository ppa:psusi/ppa sudo apt-get update sudo apt-get upgrade ** Branch linked: lp:~psusi/ubuntu/raring/multipath-tools/fix-extended- 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/1093918 Title: grub-probe auto-detection fails on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1093918/+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 1093013] Re: sensors-detect doesn't find fans on HP ProBook 6560b
Have you tried 12.10? ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1093013 Title: sensors-detect doesn't find fans on HP ProBook 6560b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1093013/+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 1078922] Re: Fan runs unnecessary
Please stop changing the status. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 1078922] Re: Fan runs unnecessary
Then I'm afraid I have to stand by what I said before: this isn't a bug. You will need to look into your motherboard manual to see if there are settings you can tune for the fan. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 1078922] Re: Fan runs unnecessary
Can you boot 12.10 using the kernel from 12.04 and see the lower temperature come back? ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 1078922] Re: Fan runs unnecessary
Have you installed lm-sensors and configured fancontrol? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 1062310] Re: ubuntu 10.04.4 LTS failed to sensor cpu , board and fans , by sensors-applet and lm-sensors
Are you saying that this has been fixed in 11.10? ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1062310 Title: ubuntu 10.04.4 LTS failed to sensor cpu , board and fans , by sensors- applet and lm-sensors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1062310/+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 1078922] Re: Fan runs unnecessary
If you aren't using fancontrol, then there's no bug here. Without that, the fans are controlled by the hardware in response to temperature rise. You have nothing to worry about as far as damage goes as processors are intended to handle 90-100 C, so even 52 is quite cool. Often times the system bios will have options to configure how aggressive the fans should work to keep temperature down, so you may want to try changing those to keep it quieter. ** Changed in: lm-sensors (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1078922 Title: Fan runs unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1078922/+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 941874] Re: (fakeraid) root device not activated during boot
Unless you must dual boot this system with Windows, the best thing to do is not to use fake raid. Switch to regular Linux software raid instead. -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 992409] Re: lm-sensors reports incorrect temperature
This looks like a kernel regression. We will need to narrow down where it was introduced. Could you try 11.04 and 11.10 next? ** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/992409 Title: lm-sensors reports incorrect temperature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/992409/+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 941874] Re: (fakeraid) root device not activated during boot
Adi, dmraid is for fake hardware raid support, not the software raid you are using. Your issue seems to be unrelated to dmraid or this bug report. -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 992409] Re: lm-sensors reports incorrect temperature
Can you please boot the 10.10 livecd and verify that you still get a correct reading there, and also run the following command and attach the resulting file ( DSDT.gz ): sudo cat /sys/firmware/acpi/tables/DSDT | gzip -c - DSDT.gz ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/992409 Title: lm-sensors reports incorrect temperature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/992409/+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
The broken/nonfunctional udev rule has not yet been removed in kpartx, but 12.04 uses kpartx to activate dmraid partitions and so supports GPT. -- 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 941874] Re: (fakeraid) root device not activated during boot
** Changed in: dmraid (Ubuntu) Importance: High = Critical ** Changed in: multipath-tools (Ubuntu) Importance: High = Critical -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
I've fixed both packages to get this working and set up an isw dmraid with my old disks and installed precise and the updated packages to verify it works. Just waiting for a sponsor to merge the changes. ** Changed in: dmraid (Ubuntu) Status: Fix Released = In Progress ** Changed in: multipath-tools (Ubuntu) Status: Triaged = In Progress -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
The -p is to disable dmraid's internal handling of partitions in favor of letting kpartx take care of it. This was done because kpartx also supports GPT, but dmraid does not. Can you try updating your initramfs and see if that helps? sudo update-initramfs -u Also please make sure you are running the -ubuntu7 version of dmraid. -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
What do you mean by added kpartx hooks? -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
Ok, kpartx has a hook rule that is supposed to do that already, but for some reason, it is not being installed. It looks like a packaging error of some sort. ** Changed in: multipath-tools (Ubuntu) Status: Incomplete = Triaged -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
** Also affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: multipath-tools (Ubuntu) Status: New = Triaged ** Changed in: multipath-tools (Ubuntu) Importance: Undecided = High ** Changed in: multipath-tools (Ubuntu) Assignee: (unassigned) = Phillip Susi (psusi) -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 941874] Re: (fakeraid) root device not activated during boot
Wait a second, the kpartx udev rule shouldn't have anything to do with dmraid. The dmraid udev rule takes care of running kpartx. ** Changed in: multipath-tools (Ubuntu) Status: Triaged = Incomplete -- 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/941874 Title: (fakeraid) root device not activated during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/941874/+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 885107] Re: resuming after suspend looses control on fan speed, which is kept at 100%
Then it isn't a bug in lm-sensors, but in the hardware/firmware of the motherboard. ** Changed in: lm-sensors (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/885107 Title: resuming after suspend looses control on fan speed, which is kept at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/885107/+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 920956] Re: Kpartx interferes with automount behaviour
When this happens, what is the output from the following commands: sudo dmsetup table sudo kpartx -l /dev/sdb1 ** Changed in: multipath-tools (Ubuntu) Status: New = Incomplete -- 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/920956 Title: Kpartx interferes with automount behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/920956/+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 885107] Re: resuming after suspend looses control on fan speed, which is kept at 100%
It looks like you have not configured fancontrol so it isn't actually working. Can you try removing the package and see if the behavior remains the same? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/885107 Title: resuming after suspend looses control on fan speed, which is kept at 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/885107/+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 884177] Re: fancontrol cannot read its own configuration file
You must write a config file for it by hand or using pwmconfig. ** No longer affects: lm-sensors (Ubuntu Oneiric) ** No longer affects: lm-sensors (Ubuntu Precise) ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/884177 Title: fancontrol cannot read its own configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/884177/+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 264200] Re: lm-sensors not recognized.
This is really a question but since it was also filed as a question at the time, and been answered, I'm just going to close the bug now. ** Changed in: lm-sensors (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/264200 Title: lm-sensors not recognized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/264200/+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 352987] Re: lm-sensors report incorrect values of CPU temparature
This appears to be a hardware defect that needs a workaround in the kernel k8temp driver. Such a workaround may already be in place. Is this still an issue with Ubuntu 11.10? ** Package changed: lm-sensors (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/352987 Title: lm-sensors report incorrect values of CPU temparature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352987/+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 884177] Re: fancontrol cannot read its own configuration file
Config files don't contain messages, they configure fancontrol to work. Is the man page not sufficient? I suppose the package could have a debconf question that prompts you to run pwmconfig when you install it... ** Summary changed: - fancontrol cannot read its own configuration file + fancontrol should have debconf prompt to run pwmconfig ** Changed in: lm-sensors (Ubuntu) Status: Invalid = Triaged ** Description changed: - - $ fancontrol - Loading configuration from /etc/fancontrol ... - Error: Can't read configuration file - - $ lsb_release -rd - Description: Ubuntu 11.10 - Release: 11.10 - - ~$ apt-cache policy fancontrol - fancontrol: - Installed: 1:3.3.0-4ubuntu1 - Candidate: 1:3.3.0-4ubuntu1 - Version table: - *** 1:3.3.0-4ubuntu1 0 - 500 http://fi.archive.ubuntu.com/ubuntu/ oneiric/universe i386 Packages - 100 /var/lib/dpkg/status + The fancontrol package needs to be cofigured before it works. This is + somewhat automated by pwmconfig. The package should prompt and run + pwmconfig for you when installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/884177 Title: fancontrol should have debconf prompt to run pwmconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/884177/+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 884177] Re: fancontrol should have debconf prompt to run pwmconfig
Yes, that's exactly the idea. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/884177 Title: fancontrol should have debconf prompt to run pwmconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/884177/+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 884173] Re: sensors returning a bogus temperature reading
Unfortunately, lm-sensors has no way of knowing whether or not your particular motherboard has the sensor properly wired. If you wish to hide sensors that your motherboard does not correctly use, then you can edit /etc/sensors3.conf. See man sensors.conf. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/884173 Title: sensors returning a bogus temperature reading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/884173/+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 894047] Re: Fansensor unavailable under Ubuntu 11.10 on Intel Corporation Mobile 945GME Express
It looks like you do not have any supported sensors. You mention that this worked on a previous release. Can you boot that release and provide the results of running sensors-detect there? Also you might want to answer yes to the question to probe i2c devices. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Incomplete ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/894047 Title: Fansensor unavailable under Ubuntu 11.10 on Intel Corporation Mobile 945GME Express To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/894047/+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 710040] Re: does not support atom d525
Please provide the output of the sensors command. ** Changed in: lm-sensors (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/710040 Title: does not support atom d525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/710040/+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 478762] Re: lm-sensors don't work
This report has become an extended support discussion, and does not describe an actual bug, therefore I am closing it. ** Changed in: lm-sensors (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/478762 Title: lm-sensors don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/478762/+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
