Public bug reported:
If I right-click on a mounted Removable Device in dolphin I get the
option to "Safely remove it".
This will unmount it and *power it off*!
Which means I need to remove it and plug it back in again to get it to
show up. Not what I want...
This is a change at 19.04. Previousl
FYI: There's a screenshot (in English, so not a translation issue) at
https://bugs.launchpad.net/bugs/1825733
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825733
Title:
ubuntu-release-upgrader-cor
Sorry - that should have said that the screenshot is in:
https://bugs.launchpad.net/bugs/1827669
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825733
Title:
ubuntu-release-upgrader-core shows upgra
Screenshot from an update of my next system to do 18.10 -> 19.04.
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827669/+attachment/5261484/+files/Screenshot_20190504_114508.png
--
You received this bug notification because you are a
Public bug reported:
I ran:
pkexec do-release-upgrade -m desktop -f DistUpgradeViewKDE &
to update Kubuntu 18.10.
The window that popped up had a heading of:
Upgrading 18.10 to 18.10.
(or something along those lines - it was 18.10 to 18.10).
It should have been 18.10 to 19.04.
NOTE: that the up
This is *still* an issue nearly a year on.
A better test line is actually this, which checks for anacron being
present before checking whether it is enabled:
( test -x /usr/sbin/anacron && systemctl -q is-enabled anacron )
The () are needed.
--
You received this bug notification because you ar
This seems to be a timing issue.
I've only ever seen this on my desktop system, which had HDDs. On my
laptop (with SSDs) it didn't happen, even though the desktop set-up was
essentially the same.
And a few weeks ago I switched my desktop system over to SSDs. The
problem no longer shows up there.
Yes. CustomizeMyBird seems to be causing the problem. SafeMode is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801782
Title:
Main window maximizes width on the closing appplication.
To mana
OK. I had a thought.
Started in Safe Mode - all is OK.
So I then went around disabling all extensions and *as I disabled one* the
window maximized width-wise.
That extension is: CustomizeMyBird.
So I'll report the issue there instead.
--
You received this bug notification because you are a mem
I can't find any way to close this report. Please do so...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801782
Title:
Main window maximizes width on the closing appplication.
To manage notificati
I only see this with Thunderbird.
I don't see it with any other application.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801782
Title:
Main window maximizes width on the closing appplication.
T
FYI: As I shut-down Thunderbird teh .xsessions-erros file gets these
entries.
==
1549728585353 addons.xpi WARNException running bootstrap method
shutdown on menuon...@agrude.com: ReferenceError: windows is not defined
(chrome://shimmenuontopecma/content/menuontop_shim.jsm:30:1
>> Expected results:
>>
>> The main window should not have been maximised on restart.
The main window should not have been maximized on shut-down in the first
place!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Yes, this still happens with 60.4.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801782
Title:
Main window maximizes width on the closing appplication.
To manage notifications about this bug go
Sorry - I forgot to add in the original post that streaming the same
stream with mpv worked OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812138
Title:
vlc on mpeg stream with radeon GPU driver
This might be useful(?):
https://patchwork.freedesktop.org/series/45979/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812138
Title:
vlc on mpeg stream with radeon GPU driver produces errors an
Public bug reported:
I tried streaming an mpeg stream (from a digital PVR) with vlc, but the
result was a blank screen (I did get the audio).
The same streaming did work with mpv.
It also worked with vlc on another system I have, which has an Intel GPU
(rather than an AMD one).
This was showing
NOTE: that I tried to add an "also affects" package of:
xserver-xorg-video-radeon
but was told that does not exist - which is odd as that is the packages
I have installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
NOTE that mlst of the problem is the use of "may not", which means "is
not allowed to".
"might not" ("appears not to") is probably intended.
Simply saying "This initramfs image does not contain cryptsetup binaries
nor crypto modules." would be even clearer.
As written it gives the impression tha
NO.
The issue is still there in 18.10.
Processing triggers for initramfs-tools (0.131ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-13-generic
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1807286
Title:
systemd SEGV freezing on install of virtualbox
To manage n
FYI: The 6.0 final installs OK. See:
https://forums.virtualbox.org/viewtopic.php?f=7&t=90239#p436126
(and it worked for me...).
However, there IS still a BUG in systemd (which is where this bug should
be moved - it isn't a virtualbox bug) as it shouldn't be possible for a
package installation
Happens to me to.
First seen when trying to install 5.2.22.
I abandoned that, cleared things up and re-installed 5.2.20 - which worked OK.
I've just tried installing 6.0.3-BETA3. That suffered this issue too.
I cleared things up (didn't wait for the install to "finish") and tried
re-installing 5
Public bug reported:
I have my Desktop Folder settings as:
Layout: Folder View
Location: Show the Desktop folder
The icons are arranged how I want them and locked in place (a 3x8
array).
When I login the icons can be wrongly arranged. This does not happen
every time, but does seem more likely t
Public bug reported:
Dolphin is using physical device names to identify locally-attached
devices.
The result of this is that if I boot a system with an external drive
(USB) attached and that happens to be detected first (which happens
every time on my laptop) then the local partitions, which are
Part of this (the "It is left marked as unmounted and nothing shows in
the listing display. But the device is actually mounted..." part) is
still an issue, and reported separately at:
https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1806154
--
You received this bug notification because you
Public bug reported:
It's trivial to get Dolphin to show a Removable Device as mounted (a
green icon) after Dolphin has actually unmounted the drive.
Steps to reproduce:
1. Plugin a removable device. This will show up in Dolphin under "Removable
Devices"
2. Click on it to mount it.
3. Open a Te
Good.
I've tested that patch in 4.18.0 and can confirm it works.
https://bugs.freedesktop.org/show_bug.cgi?id=108712#c14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
[regression] Wr
They've found the bug!!
https://bugs.freedesktop.org/attachment.cgi?id=142443
Is there a mechanism for getting this patched into the current Cosmic
kernels (and, presumably, Disco)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
I've opened:
https://bugs.freedesktop.org/show_bug.cgi?id=108712
** Bug watch added: freedesktop.org Bugzilla #108712
https://bugs.freedesktop.org/show_bug.cgi?id=108712
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Thanks.
I'll add relevant links (both ways) if I can as I report it on that site.
If the code hasn't changed in the graphics development branch I may submit a
report now anyway...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Or I could post a comment to the commit mentioned in #14 - see what the
author (from Intel) thinks?
Not sure how much printk()s would tell me - the debugfs already shows it
ends up with only 4 EUs pre sub-slice instead of 8. I'll give it a go,
though. But I (might) need signed kernels...I assume i
I've been looking (briefly) for some docs on the Intel GPU hardware
layout.
Came across this:
https://01.org/linuxgraphics/documentation/hardware-specification-prms
leading to:
https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-bdw-vol04-configurations_3.pdf
which says that a
Only affect Cosmic. Bionic is OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
[regression] Wrong EU count for i5-5250U, reducing OpenCL performance
To manage notifications about th
OK. So I have to run as root *while logged in to desktop of the system*.
Just being logged in as root (on a system where I "never" user the
console...) over the network isn't good enough.
Now done. It claims to have submitted data. I'll change the state to
Confirmed.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209801/+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/1800752
apport information
** Tags added: apport-collected
** Description changed:
I run a BOINC project which uses opencl_intel on my Kubunut system
On bioinc the tasks ran in 12,000 +/- 200 seconds.
They've been doing that for ~6 months.
I've now updated the system to cosmic, and the tas
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209800/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
>> I've installed it - it might now be collecting data...
No, it's not. It fired up the OAuth authorization page, which I
authorized (and got the mail confirmation). Now it just sits there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
>> Further information may be available in the files (readable only by root,
>> the 0 may be different if you have more than one graphics device):
Info attached (only 0 has those files) for both Cosmic
(4.18.0-10-generic) and Bionic (4.15.0-38-generic) kernels. (The change
mentioned in #14 seems t
Here's the Bionic kernel info (couldn't seem to be able to attach two
files to one comment?).
** Attachment added: "4.15.0-38-generic (Bionic) dri info"
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+attachment/5209781/+files/dri-info.4.15.0-38-generic.log
--
You received t
apport-collect 1800752
produced:
>> ERROR: The python3-launchpadlib package is not installed. This functionality
>> is not available.
which might explain why the info wasn't there...
I've installed it - it might now be collecting data...
--
You received this bug notification because you are a
Just guessing, but a possible candidate...
https://github.com/torvalds/linux/commit/8cc7669355136f8952779e6f60053c1284d59c4d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance
FYI: Boiled it down to a simple ioctl() call.
= Start code =
/* Read an ioctl value */
#include
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int eu_total;
drm_i915_getparam_t gp;
gp.value = &eu_total;
gp.param = I915_PARAM
And, just for confirmation, with the older Bionic 4.15.0-38-generic
kernel I get:
>> root@nuc:/local/users/gml4410/homework# ./gmltest
>> Got value: 48
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
>> BOINC running - haven't had sufficient time to check relative
processing speed yet.
I can confirm that it is back to "full speed". Jobs are taking ~12,000s
again.
I've rebooted to the previous Bioinc kernel (still there from the upgrade) and
when I run clinfo there I see:
kernel says 48 com
The dh_auto_configure reports this:
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
I've added a python symlink (to python3) in /usr/local/bin to get the
build to run.
but there's a bug in the build logic somewhere.
--
You received this bug notification because you are a membe
Built and installed beignet-opencl-icd_1.3.2-4_amd64.deb with the patch.
clinfo now reports (4 times):
kernel says 24 compute units, hardcoded says 48
Peak GFLOPS reported by BOINC now back at 384.
BOINC running - haven't had sufficient time to check relative processing
speed yet.
System has
Looks like there's a bug in dpkg-buildpackage!?!
There's a update_metainfo_xml.py which, from line1, expects to be run by
python3. but
a) it isn't marked as executable.
b) it produces an error when run by dpkg-buildpackage. A complaint about the
encoding= parameter, so it looks like it's being r
Public bug reported:
If I close thunderbird using File->Quit (or ctrl+Q) the window maximizes
to the screen width just before it closes and retains that max-width on
the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't nor
If it's any help here is the info from the last BOINC startup log under
Bionic and the first under Cosmic.
Bionic:
28-Oct-2018 11:12:30 [---] Starting BOINC client version 7.7.0 for
x86_64-pc-linux-gnu
28-Oct-2018 11:12:30 [---] This a development version of BOINC and may not
function properly
2
Just noticed that the logs in #4 show a difference in the reported GFLOPS peak.
Bioinc says 384, while Cosmic says 192.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance degra
>> Was this report sent from the affected system?
No - sorry. I forgot about that
This is clinfo from the affected system:
Welcome to Ubuntu 18.10 (GNU/Linux 4.18.0-10-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:
...although it is, of course, still a bug in bionic, which is an LTS, so
probably closing this report would not be a good idea?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768676
Title:
Incorrect
** Description changed:
Started an install an selected manual partitioning.
Added sda1 as /boot
Added sda5 as /
- Then realized I'd forgotten to mark sda1 as "Format" so clicked on it's box.
+ Then realized I'd forgotten to mark sda1 as "Format" so clicked on its box.
Crash
===
I've no updated the affected systems to Cosmic and the issue has gone
away. Disks now mount "properly" in dolphin.
I'd close the report, but there is no suitable option - if anyone has a
suggestion for that then please go ahead with it.
--
You received this bug notification because you are a mem
Public bug reported:
I run a BOINC project which uses opencl_intel on my Kubunut system
On bioinc the tasks ran in 12,000 +/- 200 seconds.
They've been doing that for ~6 months.
I've now updated the system to cosmic, and the task are not taking
19,000 +/- 200s.
I have another system (which is s
Has it been fixed in/checked for 18.10 (Cosmic)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new version
To manage notifications
Public bug reported:
Start plasma-discover because there are pending updates.
Click on "Update all".
When the authentication box pops up Cancel it (I've decided I now want to look
at some information before continuing).
The box goes away.
Click on "Update all" again. It greys-out all buttons, pre
>> I don't think there is a solution for this problem.
So why has it only started to happen recently?
What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Happened again last night when:
gir1.2-packagekitglib-1.0
libpackagekit-glib2-18
packagekit
packagekit-tools
went from 1.1.9-1ubuntu2 to 1.1.9-1ubuntu2.18.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
>> In case it helps, I printed today to a non-existing printer. (Or not
>> connected now)
>> This might be the reason.
That's interesting. The system on which I had the problem also had an "unusual"
printer defined.
I have a Brother printer/scanner, so add the Brother-supplied driver (more
opti
I've had to reinstall 18.04 on this system to make it usable.
It now works - with (essentially) the same configuration and with no change to
my $HOME files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
There have been two sets of updates in the last week that are security ones, so
the taskbar icon has a red dot.
After clicking on this and installing the updates Discover reports there are
none. However, the taskbar icon continues to say that there are updates (now
with a b
PS: The attached system info refers to the system after I'd run a
successful install and configuration. It's not from the installation
screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770402
Tit
Public bug reported:
Started an install an selected manual partitioning.
Added sda1 as /boot
Added sda5 as /
Then realized I'd forgotten to mark sda1 as "Format" so clicked on it's box.
Crash
=
Traceback (most recnt call last).
File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/Par
I've found the two attached crash files for this issue in /var/crash/
** Attachment added: "crashes.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+attachment/5136461/+files/crashes.tar.gz
--
You received this bug notification because you are a member of Ubu
A few other things.
The affect system has these cups processes running:
root@parent:/local/configs/packages# ps -ef | grep cups
root 3421 1 0 01:49 ?00:00:00 /usr/sbin/cupsd -l
lp3423 3421 0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus
dbus://
lp3424 3
Public bug reported:
System was running fine then the desktop background went black. I continued to
work for a while to tidy things up (open window were OK) and rebooted.
Any attempt to login will produce a black screen shortly after the desktop is
displayed.
The problem is related to this:
[
Well, it's probably not dolphin per se· If I use the dolphin binary form
17.10 exactly the same thing happens, so it's more likely the underlying
mechanisms.
And there is another, probably related, issue.
If I plug in an external USB drive the Device Notifier pops up in the bottom
right of the s
Another set of (related?) issues with this dolphin.
If I right-click on an entry under Devices and select "Open in New Window":
if there is no mount error I get a new window, but it is displaying my Home.
if there is a mount error I get no new window (which may be correct...)
If I right-cl
Public bug reported:
This is new at 18.04 (I've just upgraded from 17.10, which was fine).
I open up dolphin and click on an entry under Devices (a mixture of non-auto
mounted local devices and external USB ones).
What I now see happening most times is that the device mounts but I also get an
e
This is still a bug in 18.04 (and was in 17.10 as well).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688148
Title:
Unexpected behaviour when choosing "Other problem"
To manage notifications about
Public bug reported:
The packagekit package has just been updated by discover (Kubuntu) from 1.1.7-1
to 1.1.7-1ubuntu0.1.
Discover reported that the packagekit daemon had crashed.
The resulting dpkg status is:
[parent]: dpkg-query -l 'packagekit*'
Desired=Unknown/Install/Remove/Purge/Hold
| Sta
> I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I have a system running bionic and it's fine (see #34). Always has been. It's
never run anything else (just over 2 weeks old...). It's always had the "new"
(3.20180312.0~ubuntu1
I've tested the artful kernel on a UEFI system (and tracked own how the
signed kernel is produced from the unsigned on in the debs at he same
time - see #76).
It fixes the issue (tag already changed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Well, I *think* I can answer my own question about the signed image.
The signed image was *not* generated by my installing the lp1759920 kernel.
In fact it is the identical file to the one from:
https://launchpad.net/ubuntu/+archive/primary/+files/kernel-signed-image-4.13.0-38-generic-di_4.13.
My other system (no UEFI) does seem to be OK on this new kernel - and it
is actually running it:
[parent]: cat /proc/version_signature
Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
[parent]: cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.13.0-38-generic
root=UUID=ca819911-be41-4822-8720-4536f278aa56 r
These are the packages I have installed:
root@gmllaptop:/local/configs/packages# dpkg-query -l '*4.13.0-38*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
Well, I have a problem testing that kernel.
I've downloaded the linux-image and linux-image extra debs and installed
them with dpkg -i.
Rebooting (with the new microcode) hangs.
But on rebooting and checking /proc/version_signature I see:
Ubuntu 4.13.0-38.43-generic 4.13.16
which makes no sense
> Define *old* microcode
The microcode from 3.20180108.0+really20170707ubuntu17.10.1:
[parent]: dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0x29, date = 2013-06-12
microcode: sig=0x206a7, pf=0x2, revision=0x29
microcode: Microcode Update Driver: v2.2.
If Intel
>> Also ran:
>>
>> https://raw.githubusercontent.com/speed47/spectre-meltdown-checker/master/spectre-meltdown-checker.sh
FWIW: I just ran that on my system with the *old* microcode, and it
reports "NOT VULNERABLE" for all three variants too.
--
You received this bug notification because you ar
I've since left the 4.13.0-38-generic kernel + 3.20180312 microcode +
apparmor=0 option running for >30 mins (top constantly running plus a
short compilation using all 4 cores in parallel, make -j4, of a github
download).
It still looked OK.
--
You received this bug notification because you are
> if someone affected wanted to boot with the apparmor=0 kernel command
line option (with the latest artful kernel, without the noibpb kernel
command line option, and with the latest intel-microcode package), I'd
really appreciate it.
Just done this:
Downloaded latest microcode (3.20180312).
Repl
> A lot of the time, people's login name gets renamed from a central
authority...
Another solution would be to get that policy changed, as it's not a good one.
Such a policy would be a nightmare in any industry that has to track who does
what for regulatory purposes, where user ids should be cons
Actually
systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759846
Title:
Incorrect test used for anacron b
A modified postrotate rules that works is:
postrotate
if systemctl -q is-enabled smbd && [ -x /usr/bin/smbcontrol ];
then
/usr/bin/smbcontrol smbd reload-config
else
/bin/true
fi
endscr
Ignore the attached modified conffile - I'm reporting this from a
different system to the one I've fixed this on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760855
Title:
logrotate rules do not
Public bug reported:
The logrotate rules for log.smbd and log.nmbd assume that if
/usr/bin/smbcontrol can be run then samba can be restarted.
This ignores the fact that it is possible to have samba installed, but to have
it disabled (you may wish to only enable it for running tests, then disable
>> And adding 'noibpb' kernel boot parameter helps, at least in my case.
However, according to:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown/MitigationControls
doing that,
"Disabling these features removes mitigations for CVE-2017-5715 (aka Spectre /
Variant 2).", wh
> By any chance, do all of you have sssd installed?
No. I don't have it installed on any of my systems, two of which are
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759920
Title:
intel
This is a similar thread on Arch Linux:
https://bugs.archlinux.org/task/57511
Includes the comment:
"Wasn't the 20180108 microcode update retracted because of issues? Maybe we
should downgrade back to 20171117."
There is no 20180108 download available at Intel now:
https://downloadce
>> Well, 4.13.0-32 seems to be unaffected...
Only because it isn't the latest kernel you have, so it has never had
the latest microcode added into it - it will still be loading the
previous (working) version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>> Installing or removing intel-microcode only runs update-initramfs for
the latest kernel
I eventually noticed that too.
So it means that the problem follows the microcode - nothing to do with the
kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
FYI: These are the signatures for my three systems.
Failing for these on 17.10 (4.13.0-37-generic):
signature 0x000306c3 (and for 4.13.0-38-generic)
signature 0x000206a7
OK for this on 18.04beta (4.15.0-13-generic):
signature 0x000306d4
--
You received this bug notification be
For me, on my laptop (Intel(R) Core(TM) i5-4330M CPU @ 2.80GHz) with Kubuntu
17.10, the 4.13.0-38-generic kernel (signed image) has the same problem.
In fact it was slightly worse, a it seems to have wiped out my Ubuntu UEFI
booting (boots straight to Windows - I can get to the Ubuntu menu from t
> Could someone test out the 4.13.0-38-generic kernel from artful-proposed
> to see if you experience any lock ups with the 3.20180312.0 microcode?
Any simple install instructions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Bug #1760095 (mine) reports it for two 17.10 systems (Intel graphics only) both
on 4.13.0-37-generic.
An 18.04beta system 4.15.0-13-generic with the "same" microcode version is OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
/etc/crontab uses
test -x /usr/sbin/anacron
for whether anacron is handling the daily/weekly/monthly cron jobs on a system.
This means that if anacron is installed it is assumed to be running.
However, this is a service, and can be disabled and since the package is
insta
This isn't a 17.10 regression - it's been happening for a few years,
e.g.:
https://bugs.launchpad.net/mos/+bug/1475019
And, FWIW, I added the flags=(attach_disconnected) to the config file
yesterday on one of my systems and whereas it does seem to have removed
the operation="sendmsg" reports,
101 - 200 of 202 matches
Mail list logo
