I tested systemd 245.4-4ubuntu3.12 just now. It worked immediately on
three boots!
raek@mizar:~$ apt-cache policy systemd
systemd:
Installed: 245.4-4ubuntu3.12
Candidate: 245.4-4ubuntu3.12
Version table:
*** 245.4-4ubuntu3.12 400
400 http://archive.ubuntu.com/ubuntu focal-proposed/m
Dan: I just added the PPA, upgraded the packages and did 3 reboots. In
all cases "systemctl" showed "starting" when I logged in and then
"started" some seconds later. So it seems like the problem is solved!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
My problem looks similar to the on reported in the Home Assistant bug
tracker.
raek@mizar:~$ systemctl status systemd-time-wait-sync
... *SNIP* ...
└─508 /lib/systemd/sy
One more boot. This time I checked the timestamp of the
/run/systemd/timesync/synchronized file (and did not run any timedatectl
commands):
raek@mizar:~$ ls -la /run/systemd/timesync
total 0
drwxr-xr-x 2 systemd-timesync systemd-timesync 60 Jul 26 22:51 .
drwxr-xr-x 24 root root
I found these two bug tickets that could be relevant:
https://github.com/home-assistant/operating-system/issues/896
https://github.com/systemd/systemd/issues/8683
I should also add that this seems to happen on the majority of boots for
me, but not every boot. So there is some amount of non-deter
Here is the output from the journal from a boot where time-wait-
sync.service "stuck". (I removed some line relating to syncthing and to
a private IRC bot I run.) After boot I logged in, checked "journalctl"
and saw that time-wait-sync.service was "activating" and then ran
"timedatectl status" and
This is my contents of /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License
Hmm. The systemd-timesyncd package is installed and systemd-
timesyncd.service is enabled.
raek@mizar:~/code/raek-totp-token/firmware$ apt-cache policy systemd-timesyncd
systemd-timesyncd:
Installed: 245.4-4ubuntu3.11
Candidate: 245.4-4ubuntu3.11
Version table:
*** 245.4-4ubuntu3.11 500
This started happen to me in January of February. This is easy for me to
reproduce since it happens at every boot. I would be happy to provide
more information or run more tests if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Public bug reported:
When I start my server running Ubuntu 20.04 the systemd-time-wait-
sync.service is stuck in "activating" state. I noticed this because none
of the systemd timer units triggered, because all the timers depend on
systemd-time-wait-sync.service. Running "systemctl restart systemd
I have now tested initramfs-tools 0.130ubuntu3.12 on bionic and it fixes
the issue for me.
Same test as above.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I have now tested initramfs-tools 0.136ubuntu6.5 on focal and it fixes
the issue for me.
Same test as above.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I have tested initramfs-tools 0.137ubuntu12.1 on groovy and it fixes the
issue for me.
I performed the following test:
1. Setup swap on /dev/sda3
2. Add resume=/dev/sda3 to GRUB_CMDLINE_LINUX_DEFAULT
3. Run update-grub
4. Run pm-hibernate
The system resumes from hibernation.
** Tags removed: ver
>The crashes you mention are probably bug 1916716.
I tried your mentioned workaround and rebooted but Chrome still crashes.
ctrl+shift+alt+r work now tough.
When Chrome crashes I get this in the terminal:
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so:
/usr/lib/x86_64-linux-g
Screensharing with Firefox and Chrome unstable works now in 21.04 but
Chrome stable crashes. While chrome stable will probably start working
before 21.04 is released (both 89 and 90 coming up), electron apps like
Slack and Teams are usually not as fast to update and libpipewire0.2
would be great to
As Ubuntu 21.04 won't have Gnome 40, can this be enabled for the current
version (in 21.04 ofc.)?
It's explicitly disabled for Ubuntu here https://salsa.debian.org/gnome-
team/mutter/-/blob/debian/master/debian/rules#L41-48
--
You received this bug notification because you are a member of Ubuntu
Thank you Christian, that sounds great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802533
Title:
[MIR] pipewire
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Hello, what is the status of this MIR? Getting screen sharing to work in
Wayland would be a huge improvement in times like these and I'm weary of
the "Unassigned, importance low" status that this currently have.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you Liz! I'll see if I have the energy to do that, but with my
company pushing bad remote meeting solutions I might have to :/ Now I at
least know where things stand and what to do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Liz Fong-Jones
What did you do to get xdg-desktop-portal working in Ubuntu?
I installed pipewire (0.3.10-4 avalible in groovy) and tried to pull
xdg-desktop-portal, mutter and mutter-common form Debian but that causes mutter
to immediately crash. After restoring mutter and mutter-common I have
Yep, works like a charm with 3.38.0-1ubuntu1.1 from groovy-proposed here
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/1900729
Title:
gnome-terminal font settings show only italic version o
Thanks for the speedy work! I'm afraid I'm registering problems with the
update, however.
I just got gir1.2-gtk-3.0 through -proposed, and whereas it works as
intended in so far as I can now choose Ubuntu Mono in Gnome Terminal and
get the regular font face, it seemingly introduces a bug where gno
@Sebastien: No, I've not noticed the bug for a long while. It must have
been fixed in later Ubuntu versions somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743043
Title:
Evince sometimes fai
Public bug reported:
I originally experienced this on Pop!_OS but I have reproduced it on a
freshly installed Ubuntu.
1. Ubuntu 20.04 LTS
2. initramfs-tools-core 0.136ubuntu6
3. I expect the system to resume from hibernation when running pm_hibernate
4. The system starts up anew when I try to res
This has been open for over a year, with a fix indicated from the very
beginning. Is there any chance that patch can be applied?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813266
Title:
udhcpd:
*** This bug is a duplicate of bug 1813266 ***
https://bugs.launchpad.net/bugs/1813266
** This bug has been marked a duplicate of bug 1813266
udhcpd: not dying on SIGTERM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the
udhcpd daemon does not react properly to SIGTERM.
That bug if fixed in upstream busybox as of 1.29.0, commit
3293bc146985c56790033409facc0ad64a471084 . That patch should be back-
ported to the busybox 1.2
No, I believe it's resolved.
On Tue, Jul 30, 2019, 10:31 Po-Hsu Lin wrote:
> Do you still experiencing this issue?
>
> ** Changed in: linux-aws (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://
Public bug reported:
The upgrade manager told me to report this.
I don't really have much extra information so if this isn't helpful, just close
the issue.
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: libvlc-bin:amd64 3.0.6-1
ProcVersionSignature: Ubuntu 4.18.0-22.23-generic 4.18.20
I tried installing 4.18, but it persisted. I tried an older kernel, and
then the networking stopped working. I tried re-installing Bionic
Beaver, and when booting from USB everything works. But after install
and update, it's broken again.
--
You received this bug notification because you are a me
@vanvugt, I installed nvidia-driver-390, and now the second display
doesn't work (again). I have removed it, but the damage persists. I'll
see what I can do re disabling in BIOS.
@kaihengfeng, I'd like to test the mainline kernel, but could you give
me a couple of lines on how? I'm guessing I have
I installed an older kernel, and was able to boot and log in. But the
external display (HDMI) still didn't work. In desperation I went to
Settings -> Users -> Automatic Login.
And now everything works. Apart from the fact that my computer can be
used by anyone. So it was a mistake on my part to ta
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244164/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
Af
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244159/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244151/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244154/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244157/+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/1818899
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244152/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244166/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244150/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244155/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244158/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244165/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244160/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
Af
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244163/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Ti
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244162/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244161/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244153/+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/1818899
Title:
Afte
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244156/+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/
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1818899/+attachment/5244149/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818899
Title:
Public bug reported:
I can boot to login, but if I input correct information it freezes. If I
boot in recovery mode and choose to resume boot, I can login. But my
external display doesn't register. If I choose the failsafeX version
there is an error text related to xorg.
I have not had any proble
It can be fixed following the instructions in this answer:
https://askubuntu.com/questions/1029128/inverted-horizontal-scrolling-ubuntu-18-04#answer-1031657
I've had the problem before. It seems like a weird why-bother-choice by
the community / Canonical.
--
You received this bug notification be
This also happened to me.
> Did the upgrade process fail?
no
> If you run 'sudo apt -f install' is any change suggested there?
no
> Did you modify the allowed Secure Boot certificates in your machine's
firmware?
$ mokutil --sb-state
This system does't support Secure Boot
I could have disable
Installing resolveconf fixed it for me, now DNS resolv works after PPTP
disconnects.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778946
Title:
No dns resolution after closing a vpn/pptp connectio
Public bug reported:
The installation program crashed as I should install Ubuntu 16.04.4 x86
on an HP Compaq dx6100 MT desktop. I do not have any idea why.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.6 [modified:
lib/partman/automatically_partition/question]
ProcVersio
I filed it here: https://bugzilla.gnome.org/show_bug.cgi?id=793914
** Bug watch added: GNOME Bug Tracker #793914
https://bugzilla.gnome.org/show_bug.cgi?id=793914
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
The above bug seems to be solved or at least mitigated a bit. With just
having firefox up the CPU usage of gnome-shell is between 2-5%.
Gnome shell is still much less performant than Unity though, by moving
windows, open Activities or dragging the mouse over the dock its CPU
usage quickly jumps to
** Description changed:
Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.
The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly
** Description changed:
Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.
The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly
** Description changed:
Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.
The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly
Public bug reported:
Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open
when I'm logged on using Wayland. There's no problem using X.
The error is very simple. I double click a PDF file in my file manager
and expect it to open in Evince (Document Viewer). And mostly that's
what
Public bug reported:
When booting Ubuntu Linux 16.04 on an M5.large instance, the instance
fails to startup and dies, seemingly during initialization of the NVMe
interface, here's the most relevant lines (full kernel log attached):
[8.840439] Btrfs loaded
[ 61.888098] clocksource: tsc: mask
In Unity it's still triggered by the mouse when placing it near the edge of
the screen. I don't know how many pixels is used but I have never felt that
it has been hard to trigger it.
On Sun, Nov 12, 2017, 14:00 Michele <1726...@bugs.launchpad.net> wrote:
> @Rasmus: what'
This has worked in Unity for many years so it's certenly not impossible.
Now I don't know the code of neither Unity nor Gnome and it may well be
so that Gnome can not support it but the concept itself is very
possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I realized that this is only when I have the dock set to auto hide. With
always visible it's possible to move the cursor to the other screen
without issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
>Is this the sticky edges feature, or generally a cursor barrier
problem?
I don't know if it's the correct name. But the cursor "sticks" on the
edge between the monitors. It should move just like it does when I drag
it on a single monitor.
>Are you dragging a window when the problem happens?
No,
Public bug reported:
The sticky edge thing between monitors is very annoying as the cursor
never ends up where it should when it's moved over to the other screen.
It's annoying to the degree that I feel like I can not use multiple
monitors with standard Ubuntu anymore.
Unity had an option to disa
Same behavior when my USB hub is connected but if I have just the laptop
it works fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1603261
Title:
Grub freezes for a few seconds on every boot
To m
: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rasmus 1996 F pulseaudio
Date: Fri Jul 21 01:17:26 2017
ErrorMessage: subprocess new pre-installation script returned error exit status
Public bug reported:
Even when doing nothing at all, gnome-shell uses around 70% CPU.
```
inxi -t cm
Processes: CPU: % used - top 5 active
1: cpu: 68.6% command: gnome-shell pid: 1399
2: cpu: 50.4% command: Xwayland pid: 1405
3: cpu: 19.7% command: firefox pid: 36
Public bug reported:
Crash when I clicked edit on the profile in the preferences window
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubu
)
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rasmus 1886 F pulseaudio
Date: Wed May 17 10:56:35 2017
ErrorMessage: subprocess
MMAND
/dev/snd/controlC0: rasmus 1750 F pulseaudio
/dev/snd/controlC1: rasmus 1750 F pulseaudio
Date: Wed May 17 09:15:56 2017
ErrorMessage: subprocess new pre-installation script returned error exit status
128
HibernationDevice: RESUME=UUID=40d249fd-931c-48a4-88
Public bug reported:
Update stopped. Possibly reason Old Hardware (Asus A52N)
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: a
I have only been able to reproduce this on our production workloads, and
we've recently downgraded from HWE (4.8.0-X) to GA (4.4.0-66), where we
currently aren't seeing any issues.
If I see the issue reappear, I'll try to verify it with a mainline
kernel, if someone finds a way to reproduce this c
I can confirm hitting this on 4.8.41 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/1666260
Title:
"Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34
To manage notifications about
With the risk of stating the obvious, allowing unauthenticated packages
is not really an acceptable workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513232
Title:
do-release-upgrade no lon
@bitgandtter
Intel added driver support for hardware that is not released yet, so there are
no available firmware.
The only affect it has on any actual system is these warnings, it's nothing to
worry about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@David: That worked! Thank you very much for your help. I hope the
overarching issue is resolved soon :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633819
Title:
Some PyQt4 applications fail to
@David: Thank you; that doesn't seem to work here, tho. When I run apt-get, it
replies with:
E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4’ was not found
E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4-sql’ was not found
It seems it doesn't have access to earlier versions that the installed
Wow, this is an unfortunate surprise after upgrading to 16.10. I cannot
do without Anki. How did you perform the downgrade, David?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633819
Title:
Some P
** This bug is no longer a duplicate of private bug 1505409
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590777
Title:
gnome-shell crashed with signal 5 in _XIOError()
To manage notifications abo
I had this issue too on AWS.
In my case, it was the udev rule for vm-hotadd and the fix as mentioned
previously basically came down to "touch /etc/udev/rules.d/40-vm-
hotadd.rules" which effectively disables the /lib/udev/rules.d/40-vm-
hotadd.rules file (after a reboot).
The udev rule basically
I've verified that the linux-image-4.4.0-23-generic image in xenial-proposed
boots correctly on a c3.large ec2 instance.
uname -v: #41-Ubuntu SMP Mon May 16 23:04:25 UTC 2016
root@ip-10-33-53-135:~# apt-cache showpkg linux-image-4.4.0-23-generic
Package: linux-image-4.4.0-23-generic
Versions:
4.4
Well, they're probably waiting for the patch to hit the LTS kernel 4.4
branch, which will probably happen on the 18th May... Or something like
that.
But you can easily run it until then...
Use the 16.04 Beta 2 AMIs, but just disable kernel updates (say, with
"apt-mark hold") and update everything
Here you go, cpuid -1 -r output.
** Attachment added: "cpuid -1 -r output c3.large instances"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657733/+files/cpuid_raw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
CPUID output posted before was truncated...
** Attachment added: "Full CPUID output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657525/+files/cpuid_full.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Kernel boots correctly on a c3.large with Thomas patch.
I've attached the output of the cpuid command (apt-get install cpuid) on
the instance, in case it has any interest.
** Attachment added: "cpuid command output c3.large"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attach
I can confirm that I can boot with this kernel on a C3.large instance.
If anyone else wants to verify this, the procedure is to boot one of the
failing instances with the Beta 2 AMIs and install the build (and
reboot).
--
You received this bug notification because you are a member of Ubuntu
Bugs
I get the same issue with the build, which seemed weird so I retested and it
looks like I must have mislabeled one of my builds, because now when I build
31c2013e4ea2e594522980acc3d20e88664b19f1, I still get the issue, but if I go
back to a6ebb4464659d35e0516900a8493f9720dd77d67 it works.
Someho
Verified it on multiple instances.
31c2013e4ea2e594522980acc3d20e88664b19f1 is the last good commit.
8ae10f463b7ae3455e9d0507176349c76580995f is the first bad commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
According to my bisect this commit is responsible:
commit 8ae10f463b7ae3455e9d0507176349c76580995f
Author: Vikas Shivappa
Date: Thu Mar 10 15:32:09 2016 -0800
perf/x86/mbm: Add Intel Memory B/W Monitoring enumeration and init
BugLink: http://bugs.launchpad.net/bugs/1397880
The MB
Bisecting...
Current candidate seems to be 31c2013e4ea2e594522980acc3d20e88664b19f1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231
Title:
Kernel Panic on EC2 After Upgrading from 14.04 to 16
I can still reproduce this in 4.6-rc5. See attached boot log.
I might do a bisect on this if I find the time...
** Attachment added: "kernel4.6-rc5.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4650339/+files/kernel4.6-rc5.log
** Tags added: kernel-bug-exists-
I've tested with some instance types with the ami-3079f543 image (eg.
ubuntu 16.04 final with Ubuntu 4.4.0-21.37-generic 4.4.6)
The following instance types fail to start with a kernel panic:
r3.large
c3.large
The following instance types seem to work:
t2.micro
c4.large
m3.medium
I haven't tes
Currently also encountering this issue (the same kernel panic) with ami-
3079f543 on eu-west-1 with a c3.large instance.
So this seems to be a general ubuntu 16.04 on AWS issue and not an
upgrade specific issue. I haven't seen this issue with the beta2 AMIs.
Interestingly I seem to be able to sta
>This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1
Sounds good, but I wonder when this reaches Ubuntu then. Mine is
currently at 1:3.14.2-0ubuntu13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I' having a similar problem with trusty 3.13.0-55:
[601201.817664] 88016e03e000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00
00
[601201.818224] 88016e03e010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00
00 . ..
[601201.818827] 88016e03e020: 00 00 00 00
I ran into this bug as well and checked if it's also present in Debian.
It appears that from spamassassin 3.4.0-2 the relevant code is:
# Update
umask 022
env -i LANG="$LANG" PATH="$PATH" start-stop-daemon \
--chuid debian-spamd:debian-spamd --start \
--exec /usr/bin/sa-update -- \
--g
I have narrowed the problem down to dependent on having access to the
internet. On VLANs with internet access the installer completes without
hanging. Without it hangs 20 minutes before partitioning and 10-15
minutes at "73% .. updating list of available packages. "
There is no evidence in the log
1 - 100 of 269 matches
Mail list logo
