[Bug 1849713] WifiSyslog.txt

[Alexander List]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538695/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] ProcModules.txt

[Alexander List]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538693/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] ProcInterrupts.txt

[Alexander List]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538692/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic

[Alexander List]

Problem still visible with linux-image-4.15.0-161-generic on Intel
NUC5i5MYBE

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] ProcEnviron.txt

[Alexander List]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538691/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] ProcCpuinfoMinimal.txt

[Alexander List]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538690/+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/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] UdevDb.txt

[Alexander List]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1849713/+attachment/5538694/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] ProcCpuinfo.txt

[Alexander List]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538689/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] Lsusb.txt

[Alexander List]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1849713/+attachment/5538688/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] CurrentDmesg.txt

[Alexander List]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538686/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] Lspci.txt

[Alexander List]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1849713/+attachment/5538687/+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/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] CRDA.txt

[Alexander List]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1849713/+attachment/5538685/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] Re: Warning message in logs after kernel update to linux-image-4.15.0-66-generic

[Alexander List]

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bob1302 F pulseaudio
 /dev/snd/controlC1:  bob1302 F pulseaudio
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=8cc37bc2-8e6b-42a0-8d35-815fac62d66b
InstallationDate: Installed on 2015-12-13 (2156 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lono wireless extensions.
 
 enp0s25   no wireless extensions.
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-161-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-161.169-generic 4.15.18
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-161-generic N/A
 linux-backports-modules-4.15.0-161-generic  N/A
 linux-firmware  1.173.20
RfKill:
 
Tags:  bionic
Uname: Linux 4.15.0-161-generic x86_64
UpgradeStatus: Upgraded to bionic on 2020-10-07 (396 days ago)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 11/24/2016
dmi.bios.vendor: Intel Corporation
dmi.bios.version: MYBDWi5v.86A.0033.2016.1124.2006
dmi.board.name: NUC5i5MYBE
dmi.board.vendor: Intel Corporation
dmi.board.version: H47797-202
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorporation:bvrMYBDWi5v.86A.0033.2016.1124.2006:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5MYBE:rvrH47797-202:cvn:ct3:cvr:


** Tags added: apport-collected

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849713] AlsaInfo.txt

[Alexander List]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1849713/+attachment/5538684/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849713

Title:
  Warning message in logs after kernel update to linux-
  image-4.15.0-66-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849713/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

[Alexander List]

I can confirm this problem on Ubuntu 21.04 (hirsute) running on a Dell
XPS 13 7390 2-in-1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927255

Title:
  [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928073] Re: Display settings don't persist across reboot / sleep

[Alexander List]

I stand corrected: fractional scaling on/off persists. The scale (100%)
does not, it jumps back to 200% and my Chrome windows that were on the
external screens are back on the internal display.

The latter was already reported as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948

I am using Wayland yes, which I guess is default in 21.04.


Sorry for this off-topic comment, but I'm a bit frustrated:

What I'm also missing is instructions how to get things working nicely
in 21.04 with Wayland, this still looks like a massive WIP /
construction site. Don't get me wrong, ppl with external monitors and
HiDPI internal screen are probably a minority, so I appreciate not
everything can be fully tested by devs/QA before release.

I've tried to follow instructions here:

https://wiki.archlinux.org/title/HiDPI#Multiple_external_monitors

...but only some of them help. I would appreciate Ubuntu documentation
on how to get Chrome, Thunderbird, Skype, Signal Desktop, Telegram, ...
working nicely with this setup.

I will take some time to dig deeper and report appropriate bugs against
respective packages, if appropriate.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928073

Title:
  Display settings don't persist across reboot / sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1928073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1928073] [NEW] Display settings don't persist across reboot / sleep

[Alexander List]

Public bug reported:

My setup:

Dell XPS 13 7390 2-in-1, internal display (3840x2400)

First external monitor: Dell 24" running at 2560x1440 connected via 
USB-C/Thunderbolt
Second external monitor: same, connected to the first monitor via DP

Scale of the internal display set to 200%, fractional scaling on
Scale of the external displays set to 100%, fractional scaling on


What I expect:

Settings persist across reboot / sleep / resume.

What I observe:

Settings for external monitors are back to 200% scale, fractional
scaling off.

Looks like there's a problem detecting the external monitors/resolutions
in time.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 11 12:12:28 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-12-02 (525 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-05-05 (5 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928073

Title:
  Display settings don't persist across reboot / sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928073/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927948] Re: Windows switch monitor after resuming from sleep

[Alexander List]

I have a Dell XPS 13 7390 2-in-1 with two external monitors.

The first external monitor is connected via USB-C/Thunderbolt, the
second one via DP from the first external monitor.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927948

Title:
  Windows switch monitor after resuming from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927948] [NEW] Windows switch monitor after resuming from sleep

[Alexander List]

Public bug reported:

What I expect:

Window layout/positioning is identical after resume from sleep.

What I observe:

After resume from sleep, windows appear on a different monitor than
before.

I found this possibly relevant GNOME bug:

https://gitlab.gnome.org/GNOME/mutter/-/issues/1419

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: mutter 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May 10 13:40:28 2021
InstallationDate: Installed on 2019-12-02 (524 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: mutter
UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago)

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927948

Title:
  Windows switch monitor after resuming from sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.

[Alexander List]

I notice similar behaviour on 20.10, Dell XPS 13 7390 2-in-1, Logitech M590
When I open Settings->Bluetooth, which takes a sec or two, something seems to 
get triggered and the mouse starts working again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246981

Title:
  Bluetooth devices fail to re-connect after sleep.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904929] [NEW] cyrus-caldav stops working after upgrade

[Alexander List]

Public bug reported:

After an upgrade from Ubuntu 18.04 to 20.04 on Oct 22 2020, calendar
services stopped working.

I found the following error in the log:

Nov 19 19:52:06 host cyrus/https[49431]: DBERROR:
sqldb_exec(/var/lib/cyrus/user/f/foo.dav) prepare : no such column: alive

A quick inspection of foo.dav using sqlite3 revealed that there was
indeed no column "alive" in that db.

The 18.04 to 20.04 upgrade triggered the following package upgrade:

2020-10-22 19:18:51 upgrade cyrus-caldav:amd64 2.5.10-3ubuntu1.1
3.0.13-5

Inspection of the source code revealed that for some reason, the upgrade
process didn't adapt the schema of the sqlite files to the new format.

The relevant code can be found in cyrus-imapd/imap/caldav_db.c and
dav_db.c

Manually doctoring the sqlite3 files wasn't successful, but then I
discovered

/usr/lib/cyrus/bin/dav_reconstruct

as part of the cyrus-caldav package

Running

/usr/lib/cyrus/bin/dav_reconstruct foo

fixed the schema of the offending database and calendars started working
again.

Maybe I overlooked something in the release notes, or this is such a
rarely used feature that the schema update got overlooked.

I suggest to amend the release notes with a hint that the DAV databases
need to be fixed using dav_reconstruct. Alternatively, the package
postint scripts could offer to run this command against all users' DAV
databases.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cyrus-caldav 3.0.13-5
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Nov 19 21:25:20 2020
SourcePackage: cyrus-imapd
UpgradeStatus: Upgraded to focal on 2020-10-22 (28 days ago)

** Affects: cyrus-imapd
 Importance: Undecided
 Status: New

** Affects: cyrus-imapd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Also affects: cyrus-imapd
   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/1904929

Title:
  cyrus-caldav stops working after upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-imapd/+bug/1904929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1904929] Re: cyrus-caldav stops working after upgrade

[Alexander List]

https://nicolan-cyrus-
imapd.readthedocs.io/en/latest/imap/download/upgrade.html#id11

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904929

Title:
  cyrus-caldav stops working after upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-imapd/+bug/1904929/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892074] [NEW] WiFi keeps disconnecting

[Alexander List]

Public bug reported:

1) $ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

2) $ apt-cache policy linux-image-5.4.0-42-generic
linux-image-5.4.0-42-generic:
  Installed: 5.4.0-42.46
  Candidate: 5.4.0-42.46
  Version table:
 *** 5.4.0-42.46 500
500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status

3) No WiFi disconnects
4) WiFi disconnects (other clients don't have any issues)

The WiFi AP is a Mikrotik cAP AC running RouterOS v6.47.1, 2.4/5GHz
dual-band (4 channels), WPA2-PSK.

I see reglular WiFi disconnects since a few days now, possibly related
to a kernel and/or firmware upgrade.

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889182
looks similar, but I have different Intel hardware:

00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
160MHz Wireless Network Adapter (201NGW) (rev 30)

[87471.950797] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
[87471.950881] iwlwifi :00:14.3: Start IWL Error Log Dump:
[87471.950884] iwlwifi :00:14.3: Status: 0x0040, count: 6
[87471.950887] iwlwifi :00:14.3: Loaded firmware version: 48.4fa0041f.0
[87471.950889] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
[87471.950891] iwlwifi :00:14.3: 0xA200 | trm_hw_status0
[87471.950893] iwlwifi :00:14.3: 0x | trm_hw_status1
[87471.950895] iwlwifi :00:14.3: 0x004CA468 | branchlink2
[87471.950897] iwlwifi :00:14.3: 0x004B5438 | interruptlink1
[87471.950898] iwlwifi :00:14.3: 0x004B5438 | interruptlink2
[87471.950900] iwlwifi :00:14.3: 0x004C54E6 | data1
[87471.950902] iwlwifi :00:14.3: 0x1000 | data2
[87471.950903] iwlwifi :00:14.3: 0xF008 | data3
[87471.950905] iwlwifi :00:14.3: 0x8580BFB0 | beacon time
[87471.950907] iwlwifi :00:14.3: 0xF6D4B028 | tsf low
[87471.950909] iwlwifi :00:14.3: 0x0013 | tsf hi
[87471.950910] iwlwifi :00:14.3: 0x | time gp1
[87471.950912] iwlwifi :00:14.3: 0x03470D2D | time gp2
[87471.950914] iwlwifi :00:14.3: 0x0001 | uCode revision type
[87471.950915] iwlwifi :00:14.3: 0x0030 | uCode version major
[87471.950917] iwlwifi :00:14.3: 0x4FA0041F | uCode version minor
[87471.950919] iwlwifi :00:14.3: 0x0332 | hw version
[87471.950921] iwlwifi :00:14.3: 0x00C89008 | board version
[87471.950922] iwlwifi :00:14.3: 0x8028FD19 | hcmd
[87471.950924] iwlwifi :00:14.3: 0x2402 | isr0
[87471.950926] iwlwifi :00:14.3: 0x | isr1
[87471.950927] iwlwifi :00:14.3: 0x18F84802 | isr2
[87471.950929] iwlwifi :00:14.3: 0x00C1FFCC | isr3
[87471.950931] iwlwifi :00:14.3: 0x | isr4
[87471.950932] iwlwifi :00:14.3: 0x009D01D1 | last cmd Id
[87471.950934] iwlwifi :00:14.3: 0x004C54E6 | wait_event
[87471.950936] iwlwifi :00:14.3: 0x00D4 | l2p_control
[87471.950938] iwlwifi :00:14.3: 0x00018014 | l2p_duration
[87471.950939] iwlwifi :00:14.3: 0x0007 | l2p_mhvalid
[87471.950941] iwlwifi :00:14.3: 0x | l2p_addr_match
[87471.950943] iwlwifi :00:14.3: 0x0008 | lmpm_pmg_sel
[87471.950944] iwlwifi :00:14.3: 0x | timestamp
[87471.950946] iwlwifi :00:14.3: 0x988C | flow_handler
[87471.950984] iwlwifi :00:14.3: Start IWL Error Log Dump:
[87471.950986] iwlwifi :00:14.3: Status: 0x0040, count: 7
[87471.950988] iwlwifi :00:14.3: 0x200014FD | ADVANCED_SYSASSERT
[87471.950989] iwlwifi :00:14.3: 0x | umac branchlink1
[87471.950991] iwlwifi :00:14.3: 0xC008D49C | umac branchlink2
[87471.950993] iwlwifi :00:14.3: 0xC00871A4 | umac interruptlink1
[87471.950995] iwlwifi :00:14.3: 0x | umac interruptlink2
[87471.950996] iwlwifi :00:14.3: 0x0082 | umac data1
[87471.950998] iwlwifi :00:14.3: 0xDEADBEEF | umac data2
[87471.951000] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
[87471.951001] iwlwifi :00:14.3: 0x0030 | umac major
[87471.951003] iwlwifi :00:14.3: 0x4FA0041F | umac minor
[87471.951005] iwlwifi :00:14.3: 0x03470D20 | frame pointer
[87471.951006] iwlwifi :00:14.3: 0xC0885EA0 | stack pointer
[87471.951008] iwlwifi :00:14.3: 0x00AA0108 | last host cmd
[87471.951010] iwlwifi :00:14.3: 0x | isr status reg
[87471.951025] iwlwifi :00:14.3: Fseq Registers:
[87471.951044] iwlwifi :00:14.3: 0xE101 | FSEQ_ERROR_CODE
[87471.951049] iwlwifi :00:14.3: 0x00290033 | FSEQ_TOP_INIT_VERSION
[87471.951068] iwlwifi :00:14.3: 0x80070043 | FSEQ_CNVIO_INIT_VERSION
[87471.951090] iwlwifi :00:14.3: 0xA481 | FSEQ_OTP_VERSION
[87471.951110] iwlwifi :00:14.3: 0x0002 | FSEQ_TOP_CONTENT_VERSION
[87471.951131] iwlwifi :00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[87471.951152] iwlwifi :00:14.3: 0x02000300 | FSEQ_CNVI_ID
[87471.951157] iwlwifi :00:14.3: 

[Bug 1872967] [NEW] Xorg crash

[Alexander List]

Public bug reported:

Screen freezes when using LibreOffice writer, then crashes.

After around a minute, the X session restarts and presents me with the
login prompt.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 13:56:21 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:08b0]
InstallationDate: Installed on 2019-12-02 (134 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. XPS 13 7390 2-in-1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_psr=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd08/02/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug crash eoan ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872967

Title:
  Xorg crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872967/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1303698] Re: curiosity killed the trusty tahr

[Alexander List]

*** This bug is a duplicate of bug 1538615 ***
https://bugs.launchpad.net/bugs/1538615

Even though this is a duplicate, I just found this piece of evidence
that's worth preserving.

The cat feeling well on a Thinkpad X201 is due to heat from the CPU :)

** Attachment added: "Culprit triggering the bug"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303698/+attachment/5274867/+files/20140307_200415.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303698

Title:
  curiosity killed the trusty tahr

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1303698/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1726879] Re: Unescaped left brace in regex is deprecated

[Alexander List]

+1 for a SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726879

Title:
  Unescaped left brace in regex is deprecated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1726879/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Alexander List]

Using a clean 17.04 install, I could observe the same problem.

Against convention, our company is using .local as the internal DNS TLD.

As mentioned in #8 and #13 above, /etc/resolv.conf was symlinked to

root@dell-e5470:~# ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Apr  5 09:19 /etc/resolv.conf -> 
../run/resolvconf/resolv.conf

which contains

---
# cat /run/resolvconf/resolv.conf 
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
---

After removing the symlink /etc/resolv.conf and linking like this:

# ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

...thinks started working again. Now the file contains the DNS received
via DHCP:

-
# cat /etc/resolv.conf 
# This file is managed by systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known DNS servers.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 1.2.3.4
search local.example.com example.local
-

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624320

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1169437] Re: network-manager does not configure local resolver or dnsmasq to use the nameserver addresses received from the VPN server

[Alexander List]

I just observed this on a laptop using network-manager-vpnc-gnome.

The DNS is correctly received via vpnc and added to NetworkManager, but
not being handled by dnsmasq.

nmcli -f IPv4 c show 820e9fe8-8ae6-4f69-ba85-402936c38852 |grep -i dns
ipv4.dns:   AA.BB.CC.DD
ipv4.dns-search:
ipv4.dns-options:   (default)
ipv4.ignore-auto-dns:   yes

Disabling dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf seems
to be a valid workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169437

Title:
  network-manager does not configure local resolver or dnsmasq to use
  the nameserver addresses received from the VPN server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1576028] [NEW] wget segfaults when downloading filename with Russian characters

[Alexander List]

Public bug reported:

I tried to download an attachment from Launchpad.

wget didn't like it and segfaulted...

$ wget 
"https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/4649672/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-04-28%2008-21-35.png;
--2016-04-28 12:53:28--  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/4649672/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-04-28%2008-21-35.png
Resolving bugs.launchpad.net (bugs.launchpad.net)... 91.189.89.225, 
91.189.89.224
Connecting to bugs.launchpad.net (bugs.launchpad.net)|91.189.89.225|:443... 
connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: 
https://launchpadlibrarian.net/256821437/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-04-28%2008-21-35.png
 [following]
--2016-04-28 12:53:29--  
https://launchpadlibrarian.net/256821437/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-04-28%2008-21-35.png
Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 91.189.89.229, 
91.189.89.228
Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|91.189.89.229|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 240409 (235K) [image/png]
Saving to: ‘Снимок \321%8Dк\321%80ана о\321%82 2016-04-28 08-21-35.png.2’

Segmentation fault (core dumped)

The file is an attachment to this comment:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/comments/19

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wget 1.17.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 12:54:28 2016
InstallationDate: Installed on 2015-07-04 (298 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: wget
UpgradeStatus: Upgraded to xenial on 2016-04-26 (2 days ago)

** Affects: wget (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576028

Title:
  wget segfaults when downloading filename with Russian characters

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1576028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()

[Alexander List]

Unfortunately, I still get errors on Xenial:

Apr 26 12:50:35 xx whoopsie[1203]: [12:50:35] Parsing 
/var/crash/_usr_lib_squid_pinger.0.crash.
Apr 26 12:50:35 xx whoopsie[1203]: [12:50:35] Uploading 
/var/crash/_usr_lib_squid_pinger.0.crash.
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Sent; server replied with: No 
error
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Response code: 200
Apr 26 12:50:38 xx whoopsie[1203]: [12:50:38] Reported OOPS ID 
6acdb2bc-0b6a-11e6-a507-fa163e8d4bab

pinger assert failure: *** Error in `(pinger)': free(): invalid pointer:
0x555b3c501070 ***

$ apt-cache policy squid
squid:
  Installed: 3.5.12-1ubuntu7
  Candidate: 3.5.12-1ubuntu7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214379

Title:
  pinger crashed with SIGSEGV in malloc_consolidate()

To manage notifications about this bug go to:
https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1510616] Re: Missing PCI IDs for Intel 7265D wireless hw

[Alexander List]

I still see this on an Intel NUC5i7RYH with Intel 7265 WiFi on current
Xenial:

[7.715308] iwlwifi :02:00.0: Unsupported splx structure


02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)

# uname -a
Linux hkgofdt02 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Intel Corporation
Version: RYBDWi35.86A.0354.2016.0120.0912
Release Date: 01/20/2016

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Intel Corporation
Product Name: NUC5i7RYB
Version: H73774-101

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510616

Title:
  Missing PCI IDs for Intel 7265D wireless hw

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510616/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Alexander List]

Still happening on Xenial with latest distro kernel:

[   12.777803] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
[   12.777826] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun

Linux hkgofdt02 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550779

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573525] Re: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alexander List]

*** This bug is a duplicate of bug 1571174 ***
https://bugs.launchpad.net/bugs/1571174

** This bug has been marked a duplicate of bug 1571174
   package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573525

Title:
  package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1573525/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1313784] Re: File descriptors leaked on lvs invocation

[Alexander List]

Still visible on 16.04 LTS today.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313784

Title:
  File descriptors leaked on lvs invocation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1313784/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571174] Re: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alexander List]

I tried the same again in a Docker container:

1.) docker run --privileged -ti ubuntu:15.10 /bin/bash
2.) apt-get update; apt-get -y dist-upgrade
3.) apt-get install ufw squid-deb-proxy wget
4.) service squid-deb-proxy start
5.) wget 
http://archive.ubuntu.com/ubuntu/pool/main/u/ufw/ufw_0.35-0ubuntu2_all.deb
6.) dpkg -i ufw_0.35-0ubuntu2_all.deb
7.) due to 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1570947 
did
export SUDO_USER=root
export SUDO_UID=0
export SUDO_COMMAND=/bin/bash
export SUDO_GID=0
8.) do-release-upgrade -d 

completed without further errors. --> upgrading ufw before squid helps

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571174

Title:
  package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570947] Re: Trusty to Xenial upgrade KeyError: 'SUDO_UID'

[Alexander List]

Of course, a workaround is to set these env variables when not using
sudo but logging in as root and doing release upgrade:

export SUDO_USER=root
export SUDO_UID=0
export SUDO_COMMAND=/bin/bash
export SUDO_GID=0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570947

Title:
  Trusty to Xenial upgrade KeyError: 'SUDO_UID'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1570947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570947] Re: Trusty to Xenial upgrade KeyError: 'SUDO_UID'

[Alexander List]

I just ran into the same issue testing the release upgrade from 15.10 to
16.04 in a Docker container.

I started the container with

docker run -ti ubuntu:15.10 /bin/bash

and then installed ubuntu-release-upgrader-core and tried the upgrade,
and hit exactly the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570947

Title:
  Trusty to Xenial upgrade KeyError: 'SUDO_UID'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1570947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1539546] Re: Service mountdevsubfs has to be enabled to start service lvm2

[Alexander List]

Still visible today during an upgrade from 15.10 to 16.04:

Setting up lvm2 (2.02.133-1ubuntu9) ...
Installing new version of config file /etc/init.d/lvm2 ...
Installing new version of config file /etc/lvm/lvm.conf ...
update-initramfs: deferring update (trigger activated)
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Processing triggers for systemd (229-4ubuntu4) ...
Processing triggers for initramfs-tools (0.122ubuntu8) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-18-lowlatency
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
W: plymouth: The plugin label.so is missing, the selected theme might not work 
as expected.
W: plymouth: You might want to install the plymouth-themes and plymouth-label 
package to fix this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539546

Title:
  Service mountdevsubfs has to be enabled to start service lvm2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1539546/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571174] Re: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alexander List]

Continuing the upgrade with

apt-get -f install
apt-get dist-upgrade

completed without further errors.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571174

Title:
  package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571174] [NEW] package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alexander List]

Public bug reported:

During an upgrade from 15.10 to 16.04, upgrading squid3 erred out...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: squid3 3.3.8-1ubuntu16.2
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sat Apr 16 05:33:51 2016
DuplicateSignature: package:squid3:3.3.8-1ubuntu16.2:dependency problems - 
leaving triggers unprocessed
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-07 (131 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: squid3
Title: package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago)
modified.conffile..etc.apparmor.d.usr.sbin.squid3: [deleted]
modified.conffile..etc.init.d.squid3: [deleted]
modified.conffile..etc.init.squid3.conf: [deleted]
modified.conffile..etc.logrotate.d.squid3: [deleted]
modified.conffile..etc.resolvconf.update.libc.d.squid3: [deleted]
modified.conffile..etc.squid3.errorpage.css: [deleted]
modified.conffile..etc.squid3.msntauth.conf: [deleted]
modified.conffile..etc.squid3.squid.conf: [deleted]
modified.conffile..etc.ufw.applications.d.squid3: [deleted]

** Affects: squid3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571174

Title:
  package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571166] Re: package squid3 3.3.8-1ubuntu16.2 failed to install

[Alexander List]

*** This bug is a duplicate of bug 1571174 ***
https://bugs.launchpad.net/bugs/1571174

** This bug has been marked a duplicate of bug 1571174
   package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571166

Title:
  package squid3 3.3.8-1ubuntu16.2 failed to install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571166] [NEW] package squid3 3.3.8-1ubuntu16.2 failed to install

[Alexander List]

Public bug reported:

Trying to upgrade from 15.10 to 16.04 LTS, the upgrade of squid
failed...

When trying to use the automatic bug reporter, Launchpad complained that
it doesn't understand some of the data in the forms.

For reference,  here's the URL with the automagically uploaded data:

https://bugs.launchpad.net/ubuntu/+source/squid3/+filebug/b2f8bbcc-
03b8-11e6-8b20-002481e7f48a?field.title=package+squid3+3.3.8-1ubuntu16.2+failed+to+install%

** Affects: squid3 (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/1571166

Title:
  package squid3 3.3.8-1ubuntu16.2 failed to install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1284196] Re: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot

[Alexander List]

Hi rodsmith,

thanks a lot for your follow-up analysis.

I can confirm that I saw this issue with the server forcibly switched to
EFI only, and using grub-efi.

I cannot easily reproduce this because the system is in production use,
but I will nevertheless send a report to Supermicro with my findings, so
they can try to reproduce it on identical hardware and with 15.10 in EFI
mode. Supermicro are usually very responsive and provide fixed BIOS
within a very reasonable time frame.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284196

Title:
  Install to 3TB disk fails with "attempt to read or write outside of
  disk" error on reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1284196] Re: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot

[Alexander List]

I experienced the same problem on a System running 15.04. I know that's
EOL, but just for reference this is how I ended up in this situation:

My system is a server (Supermicro SYS-6028R-WTRT, latest firmware) with
a 4TB RAID1 for the OS, and another RAID volume for data. The system
supports legacy and UEFI boot, but due to the disk size involved I
disabled legacy or "dual mode" booting and forced the system to UEFI
only so that the installer would dtrt on an EFI system.

I used MAAS to install it. MAAS (or, the preseeds that ship with it)
created a 4TB root fs (cloudimg-rootfs) and an EFI partition.

That is the fundamental issue here: grub cannot deal with files outside
the 2TB limit it seems. I tried to manually load the initrd, and got a
similar error message.

So I started using the rescue boot provided by the Ubuntu Server install
ISO to repartition.

In the end, I created separate LVM logical volumes on the second RAID,
moved /usr /var /home to separate filesystems in LVM, and eventually
reduced the space consumed by the rootfs to a manageable size.

I created another LV for the root filesystem and one for swap (the MAAS
install used /swap.img on the root fs...)

Then I copied all the directories from the root partition (/bin, /sbin,
/lib etc) to that new filesystem.

After editing fstab in the new root, and rebooting with the rescue image
using the new LV as root FS, I was able to delete my /dev/sda1, recreate
it with ~1.5TB of space, and moved everything that was in /boot on the
root filesystem over there.

Summary: I made sure that grub, kernel etc live in an area of the disk
that grub can access.

After repartitioning, I did update-grub, reinstalled the kernel just to
be sure, and rebooted - the system now boots fine again.

My suggestion is to still create a ~1GB /boot partition even on EFI
systems. And in case the installer still defaults to ~256M in case of
legacy systems, that should get fixed as well if the disk is large
enough - autoremoving old kernels was only fixed recently :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284196

Title:
  Install to 3TB disk fails with "attempt to read or write outside of
  disk" error on reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1546838] [NEW] compiz segfaulting on Parallels VM (MBP)

[Alexander List]

Public bug reported:

compiz[2823]: segfault at 71 ip 7f3fcee22173 sp 7ffd67b0e8f0
error 4 in libprlcompiz_0_9_12_2.so[7f3fcee1b000+b000]

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Feb 18 10:09:40 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: parallels-tools, 11.1.2.32408, 4.2.0-27-generic, x86_64: installed
GraphicsCard:
 Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA 
controller])
   Subsystem: Parallels, Inc. Device [1ab8:0400]
InstallationDate: Installed on 2015-11-07 (102 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Parallels Software International Inc. Parallels Virtual Platform
PackageArchitecture: all
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=a98c2de4-95b3-40f6-b269-d6c02f098915 ro quiet splash vt.handoff=7
SourcePackage: compiz
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2015
dmi.bios.vendor: Parallels Software International Inc.
dmi.bios.version: 11.1.2 (32408)
dmi.board.name: Parallels Virtual Platform
dmi.board.vendor: Parallels Software International Inc.
dmi.board.version: None
dmi.chassis.type: 10
dmi.chassis.vendor: Parallels Software International Inc.
dmi.modalias: 
dmi:bvnParallelsSoftwareInternationalInc.:bvr11.1.2(32408):bd12/24/2015:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct10:cvr:
dmi.product.name: Parallels Virtual Platform
dmi.product.version: None
dmi.sys.vendor: Parallels Software International Inc.
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Feb 18 10:00:31 2016
xserver.configfile: None
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputSleep Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: prlvideo

** Affects: compiz (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu wily

** Summary changed:

- compiz segfaulting
+ compiz segfaulting on Parallels VM (MBP)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546838

Title:
  compiz segfaulting on Parallels VM (MBP)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1546838/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545653] [NEW] Unrecognized relocation when compiling

[Alexander List]

Public bug reported:

I am trying to compile a program against a library that was built using
gcc 5.3 on Wily, which has gcc 5.2.1.

I get

/usr/bin/ld: : unrecognized relocation (0x2a) in section `.text'
/usr/bin/ld: final link failed: Bad value
collect2: error: ld returned 1 exit status

This looks exactly like

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: binutils 2.25.1-6ubuntu2
ProcVersionSignature: User Name 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Feb 15 09:53:05 2016
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-22ubuntu2
 zlib1g 1:1.2.8.dfsg-2ubuntu4
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: binutils
UpgradeStatus: Upgraded to wily on 2016-02-13 (2 days ago)

** Affects: binutils
 Importance: Unknown
 Status: Unknown

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug wily

** Bug watch added: Debian Bug tracker #808205
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205

** Also affects: binutils via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808205
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545653

Title:
  Unrecognized relocation when compiling

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1545653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1544400] Re: squid3: systemctl reports squid is running when there is a bungled squid.conf and it has exited.

[Alexander List]

Steps to reproduce:

1) install squid3 (wily)
2) systemd is able to start/stop squid3
3) break the config (add a syntax error that prevents squid3 from starting)
4) neither manual nor systemd startup of squid3 work (expected)
5) fix the config
6) manual startup works again (expected), systemctl start squid3 does not 
(unexpected)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1544400

Title:
  squid3: systemctl reports squid is running when there is a bungled
  squid.conf and it has exited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1544400/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1544400] Re: squid3: systemctl reports squid is running when there is a bungled squid.conf and it has exited.

[Alexander List]

Steps to reproduce:

1) install squid3 (wily)
2) systemd is able to start/stop squid3
3) break the config (add a syntax error that prevents squid3 from starting)
4) neither manual nor systemd startup of squid3 work (expected)
5) fix the config
6) manual startup works again (expected), systemctl start squid3 does not 
(unexpected)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544400

Title:
  squid3: systemctl reports squid is running when there is a bungled
  squid.conf and it has exited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1544400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1514717] Re: linker error when disabling CXX11_ABI

[Alexander List]

Marked as invalid, as this is not expected to work.

** Changed in: boost1.58 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514717

Title:
  linker error when disabling CXX11_ABI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.58/+bug/1514717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1514717] [NEW] linker error when disabling CXX11_ABI

[Alexander List]

Public bug reported:

We have third party libraries that worked fine on Ubuntu 15.04 x86_64
using boost1.55 and gcc-4.9.2.

These libraries (we do not have access to the source, so recompiling is
not an option) rely on the old ABI for std::string

On 15.10, if we disable the CXX11 ABI, we get a linker error when
linking against boost libraries.

I am attaching sample code to reproduce the issue.

# this works fine
g++ -o main main.cc -lboost_program_options

# this does not
g++ -o main main.cc -lboost_program_options  -D_GLIBCXX_USE_CXX11_ABI=0

alex@wily:~$ g++ -o main main.cc -lboost_program_options  
-D_GLIBCXX_USE_CXX11_ABI=0
/tmp/ccVJh1if.o: In function `main':
main.cc:(.text+0x8f): undefined reference to 
`boost::program_options::options_description::options_description(std::string 
const&, unsigned int, unsigned int)'
/tmp/ccVJh1if.o:(.rodata._ZTVN5boost15program_options11typed_valueISscEE[_ZTVN5boost15program_options11typed_valueISscEE]+0x38):
 undefined reference to 
`boost::program_options::value_semantic_codecvt_helper::parse(boost::any&,
 std::vector const&, bool) const'
/tmp/ccVJh1if.o: In function `boost::program_options::typed_value::name() const':
main.cc:(.text._ZNK5boost15program_options11typed_valueISscE4nameEv[_ZNK5boost15program_options11typed_valueISscE4nameEv]+0x35):
 undefined reference to `boost::program_options::arg'
/tmp/ccVJh1if.o: In function `boost::program_options::typed_value::xparse(boost::any&, std::vector const&) const':
main.cc:(.text._ZNK5boost15program_options11typed_valueISscE6xparseERNS_3anyERKSt6vectorISsSaISsEE[_ZNK5boost15program_options11typed_valueISscE6xparseERNS_3anyERKSt6vectorISsSaISsEE]+0xa9):
 undefined reference to `boost::program_options::validate(boost::any&, 
std::vector const&, std::string*, 
int)'
collect2: error: ld returned 1 exit status

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libboost1.58-dev 1.58.0+dfsg-3.1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Tue Nov 10 15:04:35 2015
Dependencies:
 
InstallationDate: Installed on 2015-11-09 (0 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: boost1.58
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: boost1.58 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Attachment added: "Sample code to demonstrate the issue"
   https://bugs.launchpad.net/bugs/1514717/+attachment/4515915/+files/main.cc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514717

Title:
  linker error when disabling CXX11_ABI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.58/+bug/1514717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1514388] [NEW] installer does not let me choose UTC time zone when I set language to English/US

[Alexander List]

Public bug reported:

I am trying to install a new machine (VM) using ubuntu-15.10-server-
amd64.iso

I have selected US English locale everywhere, now I have to choose a
timezone, and I am only offered US time zones.

Many sysadmins in particular in global corporations with multiple
locations prefer US English as the language, and UTC as timezone on
servers.

Now, installer tells me to go back and choose a different country than
US ...

I don't want to configure it to UK English or Iceland or some exotic
island, as I don't want to have daylight savings changes on this box. I
want the TZ to be UTC at all times, and the locale US English.

I have reported this upstream before the wily release as the bug has
been inherited from Debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793119

...but no reaction so far, and now Wily was released with the bug...

** Affects: base-installer (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: debian-installer (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #793119
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793119

** Also affects: debian-installer (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793119
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514388

Title:
  installer does not let me choose UTC time zone when I set language to
  English/US

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1514388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1360400] Re: Invalid maas.log permission caused django to crash

[Alexander List]

I just upgraded from 14.04 all the way to 15.10.

2015-10-28 10:17:17 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~14.04.1 
1.7.6+bzr3376-0ubuntu2~15.04.1
2015-10-28 10:54:59 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~15.04.1 
1.8.3+bzr4053-0ubuntu1

MAAS wouldn't start up, with this in syslog:

Oct 28 11:09:50 maas-region-hkg sh[2050]: ValueError: Unable to
configure handler 'log': [Errno 13] Permission denied: '/var/log/maas
/maas-django.log'

That file was owned by root:root, I chowned it to maas:maas, which seems
to have fixed the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360400

Title:
  Invalid maas.log permission caused django to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1360400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1360400] Re: Invalid maas.log permission caused django to crash

[Alexander List]

I just upgraded from 14.04 all the way to 15.10.

2015-10-28 10:17:17 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~14.04.1 
1.7.6+bzr3376-0ubuntu2~15.04.1
2015-10-28 10:54:59 upgrade maas-common:all 1.7.6+bzr3376-0ubuntu2~15.04.1 
1.8.3+bzr4053-0ubuntu1

MAAS wouldn't start up, with this in syslog:

Oct 28 11:09:50 maas-region-hkg sh[2050]: ValueError: Unable to
configure handler 'log': [Errno 13] Permission denied: '/var/log/maas
/maas-django.log'

That file was owned by root:root, I chowned it to maas:maas, which seems
to have fixed the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1360400

Title:
  Invalid maas.log permission caused django to crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1360400/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Sagar, please use ifconfig and its manpage. I did nothing magic, just
manual interface configuration instead of DHCP.

It is really just about giving the interface an IP/subnet, and
eventually a default gateway with "route add" ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Sagar, please use ifconfig and its manpage. I did nothing magic, just
manual interface configuration instead of DHCP.

It is really just about giving the interface an IP/subnet, and
eventually a default gateway with "route add" ...

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1465506] Re: plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH

[Alexander List]

Control variate:

still getting this on the latest 4.2 mainline kernel

[   24.358337] [ cut here ]
[   24.358356] WARNING: CPU: 2 PID: 1026 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1362 
assert_plane.constprop.94+0x73/0xa0 [i915]()
[   24.358356] plane A assertion failure (expected on, current off)
[   24.358375] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables cmac rfcomm bnep nls_iso8859_1 uas 
usb_storage arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iwlmvm 
uvcvideo aesni_intel aes_x86_64 lrw mac80211 gf128mul glue_helper ablk_helper 
cryptd snd_usb_audio videobuf2_vmalloc snd_usbmidi_lib serio_raw snd_seq_midi 
snd_seq_midi_event videobuf2_memops videobuf2_core v4l2_common snd_rawmidi 
snd_hda_codec_hdmi iwlwifi snd_hda_codec_realtek videodev snd_hda_codec_generic
[   24.358395]  btusb snd_seq btrtl media joydev btbcm btintel cfg80211 
input_leds bluetooth mei_me snd_hda_intel mei snd_hda_codec lpc_ich 
snd_soc_rt5640 snd_hda_core snd_soc_rl6231 shpchp snd_hwdep snd_soc_core 
snd_compress ac97_bus nuvoton_cir snd_pcm_dmaengine rc_core snd_pcm 
snd_soc_sst_acpi snd_seq_device snd_timer i2c_hid acpi_pad dw_dmac snd 
dw_dmac_core 8250_dw i2c_designware_platform i2c_designware_core 
spi_pxa2xx_platform soundcore mac_hid acpi_als kfifo_buf industrialio 
parport_pc ppdev sunrpc lp parport autofs4 raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse e1000e 
drm ahci ptp libahci pps_core sdhci_acpi video sdhci
[   24.358397] CPU: 2 PID: 1026 Comm: Xorg Not tainted 4.2.0-040200rc8-generic 
#201508240030
[   24.358397] Hardware name: 
\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x
 
\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x/NUC5i7RYB,
 BIOS RYBDWi35.86A.0246.2015.0309.1355 03/09/2015
[   24.358399]  c025bc70 8804084bf7b8 817a1aa3 
0001
[   24.358400]  8804084bf808 8804084bf7f8 8107719a 
880035df
[   24.358401]   880035df 8804072e3000 
8804072e3060
[   24.358401] Call Trace:
[   24.358404]  [] dump_stack+0x45/0x57
[   24.358406]  [] warn_slowpath_common+0x8a/0xc0
[   24.358408]  [] warn_slowpath_fmt+0x46/0x50
[   24.358418]  [] assert_plane.constprop.94+0x73/0xa0 [i915]
[   24.358427]  [] hsw_disable_ips+0x41/0x180 [i915]
[   24.358436]  [] intel_pre_disable_primary+0x5d/0x90 [i915]
[   24.358444]  [] intel_crtc_disable_planes+0x48/0x110 [i915]
[   24.358452]  [] __intel_set_mode+0x251/0xb10 [i915]
[   24.358460]  [] ? intel_modeset_compute_config+0x362/0xb60 
[i915]
[   24.358468]  [] intel_crtc_set_config+0x366/0x5a0 [i915]
[   24.358477]  [] drm_mode_set_config_internal+0x68/0x100 
[drm]
[   24.358482]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
[   24.358484]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
[   24.358486]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
[   24.358495]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
[   24.358497]  [] ? jbd2_journal_dirty_metadata+0xb6/0x250
[   24.358499]  [] fb_set_var+0x191/0x400
[   24.358501]  [] ? __ext4_handle_dirty_metadata+0x81/0x210
[   24.358503]  [] fbcon_blank+0x1bc/0x2b0
[   24.358505]  [] do_unblank_screen+0xb8/0x1c0
[   24.358507]  [] vt_ioctl+0x1063/0x10e0
[   24.358508]  [] ? __slab_free+0x104/0x25c
[   24.358510]  [] tty_ioctl+0x1f7/0xbe0
[   24.358512]  [] ? kzfree+0x31/0x40
[   24.358513]  [] ? kfree+0xf8/0x130
[   24.358515]  [] do_vfs_ioctl+0x2cd/0x4b0
[   24.358517]  [] ? mntput+0x24/0x40
[   24.358518]  [] ? __fput+0x190/0x210
[   24.358519]  [] SyS_ioctl+0x79/0x90
[   24.358520]  [] entry_SYSCALL_64_fastpath+0x16/0x75
[   24.358521] ---[ end trace 537139706fa96fdd ]---

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465506

Title:
  plane A assertion failure (expected on, current off) on Intel NUC
  5i5RYH

To manage notifications about 

[Bug 1465506] Re: plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH

[Alexander List]

The above snipped was for 4.2.0rc8, the one below is from 4.2.0
(release)

---
[   25.866954] [ cut here ]
[   25.866970] WARNING: CPU: 2 PID: 1030 at 
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:1362 
assert_plane.constprop.94+0x73/0xa0 [i915]()
[   25.866971] plane A assertion failure (expected on, current off)
[   25.866991] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables cmac rfcomm bnep uas nls_iso8859_1 
usb_storage input_leds joydev uvcvideo videobuf2_vmalloc hid_generic 
videobuf2_memops videobuf2_core v4l2_common videodev btusb snd_usb_audio btrtl 
usbhid btbcm media snd_usbmidi_lib btintel bluetooth arc4 intel_rapl iosf_mbi 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iwlmvm 
crct10dif_pclmul mac80211 crc32_pclmul ghash_clmulni_intel 
snd_hda_codec_realtek snd_hda_codec_hdmi snd_soc_rt5640 snd_hda_codec_generic 
aesni_intel snd_soc_rl6231
[   25.867011]  snd_soc_core aes_x86_64 lrw snd_compress iwlwifi ac97_bus 
gf128mul snd_pcm_dmaengine glue_helper ablk_helper snd_hda_intel snd_seq_midi 
cryptd snd_hda_codec snd_seq_midi_event snd_hda_core snd_hwdep cfg80211 
serio_raw snd_pcm lpc_ich mei_me shpchp snd_rawmidi mei snd_seq snd_seq_device 
snd_timer nuvoton_cir rc_core snd i2c_hid hid dw_dmac dw_dmac_core 
snd_soc_sst_acpi soundcore i2c_designware_platform acpi_als 8250_dw 
i2c_designware_core kfifo_buf spi_pxa2xx_platform acpi_pad industrialio mac_hid 
parport_pc ppdev lp parport sunrpc autofs4 raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear i915 i2c_algo_bit psmouse drm_kms_helper e1000e drm ahci libahci ptp 
pps_core sdhci_acpi video sdhci
[   25.867012] CPU: 2 PID: 1030 Comm: Xorg Not tainted 4.2.0-040200-generic 
#201508301530
[   25.867013] Hardware name: 
\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x
 
\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x\x/NUC5i7RYB,
 BIOS RYBDWi35.86A.0246.2015.0309.1355 03/09/2015
[   25.867014]  c025bc48 880408f237b8 817a1b43 
0001
[   25.867015]  880408f23808 880408f237f8 8107719a 
880035e0
[   25.867016]   880035e0 88040c393800 
88040c393860
[   25.867016] Call Trace:
[   25.867020]  [] dump_stack+0x45/0x57
[   25.867022]  [] warn_slowpath_common+0x8a/0xc0
[   25.867023]  [] warn_slowpath_fmt+0x46/0x50
[   25.867034]  [] assert_plane.constprop.94+0x73/0xa0 [i915]
[   25.867043]  [] hsw_disable_ips+0x41/0x180 [i915]
[   25.867051]  [] intel_pre_disable_primary+0x5d/0x90 [i915]
[   25.867059]  [] intel_crtc_disable_planes+0x48/0x110 [i915]
[   25.867067]  [] __intel_set_mode+0x251/0xb10 [i915]
[   25.867075]  [] ? intel_modeset_compute_config+0x362/0xb60 
[i915]
[   25.867083]  [] intel_crtc_set_config+0x366/0x5a0 [i915]
[   25.867092]  [] drm_mode_set_config_internal+0x68/0x100 
[drm]
[   25.867095]  [] restore_fbdev_mode+0xc2/0xf0 
[drm_kms_helper]
[   25.867098]  [] 
drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
[   25.867101]  [] drm_fb_helper_set_par+0x22/0x40 
[drm_kms_helper]
[   25.867109]  [] intel_fbdev_set_par+0x1a/0x60 [i915]
[   25.867112]  [] ? jbd2_journal_dirty_metadata+0xb6/0x250
[   25.867114]  [] fb_set_var+0x191/0x400
[   25.867115]  [] ? __ext4_handle_dirty_metadata+0x81/0x210
[   25.867117]  [] fbcon_blank+0x1bc/0x2b0
[   25.867119]  [] do_unblank_screen+0xb8/0x1c0
[   25.867121]  [] vt_ioctl+0x1063/0x10e0
[   25.867123]  [] ? __slab_free+0x104/0x25c
[   25.867125]  [] tty_ioctl+0x1f7/0xbe0
[   25.867127]  [] ? kzfree+0x31/0x40
[   25.867128]  [] ? kfree+0xf8/0x130
[   25.867130]  [] do_vfs_ioctl+0x2cd/0x4b0
[   25.867131]  [] ? mntput+0x24/0x40
[   25.867133]  [] ? __fput+0x190/0x210
[   25.867134]  [] SyS_ioctl+0x79/0x90
[   25.867135]  [] entry_SYSCALL_64_fastpath+0x16/0x75
[   25.867136] ---[ end trace c6b6cf80ff58f9ce ]---
---

** Bug watch added: Linux Kernel Bug Tracker #103771
   http://bugzilla.kernel.org/show_bug.cgi?id=103771

** Also affects: xserver-xorg-video-intel via
   http://bugzilla.kernel.org/show_bug.cgi?id=103771
   Importance: Unknown
   Status: Unknown

-- 

[Bug 1488719] Re: dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

Tried 4.2.0 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.2-unstable/ - same result.

** Attachment added: dmesg.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+attachment/4454775/+files/dmesg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488719] Re: dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

** Bug watch added: freedesktop.org Bugzilla #80896
   https://bugs.freedesktop.org/show_bug.cgi?id=80896

** Also affects: linux via
   https://bugs.freedesktop.org/show_bug.cgi?id=80896
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488719] Re: dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

Nope. Still get that message.

** Attachment added: dmesg.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+attachment/4453738/+files/dmesg.log

** 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.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488758] Re: GPU crash on NUC with i915

[Alexander List]

This problem occured once in two months, and we are not aware of a way
to trigger it. However, there is a clear indication that the bug is well
known upstream, so it should be followed up with in Ubuntu as well.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

** Tags added: bot-stop-nagging

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488758

Title:
  GPU crash on NUC with i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488758] Re: GPU crash on NUC with i915

[Alexander List]

Maybe relevant:

https://bugs.freedesktop.org/show_bug.cgi?id=89901

** Bug watch added: freedesktop.org Bugzilla #89901
   https://bugs.freedesktop.org/show_bug.cgi?id=89901

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488758

Title:
  GPU crash on NUC with i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488758] Re: GPU crash on NUC with i915

[Alexander List]

** Attachment added: lspci-vnvn.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+attachment/4452466/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488758

Title:
  GPU crash on NUC with i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488758] [NEW] GPU crash on NUC with i915

[Alexander List]

Public bug reported:

Setup:

Intel NUC, i915 graphics, two monitors, one connected with
miniHDMI-HDMI cable, second with miniDP-HDMI cable.

Screen goes black, flickers back on, goes black again. Only resolution
is to ssh into the machine and reboot.

Before rebooting, I got lots of these (about 106k lines) in syslog:

kernel: [404964.521324] [drm:hsw_unclaimed_reg_detect.isra.12 [i915]]
*ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to
debug this problem.[drm:hsw_unclaimed_reg_detect.isra.12 [i915]] *ERROR*
Unclaimed register detected. Please use the i915.mmio_debug=1 to debug
this problem.

...then,

kernel: [406333.381029] [drm] stuck on render ring
kernel: [406333.381945] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], 
reason: Ring hung, action: reset
kernel: [406333.381947] [drm] GPU hangs can indicate a bug anywhere in the 
entire gfx stack, including userspace.
kernel: [406333.381947] [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI - DRM/Intel
kernel: [406333.381948] [drm] drm/i915 developers can then reassign to the 
right component if it's not a kernel issue.
kernel: [406333.381949] [drm] The gpu crash dump is required to analyze gpu 
hangs, so please always attach it.
kernel: [406333.381951] [drm] GPU crash dump saved to /sys/class/drm/card0/error
kernel: [406333.389006] drm/i915: Resetting chip after gpu hang
kernel: [406339.379515] [drm] stuck on render ring
kernel: [406339.380430] [drm] GPU HANG: ecode 8:0:0x85db, in 
webapp-containe [14994], reason: Ring hung, action: reset
kernel: [406339.380583] drm/i915: Resetting chip after gpu hang
kernel: [406417.336790] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], 
reason: Ring hung, action: reset
kernel: [406417.343850] drm/i915: Resetting chip after gpu hang
kernel: [407944.976072] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], 
reason: Ring hung, action: reset
kernel: [407944.983106] drm/i915: Resetting chip after gpu hang
kernel: [409258.618636] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], 
reason: Ring hung, action: reset
kernel: [409258.625733] drm/i915: Resetting chip after gpu hang
kernel: [409264.604180] [drm] stuck on render ring
kernel: [409264.605059] [drm] GPU HANG: ecode 8:0:0xf5de, in Xorg [918], 
reason: Ring hung, action: reset
kernel: [409264.605153] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging 
too fast, banning!
kernel: [409264.612163] drm/i915: Resetting chip after gpu hang

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-26-generic 3.19.0-26.28
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
Date: Wed Aug 26 12:31:15 2015
InstallationDate: Installed on 2015-08-01 (24 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Attachment added: version.log
   
https://bugs.launchpad.net/bugs/1488758/+attachment/4452454/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488758

Title:
  GPU crash on NUC with i915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488758/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488719] Re: dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

** Attachment added: lspci-vnvn.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+attachment/4452389/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488719] [NEW] dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

Public bug reported:

On a recent intel NUC using i915 graphics, I get the following errors in
dmesg:

[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied
(SDE)!

There are two monitors connected to this box, one with mini-HDMI-HDMI,
one with mini-DP-HDMI cable.

Maybe related:

https://bugs.freedesktop.org/show_bug.cgi?id=80896

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic 3.19.0.26.25
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
Date: Wed Aug 26 10:07:31 2015
InstallationDate: Installed on 2015-08-01 (24 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

** Attachment added: output of dmidecode
   
https://bugs.launchpad.net/bugs/1488719/+attachment/4452377/+files/dmidecode.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1488719] Re: dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

[Alexander List]

** Attachment added: version.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+attachment/4452390/+files/version.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488719

Title:
  dmesg shows [drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1487283] [NEW] DNS forwarding doesn't work because MAAS enables dnssec

[Alexander List]

Public bug reported:

I have a MAAS server that uses a box running dnsmasq as a DNS forwarder.

With MAAS enabling dnssec by default, I get errors like these and DNS
resolution from the MAAS provisioned machines doesn't work beyond what
MAAS manages.

Aug 21 01:29:17 maas-region-hkg named[1147]: error (no valid RRSIG) resolving 
'mediawiki/DS/IN': ipv4addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (network unreachable) 
resolving 'mediawiki/DS/IN': ipv6addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (network unreachable) 
resolving 'mediawiki/DS/IN': ipv6addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (insecurity proof failed) 
resolving 'mediawiki//IN': ipv4addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (insecurity proof failed) 
resolving 'mediawiki/A/IN': ipv4addr#53

/etc/bind/named.conf options contains this stanza:

//
// This file is managed by MAAS. Although MAAS attempts to preserve changes
// made here, it is possible to create conflicts that MAAS can not resolve.
//
// DNS settings available in MAAS (for example, forwarders and
// dnssec-validation) should be managed only in MAAS.

I I disable dnssec, name resolution works, and I didn't find a place in
the web UI where I can disable dnssec.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.7.6+bzr3376-0ubuntu2~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug 21 02:55:27 2015
InstallationDate: Installed on 2015-08-10 (10 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS Trusty Tahr - Beta amd64 
(20150805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1487283

Title:
  DNS forwarding doesn't work because MAAS enables dnssec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1487283/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1487283] [NEW] DNS forwarding doesn't work because MAAS enables dnssec

[Alexander List]

Public bug reported:

I have a MAAS server that uses a box running dnsmasq as a DNS forwarder.

With MAAS enabling dnssec by default, I get errors like these and DNS
resolution from the MAAS provisioned machines doesn't work beyond what
MAAS manages.

Aug 21 01:29:17 maas-region-hkg named[1147]: error (no valid RRSIG) resolving 
'mediawiki/DS/IN': ipv4addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (network unreachable) 
resolving 'mediawiki/DS/IN': ipv6addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (network unreachable) 
resolving 'mediawiki/DS/IN': ipv6addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (insecurity proof failed) 
resolving 'mediawiki//IN': ipv4addr#53
Aug 21 01:29:17 maas-region-hkg named[1147]: error (insecurity proof failed) 
resolving 'mediawiki/A/IN': ipv4addr#53

/etc/bind/named.conf options contains this stanza:

//
// This file is managed by MAAS. Although MAAS attempts to preserve changes
// made here, it is possible to create conflicts that MAAS can not resolve.
//
// DNS settings available in MAAS (for example, forwarders and
// dnssec-validation) should be managed only in MAAS.

I I disable dnssec, name resolution works, and I didn't find a place in
the web UI where I can disable dnssec.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.7.6+bzr3376-0ubuntu2~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug 21 02:55:27 2015
InstallationDate: Installed on 2015-08-10 (10 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS Trusty Tahr - Beta amd64 
(20150805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487283

Title:
  DNS forwarding doesn't work because MAAS enables dnssec

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1487283/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1487316] [NEW] MAAS doesn't report disk size of VM correctly

[Alexander List]

Public bug reported:

I have a MAAS running in a VM, LAN is bridged.

I created another VM using virt-manager, with CPU 1, RAM 1G, disk 8G and
PXE booted it from MAAS.

I have configured the power type as libvirt and added necessary
credentials to MAAS so it can remote control libvirtd via ssh.

Enlisting, commissioning, and deploying works.

However, MAAS reports the disk size as 1G even though it is 8G.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.7.6+bzr3376-0ubuntu2~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug 21 04:20:30 2015
InstallationDate: Installed on 2015-08-10 (10 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS Trusty Tahr - Beta amd64 
(20150805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1487316

Title:
  MAAS doesn't report disk size of VM correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1487316/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1487316] [NEW] MAAS doesn't report disk size of VM correctly

[Alexander List]

Public bug reported:

I have a MAAS running in a VM, LAN is bridged.

I created another VM using virt-manager, with CPU 1, RAM 1G, disk 8G and
PXE booted it from MAAS.

I have configured the power type as libvirt and added necessary
credentials to MAAS so it can remote control libvirtd via ssh.

Enlisting, commissioning, and deploying works.

However, MAAS reports the disk size as 1G even though it is 8G.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.7.6+bzr3376-0ubuntu2~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Fri Aug 21 04:20:30 2015
InstallationDate: Installed on 2015-08-10 (10 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS Trusty Tahr - Beta amd64 
(20150805)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487316

Title:
  MAAS doesn't report disk size of VM correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1487316/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1484404] [NEW] kvm unhandled rdmsr - DNS resolution fails

[Alexander List]

Public bug reported:

I have a VM host running Ubuntu 14.04.2 LTS, and several VMs running
15.04.

On the host, I found these:

Aug 13 07:47:04 hkgdcsrv01 kernel: [1804566.706973] kvm [21590]: vcpu1 
unhandled rdmsr: 0x606
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.776637] kvm [21590]: vcpu0 
unhandled rdmsr: 0x611
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.784732] kvm [21590]: vcpu0 
unhandled rdmsr: 0x639
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.792692] kvm [21590]: vcpu0 
unhandled rdmsr: 0x641
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.800670] kvm [21590]: vcpu0 
unhandled rdmsr: 0x619

On the VM, I found this one:

[1.657384] intel_rapl: no valid rapl domains found in package 0
[1.921566] ifquery[350]: segfault at 1 ip 004031c8 sp 
7fffd4fa8570 error 4 in ifup[40+d000]


Symptoms:

- I can ping my LAN and the world
- I can ping the DNS that is listed in /etc/resolv.conf
- I can *not* get names resolved against that DNS from this VM
- there is no firewall in between

After rebooting the host, everything is back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.15
ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
Uname: Linux 3.16.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Aug 13 07:51:43 2015
InstallationDate: Installed on 2015-07-06 (38 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484404

Title:
  kvm unhandled rdmsr - DNS resolution fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1484404/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1484404] [NEW] kvm unhandled rdmsr - DNS resolution fails

[Alexander List]

Public bug reported:

I have a VM host running Ubuntu 14.04.2 LTS, and several VMs running
15.04.

On the host, I found these:

Aug 13 07:47:04 hkgdcsrv01 kernel: [1804566.706973] kvm [21590]: vcpu1 
unhandled rdmsr: 0x606
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.776637] kvm [21590]: vcpu0 
unhandled rdmsr: 0x611
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.784732] kvm [21590]: vcpu0 
unhandled rdmsr: 0x639
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.792692] kvm [21590]: vcpu0 
unhandled rdmsr: 0x641
Aug 13 07:47:05 hkgdcsrv01 kernel: [1804567.800670] kvm [21590]: vcpu0 
unhandled rdmsr: 0x619

On the VM, I found this one:

[1.657384] intel_rapl: no valid rapl domains found in package 0
[1.921566] ifquery[350]: segfault at 1 ip 004031c8 sp 
7fffd4fa8570 error 4 in ifup[40+d000]


Symptoms:

- I can ping my LAN and the world
- I can ping the DNS that is listed in /etc/resolv.conf
- I can *not* get names resolved against that DNS from this VM
- there is no firewall in between

After rebooting the host, everything is back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1.15
ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
Uname: Linux 3.16.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Aug 13 07:51:43 2015
InstallationDate: Installed on 2015-07-06 (38 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1484404

Title:
  kvm unhandled rdmsr - DNS resolution fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1484404/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

[Alexander List]

Did you even consider providing the fix via SRU?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267059

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

[Alexander List]

So, there is a fix released, but it is still not in backports for
trusty... how does that help affected users?

Please backport the fix to all currently supported versions of Ubuntu,
and propose it for SRU. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267059

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473625] [NEW] Installing MAAS using 15.04 server ISO (amd64) on remote machine via virt-manager results in black screen

[Alexander List]

Public bug reported:

What I did:

* Set up a box as VM host for manually provisioned VMs (using ssh and 
virt-manager)
* Created a new VM using the 15.04 server ISO (amd64)
* Select multiple host install using MAAS
* made this VM a standalone MAAS

After installation finishes the VM reboots, and the remote console in
virt-manager remains black, or displays garbage. I can log in via ssh
tho.

Trying the same with a vanilla Ubuntu Server install works, I get a
functional remote console in virt-manager.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: maas 1.7.3+bzr3363-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sat Jul 11 06:43:31 2015
InstallationDate: Installed on 2015-07-11 (0 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473625

Title:
  Installing MAAS using 15.04 server ISO (amd64) on remote machine via
  virt-manager results in black screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1473625/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1473625] [NEW] Installing MAAS using 15.04 server ISO (amd64) on remote machine via virt-manager results in black screen

[Alexander List]

Public bug reported:

What I did:

* Set up a box as VM host for manually provisioned VMs (using ssh and 
virt-manager)
* Created a new VM using the 15.04 server ISO (amd64)
* Select multiple host install using MAAS
* made this VM a standalone MAAS

After installation finishes the VM reboots, and the remote console in
virt-manager remains black, or displays garbage. I can log in via ssh
tho.

Trying the same with a vanilla Ubuntu Server install works, I get a
functional remote console in virt-manager.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: maas 1.7.3+bzr3363-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sat Jul 11 06:43:31 2015
InstallationDate: Installed on 2015-07-11 (0 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1473625

Title:
  Installing MAAS using 15.04 server ISO (amd64) on remote machine via
  virt-manager results in black screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1473625/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1473624] [NEW] Installing apport on headless vivid machine results in hanging systemd

[Alexander List]

Public bug reported:

I have installed ubuntu-15.04-server amd64 in a VM, selecting multiple
server install with MAAS (to set up a standalone MAAS) using virt-
manager.

Trying to report a bug, I installed apport.

This pulled in several dependencies, but ended up hanging at systemd
install:

http://pastebin.ubuntu.com/11859706/

Trying apt-get -f install didn't help either:

http://pastebin.ubuntu.com/11859710/

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Sat Jul 11 06:42:36 2015
InstallationDate: Installed on 2015-07-11 (0 days ago)
InstallationMedia: Ubuntu-Server 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1473624

Title:
  Installing apport on headless vivid machine results in hanging systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1473624/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445239] Re: apt's lists/partial fills disk

[Alexander List]

Brian,

I was using sg.archive.u.c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445239

Title:
  apt's lists/partial fills disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1445239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445239] Re: apt's lists/partial fills disk

[Alexander List]

Brian,

I've run across the same problem and have installed your package from
-proposed.

I will let you know after 2-3d if the problem resurfaces. If you don't
hear from me by the end of the week, consider the problem fixed for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445239

Title:
  apt's lists/partial fills disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1445239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1465506] Re: plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH

[Alexander List]

I have two identical screens connected, one via HDMI, one via DP

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465506

Title:
  plane A assertion failure (expected on, current off) on Intel NUC
  5i5RYH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1465506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1465506] [NEW] plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH

[Alexander List]

Public bug reported:

Getting assertion failures:

[ 9925.287975] WARNING: CPU: 3 PID: 7538 at 
/build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 
assert_plane.constprop.87+0x7b/0x90 [i
915]()
[ 9925.287976] plane A assertion failure (expected on, current off)

Around the same time, WiFi connections drop. I cannot prove the two
problems are related, but I don't have WiFi issues on other devices.

alex@nuc1-hkg:~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04

alex@nuc1-hkg:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.917-1~exp1ubuntu2.2
  Candidate: 2:2.99.917-1~exp1ubuntu2.2
  Version table:
 *** 2:2.99.917-1~exp1ubuntu2.2 0
500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2:2.99.917-1~exp1ubuntu2build1 0
500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

alex@nuc1-hkg:~$ apt-cache policy linux-image-generic 
linux-image-generic:
  Installed: 3.19.0.21.20
  Candidate: 3.19.0.21.20
  Version table:
 *** 3.19.0.21.20 0
500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.19.0.15.14 0
500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Jun 16 14:33:41 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2057]
InstallationDate: Installed on 2015-06-16 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2015
dmi.bios.vendor: Intel Corporation
dmi.bios.version: RYBDWi35.86A.0249.2015.0529.1640
dmi.board.name: NUC5i5RYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H40999-503
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0249.2015.0529.1640:bd05/29/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Jun 16 14:32:31 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   10103 
 vendor AOC
xserver.version: 2:1.17.1-0ubuntu3

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465506

Title:
  plane A assertion failure (expected on, current off) on Intel NUC
  5i5RYH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1465506/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Can we expect a fix for this anytime soon?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Can we expect a fix for this anytime soon?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1446126] [NEW] qemu-system-x86 crashes with Windows guest and lots of I/O pressure

[Alexander List]

Public bug reported:

Hardware HP DL380Gen9, 128GB RAM, 2 CPUs

Windows guest causing lots of I/O pressure caused qemu to crash.

$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04


ii  qemu-system-x86   2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (x86)


[151743.650896] INFO: task jbd2/dm-0-8:573 blocked for more than 120 seconds.
[151743.651338]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[151743.651745] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[151743.652279] jbd2/dm-0-8 D 88103fc130c0 0   573  2 0x
[151743.652286]  88102618bcb0 0046 8820244adbb0 
88102618bfd8
[151743.652291]  000130c0 000130c0 81c1a480 
88102618bd98
[151743.652295]  8810241150b8 8820244adbb0 88101a66eb00 
88102618bd80
[151743.652299] Call Trace:
[151743.652312]  [817689d9] schedule+0x29/0x70
[151743.652323]  [8129db99] 
jbd2_journal_commit_transaction+0x279/0x19b0
[151743.652332]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.652341]  [8107a69b] ? lock_timer_base.isra.34+0x2b/0x50
[151743.652346]  [812a29fb] kjournald2+0xbb/0x240
[151743.652350]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.652354]  [812a2940] ? commit_timeout+0x10/0x10
[151743.652361]  [81091332] kthread+0xd2/0xf0
[151743.652368]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.652374]  [8176c9bc] ret_from_fork+0x7c/0xb0
[151743.652379]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.652402] INFO: task kworker/u49:1:16585 blocked for more than 120 
seconds.
[151743.652839]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[151743.653255] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[151743.653741] kworker/u49:1   D 88103fd330c0 0 16585  2 0x
[151743.653754] Workqueue: writeback bdi_writeback_workfn (flush-252:0)
[151743.653757]  88001c5c3928 0046 880b9ed65bb0 
88001c5c3fd8
[151743.653761]  000130c0 000130c0 881029347010 
881024115000
[151743.653765]  881024115070 41be 0014 
88103f67b150
[151743.653769] Call Trace:
[151743.653773]  [817689d9] schedule+0x29/0x70
[151743.653778]  [8129aac9] wait_transaction_locked+0x79/0xa0
[151743.653783]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.653787]  [8129adf0] start_this_handle+0x280/0x5a0
[151743.653796]  [811b7642] ? kmem_cache_alloc+0x1b2/0x1e0
[151743.653800]  [8129b2b0] ? jbd2__journal_start+0x90/0x1e0
[151743.653805]  [8129b313] jbd2__journal_start+0xf3/0x1e0
[151743.653811]  [81257e9c] ? ext4_writepages+0x3ac/0xd00
[151743.653815]  [81282859] __ext4_journal_start_sb+0x69/0xe0
[151743.653818]  [81257e9c] ext4_writepages+0x3ac/0xd00
[151743.653825]  [8116c59d] ? generic_writepages+0x4d/0x60
[151743.653830]  [8116d6ee] do_writepages+0x1e/0x40
[151743.653834]  [811fc360] __writeback_single_inode+0x40/0x220
[151743.653838]  [811fce57] writeback_sb_inodes+0x247/0x3e0
[151743.653843]  [811fd08f] __writeback_inodes_wb+0x9f/0xd0
[151743.653847]  [811fd303] wb_writeback+0x243/0x2c0
[151743.653851]  [811ffa92] bdi_writeback_workfn+0x2a2/0x430
[151743.653856]  [8108a322] process_one_work+0x182/0x450
[151743.653859]  [8108aa91] worker_thread+0x121/0x570
[151743.653863]  [8108a970] ? rescuer_thread+0x380/0x380
[151743.653868]  [81091332] kthread+0xd2/0xf0
[151743.653872]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.653877]  [8176c9bc] ret_from_fork+0x7c/0xb0
[151743.653881]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[154982.430116] INFO: task jbd2/dm-0-8:573 blocked for more than 120 seconds.
[154982.430527]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[154982.430907] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[154982.431388] jbd2/dm-0-8 D 88103fc730c0 0   573  2 0x
[154982.431396]  88102618bcb0 0046 8820244adbb0 
88102618bfd8
[154982.431400]  000130c0 000130c0 8810292b7010 
88102618bd98
[154982.431404]  8810241150b8 8820244adbb0 88101e4c3900 
88102618bd80
[154982.431409] Call Trace:
[154982.431422]  [817689d9] schedule+0x29/0x70
[154982.431435]  [8129db99] 
jbd2_journal_commit_transaction+0x279/0x19b0
[154982.431446]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[154982.431456]  [8107a69b] ? lock_timer_base.isra.34+0x2b/0x50
[154982.431461]  [812a29fb] kjournald2+0xbb/0x240
[154982.431466]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[154982.431469]  [812a2940] 

[Bug 1446126] [NEW] qemu-system-x86 crashes with Windows guest and lots of I/O pressure

[Alexander List]

Public bug reported:

Hardware HP DL380Gen9, 128GB RAM, 2 CPUs

Windows guest causing lots of I/O pressure caused qemu to crash.

$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04


ii  qemu-system-x86   2.0.0+dfsg-2ubuntu1.10
amd64QEMU full system emulation binaries (x86)


[151743.650896] INFO: task jbd2/dm-0-8:573 blocked for more than 120 seconds.
[151743.651338]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[151743.651745] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[151743.652279] jbd2/dm-0-8 D 88103fc130c0 0   573  2 0x
[151743.652286]  88102618bcb0 0046 8820244adbb0 
88102618bfd8
[151743.652291]  000130c0 000130c0 81c1a480 
88102618bd98
[151743.652295]  8810241150b8 8820244adbb0 88101a66eb00 
88102618bd80
[151743.652299] Call Trace:
[151743.652312]  [817689d9] schedule+0x29/0x70
[151743.652323]  [8129db99] 
jbd2_journal_commit_transaction+0x279/0x19b0
[151743.652332]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.652341]  [8107a69b] ? lock_timer_base.isra.34+0x2b/0x50
[151743.652346]  [812a29fb] kjournald2+0xbb/0x240
[151743.652350]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.652354]  [812a2940] ? commit_timeout+0x10/0x10
[151743.652361]  [81091332] kthread+0xd2/0xf0
[151743.652368]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.652374]  [8176c9bc] ret_from_fork+0x7c/0xb0
[151743.652379]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.652402] INFO: task kworker/u49:1:16585 blocked for more than 120 
seconds.
[151743.652839]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[151743.653255] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[151743.653741] kworker/u49:1   D 88103fd330c0 0 16585  2 0x
[151743.653754] Workqueue: writeback bdi_writeback_workfn (flush-252:0)
[151743.653757]  88001c5c3928 0046 880b9ed65bb0 
88001c5c3fd8
[151743.653761]  000130c0 000130c0 881029347010 
881024115000
[151743.653765]  881024115070 41be 0014 
88103f67b150
[151743.653769] Call Trace:
[151743.653773]  [817689d9] schedule+0x29/0x70
[151743.653778]  [8129aac9] wait_transaction_locked+0x79/0xa0
[151743.653783]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[151743.653787]  [8129adf0] start_this_handle+0x280/0x5a0
[151743.653796]  [811b7642] ? kmem_cache_alloc+0x1b2/0x1e0
[151743.653800]  [8129b2b0] ? jbd2__journal_start+0x90/0x1e0
[151743.653805]  [8129b313] jbd2__journal_start+0xf3/0x1e0
[151743.653811]  [81257e9c] ? ext4_writepages+0x3ac/0xd00
[151743.653815]  [81282859] __ext4_journal_start_sb+0x69/0xe0
[151743.653818]  [81257e9c] ext4_writepages+0x3ac/0xd00
[151743.653825]  [8116c59d] ? generic_writepages+0x4d/0x60
[151743.653830]  [8116d6ee] do_writepages+0x1e/0x40
[151743.653834]  [811fc360] __writeback_single_inode+0x40/0x220
[151743.653838]  [811fce57] writeback_sb_inodes+0x247/0x3e0
[151743.653843]  [811fd08f] __writeback_inodes_wb+0x9f/0xd0
[151743.653847]  [811fd303] wb_writeback+0x243/0x2c0
[151743.653851]  [811ffa92] bdi_writeback_workfn+0x2a2/0x430
[151743.653856]  [8108a322] process_one_work+0x182/0x450
[151743.653859]  [8108aa91] worker_thread+0x121/0x570
[151743.653863]  [8108a970] ? rescuer_thread+0x380/0x380
[151743.653868]  [81091332] kthread+0xd2/0xf0
[151743.653872]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[151743.653877]  [8176c9bc] ret_from_fork+0x7c/0xb0
[151743.653881]  [81091260] ? kthread_create_on_node+0x1c0/0x1c0
[154982.430116] INFO: task jbd2/dm-0-8:573 blocked for more than 120 seconds.
[154982.430527]   Not tainted 3.16.0-34-generic #47~14.04.1-Ubuntu
[154982.430907] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[154982.431388] jbd2/dm-0-8 D 88103fc730c0 0   573  2 0x
[154982.431396]  88102618bcb0 0046 8820244adbb0 
88102618bfd8
[154982.431400]  000130c0 000130c0 8810292b7010 
88102618bd98
[154982.431404]  8810241150b8 8820244adbb0 88101e4c3900 
88102618bd80
[154982.431409] Call Trace:
[154982.431422]  [817689d9] schedule+0x29/0x70
[154982.431435]  [8129db99] 
jbd2_journal_commit_transaction+0x279/0x19b0
[154982.431446]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[154982.431456]  [8107a69b] ? lock_timer_base.isra.34+0x2b/0x50
[154982.431461]  [812a29fb] kjournald2+0xbb/0x240
[154982.431466]  [810b4d70] ? prepare_to_wait_event+0x100/0x100
[154982.431469]  [812a2940] 

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Result of running your foocheck script:

$ ./foocheck 
found: eth0
br-int: /sys/class/net/br-int 6a:8f:8a:ce:3a:49
br-tun: /sys/class/net/br-tun 6e:8b:75:17:c9:43
eth0: /sys/class/net/eth0 6c:ae:8b:6a:d8:08
eth1: /sys/class/net/eth1 6c:ae:8b:6a:d8:09
eth2: /sys/class/net/eth2 6c:ae:8b:6a:d8:0a
eth3: /sys/class/net/eth3 6c:ae:8b:6a:d8:0b
juju-br0: /sys/class/net/juju-br0 6c:ae:8b:6a:d8:08
lo: /sys/class/net/lo 00:00:00:00:00:00
ovs-system: /sys/class/net/ovs-system ea:54:ad:75:19:e0
virbr0: /sys/class/net/virbr0 22:86:16:42:6b:7e

(this system now has nova-compute deployed via MAAS)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1442112] Re: booting ppc64el with hwe-u kernel hangs in initrd

[Alexander List]

Result of running your foocheck script:

$ ./foocheck 
found: eth0
br-int: /sys/class/net/br-int 6a:8f:8a:ce:3a:49
br-tun: /sys/class/net/br-tun 6e:8b:75:17:c9:43
eth0: /sys/class/net/eth0 6c:ae:8b:6a:d8:08
eth1: /sys/class/net/eth1 6c:ae:8b:6a:d8:09
eth2: /sys/class/net/eth2 6c:ae:8b:6a:d8:0a
eth3: /sys/class/net/eth3 6c:ae:8b:6a:d8:0b
juju-br0: /sys/class/net/juju-br0 6c:ae:8b:6a:d8:08
lo: /sys/class/net/lo 00:00:00:00:00:00
ovs-system: /sys/class/net/ovs-system ea:54:ad:75:19:e0
virbr0: /sys/class/net/virbr0 22:86:16:42:6b:7e

(this system now has nova-compute deployed via MAAS)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1442112

Title:
  booting ppc64el with hwe-u kernel hangs in initrd

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1442112/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 989396] Re: Package keyboard-configuration post-installation script. Hang on /bin/setupcon --force --save for 10 min then killed

[Alexander List]

The hang in setupcon may be a red herring. I saw this on a machine (HP
DL160 Gen9) with a FakeRAID controller (HP Dynamic Smart Array B140i)
which isn't supported (yet).

I tried to install 14.04.2 LTS from USB media, and it got stuck at 76% (Running 
live-installer-console-setup).
After switching the controller to legacy SATA / AHCI mode, the install didn't 
hang anymore.

This may be caused by the controller interfering with writing to the
target disk during the install, but I have no evidence for that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989396

Title:
  Package keyboard-configuration  post-installation script. Hang on
  /bin/setupcon --force --save for 10 min then killed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/989396/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 776028] Re: cannot see remote screen during VNC server connection

[Alexander List]

I see the same problem using two machines running trusty amd64. However,
in my case the remote system was configured to prompt the user for
confirmation to allow incoming VNC connections. You may want to ensure
this is not the case.

The behaviour can be changed using vino-preferences, and then
restarting the session to make the change effective.

If you have SSH access to the remote user, you can connect using ssh -Y,
and run vino-preferences remotely via X forwarding.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776028

Title:
  cannot see remote screen during VNC server connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/vinagre/+bug/776028/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 924105] Re: integer out of range errors for fact_values

[Alexander List]

This happened again today.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/924105

Title:
  integer out of range errors for fact_values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/924105/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 924105] Re: integer out of range errors for fact_values

[Alexander List]

This happened again today.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924105

Title:
  integer out of range errors for fact_values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/924105/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1316404] Re: MAAS from cloud-tools-next on precise fails because python-amqp too new

[Alexander List]

*** This bug is a duplicate of bug 1329383 ***
https://bugs.launchpad.net/bugs/1329383

** This bug has been marked a duplicate of bug 1329383
   celery from 12.04+cloudarchive is incompatible with python-amqp from 
cloud-tools-next

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1316404

Title:
  MAAS from cloud-tools-next on precise fails because python-amqp too
  new

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1316404/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1316404] Re: MAAS from cloud-tools-next on precise fails because python-amqp too new

[Alexander List]

*** This bug is a duplicate of bug 1329383 ***
https://bugs.launchpad.net/bugs/1329383

** This bug has been marked a duplicate of bug 1329383
   celery from 12.04+cloudarchive is incompatible with python-amqp from 
cloud-tools-next

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316404

Title:
  MAAS from cloud-tools-next on precise fails because python-amqp too
  new

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1316404/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1331571] [NEW] Clicking Disconnect VPN is sometimes unresponsive

[Alexander List]

Public bug reported:

Sometimes when connected to a VPN, when I click Disconnect VPN,
nothing happens.

If I click a second time, it usually works.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager-openvpn 0.9.8.2-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 18 19:17:19 2014
InstallationDate: Installed on 2013-03-19 (456 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318)
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to trusty on 2014-03-04 (106 days ago)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331571

Title:
  Clicking Disconnect VPN is sometimes unresponsive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1331571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1274947] Re: juju lxc instances deployed via MAAS don't have resolvable hostnames

[Alexander List]

We also see this behaviour on LXC containers deployed to MAASified
machines where MAAS does *not* manage DHCP/DNS.

We are trying to smoosh OpenStack infra into LXC units on MAASified
machines for HA.

It is most visible with rabbitmq-server, which bails out on NXdomain for
the unit.

It's also reproducible by just trying to sudo:

ubuntu@juju-machine-5-lxc-25:~$ sudo -i
sudo: unable to resolve host juju-machine-5-lxc-25

What *could* help is to pre-allocate MACs for each LXC container, either
inside or outside MAAS doesn't really matter, and inject them into the
host machine via lxc.network.hwaddr, cf.
http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html

This would require that cloud-init/juju respect what they get from
DHCP/DNS in terms of hostname...

** Attachment added: rabbitmq-server charm hook error
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947/+attachment/4133307/+files/rabbitmq-server-error.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1274947

Title:
  juju lxc instances deployed via MAAS don't have resolvable hostnames

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1274947/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1331019] [NEW] allow setting fixed MAC addresses for juju created LXC containers

[Alexander List]

Public bug reported:

Our environment requires stable IP addresses for LXC containers deployed
to MAAS managed physical machines via juju.

We are smooshing OpenStack infrastructure components (glance, cinder,
rabbitmq-server, swift-proxy, ...) to 3 units each on 3 physical hosts
for HA.

HA enabled services using the hacluster charm require that we specify a
virtual IP via config, but the IP of an LXC container comes from a pool
no matter if MAAS is used for DHCP/DNS management or not. MAC addresses
are randomized by default as well, using /etc/lxc/default.conf on the
host machine.

I suggest allowing the MAC address to be pre-allocated via config, such
that IP and hostname can be pre-allocated via DHCP/DNS as well.

References:

http://manage.jujucharms.com/charms/trusty/hacluster
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947
http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html

$ lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04

juju-core version: 1.18.4
Target distro: trusty

** Affects: juju-core (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1331019

Title:
  allow setting fixed MAC addresses for juju created LXC containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1331019/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1274947] Re: juju lxc instances deployed via MAAS don't have resolvable hostnames

[Alexander List]

We also see this behaviour on LXC containers deployed to MAASified
machines where MAAS does *not* manage DHCP/DNS.

We are trying to smoosh OpenStack infra into LXC units on MAASified
machines for HA.

It is most visible with rabbitmq-server, which bails out on NXdomain for
the unit.

It's also reproducible by just trying to sudo:

ubuntu@juju-machine-5-lxc-25:~$ sudo -i
sudo: unable to resolve host juju-machine-5-lxc-25

What *could* help is to pre-allocate MACs for each LXC container, either
inside or outside MAAS doesn't really matter, and inject them into the
host machine via lxc.network.hwaddr, cf.
http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html

This would require that cloud-init/juju respect what they get from
DHCP/DNS in terms of hostname...

** Attachment added: rabbitmq-server charm hook error
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947/+attachment/4133307/+files/rabbitmq-server-error.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274947

Title:
  juju lxc instances deployed via MAAS don't have resolvable hostnames

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1274947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1331019] [NEW] allow setting fixed MAC addresses for juju created LXC containers

[Alexander List]

Public bug reported:

Our environment requires stable IP addresses for LXC containers deployed
to MAAS managed physical machines via juju.

We are smooshing OpenStack infrastructure components (glance, cinder,
rabbitmq-server, swift-proxy, ...) to 3 units each on 3 physical hosts
for HA.

HA enabled services using the hacluster charm require that we specify a
virtual IP via config, but the IP of an LXC container comes from a pool
no matter if MAAS is used for DHCP/DNS management or not. MAC addresses
are randomized by default as well, using /etc/lxc/default.conf on the
host machine.

I suggest allowing the MAC address to be pre-allocated via config, such
that IP and hostname can be pre-allocated via DHCP/DNS as well.

References:

http://manage.jujucharms.com/charms/trusty/hacluster
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947
http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html

$ lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04

juju-core version: 1.18.4
Target distro: trusty

** Affects: juju-core (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/1331019

Title:
  allow setting fixed MAC addresses for juju created LXC containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1331019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1306344] [NEW] hp-setup crashes when adding new printer because hp-sendfax is not found

[Alexander List]

Public bug reported:

I am trying to add a new printer (also for scanning and faxing), but
this fails because the setup routine for Marvell fax expects hp-sendfax,
which is not part of the installed package.

$ hp-setup

HP Linux Imaging and Printing System (ver. 3.14.3)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-13 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Found device: hp:/net/HP_LaserJet_Professional_M1212nf_MFP?zc=laser
Traceback (most recent call last):
  File /usr/share/hplip/ui4/setupdialog.py, line 1237, in NextButton_clicked
self.showAddPrinterPage()
  File /usr/share/hplip/ui4/setupdialog.py, line 713, in showAddPrinterPage
self.readwriteFaxInformation()
  File /usr/share/hplip/ui4/setupdialog.py, line 1034, in 
readwriteFaxInformation
d = fax.getFaxDevice(self.fax_uri, disable_dbus=True)
  File /usr/share/hplip/fax/fax.py, line 533, in getFaxDevice
return MarvellFaxDevice(device_uri, printer_name, callback, fax_type, 
disable_dbus)
  File /usr/share/hplip/fax/marvellfax.py, line 90, in __init__
sendfax_a_path = os.readlink(sendfax_path+/hp-sendfax)
OSError: [Errno 2] No such file or directory: '/hp-sendfax'
Traceback (most recent call last):
  File /usr/share/hplip/ui4/setupdialog.py, line 1237, in NextButton_clicked
self.showAddPrinterPage()
  File /usr/share/hplip/ui4/setupdialog.py, line 713, in showAddPrinterPage
self.readwriteFaxInformation()
  File /usr/share/hplip/ui4/setupdialog.py, line 1034, in 
readwriteFaxInformation
d = fax.getFaxDevice(self.fax_uri, disable_dbus=True)
  File /usr/share/hplip/fax/fax.py, line 533, in getFaxDevice
return MarvellFaxDevice(device_uri, printer_name, callback, fax_type, 
disable_dbus)
  File /usr/share/hplip/fax/marvellfax.py, line 90, in __init__
sendfax_a_path = os.readlink(sendfax_path+/hp-sendfax)
OSError: [Errno 2] No such file or directory: '/hp-sendfax'

alex@thinkpad:~$ apt-cache policy hplip
hplip:
  Installed: 3.14.3-0ubuntu3
  Candidate: 3.14.3-0ubuntu3
  Version table:
 *** 3.14.3-0ubuntu3 0
500 http://tw.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: hplip 3.14.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 11 11:06:56 2014
InstallationDate: Installed on 2013-03-19 (387 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318)
MachineType: LENOVO 3626A14
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
SourcePackage: hplip
UpgradeStatus: Upgraded to trusty on 2014-03-04 (37 days ago)
dmi.bios.date: 04/26/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET69WW (1.39 )
dmi.board.name: 3626A14
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET69WW(1.39):bd04/26/2012:svnLENOVO:pn3626A14:pvrThinkPadX201:rvnLENOVO:rn3626A14:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3626A14
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

** Affects: hplip (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306344

Title:
  hp-setup crashes when adding new printer because hp-sendfax is not
  found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1306344/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs