** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => High
--
You received this bug
Would it be possible for you to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18
kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Status: Triaged
** Tags added: cosmic kernel-da-key
--
You received this bug notification
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783922
Title:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
Artful and the 4.13 kernel are now EOL. Can you see if this bug still
exists in the latest supported release?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
*** This bug is a duplicate of bug 1773704 ***
https://bugs.launchpad.net/bugs/1773704
** This bug has been marked a duplicate of bug 1773704
Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in
Bionic 18.04
--
You received this bug notification because you are a
Sorry for the delay. Just to confirm, the test kernel posted in comment
#3 did in fact resolve this bug? If so, I'll submit an SRU request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773704
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775137
Title:
Prevent speculation on user controlled pointer
To manage
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Reviewing the files from your upgrade attempt you seem to have enabled a
PPA that provides Xorg packages. This will prevent the upgrade as that
PPA contains package version numbers greater than the release
Good Aft Reinhard,
I found the crash file and used:
ubuntu-bug —tag=1782404 /var/crash/_usr_bin_transcode.1000.crash
Than a pop-up ubuntu dialog asked I send the report - pressed OK and gone.
I trust it made it’s way to you and your team.
Incidentally, I found a partial workaround using:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (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/1783689
Title:
I ran into this as well on a Dell Precision 5520. I tried all the fixes
listed at
https://help.ubuntu.com/community/SoundTroubleshootingProcedure and
nothing worked. Only reverting to the 4.4.0-130-generic kernel partially
fixed the problem, but sound still breaks when I suspend/resume.
--
You
the commit is probably https://gitlab.gnome.org/GNOME/file-
roller/commit/0ae6cf61 which could be backported to xenial if anyone
wanted to work on a SRU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the issue seems resolved since 3.24
** Changed in: file-roller (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532738
Title:
/usr/bin/file-
*** This bug is a duplicate of bug 1532738 ***
https://bugs.launchpad.net/bugs/1532738
** This bug is no longer a duplicate of private bug 1760257
** This bug has been marked a duplicate of bug 1532738
Will 2:2.0.2-1ubuntu2 released for Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651818
Title:
busybox-initramfs needs different compile options to work with
cryptroot-unlock
To manage
acpidump binary output
** Attachment added: "AcpiTables.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+attachment/5168641/+files/AcpiTables.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
acpidump output
** Attachment added: "AcpiTables.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784008/+attachment/5168640/+files/AcpiTables.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- We have try to create multiple partitions on the raid volume there is a
+ We try to create multiple partitions on the raid volume but there is a
buffer I/O error on Ubuntu 18.04.1
Below is the portion of the kernel log
-
Jul 18 21:17:11 ubuntu kernel: [
** No longer affects: nvidia-graphics-drivers-384 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721988
Title:
Ubuntu 17.10 full disk encryption + Nvidia drivers not booting
To manage
Hi @dgadomski
Yeah, in a new installed version of Kubuntu 17.10 there is NO problem if the
full-disk encryption is not ENABLED, however it also works if you do not
install the Nvidia drivers for Kubuntu. This problem occurs when you decide to
install Nvidia drivers for Kubuntu (as in my case)
** Changed in: f-spot
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/242418
Title:
while importing a photo, F-spot should ask for overwrite or ignore for
one or all
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778486
Title:
x86/kvm: fix LAPIC timer drift when guest uses periodic
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781476
Title:
[Bionic] bug fixes to improve stability of the ThunderX2 i2c
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
** This bug has been marked a duplicate of bug 1611737
Can't upgrade from a release if ros packages are installed from ROS servers
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1611737 ***
https://bugs.launchpad.net/bugs/1611737
** This bug has been marked a duplicate of bug 1611737
Can't upgrade from a release if ros packages are installed from ROS servers
--
You received this bug notification because you are a member of
** Attachment added: "kernal.log"
https://bugs.launchpad.net/ubuntu/+bug/1784014/+attachment/5168639/+files/kernal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784014
Title:
Public bug reported:
We have try to create multiple partitions on the raid volume there is a
buffer I/O error on Ubuntu 18.04.1
Below is the portion of the kernel log
Jul 18 21:17:11 ubuntu kernel: [ 609.572019] scsi 2:3:111:0: Direct-Access
DELL PERC H745P MX5.05 PQ: 0 ANSI: 5
Forget it, since then I have switched to Mint, no more problems.
On Wed, Jul 25, 2018 at 3:29 PM, Paul White <1589...@bugs.launchpad.net>
wrote:
> Lola,
>
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
Later ceph releases (and charms) do support native ceph block device
encryption.
** Changed in: charm-ceph-osd
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Libvirt should NOT be modifying ownership of my ISO images when mounting
them to install a KVM instance. This causes issues later when I use
zsync to update the images from the latest bits at cdimages.u.c. More
importantly, my files should not arbitrarily be
This change was made by a bot.
** Changed in: linux (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/1784008
Title:
brightness keys incorrectly mapped for
I just tried the reproducer steps in bionic, and it worked just fine.
The second screen -r without any further parameters attached to the
right screen.
Can we close this very old bug?
** Changed in: screen (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
I just tried the reproducer steps in bionic, and it worked just fine.
The second screen -r without any further parameters attached to the
right screen.
Can we close this very old bug?
** Changed in: screen (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
And looks like we need to find out what is adding 127.0.0.1 to
resolv.conf. It could come from many different sources, like a
nameserver configuration in some /etc/network/interfaces carried over
from xenial, or something in network-manager, etc. I guess you could
start with a brute-force grep -r
Thanks @goingwc, I have managed to reproduce it here so I can use my own
plymouth log. Turns out I couldn't get even 18.04 working correctly,
because I had integrated GPU enabled in my motherboard settings
(i7-6700K with HD 530) despite nvidia being set to "primary GPU". I had
to disable the
And looks like we need to find out what is adding 127.0.0.1 to
resolv.conf. It could come from many different sources, like a
nameserver configuration in some /etc/network/interfaces carried over
from xenial, or something in network-manager, etc. I guess you could
start with a brute-force grep -r
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783996
Title:
[efi on top of legacy] Show a warning
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754053
I've encountered this bug on the past TWO kernel updates of my Xubuntu
16.04.4 (now .5) system that uses an Nvidia card. Initially I found that
falling back to the previous kernel was a satisfactory workaround. This
morning, I tried using the "Additional drivers" system setting to change
from the
Appears to still be affecting 18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755863
Title:
netbooting the bionic live CD over NFS goes straight to maintenance
mode :
To manage
s/metter/better/!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
linux 4.15.0-1.2 [error: implicit declaration
Had the same issue (after an apt-get dist-upgrade after at least a month
since the last time I upgraded). Comment #5 solved the issue for me.
Surprisingly, I didn't even need to restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After the reboot, whether it was one where rabbit failed to start or
not, does a restart of the rabbit service always work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783325
Title:
After the reboot, whether it was one where rabbit failed to start or
not, does a restart of the rabbit service always work?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1783325
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783438
Title:
Release Upgrader unable to determine upgrade
To manage notifications about this bug go to:
Using Kubuntu 16.04 on a Thinkpad X240 with Intel graphics this problem
also causes Yakuake ("Quake-style terminal emulator based on KDE Konsole
technology") to remain invisible when activated. It still accepts input
and the window is in focus, it just is not visible.
Switching the compositor
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783589
Title:
ubuntu-release-upgrader crashes if snapd is not installed
To manage notifications about this bug go
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783593
Title:
UI frozen and no information when the upgrader is installing snap
packages
To manage
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168632/+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/1784008
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168636/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784008
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168627/+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/1784008
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168637/+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/1784008
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168633/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168631/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168628/+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/1784008
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168634/+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/1784008
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168635/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784008
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168630/+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/1784008
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168629/+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/1784008
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168626/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168624/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784008
Public bug reported:
Hello. For unknown reasons, the brightness up and brightness down keys
on my ProBook 455 G5 are being mapped to F20, which is the microphone
mute key. Because of this, the screen brightness cannot be adjusted by
pressing the brightness keys. However, the screen brightness can
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1784008/+attachment/5168625/+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/1784008
Title:
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18
I solved it, but there is something wrong... Grub lasts so much for booting
ubuntu...
El vie., 27 jul. 2018 a las 15:02, Adrián Negro Pérez ()
escribió:
> I had initially a full instalation of Windows 10, with the UEFI partition
> in FAT32. Then I deleted a 700 GB partition in the right area of
I believe this is what introduced the libibverbs1 dependency:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1692476
"[18.04 FEAT]: qemu: Enable RDMA support in qemu"
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to libibverbs in
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778658
Title:
Nvidia fails after switching its mode
To manage
** Summary changed:
- Libvert changes ownership (user/group) of my ISO images
+ Libvirt changes ownership (user/group) of my ISO images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784001
Title:
I believe this is what introduced the libibverbs1 dependency:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1692476
"[18.04 FEAT]: qemu: Enable RDMA support in qemu"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Milestone: ubuntu-16.04.5 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776259
Title:
Make fips-updates available for xenial
To manage
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status:
here is an updated fix:
https://github.com/systemd/systemd/commit/cde942f61bf231ea4a0d50780cdb4e744458daeb
#diff-5be2770e81c14245e90d2916ded39491
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783994
Looking in /etc/libvirt/qemu.conf, this setting would fix this... why is
the default not 0 here:
# Whether libvirt should dynamically change file ownership
# to match the configured user/group above. Defaults to 1.
# Set to 0 to disable file ownership changes.
#dynamic_ownership = 1
--
You
Public bug reported:
Libvirt should NOT be modifying ownership of my ISO images when mounting
them to install a KVM instance. This causes issues later when I use
zsync to update the images from the latest bits at cdimages.u.c. More
importantly, my files should not arbitrarily be stolen from me
Thanks for your reply. Closing by marking "Invalid" as issue was never
confirmed.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
What do you guys have inside /etc/resolvconf? In terms of directories,
files, and their contents.
Do you have the resolvconf package installed by any chance?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Yes! This two commands also solved my problem with wi-fi after update
from kernel 4.13.0 to 4.15.0 (hwe update) for Ubuntu 16.04.
Thank You All!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777444
What do you guys have inside /etc/resolvconf? In terms of directories,
files, and their contents.
Do you have the resolvconf package installed by any chance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: miniupnpd (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481735
Title:
init script doesn't work correctly with multiple IPs on the
** Changed in: libreoffice (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589215
Title:
'Unknown Application Name' menu item in Indicator Applet Appmenu
Hi,
In the current version I have, the tooltips work fine.
I don't remember how it was fixed for me, but this bag report can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1375407
Title:
I just fall myself in this case and I think this example and my reflection can
help this discussion ...
(Why do I think that you need not only a message, but also a choice box (legacy
/ efi) when installing ...)
My bios has efi disabled. I configured my boot start without efi with:
1 - cd / dvd
Fix is in salsa now, will be in ubuntu at next sync.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
Thanks, I did step #2 (#3 was useless because #2 didn't fail) and the
newly-created bug report is #1783999.
Thanks,
MZ
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu Bionic)
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: livecd-rootfs (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/1783129
** Description changed:
Test Case:
1. On a EFI machine with an existing system installed in BIOS mode (without
an ESP partition), boot 18.04.1 (in EFI mode)
2. Select manual partitioning
3. Resize the main partition
4. Allocate the free space to Ubuntu and do not create an ESP
Bionic and Cosmic are also affected.
** Changed in: clamav (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783897
Title:
dpkg-reconfigure for clamav-daemon
Hello. The patched kernel fixes the issue as I expected it would.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781763
Title:
HP ProBook 455 G5 needs mute-led-gpio fixup
To manage notifications
Bionic and Cosmic are also affected.
** Changed in: clamav (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1783897
Title:
dpkg-reconfigure for
Public bug reported:
Test Case:
1. On a EFI machine with an existing system installed in BIOS mode (without an
ESP partition), boot 18.04.1 (in EFI mode)
2. Select manual partitioning
3. Resize the main partition
4. Allocate the free space to Ubuntu and do not create an ESP partition
5. Proceed
Confirmed:
"MaxScriptNormalize")
StateGeneric low clamav-daemon/MaxScriptNormalize MaxZipTypeRcg
MaxHTMLNoTags
;;
"MaxZipTypeRcg")
StateGeneric low clamav-daemon/MaxZipTypeRcg SelfCheck MaxScriptNormalize
;;
"SelfCheck")
StateGeneric low clamav-daemon/SelfCheck
201 - 300 of 477 matches
Mail list logo
