[Bug 2067501] Re: Ubuntu noble is missing libaio.so.1 compat symlink

[Sascha Lucas]

I totally disagree with "something needs to be rebuilt in order to pick
up the changes". The Debian maintainer made clear, that the change in
SONAME is temporary for Debian testing and would never make it into the
next Debian release.

Only because Ubuntu is a random snapshot of Debian testing, it now has
to deal on its own, how to resolve the SONAME change.

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

Title:
  Ubuntu noble is missing libaio.so.1 compat symlink

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


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

[Bug 2067501] Re: Ubuntu noble is missing libaio.so.1 compat symlink

[Sascha Lucas]

The Debian Maintainer said[1]:

"In the Debian context this was intended to be a temporary
non-intrusive solution that would not stomp over upstream, until this
had been agreed with them. My intention has always been to revert the
local SONAME bump before the next Debian release. Ubuntu will have to
deal with this however best they see fit."

I'm hereby marking this bug to Confirmed in Ubuntu.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072471#10

** Changed in: libaio (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/2067501

Title:
  Ubuntu noble is missing libaio.so.1 compat symlink

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


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

[Bug 2063926] [NEW] Wireless connection lost after vpnc-disconnect

[Sascha Stieglitz]

Public bug reported:

How to reproduce

Create a wireless Internet connection
Open a browser, make sure you have Internet access

Install and configure vpnc
connect to VPN via "sudo vpnc"

Check in browser if you still have access to Internet, you should
Now disconnect from VPN by running "sudo vpnc-disconnect"

Reload the current page in Browser

Expected
You still have access to Internet, the page reloads

What actually happens
You won't have access to Internet anymore, the page does not reload (even 
though the Wireless Icon looks like as if you are still connected)

You can fix this by deactivating and activating the wireless connection
again.

Further Info
In Xubuntu 24, where this happens too, a message appears that the Network has 
been disconnected after running the vpnc-disconnect command

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: vpnc 0.5.3+git20220927-1build2
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 27 11:05:05 2024
InstallationDate: Installed on 2024-04-26 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: vpnc
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.vpnc.default.conf: [deleted]

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


** Tags: amd64 apport-bug noble 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/2063926

Title:
  Wireless connection lost after vpnc-disconnect

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


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

[Bug 2060967] [NEW] noble/rsync buffer overflow detected

[Sascha Lucas]

Public bug reported:

Hi,

running the following test case in a current (today/2024-04-11) Noble
install leads to a "buffer overflow detected":

$ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
*** buffer overflow detected ***: terminated
rsync: connection unexpectedly closed (11 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

Original use case for the above striped down rsync options is the
ansible module "synchronize".

ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Apr 11 14:38:46 2024
Dependencies:
 gcc-14-base 14-20240330-1ubuntu2
 init-system-helpers 1.66ubuntu1
 libacl1 2.3.2-1
 libc6 2.39-0ubuntu8
 libgcc-s1 14-20240330-1ubuntu2
 libidn2-0 2.3.7-2
 liblz4-1 1.9.4-1
 libpopt0 1.19+dfsg-1
 libunistring5 1.1-2
 libxxhash0 0.8.2-2
 libzstd1 1.5.5+dfsg2-2
 lsb-base 11.6
 sysvinit-utils 3.08-6ubuntu2
 zlib1g 1:1.3.dfsg-3.1ubuntu2
DistroRelease: Ubuntu 24.04
Package: rsync 3.2.7-1build2
PackageArchitecture: amd64
ProcCpuinfoMinimal:
 processor  : 0
 vendor_id  : GenuineIntel
 cpu family : 6
 model  : 60
 model name : Intel Core Processor (Haswell, no TSX, IBRS)
 stepping   : 1
 microcode  : 0x1
 cpu MHz: 2397.222
 cache size : 16384 KB
 physical id: 0
 siblings   : 1
 core id: 0
 cpu cores  : 1
 apicid : 0
 initial apicid : 0
 fpu: yes
 fpu_exception  : yes
 cpuid level: 13
 wp : yes
 flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good 
nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 
sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
 bugs   : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
 bogomips   : 4794.44
 clflush size   : 64
 cache_alignment: 64
 address sizes  : 40 bits physical, 48 bits virtual
 power management:
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
SourcePackage: rsync
Tags: noble
Uname: Linux 6.8.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True

** Affects: rsync (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/2060967

Title:
  noble/rsync buffer overflow detected

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


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

[Bug 2055802] [NEW] package grub-efi-arm64-signed 1.201+2.12-1ubuntu1 failed to install/upgrade

[Sascha Greuel]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu Noble Numbat (development branch)
Release:24.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

grub-efi-arm64:
  Installed: 2.12-1ubuntu1
  Candidate: 2.12-1ubuntu1
  Version table:
 *** 2.12-1ubuntu1 500
500 http://mirror.hetzner.de/ubuntu/packages noble/main arm64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen

Successful upgrade

4) What happened instead

package grub-efi-arm64-signed 1.201+2.12-1ubuntu1 failed to
install/upgrade: installed grub-efi-arm64-signed package post-
installation script subprocess returned error exit status 10

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: grub-efi-arm64-signed 1.201+2.12-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic aarch64
ApportVersion: 2.28.0-0ubuntu1
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: hetzner
CloudName: hetzner
CloudPlatform: hetzner
CloudSubPlatform: metadata (http://169.254.169.254/hetzner/v1/metadata)
Date: Sun Mar  3 05:46:47 2024
DuplicateSignature:
 package:grub-efi-arm64-signed:1.201+2.12-1ubuntu1
 Setting up grub-efi-arm64-signed (1.201+2.12-1ubuntu1) ...
 dpkg: error processing package grub-efi-arm64-signed (--configure):
  installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 10
ErrorMessage: installed grub-efi-arm64-signed package post-installation script 
subprocess returned error exit status 10
Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.4ubuntu5
 apt  2.7.12
SourcePackage: grub2-signed
Title: package grub-efi-arm64-signed 1.201+2.12-1ubuntu1 failed to 
install/upgrade: installed grub-efi-arm64-signed package post-installation 
script subprocess returned error exit status 10
UpgradeStatus: Upgraded to noble on 2024-03-03 (0 days ago)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 noble

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

Title:
  package grub-efi-arm64-signed 1.201+2.12-1ubuntu1 failed to
  install/upgrade

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


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

[Bug 1937110] Re: dhcp option 121 & 249

[sascha arthur]

Funny thing is that the rfc 3442 is from 2002.

Thats what makes me wonder of the missing support till today...

My workarround till today is to unzip the iso -> kernel+initrd, patch
the initrd, and use the patched initrd.

I would not recommend anyone to do it like that, only if theres no other
options..

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

Title:
  dhcp option 121 & 249

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


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

[Bug 1969623] Re: Creation of SNMPv3 user broken (Jammy/22.04)

[Sascha Lucas]

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  Creation of SNMPv3 user broken (Jammy/22.04)

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


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

[Bug 1969623] Re: Creation of SNMPv3 user broken (Jammy/22.04)

[Sascha Lucas]

Hi,

I've testet snmpd-5.9.1+dfsg-1ubuntu2.1 from jammy-proposed. Creation of
SNMNPv3 user works now.

Thanks, Sascha.

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

Title:
  Creation of SNMPv3 user broken (Jammy/22.04)

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


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

[Bug 1969624] [NEW] kernel NULL pointer dereference while removing floppy module

[Sascha Lucas]

Public bug reported:

Kernel/Package is linux-image-5.15.0-25-generic

running:

$ modprobe -r floppy
Killed

ends in BUG: kernel NULL pointer dereference (see dmesg).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Apr 20 13:33 seq
 crw-rw 1 root audio 116, 33 Apr 20 13:33 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Wed Apr 20 13:50:56 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220330)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/system-root ro console=ttyS0,38400n8 elevator=noop 
net.ifnames=0
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.10.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-bionic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-bionic
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug jammy

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

Title:
  kernel NULL pointer dereference while removing floppy module

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


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

[Bug 1969623] [NEW] Creation of SNMPv3 user broken (Jammy/22.04)

[Sascha Lucas]

Public bug reported:

When creating a SNMPv3 user this error appears:

$ /usr/bin/net-snmp-config --create-snmpv3-user -ro -A MD5 -a XX -x Y 
-X DES Z
touch: cannot touch '/snmp/snmpd.conf': No such file or directory
/usr/bin/net-snmp-create-v3-user: 146: cannot create /snmp/snmpd.conf: 
Directory nonexistent

Looking at /usr/bin/net-snmp-create-v3-user line 146, it seems that
$outfile references ${datarootdir} in line 139, which is undefined.
Further outfile is already defined at line 121.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: snmpd 5.9.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Apr 20 13:34:44 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220330)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: net-snmp
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.snmp.snmpd.conf: [modified]
mtime.conffile..etc.snmp.snmpd.conf: 2022-04-20T12:50:27.596000

** Affects: net-snmp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Creation of SNMPv3 user broken (Jammy/22.04)

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


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

[Bug 1968550] Re: unattended updates, missing routes

[sascha arthur]

happened on jammy

** Changed in: frr (Ubuntu)
   Status: Incomplete => New

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

Title:
  unattended updates, missing routes

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


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

[Bug 1968550] [NEW] unattended updates, missing routes

[sascha arthur]

Public bug reported:

Hello,

It happened now twice for me that after a "unattended update" the linux
kernel is missing routes which were announced via BGP. From my point of
view, the problem is that networkd is restarted(?). Which leads to a
deletion of the routes in linux kernel.


# cat /var/log/unattended-upgrades/unattended-upgrades.log | grep "upgraded:"
2022-04-08 06:45:58,859 INFO Packages that will be upgraded: cloud-init dpkg 
libarchive13 liblzma5 libudisks2-0 libutempter0 linux-generic 
linux-headers-generic linux-image-generic patch tmux udisks2 
update-notifier-common xz-utils
2022-04-09 06:11:51,294 INFO Packages that will be upgraded: 
libboost-iostreams1.74.0 libboost-thread1.74.0 libudisks2-0 libx11-6 
libx11-data libx11-dev libx11-xcb1 ltrace python3-distutils python3-gdbm 
python3-lib2to3 udisks2 update-notifier-common
2022-04-10 06:09:12,653 INFO Packages that will be upgraded: gzip liblzma5 
libnss-mymachines libnss-systemd libpam-systemd libsystemd0 libudev1 systemd 
systemd-container systemd-sysv systemd-timesyncd udev update-notifier-common 
xz-utils
2022-04-11 06:26:31,366 INFO Packages that will be upgraded: libjpeg8 
update-notifier-common


# systemctl status frr
● frr.service - FRRouting
 Loaded: loaded (/lib/systemd/system/frr.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Fri 2022-04-08 02:00:16 UTC; 3 days ago

 
# systemctl status systemd-networkd.service 
● systemd-networkd.service - Network Configuration
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Sun 2022-04-10 06:09:17 UTC; 1 day 3h ago

# vtysh -c "show ip route" | grep "B>" 
B>* 10.3.0.0/16 [20/0] via 172.25.84.114, wg-1-dc-003, weight 1, 3d08h05m
B>* 10.4.0.0/16 [20/0] via 172.25.84.122, wg-1-dc-004, weight 1, 1d15h36m
B>* 172.20.0.0/16 [20/0] via 10.0.240.129, wg-1-int, weight 1, 3d08h05m

# ip route | grep /16
10.1.0.0/16 dev ethGeoInternal proto kernel scope link src 10.1.254.253 


As you can see 10.3.0.0/16 and 10.4.0.0/16 is missing in "ip route"

** Affects: frr (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/1968550

Title:
  unattended updates, missing routes

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


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

[Bug 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

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

** This bug has been marked a duplicate of bug 1967901
   [qxl] Xorg fails to start with "Screen(s) found, but none have a usable 
configuration."

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

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


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

[Bug 1968063] Re: Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

adding Xorg crash dump

** Attachment added: "Xorg crash dump"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1968063/+attachment/5577702/+files/_usr_lib_xorg_Xorg.126.crash

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

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


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

[Bug 1968063] [NEW] Jammy: Xorg crash on virtual QXL graphics

[Sascha Lucas]

Public bug reported:

Testing current beta of Ubuntu 22.04/Jammy with Xorg (Xubuntu): Xorg-
Server will not start. Either directly via lightdm or via gdm/wayland
selecting Xubuntu session.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  6 17:59:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
   Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=8e28ee89-1f52-43a1-a486-35d9454e77e2 ro console=ttyS0,115200n8 
elevator=noop net.ifnames=0 earlyprintk=ttyS0,115200n8
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-focal
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-focal:cvnQEMU:ct1:cvrpc-i440fx-focal:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-focal
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash jammy ubuntu

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

Title:
  Jammy: Xorg crash on virtual QXL graphics

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

A lot of trouble, traced it down.

So basicly the fix is working.

The reason was an 'old' not restarted daemon on another host.

Very confusing is that even an old daemon can break itself (which is
expected) AND the CLI tools on another host.  Which was not expected by
me and confused me hardly. Sorry for the report confusing.

Thanks for solving it.

Finally closed.

** Changed in: ceph (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

hey @chris.macnaughton,

Yes i restarted all daemons, rebooted even the whole machine. As you can
see in my console logs above. Having a cluster of +10 nodes, tried it on
multiple hosts.

It was working at some point, but now it seems fully broken again. Which
is.. weird.

The mgr-daemons are broken (especially this "balancer module" for
example) and the CLI tools like "ceph crash ls" / "ceph telemtry
status".

Wondering where this "not deterministic" factor is coming from. Some
dynamic loading of python..?

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

even after reboot / restart.. under random circumstances this bug comes
back.

~ # dpkg -l | grep ceph
ii  ceph-base 17.1.0-0ubuntu3
amd64common ceph daemon libraries and management tools
ii  ceph-common   17.1.0-0ubuntu3
amd64common utilities to mount and interact with a ceph storage cluster
ii  ceph-mds  17.1.0-0ubuntu3
amd64metadata server for the ceph distributed file system
ii  ceph-mgr  17.1.0-0ubuntu3
amd64manager for the ceph distributed file system
ii  ceph-mgr-modules-core 17.1.0-0ubuntu3
all  ceph manager modules which are always enabled
ii  ceph-mon  17.1.0-0ubuntu3
amd64monitor server for the ceph storage system
ii  ceph-osd  17.1.0-0ubuntu3
amd64OSD server for the ceph storage system
ii  ceph-volume   17.1.0-0ubuntu3
all  tool to facilidate OSD deployment
ii  libcephfs217.1.0-0ubuntu3
amd64Ceph distributed file system client library
ii  libsqlite3-mod-ceph   17.1.0-0ubuntu3
amd64SQLite3 VFS for Ceph
ii  python3-ceph-argparse 17.1.0-0ubuntu3
amd64Python 3 utility libraries for Ceph CLI
ii  python3-ceph-common   17.1.0-0ubuntu3
all  Python 3 utility libraries for Ceph
ii  python3-cephfs17.1.0-0ubuntu3
amd64Python 3 libraries for the Ceph libcephfs library

~ # uptime
 20:55:23 up 52 min,  2 users,  load average: 0.04, 0.13, 0.22

~ # ceph crash ls
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' 
formats

~ # ceph telemetry status
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' 
formats

any idea?

** Changed in: ceph (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

Uhm, interesting.. its maybe still fixed.

But it needs a reconnect of ssh/reboot after installing the new
packages..


** Changed in: ceph (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

~ # dpkg -l | grep ceph
ii  ceph-base 17.1.0-0ubuntu3
amd64common ceph daemon libraries and management tools
ii  ceph-common   17.1.0-0ubuntu3
amd64common utilities to mount and interact with a ceph storage cluster
ii  ceph-mds  17.1.0-0ubuntu3
amd64metadata server for the ceph distributed file system
ii  ceph-mgr  17.1.0-0ubuntu3
amd64manager for the ceph distributed file system
ii  ceph-mgr-modules-core 17.1.0-0ubuntu3
all  ceph manager modules which are always enabled
ii  ceph-mon  17.1.0-0ubuntu3
amd64monitor server for the ceph storage system
ii  ceph-osd  17.1.0-0ubuntu3
amd64OSD server for the ceph storage system
ii  ceph-volume   17.1.0-0ubuntu3
all  tool to facilidate OSD deployment
ii  libcephfs217.1.0-0ubuntu3
amd64Ceph distributed file system client library
ii  libsqlite3-mod-ceph   17.1.0-0ubuntu3
amd64SQLite3 VFS for Ceph
ii  python3-ceph-argparse 17.1.0-0ubuntu3
amd64Python 3 utility libraries for Ceph CLI
ii  python3-ceph-common   17.1.0-0ubuntu3
all  Python 3 utility libraries for Ceph
ii  python3-cephfs17.1.0-0ubuntu3
amd64Python 3 libraries for the Ceph libcephfs library


~ # ceph telemetry status
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' 
formats


Fix doesnt work

** Changed in: ceph (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

thanks @james-page, any ETA for the fix beeing on the apt mirros?

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

# ceph telemetry status
Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' 
formats

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

Module 'balancer' has failed: PY_SSIZE_T_CLEAN macro must be defined for
'#' formats

is affected as well.

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

Title:
  Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be
  defined for '#' formats

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


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

[Bug 1964322] [NEW] Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

[sascha arthur]

Public bug reported:

#ceph -s

...
health: HEALTH_ERR
Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
..


# dpkg -l | grep ceph
ii  ceph-base 17.1.0-0ubuntu1
amd64common ceph daemon libraries and management tools
ii  ceph-common   17.1.0-0ubuntu1
amd64common utilities to mount and interact with a ceph storage cluster
ii  ceph-mds  17.1.0-0ubuntu1
amd64metadata server for the ceph distributed file system
ii  ceph-mgr  17.1.0-0ubuntu1
amd64manager for the ceph distributed file system
ii  ceph-mgr-modules-core 17.1.0-0ubuntu1
all  ceph manager modules which are always enabled
ii  ceph-mon  17.1.0-0ubuntu1
amd64monitor server for the ceph storage system
ii  ceph-osd  17.1.0-0ubuntu1
amd64OSD server for the ceph storage system
ii  ceph-volume   17.1.0-0ubuntu1
all  tool to facilidate OSD deployment
ii  libcephfs217.1.0-0ubuntu1
amd64Ceph distributed file system client library
ii  libsqlite3-mod-ceph   17.1.0-0ubuntu1
amd64SQLite3 VFS for Ceph
ii  python3-ceph-argparse 17.1.0-0ubuntu1
amd64Python 3 utility libraries for Ceph CLI
ii  python3-ceph-common   17.1.0-0ubuntu1
all  Python 3 utility libraries for Ceph
ii  python3-cephfs17.1.0-0ubuntu1
amd64Python 3 libraries for the Ceph libcephfs library

# ls -alh /usr/bin/python3
lrwxrwxrwx 1 root root 10 Jan 13 16:58 /usr/bin/python3 -> python3.10

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
Codename:   jammy

2022-03-08T17:58:18.807+ 7f7734ff9640 -1 Traceback (most recent call last):
  File "/usr/share/ceph/mgr/devicehealth/module.py", line 338, in serve
if self.db_ready() and self.enable_monitoring:
  File "/usr/share/ceph/mgr/mgr_module.py", line 1189, in db_ready
return self.db is not None
  File "/usr/share/ceph/mgr/mgr_module.py", line 1201, in db
self._db = self.open_db()
  File "/usr/share/ceph/mgr/mgr_module.py", line 1178, in open_db
self.create_mgr_pool()
  File "/usr/share/ceph/mgr/mgr_module.py", line 1084, in create_mgr_pool
self.rename_pool(devhealth, self.MGR_POOL_NAME)
  File "/usr/share/ceph/mgr/mgr_module.py", line 1048, in rename_pool
self.check_mon_command(c)
  File "/usr/share/ceph/mgr/mgr_module.py", line 1560, in check_mon_command
r = HandleCommandResult(*self.mon_command(cmd_dict, inbuf))
  File "/usr/share/ceph/mgr/mgr_module.py", line 1577, in mon_command
self.send_command(result, "mon", "", json.dumps(cmd_dict), "", inbuf)
  File "/usr/share/ceph/mgr/mgr_module.py", line 1641, in send_command
self._ceph_send_command(result, svc_type, svc_id, command, tag, inbuf)
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

maybe bug fix here: https://github.com/ceph/ceph/pull/44112

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

** Description changed:

- health: HEALTH_ERR
- Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
+ #ceph -s
+ 
+ ...
+ health: HEALTH_ERR
+ Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be 
defined for '#' formats
+ ..
  
  
  # dpkg -l | grep ceph
  ii  ceph-base 17.1.0-0ubuntu1
amd64common ceph daemon libraries and management tools
  ii  ceph-common   17.1.0-0ubuntu1
amd64common utilities to mount and interact with a ceph storage cluster
  ii  ceph-mds  17.1.0-0ubuntu1
amd64metadata server for the ceph distributed file system
  ii  ceph-mgr  17.1.0-0ubuntu1
amd64manager for the ceph distributed file system
  ii  ceph-mgr-modules-core 17.1.0-0ubuntu1
all  ceph manager modules which are always enabled
  ii  ceph-mon  17.1.0-0ubuntu1
amd64monitor server for the ceph storage system
  ii  ceph-osd  17.1.0-0ubuntu1
amd64OSD server for the ceph storage system
  ii  ceph-volume   17.1.0-0ubuntu1
all  tool to facilidate OSD 

[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew

[sascha arthur]

sadly it didnt solve the issue.. heres more infos about:

https://tracker.ceph.com/issues/23460

sadly i didnt found a solution until now..


** Bug watch added: tracker.ceph.com/issues #23460
   http://tracker.ceph.com/issues/23460

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

Title:
  mgr crashs in 16.2.5 / clock-skew

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


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

[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew

[sascha arthur]

added following cron on top of ntpd, to see if this solves the issue:

0 * * * * /usr/sbin/hwclock -w --verbose --update-drift >>
/tmp/hwclock.log

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

Title:
  mgr crashs in 16.2.5 / clock-skew

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


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

[Bug 1943238] Re: memory requirements

[sascha arthur]

latest impish stable

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

Title:
  memory requirements

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


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

[Bug 1943729] [NEW] AMD impish Libvirt7.6 nested amd-v, rbd storage broken

[sascha arthur]

Public bug reported:

Hello,

Having issues with AMD and RBD Driver. Running on latest impish, using
libvirt7.6ubuntu1.

Having following setup (not sure if matters):

Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-
VM"=CVM

ubuntu20.04 -> impish -> custom

What happens?

It seems Level1-KVM is struggeling with RBD storage access,
breaking/preventing CVM's operating system to fully boot. Half of the
booting process is going through, but later at random point in time
(still booting the kernel) it seems to deadlock, letting CVM's CPU spin
endless.

Following tests setups i verified to isolate the issue:

Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through,
rbd=virtio) -> CVM = works

Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct
storage=virtio) -> CVM = works


Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) 
-> CVM = works

Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through,
rbd=virtio) -> CVM = works

Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct
storage=virtio) -> CVM = works


---

Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through,
rbd=virtio) -> CVM = stuck

Out of those tests, the issue seems to be IMO located in libvirt 7.6,
sadly im not able to check it against 7.4 (which was shortly available
for impish, but was already removed from the repo mirror..).

Any idears what could make an AMD passthrough break access of RBD,
letting CVM stuck accessing storage?

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

** Description changed:

  Hello,
  
- 
- Having issues with AMD and RBD Driver. Running on latest impish, using 
libvirt7.6ubuntu1.
+ Having issues with AMD and RBD Driver. Running on latest impish, using
+ libvirt7.6ubuntu1.
  
  Having following setup (not sure if matters):
  
  Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer-
  VM"=CVM
  
  ubuntu20.04 -> impish -> custom
  
  What happens?
  
  It seems Level1-KVM is struggeling with RBD storage access,
  breaking/preventing CVM's operating system to fully boot. Half of the
  booting process is going through, but later at random point in time
  (still booting the kernel) it seems to deadlock, letting CVM's CPU spin
  endless.
  
- 
  Following tests setups i verified to isolate the issue:
  
- Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, 
rbd=virtio) -> CVM = works
- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct 
storage=virtio) -> CVM = works
+ Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through,
+ rbd=virtio) -> CVM = works
+ 
+ Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct
+ storage=virtio) -> CVM = works
+ 
  
  Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) 
-> CVM = works
- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) 
-> CVM = works
- Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct 
storage=virtio) -> CVM = works
+ 
+ Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through,
+ rbd=virtio) -> CVM = works
+ 
+ Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct
+ storage=virtio) -> CVM = works
+ 
+ 
+ ---
  
  Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through,
  rbd=virtio) -> CVM = stuck
  
- 
- Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly 
im not able to check it against 7.4 (which was shortly available for impish, 
but was already removed from the repo mirror..).
+ Out of those tests, the issue seems to be IMO located in libvirt 7.6,
+ sadly im not able to check it against 7.4 (which was shortly available
+ for impish, but was already removed from the repo mirror..).
  
  Any idears what could make an AMD passthrough break access of RBD,
  letting CVM stuck accessing storage?

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

Title:
  AMD impish Libvirt7.6 nested amd-v, rbd storage broken

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


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

[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew

[sascha arthur]

Heres are the last lines when the MGR is running, but kicked out of the
cluster:

2021-09-14T00:00:42.062+ 7f05361b8640 -1 received  signal: Hangup from 
pkill -1 -x 
ceph-mon|ceph-mgr|ceph-mds|ceph-osd|ceph-fuse|radosgw|rbd-mirror|cephfs-mirror  
(PID: 1137578) UID: 0
2021-09-14T00:00:42.530+ 7f0526ffd640 -1 monclient: _check_auth_rotating 
possible clock skew, rotating keys expired way too early (before 
2021-09-13T23:00:42.534987+)
2021-09-14T00:00:43.530+ 7f0526ffd640 -1 monclient: _check_auth_rotating 
possible clock skew, rotating keys expired way too early (before 
2021-09-13T23:00:43.535155+)

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

Title:
  mgr crashs in 16.2.5 / clock-skew

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


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

[Bug 1943238] Re: memory requirements

[sascha arthur]

Thanks for this hint.

But im already using this Parameter in combination with ipxe.

Lowering to less then 3 GB  brings it sometimes to fail. Doing about
50-100 installs per week.

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

Title:
  memory requirements

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


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

[Bug 1943423] [NEW] mgr crashs in 16.2.5 / clock-skew

[sascha arthur]

Public bug reported:

Hello,

Running inside an KVM, impish with latest ceph version. 
Can at least reproduce it in 3 reinstalled fresh ceph clusters.

Heres the crash info for my mgr's:

ceph crash info
2021-09-12T21:09:22.866793Z_2419107c-082c-457a-b5e6-a376d779b32f

{
"archived": "2021-09-13 07:59:37.681606",
"backtrace": [
"/lib/x86_64-linux-gnu/libc.so.6(+0x46510) [0x7f62e074e510]",
"(std::_Rb_tree_increment(std::_Rb_tree_node_base*)+0x13) 
[0x7f62e0af5573]",
"(PGMap::apply_incremental(ceph::common::CephContext*, 
PGMap::Incremental const&)+0xb60) [0x5633639f6320]",
"(ClusterState::notify_osdmap(OSDMap const&)+0x29d) [0x563363a89f1d]",
"(Mgr::handle_osd_map()+0x854) [0x563363ae0694]",
"(Mgr::ms_dispatch2(boost::intrusive_ptr const&)+0x568) 
[0x563363ae0eb8]",
"(MgrStandby::ms_dispatch2(boost::intrusive_ptr const&)+0xb8) 
[0x563363af1118]",
"(Messenger::ms_deliver_dispatch(boost::intrusive_ptr 
const&)+0x450) [0x7f62e1101d30]",
"(DispatchQueue::entry()+0x647) [0x7f62e10ff0e7]",
"(DispatchQueue::DispatchThread::entry()+0x11) [0x7f62e11be921]",
"/lib/x86_64-linux-gnu/libc.so.6(+0x988d7) [0x7f62e07a08d7]",
"/lib/x86_64-linux-gnu/libc.so.6(+0x129510) [0x7f62e0831510]"
],
"ceph_version": "16.2.5",
"crash_id": 
"2021-09-12T21:09:22.866793Z_2419107c-082c-457a-b5e6-a376d779b32f",
"entity_name": "mgr.ceph-2",
"os_id": "21.10",
"os_name": "Ubuntu Impish Indri (development branch)",
"os_version": "21.10 (Impish Indri)",
"os_version_id": "21.10",
"process_name": "ceph-mgr",
"stack_sig": 
"eccaccb958ebf382237486176ce43b704db9b0ec4b004a7697e77140821e88e9",
"timestamp": "2021-09-12T21:09:22.866793Z",
"utsname_hostname": "ceph-2.dc-003.xxx",
"utsname_machine": "x86_64",
"utsname_release": "5.13.0-14-generic",
"utsname_sysname": "Linux",
"utsname_version": "#14-Ubuntu SMP Mon Aug 2 12:43:35 UTC 2021"
}


On top MGRs having sometimes "clock-skew" issues, even though the daemon is 
running its loosing connection and kicked out of the cluster. For sure Host and 
KVM is ntp synchronized.

Not sure if this "clock-skew" is related to this crash here, but will
post the log as soon as i have it again.

** Affects: ceph (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/1943423

Title:
  mgr crashs in 16.2.5 / clock-skew

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


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

[Bug 1943238] [NEW] memory requirements

[sascha arthur]

Public bug reported:

Hello,

Was running now multiple times into the issue that the minimum memory
requirements for the installer was not met. Processes got random killed
by kernel with OOM, leading to a very weird behavior of the installer.

My experience says that (in case of loading the installer iso into the
memory for example by using ipxe) the minimal requirements is about 3 GB
of RAM.

Can anybody confirm this? Maybe could the installer also check this and
denie/warn about the installation instead of dieing randomly?

** Affects: subiquity (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/1943238

Title:
  memory requirements

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


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

[Bug 1943125] Re: devscripts breaks apt

[sascha arthur]

** Also affects: apt (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/1943125

Title:
  devscripts breaks apt

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


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

[Bug 1943125] [NEW] devscripts breaks apt

[sascha arthur]

Public bug reported:

Hello,

devscripts package seem to break apt installs.

using following Dockerfile:

FROM ubuntu:impish

ENV DEBIAN_FRONTEND noninteractive

RUN apt-get update -qq && apt-get install -y nano
RUN apt-get update -qq && apt-get install -y devscripts
RUN apt-get update -qq && apt-get install -y htop


docker build -t test .

Will break installing "htop" with random post apt install errors:

E: Problem executing scripts APT::Update::Post-Invoke 'rm -f 
/var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin || true'
E: Sub-process returned an error code

Excluding devscripts package will solve the issue.

Any idears why devscripts is breaking apt?

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

** Description changed:

  Hello,
  
  devscripts package seem to break apt installs.
  
  using following Dockerfile:
  
  FROM ubuntu:impish
  
  ENV DEBIAN_FRONTEND noninteractive
  
- RUN apt-get update -qq && apt-get install -y nano && \
-   rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin && \
-   rm -rf /var/lib/apt/lists/* && \
-   rm -rf /tmp/*
- 
- RUN apt-get update -qq && apt-get install -y devscripts && \
-   rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin && \
-   rm -rf /var/lib/apt/lists/* && \
-   rm -rf /tmp/*
- 
- RUN apt-get update -qq && apt-get install -y htop && \
-   rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin && \
-   rm -rf /var/lib/apt/lists/* && \
-   rm -rf /tmp/*
+ RUN apt-get update -qq && apt-get install -y nano
+ RUN apt-get update -qq && apt-get install -y devscripts
+ RUN apt-get update -qq && apt-get install -y htop
  
  
  docker build -t test .
  
  Will break installing "htop" with random post apt install errors:
  
  E: Problem executing scripts APT::Update::Post-Invoke 'rm -f 
/var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin || true'
  E: Sub-process returned an error code
  
- 
  Excluding devscripts package will solve the issue.
  
- 
  Any idears why devscripts is breaking apt?

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

Title:
  devscripts breaks apt

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


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

[Bug 1937110] [NEW] dhcp option 121 & 249

[sascha arthur]

Public bug reported:

Hello,

I'm running into issues with subiquity on a cloud provider.  The cloud
provider is using an on-link L3 gateway.


His DHCP response looks like this:


OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
OPTION:  54 (  4) Server identifier 172.31.1.1
OPTION:  51 (  4) IP address leasetime  86400 (24h)
OPTION:   1 (  4) Subnet mask   255.255.255.255
OPTION:   3 (  4) Routers   172.31.1.1
OPTION:   6 ( 12) DNS server
OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
ac1f0101 ..
OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
ac1f0101 ..


Im booting the subiquity process with an patched ipxe 
(https://github.com/ipxe/ipxe/pull/104) like this:

#!ipxe
kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
initrd .../initrd
boot

initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

Sadly subiquity is stuck with a broken network (because of missing dhcp
option 121/249 support). It happens when its running the /init from the
kernel right after kernel is booted, i guess even before the subiquity
is started(?).

After further debugging, it looks like the provided kernel 5.4.80 #90
Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
dhclient-4.4.1 which is lacking the given options.


Would be awesome if this could be fixed.. maybe just a simple busybox compile 
option?

** Affects: subiquity
 Importance: Undecided
 Status: New

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

** Also affects: busybox (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/1937110

Title:
  dhcp option 121 & 249

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


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

[Bug 1909603] Re: fwupd-refresh.service: Failed with result 'exit-code'

[sascha arthur]

Its a bug in 1.3.* as you can read here:

https://github.com/fwupd/fwupd/issues/391#issuecomment-756941356

Also they dont want to bring an update for ubuntu 20.04 LTS as you can
read here:

https://github.com/fwupd/fwupd/issues/2708#issuecomment-758850957

Further information can also be found here:
https://github.com/fwupd/fwupd/issues/2532


Can someone explain why exactly this fwupd is installed on ubuntu 20.04 server 
editions? 

I see mostly consumer hardware in their list of provided firmwares:
https://cdn.fwupd.org/lvfs/devices/

On most servers thers prob. no advantage of having this daemon
running/failing especially when they dont want to bring stability to
their sofware used in LTS versions..

Im removing this daemon from my servers..

** Bug watch added: github.com/fwupd/fwupd/issues #391
   https://github.com/fwupd/fwupd/issues/391

** Bug watch added: github.com/fwupd/fwupd/issues #2708
   https://github.com/fwupd/fwupd/issues/2708

** Bug watch added: github.com/fwupd/fwupd/issues #2532
   https://github.com/fwupd/fwupd/issues/2532

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

Title:
  fwupd-refresh.service: Failed with result 'exit-code'

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

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

[Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons

[sascha arthur]

Thanks for beeing fully ignored..

Well see us on the next production outtake..

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

Title:
  [SRU] unattended-upgrade still restarts blacklisted daemons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions

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

[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

[sascha arthur]

Thanks @bryce for the detailed updates.

For us personally its the second time we run into a docker daemon
restart on production (including all container restarts).

The only reason why this time it got much more attention is that a bug
prevented a clean restart of the daemon, leaving containers offline.

This fact tells us that most of the people never noticed that their
containers were also during the last update restartet. (Which is fine
because mostly a short restart, for example of a webserver nobody would
notice)

This is also fine of most of our servers because they running
lightweight containers.

The only reason why we noticed it (this and last time) is that we
running heavy database containers (for example elasticsearch with couple
of TBs) which have a restart time of minutes instead of seconds.

Especially its critical (and loosing consistency) when containers of the
same kind get restarted at the same time.

All of this chain is triggered by the unattended updates. Thats why we
excluded the automatic updates for the docker package.

But this doesnt help if depending package updates still restarting the
docker daemon/containers.

Since the unattended package is still marked as 'wont-fix', and the
dependencies problem is explained above..

The only way to safely prevent docker daemon restarts is to fully
disable the whole unattended updates? Can someone confirm this?

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

Title:
  unattended-upgrade still restarts blacklisted daemons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions

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

[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons

[sascha arthur]

Sorry but im not really on your side here and it also doesnt really
solve the problem.

I added docker.io to the blacklist because i want to take care manually
about the upgrades, it should leave in any case this package alone.

Adding here dependencies (containerd) for the packages will never solve
the issue, also i have to maintain this list, because dependencies (at
least in theorie) could change over time.

Just to prevent docker.io from restart i have to add a huge set of
packages (out of the list here
https://packages.ubuntu.com/focal/docker.io) to prevent it from
updating.

On top i have to go through all of the first level packages, to check if
it has dependencies on the next level, because those could trigger a
restart of the first level package, which will chain on the package
which i try to prevent.

As far as i get it currently, if unattended-upgrades is not considering
dependencies of blacklisted packages, theres no way except building an
incredibly huge list of packages which you dont want to update, and
regulary recalculate this list, because of maybe changed dependencies..

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

Title:
  unattended-upgrade still restarts blacklisted daemons

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

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

[Bug 1906364] [NEW] unattended-upgrade still restarts blacklisted daemons

[sascha arthur]

Public bug reported:

Hello,

Today plenty of our systems running ubuntu 20.04 were restarting the
docker daemon, even if i blacklisted the docker package. Since docker
has an dependency on containerd thats the reason why it was restarted.
IMO the blacklist should also check the full tree of dependencies...
This should NOT happen!

>From the log you find:

2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2020-12-01 06:40:46,996 INFO All upgrades installed
2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):

Also this happened for us on plenty of our servers almost at the same
(why the unattended updates are not spread over time?), which destroyed
the second time an production environment.

This is not how unattended-upgraded should be, sadly this package lost
our trust and we disable it and schedule the 'unattended updates' now on
our own.

PS: Not to say that on some servers the docker daemon did not even
restart..

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hello,
  
  Today plenty of our systems running ubuntu 20.04 were restarting the
  docker daemon, even if i blacklisted the docker package. Since docker
  has an dependency on containerd thats the reason why it was restarted.
  IMO the blacklist should also check the full tree of dependencies...
  This should NOT happen!
  
  From the log you find:
  
  2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
  2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
  2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
  2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2020-12-01 06:40:46,996 INFO All upgrades installed
  2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
  2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):
  
- 
- Also this happened for us on plenty of our servers almost at the same (why 
the unattended updates are not spread over time?), which destroyed the second 
time an production environment.
+ Also this happened for us on plenty of our servers almost at the same
+ (why the unattended updates are not spread over time?), which destroyed
+ the second time an production environment.
  
  This is not how unattended-upgraded should be, sadly this package lost
  our trust and we disable it and schedule the 'unattended updates' now on
  our own.
+ 
+ PS: Not to say that on some servers the docker daemon did not even
+ restart..

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

Title:
  unattended-upgrade still restarts blacklisted daemons

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

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

[Bug 1883628] Re: xsane crashes after upgrade to 20.04

[Sascha Lucas]

+1 fresh install of Focal/20.04:

Nov 15 12:57:23 X kernel: [27480.682846] xsane[19674]: segfault at
7f79a2ea7000 ip 7f79b03062ed sp 7fffe45a9a20 error 6 in
libjpeg.so.8.2.2[7f79b02c8000+44000]

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

Title:
  xsane crashes after upgrade to 20.04

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

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

[Bug 1883025] Re: davfs2 unable to unmount: segfault error 4 in libc.so

[Sascha]

Fixed in Ubuntu 20.10 release - There is davfs2 1.6.0 in Repos.

davfs2 1.6.0 has fixed this issue

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

Title:
  davfs2 unable to unmount: segfault error 4 in libc.so

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

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

[Bug 1898473] [NEW] canonical-livepatch snap not working

[Sascha Möller]

Public bug reported:

I installed snap and canonical-livepatch on my Ubuntu 18.04 LTS Server.

When i pass:

canonical-livepatch enable [My-Key]

i get following output after a few seconds:

sh: echo: I/O error
child exited with status 1

Trying again:

sh: echo: I/O error
child exited with status 1: File exists

Re installation of the snap is not working, also not resetting the
machine-id.

lsb_release -rd:

Description:Ubuntu 18.04.5 LTS
Release:18.04

snap info canonical-livepatch:

name:  canonical-livepatch
summary:   Canonical Livepatch Client
publisher: Canonical✓
store-url: https://snapcraft.io/canonical-livepatch
contact:   sn...@canonical.com
license:   unset
description: |
  Canonical Livepatch Client
commands:
  - canonical-livepatch
services:
  canonical-livepatch.canonical-livepatchd: simple, enabled, inactive
snap-id:  b96UJ4vttpNhpbaCWctVzfduQcPwQ5wn
tracking: latest/stable
refresh-date: heute um 16:05 CEST
channels:
  latest/stable:9.5.5 2020-03-16 (95) 9MB -
  latest/candidate: ↑ 
  latest/beta:  ↑ 
  latest/edge:  9.5.5 2020-03-16 (95) 9MB -
installed:  9.5.5(95) 9MB -

** Affects: 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/1898473

Title:
  canonical-livepatch snap not working

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

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

[Bug 1883957] [NEW] socat-1.7.3.3 (focal) termios options incorrectly applied to the second address

[Sascha Lucas]

Public bug reported:

Hi,

the socat version in Focal (1.7.3.3) breaks certain applications (i.e.
qemu serial console), when using raw mode or disabling echo (required
for serial consoles). Example: start socket in listening mode: "qemu-
system-x86_64 -serial unix:/tmp/socket,server", connect with socat:

/usr/bin/socat -ddd STDIO,raw,echo=0,escape=0x1d UNIX-CONNECT:/tmp/socket
2020/06/17 17:08:19 socat[26254] I setting option "raw"
2020/06/17 17:08:19 socat[26254] I setting option "echo" to 0
2020/06/17 17:08:19 socat[26254] I setting option "escape" to 29
2020/06/17 17:08:19 socat[26254] N reading from and writing to stdio
2020/06/17 17:08:19 socat[26254] N opening connection to AF=1 "/tmp/socket"
2020/06/17 17:08:19 socat[26254] I socket(1, 1, 0) -> 5
2020/06/17 17:08:19 socat[26254] E tcsetattr(5, TCSADRAIN, 0x556ef9be59c0): 
Inappropriate ioctl for device
2020/06/17 17:08:19 socat[26254] N exit(1)
2020/06/17 17:08:19 socat[26254] I shutdown(5, 2)

According to the Changelog from socat-1.7.3.4[1] this is a know problem
(Under certain circumstances, termios options of the first address were
applied to the second address, resulting in error "Inappropriate ioctl
for device"). The upstream commit[2] fixes this issue (also released in
socat-1.7.3.4).

Thanks, Sascha.

[1] http://www.dest-unreach.org/socat/doc/CHANGES
[2] https://repo.or.cz/socat.git/commit/5ebf36038f3960798e769bff5646e755a91a1119

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

** Summary changed:

- socat-1.7.3.3 (focal) termios options incorrecty applied to the second address
+ socat-1.7.3.3 (focal) termios options incorrectly applied to the second 
address

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

Title:
  socat-1.7.3.3 (focal) termios options incorrectly applied to the
  second address

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

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

[Bug 1883025] Re: davfs2 unable to unmount: segfault error 4 in libc.so

[Sascha]

** Description changed:

  I am getting segfaults everytime I want to unmount my webdav online-
  space (segfault error 4).
  
  Hardware failure is impossible as I see - because error already reported on 
project page (and fixed).
  Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 
on ubuntu repos ?) :)
  
  See (line 4-6):
  
http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156=markup=MAIN
  
  See 2:
  https://savannah.nongnu.org/bugs/?func=detailitem_id=56286#options
+ 
+ EDIT: Using Ubuntu 20.04 x64

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

Title:
  davfs2 unable to unmount: segfault error 4 in libc.so

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

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

[Bug 1883025] [NEW] davfs2 unable to unmount: segfault error 4 in libc.so

[Sascha Möritz]

Public bug reported:

I am getting segfaults everytime I want to unmount my webdav online-
space (segfault error 4).

Hardware failure is impossible as I see - because error already reported on 
project page (and fixed).
Error should be fixed in davfs 1.5.6 (Maybe easiest to bump to version 1.5.6 on 
ubuntu repos ?) :)

See (line 4-6):
http://cvs.savannah.nongnu.org/viewvc/davfs2/davfs2/ChangeLog?revision=1.156=markup=MAIN

See 2:
https://savannah.nongnu.org/bugs/?func=detailitem_id=56286#options

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


** Tags: davfs segfault unmount

** Package changed: linphone (Ubuntu) => davfs2 (Ubuntu)

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

Title:
  davfs2 unable to unmount: segfault error 4 in libc.so

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

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

[Bug 1876957] Re: Symbolic link 'pyvenv' is bloken

[Sascha Lucas]

probably just an packaging issue? pyvenv is officially removed in
python-3.8[1], so the symlink pyvenv should no longer be created?

[1] https://docs.python.org/dev/whatsnew/3.8.html#api-and-feature-
removals

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

Title:
  Symbolic link 'pyvenv' is bloken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1876957/+subscriptions

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

[Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent

[sascha arthur]

This crap here drives me crazy.

Im having this on an apt-installation of "redis-server".

Ubuntu 18.04

systemctl / networkctl all clean.
kernel is not booted with console parameters (also with console parameters 
doesnt work)

I tried like everything, even replacing this stupid ..
/bin/systemd-tty-ask-password-agent with /bin/true

Im running everything as root to avoid permission issues and theres no
fucking way to bypass this stupid /bin/systemd-tty-ask-password-agent

Im currently having NO WAY to install anything on the system because its
stuck on this stupid process...

Fucking get rid of this shit or bring a solution to enter the password.

Already spend 2 hours on it.

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

Title:
  restarting services hangs on systemd-tty-ask-password-agent

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

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

[Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks

[Sascha R.]

Same issue with Ubuntu 19.04 on Lenovo X1 Extreme (i7 6 core, Nvidia GPU with 
NVIDIA drivers).
Notebook gets warm/drains battery when in standby.
Log looks like some suspend tasks continue after waking up from standby.

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

Title:
  Battery drain during sleep. System suspended before kernel suspends
  all tasks

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

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

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

[Sascha Silbe]

Dimitri John Ledkov (xnox) wrote on 2019-06-19:
> Have you tried openssl 1.1.1-1ubuntu2.1~18.04.3 from bionic proposed?

I can confirm that 1.1.1-1ubuntu2.1~18.04.3 (already released a couple
of days ago) fixes the issue. Thanks a lot!

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwww-perl/+bug/1797386/+subscriptions

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

[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

[Sascha Silbe]

This update breaks salt-ssh 2016.11.2 (started from a different computer
that's running Debian Stretch) on Ubuntu 18.04 (running on the machine
being managed). Having Salt break from one day to the next for managing
an LTS (!) release is a rather major PITA.

Curiously enough, salt-ssh 2016.11.2 continues to work just fine on
minions running Ubuntu 19.04 which ships openssl 1.1.1b-1ubuntu2.1. So
whatever this SRU does apparently is different from how it works on
Ubuntu 19.04.

This is the error message (from salt-ssh):

=== Begin ===
Traceback (most recent call last):
  File "/var/tmp/.root_bdab0e_salt/salt-call", line 15, in 
salt_call()
  File "/var/tmp/.root_bdab0e_salt/py2/salt/scripts.py", line 374, in 
salt_call
import salt.cli.call
  File "/var/tmp/.root_bdab0e_salt/py2/salt/cli/call.py", line 9, in 

import salt.cli.caller
  File "/var/tmp/.root_bdab0e_salt/py2/salt/cli/caller.py", line 18, in 

import salt.loader
  File "/var/tmp/.root_bdab0e_salt/py2/salt/loader.py", line 29, in 

import salt.utils.event
  File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/event.py", line 72, 
in 
import salt.payload
  File "/var/tmp/.root_bdab0e_salt/py2/salt/payload.py", line 17, in 

import salt.crypt
  File "/var/tmp/.root_bdab0e_salt/py2/salt/crypt.py", line 43, in 

import salt.utils.rsax931
  File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/rsax931.py", line 83, 
in 
libcrypto = _init_libcrypto()
  File "/var/tmp/.root_bdab0e_salt/py2/salt/utils/rsax931.py", line 74, 
in _init_libcrypto
raise OSError("Failed to initialize OpenSSL library 
(OPENSSL_init_crypto failed)")
OSError: Failed to initialize OpenSSL library (OPENSSL_init_crypto 
failed)
=== End ===

I was able to narrow it down to ssl.create_default_context() (invoked by
tornado.netutil which salt-ssh imports indirectly via tornado.iostream)
causing OPENSSL_init_crypto() to return 0 (error) on Ubuntu 18.04, but 1
(success) on Ubuntu 19.04.

=== Begin Ubuntu 18.04 ===
root@bob:~# PYTHONPATH=/var/tmp/.root_bdab0e_salt/py2 python 
Python 2.7.15+ (default, Nov 27 2018, 23:36:35) 
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>> _client_ssl_defaults = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
[ctypes setup for libcrypto]
>>> libcrypto.OPENSSL_init_crypto(OPENSSL_INIT_NO_LOAD_CONFIG |
...  OPENSSL_INIT_ADD_ALL_CIPHERS |
...  OPENSSL_INIT_ADD_ALL_DIGESTS, None)
0
>>> 
=== End Ubuntu 18.04 ===


=== Begin Ubuntu 19.04 ===
root@bob:~# PYTHONPATH=/var/tmp/.root_bdab0e_salt/py2 python 
Python 2.7.15+ (default, Nov 27 2018, 23:36:35) 
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import ssl
>>> _client_ssl_defaults = ssl.create_default_context(ssl.Purpose.SERVER_AUTH)
[ctypes setup for libcrypto]
>>> libcrypto.OPENSSL_init_crypto(OPENSSL_INIT_NO_LOAD_CONFIG |
...  OPENSSL_INIT_ADD_ALL_CIPHERS |
...  OPENSSL_INIT_ADD_ALL_DIGESTS, None)
1
>>> 
=== End Ubuntu 19.04 ===

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwww-perl/+bug/1797386/+subscriptions

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

[Bug 1826459] Re: systemd-networkd not installing GatewayOnlink=true

[sascha arthur]

heres btw the netplan config im using:

network:
  version: 2
  renderer: networkd
  ethernets:
enp0s31f6:
  addresses: [ 95.216.96.148/26 ]
  gateway4: 95.216.96.129
  nameservers:
  addresses:
  - "8.8.8.8"
  - "1.1.1.1"
  routes:
  - to: 95.216.96.128/26
via: 95.216.96.129
on-link: true

if im modifing routes to

  routes:
  - to: 95.216.96.150/32
via: 95.216.96.129
on-link: true

it works out for 150, (but well in this case i need to add plenty of
routes..)

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

Title:
  systemd-networkd not installing GatewayOnlink=true

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

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

[Bug 1826459] Re: systemd-networkd not installing GatewayOnlink=true

[sascha arthur]

** Changed in: netplan
   Status: Invalid => New

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

** Changed in: systemd (Ubuntu)
   Status: Opinion => New

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

Title:
  systemd-networkd not installing GatewayOnlink=true

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

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

[Bug 1826459] Re: systemd-networkd not installing GatewayOnlink=true

[sascha arthur]

Hello,

Sorry for the late response and please reopen it.

The issue happens in a DMZ.

We have two servers in 95.216.96.128/26 with ip 95.216.96.149 and
95.216.96.150, normally we are able to reach those servers directly
(cause they are in the same subnet).

Sadly our hosting provider forbids direct communication between 149 and
150 (DMZ), thats why we added in the past (ubuntu 16.04) the "via"
statement, because all communication needs to go over  95.216.96.129.

Sadly netplan / systemd doesnt support / add this route, thats why our
internal communcation currently is broken.

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

Title:
  systemd-networkd not installing GatewayOnlink=true

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

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

[Bug 1743200] Re: No support for interface labels

[sascha arthur]

yes please also need it :((

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

Title:
  No support for interface labels

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

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

[Bug 1826459] Re: systemd-networkd not installing GatewayOnlink=true

[sascha arthur]

heres also the netplan file for it:

root@search-3 /run/systemd/network # netplan --debug apply
** (generate:22984): DEBUG: 21:03:47.073: Processing input file 
/etc/netplan/01-netcfg.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: Processing input file 
/etc/netplan/02-vlan.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: Processing input file 
/etc/netplan/03-gw.yaml..
** (generate:22984): DEBUG: 21:03:47.073: starting new processing pass
** (generate:22984): DEBUG: 21:03:47.073: vlan4000: setting default backend to 1
** (generate:22984): DEBUG: 21:03:47.073: enp0s31f6: setting default backend to 
1
** (generate:22984): DEBUG: 21:03:47.073: Generating output files..
** (generate:22984): DEBUG: 21:03:47.073: NetworkManager: definition vlan4000 
is not for us (backend 1)
** (generate:22984): DEBUG: 21:03:47.073: NetworkManager: definition enp0s31f6 
is not for us (backend 1)
DEBUG:netplan generated networkd configuration exists, restarting networkd
DEBUG:no netplan generated NM configuration exists
DEBUG:enp0s31f6 not found in {}
DEBUG:vlan4000 not found in {}
DEBUG:enp0s31f6 exists in {'enp0s31f6': {'addresses': ['95.216.96.148/26'], 
'gateway4': '95.216.96.129', 'nameservers': {'search': 
['148.96.216.95.clients.your-server.de'], 'addresses': ['8.8.8.8', '1.1.1.1']}}}
DEBUG:Merged config:
network:
  bonds: {}
  bridges: {}
  ethernets:
enp0s31f6:
  addresses:
  - 95.216.96.148/26
  gateway4: 95.216.96.129
  nameservers:
addresses:
- 8.8.8.8
- 1.1.1.1
search:
- 148.96.216.95.clients.your-server.de
  routes:
  - on-link: true
to: 95.216.96.148/26
via: 95.216.96.129
  vlans:
vlan4000:
  addresses:
  - 10.0.2.3/24
  dhcp4: false
  id: 4000
  link: enp0s31f6
  mtu: 1400
  wifis: {}

DEBUG:Skipping non-physical interface: lo
DEBUG:device enp0s31f6 operstate is up, not changing
DEBUG:Skipping non-physical interface: docker0
DEBUG:Skipping non-physical interface: br-c7cc901345e8
DEBUG:Skipping non-physical interface: vlan4000
DEBUG:Skipping non-physical interface: veth20a5a67
DEBUG:Skipping non-physical interface: tun0
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp0s31f6
DEBUG:netplan triggering .link rules for docker0
DEBUG:netplan triggering .link rules for br-c7cc901345e8
DEBUG:netplan triggering .link rules for vlan4000
DEBUG:netplan triggering .link rules for veth20a5a67
DEBUG:netplan triggering .link rules for tun0

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

Title:
  systemd-networkd not installing GatewayOnlink=true

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

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

[Bug 1826459] [NEW] systemd-networkd not installing GatewayOnlink=true

[sascha arthur]

Public bug reported:

root@search-3 /run/systemd/network # for i in *; do echo $i; echo; cat $i; done 
; sudo service systemd-networkd stop; SYSTEMD_LOG_LEVEL=debug 
/lib/systemd/systemd-networkd
10-netplan-enp0s31f6.network

[Match]
Name=enp0s31f6

[Network]
LinkLocalAddressing=ipv6
Address=95.216.96.148/26
Gateway=95.216.96.129
DNS=8.8.8.8
DNS=1.1.1.1
Domains=148.96.216.95.clients.your-server.de
VLAN=vlan4000

[Route]
Destination=95.216.96.148/26
Gateway=95.216.96.129
GatewayOnlink=true
10-netplan-vlan4000.netdev

[NetDev]
Name=vlan4000
MTUBytes=1400
Kind=vlan

[VLAN]
Id=4000
10-netplan-vlan4000.network

[Match]
Name=vlan4000

[Network]
LinkLocalAddressing=ipv6
Address=10.0.2.3/24
ConfigureWithoutCarrier=yes
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Failed to open configuration file '/etc/systemd/networkd.conf': No such file or 
directory
timestamp of '/etc/systemd/network' changed
timestamp of '/run/systemd/network' changed
Ignoring /run/systemd/network/10-netplan-enp0s31f6.network, because it's not a 
regular file with suffix .netdev.
Ignoring /run/systemd/network/10-netplan-vlan4000.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file 
with suffix .netdev.
Ignoring /lib/systemd/network/80-container-vz.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-ve.network, because it's not a 
regular file with suffix .netdev.
Ignoring /lib/systemd/network/80-container-host0.network, because it's not a 
regular file with suffix .netdev.
vlan4000: loaded vlan
Ignoring /run/systemd/network/10-netplan-vlan4000.netdev, because it's not a 
regular file with suffix .network.
Ignoring /lib/systemd/network/99-default.link, because it's not a regular file 
with suffix .network.
tun0: MAC address not found for new device, continuing without
tun0: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +POINTOPOINT +NOARP
tun0: Link 12 added
tun0: udev initialized link
tun0: Saved original MTU: 1500
veth20a5a67: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
veth20a5a67: Link 8 added
veth20a5a67: udev initialized link
veth20a5a67: Saved original MTU: 1500
vlan4000: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
vlan4000: Link 6 added
vlan4000: udev initialized link
vlan4000: netdev has index 6
vlan4000: Saved original MTU: 1400
br-c7cc901345e8: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
br-c7cc901345e8: Link 5 added
br-c7cc901345e8: udev initialized link
br-c7cc901345e8: Saved original MTU: 1500
docker0: Flags change: +UP +MULTICAST +BROADCAST
docker0: Link 3 added
docker0: udev initialized link
docker0: Saved original MTU: 1500
enp0s31f6: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
enp0s31f6: Link 2 added
enp0s31f6: udev initialized link
enp0s31f6: Saved original MTU: 1500
lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING
lo: Link 1 added
lo: udev initialized link
lo: Saved original MTU: 0
vlan4000: Adding address: fe80::921b:eff:fe93:5015/64 (valid forever)
vlan4000: Gained IPv6LL
tun0: Adding address: 10.0.0.13/24 (valid forever)
vlan4000: Adding address: 10.0.2.3/24 (valid forever)
br-c7cc901345e8: Adding address: 172.18.0.1/16 (valid forever)
docker0: Adding address: 172.17.0.1/16 (valid forever)
enp0s31f6: Adding address: 95.216.96.148/26 (valid forever)
lo: Adding address: 127.0.0.1/8 (valid forever)
rtnl: received address with invalid family 129, ignoring
Enumeration completed
Bus n/a: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 
reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName 
cookie=2 reply_cookie=0 signature=su error-name=n/a error-message=n/a
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=3 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_312 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=4 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_38 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=5 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Sent message type=signal sender=n/a destination=n/a 
path=/org/freedesktop/network1/link/_36 
interface=org.freedesktop.DBus.Properties 

[Bug 1820281] Re: Restarting systemd-networkd breaks keepalived clusters

[sascha arthur]

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

Heres a possible workaround until its solved (did not test it, but seems
valid): https://chr4.org/blog/2019/01/21/make-keepalived-play-nicely-
with-netplan-slash-systemd-network/

Personally i can live with 1-2 sek downtime (on network change), thats
why i added a subscribe hook in puppet to restart keepalived.

Will get rid of the workaround as soon as its solved, which is currently
hardly worked on it seems.

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

Title:
  Restarting systemd-networkd breaks keepalived clusters

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

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

[Bug 1820281] [NEW] Restarting systemd-networkd breaks keepalived clusters

[sascha arthur]

Public bug reported:

Hello,

Managing a HA floating IP with netplan and keepalived brings trouble.
Im managing a two node keepalived cluster with a floating IP. 
Everything works out except if i run on a the master node (which holds floating 
ip) "netplan apply".
Prob netplan resets the whole interface, leaving keepalived in a broken state.
This works without any trouble using the old iproute2 approach.

Even setting, net.ipv4.conf.*.promote_secondaries does not help out.

We need definitly an non strict reset option for interfaces in thise
case.

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

** Affects: netplan.io (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: systemd (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: keepalived netplan netplan-apply

** Summary changed:

- netplan, keepalived
+ netplan, keepalived, netplan-apply

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

Title:
  Restarting systemd-networkd breaks keepalived clusters

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

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

[Bug 1767703] [NEW] bootmanger

[Sascha]

Public bug reported:

i dont now.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 28 20:39:35 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu

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

Title:
  bootmanger

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

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

[Bug 1712573] Re: stenographer has regressed in artful-release on ppc64el

[Sascha Steinbiss]

Is this still relevant? Looks like the test failures have stopped now:

http://autopkgtest.ubuntu.com/packages/s/stenographer/artful/ppc64el

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

Title:
  stenographer has regressed in artful-release on ppc64el

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

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

[Bug 1749790] Re: ganeti: bionic proposed to release: bigger autopkgtest-VM

[Sascha Lucas]

According to https://irclogs.ubuntu.com/2018/02/21/%23ubuntu-devel.html
Laney managed to set a bigger test-VM. The test for i.e. amd64 are now
passed. The reason why the test fails i.e. for i386 is outside of the
scope of this bug.

I'm going to close this as solved.

Thanks, Sascha.

** Changed in: ganeti (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: ganeti (Ubuntu)
 Assignee: (unassigned) => Sascha Lucas (saschalucas)

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

Title:
  ganeti: bionic proposed to release: bigger autopkgtest-VM

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

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

[Bug 1749790] [NEW] ganeti: bionic proposed to release: bigger autopkgtest-VM

[Sascha Lucas]

Public bug reported:

Hi,

according to http://autopkgtest.ubuntu.com/packages/g/ganeti the
autopkgtests are failing for the upcoming bionic/18.04 release. The
reason can be found in the logs:

error type: insufficient_resources, error details:
Not enough memory on node node1 for creating instance instance1: needed 1024 
MiB, available 792 MiB

The reason is, that the autopkgtest-VM has per default 1536MB RAM. I've
verified, that the tests (debian/tests/vcluster-qa) succeed with 4GB
RAM.

We as the ganeti community are very interested to move ganeti from
proposed to release before bionic/18.04 gets released. Everything seems
fine, just a to small test-VM.

See also https://irclogs.ubuntu.com/2018/01/26/%23ubuntu-devel.html,
where Laney sad, that he will put ganeti on a small list of 'big'
packages. But this didn't happen, because the test still fails with "Not
enough memory" (2 times for amd64 since then: 2018-02-11 10:00:07 and
2018-02-05 15:13:30).

Thanks in advance, Sascha.

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

** Description changed:

  Hi,
  
  according to http://autopkgtest.ubuntu.com/packages/g/ganeti the
  autopkgtests are failing for the upcoming bionic/18.04 release. The
  reason can be found in the logs:
  
  error type: insufficient_resources, error details:
  Not enough memory on node node1 for creating instance instance1: needed 1024 
MiB, available 792 MiB
  
  The reason is, that the autopkgtest-VM has per default 1536MB RAM. I've
  verified, that the tests (debian/tests/vcluster-qa) succeed with 4GB
  RAM.
  
  We as the ganeti community are very interested to move ganeti from
  proposed to release before bionic/18.04 gets released. Everything seems
  fine, just a to small test-VM.
  
  See also https://irclogs.ubuntu.com/2018/01/26/%23ubuntu-devel.html,
- where Laney sad, that he will but ganeti on a small list of 'big'
+ where Laney sad, that he will put ganeti on a small list of 'big'
  packages. But this didn't happen, because the test still fails with "Not
  enough memory" (2 times for amd64 since then: 2018-02-11 10:00:07 and
  2018-02-05 15:13:30).
  
  Thanks in advance, Sascha.

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

Title:
  ganeti: bionic proposed to release: bigger autopkgtest-VM

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

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

[Bug 1739270] Re: Unable to connect to tor. Are you sure it's running?

[Sascha Steinbiss]

Confirmed -- most likely related to AppArmor, will continue to
investigate.

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

Title:
  Unable to connect to tor. Are you sure it's running?

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

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

[Bug 1718017] Re: gnome-games crashed with SIGSEGV

[Sascha Manns]

Added Valgrind Log

** Attachment added: "Valgrind Log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-games-app/+bug/1718017/+attachment/4952433/+files/valgrind.log

** Information type changed from Private to Public

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

Title:
  gnome-games crashed with SIGSEGV

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

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

[Bug 1656830] Re: Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

[Sascha]

** Summary changed:

- No DNS resolution caused by systemd-resolved
+ Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

Title:
  Ubuntu MATE 17.04: No DNS resolution caused by systemd-resolved

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

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

[Bug 1656830] [NEW] No DNS resolution caused by systemd-resolved

[Sascha]

Public bug reported:

This is something new in Ubuntu 17.04. Whenever I boot up or upon
returning from sleep, I don't have DNS resolution available. What I have
to do is go and shutdown systemd-resolved (sudo service systemd-resolved
stop) and edit /etc/resolv.conf to point to 192.168.1.1 (my router)
instead of 127.0.0.53. Then everything works peachy. Otherwise any DNS
resolution attempt will result in SERVFAIL.

Since this is a major issue out of the box and I don't see any other bug
report on this yet, I wanted to report it. This happens both on my
laptop and my desktop PC, so it's not something strange on a single
machine, but since no one else is complaining about it yet, it may be
related to my network configuration. My router forwards DNS requests to
an ODROID C2 on the same subnet, which then does the DNS resolution via
dnsmasq. Dnsqmasq is set up to forward the requests to multiple DNS
servers and respond with whichever one was fastest.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-8
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Jan 16 08:51:43 2017
InstallationDate: Installed on 2017-01-08 (7 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
MachineType: LENOVO 7675CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=b64995c7-1fd6-405b-b7ee-de3e56fe0617 ro quiet splash zswap.enabled=1 
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETC2WW (2.22 )
dmi.board.name: 7675CTO
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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn7675CTO:pvrThinkPadX61:rvnLENOVO:rn7675CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7675CTO
dmi.product.version: ThinkPad X61
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug zesty

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

Title:
  No DNS resolution caused by systemd-resolved

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

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

[Bug 1632322] Re: Computer never gets to the GDM3 login screen when nvidia- is installed

[Sascha]

Ubuntu 16.10, NVIDIA GTX 960, clean install (no upgrade)

Same here. After resolving the secure boot mess, I still cannot reach
the login screen when using the nvidia drivers. No problems with Nouveau
drivers (except for them being too slow).

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

Title:
  Computer never gets to the GDM3 login screen when nvidia- is installed

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

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

[Bug 351712]

[Sascha-zenglein]

still happens to me...

systemd-inhibit --list tells that PowerDevil has a block on all the
events, so I can't workaround this by setting
LidSwitchIgnoreInhibited=no in /etc/systemd/logind.conf

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

Title:
  KDE suspend to RAM when shutdown order has been given if laptop lid is
  closed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/351712/+subscriptions

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

[Bug 1619886] Re: keybard shortcuts stopped working for switching workspaces

[Sascha Peter]

Updating to 16.10 didn't solve.

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

Title:
  keybard shortcuts stopped working for switching workspaces

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

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

[Bug 1619886] [NEW] keybard shortcuts stopped working for switching workspaces

[Sascha Peter]

Public bug reported:

Since last time I updated my system, I can't switch between workspaces anymore 
using CTRL+ALT+arrows.
SUPER+S is still working fine, though.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160801.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep  3 12:29:34 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06df]
InstallationDate: Installed on 2016-06-13 (81 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 002: ID 1bcf:2b91 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E5570
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=104c23c8-f440-48a6-b8a0-99dd81d483e3 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.7
dmi.board.name: 0R3VX4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.7:bd03/14/2016:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0R3VX4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5570
dmi.sys.vendor: Dell Inc.
upstart.unity-panel-service.log:
 (unity-panel-service:3664): Indicator-Appmenu-WARNING **: Already have a menu 
for window ID 69206239 with path /com/canonical/menu/42000DF from :1.106, 
unregistering that one
 
 (unity-panel-service:3664): Indicator-Appmenu-WARNING **: Already have a menu 
for window ID 75497503 with path /com/canonical/menu/480001F from :1.112, 
unregistering that one
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Sep  3 12:03:31 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4589 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  keybard shortcuts stopped working for switching workspaces

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

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

[Bug 1079905] Re: mat puts unqualified module with common name in system path

[Sascha Steinbiss]

Closed as the described behaviour is no longer observed in recent
versions.

** Changed in: mat (Ubuntu)
   Status: New => Fix Released

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

Title:
  mat puts unqualified module with common name in system path

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

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

[Bug 1079905] Re: mat puts unqualified module with common name in system path

[Sascha Steinbiss]

This is apparently no longer the case, it's "libmat" in recent versions.
I guess this can be closed.

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

Title:
  mat puts unqualified module with common name in system path

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

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

[Bug 1566085] Re: Update to PHP7.0 build dependencies

[Sascha Steinbiss]

FYI: Applied to Debian as well, thanks!

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

Title:
  Update to PHP7.0 build dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/datatables.js/+bug/1566085/+subscriptions

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

[Bug 1563218] [NEW] Rhythmbox doesn't offer a menu anymore

[Sascha Biermanns]

Public bug reported:

Within the last two weeks, rhythmbox lost it's menu, so it's not
possible to access the plugins, settings or anything else, except you
know what the menu point was called - and press ALT, using the HUD to
access the settings or whatever.

Using the system menu to change, where the menu should be (window or top
panel) has no effect.


rhythmbox:
  Installiert:   3.3-1ubuntu6
  Installationskandidat: 3.3-1ubuntu6
  Versionstabelle:
 *** 3.3-1ubuntu6 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rhythmbox 3.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 29 10:02:29 2016
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2016-03-16 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
 LANGUAGE=de_DE
 XDG_RUNTIME_DIR=
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: rhythmbox (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/1563218

Title:
  Rhythmbox doesn't offer a menu anymore

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

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

[Bug 1561684] [NEW] unity launcher has no icons after returning from sleep mode

[Sascha Biermanns]

Public bug reported:

After bringing the computer into sleep mode and returning later from it,
after entering my password and being back in my session, there might or
might not be icons on the unity launcher. I made a screenshot from the
launcher without icons.

unity:
  Installiert:   7.4.0+16.04.20160321-0ubuntu1
  Installationskandidat: 7.4.0+16.04.20160321-0ubuntu1
  Versionstabelle:
 *** 7.4.0+16.04.20160321-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity 7.4.0+16.04.20160321-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
BootLog: Scanning for Btrfs filesystems
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Mar 24 19:26:34 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile GM965/GL960 
Integrated Graphics Controller (primary) [10f7:8338]
   Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile GM965/GL960 
Integrated Graphics Controller (secondary) [10f7:8338]
InstallationDate: Installed on 2016-03-16 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-15-generic 
root=UUID=56c66297-9425-4cae-9a21-f0e3c231a9cf ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.00L11
dmi.board.name: CF19-2
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-19FHGAXBG
dmi.product.version: 002
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
upstart.unity7.log: WARN  2016-03-24 19:24:37 nux.inputmethod.ibus 
InputMethodIBus.cpp:67 Impossible to connect to connect to ibus
version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Mar 24 19:23:24 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.1-1ubuntu4

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "unity-launcher without icons"
   
https://bugs.launchpad.net/bugs/1561684/+attachment/4610180/+files/Bildschirmfoto%20vom%202016-03-24%2019-23-12.png

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

Title:
  unity launcher has no icons after returning from sleep mode

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

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

[Bug 1546180] [NEW] gcc 5 compile error

[Sascha]

Public bug reported:

When using the pre-build packages in combinaton with the default gcc 5,
linking will fail due to a dual abi missconfiguration. Seems that the
cpputest binaries are build with the wrong gcc / or settings.

Compare
https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html

When downloading the current version 3.7.1 from
http://cpputest.github.io/, building the libs locally and using them
instead of the pre build ones, everything works fine.

The error occures when doing a CHECK_EQUAL on strings and results in

Nicht definierter Verweis auf `StringFrom(std::__cxx11::basic_string const&)'
collect2: error: ld returned 1 exit status

** Affects: cpputest (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/1546180

Title:
  gcc 5 compile error

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

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

[Bug 1538471] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid next size (fast): 0x0000000001ca17b0 ***

[Sascha Biermanns]

It happened to me on a real install, when searching for "Limone sul
Garda" with activated Wikipedia-scope and enabled online-search, but
only on the first search.

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

Title:
  scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3':
  free(): invalid next size (fast): 0x01ca17b0 ***

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

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

[Bug 1542599] [NEW] Xorg crashed after login

[Sascha Morr]

Public bug reported:

Just login after boot and get a failure message.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Feb  5 10:49:15 2016
ExecutablePath: /usr/lib/xorg/Xorg
InstallationDate: Installed on 2016-01-22 (14 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160121)
ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
ProcEnviron:
 
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
 RRCrtcDetachScanoutPixmap ()
Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Information type changed from Private to Public

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

Title:
  Xorg crashed after login

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

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

[Bug 1525697] [NEW] package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

[Sascha Biermanns]

Public bug reported:

1) Description: Ubuntu Xenial Xerus (development branch)
Release:16.04

2) gnome-menus:
  Installiert:   3.13.3-6ubuntu2
  Installationskandidat: 3.13.3-6ubuntu2

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-menus 3.13.3-6ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-4.13-generic 4.3.2
Uname: Linux 4.3.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
Date: Sun Dec 13 19:58:25 2015
Dependencies:
 
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2015-12-11 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.1.4
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger 
bilden eine Schleife, aufgegeben
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger
  bilden eine Schleife, aufgegeben

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

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

[Bug 1523374] [NEW] wrong height calculation, icons not visible

[Sascha Appel]

Public bug reported:

xfce4-indicator-plugin 2.2.3, xubuntu 15.10

panel height: 82
Custom-dpi: 192

GDK_DPI_SCALE 0.5
GDK_SCALE 2


The indicator plugin seems to calculate its own height wrong. If i check 
"single row" mode in preferences the icons are not completely visible, if i 
deselct single row mode i can see the first row and the half of the second row. 
(s. screenshot)

** Affects: xfce4-indicator-plugin (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "single_line.png"
   
https://bugs.launchpad.net/bugs/1523374/+attachment/4530797/+files/single_line.png

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

Title:
  wrong height calculation, icons not visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1523374/+subscriptions

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

[Bug 1523374] Re: wrong height calculation, icons not visible

[Sascha Appel]

** Attachment added: "multiple_row.png"
   
https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1523374/+attachment/4530798/+files/multiple_row.png

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

Title:
  wrong height calculation, icons not visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1523374/+subscriptions

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

[Bug 1493888] Re: FGLRX incompatible with kernel 4.2

[Sascha Biermanns]

Same with the AMD Radeon 6600M and 6700M Series, even with the newest
4.2-10 version.

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

Title:
  FGLRX incompatible with kernel 4.2

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

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

[Bug 1493888] Re: FGLRX incompatible with kernel 4.2

[Sascha Biermanns]

Workaround at the moment: Still booting up with the 4.1.0-3 kernel
version.

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

Title:
  FGLRX incompatible with kernel 4.2

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

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

[Bug 1476342] [NEW] Feature request: Copy variable

[sascha]

Public bug reported:

It would be nice if PSPP would support copying of variables.

Example: I have a questionnaire that has several items with the same
answer options only the wording of the question needs to be changed.

If I go to 'Variable View' and try to copy an existing variable with all
its data defined I'm not able to paste it. It's currently only possible
to insert a new empty variable anywhere in between or at the end of the
variable table. It would be excellent if the option 'insert variable'
would be supported.

Thanks in advance!

** Affects: pspp (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/1476342

Title:
  Feature request: Copy variable

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

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

[Bug 1476344] [NEW] Feature request: Search in syntax | Replace code in syntax

[sascha]

Public bug reported:

PSPP currently doesn't support commands like searching and replacing in
the syntax window. Even though the syntax can also be edited in every
other text editor, it would be nice to see this (basic) feature in the
PSPP syntax editor.

Thanks in advance!

** Affects: pspp (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/1476344

Title:
  Feature request: Search in syntax | Replace code in syntax

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

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

[Bug 1406981]

[Sascha Baumeister]

(In reply to Marco Rietveld from comment #46)
 This bug (or very similar one) appears to have reappeared in the latest
 update to Luna (20150219-0600). The same workaround also works there (e.g. 
 -Dorg.eclipse.swt.browser.DefaultType=mozilla).

Just to let you know, I use the latest Eclipse Luna releases on Ubuntu
Gnome 14.04.2 (both the Java and the C/C++ flavors), and have not
experienced this problem again since the Juno versions (see comment
#19). Therefore, I guess there must be something special in your setup.

Mentioning this 2 years old comment, I was probably right to predict
that there'd be tons of duplicates for this bug; the bug description is
simply not expressive enough to find it using a standard google search
...

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

Title:
  OpenHAB designer causes crash in soup_session_feature_detach

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse-eclipsers/+bug/1406981/+subscriptions

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

[Bug 1163501]

[Sascha Baumeister]

(In reply to Marco Rietveld from comment #46)
 This bug (or very similar one) appears to have reappeared in the latest
 update to Luna (20150219-0600). The same workaround also works there (e.g. 
 -Dorg.eclipse.swt.browser.DefaultType=mozilla).

Just to let you know, I use the latest Eclipse Luna releases on Ubuntu
Gnome 14.04.2 (both the Java and the C/C++ flavors), and have not
experienced this problem again since the Juno versions (see comment
#19). Therefore, I guess there must be something special in your setup.

Mentioning this 2 years old comment, I was probably right to predict
that there'd be tons of duplicates for this bug; the bug description is
simply not expressive enough to find it using a standard google search
...

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

Title:
  java crashed with SIGABRT in soup_session_feature_detach()

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

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

[Bug 1448088] [NEW] package minetest-data (not installed) failed to install/upgrade: Versuch, »/usr/games/minetest-mapper« zu überschreiben, welches auch in Paket freeminer-data 0.4.12.6-1~getdeb2~uto

[Sascha Biermanns]

Public bug reported:

The bug occured on a fresh installation of Ubuntu 15.04

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: minetest-data (not installed)
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
Architecture: amd64
Date: Fri Apr 24 13:42:52 2015
DuplicateSignature: package:minetest-data:(not installed):Versuch, 
»/usr/games/minetest-mapper« zu überschreiben, welches auch in Paket 
freeminer-data 0.4.12.6-1~getdeb2~utopic ist
ErrorMessage: Versuch, »/usr/games/minetest-mapper« zu überschreiben, welches 
auch in Paket freeminer-data 0.4.12.6-1~getdeb2~utopic ist
InstallationDate: Installed on 2015-04-23 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4
SourcePackage: minetest
Title: package minetest-data (not installed) failed to install/upgrade: 
Versuch, »/usr/games/minetest-mapper« zu überschreiben, welches auch in Paket 
freeminer-data 0.4.12.6-1~getdeb2~utopic ist
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package minetest-data (not installed) failed to install/upgrade:
  Versuch, »/usr/games/minetest-mapper« zu überschreiben, welches auch
  in Paket freeminer-data 0.4.12.6-1~getdeb2~utopic ist

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

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

[Bug 1432317] Re: [systemd] should now depend on systemd/upstart, not upstart-bin

[Sascha Mirow]

I had a problem after updating to Ubuntu 15.04 which same logs in
xsession-errors. After many tests I determined that I had the files
start and stop in /home/{user}/bin which was added as path. upstart-
event-bridge seems to use start and stop also and may not use a full
path calling.

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

Title:
  [systemd] should now depend on systemd/upstart, not upstart-bin

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

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

[Bug 1434693] [NEW] gnome-terminal-server crashed with SIGSEGV in g_closure_invoke()

[Sascha]

Public bug reported:

Terminal crashed right after apt-get upgrade and reboot

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-terminal 3.14.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 20 20:51:57 2015
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2015-03-07 (13 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306)
ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
ProcEnviron:
 XDG_RUNTIME_DIR=set
 SHELL=/bin/bash
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x4171de:mov(%rbx),%rdx
 PC (0x004171de) ok
 source (%rbx) (0xff000189407d0080) not located in a known VMA region (needed 
readable region)!
 destination %rdx ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal-server crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace vivid

** Information type changed from Private to Public

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

Title:
  gnome-terminal-server crashed with SIGSEGV in g_closure_invoke()

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

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

[Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

[Sascha Biermanns]

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

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

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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

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

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

[Bug 1407313] Re: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad)

[Sascha Biermanns]

I have the same misbehaviour with kernel 3.19.0-7-generic on Ubuntu
15.04. Synclient -l shows that the ClickPad is activated - but it
doesn't react.

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

Title:
  Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech
  Touchpad)

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

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

[Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

[Sascha Biermanns]

Suspend work in kernel 4.0.0-04rc2-generic, installed via package
linux-image-4.0.0-04rc2-generic_4.0.0-04rc2.201503031836_amd64
from kernel mainline builds

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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

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

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

[Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

[Sascha Biermanns]

I just installed Ubuntu 15.04 yesterday, and so I can only say, it
happened with the installation from yesterdays actual kernel.

** Tags added: kernel-fixed-upstream

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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

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

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

[Bug 1428404] [NEW] fglrx-updates-core 2:14.501-0ubuntu1: fglrx-updates-core kernel module failed to build

[Sascha Biermanns]

Public bug reported:

This problem occured after a kernel update.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:14.501-0ubuntu1
Uname: Linux 4.0.0-04rc2-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 4.0.0-04rc2-generic
Date: Thu Mar  5 01:34:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: fglrx-updates-core, 14.501, 3.19.0-7-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21e1]
 Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 
6630M/6650M/6750M/7670M/7690M] [1002:6741] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Radeon HD 6630M [17aa:21e1]
InstallationDate: Installed on 2015-03-02 (2 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150302)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 44015CG
PackageVersion: 2:14.501-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.0.0-04rc2-generic 
root=UUID=7b46ab59-0768-4b9e-8a6d-16b63524d4cb ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:14.501-0ubuntu1: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8JET44WW (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 44015CG
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:bvr8JET44WW(1.38):bd08/05/2013:svnLENOVO:pn44015CG:pvrThinkPadEdgeE420s:rvnLENOVO:rn44015CG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 44015CG
dmi.product.version: ThinkPad Edge E420s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Thu Mar  5 01:42:58 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12364 
 vendor SEC
xserver.version: 2:1.16.2.901-1ubuntu4

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


** Tags: amd64 apport-package compiz-0.9 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/1428404

Title:
  fglrx-updates-core 2:14.501-0ubuntu1: fglrx-updates-core kernel module
  failed to build

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

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

[Bug 1428050] [NEW] [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

[Sascha Biermanns]

Public bug reported:

When opening the lip, to resume after suspend, the computer was frozen
and some LED's where blinking in a regular rhythmn. I had to reset the
Toughbook to restart it.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: 
boot/vmlinuz-3.19.0-7-generic]
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  skb2372 F pulseaudio
Date: Wed Mar  4 10:16:51 2015
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2015-03-02 (1 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150302)
InterpreterPath: /usr/bin/python3.4
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=UUID=00bc12a3-0121-4e30-8834-27fafd4a0666 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
Title: [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume 
failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 10/10/2007
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.00L11
dmi.board.name: CF19-2
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 001
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.name: CF-19FHGAXBG
dmi.product.version: 002
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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


** Tags: amd64 apport-kerneloops resume suspend vivid

** Attachment added: output of sudo lspci -vnvn  lspci-vnvn.log
   
https://bugs.launchpad.net/bugs/1428050/+attachment/4334226/+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/1428050

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

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

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

[Bug 1424554] [NEW] package libva-x11-1 1.3.1-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libva-x11-1/changelog.Debian.gz« zu überschreiben, welches verschieden von ander

[Sascha Peter]

Public bug reported:

...

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: libva-x11-1 1.3.1-3
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Date: Mon Feb 23 09:47:50 2015
DuplicateSignature: package:libva-x11-1:1.3.1-3:Versuch, gemeinsam benutztes 
»/usr/share/doc/libva-x11-1/changelog.Debian.gz« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libva-x11-1:i386 ist
ErrorMessage: Versuch, gemeinsam benutztes 
»/usr/share/doc/libva-x11-1/changelog.Debian.gz« zu überschreiben, welches 
verschieden von anderen Instanzen des Paketes libva-x11-1:i386 ist
InstallationDate: Installed on 2014-07-11 (226 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: libva
Title: package libva-x11-1 1.3.1-3 failed to install/upgrade: Versuch, 
gemeinsam benutztes »/usr/share/doc/libva-x11-1/changelog.Debian.gz« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libva-x11-1:i386 ist
UpgradeStatus: Upgraded to utopic on 2014-10-24 (121 days ago)

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


** Tags: amd64 apport-package utopic

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

Title:
  package libva-x11-1 1.3.1-3 failed to install/upgrade: Versuch,
  gemeinsam benutztes »/usr/share/doc/libva-x11-1/changelog.Debian.gz«
  zu überschreiben, welches verschieden von anderen Instanzen des
  Paketes libva-x11-1:i386 ist

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

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

[Bug 1408988] Re: backport request for precise

[Sascha Manns]

** Description changed:

- Please backport to precise.
+ Please backport a version 4.x to precise.

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

Title:
  backport request for precise

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

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

[Bug 1408988] [NEW] backport request for precise

[Sascha Manns]

Public bug reported:

Please backport to precise.

** Affects: publican (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/1408988

Title:
  backport request for precise

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

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