what is the fix right now?
I get this message only once per kernel lifetime, when libvirtd starts
for the first time.
If I stop and restart libvirtd, it never shows again.
happens both with 20.04 lts kernel and hwe kernel (5.4 and 5.11)
--
You received this bug notification because you are a
Public bug reported:
https://github.com/lpechacek/cpuset/issues/31#issuecomment-663839081
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cpuset 1.6-3.1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
NonfreeKernelModules: zfs
I have upgrade the packages from the link provided (manual download
since they're not yet accepted into focal-proposed) and grub-pc postinst
script exits cleanly now. thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@juliank thank you.
accordingly #1896608 shouldn't be listed as a blocker on
https://discourse.ubuntu.com/t/focal-fossa-20-04-1-lts-point-release-
status-tracking/17604 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
manually installing grub works like this:
# grub-install --force --removable --boot-directory=/boot /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
meanwhile as a workaround I have symlinked /var/lib/dpkg/info/grub-pc.postinst
to /bin/true so other apt
I have enabled debugging on /var/lib/dpkg/info/grub-pc.postinst when
running dpkg --configure -a: https://termbin.com/7nh1
but I don't understand from the above output why it fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this bionic to focal upgrade still fails. not sure if this is the proper
place to discuss.
18.04.5 installed minimal in vmware player then do-release-upgrade:
https://i.imgur.com/YGLEWvy.png
18.04.5 setup deviations from defaults: root on thin lv created manually
in terminal in live installer.
ok, so now that this is fixed, why is ubuntu 18.04 to 20.04.1 still
blocked?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680
Title:
grub-pc needs to detect when debconf points to invalid
@vorlon,
some of us here are innocent 18.04LTS users waiting for canonical to enable
do-release-upgrade to focal, because this issue is blocking the LTS to LTS
upgrade process (link in comment #9)
with that in mind, how can we help testing without access to focal?
--
You received this bug
@ded, the bug says for groovy
Started work: 2020-08-18
Completed: 2020-09-02
for focal,
Started work: 2020-09-08
so one can only guess it would take another two weeks, if the same work
conditions apply
--
You received this bug notification because you are a member of Ubuntu
Bugs,
does anyone from canonical read or care about 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/686859
Title:
"Bootloader install failed" cannot be closed
To manage notifications about
because if not, just fucking tell us or fucking write a faq entry on
installation wiki
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686859
Title:
"Bootloader install failed" cannot be closed
To
still ocurring in 20.04.1 - I needed to install ubuntu alongside an
existing partitioned gpt lvm thin pool disk.
could not install grub on selected disk, now I can't get past the error,
as I can't select any other disk nor choose "continue without a
bootloader" because the OK button does
also other people complained
https://www.reddit.com/r/VFIO/comments/90tg4h/after_loading_vfiopci_instead_of_nvidia_my_dmesg/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855747
Title:
>Kai-Heng Feng (kaihengfeng) wrote on 2019-12-11: #4
> Can you please run `sudo update-initramfs -u -k all` and see if the
issue still happens?
yes this persists even after that.
I have a nvidia card but I want to blacklist it. even blacklisted, the
systemd-udevd
>Sebastien Bacher (seb128) wrote on 2016-11-22: #2
>
>Thank you for your bug report, the confinement restriction is a feature
>though. Where do you want to play videos from? Reading from another location
>than your userdir or removable media or remote shares is probably something
>most
Public bug reported:
this works ok with latest 5.3.x kernel but not with 4.15 kernel
kernel 5.0.0 does not work ok with zfs so I can't confirm it is fixed or not in
5.0.0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu
I also need to force remove a module.
It is unacceptable to have to reboot when I know for sure that removing the
module will not affect the system stability.
It is also difficult to keep rebuilding kernel just to have this feature.
Please reconsider. Thanks.
** Changed in: linux (Ubuntu)
changing dev_err to dev_err_once like suggested in comment 35 worked for me,
thank you!
probably this hides the cause but at least I'm no longer being hit with tons
of messages in syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
split is awesome but I find myself many times in need to choose where
the new terminal is created.
default is below and on right, but sometimes I need also above and on left
Please add ability to choose split placement (above/below; left/right)
Thanks.
** Affects:
suggestions how could it be done for mouse:
- if mouse is in the lower half, place split below. if mouse is in the upper
half, when I right-click and split, split above
- if shift or ctrl is held when clicking split, invert split placement
- additional split items in the menu
for keyboard: add a
I am getting similar message at boot but not to Windows target, instead to a
DELL EQUALOGIC 100E
Symptom is system hang for a few seconds during boot then it works ok
[ 56.363592] [ cut here ]
[ 56.363604] WARNING: CPU: 1 PID: 415 at
Is anyone at Canonical actually discussing this internally?
If yes, what are the key subjects? Filesystem layout (what dirs go into what
datasets, personalized parameters like excluding /tmp from being auto
snapshotted etc)? developer time to code the feature into the installer? what
else is
@ comment #9, it has landed into proposed, not into main! this means
xenial won't get 0.7 via hwe... :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734172
Title:
Upgrade ZFS to 0.7.3
To manage
this is really worrying. we chose ubuntu for native zfs but it is such a
dissapointment to not provide at least a ppa with updated zfs 0.7 for xenial.
if next LTS comes without 0.7 we will switch back to centos that has almost
immediate release packages after official release.
--
You received
this is workaround for me that runs correctly:
in rc.local:
(systemctl stop networking.service; systemctl start networking.service;
systemctl restart networking.service; true) &
if i put the commands one by one, rc.local unit will fail because
systemctl start exits non-zero. notice the
** Attachment added: "dpkg-l.txt"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1551415/+attachment/4812135/+files/dpkg-l.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551415
how do I debug this?
if i manually run 'ifup -a --read-environment' or 'systemctl start networking'
it brings all stuff up cleanly.
by 'debug' i mean more than just looking at journalctl -u networking
below contents of network/interfaces, journalctl -u networking and
contents of netwroking unit
seeing this on xenial after this sequence of operations:
lxc stop run2
lxc delete run2
lxc copy run1 run2
lxc start run2 <- hangs here, with later dmesg
[337766.146479] unregister_netdevice: waiting for lo to become free. Usage
count = 1
[337772.435786] INFO: task lxd:20665 blocked for more
workaround for ubuntu 16.04 lts is to install the deprecated ntpdate
that still works ok:
ntpdate:amd64/xenial-security 1:4.2.8p4+dfsg-3ubuntu5.3 uptodate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and #1544942 does not say dry-run removes packages, but says the output
is different between with and without dry-run (which is something I also
observed but only the first run after the upgrade to latest precise
version of unattended-upgrades)
--
You received this bug notification because you
> the --dry-run removes the packages
no, it doesn't. #1544942 affects only one person, and in comment #64 you
can see that files on /boot are not removed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> have you made sure you manually set that option to 'true'?
also, if you pay attention to my pasted logs, THE FIRST TIME the updated
version is run with -d --dry-run, it DOES mention wanting to remove kernels.
however the second time I run it, without --dry-run, it NO LONGER mentions
removing
here is another box
oot@wifi:~# eatmydata apt-get install unattended-upgrades
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
bsd-mailx
The following packages will be upgraded:
unattended-upgrades
1 upgraded, 0 newly installed, 0 to
> have you made sure you manually set that option to 'true'? It's
'false' by default.
yes,
root@mailhost:~# grep Dependencies /etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Remove-Unused-Dependencies "true";
root@mailhost:~# ls -lht /etc/apt/apt.conf.d/50unattended-upgrades
worse, before running unattended-upgrades, apt-get autoremove showed
lots of kernels good for removal. after upgrading and running the new
unattended-upgrades, apt-get autoremove no longer lists these kernels at
fit for autoremove.
--
You received this bug notification because you are a member
this bugs says "Precise Fix Released Medium Brian Murray Edit"
apt-listchanges -a /var/cache/apt/archives/unattended-
upgrades_0.76ubuntu1.2_all.deb says
" unattended-upgrades (0.76ubuntu1.2) precise-proposed; urgency=medium
* cherry pick fix for unused-dependencies removal. (LP:
Can you file it against initramfs-tools-core please?
the init file comes from that package.
ubuntu@ubuntu-mate:/tmp/test$ dpkg -S /usr/share/initramfs-tools/init
initramfs-tools-core: /usr/share/initramfs-tools/init
--
You received this bug notification because you are a member of Ubuntu
Bugs,
ubuntu@ubuntu-mate:/tmp/test$ grep -C2 hostname /usr/share/initramfs-
tools/init
# mdadm needs hostname to be set. This has to be done before the udev rules are
called!
if [ -f "/etc/hostname" ]; then
/bin/hostname -b -F /etc/hostname 2>&1 1>/dev/null
fi
--
You received this bug
ubuntu@ubuntu-mate:/tmp/test$ zcat /boot/initrd.img-4.4.0-4-generic | cpio -i
192905 blocks
ubuntu@ubuntu-mate:/tmp/test$ grep -n -C2 hostname init64-
65-
66:# mdadm needs hostname to be set. This has to be done before the udev rules
are called!
67:if [ -f "/etc/hostname" ]; then
68:
** Attachment added: "hostname.jpg"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1545297/+attachment/4574658/+files/hostname.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't think procps should return an error when one of the sysctl.d/
files contains incorrect data.
Printing the error would be useful especially if the exact file and
value is mentioned, otherwise saying oh, we failed when in fact only
one attribute failed to load is cumbersome.
Just because
Public bug reported:
Cursors
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: oxygen-cursor-theme-extra (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Tue May 10 02:28:13 2011
ErrorMessage:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/780513
Title:
package oxygen-cursor-theme-extra (not installed) failed to
install/upgrade: subprocesul script post-installation instalat a
returnat
it is a non-starter due to litigation and patent licensing. - are you
saying that it is PROHIBITED BY LICENSE to publish source code that
makes a GPL source code interface with a CDDL source code, once compiled
IN PRIVATE following PUBLIC COMPILATION INSTRUCTIONS ?
--
Add native ZFS to Ubuntu
Julián - from the host GUI.
--
Unable to run Virtual Machine
https://bugs.launchpad.net/bugs/217311
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
I can confirm this on ubuntu 9.04
Linux desktop 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009
i686 GNU/Linux
ii kvm1:84+dfsg-0ubuntu12.3
Full virtualization on i386 and amd64 hardwa
ii kvm-pxe
*** This bug is a duplicate of bug 91545 ***
https://bugs.launchpad.net/bugs/91545
how do i get rid of receiving these emails?
On 6/18/07, Apport retracing service [EMAIL PROTECTED] wrote:
*** This bug is a duplicate of bug 91545 ***
https://bugs.launchpad.net/bugs/91545
**
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7094065/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7094066/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7094067/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: kde-guidance
i don;t know; this window has appeared when i tried to use two monitors
on my toshiba satellite 1900-101
ProblemType: Crash
Architecture: i386
Date: Sat Mar 31 18:21:12 2007
DistroRelease: Ubuntu 7.04
ExecutablePath:
50 matches
Mail list logo
