[Touch-packages] [Bug 1737669] Re: New test needs arch dependent include for static lib.

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/iproute2/+git/iproute2/+merge/335065

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737669

Title:
  New test needs arch dependent include for static lib.

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Hi,
  the new test works great, but only on x86 as the test needs to build a helper 
and for that uses a fix path. Instead it would need to use a arch dependent 
include path.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737669] [NEW] New test needs arch dependent include for static lib.

[ChristianEhrhardt]

Public bug reported:

Hi,
the new test works great, but only on x86 as the test needs to build a helper 
and for that uses a fix path. Instead it would need to use a arch dependent 
include path.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737669

Title:
  New test needs arch dependent include for static lib.

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Hi,
  the new test works great, but only on x86 as the test needs to build a helper 
and for that uses a fix path. Instead it would need to use a arch dependent 
include path.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Steve Langasek]

I'll also mention that while this is being reported on ppc64el, it's an
architecture-independent problem and is keeping daily images from being
promoted currently.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1737662

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  New

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Steve Langasek]

This appears to be a regression introduced by busybox 1:1.27.2-1ubuntu4:
  * SECURITY UPDATE: directory traversal via tar symlink extraction
- debian/patches/CVE-2011-5325-2.patch: do not extract unsafe symlinks
  unless env variable is set in archival/libarchive/Kbuild.src,
  archival/libarchive/data_extract_all.c,
  archival/libarchive/unsafe_symlink_target.c, archival/tar.c,
  coreutils/link.c, include/bb_archive.h, libbb/copy_file.c,
  testsuite/tar.tests.
- CVE-2011-5325
[...]

 -- Marc Deslauriers   Fri, 24 Nov 2017
12:55:21 -0500

Marc, this patch seems to have not been included upstream in Debian, and
it's definitely a behavior difference vs. the other tar implementations
as used by debootstrap (i.e. GNU tar).  Is this actually fixing a
security vulnerability, or is it an attempt to mitigate future unknown
vulnerabilities?

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2011-5325

** Package changed: base-installer (Ubuntu) => busybox (Ubuntu)

** Changed in: busybox (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Marc Deslauriers (mdeslaur)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1737662

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  New
Status in busybox package in Ubuntu:
  New

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  

[Touch-packages] [Bug 1594073] Re: 16.04 - initrd fails to decrypt and mount /usr directory when it's on it's own cryptsetup partition

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1594073

Title:
  16.04 - initrd fails to decrypt and mount /usr directory when it's on
  it's own cryptsetup partition

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.04 LTS, upgraded from a 15.10 that did not show the
  issue.

  Initramd fails at setting up the encrypted /usr partition.
  At the (initramfs) prompt the following command is accepted and succeeds at 
decrypting the partition:

  cryptsetup --key-file /root/etc/keys/sda5_usr open --type luks
  /dev/sda5 sda5_usr

  After entering the above command and pressing + to exit the 
initramfs shell, system boot resumes and completes successfully.
  /etc (in the initramd) does not have the crypttab file, which is present in 
the decrypted and mounted root filesystem in /root/etc.

  The problem manifests itself regardless that in /etc/initramfs-
  tools/initramfs.conf MODULES=most or MODULES=dep is set before
  generating the initrd.

  Terminal output of the failed boot up to the initramfs prompt:

  Begin: Running /scripts/init-premount ... done
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
Please unlock disk sda3_ubuntu_root:
  [ 120.025413] NET: Registered protocol family 38
  cryptsetup: sda3_ubuntu_root set up successfully
  done.
  Begin: Running /scripts/local-premount ... done.
  Begin: Will now check root file system ... fsck from util-linux 2.27.1
  [/sbin/fsck.ext4 (1) -- /dev/mapper/sda3_ubuntu_root] fsck.ext4 -a -C0 
/dev/mapper/sda3_ubuntu_root
  Ubuntu_rootfs: clean, 44092/625056 files, 801590/2499604 blocks
  done.
  [ 126.996543] EXT4-fs (dm-0): mounted filesystem with ordered data mode. 
Opts: (null)
  done.
  Begin: mounting /usr file system ... Begin: Waiting for /usr file system ... 
Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  Begin: Running /scripts/local-block ... done.
  done.
  Gave up waiting for /usr device. Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT! UUID=6b18125b-32be-458c-a623-612a14e74eb3 does not exist. Dropping to 
a shell!

  BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) _

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737662] [NEW] Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Problem Description:
===
Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

Steps to re-create:
==
> on Witherspoon test system, tried to install ubuntu1804 using netboot install.

> Selected mirror path:http://10.xx.11.31:3128


   [!] Choose a mirror of the Ubuntu archive 
  ? ?
  ? Please select an Ubuntu archive mirror. You should use a mirror in  ?
  ? your country or region if you do not know which mirror has the best ?
  ? Internet connection to you. ?
  ? ?
  ? Usually, .archive.ubuntu.com is a good choice.   ?
  ? ?
  ? Ubuntu archive mirror:  ?
  ? ?
  ? us.ports.ubuntu.com ?
  ? ?
  ??
  ? ?
  ???


> Able to select the disks

  ?? [!!] Partition disks ???
  ? ?
  ? Note that all data on the disk you select will be erased, but not   ?
  ? before you have confirmed that you really want to make the changes. ?
  ? ?
  ? Select disk to partition:   ?
  ? ?
  ?/dev/nvme0n1 - 409.6 GB Unknown  ?
  ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
  ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
  ? ?
  ??
  ? ?
  ???


> Started installing base system

  ??? Installing the base system 
  ? ?
  ?6%   ?
  ? ?
  ? Retrieving libc6... ?
  ? ?
  ???

> Then seen Debootstrap warning messages as below


  ??? [!!] Install the base system ???
  ?  ? ??
  ?   ?   Debootstrap warning?  ?
  ?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
  ?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
  ? Ex?  ?  ?
  ?   ?   ?  ?
  ?  ? ??
  


  ??? [!!] Install the base system ??
  ?   ?  ?  ?
  ?   ?   Debootstrap warning?  ?
  ?   ? Warning: See the log for details ?  ?
  ? Extracting zlib1g.?  ?  ?
  ?   ?   ?  ?
  ?  ? ??
  


  [!!] Install the base system 
  ? ?
  ?  ?Debootstrap warning ? ?
  ?  ? Warning: Failure trying to run: chroot /target mount -t proc proc  ? ?
  ?  ? /proc  ? ?
  ? E?? ?
  ?  ?   

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Bug Watch Updater]

** Changed in: gnome-weather
   Status: Confirmed => Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Yuan-Chen Cheng]

@Łukasz,

per https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3054/+packages,

I can't see "no-change rebuild is still failing" per you mentioned in
#24.

Can you share where is the fail log or anything ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1725190

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  In Progress
Status in libmbim source package in Xenial:
  New
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737663] [NEW] dhclient fails setting default gateway to unreachable host

[HonoredMule]

Public bug reported:

When receiving an IP from a DHCP server and a router IP that is not the
same IP, dhclient-script silently fails to add the router as a default
route for the interface (RTNETLINK answers: Network is unreachable).
Error occurs on line 320:

# set default route
ip -4 route add default via ${router} dev ${interface} \
${if_metric:+metric $if_metric} >/dev/null 2>&1

  With no control over the DHCP server (an ISP-provided appliance
configured to propagate its external IP to this DHCP client), the
apparent solution (other than quick hard-coded hacks like `route add
default MYINTERFACE`) is to first create a single-ip route, adding the
preceding line:

ip -4 route add ${router} dev ${interface}

(Alternatively, collapsing the resulting two rules by replacing original
line's use of ${router} with ${new_ip_address} also works, and also
preserves the route table's resolution of the gateway ip to a hostname -
unlike the hack.)

I could probably write a more complex custom enter hook to correctly
handle the scenario, but this does not seem so terribly obscure to
justify it (standard appliance from a major Canadian ISP).  With
sufficient information present to infer the correct routing, I believe
it should work out of the box.

I do not rule out consequences of doing so beyond my current grasp, and
it does seem odd to me that my ISP provides a gateway outside the
subnet.  Nevertheless I hope some attention on the issue will yeild a
more robust stock configuration or at least some deeper insight.

(Sanitized) variable dump for dhclient-script:
Tue Dec 12 00:59:23 AST 2017: entering /etc/dhcp/dhclient-enter-hooks.d, 
dumping variables.
reason='BOUND'
interface='eth0'
new_ip_address='123.45.114.112'
new_network_number='123.45.114.0'
new_subnet_mask='255.255.255.0'
new_broadcast_address='123.45.114.255'
new_routers='123.45.112.1'
new_domain_name='redacted.com'
new_domain_name_servers='127.0.0.1'
old_ip_address='123.45.114.112'
old_network_number='123.45.114.0'
old_subnet_mask='255.255.255.0'
old_broadcast_address='123.45.114.255'
old_routers='123.45.112.1'
old_domain_name='redacted.com'
old_domain_name_servers='127.0.0.1'

Routing rules with stock configuration (the only one that doesn't route 
internet traffic):
Destination Gateway Genmask Flags Metric RefUse 
Iface
123.45.114.0*   255.255.255.0   U 0  00 eth0

With my added line:
Destination Gateway Genmask Flags Metric RefUse 
Iface
default fctnnbsc38w-123 0.0.0.0 UG0  00 eth0
fctnnbsc38w-123 *   255.255.255.255 UH0  00 eth0
123.45.114.0*   255.255.255.0   U 0  00 eth0

With interface ip as router ip:
Destination Gateway Genmask Flags Metric RefUse 
Iface
default fctnnbsc38w-123 0.0.0.0 UG0  00 eth0
123.45.114.0*   255.255.255.0   U 0  00 eth0

With hardcoded hack:
Destination Gateway Genmask Flags Metric RefUse 
Iface
default *   0.0.0.0 U 0  00 eth0
123.45.114.0*   255.255.255.0   U 0  00 eth0

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  When receiving an IP from a DHCP server and a router IP that is not the
  same IP, dhclient-script silently fails to add the router as a default
  route for the interface (RTNETLINK answers: Network is unreachable).
  Error occurs on line 320:
  
- # set default route
- ip -4 route add default via ${router} dev ${interface} \
- ${if_metric:+metric $if_metric} >/dev/null 2>&1
+ # set default route
+ ip -4 route add default via ${router} dev ${interface} \
+ ${if_metric:+metric $if_metric} >/dev/null 2>&1
  
- 
-   With no control over the DHCP server (an IPS-provided appliance
+   With no control over the DHCP server (an ISP-provided appliance
  configured to propagate its external IP to this DHCP client), the
  apparent solution (other than quick hard-coded hacks like `route add
  default MYINTERFACE`) is to first create a single-ip route, adding the
  preceding line:
  
- ip -4 route add ${router} dev ${interface}
+ ip -4 route add ${router} dev ${interface}
  
  (Alternatively, collapsing the resulting two rules by replacing original
  line's use of ${router} with ${new_ip_address} also works, and also
  preserves the route table's resolution of the gateway ip to a hostname -
  unlike the hack.)
  
  I could probably write a more complex custom enter hook to correctly
  handle the scenario, but this does not seem so terribly obscure to
  justify it (standard appliance from a major Canadian ISP).  With
  sufficient 

[Touch-packages] [Bug 1736880] Re: Netboot install: Incomplete Settings -> Network interface

[dino99]

What this should be ?

cat /run/NetworkManager/conf.d/netplan.conf
[keyfile]
# devices managed by networkd
unmanaged-devices+=interface-name:enp2s0

oem@ubuntu:~$ networkctl | cat
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 enp2s0   ether  routableconfiguring



** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1736880

Title:
  Netboot install: Incomplete Settings -> Network interface

Status in network-manager package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New

Bug description:
  I usually do installation via a netboot mini.iso, and was wondering
  why i was not finding the 'wired' settings into Settings -> Network,
  only the 'vpn' settings are displayed.

  A forum thread have told me that 'netplan (package name is nplan) by default 
doesn't use NetworkManager when installed from netboot'
  https://ubuntuforums.org/showthread.php?t=2379460

  Hope to get the next netboot doing a full installation when the bionic
  iso will be proposed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nplan 0.32
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec  7 08:06:48 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

[Bug Watch Updater]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launchpad.net/bugs/1443853

Title:
  Ubuntu boot in Oracle VirtualBox ends up with a corrupted display

Status in Virtualbox:
  Invalid
Status in console-setup package in Ubuntu:
  Triaged
Status in kbd package in Ubuntu:
  Triaged
Status in virtualbox package in Ubuntu:
  Triaged

Bug description:
  (Content copied from "Ubuntu 14.10 ISO live boot ends up with a
  corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz)

  Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO 
ends up with a corrupted screen. See the screenshot:
  https://launchpadlibrarian.net/186864347/ubu.png

  Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7)
  fixes the display.

  I think that this might be a problem with resolution setting:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  ```

  After switching back and forth to the tty7 (what fixes the display)
  the log says:

  ```
  00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler..
  00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=1152x400
  00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
  00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, 
BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler..
  00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, 
BytesPerLine=0, Size=720x400
  00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer 
due to format is invalid..
  00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, 
pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1
  00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler..
  00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, 
BitsPerPixel=32, BytesPerLine=4096, Size=1024x768
  00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use 
VGA device content..
  ```

  I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens
  on both of them.

  You can download the ISO images of these two systems here:

   https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10
  -desktop-amd64.iso

   http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu-
  gnome-14.10-desktop-amd64.iso

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819

[Chih-Hsyuan Ho]

** Also affects: modemmanager
   Importance: Undecided
   Status: New

** No longer affects: modemmanager

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1735134

Title:
  ModemManager uses a wrong plugin for Dell DW5818/5819

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Since linux-4.4.0-98, the kernel additionally load gcserial driver for
  Dell Wireless DW5818/5819. The reason behind it is to support firmware
  switching and upgrading. However, the change makes ModemManager to use
  Gobi plugin for this two modules. With Gobi plugin, the modules could
  establish data links, but it failed to retrieve the signal state. And
  it caused the mmcli and nm-applet giving wrong signal strength. The
  modules support the MBIM protocol, so ModemManager should use Dell
  plugin for these two modules.

  I have worked out a patch to forbid these two modules in Gobi plugin,
  and it does work well.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737657] [NEW] Failure to be root is repored in a misleading message

[Kevin O'Gorman]

Public bug reported:

This is a feature request.

When solving a problem or in a rush, I don't necessarily remember
everything from a man page, or even think to read it.  This is what
happened with ntpdate(8)

$ ntpdate
11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
$

Of course, I should have used sudo.  And it's documented.  But as I
pointed out that doesn't help much when in a hurry or stressed.  My bad,
so I usually wouldn't mention it.  But the fix is so simple I hope it
appeals to you.

-> test the permissions and if they are missing, make that message

11 Dec 20:08:12 ntpdate[13930]: insufficient permissions (suggestion:
use sudo)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5.7
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 11 17:53:23 2017
InstallationDate: Installed on 2016-08-08 (490 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: ntp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apparmor apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1737657

Title:
  Failure to be root is repored in a misleading message

Status in ntp package in Ubuntu:
  New

Bug description:
  This is a feature request.

  When solving a problem or in a rush, I don't necessarily remember
  everything from a man page, or even think to read it.  This is what
  happened with ntpdate(8)

  $ ntpdate
  11 Dec 20:08:12 ntpdate[13930]: no servers can be used, exiting
  $

  Of course, I should have used sudo.  And it's documented.  But as I
  pointed out that doesn't help much when in a hurry or stressed.  My
  bad, so I usually wouldn't mention it.  But the fix is so simple I
  hope it appeals to you.

  -> test the permissions and if they are missing, make that message

  11 Dec 20:08:12 ntpdate[13930]: insufficient permissions (suggestion:
  use sudo)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntpdate 1:4.2.8p4+dfsg-3ubuntu5.7
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Dec 11 17:53:23 2017
  InstallationDate: Installed on 2016-08-08 (490 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 301631] Re: weather/clock panel is missing Utrecht, NL, Europe

[Bug Watch Updater]

** Changed in: libgweather
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/301631

Title:
  weather/clock panel is missing Utrecht, NL, Europe

Status in libgweather:
  Fix Released
Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  I installed ubuntu 8.10 and utrecht city disappered from libgweather,
  in 8.04 was. This clock has version Clock 2.24.1 and i think in 8.04
  is version 2.22 so with higher version some cities disappeared

  2) City Name - Utrecht (http://en.wikipedia.org/wiki/Utrecht_(city))
  3) City Latitude/Longitude - 52°5'N 5°8'E 
(http://www.mapsofworld.com/lat_long/netherlands-lat-long.html)
  4) Airport Name - There isn't airport, closes is Schiphol in Amsterdam (70km) 
But there is important train station and university

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1723198] Re: package ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned

[Duane Gibson]

I'm new to ubuntu and just getting started.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1723198

Title:
  package ca-certificates 20170717~16.04.1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  I have no further information to give at this time except to say that
  there were several errors during the upgrade process from 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 12 17:52:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-11-16 (1425 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737648] [NEW] Hold libgweather in -proposed until first bionic language pack

[Jeremy Bicha]

Public bug reported:

In https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu1 we
worked around a Launchpad configuration bug for Ubuntu language packs.
That configuration issue has been fixed but we still need a language
pack to be built after the change was made or we'll end up reintroducing
LP: #1704533.

Therefore, I'm filing this bug to keep libgweather in proposed until the
first bionic language pack is published. Feel free to close this bug
once that happens.

** Affects: libgweather (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: bionic block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1737648

Title:
  Hold libgweather in -proposed until first bionic language pack

Status in libgweather package in Ubuntu:
  Triaged

Bug description:
  In https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu1 we
  worked around a Launchpad configuration bug for Ubuntu language packs.
  That configuration issue has been fixed but we still need a language
  pack to be built after the change was made or we'll end up
  reintroducing LP: #1704533.

  Therefore, I'm filing this bug to keep libgweather in proposed until
  the first bionic language pack is published. Feel free to close this
  bug once that happens.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Steve Langasek]

On Sat, Dec 09, 2017 at 05:12:36PM -, Daniel wrote:
> Hello,

> Was just bitten by this as well.  etc/resolv.conf was pointing at
> 127.0.1.1.

> hydrogen@Bliss:~$ ls -l /etc/resolv.conf
> lrwxrwxrwx 1 root root 33 May 24  2016 /etc/resolv.conf -> 
> ../run/NetworkManager/resolv.conf

> hydrogen@Bliss:~$ dpkg -S /etc/NetworkManager/
> network-manager, network-manager-vpnc: /etc/NetworkManager

> Fixed by moving symlink, but let me know if I can provide any additional
> information.

Can you attach the contents of /etc/NetworkManager/conf.d and
/etc/NetworkManager/NetworkManager.conf from your system?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1683990] Re: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

[Clare]

** Description changed:

  Edit 11-Dec-2017
  
- attached screenshot showing how there are no 'Play sound through' Output
- Options in the Sound Settings. Also, AlsaMixer keeps resetting the
- speaker to mute after each re-start.
- 
- Note that I DO have sound via headphones after resetting the speaker up to 
100%.
+ attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer indicates that the speaker keeps 
getting reset to mute after each re-start.
  -
  
  Edit 05-Nov-2017
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed
  
  and when I ran gnome-control-center at the command line recently I saw:
  
  (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
  the tree, so cannot set the active output
  
  (gnome-control-center:8955): Gvc-WARNING **: Couldn't match the portless
  stream (with card) - 'Built-in Audio Analog Stereo' is it an input ? ->
  1, streams card id -> 0
  
  (gnome-control-center:8955): Gvc-CRITICAL **:
  gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)'
  failed
  
  (gnome-control-center:8955): sound-cc-panel-WARNING **:
  on_control_active_input_update - tried to fetch an input of id 0 but got
  nothing
  
  -original text of bug--
  
- I have had no sound since original purchase
+ I have had no sound since original (fairly recent) purchase. I purchased
+ online from Dell.
  
  Sound preferences were originally showing in upper right hand corner of
  the screen, but the sliders for changing volume were grayed out, and
  choosing sound test had no audible or visual result.
  
- -
+ Now sound preferences are not showing in upper right corner at all, and
+ system preferences --> sound no longer shows 'sound test' as an option.
+ 
+ I tried to fix original problem myself by killing then re-starting pulseaudio
+ No effect. Also I tried commands
+ 
+ apt-get purge pulseaudio
+ and then later
+ apt-get install pulseaudio
+ 
+ it seemed to be after that when the sound preferences stopped showing in
+ upper right corner, but I also did a general ubuntu update at the same
+ time (and there is still a restart required for update for 'Latitude
+ E5X60 System Update' 68614)
+ 
  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 0FFPFD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

** Summary changed:

- [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
+ [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all. Resets 
to mute. No 'Play Sound Through' options

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1683990

Title:
  [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all.
  Resets to mute. No 'Play Sound Through' options

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Edit 11-Dec-2017

  attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer 

[Touch-packages] [Bug 1737637] Re: Replacing configuration file directory with file breaks unattended-upgrades

[Balint Reczey]

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 1556, in 
+ main(options)
+   File "/usr/bin/unattended-upgrade", line 1348, in main
+ if conffile_prompt(item.destfile):
+   File "/usr/bin/unattended-upgrade", line 725, in conffile_prompt
+ with open(prefix + conf_file, 'rb') as fp:
+ IsADirectoryError: [Errno 21] Is a directory: 
'/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf'

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => In Progress

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1737637

Title:
  Replacing configuration file directory with file breaks unattended-
  upgrades

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1556, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1348, in main
  if conffile_prompt(item.destfile):
File "/usr/bin/unattended-upgrade", line 725, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: 
'/etc/fonts/conf.avail/65-0-fonts-guru-extra.conf'

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1683990] Re: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

[Clare]

** Description changed:

+ Edit 11-Dec-2017
+ 
+ attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer keeps resetting the speaker to 
mute after each re-start. 
+ -
+ 
  Edit 05-Nov-2017
- wondering if my issue could be same as bug 1616079
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed
  
  and when I ran gnome-control-center at the command line recently I saw:
  
  (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
  the tree, so cannot set the active output
  
  (gnome-control-center:8955): Gvc-WARNING **: Couldn't match the portless
  stream (with card) - 'Built-in Audio Analog Stereo' is it an input ? ->
  1, streams card id -> 0
  
  (gnome-control-center:8955): Gvc-CRITICAL **:
  gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)'
  failed
  
  (gnome-control-center:8955): sound-cc-panel-WARNING **:
  on_control_active_input_update - tried to fetch an input of id 0 but got
  nothing
  
  -original text of bug--
  
  I have had no sound since original (fairly recent) purchase. I purchased
  online from Dell.
  
  Sound preferences were originally showing in upper right hand corner of
  the screen, but the sliders for changing volume were grayed out, and
  choosing sound test had no audible or visual result.
  
  Now sound preferences are not showing in upper right corner at all, and
  system preferences --> sound no longer shows 'sound test' as an option.
  
  I tried to fix original problem myself by killing then re-starting pulseaudio
  No effect. Also I tried commands
  
  apt-get purge pulseaudio
  and then later
  apt-get install pulseaudio
  
  it seemed to be after that when the sound preferences stopped showing in
  upper right corner, but I also did a general ubuntu update at the same
  time (and there is still a restart required for update for 'Latitude
  E5X60 System Update' 68614)
  
  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 0FFPFD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

** Attachment added: "No 'Play Sound Through' Output Options in Sound Settings"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683990/+attachment/5021514/+files/Screenshot%20from%202017-12-11%2019-03-59.png

** Description changed:

  Edit 11-Dec-2017
  
- attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer keeps resetting the speaker to 
mute after each re-start. 
+ attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer keeps resetting the speaker to 
mute after each re-start.
  -
  
  Edit 05-Nov-2017
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed
  
  and when I ran gnome-control-center at the command line recently I saw:
  
  (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
  the tree, so cannot set the active output
  
  

[Touch-packages] [Bug 1737637] Re: Replacing configuration file directory with file breaks unattended-upgrades

[Balint Reczey]

** Summary changed:

- 
/usr/bin/unattended-upgrade:IsADirectoryError:/usr/bin/unattended-upgrade@1556:main:conffile_prompt
+ Replacing configuration file directory with file breaks unattended-upgrades

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1737637

Title:
  Replacing configuration file directory with file breaks unattended-
  upgrades

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737637] [NEW] Replacing configuration file directory with file breaks unattended-upgrades

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1737637

Title:
  Replacing configuration file directory with file breaks unattended-
  upgrades

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/ed79dbb4e6eba8c7b89fcd7e0cbf60b0db4920ce 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: steam (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1698287

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737635] Re: Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

[Balint Reczey]

** Summary changed:

- 
/usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@1706:main:get_dpkg_log_content:decode
+ Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => In Progress

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 1706, in 
+ main(options)
+   File "/usr/bin/unattended-upgrade", line 1619, in main
+ log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
+   File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content
+ for line in fp.readlines():
+   File "/usr/lib/python3.6/codecs.py", line 321, in decode
+ (result, consumed) = self._buffer_decode(data, self.errors, final)
+ UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: 
invalid continuation byte

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1737635

Title:
  Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1706, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1619, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content
  for line in fp.readlines():
File "/usr/lib/python3.6/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: 
invalid continuation byte

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737635] [NEW] Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1706, in 
main(options)
  File "/usr/bin/unattended-upgrade", line 1619, in main
log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
  File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content
for line in fp.readlines():
  File "/usr/lib/python3.6/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: 
invalid continuation byte

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


** Tags: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1737635

Title:
  Invalid UTF-8 characters in dpkg's log crash unattended-upgrade.

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/2fa32547e0d8e7186a0a805e3db6f50317c0dafa 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1706, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1619, in main
  log_content = get_dpkg_log_content(logfile_dpkg, install_start_time)
File "/usr/bin/unattended-upgrade", line 1229, in get_dpkg_log_content
  for line in fp.readlines():
File "/usr/lib/python3.6/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 7912-7913: 
invalid continuation byte

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine

[antubis]

I am having the same issue. Ubuntu 17.10 with VLC. When seeking an mp4
file, at some point, always different, the video freezes, the mouse
cursor freezes and the PC become irresponsible. I sometimes am able to
recover by switching PC to Airplane mode. Don't know why but it unfreeze
it. But only sometimes.

I did try with the different video output but the issue keeps happening.
Ultimately I switched back to the default video player cause I don't
want to reboot my system every time I want to skip recaps.

My video card is Nvidia for what is worth.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1574354

Title:
  playing .mp4 in VLC freezes machine

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  VLC was running fine on 15.10 but since upgrading, video files (e.g.
  .mp4) play for a few minutes and then crash the whole machine (i.e. I
  have to power off and on). Possibly linked is that audio (in web pages
  or playing audio files thru Banshee) loops (stutters) for about a
  second every few minutes (but doesn't crash the machine).

  vlc-nox: /usr/bin/vlc

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  vlc:
Installed: 2.2.2-5
Candidate: 2.2.2-5
Version table:
   *** 2.2.2-5 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 19:20:41 2016
  InstallationDate: Installed on 2014-02-17 (797 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1736770] Re: debian-installer/main-menu changes priority

[Joshua Powers]

It looks like the installer is getting further now, however, failing on
kernel package install:

https://paste.ubuntu.com/26166359/

Shall we close this bug and open a new one for that issue?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1736770

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1736770] Re: debian-installer/main-menu changes priority

[Steve Langasek]

There are messages in that syslog pointing to a refusal from busybox tar
to unpack some symlinks.  There has been a new merge of busybox from
unstable after the datestamps in those logs.  Are the symptoms still the
same with the current daily image?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1736770

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Walter Lapchynski]

We need to talk about software here, not personal issues. You both are
going to stop attacking each other, defending yourself against each
other, and talk about software. If you cannot talk about the software
without getting these other issues intermingled here, do not comment at
all.

Since you seem to be concerned about the user experience, please
recognize the user experience for all the people looking at this bug
reports. Be nice.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  

[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

[Abraham]

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

Hi,

I can confirm this error. ibus is not loading neither the applet
appearing in Gnome Shell wayland session in Ubuntu 17.10. These are the
error messages I can find:

:~$ cat /var/log/kern.log |grep ibus*
Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

** This bug has been marked a duplicate of bug 1737618
   ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1727174

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  

[Touch-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+1340

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ibus (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1737618

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+1340

[Abraham]

Also attaching some crash debug logs found in /var/crash folder.

** Attachment added: "ibus-ui-gtk3 crash"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1737618/+attachment/5021481/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1737618

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737618] [NEW] ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+13

[Abraham]

Public bug reported:

Hi,

ibus is not loading neither the applet appearing in Gnome Shell wayland
session in Ubuntu 17.10. These are the error messages I can find:

:~$ cat /var/log/kern.log |grep ibus*
Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

I tried changing input method using im-config to xim and it did not
yield any positive results. Also, I remember one time, there was a
segmentation fault happened with ibus which I cannot reproduce again on
this system.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ibus-wayland 1.5.14-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: ndiswrapper
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Dec 12 02:20:20 2017
InstallationDate: Installed on 2017-11-22 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1737618

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737585] Re: ufw should not override procps' default of net.ipv4.tcp_syncookies=1

[Nils Toedtmann]

Sorry for only checking the latest LTS, didn't realize it had been fixed
in >= 17.04. Thx.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1737585

Title:
  ufw should not override procps' default of net.ipv4.tcp_syncookies=1

Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  2008 ufw decided to *disable* TCP SYN cookies by default in
  /etc/ufw/sysctl.conf, see
  https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565

  After a more detailed discussion that had started in 2006, procps
  *enabled* TCP SYN cookies by default in  /etc/sysctl.d/10-network-
  security.conf in 2009, see
  https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091

  No two packages should try to set conflicting defaults on the same
  sysctl without very good reason. This is a funny case where the base
  package procps uses a more secure default (SYN cookies enabled), and
  the firewall package ufw uses a less secure default (SYN cookies
  disabled) - one would expect the other way round. At least I would
  expect ufw not to *weaken* security settings.

  Regarding the question whether or not SYN cookies should be enabled
  (as opposed to the question which package should own this setting): I
  guess that the are lots of systems without ufw, and all of those run
  happily with procps' default net.ipv4.tcp_syncookies=1, or at least I
  could not find any bug reports that complained. The kernel only
  activates the mechanism once it thinks a syn flood is happening, so
  whatever the disadvantages of SYN cookies are, they only kick in under
  these circumstances.

  For all the above reasons I suggest ufw should not touch
  net.ipv4.tcp_syncookies and leave it however it is already set in
  /etc/sysctl.{conf,d/}

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737585] Re: ufw should not override procps' default of net.ipv4.tcp_syncookies=1

[Jamie Strandboge]

This was actually fixed earlier this year:
http://bazaar.launchpad.net/~jdstrand/ufw/trunk/revision/972 and patched
in Debian and Ubuntu via 0.35-3. I'm going to mark this as Fixed
Released.

Thanks for reporting this bug! :)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1737585

Title:
  ufw should not override procps' default of net.ipv4.tcp_syncookies=1

Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  2008 ufw decided to *disable* TCP SYN cookies by default in
  /etc/ufw/sysctl.conf, see
  https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565

  After a more detailed discussion that had started in 2006, procps
  *enabled* TCP SYN cookies by default in  /etc/sysctl.d/10-network-
  security.conf in 2009, see
  https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091

  No two packages should try to set conflicting defaults on the same
  sysctl without very good reason. This is a funny case where the base
  package procps uses a more secure default (SYN cookies enabled), and
  the firewall package ufw uses a less secure default (SYN cookies
  disabled) - one would expect the other way round. At least I would
  expect ufw not to *weaken* security settings.

  Regarding the question whether or not SYN cookies should be enabled
  (as opposed to the question which package should own this setting): I
  guess that the are lots of systems without ufw, and all of those run
  happily with procps' default net.ipv4.tcp_syncookies=1, or at least I
  could not find any bug reports that complained. The kernel only
  activates the mechanism once it thinks a syn flood is happening, so
  whatever the disadvantages of SYN cookies are, they only kick in under
  these circumstances.

  For all the above reasons I suggest ufw should not touch
  net.ipv4.tcp_syncookies and leave it however it is already set in
  /etc/sysctl.{conf,d/}

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737614] [NEW] Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop

[Abraham]

Public bug reported:

I have a new laptop HP-15-BS576TX which has this Intel Corporation
Sunrise Point-LP HD Audio.

00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio
[8086:9d71] (rev 21)

The laptop sound works perfectly fine in Windows 10 with realtek
drivers. However, in Ubuntu 17.10, the volume is significantly low, that
I've to scroll the volume slider above 100% mark in pulseaudio to the
maximum to get acceptable level of sound. I suspect the sound quality
also is low (mono-like), may be not coming from all speakers (perhaps
subwoofer exist for this model). Also alsamixer shows the speaker volume
at the maximum.

 Details about the audio hardware are below:

:~$ sudo lspci -vvv | grep -A 40 -i audio
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Hewlett-Packard Company Device 832b
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  /proc/asound/card0/codec#0 <==
Codec: Realtek ALC3227

==> /proc/asound/card0/codec#2 <==
Codec: Intel Kabylake HDMI

:~$  aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I have gone through Linux kernel sources ALSA and Snd-HDA lists and
unable to find any optimizations for this laptop.

Here is the relevant dmesg details:

[   15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   16.310510] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x19
[   16.310512] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   16.451397] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input9
[   16.451451] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input10
[   16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input11
[   16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input12
[   16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input13
[   16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input14
[   16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input15

Any further information needed, please let me know. Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: 
usr/share/alsa-base/alsa-info.sh]
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: ndiswrapper
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  admin2018   1246 F pulseaudio
CurrentDesktop: GNOME
Date: Tue Dec 12 00:46:12 2017
InstallationDate: Installed on 2017-11-22 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.24
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 832B
dmi.board.vendor: HP
dmi.board.version: 23.40
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd09/25/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.40:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-bs0xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: alsa amd64 apport-bug artful wayland-session

** Attachment added: 

[Touch-packages] [Bug 1737613] [NEW] doesn't work

[Pertti Ahvonen]

Public bug reported:

HP ProBook 4515s

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737613

Title:
  doesn't work

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  HP ProBook 4515s

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

** Patch added: "libgweather-lp1704533_zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/1704533/+attachment/5021454/+files/libgweather-lp1704533_zesty.debdiff

** Tags added: patch

** Description changed:

  [Impact]
  
  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the messages
  describing the weather type always be displayed in English.
  
  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".
  
  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.
  
  [Test Case]
  
-  * Install French language support
+  * Install French language support
  
-  * Start gnome-weather with:
-LANGUAGE=fr gnome-weather
-and find that the description of the weather type is displayed in
-English. 
+  * Start gnome-weather with:
+    LANGUAGE=fr gnome-weather
+    and find that the description of the weather type is displayed in
+    English.
  
-  * Install these packages from artful-proposed:
-- gir1.2-gweather-3.0
-- libgweather-3-6
-- libgweather-common
+  * Install these packages from -proposed:
+    - gir1.2-gweather-3.0
+    - libgweather-3-6
+    - libgweather-common
  
-  * Start gnome-weather with:
-LANGUAGE=fr gnome-weather
-and find that the description of the weather type is now displayed
-in French. 
+  * Start gnome-weather with:
+    LANGUAGE=fr gnome-weather
+    and find that the description of the weather type is now displayed
+    in French.
  
  [Regression Potential]
  
  None.
  
  [Original description]
  
  In Gnome Weather, part of it is not translated in french : cloudy, rain
  showers, etc. Should be : nuageux, pluie fine, etc.
  
  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under the
  extensions section.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

** Patch added: "libgweather-lp1704533_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/1704533/+attachment/5021452/+files/libgweather-lp1704533_xenial.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1353226] Re: [dash] On the dash the available space for app names is too small

[Rodrigo]

** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1353226

Title:
  [dash] On the dash the available space for app names is too small

Status in Ubuntu Translations:
  Fix Released
Status in Ubuntu UX:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  On the dash, System Settings is translated to Configuración del sistema.
  Configuración is too long, so it's cut as

  Configuració
  n del sistema

  That looks really bad. Maybe we can change the translation to "Ajustes
  de sistema", or just "Sistema".

  Screenshot: http://people.canonical.com/~john/lovely.png

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs

[Scott Moser]

Adding this to maas-images would look like this:
 http://paste.ubuntu.com/26165463/

but we'd avoid that as if zfs is officially supported, then it might as
well be in the default initramfs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592

Title:
  no zfs module in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.26.2-0ubuntu2

---
gnome-control-center (1:3.26.2-0ubuntu2) bionic; urgency=medium

  * debian/patches/search-provider-locale.patch: Backport patch from upstream
to set up the search provider such that setlocale() has been called early
enough for results to be translated. (LP: #1491787)

 -- Iain Lane   Mon, 11 Dec 2017 14:21:54 +

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1491787

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gettext source package in Artful:
  Invalid
Status in gnome-control-center source package in Artful:
  In Progress
Status in gnome-shell source package in Artful:
  Invalid

Bug description:
  [ Description ]

  In GNOME's activities overview, search entries from gnome-control-
  center aren't translated.

  [ Fix ]

  setlocale() wasn't being called until after the model that supplies
  search results was constructed. We fix the initialisation code to run
  slightly later, after setlocale() has been called.

  [ QA ]

  1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
  2. Hit super and type an "a"
  3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).

  [ Regression potential ]

  If we misunderstood when the initialisation phases in GtkApplication
  ran then there could be a race condition. You'd see that manifesting
  as either a crash in the search provider or no results being returned.
  Make sure there aren't crahes reported in errors.u.c.

  [ Original description ]

  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Confirmed
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  Edit the /etc/bluetooth/main.conf and disable the 'AutoEnable' option.
  Remove file 50-bluetooth-hci-auto-poweron.rules located in
  /lib/udev/rules.d. Now reboot the machine. The BT adapter shall be
  powered off now.

  [Regression Potential]

  Cannot think of any

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1737377] Re: Unknown tunnel mode "vti6"

[Simon Déziel]

Hello Christian,

On 2017-12-11 10:36 AM, ChristianEhrhardt wrote:
> Hi Simon,
> we are currently shuffling around responsibilities for iproute so extra 
> latencies might occur :-/.

I have no urgent need for this. I was simply experimenting with an
IPv6-only lab.

> 2. the Xenial kernel has this type disabled.
> If throwing in an HWE kernel [1] into xenial, does it then work for you?

The required module (ip6_vti) is in 4.4. Loading it and strace'ing the
ip link I got this:

socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 3
setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
setsockopt(3, SOL_SOCKET, SO_RCVBUF, [1048576], 4) = 0
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=1194, groups=}, [12]) = 0
write(2, ""..., 27Unknown tunnel mode "vti6"
) = 27
exit_group(-1)  = ?

I get the same on 4.13.0-19-generic from linux-image-virtual-
hwe-16.04-edge.

> 1. the iproute package needs fixes that came later than what is in Xenial:
> The package needs to be very close to the kernel version in general.
> Did you have any chance to test the newer 4.9 by forcing it into a Xenial 
> system if that works as well? If you need a ppa for that let me know and I'll 
> create one for you.

As a quick and dirty test, I installed Zesty's debs of iproute2 and
libelf1 on Xenial and that worked with both kernel 4.4 and 4.13.

Thanks,
Simon

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737377

Title:
  Unknown tunnel mode "vti6"

Status in iproute2 package in Ubuntu:
  New

Bug description:
  [Impact]

  Xenial users are unable to create vti6 tunnels.

  [Test case]

  1) Create a vti6 tunnel
   sudo ip tunnel add vti0 mode vti6 local :: remote fdd6:bdb4:5614::2 key 54
  2) No error should be displayed and "ip link" should show a new device named 
"vti0"

  The ip tunnel call currently fails with the error 'Unknown tunnel mode
  "vti6"' and no tunnel is created.

  [Other Info]

  vti6 mode is supported according to the man page:

  $ man ip-tunnel | grep vti6
 MODE :=  { ipip | gre | sit | isatap | vti | ip6ip6 | ipip6 | ip6gre | 
vti6 | any }
   Modes for IPv6 encapsulation available: ip6ip6, ipip6, 
ip6gre, vti6, and any.

  iproute2 4.9.0-1ubuntu2 on *Artful* has no problem creating vti6
  tunnels.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  $ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.3
Candidate: 4.3.0-1ubuntu3.16.04.3
Version table:
   *** 4.3.0-1ubuntu3.16.04.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.0-1ubuntu3.16.04.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   4.3.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  9 21:55:27 2017
  InstallationDate: Installed on 2016-12-06 (368 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.iproute2.rt_tables: [modified]
  mtime.conffile..etc.iproute2.rt_tables: 2016-12-21T17:41:32.869321

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1737589] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Marius NGADOM]

Please how to ga back to python??


Cordialement
*Marius NGADOM*
Web & Mobile developer,
Marketer, Community Manager
Tel : (237) 699 120 192 - 243 199 566
Mail : marius.nga...@gmail.com
Site : http://www.lecamerounaisinfo.com

*Si vous voulez aller vite: allez-y seul, si vous voulez aller loin:
allez-y ensemble ...*


2017-12-11 19:48 GMT+01:00 Mattia Rizzolo :

> indeed, having the `python` in the path being a python3 is not supported.
> Don't do it.
>
> ** Changed in: libxml2 (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737589
>
> Title:
>   package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
>   install/upgrade: subprocess new pre-removal script returned error exit
>   status 1
>
> Status in libxml2 package in Ubuntu:
>   Invalid
>
> Bug description:
>   i have problem to update my Ubuntu
>
>   i have use some code line on internet to make my Ubuntu see my Iphone
>   i think i have alias python 2 to 3 form installation i have made
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
>   Uname: Linux 4.10.10-041010-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.12
>   Architecture: amd64
>   Date: Mon Dec 11 19:20:39 2017
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-12-30 (346 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.3
>apt  1.2.24
>   SourcePackage: libxml2
>   Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
> install/upgrade: subprocess new pre-removal script returned error exit
> status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/
> 1737589/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737589

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  i have problem to update my Ubuntu

  i have use some code line on internet to make my Ubuntu see my Iphone
  i think i have alias python 2 to 3 form installation i have made

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  Uname: Linux 4.10.10-041010-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Mon Dec 11 19:20:39 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-12-30 (346 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737601] [NEW] system hangs immediately when keyring error appears

[John A Peters]

Public bug reported:

Right after the system launches (unity i think) the comoputer hangs.  I
have mouse only. nothing works. Error message on screen is a Keyring
error dialog but the buttons don't activate. all is dead.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
CasperVersion: 1.376
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Dec 11 18:59:47 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0309
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A/USB 3.1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Dec 11 18:52:50 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1737601

Title:
  system hangs immediately when keyring error appears

Status in xorg package in Ubuntu:
  New

Bug description:
  Right after the system launches (unity i think) the comoputer hangs.
  I have mouse only. nothing works. Error message on screen is a Keyring
  error dialog but the buttons don't activate. all is dead.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec 11 18:59:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7660D] [1043:8526]
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: American Megatrends Inc.

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

** Bug watch added: GNOME Bug Tracker #789867
   https://bugzilla.gnome.org/show_bug.cgi?id=789867

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (probably fresh 

Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

On 12/7/2017 8:15 PM, bodhi.zazen wrote:
> Wayland , upstream, does not and will not support running graphical
> applications, as root, from the terminal using sudo , period, end of story.
> There are other mechanisms to grant graphical applications root access, but
> again the application itself is not going to run as root.

Yes, it does, as you can easily test by suing to root and running gedit.

> And if you take your fat head out of your ass and look upstream you will
> see every bug files against wayland regarding the problem of running
> graphical applications with sudo has been closed as either not a bug or
> wont fix.

https://bugs.freedesktop.org/show_bug.cgi?id=91071 is not.

Neither is https://bugzilla.gnome.org/show_bug.cgi?id=789867

And there it is noted that wayland does not explicitly allow or deny
root applications.

> On the forums, we would ban him for a period of time, 1-3 months
> depending on his behavior. Often we would start with a week or a month,
> but on his return he would start right back up with his violations, and
> we would extend the ban. Eventually he would cool down and we would
> restore his  privileges.

Well now you're just lieing.  You banned me permanently one time because
I dared to point out that you incorrectly closed another user's thread
for breaking the rules when he did no such thing.

> reference 32 is here https://lwn.net/Articles/517375/

This talks about weston not having to be run as root; not disallowing
client applications running as root.

> The blog is here http://mupuf.org/blog/2014/02/19/wayland-compositors-
> why-and-how-to-handle/

This talks about having weston be able to isolate different clients from
interfering with one another.  Nowhere does it talk about refusing
clients with uid=0.

> Please could both of you take a deep breath and stop the personal
> attacks and aggressive language?

I haven't made any personal attacks.  What I have done is point out that
this misconception that disallowing root applications is not true; that
gdm fails to perform its job as described by its man page.  This
therefore is, ipso facto, a bug, whether or not you agree with the
terrible user facing consequences it has.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. 

[Touch-packages] [Bug 1737589] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Mattia Rizzolo]

indeed, having the `python` in the path being a python3 is not supported.
Don't do it.

** Changed in: libxml2 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737589

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in libxml2 package in Ubuntu:
  Invalid

Bug description:
  i have problem to update my Ubuntu

  i have use some code line on internet to make my Ubuntu see my Iphone
  i think i have alias python 2 to 3 form installation i have made

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  Uname: Linux 4.10.10-041010-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Mon Dec 11 19:20:39 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-12-30 (346 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs

[Scott Moser]

As a work around you can specifically add the zfs module (if its in your
kernel) with:

$ cat /etc/initramfs-tools/hooks/zfs
#!/bin/sh
. /usr/share/initramfs-tools/hook-functions

manual_add_modules zfs

$ update-initramfs -u -k all

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592

Title:
  no zfs module in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/335046

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592

Title:
  no zfs module in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737592] [NEW] no zfs module in initramfs

[Scott Moser]

Public bug reported:

zfs support exists in Ubuntu kernels for 16.04 and later, but the
default initramfs build does not include this module.

Other common filesystems are included.

As a small piece of information:
$ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
3.2M/lib/modules/4.13.0-17-generic/kernel/zfs/


ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools-core 0.125ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 11 13:05:15 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (872 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

** Description changed:

  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.
  
  Other common filesystems are included.
+ 
+ As a small piece of information:
+ $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
+ 3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1737592

Title:
  no zfs module in initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1734167

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://;

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737589] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737589

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in libxml2 package in Ubuntu:
  New

Bug description:
  i have problem to update my Ubuntu

  i have use some code line on internet to make my Ubuntu see my Iphone
  i think i have alias python 2 to 3 form installation i have made

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  Uname: Linux 4.10.10-041010-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Mon Dec 11 19:20:39 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-12-30 (346 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737589] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Marius NGADOM]

Public bug reported:

i have problem to update my Ubuntu

i have use some code line on internet to make my Ubuntu see my Iphone i
think i have alias python 2 to 3 form installation i have made

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
Uname: Linux 4.10.10-041010-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Mon Dec 11 19:20:39 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-12-30 (346 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libxml2
Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737589

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in libxml2 package in Ubuntu:
  New

Bug description:
  i have problem to update my Ubuntu

  i have use some code line on internet to make my Ubuntu see my Iphone
  i think i have alias python 2 to 3 form installation i have made

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.3
  Uname: Linux 4.10.10-041010-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Mon Dec 11 19:20:39 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-12-30 (346 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.3 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty

[Bug Watch Updater]

** Changed in: jasper (Debian)
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jasper in Ubuntu.
https://bugs.launchpad.net/bugs/1612835

Title:
  Please remove jasper from Zesty

Status in digikam package in Ubuntu:
  Fix Released
Status in jasper package in Ubuntu:
  Fix Released
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kimageformats package in Ubuntu:
  Fix Released
Status in kopete package in Ubuntu:
  Fix Released
Status in digikam package in Debian:
  Fix Released
Status in jasper package in Debian:
  Fix Released
Status in kde4libs package in Debian:
  Fix Released
Status in kimageformats package in Debian:
  Fix Released
Status in kopete package in Debian:
  Fix Released

Bug description:
  Jasper has been removed from Debian. It would be great if jasper's
  source and all binary packages could be removed in Ubuntu before 17.04
  is released. Jasper has a long security history and shouldn't remain,
  unmaintained, in universe.

  
https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html
  /jasper-rm.html

  As of 2017-02-10, all reverse depends in Zesty have been updated to
  drop dependencies on jasper:

  $ reverse-depends -b src:jasper
  No reverse dependencies found

  
  == Original Report ==

  # reverse-depends -b src:jasper
  Reverse-Build-Depends
  =
  * digikam   (for libjasper-dev)
  * kde4libs  (for libjasper-dev)
  * kimageformats (for libjasper-dev)
  * kopete(for libjasper-dev)

  The last 4 are KDE stuff. Since these packages have already removed
  their jasper dependency in Debian, you should be able to just copy
  what's already been done.

  February 2017 Update
  
  Here are the remaining commits from Debian that need to be applied in Ubuntu:

  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d
  
https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b

  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186
  
https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.14.1-0ubuntu2

---
iproute2 (4.14.1-0ubuntu2) bionic; urgency=medium

  * d/p/1002-ubuntu-poc-fan-driver-vxlan.patch: update to fix fan-map
processing in vxlan_parse_opt in new version of iproute2.

iproute2 (4.14.1-0ubuntu1) bionic; urgency=medium

  [ Christian Ehrhardt ]
  * Merge from Debian unstable AND latest upstream (LP: #1726730)
(LP: #1735032). Remaining changes:
- debian/patches/1000-ubuntu-poc-fan-driver.patch
  Ubuntu FAN driver support V2 (LP 1439706)
- debian/patches/1001-ubuntu-poc-fan-driver-v3.patch
  Ubuntu FAN driver support V3 (LP 1470091)
- debian/patches/1002-ubuntu-poc-fan-driver-vxlan.patch
  Ubuntu FAN driver support VXLAN V4.
  * Dropped changes (upstream now)
- Fix ip maddr show (LP 1732032):
  - d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
  - d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
uninitialized data
  - d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
by device
- d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
  explicitly for UINT16_MAX (LP 1735158)
  * Added changes
- drop 0003-fix-segfault-with-iptables-1.6.patch (upstream)
- update d/p/*ubuntu-poc-fan-driver*.patch to latest upstream
- d/control: fix lintian priority-extra-is-replaced-by-priority-optional
- d/t/control: d/t/testsuite.sh: add iproute2 testsuite as autopkgtest
- d/p/fix-testsuite-broken-pipes.patch: avoid broken pipe errors in tests

  [ Julian Wollrath  ]
  * Added changes based on suggested 4.14.1-0 changes for Debian in bug 879854
- dropped d/p/0001-Add-moo-feature.patch (isn't needed)
- follow upstream dropping the old ip documentation (of 1999)
- d/rules: consider DEB_*_GNU_TYPE from env
- d/control: bump debhelper dependency and Standards-Version
- set compat level 10 (no further changes needed)

iproute2 (4.9.0-2.1) unstable; urgency=high

  * Non-maintainer upload.
  * Backport upstream commit 97a02cabef to fix segfault with iptables 1.6;
the xtables_globals structure needs to have its new member compat_rev
initialized. (Closes: #868059)
  * Sync include/xtables.h from iptables to make sure the right offset is
used when accessing structure members defined in libxtables. One could
get “Extension does not know id …” otherwise. (See also: #868059)

iproute2 (4.9.0-2) unstable; urgency=medium

  * Let uscan verify signature of upstream tarball
  * Add debian/upstream/metadata
  * Remove myself from uploaders
  * Reinstate Alexander Wirt as primary maintainer

 -- Christian Ehrhardt   Mon, 11 Dec
2017 12:13:50 +0100

** Changed in: iproute2 (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1735032

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 package in Debian:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1726730] Re: IPRoute pkg is in different version than kernel

[Launchpad Bug Tracker]

This bug was fixed in the package iproute2 - 4.14.1-0ubuntu2

---
iproute2 (4.14.1-0ubuntu2) bionic; urgency=medium

  * d/p/1002-ubuntu-poc-fan-driver-vxlan.patch: update to fix fan-map
processing in vxlan_parse_opt in new version of iproute2.

iproute2 (4.14.1-0ubuntu1) bionic; urgency=medium

  [ Christian Ehrhardt ]
  * Merge from Debian unstable AND latest upstream (LP: #1726730)
(LP: #1735032). Remaining changes:
- debian/patches/1000-ubuntu-poc-fan-driver.patch
  Ubuntu FAN driver support V2 (LP 1439706)
- debian/patches/1001-ubuntu-poc-fan-driver-v3.patch
  Ubuntu FAN driver support V3 (LP 1470091)
- debian/patches/1002-ubuntu-poc-fan-driver-vxlan.patch
  Ubuntu FAN driver support VXLAN V4.
  * Dropped changes (upstream now)
- Fix ip maddr show (LP 1732032):
  - d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
  - d/p/1004-ip-maddr-avoid-uninitialized-data.patch: avoid accessing
uninitialized data
  - d/p/1005-ip-maddr-fix-filtering-by-device.patch: fix filtering
by device
- d/p/1006-fix-undeclared-UINT16_MAX.patch: FTBFS: tc: include stdint.h
  explicitly for UINT16_MAX (LP 1735158)
  * Added changes
- drop 0003-fix-segfault-with-iptables-1.6.patch (upstream)
- update d/p/*ubuntu-poc-fan-driver*.patch to latest upstream
- d/control: fix lintian priority-extra-is-replaced-by-priority-optional
- d/t/control: d/t/testsuite.sh: add iproute2 testsuite as autopkgtest
- d/p/fix-testsuite-broken-pipes.patch: avoid broken pipe errors in tests

  [ Julian Wollrath  ]
  * Added changes based on suggested 4.14.1-0 changes for Debian in bug 879854
- dropped d/p/0001-Add-moo-feature.patch (isn't needed)
- follow upstream dropping the old ip documentation (of 1999)
- d/rules: consider DEB_*_GNU_TYPE from env
- d/control: bump debhelper dependency and Standards-Version
- set compat level 10 (no further changes needed)

iproute2 (4.9.0-2.1) unstable; urgency=high

  * Non-maintainer upload.
  * Backport upstream commit 97a02cabef to fix segfault with iptables 1.6;
the xtables_globals structure needs to have its new member compat_rev
initialized. (Closes: #868059)
  * Sync include/xtables.h from iptables to make sure the right offset is
used when accessing structure members defined in libxtables. One could
get “Extension does not know id …” otherwise. (See also: #868059)

iproute2 (4.9.0-2) unstable; urgency=medium

  * Let uscan verify signature of upstream tarball
  * Add debian/upstream/metadata
  * Remove myself from uploaders
  * Reinstate Alexander Wirt as primary maintainer

 -- Christian Ehrhardt   Mon, 11 Dec
2017 12:13:50 +0100

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1726730

Title:
  IPRoute pkg is in different version than kernel

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  Hello,

  At the moment there is a problem with Iproute package in Zesty and
  artful.

  In Zesty the kernel version is 4.10.0, and the Iproute package is 4.9.0. 
  In Artful the kernel version is 4.13, and the Iproute is 4.9.0 too. 

  This is causing some problems in the BPF/XDP setup, some code is in
  the kernel but doesn't have the same version in Iproute, so it'll
  fail.

  Found the problem using cilium project
   and the problem was
  validated by Daniel Borkmann (iproute mantainer)

  I didn't find any related bug related to updating. If you need help to
  test/update, I can help you.

  Regards and many thanks.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 189565] Re: ufw enables syncookies by default, which is not considered a great idea

[Nils Toedtmann]

Requesting to revert and leaving this to procps:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1737585

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/189565

Title:
  ufw enables syncookies by default, which is not considered a great
  idea

Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ufw

  The default configuration of ufw enables syncookies, which is not
  considered a great idea by the developers of the Linux network stack.
  For details see this thread:

  http://article.gmane.org/gmane.linux.network/85365

  From that message:

  > Syncookies are discouraged these days. They disable too many 
  > valuable TCP features (window scaling, SACK) and even without them 
  > the kernel is usually strong enough to defend against syn floods
  > and systems have much more memory than they used to be.

  Regards,
  Daniel

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

[Nils Toedtmann]

I filed a request for ufw not to override
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1737585

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/57091

Title:
  proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to
  permit SYN flood defense...

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  This is intended to be a 'wishlist' wulnerability -- w.r.t. procps and
  Edgy.

  In my opinion,the /etc/sysctl.conf should have
  'proc/sys/net/ipv4/tcp_syncookies=1' in order to permit the linux
  SYNcookies syn-flood trivial DoS attack to be mitigated as-necessary,
  by default.

  Note that the disadvantages of connections initiated w/ SYNcookies
  enabled only apply when the system is under attack (SYN queue getting
  rather full), as the syncookies reply-with-only-one-SYN+ACK behaviour
  only 'kicks in' when the system has a SYN_RECVD backlog problem.  (If
  SYNcookies were not permitted incoming TCP connections have a very low
  chance of succeeding at all while under SYN-flood attack).

  Without this setting enabled, any TCP services on the machine can be
  DoSed from a dial-up line sending a stream of SYN packets from weird
  source addresses to open TCP ports like Samba/VNC/http/whatever

  
  Does anybody have any legitimate reason tcp_syncookies should be disabled?

  Some people claimed that SYNcookies break some RFCs once but I have
  not seen any evidence to this effect, only notes from djb saying that
  this is not true.

  Comments wanted please ;-)
  Thankyou in advance,
  -- enyc

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1724152] Re: ISST-LTE: pVM: aureport couldn't get the right auid from the audit log on ubuntu16.04

[Tyler Hicks]

@Pavithra Hello! I believe that your `aureport -l` is showing that the
bug is not fixed although I suspect that you did not install the auditd
package from zesty-proposed. Can you reply with the version of auditd
that was installed when you ran aureport?

It should be version 1:2.6.6-1ubuntu1.1 which can be installed by
enabling the proposed pocket:


  https://wiki.ubuntu.com/Testing/EnableProposed

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
https://bugs.launchpad.net/bugs/1724152

Title:
  ISST-LTE: pVM: aureport couldn't get the right auid from the audit log
  on ubuntu16.04

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in audit package in Ubuntu:
  Invalid
Status in audit source package in Xenial:
  Fix Committed
Status in audit source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  The aureport command, part of the audit userspace utilities,
  incorrectly reports the user id of successful logins. "-1" is printed
  instead of the expected user id.

  [Test Case]

  As root, run `login`. Proceed as follows:

  1. Login with a blank username and any password
  2. Login with an invalid username and any password
  3. Login with a valid username and an invalid password
  4. Login with a valid username and a valid password
  5. Exit from the login shell
  6. Run `aureport -l` and examine the last for login records

  An unpatched aureport will print the following:

  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:45:32 UNKNOWN ? /dev/pts/8 /bin/login no 97
  3. 10/17/2017 23:45:39 UNKNOWN ? /dev/pts/8 /bin/login no 99
  4. 10/17/2017 23:45:45 tyhicks ? /dev/pts/8 /bin/login no 101
  5. 10/17/2017 23:45:49 -1 ? /dev/pts/8 /bin/login yes 107

  A patch aureport will print the correct output:

  Login Report
  
  # date time auid host term exe success event
  
  ...
  2. 10/17/2017 23:52:44 UNKNOWN ? /dev/pts/8 /bin/login no 165
  3. 10/17/2017 23:52:52 UNKNOWN ? /dev/pts/8 /bin/login no 167
  4. 10/17/2017 23:52:58 tyhicks ? /dev/pts/8 /bin/login no 169
  5. 10/17/2017 23:53:02 1000 ? /dev/pts/8 /bin/login yes 175

  Note the "1000" in the auid column on the #5 row. It should *not* be
  "-1".

  [Regression Potential]

  The regression potential is limited due to the change only affecting a
  single line of code, the fix comes from upstream, and that the
  aureport utility is not critical.

  [Original Report]

  == Comment: #0 - Miao Tao Feng  - 2016-11-23 02:46:25 ==
  When we develop new testcase for audit, we found that command "aureport -l" 
print out wrong auid "-1"  on ubuntu16.04  and it should be 1000 according to 
the audit.log.

  The following are details:

  root@roselp2:~# aureport -l

  Login Report
  
  # date time auid host term exe success event
  
  1. 11/23/2016 02:20:12 -1 10.33.24.118 /dev/pts/0 /usr/sbin/sshd yes 18

  The auid "-1" on the above line should be "1000? according to the
  audit.log.

  root@roselp2:~# grep ":18" /var/log/audit/audit.log
  type=USER_LOGIN msg=audit(1479889212.292:18): pid=4177 uid=0 auid=1000 ses=4 
msg='op=login id=1000 exe="/usr/sbin/sshd" hostname=10.33.24.118 
addr=10.33.24.118 terminal=/dev/pts/0 res=success'

  root@roselp2:~# dpkg -s auditd
  Package: auditd
  Status: install ok installed
  Priority: extra
  Section: admin
  Installed-Size: 1051
  Maintainer: Ubuntu Developers 
  Architecture: ppc64el
  Source: audit
  Version: 1:2.4.5-1ubuntu2
  Depends: lsb-base (>= 3.0-6), mawk | gawk, init-system-helpers (>= 1.18~), 
libaudit1 (>= 1:2.4.2), libauparse0 (>= 1:2.3.1), libc6 (>= 2.17)
  Suggests: audispd-plugins

  root@roselp2:~# uname -a
  Linux roselp2 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  root@roselp2:~# service auditd status
  ? auditd.service - Security Auditing Service
     Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: e
     Active: active (running) since Wed 2016-11-23 02:19:21 CST; 19s ago
   Main PID: 4085 (auditd)
     CGroup: /system.slice/auditd.service
     ??4085 /sbin/auditd -n

  Nov 23 02:19:21 roselp2 auditctl[4086]: enabled 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: failure 1
  Nov 23 02:19:21 roselp2 auditctl[4086]: pid 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: rate_limit 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_limit 320
  Nov 23 02:19:21 roselp2 auditctl[4086]: lost 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog 0
  Nov 23 02:19:21 roselp2 auditctl[4086]: backlog_wait_time 15000
  Nov 23 02:19:21 roselp2 systemd[1]: Started 

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete
Status in util-linux source package in Xenial:
  Incomplete

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010

[Touch-packages] [Bug 1737585] [NEW] ufw should not override procps' default of net.ipv4.tcp_syncookies=1

[Nils Toedtmann]

Public bug reported:

2008 ufw decided to *disable* TCP SYN cookies by default in
/etc/ufw/sysctl.conf, see
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565

After a more detailed discussion that had started in 2006, procps
*enabled* TCP SYN cookies by default in  /etc/sysctl.d/10-network-
security.conf in 2009, see
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091

No two packages should try to set conflicting defaults on the same
sysctl without very good reason. This is a funny case where the base
package procps uses a more secure default (SYN cookies enabled), and the
firewall package ufw uses a less secure default (SYN cookies disabled) -
one would expect the other way round. At least I would expect ufw not to
*weaken* security settings.

Regarding the question whether or not SYN cookies should be enabled (as
opposed to the question which package should own this setting): I guess
that the are lots of systems without ufw, and all of those run happily
with procps' default net.ipv4.tcp_syncookies=1, or at least I could not
find any bug reports that complained. The kernel only activates the
mechanism once it thinks a syn flood is happening, so whatever the
disadvantages of SYN cookies are, they only kick in under these
circumstances.

For all the above reasons I suggest ufw should not touch
net.ipv4.tcp_syncookies and leave it however it is already set in
/etc/sysctl.{conf,d/}

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1737585

Title:
  ufw should not override procps' default of net.ipv4.tcp_syncookies=1

Status in ufw package in Ubuntu:
  New

Bug description:
  2008 ufw decided to *disable* TCP SYN cookies by default in
  /etc/ufw/sysctl.conf, see
  https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/189565

  After a more detailed discussion that had started in 2006, procps
  *enabled* TCP SYN cookies by default in  /etc/sysctl.d/10-network-
  security.conf in 2009, see
  https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091

  No two packages should try to set conflicting defaults on the same
  sysctl without very good reason. This is a funny case where the base
  package procps uses a more secure default (SYN cookies enabled), and
  the firewall package ufw uses a less secure default (SYN cookies
  disabled) - one would expect the other way round. At least I would
  expect ufw not to *weaken* security settings.

  Regarding the question whether or not SYN cookies should be enabled
  (as opposed to the question which package should own this setting): I
  guess that the are lots of systems without ufw, and all of those run
  happily with procps' default net.ipv4.tcp_syncookies=1, or at least I
  could not find any bug reports that complained. The kernel only
  activates the mechanism once it thinks a syn flood is happening, so
  whatever the disadvantages of SYN cookies are, they only kick in under
  these circumstances.

  For all the above reasons I suggest ufw should not touch
  net.ipv4.tcp_syncookies and leave it however it is already set in
  /etc/sysctl.{conf,d/}

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Dimitri John Ledkov]

** Summary changed:

- systemd journal should be persistent by default: /var/log/journal should be 
created; remove rsyslog from default installs
+ systemd journal should be persistent by default: /var/log/journal should be 
created

** No longer affects: ubuntu-meta (Ubuntu)

** Also affects: systemd (Ubuntu Bionic)
   Importance: Wishlist
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Steve Langasek]

As I understand it, this change is wanted as an SRU into 16.04.  This
will need a test case and a description of regression potential.
Knowing nothing about how to guard CPUs, how would we go about
reproducing the problem?

** Also affects: util-linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: util-linux (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1732865

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Incomplete
Status in util-linux source package in Xenial:
  Incomplete

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [

[Touch-packages] [Bug 1120611] iPhone X (64 GB)

[Roberto BG]

** Attachment added: "B18F1C3BC27CFBED.jpg"
   
https://bugs.launchpad.net/bugs/1120611/+attachment/5021366/+files/B18F1C3BC27CFBED.jpg

** Attachment added: "B18F1C3BC27CFBED2.jpg"
   
https://bugs.launchpad.net/bugs/1120611/+attachment/5021367/+files/B18F1C3BC27CFBED2.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1120611

Title:
  [Aspire 5920G, Realtek ALC1200, White Digital Out, HDMI] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 12.10
  N: Impossibile trovare il pacchetto pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic i686
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roberto1668 F pulseaudio
  Date: Sat Feb  9 22:03:45 2013
  InstallationDate: Installed on 2013-02-09 (0 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Audio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roberto1668 F pulseaudio
  Symptom_Jack: White Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Aspire 5920G, Realtek ALC1200, White Digital Out, HDMI] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3811
  dmi.board.name: Chapala
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3811:bd03/14/2008:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 5920G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1718890] Re: name resolution stops working

[Sebastien Bacher]

thank you for your bug report. So the issue there is the same as in the
upstream ticket, that you expect the lookups to always be done using the
servers in the order of what is in resolv.conf? if so could you update
the title to state that/what you believe the problem to be exactly?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718890

Title:
  name resolution stops working

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  System: Ubuntu 17.10 beta
  DNS server hosts an internal and an external domain (the internal is used for 
internal purposes).

  Name resolution works for a while. Every now and then, the name resolution 
stops working.
  This issue was reported in 17.04 but no suggestion for resolv has worked.

  In 17.10 the symptoms are the same, the duration till it happens are
  longer (about 1.5 days).

  restarting systemd-resolved solves the issue temporarily. However,
  this should not be required at all.

  Happens on a fresh install

  Setup:

  DNS serves rsb.at and rsb.intern
  Server www.rsb.at can be reached even when internal resolution fails.
  Seems that the internal DNS server (the first in the line) is not queried 
first.
  If so, an rsb.intern address will not be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu10
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 11:05:57 2017
  InstallationDate: Installed on 2017-09-05 (16 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2017-09-06T23:14:52.682864

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737582] Re: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vg

[Sistemas]

** Description changed:

  Hi:
  
  We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
  But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
  Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on 
screen.
  It seems there is an error related to LVM, but We don't know what.
  I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"
  
  About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
  I restarted the server and try several things but no luck.
  
  Ubuntu versión is:
  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.4 LTS
  Release: 14.04
  Codename: trusty
  
  Version of lvm package is:
  # dpkg -l | grep lvm
  ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager
  
+ I can see the LV is mounted:
+ # mount | grep /opt
+ /dev/mapper/vg--opt--zimbra-lv--opt--zimbra on /opt type ext4 (rw)
+ 
+ There are LVs that they shouldn't exist:
+ # ls -l /dev/mapper
+ total 0
+ crw--- 1 root root 10, 236 Dec 11 03:13 control
+ lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-lv--opt--zimbra 
-> ../dm-1
+ lrwxrwxrwx 1 root root   7 Dec 11 03:13 
vg--opt--zimbra-lv--opt--zimbra-real -> ../dm-0
+ lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-opt--snapshot -> 
../dm-3
+ lrwxrwxrwx 1 root root   7 Dec 11 03:13 vg--opt--zimbra-opt--snapshot-cow 
-> ../dm-2
+ 
+ 
+ Too much devices in /dev/disk:
+ # ls -lR /dev/disk/
+ /dev/disk/:
+ total 0
+ drwxr-xr-x 2 root root 140 Dec 11 03:13 by-id
+ drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partlabel
+ drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partuuid
+ drwxr-xr-x 2 root root 100 Dec 11 03:13 by-uuid
+ 
+ /dev/disk/by-id:
+ total 0
+ lrwxrwxrwx 1 root root  9 Dec 11 03:13 ata-QEMU_DVD-ROM_QM3 -> ../../sr0
+ lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-name-vg--opt--zimbra-lv--opt--zimbra -> ../../dm-1
+ lrwxrwxrwx 1 root root 10 Dec 11 10:27 dm-name-vg--opt--zimbra-opt--snapshot 
-> ../../dm-3
+ lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZ9E3YnxMBSQasz7G0mUkcWQa6tQhSmggA -> 
../../dm-1
+ lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZCRr8AQtnx7QpnAjSCEp8Dikr7zapGgmL -> 
../../dm-3
+ 
+ /dev/disk/by-partlabel:
+ total 0
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 primary -> ../../vdc1
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 PRIMARY -> ../../vdb1
+ 
+ /dev/disk/by-partuuid:
+ total 0
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 59ee8853-ae0e-4a7f-90d1-f1e5a8e4489d 
-> ../../vdb1
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 9669fe59-0ab9-4e5c-b559-3a5f7e70cbf0 
-> ../../vdc1
+ 
+ /dev/disk/by-uuid:
+ total 0
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 5d485a10-6f17-48f6-b9a2-260b8aa09d49 
-> ../../vda1
+ lrwxrwxrwx 1 root root 10 Dec 11 10:27 9aa61566-8f53-4201-8b74-8401ce4f3985 
-> ../../dm-1
+ lrwxrwxrwx 1 root root 10 Dec 11 03:13 ee2649c4-818c-448f-aa9a-41dc42aad7b2 
-> ../../vdc1
+ 
+ 
+ I tried to remove them with lvremove, but no error message nor other kind of 
information.
+ 
+ 
  
  Any idea if this problem is related with the error on dmesg?
  Any idea to resolve it?
  
  Regards

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1737582

Title:
  We have a server with a volume Group (VG) and two logical volumes
  (LV). About two 11 days ago it worked fine and we could see
  information when we run "lvs -a" or "vgs -a", but now nothing is
  shown.

Status in upstart package in Ubuntu:
  New

Bug description:
  Hi:

  We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
  But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
  Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on 
screen.
  It seems there is an error related to LVM, but We don't know what.
  I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"

  About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
  I restarted the server and try several things but no luck.

  Ubuntu versión is:
  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.4 LTS
  Release: 14.04
  Codename: trusty

  Version of lvm package is:
  # dpkg -l | grep lvm
  ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager

  I can see the LV is mounted:
  # mount | grep 

[Touch-packages] [Bug 1737582] Re: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vg

[Sistemas]

Ubuntu versión is:
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename:   trusty

Version of lvm package is:
# dpkg -l | grep lvm
ii  lvm2  2.02.98-6ubuntu2  
amd64Linux Logical Volume Manager


** Description changed:

  Hi:
  
  We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
  But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
  Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on 
screen.
  It seems there is an error related to LVM, but We don't know what.
  I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"
  
  About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
  I restarted the server and try several things but no luck.
  
+ Ubuntu versión is:
+ #lsb_release -a
+ No LSB modules are available.
+ Distributor ID: Ubuntu
+ Description: Ubuntu 14.04.4 LTS
+ Release: 14.04
+ Codename: trusty
+ 
+ Version of lvm package is:
+ # dpkg -l | grep lvm
+ ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager
+ 
+ 
  Any idea if this problem is related with the error on dmesg?
  Any idea to resolve it?
  
  Regards

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1737582

Title:
  We have a server with a volume Group (VG) and two logical volumes
  (LV). About two 11 days ago it worked fine and we could see
  information when we run "lvs -a" or "vgs -a", but now nothing is
  shown.

Status in upstart package in Ubuntu:
  New

Bug description:
  Hi:

  We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
  But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
  Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on 
screen.
  It seems there is an error related to LVM, but We don't know what.
  I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"

  About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
  I restarted the server and try several things but no luck.

  Ubuntu versión is:
  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.4 LTS
  Release: 14.04
  Codename: trusty

  Version of lvm package is:
  # dpkg -l | grep lvm
  ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager

  I can see the LV is mounted:
  # mount | grep /opt
  /dev/mapper/vg--opt--zimbra-lv--opt--zimbra on /opt type ext4 (rw)

  There are LVs that they shouldn't exist:
  # ls -l /dev/mapper
  total 0
  crw--- 1 root root 10, 236 Dec 11 03:13 control
  lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-lv--opt--zimbra 
-> ../dm-1
  lrwxrwxrwx 1 root root   7 Dec 11 03:13 
vg--opt--zimbra-lv--opt--zimbra-real -> ../dm-0
  lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-opt--snapshot -> 
../dm-3
  lrwxrwxrwx 1 root root   7 Dec 11 03:13 vg--opt--zimbra-opt--snapshot-cow 
-> ../dm-2

  
  Too much devices in /dev/disk:
  # ls -lR /dev/disk/
  /dev/disk/:
  total 0
  drwxr-xr-x 2 root root 140 Dec 11 03:13 by-id
  drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partlabel
  drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partuuid
  drwxr-xr-x 2 root root 100 Dec 11 03:13 by-uuid

  /dev/disk/by-id:
  total 0
  lrwxrwxrwx 1 root root  9 Dec 11 03:13 ata-QEMU_DVD-ROM_QM3 -> ../../sr0
  lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-name-vg--opt--zimbra-lv--opt--zimbra -> ../../dm-1
  lrwxrwxrwx 1 root root 10 Dec 11 10:27 dm-name-vg--opt--zimbra-opt--snapshot 
-> ../../dm-3
  lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZ9E3YnxMBSQasz7G0mUkcWQa6tQhSmggA -> 
../../dm-1
  lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZCRr8AQtnx7QpnAjSCEp8Dikr7zapGgmL -> 
../../dm-3

  /dev/disk/by-partlabel:
  total 0
  lrwxrwxrwx 1 root root 10 Dec 11 03:13 primary -> ../../vdc1
  lrwxrwxrwx 1 root root 10 Dec 11 03:13 PRIMARY -> ../../vdb1

  /dev/disk/by-partuuid:
  total 0
  lrwxrwxrwx 1 root root 10 Dec 11 03:13 59ee8853-ae0e-4a7f-90d1-f1e5a8e4489d 
-> ../../vdb1
  lrwxrwxrwx 1 root root 10 Dec 11 03:13 9669fe59-0ab9-4e5c-b559-3a5f7e70cbf0 
-> ../../vdc1

  /dev/disk/by-uuid:
  total 0
  lrwxrwxrwx 1 root root 10 Dec 11 03:13 5d485a10-6f17-48f6-b9a2-260b8aa09d49 
-> ../../vda1
  lrwxrwxrwx 

[Touch-packages] [Bug 1737582] [NEW] We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "

[Sistemas]

Public bug reported:

Hi:

We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on screen.
It seems there is an error related to LVM, but We don't know what.
I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"

About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
I restarted the server and try several things but no luck.

Ubuntu versión is:
#lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

Version of lvm package is:
# dpkg -l | grep lvm
ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager

I can see the LV is mounted:
# mount | grep /opt
/dev/mapper/vg--opt--zimbra-lv--opt--zimbra on /opt type ext4 (rw)

There are LVs that they shouldn't exist:
# ls -l /dev/mapper
total 0
crw--- 1 root root 10, 236 Dec 11 03:13 control
lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-lv--opt--zimbra -> 
../dm-1
lrwxrwxrwx 1 root root   7 Dec 11 03:13 
vg--opt--zimbra-lv--opt--zimbra-real -> ../dm-0
lrwxrwxrwx 1 root root   7 Dec 11 10:27 vg--opt--zimbra-opt--snapshot -> 
../dm-3
lrwxrwxrwx 1 root root   7 Dec 11 03:13 vg--opt--zimbra-opt--snapshot-cow 
-> ../dm-2


Too much devices in /dev/disk:
# ls -lR /dev/disk/
/dev/disk/:
total 0
drwxr-xr-x 2 root root 140 Dec 11 03:13 by-id
drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partlabel
drwxr-xr-x 2 root root  80 Dec 11 03:13 by-partuuid
drwxr-xr-x 2 root root 100 Dec 11 03:13 by-uuid

/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root  9 Dec 11 03:13 ata-QEMU_DVD-ROM_QM3 -> ../../sr0
lrwxrwxrwx 1 root root 10 Dec 11 10:27 dm-name-vg--opt--zimbra-lv--opt--zimbra 
-> ../../dm-1
lrwxrwxrwx 1 root root 10 Dec 11 10:27 dm-name-vg--opt--zimbra-opt--snapshot -> 
../../dm-3
lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZ9E3YnxMBSQasz7G0mUkcWQa6tQhSmggA -> 
../../dm-1
lrwxrwxrwx 1 root root 10 Dec 11 10:27 
dm-uuid-LVM-6tkfLRvf42Y68M2Bcme0LzAeMzJja2HZCRr8AQtnx7QpnAjSCEp8Dikr7zapGgmL -> 
../../dm-3

/dev/disk/by-partlabel:
total 0
lrwxrwxrwx 1 root root 10 Dec 11 03:13 primary -> ../../vdc1
lrwxrwxrwx 1 root root 10 Dec 11 03:13 PRIMARY -> ../../vdb1

/dev/disk/by-partuuid:
total 0
lrwxrwxrwx 1 root root 10 Dec 11 03:13 59ee8853-ae0e-4a7f-90d1-f1e5a8e4489d -> 
../../vdb1
lrwxrwxrwx 1 root root 10 Dec 11 03:13 9669fe59-0ab9-4e5c-b559-3a5f7e70cbf0 -> 
../../vdc1

/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 Dec 11 03:13 5d485a10-6f17-48f6-b9a2-260b8aa09d49 -> 
../../vda1
lrwxrwxrwx 1 root root 10 Dec 11 10:27 9aa61566-8f53-4201-8b74-8401ce4f3985 -> 
../../dm-1
lrwxrwxrwx 1 root root 10 Dec 11 03:13 ee2649c4-818c-448f-aa9a-41dc42aad7b2 -> 
../../vdc1


I tried to remove them with lvremove, but no error message nor other kind of 
information.


Any idea if this problem is related with the error on dmesg?
Any idea to resolve it?

Regards

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1737582

Title:
  We have a server with a volume Group (VG) and two logical volumes
  (LV). About two 11 days ago it worked fine and we could see
  information when we run "lvs -a" or "vgs -a", but now nothing is
  shown.

Status in upstart package in Ubuntu:
  New

Bug description:
  Hi:

  We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a", but now nothing is shown.
  But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
  Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on 
screen.
  It seems there is an error related to LVM, but We don't know what.
  I have the error on dmesg "init: Failed to obtain startpar-bridge instance: 
Unknown parameter: INSTANCE"

  About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
  I restarted the server and try several things but no luck.

  Ubuntu versión is:
  #lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.4 LTS
  Release: 14.04
  Codename: trusty

  Version of lvm package is:
  # dpkg -l | grep lvm
  ii lvm2 2.02.98-6ubuntu2 amd64 Linux Logical Volume Manager

  I can see the LV is mounted:
  # mount | grep /opt
  /dev/mapper/vg--opt--zimbra-lv--opt--zimbra on /opt type ext4 (rw)

  There are 

[Touch-packages] [Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

[Sistemas]

Hi:

I have the same error on dmesg "init: Failed to obtain startpar-bridge 
instance: Unknown parameter: INSTANCE"
We have a server with a volume Group (VG) and two logical volumes (LV). About 
two 11 days ago it worked fine and we could see information when we run "lvs 
-a" or "vgs -a".
But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got no 
information.
Even if I run "lvs --help" or "lvdisplay --help", nothing is printed on screen.
It seems there is an error related to LVM, but We don't know what.

About two 11 days ago it worked fine and we could see information when we run 
"lvs -a" or "vgs -a", but now nothing is shown.
I restarted the server and try several things but no luck.

Any idea if this problem is related with the error on dmesg?
Any idea to resolve it?

Regards

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1295596

Title:
  init: Failed to obtain startpar-bridge instance: Unknown parameter:
  INSTANCE

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have came accross the failure of init in /var/log/dmesg
  init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

  # ---
  Ubuntu development branch Trusty 14.04
  kernel Linux 3.13.0-18-lowlatency #38-Ubuntu SMP PREEMPT Mon Mar 17 22:08:57 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy upstart
  upstart:
Installed: 1.12.1-0ubuntu1
Candidate: 1.12.1-0ubuntu1
Version table:
   *** 1.12.1-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Kind Regards,
  Martin

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Ubuntu Foundations Team Bug Bot]

The attachment "protobuf.debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1735160

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  New
Status in protobuf package in Ubuntu:
  New
Status in pymacaroons package in Ubuntu:
  New
Status in python-nacl package in Ubuntu:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 
1.0.1-1build1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  TBC

  [Regression Potential]
  - httmock, none has it's not in xenial
  - python3-protobuf, none has the python2 code was not edited
  TBC

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful

[Sebastien Bacher]

@Jan, were you maybe using a wifi behind a captive portal at the time?
could be bug #1727237 maybe?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725680

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735160] Re: Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

** Also affects: httmock (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pymacaroons (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: python-nacl (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: protobuf (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: xenial-backports

** Summary changed:

- Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
+ [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

** Description changed:

- As part of allowing Ubuntu users to enable canonical-livepatch from
- software-properties GUI
- (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to
- backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This
- will requires quite few changes:
+ [Impact]
+ As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 
1.0.1-1build1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

** Description changed:

  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 
1.0.1-1build1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.
+ 
+ [Test case]
+ 
+ [Regression Potential]

** Description changed:

  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 
1.0.1-1build1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.
  
  [Test case]
  
  [Regression Potential]
+ - httmock, none has it's not in xenial
+ - python3-protobuf, none has the python2 code was not edited

** Description changed:

  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 
1.0.1-1build1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.
  
  [Test case]
+ TBC
  
  [Regression Potential]
  - httmock, none has it's not in xenial
  - python3-protobuf, none has the python2 code was not edited
+ TBC

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1735160

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  New
Status in protobuf package in Ubuntu:
  New
Status in pymacaroons package in Ubuntu:
  New
Status in python-nacl package in Ubuntu:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from 

[Touch-packages] [Bug 1578832] Re: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ChristianEhrhardt]

Hi Marcus,
here from your log:
insserv: warning: script 'S20vpnserver' missing LSB tags and overrides
insserv: warning: script 'vpnserver' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service vpnserver and udev if started
insserv:  loop involving service mountkernfs at depth 1
insserv: There is a loop at service vpnserver if started
insserv: Starting vpnserver depends on plymouth and therefore on system 
facility `$all' which can not be true!
...
insserv: Starting vpnserver depends on plymouth and therefore on system 
facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service vpnserver at depth 1
insserv: There is a loop between service vpnserver and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

At least according to my checks /etc/init.d/vpnserver is not part of any 
package, but in this file is the dependency loop trigger.
You can check if it belongs to a package with:
$ dpkg -S /etc/init.d/vpnserve

You need to sort that config issue out or remove the file if it is a
remainder of some aborted experiments.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1578832

Title:
  package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Tried to install ssh.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 23:29:32 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1578832] Re: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ChristianEhrhardt]

@Marcus - I just realized your issue is rather old, but something made
another user to say "I ahve the same issue" so I might at least have
helped him in time :-/.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1578832

Title:
  package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Tried to install ssh.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 23:29:32 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1578832] Re: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[ChristianEhrhardt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with 
the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays 
unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but 
since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting 
the service will work.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

And finally this is not tied to openssh - anything that would insert
init scripts would trigger the same issue.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1578832

Title:
  package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Tried to install ssh.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 23:29:32 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1604010] Re: sntp missing

[Doug Smythies]

** Changed in: serverguide
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1604010

Title:
  sntp missing

Status in Ubuntu Server Guide:
  Fix Released
Status in ntp package in Ubuntu:
  Fix Released
Status in ntp package in Debian:
  Fix Released

Bug description:
  In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the
  package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is
  still included.

  How to reproduce:

  $ sudo apt-get install ntp
  $ dpkg-query -L ntp | grep sntp
  /usr/share/man/man1/sntp.1.gz

  Expected result:

  /usr/bin/sntp was included in Ubuntu 14.04:

  $ dpkg-query -L ntp | grep sntp
  /usr/bin/sntp
  /usr/share/man/man1/sntp.1.gz

  The sntp program remains a very useful tool for interactively testing
  on the command line the offset of the local clock to a remote NTP
  server (like "ntpdate -qu [ntp-server]" previously). It should be
  included in the same package as its man page.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

[Joseph Salisbury]

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Zesty)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Artful)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Tags removed: kernel-key

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 

[Touch-packages] [Bug 1737570] [NEW] Add support for RequiredForOnline in networkd

[Dimitri John Ledkov]

Public bug reported:

Add support for RequiredForOnline in networkd

https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

RequiredForOnline= denotes a link/network that does/does not require being up
for systemd-networkd-wait-online to consider the system online; this makes it
possible to ignore devices without modifying parameters to wait-online.

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

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

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

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

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

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737377] Re: Unknown tunnel mode "vti6"

[ChristianEhrhardt]

Hi Simon,
we are currently shuffling around responsibilities for iproute so extra 
latencies might occur :-/.

I have two theories:
1. the iproute package needs fixes that came later than what is in Xenial:
The package needs to be very close to the kernel version in general.
Did you have any chance to test the newer 4.9 by forcing it into a Xenial 
system if that works as well? If you need a ppa for that let me know and I'll 
create one for you.

2. the Xenial kernel has this type disabled.
If throwing in an HWE kernel [1] into xenial, does it then work for you?


[1]: https://wiki.ubuntu.com/Kernel/LTSEnablementStack

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1737377

Title:
  Unknown tunnel mode "vti6"

Status in iproute2 package in Ubuntu:
  New

Bug description:
  [Impact]

  Xenial users are unable to create vti6 tunnels.

  [Test case]

  1) Create a vti6 tunnel
   sudo ip tunnel add vti0 mode vti6 local :: remote fdd6:bdb4:5614::2 key 54
  2) No error should be displayed and "ip link" should show a new device named 
"vti0"

  The ip tunnel call currently fails with the error 'Unknown tunnel mode
  "vti6"' and no tunnel is created.

  [Other Info]

  vti6 mode is supported according to the man page:

  $ man ip-tunnel | grep vti6
 MODE :=  { ipip | gre | sit | isatap | vti | ip6ip6 | ipip6 | ip6gre | 
vti6 | any }
   Modes for IPv6 encapsulation available: ip6ip6, ipip6, 
ip6gre, vti6, and any.

  iproute2 4.9.0-1ubuntu2 on *Artful* has no problem creating vti6
  tunnels.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  $ apt-cache policy iproute2
  iproute2:
Installed: 4.3.0-1ubuntu3.16.04.3
Candidate: 4.3.0-1ubuntu3.16.04.3
Version table:
   *** 4.3.0-1ubuntu3.16.04.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.3.0-1ubuntu3.16.04.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   4.3.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec  9 21:55:27 2017
  InstallationDate: Installed on 2016-12-06 (368 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.iproute2.rt_tables: [modified]
  mtime.conffile..etc.iproute2.rt_tables: 2016-12-21T17:41:32.869321

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1732032

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Committed
Status in iproute2 source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1

  == Comment: #12 - David Z. Dai  - 2017-11-13 15:07:32 ==

  I found upstream 

[Touch-packages] [Bug 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

[Dimitri John Ledkov]

> KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.

But the inner PV is only for the guest to use - no?
and thus it should not be mounted on the host, on boot.
Or do you somehow mount and access that PV on the host as well as the guest? 
That doesn't sound right.

Or are you saying when such things exist (and not required to mount/boot
the host) the boot stalls nonetheless, and should not?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731566

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
  This is somewhat involuntary as certain appliance VMs come configured this 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

[Dimitri John Ledkov]

I'll try to reproduce this locally to understand what is going on,
sounds bad based on the description.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731566

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
  This is somewhat involuntary as certain appliance VMs come configured this 
way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Jeremy Bicha]

** Changed in: libgweather (Ubuntu Artful)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  In Progress

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
 LANGUAGE=fr gnome-weather
 and find that the description of the weather type is displayed in
 English. 

   * Install these packages from artful-proposed:
 - gir1.2-gweather-3.0
 - libgweather-3-6
 - libgweather-common

   * Start gnome-weather with:
 LANGUAGE=fr gnome-weather
 and find that the description of the weather type is now displayed
 in French. 

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1706948] Re: [Ubuntu 18.04] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils

[Frank Heimes]

** Changed in: pm-utils (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntu-power-systems
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1706948

Title:
  [Ubuntu 18.04] [Feature] Inconsistent report of pm CanSuspend state by
  systemd and pm-utils

Status in The Ubuntu-power-systems project:
  Invalid
Status in pm-utils package in Ubuntu:
  Invalid

Bug description:
  == Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 ==
  systemd and pm-utils interprets CanSuspend states differently and reports it 
as supported or not in a conflicting way.

  # gdbus call --system --dest org.freedesktop.login1 --object-path 
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend
  ('yes',)

  # pm-is-supported --suspend
  # echo $?
  1

  Both systemd and pm-is-supported looks into /sys/power/state file to
  check if suspend is supported.

  pm-is-supported --suspend returns true if either "standby" or "mem" is 
present in the file.
  ( /usr/lib/pm-utils/pm-functions )

  systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is 
present in the file.
  ( 
https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c
 )

  # cat /sys/power/state
  freeze

  So here, pm-is-supported --suspend returns false and gdbus returns
  true.

  Both these utilities interpret /sys/power/state differently.

  Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or
  don't report freeze as CanSuspend.

  Impact of this inconsistency can be felt from Libvirt supported pm
  states:

  To reduce ABI dependency, libvirt queries the available states via
  dbus, if not falls to pm-utils. Libvirt won't check for strings in
  sys/power/state and interpret directly.

  so due to this, libvirt will list that suspend_to_mem is supported
  from virsh capabilities but ideally it might not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

[Iain Lane]

Uploaded to A (needs manually accepting) + B. Thanks!

** Also affects: gettext (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gnome-control-center (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: gettext (Ubuntu Artful)
   Status: New => Invalid

** Changed in: gnome-shell (Ubuntu Artful)
   Status: New => Invalid

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1491787

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gettext source package in Artful:
  Invalid
Status in gnome-control-center source package in Artful:
  In Progress
Status in gnome-shell source package in Artful:
  Invalid

Bug description:
  [ Description ]

  In GNOME's activities overview, search entries from gnome-control-
  center aren't translated.

  [ Fix ]

  setlocale() wasn't being called until after the model that supplies
  search results was constructed. We fix the initialisation code to run
  slightly later, after setlocale() has been called.

  [ QA ]

  1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
  2. Hit super and type an "a"
  3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).

  [ Regression potential ]

  If we misunderstood when the initialisation phases in GtkApplication
  ran then there could be a race condition. You'd see that manifesting
  as either a crash in the search provider or no results being returned.
  Make sure there aren't crahes reported in errors.u.c.

  [ Original description ]

  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

Discussed the proposal in comment #21 with Sebastien Bacher, and changed
the template name and translation domain to "libgweather-3.0" in LP for
bionic.

** Changed in: ubuntu-translations
   Importance: Undecided => High

** Changed in: ubuntu-translations
   Status: New => In Progress

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Description changed:

+ [Impact]
+ 
+ The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
+ libgweather, which makes the libgweather-common binary look for
+ translations in files named "libgweather-3.0.mo". The template name in
+ Rosetta (LP) is "libgweather", so the files provided by the language
+ packs are named "libgweather.mo". This mismatch results in the messages
+ describing the weather type always be displayed in English.
+ 
+ The uploaded package works around the issue by setting GETTEXT_PACKAGE
+ to "libgweather".
+ 
+ In bionic the template name in Rosetta has been changed to
+ "libgweather-3.0", and thus the workaround will be reversed.
+ 
+ [Test Case]
+ 
+  * Install French language support
+ 
+  * Start gnome-weather with:
+LANGUAGE=fr gnome-weather
+and find that the description of the weather type is displayed in
+English. 
+ 
+  * Install these packages from artful-proposed:
+- gir1.2-gweather-3.0
+- libgweather-3-6
+- libgweather-common
+ 
+  * Start gnome-weather with:
+LANGUAGE=fr gnome-weather
+and find that the description of the weather type is now displayed
+in French. 
+ 
+ [Regression Potential]
+ 
+ None.
+ 
+ [Original description]
+ 
  In Gnome Weather, part of it is not translated in french : cloudy, rain
  showers, etc. Should be : nuageux, pluie fine, etc.
  
  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under the
  extensions section.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1704533

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Confirmed
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Artful:
  Triaged

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
 LANGUAGE=fr gnome-weather
 and find that the description of the weather type is displayed in
 English. 

   * Install these packages from artful-proposed:
 - gir1.2-gweather-3.0
 - libgweather-3-6
 - libgweather-common

   * Start gnome-weather with:
 LANGUAGE=fr gnome-weather
 and find that the description of the weather type is now displayed
 in French. 

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737544] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de

[Leonidas S. Barbosa]

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1737544

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade:
  le paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in openssl package in Ubuntu:
  New

Bug description:
  wifi doesn't work anymore

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu9.3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec 11 14:02:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-11  14:02:32
   Commandline: apt-get upgrade
   Requested-By: niko (1000)
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet libssl1.0.0:i386 (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (532 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
le paquet est dans un état vraiment incohérent; vous devriez  le réinstaller 
avant de tenter de le configurer.
  UpgradeStatus: Upgraded to yakkety on 2017-04-29 (226 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

[Iain Lane]

** Description changed:

+ [ Description ]
+ 
+ In GNOME's activities overview, search entries from gnome-control-center
+ aren't translated.
+ 
+ [ Fix ]
+ 
+ setlocale() wasn't being called until after the model that supplies
+ search results was constructed. We fix the initialisation code to run
+ slightly later, after setlocale() has been called.
+ 
+ [ QA ]
+ 
+ 1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
+ 2. Hit super and type an "a"
+ 3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).
+ 
+ [ Regression potential ]
+ 
+ If we misunderstood when the initialisation phases in GtkApplication ran
+ then there could be a race condition. You'd see that manifesting as
+ either a crash in the search provider or no results being returned. Make
+ sure there aren't crahes reported in errors.u.c.
+ 
+ [ Original description ]
+ 
  Hey,
  
  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview
  
  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see screenshot
  in the above mentioned link), even though my system language is German.
  The entries in the gnome-control-center itself are however in German.
  
  Is this due to a bug or missing translations?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1491787

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Fix Released
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  [ Description ]

  In GNOME's activities overview, search entries from gnome-control-
  center aren't translated.

  [ Fix ]

  setlocale() wasn't being called until after the model that supplies
  search results was constructed. We fix the initialisation code to run
  slightly later, after setlocale() has been called.

  [ QA ]

  1. Open a session in a non-English locale which has gnome-control-center 
translations (French works).
  2. Hit super and type an "a"
  3. There should be some results from "Settings". They should be in French (or 
whatever language you're using).

  [ Regression potential ]

  If we misunderstood when the initialisation phases in GtkApplication
  ran then there could be a race condition. You'd see that manifesting
  as either a crash in the search provider or no results being returned.
  Make sure there aren't crahes reported in errors.u.c.

  [ Original description ]

  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1630623] Re: package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Mattia Rizzolo]

** Package changed: pyside (Ubuntu) => python-defaults (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-defaults in Ubuntu.
https://bugs.launchpad.net/bugs/1630623

Title:
  package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-pyside.qtcore 1.2.2-2build2
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 15:51:23 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: pyside
  Title: package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[Daniel Borkmann]

Awesome, thanks a lot, Christian!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1735032

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Fix Committed
Status in iproute2 package in Debian:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1731566] Re: systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an LV

[Metta Crawler]

** Description changed:

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  
  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  
  Expected:
  
  Ubuntu 17.10 booting up as fast as Ubuntu 16.04
  
  What happened instead:
  
  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.
  
  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s
  
  The second one is from /scripts/init-bottom/lvm where 'udevadm --settle'
  is run.
  
  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi
  
  Reproducing:
  
  Where $vg is some existing volume group name:
  
  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot
  
  Use case:
  
  KVM/Qemu libvirt VM guest's vda with PV in it stored in host LV.
- 
+ This is somewhat involuntary as certain appliance VMs come configured this 
way.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 18:29:33 2017
  InstallationDate: Installed on 2017-11-05 (5 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro verbose
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1731566

Title:
  systemd-udevd delays boot for 4+ minutes when an LVM PV is inside an
  LV

Status in systemd package in Ubuntu:
  New
Status in udev package in Debian:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy udev
  udev:
    Installed: 234-2ubuntu12.1
    Candidate: 234-2ubuntu12.1
    Version table:
   *** 234-2ubuntu12.1 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   234-2ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Expected:

  Ubuntu 17.10 booting up as fast as Ubuntu 16.04

  What happened instead:

  During boot up the system will hang and then a timeout will allow it
  continue. This happens twice.

  The first one occurs right after the network interfaces are renamed. Example:
  [5.160480] e1000e :02:00.0 enp2s0f0: renamed from eth0
  [  121.345255] raid6: sse2x1   gen()  4431 MB/s

  The second one is from /scripts/init-bottom/lvm where 'udevadm
  --settle' is run.

  # we cannot properly synthesize LVM LV change events with udevadm trigger, so
  # if we use LVM, we need to let it finish; otherwise we get missing LV 
symlinks
  # (LP #1185394)
  if [ -x /sbin/vgchange ]; then
  udevadm settle --timeout=121 || true
  fi

  Reproducing:

  Where $vg is some existing volume group name:

  lvcreate -n pvtest -L 20m $vg
  pvcreate /dev/$vg/pvtest
  reboot

  Use case:

  KVM/Qemu 

[Touch-packages] [Bug 1630623] [NEW] package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

NA

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-pyside.qtcore 1.2.2-2build2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct  5 15:51:23 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-01 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: pyside
Title: package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial
-- 
package python-pyside.qtcore 1.2.2-2build2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1630623
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to python-defaults in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful

[patpat]

It seems Casper does not update /etc/systemd/resolved.conf
then I do not really know how you get this working if booting 
from an untouched live 17.10 Ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725680

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1726730] Re: IPRoute pkg is in different version than kernel

[ChristianEhrhardt]

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1726730

Title:
  IPRoute pkg is in different version than kernel

Status in iproute2 package in Ubuntu:
  Fix Committed
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  New
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  Hello,

  At the moment there is a problem with Iproute package in Zesty and
  artful.

  In Zesty the kernel version is 4.10.0, and the Iproute package is 4.9.0. 
  In Artful the kernel version is 4.13, and the Iproute is 4.9.0 too. 

  This is causing some problems in the BPF/XDP setup, some code is in
  the kernel but doesn't have the same version in Iproute, so it'll
  fail.

  Found the problem using cilium project
   and the problem was
  validated by Daniel Borkmann (iproute mantainer)

  I didn't find any related bug related to updating. If you need help to
  test/update, I can help you.

  Regards and many thanks.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1677869] Re: Missing dep8 tests

[ChristianEhrhardt]

Hi,
I missed to realize this was an open bug in our overall dep8-missing-campaign.
I added it in [1] which is about to migrate soon.

TL;DR let the upstream testsuite run in a VM as dep8 test (has plenty of
tests).

Will set this done once it is in bionic.

[1]:
https://git.launchpad.net/~paelzer/ubuntu/+source/iproute2/commit/?id=4b4dbb6cf045f05cc5f235487b06d2706a5b93a8

** Changed in: iproute2 (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1677869

Title:
  Missing dep8 tests

Status in iproute2 package in Ubuntu:
  Fix Committed

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source iproute2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/iproute2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YCYAAoJEIP8BxPaZgwl+YMP/itZd9vMISQh89Gz1BvsISKo
  u8TSiOxpvECMUls1s530MQQq4qY5fLH3ofyP2RiMkZQpOGZTscHIV1AwntBuYQTY
  z039AKp/CRqHdb9z4GCHxDy13B2fIjAEfIcPfD/5XrPHXTTePvvsl2abC1niB+xY
  MWyFeHzTVj2vfSnBegiSM4LFvOTqtx4c0JCi7E3njO5AnZQ6Q3NUZ6uY1kzEingO
  BaSkM6P7PLRWeX3ScLqk/yFjWbDheQsDTqmqfTjx2gu2aAAPyH10+aZXVotUpklL
  +EACK78VRslNPLdq/VAkoCxztcLx7SNSL3oI2Uf27xFY3LYh5MmeZN+J5N2NwLa3
  PaCmCt5fYIB6kGTR0eyZyth8S96frOLX8AgifQ7mPlariPosn4bGu/U7vJ3aR+Al
  DnD9pr8t9gpToAP2rDOADLzvtX1gaa2/JcULet0ZiYlEAcizW2nJFZjuO7oqOj/G
  Y8/MFT6yRXPWRhmhO9f6/O0OE15fTTYwmoYnjkMz2+rtMZkJg7S7OFgfdyfz9LOi
  3bcNgw6zNpdoZwpZAhknOst7dZQ0hC9crG4W7r6jBvLTvdEhNwPTkg64HZHWq510
  PCCK2MLjxKJdozeyF9yD/gA9H8bgP5cIVy3eEglZr4nlr9W1VDcTl/ZJg65d1HGb
  PDmiWw9XnV1jO4QBlD7z
  =jCpZ
  -END PGP SIGNATURE-

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[ChristianEhrhardt]

FYI - to improve the aligning with Ubuntu Kernel releases I also
organized that we will pass over responsibility for this package to the
kernel team. That way it should be much more in sync which should
improve future kernel/iproute2 level match.

** Changed in: iproute2 (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1735032

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Fix Committed
Status in iproute2 package in Debian:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1735032] Re: rebase iproute2 to newer version

[ChristianEhrhardt]

New upload landed in bionic-proposed and looking good in tests.
If there is no hickup this will be resolved soon.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1735032

Title:
  rebase iproute2 to newer version

Status in iproute2 package in Ubuntu:
  Fix Committed
Status in iproute2 package in Debian:
  New

Bug description:
  Ubuntu's iproute2 version [1] is still many kernel versions behind.
  It's still on 4.9, whereas shipped kernel is on 4.13 in the meantime!

  iproute2 is developed alongside the kernel, so new kernel features
  will also get updates to iproute2 whenever they change related code.
  Meaning, these features cannot be used out of the box if the actual
  shipped iproute2 version here is not on par with the kernel version
  (the release tags have 1:1 mapping with kernel releases) [2].

  Please consider updating iproute2 package, and please also consider
  updating it regularly along with officially shipped kernels in Ubuntu,
  so that all the added networking features can be used there without
  forcing users to do a manual compilation of iproute2.

  Thanks,
  Daniel

[1] 
http://changelogs.ubuntu.com/changelogs/pool/main/i/iproute2/iproute2_4.9.0-1ubuntu2/changelog
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/refs/tags

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

[Balint Reczey]

There are a few other crashes in apt reported for u-u at
errors.ubuntu.com, they may be hold more useful information.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1737441

Title:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

Status in python-apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp