** Changed in: initramfs-tools (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/1719302
Title:
Please include mlx4 and mlx5 InfiniBand modules
To manage
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661878
Title:
[Asus UX360UA]
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Also affects: linux (Ubuntu Bionic)
Importance: Wishlist
Status: Triaged
--
You
> On 2 Jan 2018, at 9:06 PM, Vasya Pupkin <1740...@bugs.launchpad.net> wrote:
>
>> Apparently the original patch didn’t send for linux stable branch.
>
> I don't know exactly what you mean, but 4.14 kernel has this patch. It's
> easy to verify by changed messages ("enabling ssd optimizations" vs
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Thanks for filing. Would you mind filing this report upstream though?
It's an upstream issue and should be debugged there:
https://github.com/hughsie/fwupd/
** Changed in: fwupd (Ubuntu)
Status: New => Triaged
** Changed in: fwupd (Ubuntu)
Importance: Undecided => Low
--
You
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740861
Title:
Packaging version 2.9
To manage notifications about this bug go to:
** Tags added: needs-packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740791
Title:
[needs-packaging] sstp-client
To manage notifications about this bug go to:
This may also be the cause of https://bugs.launchpad.net/ubuntu/+source
/gnome-settings-daemon/+bug/1722034
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to
«MeeToo».
My Epson Perfection V370 Photo does not work with my newly installed Kubuntu
17.10. With the 14.04-5 it works perfectly.
I do hope you will solve the problem before the Version 18.04 LTS is out.
I am still use the 14.10 as working version, but want to adobt myself with
Plasma5
--
You
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147
Hello guys if you have the Ubuntu 17.10 bios problems and you have warenty you
may want to send the laptop for a possible fix ose better a replacement laptop
, i was luck and they replaced my laptop and
Public bug reported:
There are a couple things going on, that could be fixed by a Debian or
Ubuntu maintainer:
- libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces
the RFKill key: https://lists.freedesktop.org/archives/wayland-
devel/2017-August/034721.html
- x11-proto needs
Attached is an alternative script which sends KEY_WLAN, which does
trigger Airplane Mode, as expected.
** Attachment added: "wlan.py"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1740894/+attachment/5030182/+files/wlan.py
--
You received this bug notification because
In artful and later, a number of kernel drivers send KEY_RFKILL - which
is being ignored by the userspace handling code.
https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL
** Also affects: libxkbcommon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg
Attached is a test script that should trigger Airplane Mode in GNOME,
but does not. The code in gnome-settings-daemon looks for XF86RFKill,
but the key is not identified as such.
This is what xev reports from the script:
KeyPress event, serial 55, synthetic NO, window 0x2c1,
root 0x1ee,
This bug was fixed in the package squashfs-tools -
1:4.2+20130409-2ubuntu0.14.04.2
---
squashfs-tools (1:4.2+20130409-2ubuntu0.14.04.2) trusty; urgency=medium
* debian/patches/0003-unsquashfs-preserve-symlink-times.patch: Preserve
atime and mtime of symlink inodes in unsquashfs
This bug was fixed in the package squashfs-tools -
1:4.3-3ubuntu2.16.04.1
---
squashfs-tools (1:4.3-3ubuntu2.16.04.1) xenial; urgency=medium
* debian/patches/0007-unsquashfs-preserve-symlink-times.patch: Preserve
atime and mtime of symlink inodes in unsquashfs rather than using
This bug was fixed in the package squashfs-tools -
1:4.3-3ubuntu2.17.04.1
---
squashfs-tools (1:4.3-3ubuntu2.17.04.1) zesty; urgency=medium
* debian/patches/0007-unsquashfs-preserve-symlink-times.patch: Preserve
atime and mtime of symlink inodes in unsquashfs rather than using
The verification of the Stable Release Update for squashfs-tools has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package squashfs-tools - 1:4.3-4ubuntu1.1
---
squashfs-tools (1:4.3-4ubuntu1.1) artful; urgency=medium
* debian/patches/0008-unsquashfs-preserve-symlink-times.patch: Preserve
atime and mtime of symlink inodes in unsquashfs rather than using the
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.15
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.15
Oh I just found that dpdk-doc is still depending on python.
So the sync wont auto fix it yet, setting back to triaged.
We would need to check latest doc python code if all would work.
** Changed in: dpdk (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification
Sync of the package is started, this will trigger issues with
openvswitch (patches for that are ready and will be uploaded later on
once in dpdk is ready in bionic-proposed), but therefore the expected
time from sync to fix might be more than usual.
** Changed in: dpdk (Ubuntu)
Status:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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
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.15
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In artful and later, a number of kernel drivers send KEY_RFKILL - which
is being ignored by the userspace handling code.
https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attached is an alternative script which sends KEY_WLAN, which does
trigger Airplane Mode, as expected.
** Attachment added: "wlan.py"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1722034/+attachment/5030178/+files/wlan.py
--
You received this bug notification because
Attached is a test script that should trigger Airplane Mode in GNOME,
but does not. The code in gnome-settings-daemon looks for XF86RFKill,
but the key is not identified as such.
This is what xev reports from the script:
KeyPress event, serial 55, synthetic NO, window 0x2c1,
root 0x1ee,
Hi how i fix this after i format my hdd?? How i boot somthing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
To
Hi Christian Ehrhardt,
I ran:
mysqlcheck -c -u root -p --all-databases
and all my databases returned "OK". So my MySQL Database does NOT appear to
be "broken".
What else might be going on?
Also, if a "broken" database can cause this failure, why not run:
mysqlcheck -u root -p
Thank you for responding to my question/posting. I hope to have a chance
to try your suggestions soon and let you know if I have any luck.
Mark Fossett
On Tue, Jan 2, 2018 at 9:10 AM, ChristianEhrhardt <
1740...@bugs.launchpad.net> wrote:
> Hi Mark,
> Thank you for taking the time to report
** Also affects: ubuntu-release-upgrader (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740523
Title:
Prompt value is set to
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.15
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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
I am sorry, but with the provided details this report isn't actionable.
You have run apt on the terminal so including the ENTIRE output would
have been a good idea, can't do much with the hashsum mismatches –
expect predicting that this is indeed some sort of problem on your end
of the internet
** Changed in: linux-lts-trusty (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740263
Title:
Build action button
To manage notifications about this bug go
** 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/1740290
Title:
Server is EL 7.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1722936
Title:
sssd hbac rule applicaton for AD users is inconsistent
To manage notifications about this bug go to:
This is becoming a persistent problem on numerous servers that I
monitoring/maintain.
I am seriously considering disabling this cron.
Is there anyway I could get some traction on this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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.15
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.15
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.15
Apologies for my lack of feedback but those were quite busy days ...
A small update though: the bug I reported on the MySQL bugs has been set as
duplicate of the following on the bugs.mysql.com portal:
https://bugs.mysql.com/bug.php?id=88844
Severity is S1: critical.
** Bug watch added: MySQL
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Public bug reported:
Ubuntu 14.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-103-generic 4.4.0-103.126~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
Can you see if this issue also happens with the latest daily image? It can be
downloaded from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added:
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.15
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740890
Title:
package linux-image-4.4.0-103-generic 4.4.0-103.126~14.04.1 failed to
install/upgrade:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: roaraudio (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/1588138
Title:
intel-microcode promoted to main in bionic:
Override component to main
intel-microcode 3.20171117.1 in bionic: restricted/admin -> main
intel-microcode 3.20171117.1 in bionic amd64: restricted/admin/extra/100% ->
main
intel-microcode 3.20171117.1 in bionic i386: restricted/admin/extra/100% ->
If we don't yet know what patch in v4.15-rc4 fixes the bug, we can
perform a "Reverse" bisect to identify the fix.
Can you test v4.14-rc1, so we can narrow down the last bad kernel
version and the first good one? It can be downloaded from:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: backuppc (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/1723392
Title:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
*** This bug is a duplicate of bug 1734147 ***
https://bugs.launchpad.net/bugs/1734147
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** This bug has been marked a duplicate of bug 1734147
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
--
You received this bug
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Still an issue with 384.90. In Xorg8.log I see
[272208.772] (II) Loading /usr/lib/nvidia-384/xorg/libglx.so
[272208.773] (EE) Failed to load /usr/lib/nvidia-384/xorg/libglx.so:
libnvidia-tls.so.384.90: cannot open shared object file: No such file or
directory
[272208.773] (II) UnloadModule:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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
Hi Xav, do you have any more feedback on ocata-proposed testing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731595
Title:
L3 HA: multiple agents are active at the same time
To manage
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1740886
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I try to install Ubuntu 16.04.3 but when I finished all the installation's
steps the installation crashed.
Thanks for all your messages !
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4 [modified:
lib/partman/automatically_partition/question]
Public bug reported:
I initially tried to update the firmware of my Logitech K780 Wireless
Keyboard via Gnome Software, and it acted like it was pushing the
update, but then threw an error.
"Unable to update "Logitech K780 Multi-Device Wireless Keyboard" failed
to write @0x10260: failed to get
We've seen a couple of potential regressions in artful, so we should
hold off on this xenial SRU until we've triaged these:
https://bugs.launchpad.net/cloud-images/+bug/1740176
https://bugs.launchpad.net/cloud-images/+bug/1740178
--
You received this bug notification because you are a member of
Omiting architecture makes it default to amd64 afaik; you'd need to know
the list of architectures of the store you're querying, and loop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701232
Title:
I'm now able to boot from my USB. The kernel update thankfully resolved
this issue.
Booting into GRUB, entering the command line and typing "exit" seems to
have worked for me. Of course, this was after I installed Kernel 4.14.9.
Thank you all for the help!
** Description changed:
Public bug reported:
I found the following Warning while running update-manager -d -c from the
terminal to upgrade Lubuntu 17.10 to 18.04.
WARNING **: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ally.Bus was not
provided by any .service
Ideally the store would provide the required information. We get currently:
"""
$ http --pretty=format --print b
https://api.snapcraft.io/api/v1/snaps/details/robotfindskitten
X-Ubuntu-Architecture:arm64 X-Ubuntu-Series:16
#424:
I've installed the following kernel images and headers:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.9/linux-
headers-4.14.9-041409_4.14.9-041409.201712251541_all.deb
linux-image-4.14.9-041409-generic_4.14.9-041409.201712251541_amd64.deb
Booted into Ubuntu 17.10 with the newly
The kernel update worked for my Lenovo Y50-70 and I can now boot from
USB.
Thanks all for those who helped to fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
Ubuntu 17.10
The discard-ns will happen automatically once
https://github.com/snapcore/snapd/pull/4329 lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671421
Title:
Snap apps keep asking installing
Sorry, I forgot to mention that I also tried with Ubuntu 16.04.3 LTS and
I have the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740026
Title:
ubiquity crashed with
This problem only occurs when I try to install an Ubuntu-based distro on my
Teclast X80 Plus tablet (Intel Atom x5-Z8350, 2GB RAM, 32GB EMMC).
I also tried selecting another language (English) but nothing changed.
I can install Lubuntu without any problem using the alternate iso where the
Public bug reported:
I was doing the installation of Ubundu and the installation has crash whew I
have finished all the steps .
Thank you for your messages ;)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4 [modified:
lib/partman/automatically_partition/question]
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740883
Title:
package mysql-server-5.7 5.7.11-0ubuntu6 failed to install/upgrade:
subprocess installed
Thanks for sharing this. This is not a fwupd bug, but a firmware bug.
I believe the root cause to be a clash in the ESRT GUID between these two
machines.
Until the firmware bug is resolved please blacklist the device using the
blacklist option in /etc/fwupd/daemon.conf to prevent trying to
Hi all, this issue affect me too, and I would like to built the DKMS
package for different kernels,
@Pilot6 could you share your recipe to built the DKMS package?
Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Rob, or anyone else affected,
Accepted nova into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Zhenyu, or anyone else affected,
Accepted nova into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Thanks for your report.
Could you please detail the steps to reproduce this crash? I tried with
Lubuntu 17.10, Ubuntu 17.10 and 18.04 with Italian and cannot reproduce
this bug.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Hello James, or anyone else affected,
Accepted openvswitch into mitaka-proposed. The package will build now
and be available in the Ubuntu Cloud Archive in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Hello Xav, or anyone else affected,
Accepted neutron into mitaka-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo
Public bug reported:
.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.11-0ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
AptOrdering:
mysql-server-5.7: Configure
Hi Rahmad,
I see from your logs that you have:
modified.conffile..etc.apache2.mods-available.php7.0.conf: [deleted]
modified.conffile..etc.apache2.mods-available.php7.0.load: [deleted]
I'm not sure since there are not much further good details in the logs, but
that could be your issue.
As that
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to
Hi Mark,
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
You could run:
$ sudo apt update
$ sudo apt upgrade
And report the full output of your console here.
Since so far there isn't enough information in your report to
differentiate between a local
$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)
real0m10.007s
user0m0.001s
sys 0m0.001s
--
You received this bug notification because you are a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Hi Marco,
here from your log:
ERROR: Unable to start MySQL server:
2017-12-28T11:20:26.058037Z 0 [ERROR] unknown variable
'log_slow_queries=/var/log/mysql/mysql-slow.log'
2017-12-28T11:20:26.064217Z 0 [ERROR] Aborting
Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on
Hi Akshay, This has been released for Ocata.
** Changed in: cloud-archive/ocata
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1720397
Hi Akshay, This has been released for Ocata.
** Changed in: cloud-archive/ocata
Status: Fix Committed => 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/1720397
Title:
qemu-kvm
I see that most of the failing kernel autopkgtests for this upload are
simply the usual 'kernel version mismatch' thing, so they shouldn't
potentially block the release of this SRU. Would be good though if the
uploader double-confirms this along with verifying the fix with the new
package.
--
Sometimes the dkms modules get out of sync with the kernel.
Your log file:
/var/lib/dkms/iscsitarget/1.4.20.3+svn499/build/make.log
should have more detail what failed on the upgrade.
Please make sure to upgrade to the latest kernel as well as iscsitarget package
and retry on that.
Sometimes it
Had the same problem in Windows (I think, harder to diagnose on Windows), even
after installing updates for BIOS, firmware & drivers, so this is probably a
hardware problem.
Lenovo support should visit me soon to fix the problem (with new hardware),
I'll give an update after that.
--
You
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
301 - 400 of 616 matches
Mail list logo
