Current xenial linux-image-4.4.0-62-generic remains broken, with dmesg
WARNs on CRTC clocks and then system hangs when switching user sessions
(which invokes some gnome-session xrandr setup). Lost the exact dmesg on
the system hang.
Current mainline 4.8.x (4.8.17-040817-generic) continues to
I've had good enough experiences with mainline 4.8.15 at this point that
I would consider this bug fixed in linux 4.8.x; it's still not perfect
(have to typically play around with xrandr and maybe undock/dock), but
external 4k DP monitor via a ThinkPad dock works fairly reliably now.
OTOH I was
I've been running the 4.8.x mainline release kernels recently, and had
some success with 4k DP connected to the dock. It doesn't always work,
but a reboot fixes it, until it breaks again.
I'd appreciate advice for debugging this, it's pretty reproducible, but
typically when it happens I don't
I've been having more luck with the newer 4.7 and 4.8 kernels, and using
a 4k monitor on the integrated DP connector mostly works okay at 60Hz.
Haven't really noticed any difference in stability with the
xorg.conf.d/20-intel.conf settings in https://github.com/linuxenko
You can try the mainline 4.8-rc builds here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567417
Title:
WARN_ON(!wm_changed)
Workaround is to use go build:
GOPATH=~/go GOOS=linux GOARCH=arm GOARM=5 go build -o
bin/linux_arm/foo -v .
But this recompiles the entire stdlib each time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On Ubuntu trusty, I used to cross-compile Golang programs for ARM
devices, IIRC by installing the golang-go-linux-arm package. However,
these packages no longer exist in xenial, even though it is referred to
in the /usr/share/doc/golang-1.6-go/README.Debian file:
If you
I found a couple existing bugs in the freedesktop.org tracker that might
be related, all marked as fixed in recent nightlies:
https://bugs.freedesktop.org/show_bug.cgi?id=96714
https://bugs.freedesktop.org/show_bug.cgi?id=95498
https://bugs.freedesktop.org/show_bug.cgi?id=94822
I can confirm that linux-image 4.7.0-994-generic_4.7.0-994.201607052202
from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/2016-07-06/ behaves much better.
DP hotplug/unplug behaves correctly across text console, VT switch to
lightdm and login into Unity. There's still some
And no upgrades or prior working versions, this is a fresh Ubuntu 16.04
install on a newly purchased X260 laptop.
** Description changed:
Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD
Graphics 520, connecting an external monitor to the DisplayPort
connector causes
As per the description, I have tested this with 4.4.0-28-generic as well
as mainline 4.6.3-040603-generic and 4.7.0-040700rc5-generic; they all
hang in a similar fashion.
In fact, the journal output I attached was from the 4.7 kernel, I
renamed the attachment accordingly:
Note that compared to #1559308 , connecting the same monitor via the
HDMI port on the laptop running 4.4.0-28-generic does seem to work fine:
There's still some stuff in dmesg when using HDMI as well:
snd_hda_codec_hdmi hdaudioC0D2: HDMI: ELD buf size is 0, force 128
snd_hda_codec_hdmi
Public bug reported:
Running Ubuntu 16.04 on a Lenovo ThinkPad X260 with Intel Skylake HD
Graphics 520, connecting an external monitor to the DisplayPort
connector causes the system to quickly hang. The system stops responding
to network pings, cannot switch consoles, and needs a hard reboot.
Public bug reported:
Hi,
Running Ubuntu xenial with current 4.4.0-22-generic kernel and lxd
2.0.2-0ubuntu1~16.04.1, running Ubuntu's patched docker.io package
within an unprivileged container (`lxc launch -p default -p docker
ubuntu:xenial docker-test`) works, but fails once configuring the
Public bug reported:
On Ubuntu xenial,
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy systemd
systemd:
Installed: 229-4ubuntu4
Candidate: 229-4ubuntu4
Version table:
***
Public bug reported:
After installing xenial using the daily ubuntu-server installer,
creating an LVM volume for the root filesystem, I lvconverted it into a
raid1 mirror for redundancy over the pair of SSDs installed (as separate
LVM PVs):
sudo lvconvert -m 1 --type raid1 bonk/bonk1
Crude, crude workaround on trusty:
aptitude markauto '?name(linux-image-.*-generic)'
This lets 'apt-get autoremove' clean out old kernels installed via
update-manager, while /etc/apt/apt.conf.d/01autoremove-kernels ensures
that some kernels are retained.
--
You received this bug
Public bug reported:
Running Puppet on Ubuntu 15.04 Vivid:
$ lsb_release -d
Description:Ubuntu 15.04
$ apt-cache policy puppet-common
puppet-common:
Installed: 3.7.2-1ubuntu2
Using the bird package as an example:
$ dpkg -L bird |
** Summary changed:
- puppet service enable broken on ubuntu vivid for services shipping sysvinit
and systemd support
+ puppet service enable broken on ubuntu vivid with debian provider
** Description changed:
Running Puppet on Ubuntu 15.04 Vivid:
- $ lsb_release -d
-
Note that the same scenario behaves correctly under Debian jessie, with
the patched debian service provider in version 3.7.2-3:
https://bugs.debian.org/775795
Similar example on a Debian jessie system:
$ sudo lsb_release -d
Description:Debian GNU/Linux 8.2 (jessie)
Note that the same scenario behaves correctly under Debian jessie, with
the patched debian service provider in version 3.7.2-3:
https://bugs.debian.org/775795
Similar example on a Debian jessie system:
$ sudo lsb_release -d
Description:Debian GNU/Linux 8.2 (jessie)
Public bug reported:
Running Puppet on Ubuntu 15.04 Vivid:
$ lsb_release -d
Description:Ubuntu 15.04
$ apt-cache policy puppet-common
puppet-common:
Installed: 3.7.2-1ubuntu2
Using the bird package as an example:
$ dpkg -L bird |
** Summary changed:
- puppet service enable broken on ubuntu vivid for services shipping sysvinit
and systemd support
+ puppet service enable broken on ubuntu vivid with debian provider
** Description changed:
Running Puppet on Ubuntu 15.04 Vivid:
- $ lsb_release -d
-
Yes, I can confirm that the trusty-proposed 3.13.0-38 kernel resolves
this issue. The dnsmasq-tftp transfer succeeds in my test environment
without any of the symptoms that were present with the trusty-
updates/security kernels between -30 and -37, nor do I notice any
regressions in my (IPv4) ipvs
ACK
3.13.0-35-generic #62~lp1349768v5v201408250842 appears to resolve the
issue completely on my actual test setup as well. No TFTP stalls,
dnsmasq EPERM errors or dmesg errors, and ftrace doesn't show any calls
to ipv6_find_hdr.
--
You received this bug notification because you are a member of
NAK
Unfortunately no, the 3.13.0-35-generic #62~lp1349768v4v201408220857
from above continues to exhibit the same issues with my actual test
setup. Same thing with the ./lp1349768.sh testcase.
The 0041-ipvs-fix-ipv4-issues-in-ip_vs_out.patch in the lp1349768v4
build is a different patch, though?
NAK
Linux 3.13.0-35-generic #62~lp1349768v3v201408191448 still exhibits the
same symptoms (stalled dnsmasq-tftp transfer and IPv6 header not found
messages). Unloading the ip_vs module clears the issue.
I'll attempt to work out a minimal reproducer.
--
You received this bug notification
Attached is a small script to setup dnsmasq-tftp and ipvs to reproduce
the dnsmasq-tftp stall. The strace at the end should start showing
sendto() = EPERM errors after running the curl tftp://.../ command given
as an example from a remote host.
The exact contents of the ipvs rules don't seem to
ACK
I can confirm that this issue is no longer present with the Linux
3.13.0-33-generic #58~lp1349768v2v201407300928 kernel as installed from
above. Rebooting into the given kernel results in dnsmasq-tftp transfers
working fine, and no related dmesg errors occur.
Apologies for the delay. I was
The utopic kernel appears to be affected as well. Booting the same
Ubuntu 14.04 machine into the Linux 3.16.0-6-generic #11-Ubuntu kernel
installed from
https://launchpad.net/ubuntu/+source/linux/3.16.0-6.11/+build/6217368
gives identical symptoms, i.e. dnsmasq-tftp stalls, dmesg reports IPv6
NACK
The same faulty behaviour persists with linux-
image-3.13.0-33-generic=3.13.0-33.58~lp1349768v201407290941 (uname
3.13.0-33-generic #58~lp1349768v201407290941).
I do not notice any difference; identical symptoms. `rmmod ip_vs_rr
ip_vs` continues to immediately resolve the fault.
Note that
Apologies, misfiled initially on biosdevname, I meant to file on the
linux-image package source.
** Description changed:
I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
loadbalancer and dnsmasq server for pxebooting servers.
- After updating linux-image 3.13.0-30.55
Public bug reported:
I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
loadbalancer and dnsmasq server for pxebooting servers.
After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
dnsmasq-tftp stopped working. pxeboot clients would hang on the Loading
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165028/+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/1349768
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165025/+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/1349768
apport information
** Tags added: apport-collected trusty
** Description changed:
I have an Ubuntu 14.04 host that I am using as both a keepalived/ipvs
loadbalancer and dnsmasq server for pxebooting servers.
After updating linux-image 3.13.0-29.53 - 3.13.0-32.57 I noticed that
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165033/+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/1349768
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165030/+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/1349768
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165026/+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/1349768
Reported apport-collect information against package linux-
image-3.13.0-32-generic, reproducing the dnsmasq-tftp issue with a
remote client pxebooting and stalling.
The CurrentDmesg contains the symptom message at 1214.740931
--
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165032/+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/1349768
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165035/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165031/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165029/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165027/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1349768/+attachment/4165034/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349768
Title:
A type=VIR_STORAGE_TYPE_VOLUME disk is not necessarily a
virStoragePoolDefPtr.type=VIR_STORAGE_POOL_LOGICAL, and may or may not
involve a /dev/... path; the logic for translating them into src paths
seems to be somewhere like qemuTranslateDiskSourcePool() via
virStorageVolGetPath(), and seems to
Public bug reported:
Release:14.04
Package:libvirt-bin
Version: 1.2.2-0ubuntu13.1.1
For a normal block-based LVM disk definition
disk type='block' device='disk'
driver name='qemu' type='raw'/
source dev='/dev/host-vg/guest.img'/
target dev='vda'
Public bug reported:
Release:14.04
Package:libvirt-bin
Version: 1.2.2-0ubuntu13.1.1
For a normal block-based LVM disk definition
disk type='block' device='disk'
driver name='qemu' type='raw'/
source dev='/dev/host-vg/guest.img'/
target dev='vda'
Any chance of getting this fix into trusty?
Fixing this up by hand via /etc/apparmor.d/libvirt/TEMPLATE is possible
for pre-existing domain profiles, but involves shutting down the domain
etc. Is there any better way?
virsh shutdown foobar
sudo /usr/lib/libvirt/virt-aa-helper --delete --uuid
Note that in Ubuntu 12.04 (where Lubuntu LTSP works) the lubuntu-
default-settings 0.27 package ships a different
/usr/share/xsessions/Lubuntu.desktop :
Exec=/usr/bin/startlubuntu
The /etc/X11/Xsession.d/... files seem to be the same.
--
You received this bug notification because you are a
Public bug reported:
DistroRelease: Ubuntu 14.04
Package: ltsp-server 5.5.1-1ubuntu2
The following code in `/etc/X11/Xsession.d/40-ltsp-server` causes issues with
dash `export ...` expansion as regards LP#139097 :
DESKTOP_SESSION=$(echo $1 | sed s/gnome-session --session=//g)
Given the
Do you have the updated linux-firmware 1.79.10 installed? Confirm with
`dpkg -L linux-firmware | grep iwlwifi-7260-7.ucode`?
$ dpkg -l linux-firmware
||/ Name VersionDescription
+++-==-==-
ii linux-firmware
Public bug reported:
The latest precise-updates linux-image seems to omit the required
iwlwifi-7260-7.ucode firwmware
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)
$ dpkg -l linux-image-3.11*
ii linux-image-3.11.0-14-generic 3.11.0-14.21~precise1
*** This bug is a duplicate of bug 1281964 ***
https://bugs.launchpad.net/bugs/1281964
Workaroud: Boot with Shift held down, and select older 3.11.0-15 linux
version in grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1281964 ***
https://bugs.launchpad.net/bugs/1281964
Confirm that updating to linux-firmware 1.79.10 from precise-updates
resolves this, giving me a functional phy0 on 3.11.0-17-generic.
$ apt-cache policy linux-firmware
linux-firmware:
Installed: 1.79.10
I can confirm this happening with F-Spot 0.3.5-0ubuntu2 on Ubuntu 7.04
with libexif12 0.6.13-5ubuntu0.2 and libmono0 1.2.3.1-1ubuntu1. F-Spot
crashes to the desktop when exporting a vertically taken photo (as
opposed to horizontal) to a Folder (web gallery or files only) with the
Autorotate option
I have researched this further, and it turns out that the bug is in libexif -
the exiftran utility uses 1.7g of mem and segfaults when trying to process
these photos (taken with an Olympus E-510 camera), and The GIMP cannot open
them:
58 matches
Mail list logo
