Public bug reported:
I can not find the apt amd64 version 2.7.14 on Ubuntu Noble. It seems apt only
exists for non-amd64 architecture:
https://packages.ubuntu.com/search?suite=noble=apt
noble (admin): commandline package manager
2.7.14: arm64 armhf i386 ppc64el riscv64 s390x
I can not find any
Public bug reported:
The latest version of dislocker on Ubuntu Jammy is 0.7.3-2ubuntu1:
# dpkg -l dislocker
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Thank you very much. I confirmed it's working on Ubuntu 20.04, and the
grub is 2.04-1ubuntu26.
Steven
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829331
Title:
Grub regexp command does not work
Public bug reported:
Dear maintainer,
The package console-common 0.7.91 causes debootstrap failing to bootstrap a
basic Focal system.
Here is how to reproduce this issue:
$ debootstrap --verbose --arch=amd64 --components=main,universe
--include=console-common focal focal-chroot
I have tested Ubuntu Focal with systemd 243-3ubuntu1:
https://launchpad.net/ubuntu/+source/systemd/243-3ubuntu1
and the issue I have reported in Bug 1849608, which is marked as the duplicate
of this bug, is gone now. Hence I confirmed the fix works here.
--
You received this bug notification
BTW, forgot to mention, after applying the patch in my system, I have to
reboot the system then run "dhclient -v" so that the stale status of
previous dhclient won't confuse it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The file /etc/dhcp/dhclient-enter-hooks.d/resolved
provided by systemd (242-7ubuntu3) causes the dhclient failing to get DNS due
to systemd-resolved is not run.
This issue can be reproduced on Ubuntu Eoan:
==
root@eoan:~# dhclient -v
Internet
OK, for ubuntu-19.04-live-server-amd64.iso booting in secure boot mode, I found
more commands are not working, at least including:
lspci
probe
md5sum
play
sha1sum
tr
usb
videoinfo
While the following are working:
ls
cat
echo
help
reboot
I am wondering is this due to some purpose about
I repeated the above steps for ubuntu-18.04.2-live-server-amd64.iso, and
got the same result. The regexp command in the grub shell does not work
in secure boot mode. However, it does work in non-secure boot mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Grub command regexp works in the non-secure boot mode"
https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1829331/+attachment/5264191/+files/grub-working.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Dear maintainer,
The grub command "regexp" on Ubuntu 19.04 does not work in the secure boot
mode, yet it works in the non-secure boot mode.
Attached please find the screenshots about that.
How to reproduce it?
1. Download Ubuntu 19.04 sever ISO file:
Public bug reported:
I am using the parted from Xenial. When the command "paretd -s /dev/sda print"
is run on my Macmini15, it crashes. If you need more info, please let me know.
The details:
# dpkg -l |grep parted
ii libparted-fs-resize0:amd64 3.2-15
I have similar issue on Ubuntu 16.04 beta 2 (updated on Apr/5/2016):
$ sudo apt-get install runit
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
socklog-run
The following NEW packages will be installed:
runit
0 upgraded, 1 newly
The final beta for Xenial will be released recently. However, this issue still
remains.
Package console-common still conflicts with plymouth and cryptsetup. Therefore
if plymouth and cryptsetup are installed, there is no way "dpkg-reconfigure
console-data" can be used to tune the keymap.
Is
I found a side effect if console-common is not installed. There is a problem to
run "dpkg-reconfigure console-data", i.e. when it's run, after selecting
"Select keymap from arch list", nothing happens. Normally it should ask the
"Keyboard layout family", then "Keyboard layout".
This is how to
OK, got it. Thank you very much.
Steven.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528861
Title:
cryptsetup can not coexist with console-common
To manage notifications about this bug go to:
Thanks.
The reason we need to use install-keymap is it's easier to do that in
unattended mode, i.e. e.g. to set the French keyboard, just use:
install-keymap /usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz
So if console-common is obsolete, is that possible to use console-setup and
Public bug reported:
The package cryptsetup can not coexist with console-common due to
cryptsetup depends on plymouth. However, plymouth conflicts with
console-common, so this makes the cryptsetup can not coexist with
console-common. This does not happen on Debian Sid because cryptsetup on
Debian
Somehow my bug report sent to intel-wired-...@lists.osuosl.org is never shown
on the list. I sent twice, both of them just disappeared. I have successfully
joined the mailing list a few days ago, and have received many emails from the
list.
Anyway, I did another test with Linux kernel
I just did a test with
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc7-vivid/linux-image-4.0.0-04rc7-generic_4.0.0-04rc7.201504061936_amd64.deb
The e1000e issue still remains. The output of dmesg was attached.
** Attachment added: e1000e kernel oops with linux kernel
Same problem for the updated linux kernel 3.19.0-12.12-generic in Vivid
repository.
The output of dmesg was attached.
** Attachment added: e1000e kernel oops for linux kernel 3.19.0-12.12-generic
I have reported this to e1000-devel:
http://sourceforge.net/p/e1000/mailman/e1000-devel/thread/55234954.8030600%40nchc.org.tw/#msg33737691
Steven.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, I will wait for another rc deb in
http://kernel.ubuntu.com/~kernel-ppa/mainline/
then I will do a test again.
Thanks.
Steven.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438562
Title:
apport information
** Tags added: apport-collected
** Description changed:
When I booted the daily build vivid iso from
http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
vivid-desktop-amd64.iso 31-Mar-2015 03:41 1.0G Desktop image for
64-bit PC (AMD64)
The mainline kernel does not fix this bug. It still exist in
linux-image-4.0.0-04rc6-generic, i.e. using this:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc6-vivid/linux-image-4.0.0-04rc6-generic_4.0.0-04rc6.201503291935_amd64.deb
The dmesg for kernel oops with e1000e was
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363911/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363908/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363909/+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/1438562
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363904/+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/1438562
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363906/+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/1438562
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363903/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363905/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438562
Title:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363907/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438562
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363901/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438562
Title:
e1000e
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363902/+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/1438562
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1438562/+attachment/4363910/+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/1438562
Title:
Christopher, did you mean to follow the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel
then send to
https://lists.sourceforge.net/lists/listinfo/e1000-devel
?
Otherwise I can not find any e1000-devel list on vger.kernel.org. The most
related one I found is
Public bug reported:
When I booted the daily build vivid iso from
http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
vivid-desktop-amd64.iso 31-Mar-2015 03:41 1.0G Desktop image for
64-bit PC (AMD64) computers (standard download)
I got a kernel oops.
The virtual
** Attachment added: The installation of nfs-kernel-server package
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+attachment/4258025/+files/nfs-kernel-server-installation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: Output crreated by ubuntu-bug for nfs-common
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391405/+attachment/4258028/+files/14.10-nfs-common-environment.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I just did a fresh installation for Ubuntu 14.10 i386 release, and
nfs-kernel-server was installed correctly.
During the installation of nfs-kernel-server package, I can see statd service
was started successfully. I confirmed it's running:
steven@utopic:~$ ps -ef |grep
Public bug reported:
I installed a text mode Utopic i386 via network. All works fine, except the
plymouth is not working.
Instead of plymouth-theme-ubuntu-text, I manually installed
plymouth-theme-text, and make sure the boot parameters has splash:
$ cat /proc/cmdline
Public bug reported:
When running this command on Ubuntu 14.04 amd64 release:
yes | apt-get -y install tftpd-hpa
It never finishes... Only shows black screen on the terminal.
I know it's weird to use yes for this command. However, just to show it does
make any sense the command can not be
BTW, forgot to mention if the command is run as:
yes | apt-get -y install tftpd-hpa /dev/null
It finishes successfully.
** Description changed:
When running this command on Ubuntu 14.04 amd64 release:
yes | apt-get -y install tftpd-hpa
It never finishes... Only shows black screen on the
Public bug reported:
When mdadm (3.2.5-5ubuntu3) is installed in a bootstrap/live Trusty
environment, it fails. It's because update-grub is run. However, in a
bootstrap/live system, although grub is installed, actually it's not use for
the boot loader. Therefore update-grub fails.
Attached
This issue still exists on the released saucy, i.e. linux kernel
3.11.0-12-generic.
Apparently the issue is about vmwgfx, so a workaround is to disable vmwgfx by
adding a boot parameter like vmwgfx.enable_fbdev=no because if
vmwgfx.enable_fbdev=0 is used, vmwgfx module is still loaded.
The
46 matches
Mail list logo
