Public bug reported:
I can't deploy Bioinc on the P8 system "modoc", it will run into a
kernel-panic situation (power9 system works fine).
Output from IPMI console:
[1.910940] Loaded X.509 cert 'Build time autogenerated kernel key:
c68a20e7bfd228430401173121559235d0c5ceb1'
[1.911145]
Output from an IPMI console.
** Attachment added: "ppc-log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775855/+attachment/5150279/+files/ppc-log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
How did you add the certificate to the user? Following
https://www.freeipa.org/page/Howto/Client_Certificate_Authentication_with_LDAP
perhaps? Is that howto still up-to-date for your deployment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fyi, Bionic unapproved queue:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=
** Description changed:
Since the two wsgi modules are conflicting, installing gnocchi-api
breaks other OpenStack services.
+
+ [Impact]
+ Installation of gnocchi-api (which is py3 only) on the same
** Tags removed: neutron-proactive-backport-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750777
Title:
openvswitch agent eating CPU, time spent in ip_conntrack.py
To manage
Thanks Andreas, I had missed this in the previous discussion.
First, I must say it's a very clever hack :)
I have not looked at it deeply yet, but I have some initial questions:
- Can you describe a bit how you imagine the changes to xkeyboard-config
would look with this approach?
- Do you
Since they might be related, lets focus on the second issue first, which
is cause by the missing files.
I'll set up a test system to try and reproduce.
It seems like this is a regression, but it would be good to confirm.
Can you test these two kernels?
Last 4.14 Bionic kernel:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
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/1725163
Title:
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
Your USB stick has files from xenial and kali on it. You need to clean
the stick before reusing it on another distro or release.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Joseph,
I couldn't exactly reproduce this as it happens during deployment. BUT
the closest I could get was deploying 16.04.4 (4.13) and then installing
4.17 once I was up and running. So I did that, and I am able to reboot
the system into 4.17:
ubuntu@fesenkov:~$ uname -a
Linux fesenkov
also 3D view - create picture creates an unusable picture.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773532
Title:
Sweethome3d 5.7 can't import furniture library
To manage notifications about
Sorry for the late reply.
Can you try 18.04? Without any "acpi_osi=" parameter of course...
Also, please ask the vendor which device should control the brightness?
I can see the PEGP's _BCM method reference to GFX0's _BCM, maybe it can
only be called on GFX0 directly?
--
You received this bug
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm trying on trusty and just found out realmd there segfaults when
joining
On Fri, Jun 8, 2018, 12:30 4tro <1775...@bugs.launchpad.net> wrote:
> Yes, seems right.
>
> I have setup a system with ubuntu 18.04, and the problem doesn't show up
> there.
>
> --
> You received this bug notification
How did you add the certificate to the user? Following
https://www.freeipa.org/page/Howto/Client_Certificate_Authentication_with_LDAP
perhaps? Is that howto still up-to-date for your deployment?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed
I built a second test kernel with the updated patch you posted in comment #3.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1775235
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of
** 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/1775526
Title:
package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
You have been subscribed to a public bug:
We are unable to get http responses from qemu guest machine until
interface inside qemu guest machine is in promiscuous mode.
Our configuration is following:
| Host server|
You are right, thanks for pointing that out. Updated patch attached.
--
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/36812
Title:
Keyboard layout change on hotkeys press instead of release
** No longer affects: df-libreoffice
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/689349
Title:
[Upstream] Draw file exported to PDF have erroneous pixel-sized dots
in Acroread, not in Evince
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Project changed: qemu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463909
Title:
virtio: networking not working when guest's eth0 is not in promiscuous
mode
To manage
Dear xorg developers. This is an old bug. In fact this is a 13 years old bug.
And it has been at least 7 years since this bug had a patch to fix it.
Yes, existing patch breaks specification. But one would seem that the fact that
patch existed for 7 years and was applied by default by popular
I've only run the Xorg session. If that helps I'll run the Wayland
session for a while to give feedback on all the bugs I've encountered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775635
Title:
>From the test history, this P8 node was tested with 4.15.0-21, which
mean that the deployment works with some version earlier than
4.15.0-21, and at least it can boot with 4.15.0-21 in the last cycle.
So it's a bit odd to me to see the deployment failure here, as it should
be deployed with
** Description changed:
If a user, already running a Gnome session upgrades or install unity by
installing unity-session, background plugin doesn't start automatically
(with u-s-d). This plugin has been removed from gnome-settings-daemon
- and since gsd doesn't use it, it gets turned off.
+
Public bug reported:
Version 66.0.3359.181 (Official Build) Built on Ubuntu , running on
Ubuntu 16.04 (64-bit)
local-link IPv6 adresses (fe80::/10) are tricky. Network interface has
to be added to tell OS what interface to use (all network interfaces
have address with prefix fe80::)
So this is
** Summary changed:
- virtualbox-dkms installation hangs in 18.04
+ virtualbox-dkms installation hangs in 18.04 (with secure boot)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775672
Title:
Public bug reported:
Ubuntu Version 18.04 LTS
gdm3:
Installed: 3.28.0-0ubuntu1 500
Package name: /etc/gdm3
Whenever I boot Ubuntu following installation from the official install
ISO, the boot screen appears, but the login manager appears as static,
scrambled graphics, making me unable to
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
this is not possible when launching from a USB or DVD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767633
Title:
Installation of Ubuntu 18.04 crashes
To manage notifications about this bug go
Public bug reported:
[Impact]
It is not possible to perform a network install over the onboard NIC.
[Test Case]
Perform a d-i network install.
[Fix]
There are fixes for this upstream that cleanly cherry-pick back to bionic's
kernel.
[Regression Risk]
Fixes are restricted to the netsec driver
Public bug reported:
It is missing the packages to recreate the initramdisk after enrolling a
luks partition. It is also missing the yubikey-luks-open utility. You
need to get someone to setup yubikey full disk encryption on a test
system. You will identify a lot of missing utilities.
**
I'm trying on trusty and just found out realmd there segfaults when
joining
On Fri, Jun 8, 2018, 12:30 4tro <1775...@bugs.launchpad.net> wrote:
> Yes, seems right.
>
> I have setup a system with ubuntu 18.04, and the problem doesn't show up
> there.
>
> --
> You received this bug notification
Public bug reported:
some grub2 file error is present.
ubuntu is not insatlling
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture:
** Summary changed:
- Fixes for NIC on socionext board
+ Network installs fail on SocioNext board
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775884
Title:
Network installs fail on SocioNext
@Mark Stosberg - thank you for adding your voice to the bug report. I
was wondering if this particular bug was mainly to do with Bay Trail
(Celeron/Atom) based CPU's using an SSD as their main storage, but if it
is affecting the Dell XPS 9370 then that rather scuppers my theory ;)
Can you just
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1758378
and then change the status of the bug to 'Confirmed'.
If, due to the
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
--- Comment From gwal...@br.ibm.com 2018-06-08 12:57 EDT---
I got a Boston
I used a kernel with proposed patches and I did not see a hang of error
in dmesg after ipmi test in KVM guest.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received
Hello.
> Your disk is currently partitioned to boot in bios mode
I did not know that. I currently have a double boot with Windows - and
said Windows was installed by another person. I assumed that I was in
EFI mode because I assumed recent Windows did not accept bios.
Sorry.
I finally manage
** Description changed:
-
SRU Justification
Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
I've just got an automated email saying that my bug #1775790 is a
duplicate of bug #1753012, but if I try to open it, I get a not found
page, I suppose because these reports are private to the subscribers.
This bug affects us too. We tried working around the issue by switching
to a locale which provides timestamps in a shorter format by default
(e.g. DD.MM.YY) so it would still fit into the greeter box, but
apparently simply overriding $LANG and $LC_TIME is not enough to affect
the PAM messages.
--
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/oem/4.13.0-1030.33/oem-4.13-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
Looks like this was fixed in Artful onwards but still affects Xenial
(but workaround for Xenial available as described).
** Also affects: anope (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: anope (Ubuntu Xenial)
Status: New => Triaged
** Changed in: anope
Public bug reported:
I've been using libreoffice off and on for a few years. When I tried to
use it today on my Ubuntu 16.04 LTS system, it wouldn't come up.
Clicking on the icons causes no action. Running "libreoffice" from the
command line silently hangs (nothing is printed, but the process
(In reply to Oleg from comment #151)
> Did the old patch work for you? I mean could you switch the layout pressing
> Ctrl while combos like Ctrl-S also worked as expected?
Which patch do you mean when you say "old"?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
[Impact]
When registering a new binfmt_misc handler, it is possible to overflow
the offset to get a negative value, which might crash the system, or
possibly leak kernel data.
Here is a crash log when 25 was used as an offset:
BUG: unable to handle kernel paging
(In reply to Oleg from comment #149)
>
> And the layout switching - does it occur when you press Ctrl+s? Could you
> please test with Ctrl+Shift?
No, it does not. Currently I could not to test multi-keys switching
combinations.
--
You received this bug notification because you are a member of
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1775858
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1775855
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1775856
and then change the status of the bug to 'Confirmed'.
If, due to the
** No longer affects: xserver-xorg-input-synaptics (Ubuntu)
** Project changed: evdev => xserver-xorg-input-evdev (Ubuntu)
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Importance: Medium => Undecided
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Won't Fix => New
**
Oh how I wish it were possible to edit lauchpad comments...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905441
Title:
Compiz does not integrate well with the system colour scheme
To manage
I found out what was breaking transparency, sort of; it was not related
to this bug report.
Still, for a while compiz was following my system color scheme for quite
a while, until one day it went back to Ubuntu orange and purple and I've
had to manually set colors ever since.
--
You received
Trying to install grub & system on SSD, data (and existing win 7) on
separate disc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/289101
Title:
Ubiquity crashed while installing grub
To manage
** Summary changed:
- SIGSEGV on internal_getent nss_files/files-XXX.c:251
+ NSS is unreliable in statically linked binaries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613067
Title:
NSS is
Ubuntu 18.04
The same problem
# service lighttpd status
● lighttpd.service - Lighttpd Daemon
Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor
preset: enabl
Active: failed (Result: exit-code) since Fri 2018-06-08 17:03:43 CEST; 16s
ago
Process: 28595
*** This bug is a duplicate of bug 173 ***
https://bugs.launchpad.net/bugs/173
@fossfreedom: Bug #173 made me test a British Ubuntu install
(comment #13) and I saw the same result. The fact that Ubiquity
uninstalls certain langsupport packages, which are on the ISO, is not
wrong
Public bug reported:
After the update, totem does not play any video.
the only error is about some gtk widget.
Gstreamer works, since
gst-launch-1.0 playbin uri=file:///file.mp4
correctly plays the video.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.14.0-1
Public bug reported:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename: bionic
uname -r
4.15.0-22-generic
How to reproduce:
1) connect dock station
2) disconnect dock station
3) type: systemctl suspend
Hello Iain, or anyone else affected,
Accepted gst-libav1.0 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gst-
libav1.0/1.14.1-1~ubuntu18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Public bug reported:
GNU Wget 1.17.1 built on linux-gnu. (Ubuntu 16.04 amd64)
IPv6 local link addresses (fe80::/10) are tricky. Network interface has
to be specified to tell OS what interface to use. wget cannot handle
that
First, IPv6 address, no interface specified, it fails with an error
Hello Iain, or anyone else affected,
Accepted gstreamer-vaapi into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gstreamer-
vaapi/1.14.1-1~ubuntu18.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Iain, or anyone else affected,
Accepted gst-plugins-bad1.0 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-
plugins-bad1.0/1.14.1-1ubuntu1~ubuntu18.04.1 in a few hours, and then in
the -proposed repository.
Please help us by
Hello Iain, or anyone else affected,
Accepted gst-rtsp-server1.0 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/gst-rtsp-
server1.0/1.14.1-1~ubuntu18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hi Joseph,
We gave it a try internally and it looks good. Passed the same set of
tests I ran with the previous kernel you provided: works with mq
disabled, enabled and also passes a simple io integrity test.
Thanks,
F.
--
You received this bug notification because you are a member of Ubuntu
--- Comment From thorsten.di...@de.ibm.com 2018-06-08 11:49 EDT---
(In reply to comment #24)
> It would be useful to request IBM QA to rerun this particular testcase on
> 18.04 LTS to check if things are still just as broken, or have become better
> or worse. This will at least gives us
Public bug reported:
When trying to upload a sdist (tar.gz) package to PyPI from Bionic, I
get the following error:
TypeError: expected string or bytes-like object
(see also https://stackoverflow.com/questions/49806586/twine-upload-
typeerror-expected-string-or-bytes-like-object)
Uloading a
We've an undefined $VERSION in config/binary which is resolved by
https://code.launchpad.net/~rcj/livecd-rootfs/xenial-
proposed/+merge/347703 (which also brings the zero'ing of the UEFI
partition from the same release)
** Tags removed: verification-needed verification-needed-xenial
** Tags
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker.
We understand the difficulties you are facing,
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
No, I am only talking about myself, as a developer of xkbcommon; as I
said, I am not a xorg developer so I cannot speak for that. I do not
really mind if the spec is actually changed or not, what I am interested
in is:
1. A clear and precise description of the proposed change.
2. A serious
--- Comment From wenxi...@us.ibm.com 2018-06-08 11:10 EDT---
linux-x6bg:/usr/src/packages/BUILD/systemd-v234+suse.160.gd5dfab21f # ./udevadm
test-builtin path_id /sys/block/nvme1n1
calling: test-builtin
Load module index
Network interface NamePolicy= disabled by default.
Parsed
Yes, seems right.
I have setup a system with ubuntu 18.04, and the problem doesn't show up
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775636
Title:
sss_ssh_authorizedkeys fails with:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1775875
and then change the status of the bug to 'Confirmed'.
If, due to the
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. A warning message prompted you that this
could be a problem and recommended performing a bios mode install
instead, but you chose not to. You either need to perform the bios mode
install, or
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Marcelo Cerri
It looks like your EFI system partition does not contain the EFI/
directory. Can you check it?
** Changed in: grub-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: Undecided => Medium
** Tags added: triage-g
--
Public bug reported:
ping6 utility, iputils-s20121221, Ubuntu 16.04.4 amd64
IPv6 address can have extension with local interface. It is required to
ping link-level IPv6 addresses (fe80::/10).
Example,
ping6 fails, OS doesn't know where to route packets
user@test$ ping6 -c1
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
You modified your /etc/default/grub file and put an extra quote here:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"i8042.kbdreset=1"
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You have been subscribed to a public bug:
When moving the mouse, if you click any keyboard keys, the mouse will
lag. This was observed in 10.10.
Architecture: i386
DRM.card0.HDMI_Type_A.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status:
** Changed in: nautilus
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/871492
Title:
Copy process pauses/interrupts on file conflict
To manage notifications
Public bug reported:
This ussue appears after entering the follow instructions on terminal:
sudo apt-get clean all
sudo apt-get update
sudo apt-get upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64 2.02-2ubuntu8
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic
Public bug reported:
$ /sbin/hwclock --debug --set --date "2004/10/20 04:10:00"
hwclock from util-linux 2.31.1
System Time: 1528467313.266333
Trying to open: /dev/rtc0
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
ProblemType: Bug
DistroRelease:
I can confirm the crash with drag-drop operations after applying th
patch from comment #76. I opened two instances of Thunar, selected two
different folders and moved a file from one location to the next using
drag-drop. This went ok. However, when moving the file back Thunar
crashed. It turned
Public bug reported:
grub-efi-amd64-signed package failed to install, boot loader crashed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
** Package changed: langpack-locales (Ubuntu) => glibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1492568
Title:
Add new locale en_ID (Indonesian English)
To manage notifications about
** Package changed: ubiquity (Ubuntu) => grub2-signed (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719191
Title:
Black screen with messages after new install 17.10
To manage
I'm affected by this bug. I independently discovered the disable "Use
transparency from system theme" fix.
I don't think I had this problem with an NVIDIA graphics card, it was
only when I changed over to an AMD RX580 that the flickering started.
Ubuntu 18.04
AMD RX580
--
You received this bug
You will need to allow the installer to automatically file a bug report
when it crashes so the relevant log files are attached.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
I can't deploy Bioinc on the P8 system "modoc", it will run into a
kernel-panic situation (power9 system works fine).
+
+ From the testing history, it looks like this can be deployed with
+ 4.15.0-21.22
Output from IPMI console:
[1.910940] Loaded X.509 cert
I can confirm having the same issue on my Ubuntu 18.04 system when using
Wayland, but if I use a Xorg session the shift key is recognized and I
have no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 891 matches
Mail list logo