[Bug 2065608] [NEW] An unresolvable problem occurred while calculating the upgrade
Public bug reported: $ grep ^Pr /etc/update-manager/release-upgrades Prompt=normal $ sudo do-release-upgrade [...] Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Mon May 13 17:51:20 2024 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-05-13 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2024-05-13T16:47:29.516789 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065608 Title: An unresolvable problem occurred while calculating the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063360] Re: Could not calculate the upgrade
** Attachment added: "/var/log/dist-upgrade/apt.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+attachment/5770091/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063360 Title: Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063360] [NEW] Could not calculate the upgrade
Public bug reported: Trying to upgrade from 22.04.4 to 24.04: $ do-release-upgrade -d Checking for a new Ubuntu release = Welcome to Ubuntu 24.04 LTS 'Noble Numbat' = [...] Checking package manager Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Wed Apr 24 19:28:06 2024 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-04-24 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy ** Attachment added: "/var/log/dist-upgrade/main.log" https://bugs.launchpad.net/bugs/2063360/+attachment/5770081/+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/2063360 Title: Could not calculate the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer
** Bug watch added: Red Hat Bugzilla #1413858 https://bugzilla.redhat.com/show_bug.cgi?id=1413858 ** Also affects: wayland-protocols (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1413858 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857655 Title: gdkselection-wayland.c:275: error reading selection buffer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863165] Re: autoremove-kernels doesn't purge kernels
I'd consider having remnants of old package versions (and lots of them) to be a bug, but it's your distribution, so having this dismissed is an answer to this problem nonetheless. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863165 Title: autoremove-kernels doesn't purge kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863165] Re: autoremove-kernels doesn't purge kernels
** Changed in: apt (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863165 Title: autoremove-kernels doesn't purge kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863165] Re: autoremove-kernels doesn't purge kernels
So, how can I convince APT to _automatically_ remove all kernel leftovers? I could of course run a cron job with the workaround, but maybe this can be done The Right Way? :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863165 Title: autoremove-kernels doesn't purge kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863165] [NEW] autoremove-kernels doesn't purge kernels
Public bug reported:
Maybe this is a configuration issue, but:
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.
The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.
Workaround:
dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg -P
# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Maybe this is a configuration issue, but:
-
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
- # dpkg -l | grep ^rc | cut -c-80
- rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel image
generic
- rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel extra
modules
+ # dpkg -l | grep ^rc | cut -c-70
+ rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
+ rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
+ rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
+ rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
+ rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
+ rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
+ rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
+ rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
+ rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
-
- And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels
[Bug 1742789] Re: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device
FWIW, this just happened again while trying out the latest mainline kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline * Kernels up to v5.3-rc5 work fine, but booting it takes up ~36MB of /run (unpacking during boot) on the Dom0 here. * Kernel v5.3-rc6 seems to take up even more, filling up the 40MB /run filesystem completely and booting fails. But vt100 is correct of course, extending the /run filesystem solves this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742789 Title: Xen PV Guest won't boot latest kernel- OSError: [Errno 28] No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys
** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
*** This bug is a duplicate of bug 578431 *** https://bugs.launchpad.net/bugs/578431 ** This bug has been marked a duplicate of bug 578431 wpa_supplicant spams syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Launchpad really needs something similar to RESOLVED/DUPLICATE, as I had to crawl through the whole report to find out that this is considered a duplicate of 578431. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555852] Re: Make it possible to use ULOG instead of LOG
I guess bug #1475676 would be the logical consequence here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/555852 Title: Make it possible to use ULOG instead of LOG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/555852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 966039] Re: netsnmp_assert 1 == new_val->high failed int64.c:419 netsnmp_c64_check32_and_update()
FWIW, this had been reported to upstream recently and a fix has been commited to their source tree: https://sourceforge.net/p/net-snmp/mailman/message/35585541/ https://sourceforge.net/p/net-snmp/code/ci/333aea41eb8bcdb9afae6bb89f3581f8e70ee830 There have been no official net-snmp relases since v5.7.3 (Dec 2014), but their commit log suggests that development is still active. So, upgrading to their latest version plus cherry picking the commit above should fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/966039 Title: netsnmp_assert 1 == new_val->high failed int64.c:419 netsnmp_c64_check32_and_update() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/966039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1397652] Re: /dev/random and /dev/urandom world writeable
FWIW, Debian #81748 explains why it's safe to have world-writable
/dev/{u,}random devices.
** Bug watch added: Debian Bug tracker #81748
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81748
** Also affects: makedev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=81748
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397652
Title:
/dev/random and /dev/urandom world writeable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397652/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys
** Summary changed: - ssh-add does not handle ECDSA keys until ssh-agent exports are manually launched + gnome-keyring doesn't support ecdsa or ed25519 keys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498145] Re: virtualbox-dkms 5.0.4-dfsg-2: virtualbox kernel module failed to build [SUPDrv-linux.c:488:8: error: void value not ignored as it ought to be]
There's a patch in the VirtualBox forum for this one: https://forums.virtualbox.org/viewtopic.php?f=7=70150 ** Attachment added: "Fixes compilation error with Linux 4.3" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1498145/+attachment/4478176/+files/vbox_linux-4.3.diff.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498145 Title: virtualbox-dkms 5.0.4-dfsg-2: virtualbox kernel module failed to build [SUPDrv-linux.c:488:8: error: void value not ignored as it ought to be] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1498145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253155] Re: Failure to validate module signature at boot time
Why is this bug set to Fix released for Trusty? This is still happening: $ uname -rv 3.13.0-53-generic #88-Ubuntu SMP Wed May 13 18:10:29 UTC 2015 $ modprobe xfs $ dmesg -T | tail -2 [Fri May 29 10:41:08 2015] Request for unknown module key 'Magrathea: Glacier signing key: 9aac900abd0220fb93c8be10f20d6973dab829f5' err -11 [Fri May 29 10:41:08 2015] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253155 Title: Failure to validate module signature at boot time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1253155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1395988] Re: apt-file cannot resolve mirror://mirrors.ubuntu.com/mirrors.txt
Workaround: create another sources.list file with http:// sources and have apt-file use it: $ apt-file --sources-list /etc/apt/sources.list.http update Btw, I stumbled across the mirror:// functionality only by accident on askubuntu.com - but could not find it documented. Any pointers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1395988 Title: apt-file cannot resolve mirror://mirrors.ubuntu.com/mirrors.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-file/+bug/1395988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067301] Re: ssh-add: Error reading response length from authentication socket.
** Bug watch added: Debian Bug tracker #738660 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660 ** Also affects: gnome-keyring (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738660 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067301 Title: ssh-add: Error reading response length from authentication socket. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1067301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1323089] Re: wpa_supplicant writes to syslog every 2 minutes
Same here, every 2 minutes with wpa_supplicant v2.3: $ sudo grep wpa_supplicant /var/log/messages | grep -v WPA | tail -3 Nov 14 11:24:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs failed: -33 Nov 14 11:26:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs failed: -33 Nov 14 11:28:32 acorn wpa_supplicant[942]: nl80211: send_and_recv-nl_recvmsgs failed: -33 No connectivity issues though, rekeying happens just fine every 10min: $ sudo grep wpa_supplicant /var/log/messages | grep WPA | tail -3 Nov 14 11:07:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed with [GTK=CCMP] Nov 14 11:17:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed with [GTK=CCMP] Nov 14 11:27:28 acorn wpa_supplicant[942]: wlan0: WPA: Group rekeying completed with [GTK=CCMP] Wifi chip: 04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1323089 Title: wpa_supplicant writes to syslog every 2 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1323089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398670] Re: eject: unable to eject, last error: Inappropriate ioctl for device
This just happened here with eject-2.1.5, but using eject -i off as suggested by zheoffec in comment #2 helped - thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/398670 Title: eject: unable to eject, last error: Inappropriate ioctl for device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eject/+bug/398670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1039887] Re: fstab does not honor /proc mount options
On Sat, 5 Jul 2014 at 17:18, KDEUSER56 wrote: So, how do I pass mount options to /proc instead? I need to enable acl support for /proc for security reasons. I don't think procfs supports ACLs: $ sudo mount -o remount,acl -v /proc mount: mount failed proc: unrecognized mount option acl or missing value As a workaround, use /etc/rc.local to remount /proc with specific mount options until this bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039887 Title: fstab does not honor /proc mount options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1039887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
FWIW, Fedora also ships plymouth by default but it is entirely possible to remove all plymouth packages w/o any hard dependencies. I was really surprised by this, given that RPM based distributions have a bad rep for the rpm hell. Not anymore, it seems... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954620] Re: SSH StrictModes does not work correctly
@Frank: does your home belong to your own per-user group? If so, StrictMode=yes might notice that and still allow login. In my case: christian@alice$ ls -ld $HOME drwx-- 24 christian christian 20480 Jul 23 03:44 /home/christian = Now, setting $HOME to 0720 will still allow login with public keys. But changing the ownership to e.g. :users makes StrictMode work. Note that sshd_config defines StrictModes only as specifies whether sshd(8) should check file modes and ownership of the user's files and home directory before accepting login. - i.e. there's no mention what exactly is checked. The source may be helpful on that. ** Bug watch added: Debian Bug tracker #119886 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=119886 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+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 954620] Re: SSH StrictModes does not work correctly
FWIW, http://bugs.debian.org/119886 deals with a similar issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+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 954620] Re: SSH StrictModes does not work correctly
FWIW, http://bugs.debian.org/119886 deals with a similar issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954620] Re: SSH StrictModes does not work correctly
@Frank: does your home belong to your own per-user group? If so, StrictMode=yes might notice that and still allow login. In my case: christian@alice$ ls -ld $HOME drwx-- 24 christian christian 20480 Jul 23 03:44 /home/christian = Now, setting $HOME to 0720 will still allow login with public keys. But changing the ownership to e.g. :users makes StrictMode work. Note that sshd_config defines StrictModes only as specifies whether sshd(8) should check file modes and ownership of the user's files and home directory before accepting login. - i.e. there's no mention what exactly is checked. The source may be helpful on that. ** Bug watch added: Debian Bug tracker #119886 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=119886 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954620 Title: SSH StrictModes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/954620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
On Sun, 30 Jun 2013 at 21:59, Steve Langasek wrote: This dependency: - is not a bug in plymouth. Well, no, but it's a bug in packages like mountall an cryptsetup which DEPEND on plymouth - that's the whole point of this bug. - is not up for debate. Oh? Why so? You do not have a properly functioning system if you have purged plymouth. You have a system that will fall on its face and fail to boot with no recovery options if there is ever any problem with any of the filesystems listed in /etc/fstab. Booting with init=/bin/sh is sufficient for a recovery system, I don't need plymouth for that. More to the point, relying on even more software for a recovery system makes no sense - if the system is heavily damaged, I should rely on as little software as possible to get it running again. A kernel and a working shell would be sufficient. With plymouth and its dependency tree this cannot be guaranteed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
On Sat, 29 Jun 2013 at 00:22, Steve Langasek wrote: ** Changed in: plymouth (Ubuntu) Status: Confirmed = Invalid Can you comment on this one, please? So far there has been no technical reasoning in #556372 as to why a Depends: plymouth should be warranted. OTOH, technical reasons have been given why Recommends: would be sufficient. Thanks, Christian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
** Also affects: plymouth (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/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
This bug is not meant to remove plymouth - if you feel that way, please file another bug. Speaking of which: this bug here is set to wontfix - do I need to file a new bug or can this be set to confirmed again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] Re: Don't autoload unneeded modules
Hah! Great, thanks! os-prober doesn't come with any documentation (I guess this warrants another bug :-)), never thought that it was to blame here. For the record, /usr/bin/os-prober calls /usr/lib/os-probes/init/10filesystems, where it does something like this: for fs in $FILESYSTEMS; do modprobe $fs done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] [NEW] Don't autoload unneeded modules
Public bug reported: Every time the kernel is upgraded and initrd is regenerated, some modules are loaded. These modules are not necessary for the system to run, take up memory and may even enlarge the attack surface when (security-)issues were to be found in these modules. How to reproduce on this Amazon EC2 instance: -- # lsmod [nothing] # dpkg-reconfigure linux-image-3.2.0-38-virtual Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual update-initramfs: Generating /boot/initrd.img-3.2.0-38-virtual run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-3.2.0-38-virtual Updating /boot/grub/menu.lst ... done run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual Generating grub.cfg ... cat: /boot/grub/video.lst: No such file or directory /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. Found linux image: /boot/vmlinuz-3.2.0-38-virtual Found initrd image: /boot/initrd.img-3.2.0-38-virtual /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. done # lsmod Module Size Used by btrfs 638248 0 zlib_deflate 26622 1 btrfs libcrc32c 12543 1 btrfs ufs78131 0 vfat 17308 0 msdos 17132 0 fat55605 2 vfat,msdos xfs 747494 0 ext2 67987 0 # grep -r ^[a-zA-Z] /etc/modules /etc/initramfs-tools/ /etc/modprobe.d/ | grep -v blacklist /etc/initramfs-tools/initramfs.conf:MODULES=list /etc/initramfs-tools/initramfs.conf:BUSYBOX=y /etc/initramfs-tools/initramfs.conf:COMPCACHE_SIZE= /etc/initramfs-tools/initramfs.conf:COMPRESS=gzip /etc/initramfs-tools/initramfs.conf:BOOT=local /etc/initramfs-tools/initramfs.conf:DEVICE= /etc/initramfs-tools/initramfs.conf:NFSROOT=auto /etc/initramfs-tools/update-initramfs.conf:update_initramfs=yes /etc/initramfs-tools/update-initramfs.conf:backup_initramfs=no # grep ^b /etc/modprobe.d/local.conf blacklist btrfs blacklist zlib_deflate blacklist libcrc32c blacklist crc32c blacklist ufs blacklist qnx4 blacklist hfsplus blacklist hfs blacklist minix blacklist ntfs blacklist vfat blacklist msdos blacklist fat blacklist dm_crypt -- Interestingly, none of these modules are included in the resulting initrd: # gzip -dc /boot/initrd* | cpio -it | grep kernel/ lib/modules/3.2.0-38-virtual/kernel/drivers lib/modules/3.2.0-38-virtual/kernel/drivers/video lib/modules/3.2.0-38-virtual/kernel/drivers/video/vga16fb.ko lib/modules/3.2.0-38-virtual/kernel/drivers/video/vgastate.ko lib/modules/3.2.0-38-virtual/kernel/drivers/video/vesafb.ko lib/modules/3.2.0-38-virtual/kernel/drivers/md lib/modules/3.2.0-38-virtual/kernel/drivers/md/dm-crypt.ko lib/modules/3.2.0-38-virtual/kernel/crypto lib/modules/3.2.0-38-virtual/kernel/crypto/xts.ko lib/modules/3.2.0-38-virtual/kernel/crypto/gf128mul.ko lib/modules/3.2.0-38-virtual/kernel/arch lib/modules/3.2.0-38-virtual/kernel/arch/x86 lib/modules/3.2.0-38-virtual/kernel/arch/x86/crypto lib/modules/3.2.0-38-virtual/kernel/arch/x86/crypto/aes-i586.ko 10837 blocks Note: executing update-initramfs -u -k `uname -r` alone does NOT load these modules! Workaround: Running rmmod btrfs zlib_deflate libcrc32c ufs vfat msdos fat xfs ext2 after every kernel upgrade. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Every time the kernel is upgraded and initrd is regenerated, some modules are loaded. These modules are not necessary for the system to run, take up memory and may even enlarge the attack surface when (security-)issues were to be found in these modules. How to reproduce on this Amazon EC2 instance: -
[Bug 1125597] Re: Don't autoload unneeded modules
apport information ** Tags added: apport-collected ** Description changed: Every time the kernel is upgraded and initrd is regenerated, some modules are loaded. These modules are not necessary for the system to run, take up memory and may even enlarge the attack surface when (security-)issues were to be found in these modules. How to reproduce on this Amazon EC2 instance: -- # lsmod [nothing] # dpkg-reconfigure linux-image-3.2.0-38-virtual Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual update-initramfs: Generating /boot/initrd.img-3.2.0-38-virtual run-parts: executing /etc/kernel/postinst.d/x-grub-legacy-ec2 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-3.2.0-38-virtual Updating /boot/grub/menu.lst ... done run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.2.0-38-virtual /boot/vmlinuz-3.2.0-38-virtual Generating grub.cfg ... cat: /boot/grub/video.lst: No such file or directory /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. Found linux image: /boot/vmlinuz-3.2.0-38-virtual Found initrd image: /boot/initrd.img-3.2.0-38-virtual /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. /usr/sbin/grub-probe: warn: disk does not exist, so falling back to partition device /dev/xvda1. done # lsmod Module Size Used by btrfs 638248 0 zlib_deflate 26622 1 btrfs libcrc32c 12543 1 btrfs ufs78131 0 vfat 17308 0 msdos 17132 0 fat55605 2 vfat,msdos xfs 747494 0 ext2 67987 0 # grep -r ^[a-zA-Z] /etc/modules /etc/initramfs-tools/ /etc/modprobe.d/ | grep -v blacklist /etc/initramfs-tools/initramfs.conf:MODULES=list /etc/initramfs-tools/initramfs.conf:BUSYBOX=y /etc/initramfs-tools/initramfs.conf:COMPCACHE_SIZE= /etc/initramfs-tools/initramfs.conf:COMPRESS=gzip /etc/initramfs-tools/initramfs.conf:BOOT=local /etc/initramfs-tools/initramfs.conf:DEVICE= /etc/initramfs-tools/initramfs.conf:NFSROOT=auto /etc/initramfs-tools/update-initramfs.conf:update_initramfs=yes /etc/initramfs-tools/update-initramfs.conf:backup_initramfs=no # grep ^b /etc/modprobe.d/local.conf blacklist btrfs blacklist zlib_deflate blacklist libcrc32c blacklist crc32c blacklist ufs blacklist qnx4 blacklist hfsplus blacklist hfs blacklist minix blacklist ntfs blacklist vfat blacklist msdos blacklist fat blacklist dm_crypt -- Interestingly, none of these modules are included in the resulting initrd: # gzip -dc /boot/initrd* | cpio -it | grep kernel/ lib/modules/3.2.0-38-virtual/kernel/drivers lib/modules/3.2.0-38-virtual/kernel/drivers/video lib/modules/3.2.0-38-virtual/kernel/drivers/video/vga16fb.ko lib/modules/3.2.0-38-virtual/kernel/drivers/video/vgastate.ko lib/modules/3.2.0-38-virtual/kernel/drivers/video/vesafb.ko lib/modules/3.2.0-38-virtual/kernel/drivers/md lib/modules/3.2.0-38-virtual/kernel/drivers/md/dm-crypt.ko lib/modules/3.2.0-38-virtual/kernel/crypto lib/modules/3.2.0-38-virtual/kernel/crypto/xts.ko lib/modules/3.2.0-38-virtual/kernel/crypto/gf128mul.ko lib/modules/3.2.0-38-virtual/kernel/arch lib/modules/3.2.0-38-virtual/kernel/arch/x86 lib/modules/3.2.0-38-virtual/kernel/arch/x86/crypto lib/modules/3.2.0-38-virtual/kernel/arch/x86/crypto/aes-i586.ko 10837 blocks Note: executing update-initramfs -u -k `uname -r` alone does NOT load these modules! Workaround: - Running rmmod btrfs zlib_deflate libcrc32c ufs vfat msdos fat xfs ext2 - after every kernel upgrade. + Running rmmod btrfs zlib_deflate libcrc32c ufs vfat msdos fat xfs ext2 after every kernel upgrade. + --- + AcpiTables: + + AlsaDevices: + total 0 + crw-rw---T 1 root audio 116, 1 Feb 8 15:01 seq +
[Bug 1125597] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1125597/+attachment/3529253/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1125597/+attachment/3529254/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1125597/+attachment/3529255/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1125597/+attachment/3529256/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1125597] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1125597/+attachment/3529257/+files/UdevLog.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1125597 Title: Don't autoload unneeded modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1125597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045706] Re: dkms module fails to build with: error: implicit declaration of function ‘get_io_context’
** Bug watch added: Debian Bug tracker #696383 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696383 ** Also affects: iscsitarget (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696383 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045706 Title: dkms module fails to build with: error: implicit declaration of function ‘get_io_context’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1045706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071613] [NEW] JFS module missing
Public bug reported: After upgrading from Ubuntu 12.04 to 12.10, the module for the JFS filesystem seems to be missing from the new kernel, although its config states that JFS has been enabled: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.10 Release:12.10 Codename: quantal $ cat /proc/version Linux version 3.5.0-17-generic (buildd@roseapple) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 $ grep JFS /boot/config-$(uname -r) CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y CONFIG_JFS_SECURITY=y # CONFIG_JFS_DEBUG is not set CONFIG_JFS_STATISTICS=y $ modprobe -l | grep jfs empty $ find /lib/modules/$(uname -r) | grep jfs empty ** Affects: linux (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/1071613 Title: JFS module missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071613] Re: JFS module missing
No, I don't. But looking at Ubuntu 12.04 I see now that linux-image- virtual (3.2.0-33) did not contain the JFS module as well. apt-cache search jfs does not return any kernel images. I guess listing all the modules provided by linux-image-extra would make its description overly long (Are there any hidden tags for apt to parse, so that apt-cache search jfs would match on linux-image-extra but apt-cache show linux-image-extra would not show the entire module list?) So yes, installing linux-image-extra-virtual does fix this issue. Oh, and if I'd only used apt-file before filing this bug: $ apt-file search jfs.ko linux-image-3.5.0-17-lowlatency: /lib/modules/3.5.0-17-lowlatency/kernel/fs/jfs/jfs.ko linux-image-extra-3.5.0-17-generic: /lib/modules/3.5.0-17-generic/kernel/fs/jfs/jfs.ko (Btw, ufs.ko is provided by linux-image-3.5.0-17-generic, but not jfs.ko? Wow :-)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071613 Title: JFS module missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1071613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1039887] [NEW] fstab does not honor /proc mount options
Public bug reported: Passing mount options (here: hidepid=2) for /proc via /etc/fstab does not seem to work: $ grep /proc /etc/fstab /etc/mtab /proc/mounts /etc/fstab:proc /proc proc nodev,noexec,nosuid,hidepid=2 0 0 /etc/mtab:proc /proc proc rw,noexec,nosuid,nodev 0 0 /proc/mounts:proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 Also, /etc/mtab and /proc/mounts are out of sync - are there plans to link /etc/mtab against /proc/mounts? (Note: I'm not particularly in favor of bug 906293, propsing yet another file to the mix). The system is a fully patched Ubuntu 12.04.1 LTS (i686) in an Amazon EC2 virtual machine. Workaround: add the following line to /etc/rc.local: mount -o remount,hidepid=2 /proc ** Affects: mountall (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/1039887 Title: fstab does not honor /proc mount options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1039887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
** Changed in: cryptsetup Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is No available ptys)
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936667 Title: Upstart early job logging causes boot failure for systems with no initramfs (error is No available ptys) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/936667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 987993] Re: 'Test WP failed, assume Write Enabled' messages on console
*** This bug is a duplicate of bug 925760 *** https://bugs.launchpad.net/bugs/925760 ** This bug has been marked a duplicate of bug 925760 Constant warnings from the kernel: Test WP failed, assume Write Enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987993 Title: 'Test WP failed, assume Write Enabled' messages on console To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/987993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991395] Re: syslog fills with messages due to empty SD card slot.
*** This bug is a duplicate of bug 925760 *** https://bugs.launchpad.net/bugs/925760 ** This bug has been marked a duplicate of bug 925760 Constant warnings from the kernel: Test WP failed, assume Write Enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991395 Title: syslog fills with messages due to empty SD card slot. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/991395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925760] Re: Constant warnings from the kernel: Test WP failed, assume Write Enabled
Still present with3.2.0-24-generic. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=43191 The workaround from comment #8 works here (Lenovo Ideapad S10), thanks nealmcb :) ** Bug watch added: Linux Kernel Bug Tracker #43191 http://bugzilla.kernel.org/show_bug.cgi?id=43191 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=43191 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925760 Title: Constant warnings from the kernel: Test WP failed, assume Write Enabled To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/925760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
Whooha, language! And I think they fixed it, albeit in a weird way: CONFIG_TASK_DELAY_ACCT is enabled in the kernel config, but the feature is still disabled unless the kernel is booted with delayacct as a boot parameter, see my comment above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493156 Title: Please enable CONFIG_TASK_DELAY_ACCT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/493156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Feel free to attach the resulting .deb (if one is allowed to attach binary files). Maybe users will be more comfortable doing this on their own, so they see what they're installing. And yes, the deb works for all Ubuntu versions. Also yes: the equivs version will have no functionality whatsoever but to satisfy the Depend: plymouth from various packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
@Oliver: this can be achieved via equivs, see my comment #16. This creates a dummy package (with Provides: plymouth) that will fullfil this depenancy. Works like a charm here :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is No available ptys)
Booting Linux 3.3.0-rc5 (vanilla, no initramfs) with upstart-1.4-0ubuntu9 (from James' upstart-job-logging PPA) went fine, even w/o the --no-log kernel option. However, at the end of the booting process, syslog says: kernel: [ 17.913723] init: No available ptys kernel: [ 17.913826] init: Failed to create pty - disabling logging kernel: [ 17.915596] init: Temporary process spawn error: No such file or directory kernel: [ 17.929426] init: No available ptys kernel: [ 17.929531] init: Failed to create pty - disabling logging kernel: [ 17.931403] init: Temporary process spawn error: No such file or directory kernel: [ 17.939599] init: No available ptys kernel: [ 17.939687] init: Failed to create pty - disabling logging kernel: [ 17.947603] init: Temporary process spawn error: No such file or directory kernel: [ 17.976511] init: plymouth-stop pre-start process (605) terminated with status 1 The Failed to create pty - disabling logging message is also printed on the local console and repeated every now and then. Maybe this (debugging?) information can be omitted in the final version? $ ls -l /dev/ptmx crw-rw-rw- 1 root tty 5, 2 Mar 7 01:34 /dev/ptmx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/936667 Title: Upstart early job logging causes boot failure for systems with no initramfs (error is No available ptys) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
I still don't understand what the _technical_ reason is not to switch to Recommends: rather than Depends: as it is now. If plymouth would be recommended only - nothing would change, since Install-Recommends is on by default and everything would just continue to work. But the sysadmin is free to uninstall plymouth, w/o going through these hoops of custom mountall packages and equivs dummy packages. Plymouth is out for...some years now and it's still hindering proper boot-related debugging now and then and it's still uneccesary for headless systems. Please explain why plymouth cannot be set to Recommended to the affected packages (mountall, cyrptsetup, ...). Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 14644] Re: Runlevel 2 starting GUI
The attached patch will prevent lxdm from starting in runlevel 2 (and 1, don't know why lxdm is supposed to start in RL 1). One has to edit their /etc/init/*dm.conf for the desktop manager they're using. But I agree with James here: there's no reason to start X11 in runlevel 2. Just because some-other-distribution does it, did not seem to be a valid excuse before. And when some-other-distribution starts X11 in RL 5 and users find it practical, I'd say: go for it. But not because of a policy but because of user's demand. To be more specific: disable X11 in RL 2 and set the default RL to 5. Nobody would notice and power-users can just alter the default runlevel or pass 2 to the bootloader and still have a functional multi-user system but w/o X11. ** Patch added: Don't start lxdm in runlevel 1,2 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/14644/+attachment/2567383/+files/init.diff ** Changed in: xorg (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/14644 Title: Runlevel 2 starting GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/14644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Why has this been set to WONTFIX again? Has a consensus been reached already? From looking at the comments here, I doubt that. I still think Depends is too hard and think Recommends is a better suit for this. As APT::Install-Recommends=true is the default, nothing would change for the general users. Powerusers with need to the console can opt to uninstall it w/o breaking their system and w/o the equivs hack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Why has this been set to WONTFIX again? Has a consensus been reached already? From looking at the comments here, I doubt that. I still think Depends is too hard and think Recommends is a better suit for this. As APT::Install-Recommends=true is the default, nothing would change for the general users. Powerusers with need to the console can opt to uninstall it w/o breaking their system and w/o the equivs hack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835833] Re: spurious syslog error because of use of -w on boot [rpcbind.xdr / portmap.xdr : errno 2 (no such file)]
** Bug watch added: Debian Bug tracker #620800 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800 ** Also affects: rpcbind (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620800 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/835833 Title: spurious syslog error because of use of -w on boot [rpcbind.xdr / portmap.xdr : errno 2 (no such file)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/835833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608701] Re: vino establishes a HTTP connection to check connectivity
Yesterday I found this in my log: Aug 1 12:39:33 len IN= OUT=eth1 MAC= SRC=192.168.0.107 DST=189.38.80.51 LEN=60 TOS=10 PREC=0x00 TTL=64 ID=43445 CE DF PROTO=TCP SPT=39385 DPT=22 SEQ=3475551532 ACK=0 WINDOW=5840 SYN URGP=0 This 189.38.80.51 maps back to kamotini.kinghost.net but is also the address for blog.jorgepereira.com.br, which is listed in /usr/share/vino/webservices. Guys girls, this is unacceptable. vino must not contact any random webservices w/o asking the user first. No matter how trusted these webservices are supposed to be or that no sensitive information will be transferred. Please reconsider and disable these services ASAP until a viable solution is found to let NetworkManager know if an _incoming_ port is open or not. Thanks, C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/608701 Title: vino establishes a HTTP connection to check connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/608701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608701] Re: vino establishes a HTTP connection to check connectivity
Will this be fixed in 10.04 (LTS!) too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/608701 Title: vino establishes a HTTP connection to check connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/608701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770430] Re: module cachefiles missing from linux-image-virtual
For the record: I still find it odd/wrong that /etc/init.d/cachefilesd is messing with module loading at all (/etc/init.d/network does not load network drivers...), but that'd have to be reported against the cachefilesd package, I suppose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770430 Title: module cachefiles missing from linux-image-virtual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/770430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793387] Re: chronyd won't start with linux 3.x
Out of curiosity: why does commit ec7d302a6ca9e7974a05d338267b40491a1d7abb close #628919 (dup of #484499, syntax errors in /etc/default/grub)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793387 Title: chronyd won't start with linux 3.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/793387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793387] Re: chronyd won't start with linux 3.x
This has been fixed upstream: http://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony- dev/2011/06/msg6.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793387 Title: chronyd won't start with linux 3.x -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 675087] Re: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 659649 *** https://bugs.launchpad.net/bugs/659649 ** This bug has been marked a duplicate of bug 659649 package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/675087 Title: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 666675] Re: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 659649 *** https://bugs.launchpad.net/bugs/659649 ** This bug has been marked a duplicate of bug 659649 package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/75 Title: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659649] Re: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Is this still happening in 11.04? Can you run sh -x /var/lib/dpkg/info/chrony.postinst and see why it fails? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659649 Title: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659649] Re: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Computer freezes / issues with Unity surely belong to another bug report, right? :-) If chrony is running fine in 10.10 though, that's good news... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659649 Title: package chrony 1.23-7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793387] [NEW] chronyd won't start with linux 3.x
Public bug reported: Binary package hint: chrony This is a copy of Debian's #628919. With Linux 3.0-rc1, this happens: $ uname -r 3.0.0-rc1+ $ sudo /usr/sbin/chronyd -d sys_linux.c:688:(get_version_specific_details)[06-06:52:55] Initial txc.tick=1 txc.freq=0 (0.) txc.offset=0 = hz=100 shift_hz=7 sys_linux.c:704:(get_version_specific_details)[06-06:52:55] set_config_hz=0 hz=100 shift_hz=7 basic_freq_scale=1.2800 nominal_tick=1 slew_delta_tick=833 max_tick_bias=1000 sys_linux.c:742:(get_version_specific_details)[06-06:52:55] Linux kernel major=3 minor=0 patch=0 sys_linux.c:823:(get_version_specific_details)[06-06:52:55] Fatal error : Kernel's major version not supported yet, sorry ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Affects: chrony (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #628919 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628919 ** Also affects: chrony (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628919 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793387 Title: chronyd won't start with linux 3.x -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 458061] Re: openntpd no longer installs -/etc/openntpd/ntpd.conf: Permission denied
Still there on 10.04.2. Disabling apparmor (boot with security=) helped. Rebooting with apparmor enabled again (security=apparmor) still allows openntpd to run. So, this looks like an apparmor related problem - openntpd can't do much about it (but its install scripts can). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/458061 Title: openntpd no longer installs -/etc/openntpd/ntpd.conf: Permission denied -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496422] Re: cachefilesd not starting with CONFIG_CACHEFILES=y
bump! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496422 Title: cachefilesd not starting with CONFIG_CACHEFILES=y -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770430] Re: module cachefiles missing from linux-image-virtual
With2.6.38-9-virtual from -proposed the 'cachefiles' module is there and cachefilesd is working again. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770430 Title: module cachefiles missing from linux-image-virtual -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
In 10.04.2 linux-image-server depends on linux-image-generic-pae which in turn depends on linux-image-2.6.32-21-generic-pae which has TASK_DELAY_ACCT enabled. However, be sure to pass delayacct to your boot options, otherwise it won't work (sigh...) Christian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493156 Title: Please enable CONFIG_TASK_DELAY_ACCT -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584800] Re: webdav: DBus error / org.freedesktop.DBus.Error.NoReply
This still happens in Ubuntu 11.04 nautilus 2.32.2.1 ** Summary changed: - connect to server--(using webdav(http))--failed to open big folder + webdav: DBus error / org.freedesktop.DBus.Error.NoReply ** Summary changed: - webdav: DBus error / org.freedesktop.DBus.Error.NoReply + nautilus: DBus error / org.freedesktop.DBus.Error.NoReply when using webdav ** Changed in: ubuntu Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584800 Title: nautilus: DBus error / org.freedesktop.DBus.Error.NoReply when using webdav -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
FWIW, the equivs package[0] from comment #16 is still working, no need to upgrade every time a new mountall/cryptsetup/whatnot version is released. cheers, C. [0] http://nerdbynature.de/bits/LP-506297/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/556372 Title: Please remove the plymouth dependency from mountall / cryptsetup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506297] Re: Graphical Ubuntu logo enabled on servers, no more login prompt
@Maintainers, please reconsider. I just had a real usecase here where some box just hung and the last message I was seeing came from plymouth. I booted with ro nosplash noplymouth INIT_VERBOSE=yes init=/sbin/init -v, but it still hung. See plymouth-1.png under: http://nerdbynature.de/bits/LP-506297/ So I removed plymouth via equivs (control file installable .deb on URL above) and it turned out it wasn't plymouth-related at all. As a bonus, the screen does not clear any more after boot, so I can see all the boot messages (if one had to plugin a display device :)) Again, please tell what plymouth would be good for in a Ubuntu _server_ installation. Last I checked, Ubuntu still supports server installations, does it not? Options: 1) remove plymouth altogether on Ubuntu server (until it does something useful) 2) make plymouth Recommends, not Depends 3) ? Thanks for listening, C. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/506297 Title: Graphical Ubuntu logo enabled on servers, no more login prompt -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607632] Re: DPKG is very slow when using BTRFS
Thanks Ferdinand, this helped a lot. Quick PoC with installing/purging a samba4 (13.5MB): # grep btrfs /proc/mounts uname -r /dev/sda2 / btrfs rw,nodev,noatime 0 0 2.6.35-27-generic # sysctl -w vm.drop_caches=3 # time (LD_PRELOAD=/usr/local/lib/libnosync.so apt-get -y install samba4 sync) real0m31.115s user0m1.620s sys 0m3.150s # time (LD_PRELOAD=/usr/local/lib/libnosync.so apt-get -y purge samba4 sync) real0m30.940s user0m1.370s sys 0m2.690s # sysctl -w vm.drop_caches=3 # time (apt-get install samba4 sync) real0m41.611s user0m1.530s sys 0m3.250s # time (apt-get purge -y samba4 sync) real0m40.015suser0m1.390s sys 0m2.850s And this is reproducible: so it's always 30 or 31 seconds with libnosync and always ~10sec more w/o libnosync. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607632 Title: DPKG is very slow when using BTRFS -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
Here too: linux-image-2.6.32-28-generic (2.6.32-28.55) with 'delayacct' running fine, iotop working too. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493156 Title: Please enable CONFIG_TASK_DELAY_ACCT -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
Tim, If I understand your comment correctly, you're going to enable CONFIG_TASK_DELAY_ACCT in the config but the actual delay accounting will be disabled unless booted with delayacct? What happened to Leann's RFC[0] and all the comments in this bug? Why introduce another bootoption for that? What was the reasoning here? Also, I don't approve of your lemming comparision[1]: I merely mentioned that other distributions have enabled this feature and are apparently not reporting any downsides - I did not mention this to imply that we should blindly follow others. Thanks, Christian. [0] https://lists.ubuntu.com/archives/kernel-team/2010-June/011238.html [0] https://lists.ubuntu.com/archives/kernel-team/2010-June/011240.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/493156 Title: Please enable CONFIG_TASK_DELAY_ACCT -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 493156] Re: Please enable CONFIG_TASK_DELAY_ACCT
Wow. I just came over from #532490 to see that bugs like these (wishlist, really?) are being happily set to WONTFIX. I still fail to understand the reasoning behind that decision and I hope this will be revisited. Again: - Iotop doesn't work properly w/o CONFIG_TASK_DELAY_ACCT - There is no measurable overhead when enabled. I tried to measure in #532490, comment #6, but no winner there. @Tim/Andy: please elaborate on the performance hit with this option enabled, I'm really curious if this is still valid for current kernels and which usecase has been tested to determine this hit. - The nodelayacct can be used to disable delay accounting for those usecases where an actual performance hit can be seen. - All other major Linux distributions are doing it, only Ubuntu stands out :-\ -- Please enable CONFIG_TASK_DELAY_ACCT https://bugs.launchpad.net/bugs/493156 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 440522] Re: Kernel modules not compiled (Stats, NFS, AFS, etc)
@Leann: can you change the importance from wishlist back to something more serious? Without the *_FSCACHE options, the cachefilesd package is pretty much useless :-\ -- Kernel modules not compiled (Stats, NFS, AFS, etc) https://bugs.launchpad.net/bugs/440522 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 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
If plymouth is really needd and actually doing something useful besides providing fancy booting, then its package desciption should be changed to something more verbose (a bug against plymouth should be filed, I guess). However, when following the package page for plymouth I eventually end up on the freedesktop.org page where it's all about graphics and splashes. But again, as Ubuntu is still shipping -server flavours, I fail to see the point why any package from the x11 section would be of priority required. Why can't it be a dependency for ubuntu-desktop, as in: I want a desktop system, with fancy bootup and so on. It's enough of a burden for all the headless admin (hihi) out there fiddling with bootparams to get to see exactly when the box stopped booting when something has gone wrong. -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 532490] Re: CONFIG_TASK_DELAY_ACCT not enabled in kernel
In the URL above it's mentioned that it would cause a performance hit and has therefore been disabled in the config. However, delay accounting can be disabled by passing nodelayacct as a boot parameter (see Documentation/accounting/delay-accounting.tx). I have not seen actual numbers confirming this performance hit - and I'd like to have TASK_DELAY_ACCT, so that things like iotop (a helpful tool that actually *helps* tracking I/O performance issues!) are useful again. -- CONFIG_TASK_DELAY_ACCT not enabled in kernel https://bugs.launchpad.net/bugs/532490 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 532490] Re: CONFIG_TASK_DELAY_ACCT not enabled in kernel
I did a really quick test: bonnie++ [0] on a SunV40z, 16GB RAM with CONFIG_TASK_DELAY_ACCT=y and another test with nodelayacct: http://nerdbynature.de/bits/LP-532490/ AFAICT bonnie++ was slightly faster with nodelayacct for ext4, but slightly slower for btrfs. Latencies seem to be slightly lower (good!) for nodelayacct, but not always. I could not really find out a winner here. Maybe if you squint in the right way one may see something else. Given that, I still think that TASK_DELAY_ACCT=y is really important to have. Just look around: every time disk I/O + Linux + performance comes up, one is advised to use iotop. It'd good if Ubuntu would provide the envrionment for such analysis. Thanks, Christian. [0] Yeah, I know. If anyone has an actual usecase where the performance hit for TASK_DELAY_ACCT=y vs. TASK_DELAY_ACCT=n can be seen, please let me know! -- CONFIG_TASK_DELAY_ACCT not enabled in kernel https://bugs.launchpad.net/bugs/532490 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 532490] Re: CONFIG_TASK_DELAY_ACCT not enabled in kernel
Oh, and openSuSE 11.3, Fedora 13 and Debian's 2.6.32 kernel package have it enabled too: CONFIG_TASKSTATS=y CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y Dunno about Vista, though :-) -- CONFIG_TASK_DELAY_ACCT not enabled in kernel https://bugs.launchpad.net/bugs/532490 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 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Yet anouther workaround: instead of patching (Thanks, Ingo!) mountall and all the other packages depending on plymouth now, one could install plymouth-pseudo package. This way the dependency would be satisfied but one can still receive updates on the other Ubuntu packages: $ apt-get install equivs $ equivs-control plymouth-dummy $ vi plymouth-dummy [...] $ grep -v ^\# plymouth-dummy Section: misc Priority: optional Standards-Version: 3.6.2 Package: plymouth-dummy Provides: plymouth Version: 1.0 Description: plymouth-dummy, see LP# 556372 $ equivs-build plymouth-dummy $ ls -lgo plymouth-dummy* -rw-r- 1 826 2010-04-08 16:45 plymouth-dummy -rw-r--r-- 1 2040 2010-04-08 16:47 plymouth-dummy_1.0_all.deb $ dpkg -i plymouth-dummy_1.0_all.deb Maybe the Version: tag has to be altered at some point later (when e.g. mountall depends on plymouth-2.0 or something). I did this here and it's running fine so far. Of course, if at some point they add some magical functional dependency to plymouth, one would be forced to install the real plymouth eventually. -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Oh, and for libdrm is the interface to the kernel rendering manager - yes, for desktop systems that may be valid. But there's still the Ubuntu server installation. Less dependencies, less code - less (security) issues. -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 355040] Re: cpufreq directory missing
** Package changed: ubuntu = linux (Ubuntu) -- cpufreq directory missing https://bugs.launchpad.net/bugs/355040 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 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Setting to confirmed as it seems to affect other people as well. Please don't just set to WONTFIX if discussion is still ongoing. ** Changed in: mountall (Ubuntu) Status: Won't Fix = Confirmed -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 559756] [NEW] Please upgrade to jfsutils 1.1.14
Public bug reported: Binary package hint: jfsutils Jfsutils v1.1.14 is out since 2009-04-06 (http://jfs.sourceforge.net). Although jfsutils (and JFS) is not actively developed, it is still maintained and important bugfixes have been commited to newer versions, which might help remediate currently open bugreports for jfsutils. Please consider upgrading. Thanks, Christian. ** Affects: jfsutils (Ubuntu) Importance: Undecided Status: New -- Please upgrade to jfsutils 1.1.14 https://bugs.launchpad.net/bugs/559756 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 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
Plymouth merely regulates access to the system console in cases of filesystem decryption and error Again, my system runs fine w/o plymouth. Also, why is plymouth marked optional then when it appears to be required? And what about the libraries plymouth drags in, is libdrm-* really required to regulating access to the system console? -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 556372] [NEW] Please remove the plymouth dependency from mountall / cryptsetup
Public bug reported: Binary package hint: mountall I noticed that mountall (and cryptsetup) depends on plymouth now. Whatever plymouth is doing or not doing, my headless system is booting fine without plymouth (dpkg --force-depends -P plymouth), yet all disks (local, NFS) are mounted and cryptsetup is setting up encrypted swap as it used to. IMHO the Depends: plymouth is too hard and should be replaced with Recommends: or Suggests: for the following reasons: - Headless systems won't ever see what plymouth is doing (graphical boot animation) - Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily adding code to the installation- Mountall is of Priority: required while plymouth is optional. The Depends: makes plymouth essentially required as well and cannot be uninstalled w/o --force options. Please reconsider this dependency. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu lucid (development branch) Release:10.04 Codename: lucid # dpkg -l | egrep 'mountall|cryptsetup' | cut -c1-90 ii cryptsetup 2:1.1.0~rc2-1ubuntu13 ii mountall2.10 # apt-cache show plymouth | egrep 'Vers|Depe' Version: 0.8.1-4ubuntu1 Depends: libc6 (= 2.8), libdrm-intel1 (= 2.4.9), libdrm-nouveau1 (= 2.4.11-1ubuntu1~), libdrm-radeon1 (= 2.4.17), libdrm2 (= 2.4.3), libplymouth2 (= 0.8.1-4ubuntu1), upstart-job, udev (= 149-2), mountall (= 2.0) ** Affects: mountall (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: mountall I noticed that mountall (and cryptsetup) depends on plymouth now. Whatever plymouth is doing or not doing, my headless system is booting fine without plymouth (dpkg --force-depends -P plymouth), yet all disks (local, NFS) are mounted and cryptsetup is setting up encrypted swap as it used to. IMHO the Depends: plymouth is too hard and should be replaced with Recommends: or Suggests: for the following reasons: - Headless systems won't ever see what plymouth is doing (graphical boot animation) - Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily adding code to the installation- Mountall is of Priority: required while plymouth is optional. The Depends: makes plymouth essentially required as well and cannot be uninstalled w/o --force options. Please reconsider this dependency. + + # lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description:Ubuntu lucid (development branch) + Release:10.04 + Codename: lucid + + # dpkg -l | egrep 'mountall|cryptsetup' | cut -c1-90 + ii cryptsetup 2:1.1.0~rc2-1ubuntu13 + ii mountall2.10 + + # apt-cache show plymouth | egrep 'Vers|Depe' + Version: 0.8.1-4ubuntu1 + Depends: libc6 (= 2.8), libdrm-intel1 (= 2.4.9), libdrm-nouveau1 (= 2.4.11-1ubuntu1~), libdrm-radeon1 (= 2.4.17), libdrm2 (= 2.4.3), libplymouth2 (= 0.8.1-4ubuntu1), upstart-job, udev (= 149-2), mountall (= 2.0) -- Please remove the plymouth dependency from mountall / cryptsetup https://bugs.launchpad.net/bugs/556372 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 199047] Re: Poor quality sound on Aluminium iMac
If the bug is still about poor sound quality (and not about sound not working at all, that's a different issue): I managed to get sound working with options snd-hda-intel model=imac24 (for this iMac8,1) but it's lacking any bass. Switching through the different hardware-profiles (gnome-volume-control) did not do any good. FWIW, I've uploaded my ALSA information: http://www.alsa-project.org/db/?f=cd54f33bc07a2b573e3ab1cdcbe4946653bc93ad I'm running Lucid (just upgraded to 2.6.32-19-generic); running vanilla 2.6.34-rc3 with the Ubuntu .config applied did not help. Has this one been forwarded upstream (ALSA? snd-hda-intel maintainer?) already? ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- Poor quality sound on Aluminium iMac https://bugs.launchpad.net/bugs/199047 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 199047] Re: Poor quality sound on Aluminium iMac
Btw, why is this tagged wishlist? It's clearly a serious bug - it's like having no sound at all. It's sound coming out of the speaker but it's not really usable. So, no multimedia for all the iMac users out there :-\ -- Poor quality sound on Aluminium iMac https://bugs.launchpad.net/bugs/199047 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 367751] Re: [SRU] irqstats is confused by 2.6.24 /proc/interrupts
The bug has been fixed for 8.04, although the changelog is missing the LP#: munin (1.2.5-2ubuntu3.2) hardy; urgency=low * Added patch to fix irqstats using the 2.6.24 kernel. -- Chuck Short zul...@ubuntu.com Tue, 30 Jun 2009 10:34:39 -0400 And /usr/share/munin/plugins/irqstats is indeed working correctly with 2.6.24 now. ** Changed in: munin (Ubuntu Hardy) Status: New = Fix Released -- [SRU] irqstats is confused by 2.6.24 /proc/interrupts https://bugs.launchpad.net/bugs/367751 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- 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 367751] Re: [SRU] irqstats is confused by 2.6.24 /proc/interrupts
Whoops, too soon: when I looked at the changelog, I forgot that this is still Chuck's version of munin-node[0] that is installed on my system. So no, the bug is still present in hardy/8.04 and it would be most helpful if someone was able to upload Chuck's version[1] to the official archives. Later Ubuntu versions seem to be fine, as the bug has been fixed upstream. [0] http://launchpad.net/~zulcss/+archive/ppa [1] https://launchpad.net/~zulcss/+archive/ppa/+files/munin-node_1.2.5-2ubuntu3.2_all.deb ** Changed in: munin (Ubuntu Hardy) Status: Fix Released = Fix Committed -- [SRU] irqstats is confused by 2.6.24 /proc/interrupts https://bugs.launchpad.net/bugs/367751 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in ubuntu. -- 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 367751] Re: [SRU] irqstats is confused by 2.6.24 /proc/interrupts
The bug has been fixed for 8.04, although the changelog is missing the LP#: munin (1.2.5-2ubuntu3.2) hardy; urgency=low * Added patch to fix irqstats using the 2.6.24 kernel. -- Chuck Short zul...@ubuntu.com Tue, 30 Jun 2009 10:34:39 -0400 And /usr/share/munin/plugins/irqstats is indeed working correctly with 2.6.24 now. ** Changed in: munin (Ubuntu Hardy) Status: New = Fix Released -- [SRU] irqstats is confused by 2.6.24 /proc/interrupts https://bugs.launchpad.net/bugs/367751 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 367751] Re: [SRU] irqstats is confused by 2.6.24 /proc/interrupts
Whoops, too soon: when I looked at the changelog, I forgot that this is still Chuck's version of munin-node[0] that is installed on my system. So no, the bug is still present in hardy/8.04 and it would be most helpful if someone was able to upload Chuck's version[1] to the official archives. Later Ubuntu versions seem to be fine, as the bug has been fixed upstream. [0] http://launchpad.net/~zulcss/+archive/ppa [1] https://launchpad.net/~zulcss/+archive/ppa/+files/munin-node_1.2.5-2ubuntu3.2_all.deb ** Changed in: munin (Ubuntu Hardy) Status: Fix Released = Fix Committed -- [SRU] irqstats is confused by 2.6.24 /proc/interrupts https://bugs.launchpad.net/bugs/367751 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 440522] Re: Kernel modules not compiled (Stats, NFS, AFS, etc)
FWIW, the experimemental tag has been removed in mainline: http://tinyurl.com/y8h8yq6 @Pete: please elaborate if you're changing bugs to WONTFIX. ** Changed in: linux (Ubuntu) Status: Won't Fix = Confirmed -- Kernel modules not compiled (Stats, NFS, AFS, etc) https://bugs.launchpad.net/bugs/440522 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 440522] Re: Kernel modules not compiled (Stats, NFS, AFS, etc)
@Leann: Perhaps it's too late now, I should've double checked the moment you were replying: you're saying that the *_FSCACHE modules cannot be enabled in an Ubuntu kernel, because they depend on EXPERIMENTAL. While I'm currently trying to convince[0] upstream to remove the EXPERIMENTAL flag from NFS_FSCACHE, I just noticed that both CONFIG_FSCACHE and CONFIG_CACHEFILES is already enabled in Karmic - which are both marked EXPERIMENTAL (since CACHEFILES depends on FSCACHE). So, I just have to ask: how comes? From looking at a Karmic config (2.6.31-20-server) I can see that there are other options, which are enabled as well, despite the fact that they depend on EXPERIMENTAL. Also, Ubuntu is currently shipping the userspace cachefilesd daemon - which is unusable, without the proper kernel support. So, if anyone from the kernel team reads this - please reconsider and enable the missing *_FSCACHE options. Thanks, Christian. [0] http://marc.info/?l=linux-nfsm=126684776217594w=2 -- Kernel modules not compiled (Stats, NFS, AFS, etc) https://bugs.launchpad.net/bugs/440522 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
