Hi, dhcpig is working for sure with python 3 since version 1.5-4 (in
Debian at least, can't be sure for Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063966
Title:
version not compatible
Apparently everything is ok in the file. However, as you can see in the video I
posted on YouTube, when accessing after restarting the computer, or even after
a few minutes of use, these keys become disconfigured. In the video, the keys
that I had previously configured appear normal, but when
I turned on the computer this morning, and the shortcut I made using the
"super+down" key to reduce the computer's sound volume did not work
correctly. "super+up" worked as expected, it increases my sound volume,
but "super+down" didn't work. It seems that when restarting the
computer, there is a
When I make the insertion work. The problem is when I restart, it comes
back unconfigured.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064169
Title:
Keyboard shortcuts
To manage notifications
Public bug reported:
I don't know if the section is correct, but when using the ubuntu
keyboard shortcuts I added. Increase sound volume, when you put the
super+up on, it ends up doing the behavior of another one that I had
already removed to give way to this new one I made.
ProblemType: Bug
thanks for your help
Em ter., 26 de abr. de 2022 às 06:05, Chris Guiver <
1970...@bugs.launchpad.net> escreveu:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better.
>
> Bug reporting is mostly about finding & fixing problems thus preventing
> future users from
Public bug reported:
ubuntu mate 20.04 installation message:
"error creating directory
'./usr/src/linux-hwe-5.13-headers-5.13.0-40/-arch/sh/include/cpu-sh3':Read-only
file system".
My PC has amd-64 processor, 4G ram...
thanks folks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1969863/+attachment/5583612/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since there's so many questions that need to be asked before it becoming
a definitive Bug Report, like if it's affected by some third-party
packages or system configuration/modification done by me, I converted it
into a question seeking better support.
So, the reason it was originally a
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+question/701476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
This packages appeared to be upgraded, when attempting to upgrade it
trough discover, a message appeared saying that kubuntu-desktop and
ubuntu-release-upgrader-qt will be removed. Trough the terminal, they
aren't upgraded trough `sudo apt upgrade`, but instead trough `sudo
Thanks for the help! It seems to be fixed using the new Ubuntu 20.04.4's
Mesa (Mesa 21.2.6).
Tested Mesa 22 and kernel 5.15 trough some PPAs and it seems to also work
really fine!!
Can't wait for Ubuntu 22.04!!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: autotools-dev (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/1743051
Title:
package autotools-dev 20150820.1 failed to install/upgrade: le
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1958236/+attachment/5557364/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958236
Title:
Kernel 5.13
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+bug/1958236/+attachment/5557363/+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/1958236
Title:
Kernel 5.13
** Attachment added: "allpackages.txt"
https://bugs.launchpad.net/ubuntu/+bug/1958236/+attachment/5557074/+files/allpackages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958236
Title:
I removed the kisak-Mesa PPA, Mesa was reverted to 21.0.3 and now these
games are not even launching, but at least the following error appears
on the log files:
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 0 ()
Serial
Public bug reported:
These games on Kernel 5.11.0-46 used to work fine, didn't crashing at
all, but after the system updating its kernel to 5.13, hangs/crashes
constantly started occurring on those games.
Description:Ubuntu 20.04.3 LTS
Release:20.04
Kernel: 5.13.0-25-generic
i have the exact same problem on kubuntu 20.04. can i help?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928512
Title:
Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
To
Public bug reported:
i can't using snap store and aptitude
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: libapache2-mod-wsgi-py3 4.7.1-3build2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Public bug reported:
Hello, I am able to access localhost normally, but sometimes a window
opens saying there is an error with Apache
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: apache2 2.4.41-4ubuntu3.5
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux
According to Intel, this bug has been fixed in the microcode updates
released in the 20210608 package.
HOWEVER one must go from BIOS to the newest microcode update directly,
using kernel early updates. This is how it is supposed to happen by
default in Debian (and, AFAIK, Ubuntu nowadays) so it
So, according to Intel, the probable cause for 0x406e3 and 0x506e3
processors to fail loading the microcode update *early* is an
incompatibility when you update from a very old microcode release in
BIOS/UEFI (BIOS has a revision older/smaller than 0x80) to the newer
microcode updates.
This
** Changed in: aeskeyfind (Ubuntu)
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/1417160
Title:
aeskeyfind doesn´t work as expected on big files
To manage
** Bug watch added: Debian Bug tracker #989179
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179
** Also affects: aeskeyfind (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989179
Importance: Unknown
Status: Unknown
--
You received this bug notification
Public bug reported:
I'm currently trying to fix my NVIDIA drivers and can't seem to do it as
it crashes when I tried to run it. I already tried reinstalling the
drivers, but I can't fix it ;(
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460-server (not installed)
You are advised to keep the microcode for skylake D0 and R0 locked at
revision 0xd6 using a microcode revision override when backporting
3.2028.1.
That is signatures 0x406e3 and 0x506e3. Override to revision 0xd6.
Otherwise, systems with old microcode (lower than 0x80) can hang.
--
You
/bugs/1913866
>
> Title:
> intel-microcode 20201118 bump request
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1913866/+subscriptions
>
--
Henrique de Moraes Holschuh
--
You received this bug notific
For model 78 stepping 3 processors, look here:
https://github.com/intel/Intel-Linux-Processor-Microcode-Data-
Files/issues/31
To put it bluntly: update your system firmware. If no such update is
available, pressure the system vendor into releasing one. For now,
that's the only available fix.
For the record: systems with firmware outdated enough to actually hit
this microcode update issue *most likely* have several other critical
security issues in their Intel platform, not just in the processor.
The outdated firmware not only blocks you from updating the processor
microcode (thus
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: henrique 1142 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 20 17:06:22 2020
InstallationDate: Installed on 2020-12-16 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "
Public bug reported:
During Ubuntu Installation process, something happens that it failed to
install Grub.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
The new microcode update from 20201110 has rev 0x40 for this microcode,
can you check if it improves the situation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900149
Title:
Microcode update
Public bug reported:
When I tried to upgrade from Ubuntu 20.04 LTS to 20.10 using Ubuntu
update-manager an error happens:
"Invalid package information
After updating your package information, the essential package 'ubuntu-minimal'
could not be located. This may be because you have no official
Public bug reported:
This is the output of the terminal when I tried to upgrade from Ubuntu
20.04 LTS to Ubuntu 20.10:
$sudo do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1.338 kB]
A patch fixing this issue was incorporated in version 0.99-2.
** Changed in: easygit (Ubuntu)
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/1593949
Title:
ERROR
A patch fixing this issue was incorporated in version 0.99-2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593949
Title:
ERROR message: Unescaped left brace in regex is deprecated
To manage
*** This bug is a duplicate of bug 1499985 ***
https://bugs.launchpad.net/bugs/1499985
** This bug has been marked a duplicate of bug 1793014
Plank prevents windows from moving between monitors if vertical & not
autohidden
** This bug is no longer a duplicate of bug 1793014
Plank
** Also affects: ubuntu
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793014
Title:
Plank prevents windows from moving
Same with peppermint 10-amd-64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807537
Title:
failure in fsck option of advanced boot
To manage notifications about this bug go to:
Debian will also issue such an update, but we have both "works" and
"fails" reports of 0x506e3.
We're waiting for some more data re. 0x806eX and 0x906eX, but the
situation there is far less clear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Debian bug report:
https://bugs.debian.org/962757
Facts from debian bug report:
Hang only on rev 0xd6 (20200609), works with previous revisions (including rev.
0xca). Since the bug doesn't always trigger, maybe rev 0xd6 made it easier to
trigger.
** Bug watch added: Debian Bug tracker #962757
That's enough, it confirms that the bug is *fixed*.
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855784
Title:
Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot
Fixed by upstream 20200609 release.
** Changed in: intel-microcode (Ubuntu)
Status: Confirmed => 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/1855784
Title:
Intel Microcode
Arnaud, there were some revisions of that security update. Could you
retry with the newest? If it still hangs, please check if one of the
open bug reports matches your processor model and report there.
Otherwise, please open a new report and add your processor model to the
bug title, and in the
~ Two years later... :-)
Intel does not keep their microcode guidance docs up-to-date, a new one
is issued when they deem it necessary, and they're related to a specific
issue being addressed.
The processor specification updates are still as opaque as always, and
are slowly getting even harder
This has been reported to be fixed on very similar processors (with the
same microcode signature as yours) in the 20200609 microcode updates,
could you test them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, now we need more testing to know if it works or not, since it is
kinda expected that some microcode updates would object *heavily* to
late-load but work just fine from the early-initramfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I see. I will keep that in mind for the future, I thought you guys were
doing late-loading triggering *only* inside the initramfs, and not
during the update...
Well, blacklisting it from late-loading is a no-brainer. I will do that
too for Debian, although Debian never late-loads automatically.
ings can (and likely will) happen* the next time you reboot.
If the reboot to activate the microcode update does hang, does it also
hang when powering up the computer with the new microcode package
installed (instead of rebooting)?
--
Henrique Holschuh
--
You received this bug notification b
Good morning sir
I'm sorry my english is not very good (I'm portuguese)
The title is another problem I have . When I open Terminal in the first
line show me (image).
Thank for your help
I'm not a developer but a single user, but I try again todo do what you
mean
Thank you
Jorge Carmo
Public bug reported:
I don’t know how repair my system
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-51.44-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture:
Public bug reported:
Ubuntu-Mate menu icons are not showing, and my language is: pt-BR
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mate-applet-brisk-menu 0.6.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion:
Public bug reported:
sudo do-release-upgrade -d
Verificando por uma nova versão do Ubuntu
Obtendo:1 Assinatura da ferramenta de atualização [1.554 B]
Obtendo:2 Ferramenta de atualização [1.344 kB]
Obtidos 1.346 kB em 0s (0 B/s)
Torchat version 0.9.9.553-2_all.deb
Ubuntu 18.04.4 LTS i686
Kernel: 4.15.0-94-generic
** Affects: torchat (Ubuntu)
Importance: Undecided
Assignee: Rodrigo Henrique (gatofladigo1)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
close to late loading.
The target audience of late loading is, as far as I know, gigantic cloud
provider senior engineers with proper NDAs signed with Intel and access
to relevant support channels and non-public information.
I am not adding this change to Debian, FWIW.
--
Henrique Holschuh
-
Yes, the previous kernel and others from Ubuntu 19.04 or 19.10 were quick.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859429
Title:
Boot took much longer with repeated error message PCIe
I appreciate the quick answer and will investigate more the boot time. It might
be something hidden.
Thank you very much. This 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/1859429
Adding: lspci -vnvn
** Attachment added: "lspci -vnvn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859429/+attachment/5319765/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hi,
I saw this message in several other bugs but I am using the newest kernel.
Right after upgrade the kernel the boot took several minutes and a message was
being repeated several times in screen:
[ 340.489762] pcieport :00:1c.5: AER: Corrected error received:
Public bug reported:
Reinstalling ubuntu mate 19.10 didn't work cause of read-only error.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.21
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
This is likely better done in Debian.
That said, dpkg-statoverride seems like a possible layer to extend. It
is responsible for updating the owner and permission of files installed
by packages, after all. Extending it to deal with capabilities, or for
that matter POSIX ACLs and Linux extended
Public bug reported:
just dont install thats all
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion:
version 4.15.0-55 has serious problems with Hard Disc
control.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Henrique Watanabe (henrixwat)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Henrique Watanabe (henrixwat)
** Description chan
Public bug reported:
```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
, a new version of Asus
firmware) will be more compatible.
Until then, you will depend on Asus issuing bios/uefi updates (and you
have to apply them to get the fixes).
--
Henrique de Moraes Holschuh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello,
Release 20190618 is out, and has these updates.
I uploaded it to Debian unstable a few hours agoand we will issue it as
a security update as well soon.
I imagine Ubuntu will do the same.
--
Henrique de Moraes Holschuh
--
You received this bug notification because you are a member
Public bug reported:
~apt-get install xserver-xorg-vt-get install xserver-xorg-video-intel
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you
Public bug reported:
grub-install/dev/sda failure
this is a factal error
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Public bug reported:
the execution of grub-install/dev/sda failured
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.7 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic
Public bug reported:
udev failed to upgrade during the upgrade from 18.04.1 LTS to 18.10.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: udev 239-7ubuntu10.6
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion:
signee: (unassigned) => Samuel Henrique (samueloph)
** Changed in: nmap (Debian)
Status: New => Fix Released
** Changed in: nmap (Debian)
Assignee: Samuel Henrique (samueloph) => (unassigned)
** Changed in: nmap (Debian)
Assignee: (unassigned) => Samuel Henrique (s
Setting to incomplete, since the fact that spectre, ssb and l1tf
mitigations are expensive (and utterly so for some workloads) is well
documented and well known, and there is nothing we can suggest unless we
know the under-the-hood details of the affected workload.
** Changed in: intel-microcode
I have just uploaded intel-microcode 3.20180807a.2. to Debian, which
does distribute 0x206c2.
All other microcodes cited on this bug report have been properly
distributed by Debian, and presumably by Ubuntu. As far as I am
concerned, this bug is either fixed-upstream (in Debian), or more-
Public bug reported:
I have a Lubuntu installation, in which I cannot upgrade because
grub2-pc refuses to install. After a while I found that linux-
image-4.15.0.38-generic also not installs, but grub2 in the main one,
because every apt installation is extremely long, since it tries to
install
re, or do the same.
--
Henrique Holschuh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795594
Title:
Microcode for 206C2 Westmere EP is missing
To manage notifications about this bug go to:
https://
** Changed in: intel-microcode (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/1795594
Title:
Microcode for 206C2 Westmere EP is missing
To manage
For 0x206c2:
Refer to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907402
0x206c2 is missing *from the Debian and Ubuntu packages* on purpose, but
we could ship it if Intel explicitly tells us it is not going to
permanently disable a box that has a very old BIOS with the blacklisted
SINIT
@pragyan:
Confirmed by @nanook on #18 that the problem still exists on the Linux
microcode package 20180807a.
Also, by the bug report date, this issue has existed in the relevant
microcode updates for a while: it is not a recent regression.
** Summary changed:
- intel-microcode when installed
>From reports elsewhere in the Internet, made by Microsoft Windows users
with KB4100347 installed. Behavior in Linux might be slightly different.
* Several motherboard vendors affected (at least ASUS, EVGA);
* Motherboards based on X99 with overclocking features available through vendor
@nanook:
What we need explicit testing for is this: does the latest version of
the intel-microcode package which is present in the latest Ubuntu
(Cosmic Cuttlefish *or* up-to-date Bionic Beaver/18.04.01 LTS *or* up-
to-date Xenial LTS 16.04.01) disables overclocking on the i7-6850K ?
To test
is bug report has "Artful" in the title.
--
Henrique Holschuh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748543
Title:
intel-microcode when installed on an i7-6850k based system
Looks like I should add:
As far as I know, Ubuntu Artful is now unsupported, so users of Ubuntu
Artful must ensure they switched to Ubuntu Bionic Beaver *or* manually
update their intel-microcode package to the one in Bionic Beaver for
them to have microcode 0xb2e.
I am not sure this will
@pragyan:
Ubuntu is shipping the same microcode updates as Debian, so I can answer
that.
The current version of intel-microcode in Debian and Ubuntu ships what
is inside Intel's 20180807a "Linux microcode" package as far as the
Intel x86-64 processors are concerned.
For the i7-6850K (sig:
ure Intel is really to blame here, it depends
entirely on the motherboard vendor not doing *anything* unsupported [by
Intel] to further enhance the overclocking capabilities of the
motherboard.
So, you'd need to ask your motherboard vendor *and* Intel about it, to
know the full story...
--
For the record:
Now that Microsoft started distributing the recent batch of Intel
microcode updates, there are reports everywhere from Windows 10 users,
that the Microcode updates do break i7-6850K over-clocking. As
expected, really.
The recommended action is to demand a firmware update from
Public bug reported:
the system is currently presenting some troubles related to updating
packages
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libc6-dev-i386 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
Basically, *you* need to know if:
1. your workload does a LOT of syscalls (kernel entries from userspace)
OR
2. your workload does a LOT of VMEXITs (runs on a VM) OR
3. uses Intel SGX (you're on your own in that case, go talk to Intel).
Which are directly impacted by the microcode and/or
For guidance on how to set kernel parameters:
https://wiki.ubuntu.com/Kernel/KernelBootParameters
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789719
Title:
severe performance issue after
Can you give us the with-old-microcode and with-new-microcode contents
of /proc/cpuinfo, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781806
Title:
With intel-microcode 3.20180425.1, Xorg
I am afraid you need to disclose a _lot_ more information about your
workload for us to even have an idea how you'd hit such an extreme
slowdown effect...
Also, what mitigation modes have you enabled in the kernel, etc.
--
You received this bug notification because you are a member of Ubuntu
I believe this is fixed in the latest version of intel-microcode
available on every still-supported branch of Ubuntu...
Can you confirm and close the report, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
20180807 has license problems, and cannot be distributed at the moment.
Debian is waiting for Intel to address the matter. I assume Canonical
will do the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, I couldn't even download it, but, I think this might be my
computer out of disk for it.
I also have a Windows installed on it, but it is an notebook with 4 of RAM
and an jntel I3, so I prefer using Linux on it. Much faster, well done
On Mon, Jul 30, 2018, 23:40 Alex Murray
wrote:
>
Public bug reported:
I don't know more info
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.4
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
Dell XPS 13 9343 here too, running Ubuntu 18.04.1 with 4.15.0-23-generic.
However, I do not use the same method as @mes2k for BIOS updates. I just boot
into Windows to install the .exe... Therefore I have nothing under /boot/efi
that could be causing it...
➜ ~ sudo dpkg-reconfigure
#43 worked for me. Thanks for the work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Title:
Bluetooth not working
To manage notifications about this bug go to:
Public bug reported:
I'm try to install mysqld-server and ubuntu crash.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Public bug reported:
3,7 GiB
Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz
Intel® HD Graphics 520 (Skylake GT2)
64-bit
970,9 GB
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gir1.2-javascriptcoregtk-4.0:amd64 2.20.3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-128.154-generic
Fix 0.6-3.1+deb8u1 released on Debian
** Changed in: bwm-ng (Ubuntu)
Status: New => Fix Released
** Changed in: bwm-ng (Ubuntu)
Assignee: (unassigned) => Samuel Henrique (samueloph)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
1 - 100 of 834 matches
Mail list logo
