Seeing the same on Ubuntu 18.04.3 with the HWE kernel, 5.0.0-25-generic
AMD A6-9225 RADEON R4
This appears to be tied in to the problems resuming the laptop from
suspended (black screen, flashing cursor)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm confused. Do you need verification or not? Cosmic is not
specifically supported on our platform, and there are no plans at the
moment to support non-LTS releases that I know of. I can certainly test
this if needs be, though.
--
You received this bug notification because you are a member
Public bug reported:
See upstream bug, a new version has been released which fixes this error:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858583
Current version of trace-summary in Bionic is 0.84-1. Upstream released
0.84-2 in July with the appropriate fix. Pulling in the update from
Fix has only been released for Cosmic. Given the package is basically
non-functional on Bionic, is there a plan to backport the fix? There
doesn't seem much point in keeping it in the repository otherwise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Patch submitted to netdev: https://marc.info/?l=linux-
netdev=153695411427176=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790652
Title:
Oracle cosmic image does not find broadcom network
I've been able to replicate the situation with a few different
distributions. It seems to only occur with VMs. When I tried 4.18.7 on
a bare metal instance, there was no problem.
We believe we've isolated the kernel commit that is introducing the
problem to
I haven't specifically seen that one, but I'll check in with both the
Oracle Linux team and our Hypervisor team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790652
Title:
Oracle cosmic image
Public bug reported:
This is probably a bit of a daft one, and it's not blocking me on
anything, but I see this more as a UX bug.
mkfs.ext4dev creates a file system that mount then can't mount, unless
it is told explicitly that it is ext4.
(on a side note, what is ext4dev? Can't seem to find a
That would be a different bug, unfortunately.
Mine was specifically down to ipconfig not handling multiple network
interfaces correctly, triaged and successfully fixed by Canonical, and
exhaustively validated in our infrastructure.
Roughly speaking, it would quickly loop through the interfaces
Note: I've also discovered (unsurprisingly, I guess?) that I see the
exact same behaviour on Ubuntu 14.04. Can this fix be backported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
I've tested and confirmed that this solves the issue on 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
initrd dhcp fails / ignores valid response
To manage notifications about
Given this is a fundamental bug in klibc, is there a plan to try to
upstream this patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
initrd dhcp fails / ignores valid response
To
I took a step back from doing bisecting and focussed on creating a
replication scenario, which I've done successfully.
ipconfig is struggling to handle things when two interfaces are present
and sending out DHCP requests, even if one interface doesn't get a
response.
Here's what I've done:
I'm continuing to bisect the mainline linux kernel, and also trying to
see if I can create a straightforward reproducible example.
First focus on bisecting was between 4.5 and 4.6, to figure out what
changed to suddenly have ipconfig working. I've tracked it down to this
using bisect, and
I've tried every version in the v4 series, and a few in v3. None prior
to (and including) v4.0.0 will boot, none output anything on the screen
to give me a clue why they're not booting.
So far:
v4.0 = won't boot
v4.1 = ipconfig bug
v4.2 = ipconfig bug
v4.3 = ipconfig bug
v4.4 = ipconfig bug
The more I look at this, the more I'm convinced *most* of the real
problem lies in that ipconfig tool. Yes, various kernel changes seem to
make it alter between working & not working under the circumstances
(which is bizarre), but unless something is specifically interfering
with the
My apologies for any lack of clarity.
I tested against the head of ubuntu-xenial, reverting just that commit
and it fixed it.
I tested against the head of the mainstream kernel and it didn't (last
night I tried 4.9, 4.8, 4.5, 4.4, 4.2 tags of the mainstream kernel and
in every place I find the
I tried reverting that specific commit from upstream, but that didn't
resolve the issue. Time for a new round of bisecting the kernel, this
time using mainline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems to make no sense to me, as a layman anyway.
I checked out the 4.4.0-58.79 tag, reverted that one commit and
confirmed I have a booting 4.4.0-58-generic that'll happily DHCP in the
initrd environment on multiple boots. It really does seem like,
somehow, that commit is the source of the
I bisected again, and again it came back to that mount point change.
This seems so bizarre.
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good: [db5f146d309e70067dae57798c9ea679af835aa7] UBUNTU: Ubuntu-4.4.0-53.74
git bisect start
I see where I messed up.. I'll try the bisect again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
initrd dhcp fails / ignores valid response
To manage notifications about this bug
Okay... I can't help but think I made a mistake somewhere in the
bisecting process, but it seems to have isolated
fd4b5fa6e3487d15ede746f92601af008b2abbc0 as the bad commit
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good:
I'll take a fresh look in the morning, but ran into this:
make[1]: Leaving directory
'/home/ubuntu/storage/ubuntu-xenial/debian/build/build-generic/zfs/module'
Debug: module-check-generic
install -d
/home/ubuntu/storage/ubuntu-xenial/debian.master/abi/4.4.0-54.76/amd64
find
I can give that a shot, following the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
I should clarify, I know for certain that 4.4.0-51 is stable and
reliable (and doesn't exhibit the bug). As part of our attempt to
verify everything was correct with the installation we had a system run
from Wednesday before Thanksgiving, all the way through to the following
Monday, during which
Okay.. this is interesting. It seems like the Ubuntu dev version of
4.10 is actually intermittently failing (?!) I guess the next thing to
do here is keep rebooting on this version of the kernel and see how
often the bug occurs vs doesn't occur, so I can get a feel for a
reasonable number of
Gah.. okay https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
initrd dhcp fails / ignores valid response
To manage notifications about
Rolling that command against master fails too:
ubuntu@Beta:~/linux$ mainline-build-one
afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc xenial
*** BUILDING: commit:afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc series:xenial
abinum: ...
full_version<4.4.0>
version<4.4.0>
long
abinum<040400>
fatal: 'xenial'
Ahh, I see where the kteam tools stuff is supposed to come from.
It's not clear if I'm supposed to go down that route and use the
mainline-build-one script or not when trying to build the kernel in this
case. If I use the mainline-build-one tool:
$ mainline-build-one
I'll get started on it. This might take a while to do.
A couple of quick observations:
1) we haven't validated that mainline 4.4.0 actually works. I only know
certain Ubuntu versions of the 4.4.0 kernel work. Given how much seems
to be changing between Ubuntu releases of it, that seems a risky
Tried and tested (the current up-to-date kernels at the time of
posting):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
headers-4.10.0-041000rc1-generic_4.10.0-041000rc1.201612252031_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
I've also confirmed the bug is present all the way back in
4.4.0-21-generic, and is present in 4.8.0-34-generic from yakkety-
proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
I've worked my way back through the kernels. The bug, as it was
(avoided by ip=dhcp in the kernel command line), was in effect in
version 4.4.0-38-generic. It was fixed in 4.4.0-42-generic. This is
the state of play so far with kernels I've tested:
linux-image-4.4.0-38-generic - Affected
apport-collect doesn't exist in initrd. I'm unable to supply the
requested information.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "pcap from dhcp server side of inird startup doing dhcp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795820/+files/failed.pcap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The checksum invalid mentioned in the pcap is interesting, but happens
in both failed and successful, so I'm not sure it's relevant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652348
Title:
** Attachment added: "pcap from dhcp server side of 'ipconfig -t "dhcp" -d
"ens2f0" '"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795819/+files/worked.pcap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Working 4.4.0-53 initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795794/+files/initrd.img-4.4.0-53-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "4.4.0-57 "broken" initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795793/+files/initrd.img-4.4.0-57-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
(re?)introduced that is breaking dhcp booting in the initrd environment.
This is stopping instances that use iscsi storage from being able to
connect.
Over serial console it outputs:
IP-Config: no response after 2
Still seems to be affecting 16.04. It's really quite annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312243
Title:
error messages completing args inside $()
To manage notifications about
We can tackle the other aspects of this on other tickets, but it does
seem like we have a good understanding of what is happening here. I want
to make sure we don't end up derailing slightly here from the "bug" as
it were (though it's not so much a bug, it appears)
Just operating from the
Kernel command line:
$ cat /proc/cmdline
BOOT_IMAGE=(http)/kernel initrd=initrd root=/dev/sda3 ro
netroot=iscsi:@169.254.0.2::3260::iqn.2015-02.oracle.boot:uefi crashkernel=auto
ip=dhcp iscsi_initiator=iqn.2015-10.oracle:2.1g1538-gb000393 LANG=en_US.UTF-8
console=ttyS0,9600 console=tty0
The
Trying another time. Again, clean instance. This time using a very
minimal cloud.cfg:
$ cat /etc/cloud/cloud.cfg
users:
- default
datasource_list: ['OpenStack']
datasource:
OpenStack:
metadata_urls: ['http://169.254.169.254']
timeout: 10
max_wait: 20
cloud_init_modules:
Clean instance, ran apt upgrade, and apt install cloud-init. I didn't
replace the cloud.cfg file with one of our format as I tried to keep
changes as minimal as possible, and the supplied one seems to work
sufficiently.
$ echo "network: {config: disabled}" | sudo tee
Public bug reported:
Package: cloud-init 0.7.8-1-g3705bb5-0ubuntu1~16.04.3
The file /etc/network/interfaces.d/50-cloud-init.cfg states that:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's
I ran into this with iSCSI root. Installing cloud-init resulted in
problems rebooting.
If I install the ifupdown patch (without cloud-init installed), that
triggers the bug for me.
Spinning up a clean instance, installing cloud-init, letting it run (so
the conditions that cause the bug are
Public bug reported:
When running virt-customize against an existing raw image, it seems to
hang and do nothing. With verbose flag passed the logs are filled with:
/sbin/dhclient-script: 31: /sbin/dhclient-script: cannot open /etc/fstab: No
such file
RTNETLINK answers: File exists
There isn't a kernel in proposed at the moment, but I've tested using
the latest in yakkety and it seems to be working fine.
I don't have a simple replication case for the bug, unfortunately. It
just seems to happen for (hand-wavey guess) 50% of boots.
So far I've got this 4.8.0-19-generic
Public bug reported:
On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger
off a kernel panic against somepart of the NVMe driver it looks like,
after which the logs get filled with entries over and over again of:
"bad: scheduling from the idle thread!"
Here's the initial stack
gzip'd copy of the kern.log showing the error.
** Attachment added: "kern.log.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626679/+attachment/4746377/+files/kern.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On installing the server version of 16.04 you get asked to provide
language and then a region for localisation. The text in the installer
indicates that this will be used to help determine which timezone you
want to use for the machine. If you put in English (US) and select
I'm using the MATE PPA http://ppa.launchpad.net/ubuntu-mate-
dev/ppa/ubuntu/ with Ubuntu 12.04.5, and get the same issue, so I'm not
sure it's related to specific versions of Ubuntu. If there are any
suitable packages for me to report on versions for, Id be happy to do
so.
--
You received this
This one affects me as well. Muting mutes the master, and headphone and
PCM. Unmuting only unmutes Master.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/496354
Title:
amixer doesn't seem to
Can't say for sure if it's a problem any more or not. I've long since
given up on Unity, in no small part due to this bug. The response on
the bug report did little to convince me it was worth continuing to use
it either. A whole bunch of people experiencing it, and the bug just
constantly
From the Debian POV, this is working as designed.
If that's the case, why did Debian consider it a bug and fix it
upstream? You've got me very confused.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That worked for my peculiar case too. Mahalo!
As Pablo commented, still seems to fail on mediafire.com but I'm not
certain mediafire's end point is working correctly as it fails in both
openssl (1.0.1-4ubuntu3) AND gnutls (3.0.11+really2.12.14-5ubuntu3) :
$ openssl s_client -connect
Affected me last night, spawned off a tightvncserver instance, connected
and got no launcher or icons.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901211
Title:
compiz crashed with SIGSEGV in
I was finally able to re-create this consistently.
Clean install from Beta 1, press alt+f2, type in gnome-terminal, and hit enter
(don't click the icon).
That resulted in a gnome-terminal screen loading but with an unfilled triangle.
It seems that some update since I originally reported the bug
I should add, the other problems still exist, as documented in screen
captures and photographs. However given you've been ignoring those so
far in the ticket, I suppose it's unlikely we'll see any kind of
dialogue about them.
--
You received this bug notification because you are a member of
I've been butting up against this one on and off in the Beta. Seems to
me in no small part to be down to how fast the graphic acceleration is.
e.g. I hit this more on my computer at work as it's got a slow old
Nvidia card in it, vs my home machine with a much higher spec card in
it.
If you've
Get this on choosing advanced partition tool during the installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/912031
Title:
ubiquity crashed with TypeError in partman_column_name(): argument of
You've actually hit on the right problem there Tim. It looks like Unity
is getting confused about where a window is.
See the next attached two screenshots. In them you can see Gnome
Terminal running behind Ubuntu Software Center, but according to the
icon in the dock bar Unity thinks Gnome
** Attachment added: IMG_20120315_074710.jpg
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/951929/+attachment/2876839/+files/IMG_20120315_074710.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe this problem is part of an even wider scope.
Unity seems to be having big problems with remembering which workspace
an application is associated.
This is manifesting itself in one of three specific ways:
1) Applications not appearing in alt-tab. (usually combined with a
hollow
Got this under 12.04 as well. Pidgin 1:2.10.1-1ubuntu2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/727589
Title:
pidgin crashed with SIGSEGV in g_type_check_instance_cast()
To manage
That's interesting, I'm certainly not moving it
(ctrl+alt+shift+direction isn't a combination you just stumble across),
but also that doesn't explain what's going on in note #6 with screenshot
where Chrome is clearly on the same workspace (you can see it right
behind the active terminal pane) but
Installing manually works (for me)(, but not from Additional Hardware
Wizard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/804662
Title:
jockey-gtk crashed with TypeError in _execute_child():
Actually, I need to broaden the scope of this. Looks like it's
affecting all sorts of apps at various stages. E.g. currently I have
Chrome and Gnome-Terminal open. Alt+tab shows Terminal and Desktop, but
not Chrome.
--
You received this bug notification because you are a member of Ubuntu
I'm not 100% convinced, but now wondering if it's just happening to the
first app started on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951929
Title:
alt+tab doesn't show gnome-terminal
No. I hadn't moved the window, and I did double check on each workspace
just in case. I'm a little surprised that the workspace switcher icon
is non-dynamic. Almost every GUI indicates in some way that windows are
open on other workspaces, even minimalist GUIs do it.
I'm unable to re-create it
I've attached a hopefully a good example of the behaviour, this time
affecting Chrome.
In the foreground is Gnome Terminal, with transparency enabled (and a
dmesg output just to have text appearing). Behind it you can see Google
Chrome on the Google home page. In the alt+tab box you can see
I'm seeing this in Precise still:
dpkg output to show packages are installed:
$ sudo dpkg -l | grep fgl
ii fglrx-amdcccle-updates 2:8.911-0ubuntu1
Catalyst Control Center for the AMD graphics accelerators
ii fglrx-updates
** Summary changed:
- alt+tab doesn't show gnome-terminal
+ alt+tab doesn't show all apps
** Description changed:
+ edit: Updated title, its affecting more than gnome-terminal
+
1) Description: Ubuntu precise (development branch)
Release: 12.04
2) unity:
- Installed:
This seems to be happening quite frequently, but I can't figure out an
exact sequence that results in it happening. Applications are not
always registering as running according to dock, but are clearly loaded
and visible on the screen, and not alt-tabbable.
Also noticing, in cases where the
Public bug reported:
1) Description: Ubuntu precise (development branch)
Release:12.04
2) unity:
Installed: 5.4.0-0ubuntu2
3) Gnome-Terminal to show in list of programs to alt+tab to.
4) Alt+Tab consistently fails to show gnome-terminal for 'a while' (I
hate to be vague, I can't
** Attachment added: photo of screen
https://bugs.launchpad.net/bugs/951929/+attachment/2848135/+files/IMG_20120310_145309.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951929
Title:
This is no longer relevant. I'm not sure at which version the reference
was removed, but it's certainly not been part of the last two revisions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/428853
78 matches
Mail list logo
