The "sudo dhcpcd" command worked to get my network back. I had to do
another update/upgrade cycle before network-manager would re-install.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
After the extensive upgrades of today no network. As per this bug
report, network-manager seems to be gone. In my case this is a 24.04
Ubuntu Desktop QEMU/KVM VM running on my main Debian server host.
In my case the command was "sudo apt dist-upgrade"
** Attachment added: "dpkg listing"
Hi Christian,
Thank you for your reply to my post.
> I do not know the ping pong test,
A simple token passing ring, that is useful for getting the system to utilize
shallow idles states. Otherwise it can be difficult to get to such shallow
states on my test system, without them being timer
Lots of good comments. I sort of agree with:
> So if we're going to make a change, there
> should be due diligence to demonstrate a
> benefit, it should not be based on
> Internet hype.
However, I would have said:
If irqbalance is to be included by default, then there should be due diligence
Thank you for your incredibly thorough analysis of this. Since finding
this via bug 2046470, I have tried, without success, to create a test to
show any difference in performance or power or whatever between
irqbalance enabled/disabled on my Ubuntu 20.04 test server.
While my vote carries little
I tested apt version 2.0.3. This:
sudo apt install gnome-user-docs* gnome-getting-started-docs*
whereas it did not before, and I had to use Gunnar's workaround from
comment #6 above.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug
@Gunnar : Thank you for the workaround. It solved my problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1872200
Title:
apt does not accept globs and regexes in some
For what it's worth, the versions of things in my test computers, all
servers, no GUI:
name: serv-ff (a 20.04 VM, that has not had an update since around February
12th):
initramfs-tools: 0.133ubuntu14
kmod; 26-3ubuntu1
name: s18 (a physical i5-9600K based computer, up to date as of a few days
I think bug 1864992 and this one are duplicates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864436
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file()
** Changed in: kmod (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992
Title:
depmod: ERROR: ../libkmod/libkmod.c:515
I have a 20.04 VM that I had not run for awhile (Feb 12th). It has kmod
version 26-3ubuntu1, and installed mainline kernel
5.6.0-050600rc4-lowlatency fine.
The other two physical 20.04 test servers have kmod version 27-1ubuntu1,
and both spew the error 5600 times during kernel installation the
Ever since the default changed to never blanking the screen, and after I
whined in comment #18 above, I have been running this in
/etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT=" consoleblank=300 "
always save a copy of grub first, and do "sudo update-grub afterwards",
then re-boot.
--
You
** Changed in: serverguide
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1604010
Title:
sntp missing
Status in Ubuntu Server
The changes that were introduced in kernel 4.13-rc1 have been reverted
in kernel 4.14-rc8 (and queued for backporting to stable kernels).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
This is not a bug, the change was done on purpose. What is displayed
here and under /proc/cpuinfo has changed. For Intel processors it simply
displays tsc now.
One of several upstream references for this is:
https://bugzilla.kernel.org/show_bug.cgi?id=197153
If you want to observe your current
@John: O.K., I think this excerpt from kern.log is what you might be
looking for.
** Attachment added: "kern.log.txt"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+attachment/4995556/+files/kern.log.txt
--
You received this bug notification because you are a member of
Further to my comment #32: That setup then breaks lots of stuff if I
subsequently boot a normal default kernel (i.e. 4.4.0-96-generic). I'm
going back to just booting with apparmor disabled.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@John: That patch works great, thanks.
On kernel 4.14-rc6 + patch, I re-did the stuff from my comment #22,
which in turn was implementing one of the methods from your comment #19.
This time it worked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@John:
I tried your suggestion on my main 16.04.3 test server. I edited
/etc/apparmor/parser.conf, keeping an "original copy" first.
And used "the hand edited features 4.14 feature file attached".
It made things worse, as in addition to mysql and libvirt not starting,
now the network doesn't
John wrote:
> Ubuntu's parser is missing upstream commit r3700, resulting in this failure.
Is there any boot option that would allow Ubuntu mainline kernels to work?
For my own work, and as mentioned in comment #3, I am compiling with "#
CONFIG_SECURITY_APPARMOR is not set".
--
You received
> I've found that it's more than just cups blows up, some networking
> related items (DHCP client, network manager IIRC) also explode.
yes, and libvirtd and mysql.
I was not aware of "teardown". I'll try it when I get a chance.
--
You received this bug notification because you are a member of
Paul wrote:
> I am using Linux 4.14-rc3+.
O.K. that is/was really important information.
While I have been calling this a kernel regression, it might be that a
great number of apparmor profiles need to be updated to accommodate the
new security stuff that was introduced in kernel 4.14-rc2 (it
Which kernel are you using?
On my development 17.10 Desktop, I get the same as you but only for mainline
kernels 4.14-rc2 and 4.14-rc3. Earlier kernels, including mainline 4.14-rc1,
seem to be fine with respect to this issue.
--
You received this bug notification because you are a member of
> Well, Doug, it preserves the latest 2 kernels.
> You have several 4.13 and 4.10 builds, and 4.13 > 4.10 > 4.4.
Didn't it used to ignore manually installed kernels and only count
automatically installed kernels?
This issue only came up about a year or two ago, I think.
> Note that your version
** Attachment added: "I'll attach the entire 01autoremove-kernels file as a
text file"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1427910/+attachment/4941613/+files/01autoremove-kernels.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
In my case autoremove wants to delete the second-latest regular kernel
version. Maybe because I have a bunch of mainline kernels installed
also.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
autoremove seems to want to remove the second to last regular kernel on my
systems also.
I always have a bunch of mainline kernels installed on my computers, and maybe
that is the reason.
Example:
$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state
** Changed in: serverguide
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1604010
Title:
sntp missing
Status in Ubuntu Server
Kernel 4.12-rc1 has this change, so the console now defaults to never
going blank. I disagree with this change.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/869017
Title:
@fish : Yes your issue does not belong here.
To figure out where your issue actually belongs, some details are
missing:
If your stuck at low frequency issue only occurs after a suspend and on
battery power, then your issue is covered by:
https://bugzilla.kernel.org/show_bug.cgi?id=90041 (and it
The now upstream committed solution to this issue (
https://github.com/logrotate/logrotate/issues/93 ) does not change the
default way logrotate worked in the past. So now it just has to make its
way downstream.
--
You received this bug notification because you are a member of Ubuntu
Touch
In addition to the proper fix for this issue, they are wanting to make a
fundamental change to how weekly log rotation works by eliminating the
migration to Sunday portion. This part of the change should NOT be done,
in my opinion. Before it is too late, Please chime in on the upstream
thread.
** Description changed:
Over the last few Ubuntu releases, the status file the logrotate
- generates and uses has been adding more and more detailed time stamp
- information.
+ generates and uses has added more detail to the time stamp information.
In 12.04 it seems to only keep
There is also issue 93 at GitHub:
https://github.com/logrotate/logrotate/issues/93
I seem to be unable to create a GitHub account so that I can add to the
issue discussion, and point to here.
** Bug watch added: github.com/logrotate/logrotate/issues #93
Public bug reported:
Over the last few Ubuntu releases, the status file the logrotate
generates and uses has been adding more and more detailed time stamp
information.
In 12.04 it seems to only keep information to the day.
In 14.04 it seems to only keep information to the hour.
In 16.04 it seems
@Haw Loeung: In addition to what I wrote earlier:
> With the new Ubuntu archive servers, we saw constantly high load
> and after some tinkering, we found that it was mostly CPUs
> being woken up to see if they should enter idle states.
> Changing the CPU frequency scaling governor to
@Haw Loeung: It would be good to understand in more detail your
findings. As far as I know (and I am not an expert in this area), great
care has been taken to avoid things like wakeups just to decide to go
idle.
I did a test on my computer (Ubuntu 16.04 server, no GUI), but to avoid
extra
The table formatting got messed up, trying again:
Load: idle0.5XX 2X 3X 4X 5X 100%
powersave 570811037 16075 29147 45913 61165 76650 81695
3.817.3610.72 19.43 30.61 40.78 51.10 54.46
performance
Using kernel 4.8-rc5 I did some energy tests, using a SpecPower simulator that
I made one time. I reused intel_pstate powersave data from a previous test.
Reference:
http://marc.info/?l=linux-kernel=147326197513427=2
Big numbers are Joules (package Joules from turbostat)
Smaller numbers are
>> The preferred governor with the intel_pstate driver is powersave.
> Do you have some references/proof for that? This is contrary to what
> kernel developers say, see comment 1.
In my opinion, that reference is obsolete.
While I don't work for Intel, the intel_pstate CPU frequency driver is
What has been done here is incorrect.
The old "ondemand" script was modified so that if the intel_pstate
driver was being used, and therefore "ondemand" did not exist, it would
fall through to setting the "powersave" governor (refer to bug
#1314643). Note that "powersave" with the intel_pstate
Correction 1: Stefan not Stephan, sorry.
Correction 2: Things broke down about another 1/2 day after the lease times
changes to 1 hour. The client didn't seem to release this and resorted to
broadcast type discover stuff. Then it was getting leases for 5 minutes, and
the cycle continued until I
>From Stephan comment 14:
"Hm, of course, if one starts dhclient in debug mode (foreground) by
adding a "-d", everything does work."
Yes, that does seem to work, but only for about another day, at least in
my case. Thereafter, my ISP stopped returning my domain name, host name
and some other
Stefan, I think the answer is yes. Just a few minutes before my lease was going
to expire, I did: "sudo dhclient enp4s0"
However, I didn't notice any change in the leases file, so I expected internet
it to stop working after the expire time, but it didn't stop working. So I
looked at my tcpdump
Well, that one got set as a duplicate of this one. Please see also bug
#1551415.
I did manage to avoid having to re-boot, via the Rob Whyte method "sudo
dhclient eth0", however my leases file is now out of date, but I did
observe a new lease actually being granted via capturing the packets on
This occurs also on my server, and as of two days ago.
My system is not renewing the lease of its IP address from my ISP.
(while I have static IP adresses, my ISP still requires using dhcp). The
expire time is 24 hours, and exactly 24 hours since my last re-boot,
internet stopped working.
*** This bug is a duplicate of bug 1543794 ***
https://bugs.launchpad.net/bugs/1543794
Yes, I think bug #1543794 is a duplicate.
** This bug has been marked a duplicate of bug 1543794
isc-dhcp-server fails to start on second & further attempts with 'Can't open
/var/lib/dhcp/dhcpd.leases
4.3.3-5ubuntu8 does fix the apparmor issue. However, now my IP address
lease does not renew.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1549736
Title:
dhclient needs
Note 1: isc-dhcp-server 4.3.3-5ubuntu8 does not fix this issue.
Note 2: There seems to be other apparmor issues, one of which was fixed
by isc-dhcp-client 4.3.3-5ubuntu8. The other remaining one is with
named:
Feb 27 07:53:07 DOUG-64 kernel: [ 21.320614] audit: type=1400
Yes, isc-dhcp - 4.3.3-5ubuntu8 fixes the issue with the dhclient stuff
that caused this:
Feb 26 14:05:21 DOUG-64 kernel: [ 17.518717] audit: type=1400
audit(1456524321.220:10): apparmor="DENIED" operation="open"
profile="/sbin/dhclient" name="/etc/ssl/openssl.cnf" pid=483
comm="dhclient"
I am suggesting that the issue was fixed by this:
2016-02-17 17:24:06 upgrade isc-dhcp-server:amd64 4.3.3-5ubuntu4
4.3.3-5ubuntu5
And then broken again by this:
2016-02-26 08:22:59 upgrade isc-dhcp-server:amd64 4.3.3-5ubuntu5
4.3.3-5ubuntu7
--
You received this bug notification because you
I can not seem to run the requested command. I just get this:
ubuntu-bug 1540672
No pending crash reports. Try --help for more information.
Note: while experienced at bug reports and such, I have never ever
successfully run any of the collect stuff.
** Attachment added: "the requested file"
This issue has returned. I'll supply the extra requested information as
soon as I can.
** Changed in: isc-dhcp (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in
Oh, I see there was an update to this stuff a few minutes ago. It seems
to fix the issue. I couldn't find the original profile file in any
source package nor could I find any bizzare branch on launchpad, so I
installed it on another server and copied the file back to the problem
server,
Yes, I am seeing this issue with an up to date Xenial (well, updated yesterday).
I can not undo the changes to the profile. Why not? Because I didn't know that
aa-logprof didn't make a backup file before messing with the file, and I had
not saved one myself. However, I'll see if I can find it
I used aa-logprof and it came up with the the attached file. Now I can run
apparmour in enforce mode. i.e.
"sudo aa-enforce /usr/sbin/dhcpd"
** Attachment added: "an apparmour profile with changes so that it works"
Try disabling apparmour. That fixed it for me. see also bug 1540672.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1543794
Title:
isc-dhcp-server fails to start on
I gather I was supposed to file this under isc-dhcp instead of
apparmour.
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
The claim in comment number #4 is:
> This bug was fixed in the package installation-guide - 20160121ubuntu2
Then why can I not find the master source code at:
https://code.launchpad.net/~ubuntu-core-dev/installation-guide/ubuntu
?
--
You received this bug notification because you are a member of
Public bug reported:
I only seem to be able to make my dhcp server work properly by disabling
apparmor.
With apparmor enabled it seems to complain that it is unable to open the leases
file for append.
With apparmor either disabled completely (via linux command line in grub), or
set to complain
** Changed in: pm-utils (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1493156
Title:
pm-suspend aborts if highest numbered
As of kernel 4.4-rc1 this bug becomes invalid, as the kernel was patched such
that this issue no longer occurs.
I'll wait until kernel 4.4 is finished, check again, then set the status of
this bug report to invalid.
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Kernel 4.2 includes a significant commit
(87549141d516aee71d511138e27117c41e8aef68), after the patch the files
and directory are present even if the CPU is offline. If the CPU is
offline, writing to those files isn't allowed and so the echo in
94cpufreq fails.
If the failed
, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:
grep MHz /proc/cpuinfo
to observe CPU frequencies.
The commit that, I think, fixes this issue is:
commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies
Requested information. Fresh server installation from Wily daily a
couple of days ago:
doug@serv64-dev:~$ sudo sudo -V | head -1
Sudo version 1.8.12
doug@serv64-dev:~$ sudo sudo -V | grep -e ve: -e HOME
Environment variables to remove:
PYTHONHOME
Environment variables to preserve:
Public bug reported:
Just to separate the variables, use a different Turn screen off when
inactive for time and Lock screen after time under Brightness and
Lock under System Setting.
Leave the system inactive.
The screen goes blank after the appropriate inactive period.
After the additional
I changed this from won't fix and set the importance to high. Why
because it has to be fixed and should actually be critical.
** Changed in: sysvinit (Ubuntu Trusty)
Status: Won't Fix = Confirmed
** Changed in: sysvinit (Ubuntu Trusty)
Importance: Undecided = High
--
You received
Why are you not going to do this for Trusty? Many of us (well, O.K. me)
have been forcing the use of the intel_pstate driver in 14.04 and
14.04.1. Now it is my understanding that the intel_pstate driver will be
enabled by default in 14.04.2.
--
You received this bug notification because you are
There has been some regression with this file, because the above
mentioned change was originally done a long time ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
For my post above please note that there is not a regression, as I did
the edit to /etc/init.d/ondemand myself a long time ago, and then forgot
that I had done so.
Since your are changing back from the intel_pstate driver being disabled
by default to enabled by default, this change needs to be
*** This bug is a duplicate of bug 1314653 ***
https://bugs.launchpad.net/bugs/1314653
** This bug has been marked a duplicate of bug 1314653
sysvinit: default cpufreq governor to powersave for intel-pstate driver
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Under vivid, the serverguide validation script gives and error:
doug@desk-dev:~/sguide-trunk/serverguide$ scripts/validate.sh
serverguide/C/serverguide.xml
--Validating serverguide/C/serverguide.xml ...
serverguide/C/serverguide.xml:2: element legalnotice: validity error :
Bug 1382059 is duplicate with bug 1298505. The serverguide has already
been fixed for 14.04. The bug remains open for the 12.04 serverguide,
but is unlikely to ever be done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
In my case this was a new 14.10 installation from the daily ISO of
2014.09.16. It was todays updates that created this issue, but the last
update I did was September 30th.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity
74 matches
Mail list logo
