I switched to Firefox for about a week and noticed I never experienced
this bug under it as I did with Chrome. However, Firefox isn't my
preferred browser so I switched back to Chrome after installing Flash
Aid (https://addons.mozilla.org/en-US/firefox/addon/flash-aid/) in
Firefox and letting it ru
Nanovarium's fix didn't work for me, used ppa purge to roll back.
Still having the same issues, worse when interacting with text boxes and
copy+paste in Chrome. Very annoying bug, a fix would be appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I ended up switching to Cinnamon. GNOME still randomly crashes as I'm
working on Chrome, losing data and hours of work...I couldn't take it
anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889706
@Alexander Ast
You're absolutely right, I just experienced this bug under Cinnamon as
well. I'm still under Mint 12 because, for some strange reason, I can't
install Mint 13 from a Live CD (it just hangs after the 'Linux Mint 13'
loading screen)
--
You received this bug notification because you
Well, looks like there was an update for my Intel graphics card, and so
far, so good. Let's hope it sticks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889706
Title:
Gnome-shell randomly crashes
@Alexander Ast
I switched to Mint 13 today. It's odd having a computer that doesn't
crash every other hour, guess I was starting to see this bug as a
feature...but so far, so good!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Same problem here, tends to pop up when using Google Chrome.
Lenovo G570
Intel HD Graphics 3000
Mint 12, Gnome 3, 64 Bit
Would love a fix because this is my main computer and I nuked Windows 7
for Mint 12.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I installed the Gnome3 PPA as suggested above and I haven't had a single
crash in Chrome for at least two hours now. Hopefully that's the end of
that. Will report if any changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Nope, spoke too soon, came back.
However, I'm able to duplicate the error. It always happens when I
highlight text in Chrome, which freezes GNOME. I can only interact with
the top menus, such as right-click, but I can't minimize/maximize/close
any windows. Tabs with music playing in the background
Brian,
my current version of openoffice.org come with Gutsy as an upgrade obtained by
update-manager .
With synaptic i see:
package: openoffice.org
installed version: 1:2.3.0-1ubuntu5.1
last version: 1.2.3.0-1ubuntu5.1
in openoffice --> Help -> About OpenOffice.org, i see:
OpenOffice.org 2.3.0
i have tried OO 2.3.0 (openoffice.org-core 1:2.3.0-1ubuntu5.1) and is affected
by de same bug
what i can do?
--
crash when editing a input field
https://bugs.launchpad.net/bugs/76513
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Binary package hint: openoffice.org
try to insert a variable field and then a input field of previous
defined variable. Save, close and re-open. Click on input field and edit
variable value. Oo crash when you insert second char
openoffice.org 2.0.4-2ubuntu0.4 on ubuntu 6.10
here a test file that exploit bug
** Attachment added: "open the attached file and try to edit input field"
http://librarian.launchpad.net/5478119/test_edit_field.odt
--
crash when editing a input field
https://launchpad.net/bugs/76513
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Ryan,
Attached you can find backtrace of soffice.bin crash event,
Mao
** Attachment added: "gdb backtrace of soffice.bin"
http://librarian.launchpad.net/5482688/gdb-soffice.bin.txt
--
crash when editing a input field
https://launchpad.net/bugs/76513
--
ubuntu-bugs mailing list
u
** Attachment added: "same problem"
http://librarian.launchpad.net/5483023/_usr_bin_btdownloadgui.bittornado.1000.crash
--
bittornado crashed "after quiting".
https://launchpad.net/bugs/68597
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mao1285 F pulseaudio
CRDA: Error: [Errno 2] 沒有此一檔案或目錄
Card0.Amixer.info:
Card hw:0 'SI7012'/'SiS SI7012 with AD1980 at irq 18'
Mixer name : &#
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/39669076/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/39669077/ArecordDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39669078/BootDmesg.txt
**
Public bug reported:
1) Ubuntu Trusty Tahr (14.04)
2) MenuLibre 2.0.3-1
3) MenuLibre would launch
4) MenuLibre refuses to launch. Cursor changes to 'busy' for a couple of
minutes, then stops. Cannot send any information to Canonical through
Apport, as MenuLibre simply doesn't start. Launch from
Purged and reinstalled. Now getting this output:
mao@CatLap:~$ menulibre
**
ERROR:/build/buildd/gnome-menus-3.10.1/./libmenu/gmenu-tree.c:4022:preprocess_layout_info:
assertion failed: (!directory->preprocessed)
Aborted (core dumped)
mao@CatLap:~$
--
You received this bug notification beca
Hi,
the bug also occours on my installation (compiz 0.9.10.2 + ubuntu
13.10), after I played with Ubuntu Tweak, Unity Tweak, or after I run
this command 'dconf reset -f /org/compiz/', I don't know. Now I could
not restore the correct behavior.
Maybe this could help you ro resolve this very annoyi
Public bug reported:
During installation booltloader failed to install.
It wanted to install on raid /dev/cciss/c0d0, that failed. Attempted to change
to sdb, where it should install. Also failed.
Aborted installation and got a crash report.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package:
When creating a new VPN connection it doesn't get shown in the VPN under
"Connect to VPN". If one reconnects to an connected network, lets say
the WiFi it appears straight away as it should.
When setting the VPN as "Available to all users" it's not possible to
set a password for the VPN connection
Public bug reported:
ran apt install ukui-wallpapers
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: ukui-wallpapers (not installed)
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.
I get the same problem as CTW above, and I'm on an Intel processor too.
In addition, I am using the Gnome environment.
--
I get an error message after boot-up telling me that there is an kernel error
and that the system might be ubstable
https://bugs.launchpad.net/bugs/454725
You received this b
Public bug reported:
On Asus Server, when it run "sosreport -a" to the network step, the
console would print below call trace and the 100G Nic port became
unreachable.
call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/
** Affects: ubuntu
Importance: Undecided
S
The call trace seems correlating to ethtools like below:
Jun 18 01:19:08 frank-viper kernel: [69418.453457] BUG: unable to handle page
fault for address: b2660b04
Jun 18 01:19:08 frank-viper kernel: [69418.465204] #PF: supervisor read access
in kernel mode
Jun 18 01:19:08 frank-viper ke
For #37 screen shot and #39. We found this wayland issues for 18.04 and
Huawei x86 server, but it seems no for 18.04.1. In my test, apt-get
install ubuntu-desktop and reboot works fine.
For #37 "Why would hibmc_drm be arm64-specific?", I guess it might
because vendors (sm750 vga) have already prov
For #37-#39
This screen blur issues during install are only happened on Huawei X86
server for 18.04 and 18.04.1 d-i iso. As I know, 18.04 and even 18.04.1
ARM64 iso works fine with this new hibmc-drm module for installation on
Hisilicon D05 board.
--
You received this bug notification because yo
Dann,
For the wanland issues, I understood it as comments in #15, that is:
Blur screen for GDM login was caused by wayland, it can be fix by force
to use Xorg in
/etc/gdm3/customer.conf to uncoment WaylandEnable=false
Is this right for your wanland issues on D05?
In 18.04, we fo
A good feedback from partner is "I just update Ubuntu kernel to v4.19
and Memory Stress can got pass result this time."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796217
Title:
Qunata server me
** Attachment added: "sos report when issued showed on console"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197396/+files/sosreport-right-goblin-20181003095301.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
We are facing a problem during the certification test. System always
stop at below screen while memory stress. In the following re-producing,
kernel seems un-normal and it can’t capture above info into the syslog
or kernel log, but the console will show same warning as screen
** Attachment added: "sos report when issued showed on console"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796217/+attachment/5197397/+files/sosreport-right-goblin-20181003095301.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
ethtools report i40e as 10G instead the real 1G on Ubuntu 16.04.5 ga-
kernel
** 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://bug
sos-reports
** Attachment added: "sos reports"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802832/+attachment/5211663/+files/sosreport-R4900G3-20180930070440.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
It is also found on 16.04.5 hwe kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name floated after boot in Ubuntu 18.04
To manage notifications about this bug go to:
https:
** Attachment added: "dmesg before"
https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188979/+files/dmesg_before
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name
** Attachment added: "dmegs after"
https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5188978/+files/dmesg_after
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name fl
It was found on v4.15.0 kernel and not for v4.4 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name floated after boot in Ubuntu 18.04
To manage notifications about this
Public bug reported:
nvme device name such as /dev/nvme?n?p? would be floated that is symbol
link to different real ssd device after reboot in 4.15.0 kernel.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: bionic
--
You received this bug notification because you ar
** Summary changed:
- nvme name floated after boot in Ubuntu 18.04
+ nvme name floated after boot with 4.15.0 kernel
** Description changed:
nvme device name such as /dev/nvme?n?p? would be floated that is symbol
- link to different real ssd device after reboot in 4.15.0 kernel.
+ link to diff
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for
example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory
which might be wrong. In 4.4 kernel, it is a matched directory of
nvme1n1. Please refer to attach screen shot for more details.
** Attachment added: "misma
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme"
https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189361/+files/image004.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "match name in 4.4.0 kernel for /sys/class/nvme"
https://bugs.launchpad.net/ubuntu/+bug/1792660/+attachment/5189362/+files/image004.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
In the 4.15.0 kernel, a mismatch was found under /sys/class/nvme/, for
example for the /sys/class/nvme/nvme1/, there is a of nvme3n1 directory
which might be wrong. In 4.4 kernel, it is a matched directory of
nvme1n1. Please refer to attach screen shot for more details.
** Attachment added: "misma
** Package changed: ubuntu => kernel-package (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name floated after boot with 4.15.0 kernel
To manage notifications about this
@AaronMa
Do you have docs for how to compile a new kernel. I can found below doc link
https://help.ubuntu.com/community/Kernel/Compile
But it seems a bit old.
The other difficult is how to get compile config from d-i iso kernel. I
found if I use a kernel from running/installed system to replace d
The log which collect via
apport-cli --save=/tmp/apport-log linux
** Attachment added: "apport-cli log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+attachment/5191267/+files/apport-log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Guiherme
Firstly, thank you much to provide those inforamtion. I asked customer
to check on 4.15.0-34 with kernel parameter of "nvme_core.multipath=0",
it was reported the same ( nvme device name would be changed every
reboot).
** Attachment added: "nvme name mismatch screen shoot"
https://
:82:00.0/nvme/nvme1/nvme3n1
zlmao@zlmao-T460s:~/tmp$
thanks,
Mao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792660
Title:
nvme name floated after boot with 4.15.0 kernel
To manage no
summary for workaround via kernel parameter to blocker loading:
modprobe.blacklist=hibmc_drm
**prevent load during install
To add "modprobe.blacklist=hibmc_drm" kernel parameter in grub when boot from
d-i iso (press ‘e’ key and then press F10 or ctrl+x ( those key was noticed on
the screen)
Public bug reported:
The existing ipmitool can't works for Quanta server as it didn't include
lasted patches, even in 20.04.
>From Quanta feedback that pmitools in 20.04 can work for quanta server if
>apply this patch set:
https://github.com/ipmitool/ipmitool/commit/5c033c06abb45bc183f42cd758c61
Got feedback about what was fixed by the patch as below:
New IPMITOOL QCT support OEM DIMM description as below, so customer can
know which CPU/DIMM/slot
Logged "Correctable ECC / SBE Warning Threshold (DIMM A0) - Asserted":
ipmitool -U admin -P admin -H 10.10.12.21 raw 0xa 0x44 0x0 0x0 0x2 0x0
It was also tested that freeipmi tools of ipmiconsole and ipmipower cmd
works fine with Quanta server as it is standard for ipmi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864612
Title:
request
It seems not works on my side ( 18.04 ARM64). I have to add the
listening IP explicitly.
ubuntu@infra1:/etc/bind$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"
ubuntu@infra1:/etc/bind$ uname -a
Linux infra1 4.15.0-4
to add floating ip too as:
listen-on { 185.168.3.1; 185.168.3.5; };
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service when MAAS is managing DNS
To manage
Public bug reported:
During fio testing as below on 16.04 (xenial) hwe-kernel (
4.15.0-55-generic), the below fio woluld get call trace or segment
falut:
/tmp/juju-exec53975/script.sh: line 1: 1104000 Segmentation fault
(core dumped) fio --name=randread --ioengine=rbd --clientname=admin
--poo
Public bug reported:
In Quanta server testing for 18.04.3 hwe-kernel 18.04.4 hwe-kernel and 20.04
daily build, it seems usb keyboard would:
1.Same OS would lost keybord and record usb usbx-portx: couldn't allocate
usb_device log.
2.It is easy to reproduce the issue if add "open initcall debug" i
Also, it was said that this issues didn't found on rhel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869138
Title:
The keyboard does not have responeded when boot system into Ubuntu
18.04.4 wit
kernel log from testing
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1869138/+attachment/5341769/+files/log.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
>From the kernel log, beside below errors, there are no errors for usb or
keryboard, it also show correctly dectected keyboard for every reboot.
$ grep -i error kern.log | tail -n5
Feb 26 10:04:45 user-QuantaGrid-D52PL-4U kernel: [4.321273] ERST: Error
Record Serialization Table (ERST) suppor
The boot which failed to detected keyboard are below:
Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.688666] xhci_hcd
:00:14.0: xHCI Host Controller
Feb 25 20:56:06 user-QuantaGrid-D52PL-4U kernel: [ 12.739684] xhci_hcd
:00:14.0: new USB bus registered, assigned bus number 1
F
The Quanta give me hits about error and it seems that in 68 reboot
cycles there are 11 times which can't detected out the usb keyboard.
$ grep 'Command line' kern.log |wc
68 952 12988
$ grep "usb1-port2: couldn't allocate usb_device" kern.log |wc
11 1321199
--
You rece
The boot with keyboard detected logs as below:
Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.242592] hub 1-0:1.0: 16
ports detected
Feb 25 20:30:37 user-QuantaGrid-D52PL-4U kernel: [ 13.308359] probe of
1-0:1.0 returned 1 after 129930 usecs
Feb 25 20:30:37 user-QuantaGrid-D52PL-4U ke
Compare the kernel related usb logs between keyboard detected and not,
all previous logs are no difference, it began difference only from. I
personally thought it might not issues from kernel as it likes external
device (keyboad) didn't report devices information back and from testing
log it sees j
The kernel of Linux version 3.10.0-862.el7.x86_64 which didn't find
issues. From the below log of "usb 1-1: Product: Keyboard Hub", it seems
ubuntu new hwe kernel can't detected and support this usb hub of the
keybaord. The full log about usb 1-1 are below:
usb 1-1: new high-speed USB device numbe
Public bug reported:
The user upgrade Ubuntu server to linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of
ES3000 V2 SSD which the correspond module driver of hio.ko is include in
this kernel. The data write to disk seems was incorrect.
To format this sdd disk with xfs get e
** Description changed:
The user upgrade Ubuntu server to linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb and it use a SSD of
ES3000 V2 SSD which the correspond module driver of hio.ko is include in
this kernel. The data write to disk seems was incorrect.
To format this sdd disk
It is Ubuntu server without Desktop environment and I can't provide my
launchpad access to customer too.
I will ask them to collect bug reports by:
apport-bug linux-image-4.10.0-26-generic_4.10.0-26.30_amd64.deb
I am not family for apport. Can apport-bug provide what you want?
--
You received
We found same problem on Ubuntu17.04 the kernel version is
linux-image-4.10.0-19-generic上. The apport report is in the attachment file.
We compared and testing on kernel 4.9 an 4.10， this HIO driver works fine on
4.9 but does not work
on kernel 4.10-rc5 and aboe.
** Attachment added: "Th
This patch need to merged and fixed for the release 16.04.04. The final
SRU4 windows is 8 Dec. to 6 Jan 2018.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738334
Title:
hisilicon hibmc regression
Notes and some more detail for this bug/patch:
The bug is from/caused by 4.12 DRM architecture, the main line commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.15-rc3&id=ea642c3216cb2a60d1c0e760ae47ee85c9c16447
It will cause x-window start hanged, the detail
** Attachment added: "screen shot for apt-get conflicts"
https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/1738990/+attachment/5024549/+files/fjedfhha.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
sudo apt-get install rdma-core reports for "tring to overwrite
/etc/modprobe.d/mlx4.conf which is also in package kmod 24-1ubuntu2".
This test on 16.04.3 ARM64 with 18.04 repository.
The mlx4.conf contains are:
cat /etc/modprobe.d/mlx4.conf
# mlx4_core gets automatically lo
** Attachment added: "full demsg and syslog for 18.04 uefi install, 18.04
legacy bios install, 16.04.4 uefi install"
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5110296/+files/dmesg_syslog_1804_1604.tar.gz
--
You received this bug notification because
Public bug reported:
For all(as I know) Huawei servers, the vga adapter are embed in the iBMC
chips. Those server can install from ISO manually for 16.04.4 and screen
display normally. But for 18.04 ( tested both for daily and final
beta)version, the install screen is blur. One of tested server is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 1804 install screen becomes blur on Huawei server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
** Summary changed:
- Ubuntu 1804 install screen becomes blur on Huawei server
+ Ubuntu 18.04 install screen becomes blur on Huawei server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title
** Attachment added: "debug log for KVM UEFI model without internet access"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137592/+files/subiquity-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770585
Title:
18.04 installer would become failed in UEFI without Internet
connection
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
Below iso use new Subiquity (not d-i) and it would be fail without
correct internet connection in UEFI mode. After reboot it would show
error of "No boot device, please reboot system with manual operaton" in
Huawei server.
This issue can be produce by KVM with UEFI too. It wo
** Attachment added: "Sos report on KVM UEFI testing"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770585/+attachment/5137665/+files/sosreport-ubuntu-server-20180511073713.tar.xz.md5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1750819 ***
https://bugs.launchpad.net/bugs/1750819
If I change UEIF to BIOS for my local VM (kvm) then it can be installed
successfully after I configure an IP without actually internet access.
But if I use UEFI, the install would failed and can't boot into
For ISO of classic Debian installer (d-i), it would become screen blur
after kernel load and in the first screen of "select a langue"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubu
** Attachment added: "This screen bure on UEFI model for 18.04 classic d-i
installer in the first installer screen of language select"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+attachment/5141063/+files/uefi-di-screen-blur.png
--
You received this bug notification because
Below image uses the Subiquity and it can be installed successfully. But after
install ubuntu-desktop, the login screen would become screen blur after reboot
or init 5, but it can be start by startx after init 3 in the terminal.
http://releases.ubuntu.com/18.04/ubuntu-18.04-live-server-amd64.iso
Blur screen for GDM login was caused by wayland, it can be fix by force
to use Xorg in /etc/gdm3/customer.conf to uncoment WaylandEnable=false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Tit
@Aaron Ma
I want to test your patch. But seems it would patch with error. I guess, the
new 18.04 source code have been change to:
list_add_tail(&vgadev->list, &vga_list);
instead of:
- list_add(&vgadev->list, &vga_list);
+ list_add_tail(&vgadev->list, &vga_list);
Does it mean
For #44 Aaron's suggested patch, it seems patch have been included after
4.15.0-46. The testing 18.04.2 iso with 4.15.0-48 kernel seems the
system would be hang on language selection after select install server
of grub screen. So it seems this hibmc_drm would caused another this
hang issues too.
T
For #44, in the following testing, if disable hibmc_drm loading, then it
works fine and would not be hang.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762940
Title:
Ubuntu 18.04 d-i install scree
Public bug reported:
On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would
fail as below if the back devices are large than 1024G ( 1025 would
fail, but not 1024 ).
[ 727.756453] bcache: register_bdev() error nvme12n1: cannot allocate memory
[ 727.756456] bcache: register_bcach
Also, 18.04 ga-kernel worked fine too.
** Description changed:
On 20.04(focal) ga-kernel and 18.04 (hwe-kernel). To make.bcache would
fail as below if the back devices are large than 1024G ( 1025 would
fail, but not 1024 ).
[ 727.756453] bcache: register_bdev() error nvme12n1: cannot
This max 1024G size applies to the 512byte sector, most NVME ssd can
change ( LBA format ) to 4K and the max limits will be 16T than.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909518
Title:
bc
The command example to change 512 sector to 4K for “Intel P4510 4.0TB
U.2 NVMe SSD”
ubuntu@prdhci01a:~$ sudo nvme id-ns /dev/nvme1 -n 1 -H |grep "LBA Format"
[3:0] : 0 Current LBA Format Selected
LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative
Performance: 0x2 Goo
For the 4K sectors, the max limits should be 8T then. (1024G*4096/512)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909518
Title:
bcache register_bdev() error cannot allocate memory
To manage no
Public bug reported:
Ubuntu 18.04.5/20.04 kernel doesn't have latest i40e driver for X710-T2L
module,Please add the driver on next kernel version release.
More details please refer to
https://bugs.launchpad.net/quantatw/+bug/1905673
** Affects: linux (Ubuntu)
Importance: Undecided
Public bug reported:
After upgrading to 20.04.1 LTS, when the display goes to sleep and the
session locks, I can't log back in. An incorrect password is notified
as such, but the correct password blanks the screen. When I move the
mouse, the login prompt re-appears.
If I lock the session manual
Problem appears when the Xfce Power Manager locks the session (under the
security tab). When the screensaver locks the screen, I am still able
to log back in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
After add this to /etc/default/grub,
ubuntu@test-2:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic
root=UUID=0ba22f57-08ab-4b84-9592-936a48bd5692 ro console=tty0 quiet splash
vt.handoff=1
ubuntu@test-2:~$
The issues is same which still show as "error: no suitalbe video mode
found
the out put of "virsh dumpxml"
...
...
This should be OpenStack configured for VNC and qemu devices. If I
manual remove them, and the virt-manager can become normally which show
grub menu, boot message and login etc.
--
You received this bug notifi
1 - 100 of 260 matches
Mail list logo
