Public bug reported:
udev(7) is wrong: It says, that system rules are in /usr/lib/udev/rules.d but
obviously there are no udev rules!
Should be corrected to /lib/udev/rules.d .
** Affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification becau
Haven't tried, but found a way to fix it myself. In general the problem
is, that Ubuntu still uses a setup/environment, which looks like ~15
years ago - all the bogus klibc/busybox pain! I mean, I want to boot a
workstation, not my dish washer!
In detail one problem seems, that Ubuntu uses the bug
Public bug reported:
We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to
our labs for studs, which just wanna give it a try.
Unfortunately it doesn't work: If it tries to exec the final step (e.g.
run-init /root /sbin/init textonly toram /root/dev/console
2>&1) it pa
Since after the kernel panic the machine is frozen, there is no way to
run any app or collect further information.
** 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.
ht
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174541/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355010
Title:
erne
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174538/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174540/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355010
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174544/+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/135
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174542/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355010
Title:
erne
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174545/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355010
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174543/+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/1355010
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174546/+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/1355010
Title:
er
apport information
** Tags added: apport-collected
** Description changed:
We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to
our labs for studs, which just wanna give it a try.
Unfortunately it doesn't work: If it tries to exec the final step (e.g.
run-init /ro
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1355010/+attachment/4174539/+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/1355010
To get the info above, I added break=init and did manually:
chroot /root /bin/bash
# created /etc/resolv.conf
apt-get install python-apport
apport-collect 1355010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Public bug reported:
Unfortunately pax is useless since not POSIX conform. The following
command should work, but doesn't:
cd /etc/skel && sudo pax -rwLlk -o gid=118 -o uid=118 . /home/test
see http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html
** Affects: ubuntu
Importance
** Package changed: ubuntu => pax (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393611
Title:
pax is not POSIX compliant
To manage notifications about this bug go to:
https://bugs.launchp
Public bug reported:
Obviously lxc does NOT depend on dnsmasq-base and thus this dependency
should be lowered to "optional" or "recommended".
Today entities using containers already have proper DNS as well as DHCP
servers and thus do not need at all another point of failure/possible
weak software
Public bug reported:
Defining USE_LXC_BRIDGE and than overwriting it unconditionally in the
source /etc/default/lxc-net doesn't make sense/is confusing.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubu
Public bug reported:
When one creates a incorrect profile, apparmor_parser seems to leave an
artifact of the "problem" file in the same directory, which in turn
leads to another error, when the file gets fixed. Not sure, how appamor
stuff works, but this is simply an unacceptable behavior! It shou
Well, it is strange: If there is such a setting in /etc/default/lxc, one
usually assumes, that this is the master of the disaster and gets
"propagated" downwards, but obviously it is not ... And thus I wonder,
which files in the lxc forest need to be checked as well to avoid
further surprises ...
Public bug reported:
If one defines a type with variables incl. help message, the
corresponding man page for this type displays in DETAILS section
displays wrong help messages for variables.
Example:
#!/bin/ksh93
typeset -T Log_t=(
typeset -Sh 'Color for info messages' GREEN='38;5;232;48;5;1
kdump package is crap, because it is using a different image (initrd)
than update-initramfs creates, so /boot/initrd.img-* !=
/var/lib/kdump/initrd.img-* . Yes, they may have the same name, but not
the same content. What a hugh bullshit! So no wonder, why one has to
waste several hours to find out,
We use 'Linux kino6 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux' (Ubuntu 18.04.3 LTS) and see
all the time 'hw csum failure's:
[ +28.297139] kino6_0: hw csum failure
[ +0.003607] CPU: 12 PID: 0 Comm: swapper/12 Tainted: P O
4.15.0-58-
So you suggest to break several hundred scripts written on/for standard
conforming platforms (i.e. not only for Linux) within the last 30 years
just because of bogus grub scripts? IMHO not a smart idea.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
The package is still broken (at least on focal) and outdated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892372
Title:
oomd does not start
To manage notifications about this bug go to:
https://
Public bug reported:
If one starts dhcrelay with explicitly specifying the interfaces to
listen,it silently ignores these options and still listens on all
interfaces. This is neither what the man page says (it says, only if no
interface is given, it listen on all interfaces), nor what is needed. I
Hmmm, that's an old one. IIRC the real root cause was, that some files
possibly included via /usr/share/lxc/config/ubuntu.common.conf still
used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine
was upgraded from bionic to focal).
--
You received this bug notification because you
FWIW: /usr/sbin/grub-probe is also posixly incorrect, e.g.:
# export POSIXLY_CORRECT=1
# /usr/sbin/grub-probe --device /dev/sda2 --target=partmap
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check
your device.map.
# unset POSIXLY_CORRECT
# /usr/sbin/grub-probe --device /
FWIW: Because on jammy (on my desktop) nfs-server works, I downloaded
and replaced/installed the related nfs-packages on noble
(libldap-2.5-0_2.5.18+dfsg-0ubuntu0.22.04.2_amd64.deb
libnfsidmap1_1%3a2.6.1-1ubuntu1.2_amd64.deb nfs-
common_1%3a2.6.1-1ubuntu1.2_amd64.deb nfs-kernel-
server_1%3a2.6.1-1u
Public bug reported:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answ
Wrong terminal for 'About Ubuntu'. It is of course 'Ubuntu 24.04.1 LTS'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088282
Title:
kernel-nfs-server does not work at all
To manage notifications
s/mountd/gssd/ ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2088282
Title:
kernel-nfs-server does not work at all
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
101 - 133 of 133 matches
Mail list logo
