[Touch-packages] [Bug 1756755] Re: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[xor]

I am also affected and I did not manually install systemd-shim and did
not tamper with upstart.

-- 
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/1756755

Title:
  package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from xenial to bionic failed the removal of systemd-shim.
  I think the messages were the same as the following, that I can reproduce by 
running "apt upgrade" from the upgraded system:

  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 18 22:52:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-11 (1892 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756755/+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 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Ok, how does this look?

** Patch added: "link-files-in-run.debdiff"
   
https://bugs.launchpad.net/netplan/+bug/1770082/+attachment/5139062/+files/link-files-in-run.debdiff

-- 
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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain cloud environments.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1770082/+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 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)

[Launchpad Bug Tracker]

[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1755202

Title:
  Clone Mac Address Function On Default Wifi Setting Does Not Work
  (Ubuntu 17.10)

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I am Just Using Ubuntu 17.10.

  My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri
  Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.

  Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is
  also (MAC Address Randomization issue). I can fixed it and can use
  default mac address spoofing function from wifi setting -> Network
  Profile Setting (*) -> Identity -> Cloned Address -> And Add mac
  address to spoof for particular network.

  This Default mac address spoof function is very useful for me.

  Clearly, I doesn't mean (MAC Address Randomization issue)
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513

  Now I have a trouble with this feature (default mac spoffing). I can
  connect Wifi-s with great signal easily without using cloned address
  function.

  But when I added spoof address to setting, the wifi-s cannot be
  connected. I tried two wifi-s from near me which can connect on fedora
  26. One is open type network and the other is WPA Enterprise network.

  If this function doesn't work for anyone, this must be a bug.
  If it is a bug, hope it will fix it next release.

  Please, Don't Hesitate to ask more information. I really want to help
  to fix bug.

  Hardware Info
  Lenovo Z470 - Core i5 Second Gen
  I used external wifi adapter - Card King http://a.co/gMrHzZQ  (RT3072 Chipset)

  
  #info
  lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  network-manager:
    Installed: 1.8.4-1ubuntu3
    Candidate: 1.8.4-1ubuntu3
    Version table:
   *** 1.8.4-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Update Journalctl with network-manager log
  First I Connect my wifi named "blizzart" without using spoof address. 
Connected and works fine.
  After 2 minutes later, I disconnected.
  And then add spoof address and try to connect again.
  But It is still trying to connect. You can see in the log.
  https://pastebin.com/vmFMefih

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu Artful) because there has been no activity
for 60 days.]

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

-- 
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/1718771

Title:
  Incorrect handling of link-local IPv6 DNS servers

Status in systemd package in Ubuntu:
  Expired
Status in systemd source package in Artful:
  Expired

Bug description:
  We've recently seen odd looking DNS failures on autopkgtest:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz

  This shows a fe80:: link-local IPv6 address as one of the DNS servers
  on the interface. That's because dnsmasq includes both the link-local
  and global addresses of its DNS server in the router advertisement.

  systemd-networkd appears to pick that up and send it to resolved,
  which includes it in its config but apparently doesn't know how to
  actually query it, leading to the failure above.

  
  This is racy because once DHCPv4 completes, the resolved config will then 
work properly again.

  
  I've confirmed that dnsmasq properly answers on all addresses:
http://paste.ubuntu.com/25588197/

  
  I've uploaded a workaround for this issue as part of the docker.io package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718771/+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 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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/1718771

Title:
  Incorrect handling of link-local IPv6 DNS servers

Status in systemd package in Ubuntu:
  Expired
Status in systemd source package in Artful:
  Expired

Bug description:
  We've recently seen odd looking DNS failures on autopkgtest:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz

  This shows a fe80:: link-local IPv6 address as one of the DNS servers
  on the interface. That's because dnsmasq includes both the link-local
  and global addresses of its DNS server in the router advertisement.

  systemd-networkd appears to pick that up and send it to resolved,
  which includes it in its config but apparently doesn't know how to
  actually query it, leading to the failure above.

  
  This is racy because once DHCPv4 completes, the resolved config will then 
work properly again.

  
  I've confirmed that dnsmasq properly answers on all addresses:
http://paste.ubuntu.com/25588197/

  
  I've uploaded a workaround for this issue as part of the docker.io package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718771/+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 1771033] Re: python3-avahi is missing in Ubuntu/debian

[dino99]

source: https://github.com/lathiat/avahi/tree/master/avahi-python

packaged: https://launchpad.net/~yavdr/+archive/ubuntu/experimental-main

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

Title:
  python3-avahi is missing in Ubuntu/debian

Status in avahi package in Ubuntu:
  New

Bug description:
  Under Ubuntu 18.04 if you install the package Gajim the local account
  is permanently disabled because of missing dependencies.

  https://dev.gajim.org/gajim/gajim/issues/9125

  The required package is python3-avahi

  The python3-avahi package is missing, apt-get is unable to find it.

  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.

  I hope this package can be added, if this is the wrong place to file
  this bug I applologize. I don't have a lot of experience reporting
  bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1771033/+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 571356] Re: gdbtui shows "dl-debug.c:77: No such file or directory."

[rich painter]

STILL not fixed.

4.4.0-124-generic #148~14.04.1-Ubuntu SMP Thu May 3 07:26:53 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1

any c program compiled with -g and then 
gdb -tui program
set a breakpoint
run

multiple dl-debug.c:74: No such file or directory.
will be produced.

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

Title:
  gdbtui shows "dl-debug.c:77: No such file or directory."

Status in gdb package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gdb

  Using gdbtui to run a simple program shows "dl-debug.c:77: No such
  file or directory." repeatedly.  It seems that debugging can continue
  normally.

  Observed on
 Ubuntu 10.04 LTS
 g++ 4:4.4.3-1ubuntu1
 gdb version 7.1-1ubuntu2

  To reproduce:
  1) Create a dumb program, e.g. foo.cpp:
   int main(int argc, char *argv[]) {return 0; }
  2) Compile using g++ foo.cpp -o foo
  3) Fire up gdb tui using gdbtui ./foo
  4) Enter 'r' to run the program
  5) Observe the error message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/571356/+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 1771046] Re: pulseaudio crashed with SIGABRT in pa_memimport_free()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1770865, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139037/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139040/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139043/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139044/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139046/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139047/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1771046/+attachment/5139048/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1770865

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pulseaudio crashed with SIGABRT in pa_memimport_free()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  just ordinary pulse crash. every day routine.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  tp23619 F pulseaudio
   /dev/snd/controlC0:  tp22876 F audacity
tp23619 F pulseaudio
   /dev/snd/controlC1:  tp23619 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon May 14 04:33:26 2018
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-07-27 (1021 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: pulseaudio --start
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_memimport_free () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_pstream_unlink () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so
   ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGABRT in pa_memimport_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark
  dmi.bios.date: 07/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785TD-V EVO
  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.:bvr2105:bd07/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-05-14T04:23:08.098116

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1771046/+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 1748812] Re: cannot view wifi networks after resume from suspend

[Alfred]

>From comment 40 in upper stream bug - 
>https://bugzilla.gnome.org/show_bug.cgi?id=767317#c40
Upgrade to higher version(1.8) of NM should fix this. However xenial is stuck 
in 1.2.6... So I think 18.04 upgrade can fix this - which NM is 1.8.10.


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

-- 
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/1748812

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+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 1470235] Re: PolicyKit high memory usage

[Wedge009]

I have this issue on 17.10 and 18.04 but I'm not sure if it's related to
the original reporter's case because for me I suspect it's related to
amdgpu-pro. In earlier distributions the memory leak was elsewhere - I
can't remember if it was in xorg or plasmashell, though. I *think* it
also happened with fglrx, before amdgpu was released, but that was so
long ago now I can't be sure.

Regardless, the way I work around this is to restart the polkitd service
every now and then. Otherwise, after a few days the memory usage is in
the order of *gigabytes*!

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

Title:
  PolicyKit high memory usage

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Periodically I install updates on my computer and reboot without
  logging in. When I come back to my computer and log in, polkitd is
  using a large chunk of memory. At the moment it's using > 2.3 GiB of
  memory on a machine with 8 GB RAM:

  $ ps aux | grep polkit
  root  1229  0.4 29.8 2652532 2420916 ? Sl   Jun19  67:38 
/usr/lib/policykit-1/polkitd --no-debug

  Killing the process frees the memory until I reboot again.

  
  I'm currently using the latest version of policykit-1:

  $ apt-file search /usr/lib/policykit-1/polkitd
  policykit-1: /usr/lib/policykit-1/polkitd

  $ apt-cache policy policykit-1
  policykit-1:
Installed: 0.105-4ubuntu2.14.04.1
Candidate: 0.105-4ubuntu2.14.04.1
Version table:
   *** 0.105-4ubuntu2.14.04.1 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.105-4ubuntu2 0
  500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  $ sudo apt-get upgrade policykit-1
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  policykit-1 is already the newest version.

  
  Other information:

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Tue Jun 30 16:14:51 2015
  InstallationDate: Installed on 2014-08-25 (309 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+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 1771041] Re: Remove gconf from Ubuntu

[Jeremy Bicha]

** Also affects: gyrus (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnomint (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-xcf-thumbnailer (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-mastermind (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gkdebconf (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ekiga (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: evolution-indicator (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: autopilot-legacy (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: desktopnova (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gtkwave (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.
  
  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.
  
  We are waiting on pulseaudio also (fixed in git master).
  
  libgnome is a blocker so do it first LP: #1771031
- And remove libqt-gconf LP: #1740538
+ And remove libqt-gconf LP: #1740538 and xiphos LP: #1710318
  
  thunderbird needs to be fixed (should happen for the 60 release expected
  "soon")

** Also affects: guake-indicator (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gxneur (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove gconf from Ubuntu

Status in autopilot-legacy package in Ubuntu:
  New
Status in desktopnova package in Ubuntu:
  New
Status in ekiga package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  New
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  New
Status in guake-indicator package in Ubuntu:
  New
Status in gxneur package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  New
Status in jack-mixer package in Ubuntu:
  New
Status in jana package in Ubuntu:
  New
Status in morla package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  We are waiting on pulseaudio also (fixed in git master).

  libgnome is a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538 and xiphos LP: #1710318

  thunderbird needs to be fixed (should happen for the 60 release
  expected "soon")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopilot-legacy/+bug/1771041/+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 1771041] Re: Remove gconf from Ubuntu

[Jeremy Bicha]

** Also affects: ooo-thumbnailer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jana (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jack-mixer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove gconf from Ubuntu

Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  New
Status in jack-mixer package in Ubuntu:
  New
Status in jana package in Ubuntu:
  New
Status in morla package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  We are waiting on pulseaudio also (fixed in git master).

  libgnome is a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

  thunderbird needs to be fixed (should happen for the 60 release
  expected "soon")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1771041/+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 1759836] Re: systemd-udevd consumes 100% of CPU

[Wedge009]

Adding some information in case it's useful.

Old - but still useful - Intel Core 2 laptop with discrete Mobility
Radeon GPU. I had nvidia packages installed for development purposes
years ago, but don't really use them any more. After the upgrade from
17.10 to 18.04 (only performed 2018-05-12, several days after official
release), I noticed single-threaded 100% CPU usage from systemd-udevd,
with modprobe starting and exiting over and over again. I saw lots of
messages complaining about NVIDIA hardware not being found in dmesg
output. After uninstalling the nvidia packages and rebooting, the high
CPU usage seemed to go away.

So at least on my system, it seems there was a conflict between having
nvidia drivers present with no NVIDIA hardware available.

-- 
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/1759836

Title:
  systemd-udevd consumes 100% of CPU

Status in Bluez Utilities:
  Unknown
Status in linux:
  Unknown
Status in bluez package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  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: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1759836/+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 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

[Hui Wang]

Tested 1.1.3-5ubuntu0.1 on bionic, it worked well and fixed the problem.

thx.


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

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

To manage notifications 

[Touch-packages] [Bug 1771041] Re: Remove gconf from Ubuntu

[Jeremy Bicha]

** Also affects: planner (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ogmrip (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mssh (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: morla (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.
  
  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.
  
  We are waiting on pulseaudio also (fixed in git master).
  
  libgnome is a blocker so do it first LP: #1771031
+ And remove libqt-gconf LP: #1740538
  
  thunderbird needs to be fixed (should happen for the 60 release expected
  "soon")

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

Title:
  Remove gconf from Ubuntu

Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in morla package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  We are waiting on pulseaudio also (fixed in git master).

  libgnome is a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

  thunderbird needs to be fixed (should happen for the 60 release
  expected "soon")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1771041/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

** Changed in: hwe-next
   Status: In Progress => Fix Released

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1771041] [NEW] Remove gconf from Ubuntu

[Jeremy Bicha]

Public bug reported:

gconf is being removed from Debian Testing. We should remove it from
Ubuntu also.

eclipse is troublesome. At a minimum, we can remove everything but
eclipse and gconf.

We are waiting on pulseaudio also (fixed in git master).

libgnome is a blocker so do it first LP: #1771031

thunderbird needs to be fixed (should happen for the 60 release expected
"soon")

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

** Affects: gconf-editor (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

** Also affects: gconf-editor (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.
  
  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.
  
  We are waiting on pulseaudio also (fixed in git master).
  
  libgnome is a blocker so do it first LP: #1771031
+ 
+ thunderbird needs to be fixed (should happen for the 60 release expected
+ "soon")

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

Title:
  Remove gconf from Ubuntu

Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in morla package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in planner package in Ubuntu:
  New

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  We are waiting on pulseaudio also (fixed in git master).

  libgnome is a blocker so do it first LP: #1771031

  thunderbird needs to be fixed (should happen for the 60 release
  expected "soon")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1771041/+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 1771040] [NEW] Bluetooth HFP/HSP profile doesn't work in 18.04

[Christopher Berner]

Public bug reported:

Hardware: Bose QC35 II

When selecting the A2DP Sink profile these headphones work fine.
However, with HSP/HFP selected neither the output nor the microphone
work. The headphones will periodically say "Call from" and then break
off, and also you can hear a low grade crackling like line noise in them
the rest of the time.

Potentially relevant logs:
dmesg (the second message is repeated frequently):
[   68.288408] input: 2C:41:A1:80:A1:C4 as /devices/virtual/input/input21
[   78.575027] Bluetooth: hci0: last event is not cmd complete (0x0f)

Originally, I got an error like the following from ("journalctl -u bluetooth"), 
but then ran "rfkill unblock bluetooth" which seems to have fixed it:
May 13 15:58:02 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
May 13 15:58:19 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Headset 
Voice gateway: getpeername: Transport endpoint is not connected (107)
May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Phone Book 
Access: getpeername: Transport endpoint is not connected (107)

What additional information would be useful to debug this?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 16:33:13 2018
InstallationDate: Installed on 2018-05-13 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3406
dmi.board.asset.tag: Default string
dmi.board.name: Z170I PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3406:bd07/10/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170IPROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
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
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: C8:FF:28:31:68:E4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:19479 acl:97 sco:0 events:730 errors:0
TX bytes:8355 acl:99 sco:3 commands:148 errors:0

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


** Tags: amd64 apport-bug bionic

-- 
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/1771040

Title:
  Bluetooth HFP/HSP profile doesn't work in 18.04

Status in bluez package in Ubuntu:
  New

Bug description:
  Hardware: Bose QC35 II

  When selecting the A2DP Sink profile these headphones work fine.
  However, with HSP/HFP selected neither the output nor the microphone
  work. The headphones will periodically say "Call from" and then break
  off, and also you can hear a low grade crackling like line noise in
  them the rest of the time.

  Potentially relevant logs:
  dmesg (the second message is repeated frequently):
  [   68.288408] input: 2C:41:A1:80:A1:C4 as /devices/virtual/input/input21
  [   78.575027] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Originally, I got an error like the following from ("journalctl -u 
bluetooth"), but then ran "rfkill unblock bluetooth" which seems to have fixed 
it:
  May 13 15:58:02 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
  May 13 15:58:19 skylake bluetoothd[1023]: Failed to set mode: Blocked through 
rfkill (0x12)
  May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Headset 
Voice gateway: getpeername: Transport endpoint is not connected (107)
  May 13 16:00:41 skylake bluetoothd[1023]: Unable to get io data for Phone 
Book Access: getpeername: Transport endpoint is not connected (107)

  What additional information would be useful to debug this?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 16:33:13 2018
  InstallationDate: Installed on 2018-05-13 (0 days ago)

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

[Rumen]

I use 18.04 / login session Xorg and had the same issue. Got help from
the IRC channel.

Workaround for me which actually works:

Alt+F2

Type "r" without the quotes

Hit "Enter"

The icons appears!

Regards all.

Rumen

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+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 1770839] Re: Syncevolution does not run in Ubuntu 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Syncevolution does not run in Ubuntu 18.04

Status in syncevolution package in Ubuntu:
  Confirmed

Bug description:
  There is a problem with the package syncevolution (1.5.3-1ubuntu2) in
  Ubuntu 18.04 :

  Step to reproduce:
  >$ sudo apt install syncevolution

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les paquets supplémentaires suivants seront installés : 
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution-common syncevolution-libs syncevolution-libs-gnome
  Les NOUVEAUX paquets suivants seront installés :
libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 
syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome
  0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 2'230 ko dans les archives.
  Après cette opération, 10.2 Mo d'espace disque supplémentaires seront 
utilisés.
  Souhaitez-vous continuer ? [O/n] O
  [...]
  Paramétrage de syncevolution (1.5.3-1ubuntu2) ...
  [...]

  > $ syncevolution --version
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-peers
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  > $ syncevolution --print-config
  syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: 
cannot open shared object file: No such file or directory

  Please note that this bug semms corrected in a new release of syncevolution :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043

  Would it be possible to have the corrected verion in Ubuntu 18.04 ?

  Thanks in advance for your help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1770839/+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 1771036] [NEW] Please remove libgnome-keyring from Ubuntu

[Jeremy Bicha]

Public bug reported:

libgnome-keyring has been removed from Debian Testing and will not be
included in the Debian 10 "Buster" release. We should do the same. Users
who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few
years.

This bug depends on the libgnome removal LP: #1771031

ukui-power-manager is a blocker LP: #1767165

mate-power-manager was fixed in Debian so presumably can be done in
18.10 too.

subversion 1.10 needs to be synced or merged to drop the unused
libgnome-keyring build-dependency

** Affects: libgnome-keyring (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: moonshot-ui (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: mysql-workbench (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same. Users
  who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few
  years.
  
  This bug depends on the libgnome removal LP: #1771031
  
  ukui-power-manager is a blocker LP: #1767165
+ 
+ mate-power-manager was fixed in Debian so presumably can be done in
+ 18.10 too.

** Also affects: moonshot-ui (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libsocialweb (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mysql-workbench (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same. Users
  who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few
  years.
  
  This bug depends on the libgnome removal LP: #1771031
  
  ukui-power-manager is a blocker LP: #1767165
  
  mate-power-manager was fixed in Debian so presumably can be done in
  18.10 too.
+ 
+ subversion 1.10 needs to be synced or merged to drop the unused
+ libgnome-keyring build-dependency

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

Title:
  Please remove libgnome-keyring from Ubuntu

Status in libgnome-keyring package in Ubuntu:
  New
Status in libsocialweb package in Ubuntu:
  New
Status in moonshot-ui package in Ubuntu:
  New
Status in mysql-workbench package in Ubuntu:
  New

Bug description:
  libgnome-keyring has been removed from Debian Testing and will not be
  included in the Debian 10 "Buster" release. We should do the same.
  Users who are hurt by these removals can keep using Ubuntu 18.04 LTS
  for a few years.

  This bug depends on the libgnome removal LP: #1771031

  ukui-power-manager is a blocker LP: #1767165

  mate-power-manager was fixed in Debian so presumably can be done in
  18.10 too.

  subversion 1.10 needs to be synced or merged to drop the unused
  libgnome-keyring build-dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgnome-keyring/+bug/1771036/+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 1771033] [NEW] python3-avahi is missing in Ubuntu/debian

[xekon]

Public bug reported:

Under Ubuntu 18.04 if you install the package Gajim the local account is
permanently disabled because of missing dependencies.

https://dev.gajim.org/gajim/gajim/issues/9125

The required package is python3-avahi

The python3-avahi package is missing, apt-get is unable to find it.

This is a vital feature for us, we use Gajim internally without
internet, and this simply works, no adding accounts, no information or
messages sent over the internet, it all works locally.

I hope this package can be added, if this is the wrong place to file
this bug I applologize. I don't have a lot of experience reporting bugs.

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


** Tags: avahi gajim local python-avahi python3-avahi

** Description changed:

- Under Ubuntu 18.08 if you install the package Gajim the local account is
+ Under Ubuntu 18.04 if you install the package Gajim the local account is
  permanently disabled because of missing dependencies.
  
  https://dev.gajim.org/gajim/gajim/issues/9125
  
  The required package is python3-avahi
  
  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.
  
  I hope this package can be added, if this is the wrong place to file
  this I applologize. I don't have a lot of experience reporting bugs.

** Description changed:

  Under Ubuntu 18.04 if you install the package Gajim the local account is
  permanently disabled because of missing dependencies.
  
  https://dev.gajim.org/gajim/gajim/issues/9125
  
  The required package is python3-avahi
  
+ The python3-avahi package is missing, apt-get is unable to find it.
+ 
  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.
  
  I hope this package can be added, if this is the wrong place to file
  this I applologize. I don't have a lot of experience reporting bugs.

** Description changed:

  Under Ubuntu 18.04 if you install the package Gajim the local account is
  permanently disabled because of missing dependencies.
  
  https://dev.gajim.org/gajim/gajim/issues/9125
  
  The required package is python3-avahi
  
  The python3-avahi package is missing, apt-get is unable to find it.
  
  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.
  
  I hope this package can be added, if this is the wrong place to file
- this I applologize. I don't have a lot of experience reporting bugs.
+ this bug I applologize. I don't have a lot of experience reporting bugs.

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

Title:
  python3-avahi is missing in Ubuntu/debian

Status in avahi package in Ubuntu:
  New

Bug description:
  Under Ubuntu 18.04 if you install the package Gajim the local account
  is permanently disabled because of missing dependencies.

  https://dev.gajim.org/gajim/gajim/issues/9125

  The required package is python3-avahi

  The python3-avahi package is missing, apt-get is unable to find it.

  This is a vital feature for us, we use Gajim internally without
  internet, and this simply works, no adding accounts, no information or
  messages sent over the internet, it all works locally.

  I hope this package can be added, if this is the wrong place to file
  this bug I applologize. I don't have a lot of experience reporting
  bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1771033/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Dedas]

If you want it to stay create a file /etc/rc.local and make it
executable:

sudo chmod +x /etc/rc.local

In rc.local type:

#!/bin/sh -e
sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
sh -c "echo "1" > remove" (I didn't need this)
exit 0

-- 
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/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1771012] Re: package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exit

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1771012

Title:
  package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade:
  installed libpam-systemd:amd64 package post-installation script
  subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know what append? I have so much report of bug.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpam-systemd:amd64 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 17:49:29 2018
  ErrorMessage: installed libpam-systemd:amd64 package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade: 
installed libpam-systemd:amd64 package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771012/+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 1771011] [NEW] Doesn't accept environment variable with underscore in its name in AuthorizedKeysFile

[Peter Poliak]

Public bug reported:

If environment variable name defined in AuthorizedKeysFile contains underscore 
character (environment="FOO_BAR=1" ...), sshd refuses connection and throws 
following error:
authorized_keys:1: bad key options: invalid environment string

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


** Tags: authorizedkeysfile underscore

-- 
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/1771011

Title:
  Doesn't accept environment variable with underscore in its name in
  AuthorizedKeysFile

Status in openssh package in Ubuntu:
  New

Bug description:
  If environment variable name defined in AuthorizedKeysFile contains 
underscore character (environment="FOO_BAR=1" ...), sshd refuses connection and 
throws following error:
  authorized_keys:1: bad key options: invalid environment string

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771011/+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 1771012] [NEW] package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exi

[Sylin Bruno]

Public bug reported:

I don't know what append? I have so much report of bug.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libpam-systemd:amd64 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri May 11 17:49:29 2018
ErrorMessage: installed libpam-systemd:amd64 package post-installation script 
subprocess returned error exit status 1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: systemd
Title: package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade: 
installed libpam-systemd:amd64 package post-installation script subprocess 
returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-11 (2 days ago)

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


** Tags: amd64 apport-package bionic

-- 
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/1771012

Title:
  package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade:
  installed libpam-systemd:amd64 package post-installation script
  subprocess returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I don't know what append? I have so much report of bug.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libpam-systemd:amd64 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 17:49:29 2018
  ErrorMessage: installed libpam-systemd:amd64 package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 237-3ubuntu10 failed to install/upgrade: 
installed libpam-systemd:amd64 package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771012/+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 1771000] [NEW] do-release-upgrade on a server with encrypted swap does not boot

[Frédéric Grosshans]

Public bug reported:

I’ve upgraded a server to bionic beaver, and it couldn’t boot anymore.
Using the “recovery boot” option hanged a long time with the message
"waiting for resume device".

Some googling lead be to the bug #206358, and I deduced that do-release-
upgrade “messed with my swap” (as said by @aldebx on there). This was a
LVM set-up with an encrypted swap, which may explain the bug.

My workaround, form the root login of the recovery mode was the following 
1. comment out the RESUME line in /etc/initramfs-tools/conf.d/resume 
2. rebuild the initramfs with update-initramfs -u
3. mount the /boot partiton to actually put the initramfs on the correct place

Now the systems boots again, but this problem shouldn’t have happened in
the first place.

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


** Tags: bionic

-- 
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/1771000

Title:
  do-release-upgrade on a server with encrypted swap does not boot

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I’ve upgraded a server to bionic beaver, and it couldn’t boot anymore.
  Using the “recovery boot” option hanged a long time with the message
  "waiting for resume device".

  Some googling lead be to the bug #206358, and I deduced that do-
  release-upgrade “messed with my swap” (as said by @aldebx on there).
  This was a LVM set-up with an encrypted swap, which may explain the
  bug.

  My workaround, form the root login of the recovery mode was the following 
  1. comment out the RESUME line in /etc/initramfs-tools/conf.d/resume 
  2. rebuild the initramfs with update-initramfs -u
  3. mount the /boot partiton to actually put the initramfs on the correct place

  Now the systems boots again, but this problem shouldn’t have happened
  in the first place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771000/+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 1702013] Re: package libsystemd0 229-4ubuntu10 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from oth

[Launchpad Bug Tracker]

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

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

-- 
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/1702013

Title:
  package libsystemd0 229-4ubuntu10 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz',
  which is different from other instances of package libsystemd0:amd64

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Preparing to unpack .../libsystemd0_229-4ubuntu17_amd64.deb ...
  Unpacking libsystemd0:amd64 (229-4ubuntu17) over (229-4ubuntu10) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libsystemd0_229-4ubuntu17_amd64.deb (--unpack):
   trying to overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz', 
which is different from other instances of package libsystemd0:amd64
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libsystemd0_229-4ubuntu17_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0 229-4ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jul  3 13:49:42 2017
  DpkgHistoryLog:
   Start-Date: 2017-07-03  13:49:40
   Commandline: apt-get install -f
   Requested-By: taman (1000)
   Upgrade: dbus-x11:amd64 (1.10.6-1ubuntu3.1, 1.10.6-1ubuntu3.3), 
libdbus-1-3:amd64 (1.10.6-1ubuntu3.1, 1.10.6-1ubuntu3.3), libsystemd0:amd64 
(229-4ubuntu10, 229-4ubuntu17), dbus:amd64 (1.10.6-1ubuntu3.1, 
1.10.6-1ubuntu3.3), libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu17)
  DpkgTerminalLog:
   Preparing to unpack .../libsystemd0_229-4ubuntu17_amd64.deb ...
   Unpacking libsystemd0:amd64 (229-4ubuntu17) over (229-4ubuntu10) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsystemd0_229-4ubuntu17_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from other 
instances of package libsystemd0:amd64
  DuplicateSignature:
   package:libsystemd0:229-4ubuntu10
   Unpacking libsystemd0:amd64 (229-4ubuntu17) over (229-4ubuntu10) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libsystemd0_229-4ubuntu17_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from other 
instances of package libsystemd0:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libsystemd0/changelog.Debian.gz', which is different from other 
instances of package libsystemd0:amd64
  InstallationDate: Installed on 2016-12-31 (183 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: systemd
  Title: package libsystemd0 229-4ubuntu10 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libsystemd0/changelog.Debian.gz', which is 
different from other instances of package libsystemd0:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1702013/+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 1770052] Re: display crashes

[Launchpad Bug Tracker]

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

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

-- 
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/1770052

Title:
  display crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  i am using ASROCK N68C-GS FX mother board and AMD SEMPRON LE1250 processor 
with 1GB RAM,500GB HDD,
  UBUNTU 14.04 INSTALLED WITHOUT ANY WARNING MESSAGES.but now the display 
crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  9 07:14:59 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:03d6]
  InstallationDate: Installed on 2018-05-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=efc9f66a-4d8f-412d-b243-becd83011893 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd01/18/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May  9 12:23:14 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImExPS/2 Logitech Explorer Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   VGA-1
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770052/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

It seems with the following two commands,  I can get my power from ~15W
to ~8W on Dell XPS 15 9560:

 # move from Nvidia to intel graphics (if not already done)
 prime-select intel
 # switch of power to Nvidia (repeat after each laptop start)
 sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
 sudo sh -c "echo "1" > remove"

-- 
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/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1762952] [NEW] Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
18.04

Steps to reproduce:
1. Define two keyboard input methods in Settings -> Region & Language -> Input 
Sources
2. Open several applications
3. Observe that application windows can be iterated with Alt + Tab
4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
5. Try to change keyboard input method switching hotkeys in Settings -> Region 
& Language -> Input Sources -> Options.
6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

Actual state:
* Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

Expected state:
* The shortcut for "Alternative switch to next source" can be changed and / or 
deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

Notes:
* The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: console-setup (Ubuntu)
 Importance: High
 Status: Confirmed

-- 
Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
https://bugs.launchpad.net/bugs/1762952
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to console-setup 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 1770968] Re: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

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

-- 
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/1770968

Title:
  package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read
  (Input/output error)

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Nothing else

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2.10
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Sun May 13 09:59:47 2018
  DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.10:cannot compute 
MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to 
read (Input/output error)
  InstallationDate: Installed on 2010-03-22 (2974 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2.10
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10, OpenSSL 1.0.1f 6 Jan 
2014
  SourcePackage: openssh
  Title: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read 
(Input/output error)
  UpgradeStatus: Upgraded to trusty on 2014-10-10 (1310 days ago)
  modified.conffile..etc.ssh.moduli: [inaccessible: [Errno 5] Input/output 
error]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770968/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

** Package changed: ubuntu-release-upgrader (Ubuntu) => console-setup
(Ubuntu)

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Carlos Gomes]

Most important information: I'm using ubuntu 18.04, fresh install

-- 
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/1574120

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Carlos Gomes]

My Thinkpad P51 is also affected by this bug. 
Gnome tweak tools is set to suspend on lid close, but nothing happens.

-- 
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/1574120

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Tom]

@Dedas: I cant see any difference; power consumption on Dell XPS 15 9560
stays the same...

-- 
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/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1770968] Re: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)

[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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1770968

Title:
  package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read
  (Input/output error)

Status in openssh package in Ubuntu:
  New

Bug description:
  Nothing else

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2.10
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Sun May 13 09:59:47 2018
  DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.10:cannot compute 
MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to 
read (Input/output error)
  InstallationDate: Installed on 2010-03-22 (2974 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2.10
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10, OpenSSL 1.0.1f 6 Jan 
2014
  SourcePackage: openssh
  Title: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read 
(Input/output error)
  UpgradeStatus: Upgraded to trusty on 2014-10-10 (1310 days ago)
  modified.conffile..etc.ssh.moduli: [inaccessible: [Errno 5] Input/output 
error]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770968/+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 1770968] [NEW] package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)

[Delta Creative]

Public bug reported:

Nothing else

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: openssh-client 1:6.6p1-2ubuntu2.10
ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
Uname: Linux 3.13.0-143-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Sun May 13 09:59:47 2018
DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.10:cannot compute 
MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)
ErrorMessage: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to 
read (Input/output error)
InstallationDate: Installed on 2010-03-22 (2974 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome 1:6.6p1-2ubuntu2.10
SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10, OpenSSL 1.0.1f 6 Jan 2014
SourcePackage: openssh
Title: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read 
(Input/output error)
UpgradeStatus: Upgraded to trusty on 2014-10-10 (1310 days ago)
modified.conffile..etc.ssh.moduli: [inaccessible: [Errno 5] Input/output error]

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


** Tags: apport-package i386 trusty

-- 
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/1770968

Title:
  package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade:
  cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read
  (Input/output error)

Status in openssh package in Ubuntu:
  New

Bug description:
  Nothing else

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2.10
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Sun May 13 09:59:47 2018
  DuplicateSignature: package:openssh-client:1:6.6p1-2ubuntu2.10:cannot compute 
MD5 hash for file '/etc/ssh/moduli': failed to read (Input/output error)
  ErrorMessage: cannot compute MD5 hash for file '/etc/ssh/moduli': failed to 
read (Input/output error)
  InstallationDate: Installed on 2010-03-22 (2974 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2.10
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10, OpenSSL 1.0.1f 6 Jan 
2014
  SourcePackage: openssh
  Title: package openssh-client 1:6.6p1-2ubuntu2.10 failed to install/upgrade: 
cannot compute MD5 hash for file '/etc/ssh/moduli': failed to read 
(Input/output error)
  UpgradeStatus: Upgraded to trusty on 2014-10-10 (1310 days ago)
  modified.conffile..etc.ssh.moduli: [inaccessible: [Errno 5] Input/output 
error]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1770968/+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 1770961] [NEW] Add options to set the snappy refresh schedule

[Ads20000]

Public bug reported:

Snappy has a feature where the user can state when in a month to refresh
(update) their snaps. Please provide options in Software & Updates to
control this.

https://snapdocs.labix.org/configuration-options/87

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Sun May 13 15:10:07 2018
InstallationDate: Installed on 2017-08-03 (282 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  New

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://snapdocs.labix.org/configuration-options/87

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770961/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Kyle Weber]

I upgraded from 17.10 to 18.04. It wouldn't log in, but through ssh I
purged the nvidia drivers, installed 396 through the PPA, rebooted, and
it came up and worked. It is a tower with GTX 1060.

-- 
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/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1586528] Re: Avahi-daemon withdraws address record

[ronny]

I think I found the culprit:
https://bugs.isc.org/Public/Bug/Display.html?id=45540

It boils down to a bug in the isc-dhcp-client. It doesn't correctly
react to time synchronization events and therefore simply breaks in
situations where time jumps "backwards" and the lease time in the
network is relatively short.

In my case I "fixed" the bug by removing the package isc-dhcp-client.
The NetworkManager now uses its internal dhcp client which doesn't
support as much features but at least works in my situations without
breaking the network connection.

** Bug watch added: bugs.isc.org/Public/ #45540
   https://bugs.isc.org/Public/Ticket/Display.html?id=45540

-- 
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/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration

[Bogdan Gribincea]

Installing libegl-mesa0 fixed the problem for me.
Kubuntu/KDE, AMD Radeon 7950

-- 
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/1752938

Title:
  Upgrading Ubuntu 18.04 disables GPU hardware acceleration

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I don't know which package causes this problem. The thing is ugrading
  Ubuntu 18.04 disables my GPU hardware acceleration.

  glxinfo_before_upgrade 
  OpenGL vendor string: X.Org
  OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 
4.15.0-10-generic, LLVM 5.0.1)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3

  glxinfo_after_upgrade 
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3

  This problem is reproducible.

  Steps to reproduce:
  1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily 
live(the installer in Mar 1 crashes which prevents me from installing it) and 
Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session 
and after the fresh install Ubuntu is also utilizing my GPU.
  2. Reboot into the newly installed system, do a dist-upgrade and reboot 
again. Opengl renderer falls back to llvmpipe.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Mar  3 00:58:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be]
  InstallationDate: Installed on 2018-03-02 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V-A
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D3V-A
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Dmitrii Shcherbakov]

I can confirm that the package version from bionic-proposed solves the
problem.

During an installation I used Dell 2715Q with settings as in the
screenshot attached (single monitor mode, 200% scaling).

# the updated package
apt policy ubiquity
ubiquity:
  Installed: 18.04.14.1
  Candidate: 18.04.14.1
  Version table:
 *** 18.04.14.1 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 18.04.14 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Before adding "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed
main restricted" to sources.list and doing `apt install ubiquity` I had
this in syslog:

ay 13 12:39:12 ubuntu ubiquity: W: --force-yes is deprecated, use one of the 
options starting with --allow instead.
May 13 12:39:12 ubuntu ubiquity[4617]: debconffilter_done: ubi-usersetup 
(current: ubi-usersetup)
May 13 12:39:12 ubuntu ubiquity[4617]: Step_before = stepUserInfo
May 13 12:39:12 ubuntu kernel: [  249.861407] do_trap: 40 callbacks suppressed
May 13 12:39:12 ubuntu kernel: [  249.861410] traps: ubiquity[4617] trap int3 
ip:7fc1a36cdc41 sp:7ffe6a90a760 error:0 in 
libglib-2.0.so.0.5600.1[7fc1a367c000+113000]
May 13 12:39:21 ubuntu update-notifier[4223]: GtkDialog mapped without a 
transient parent. This is discouraged.
May 13 12:39:22 ubuntu /install.py: Exception during installation:
May 13 12:39:22 ubuntu /install.py: Traceback (most recent call last):
May 13 12:39:22 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 765, in 
May 13 12:39:22 ubuntu /install.py: install.run()
May 13 12:39:22 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 135, in run
May 13 12:39:22 ubuntu /install.py: self.copy_all()
May 13 12:39:22 ubuntu /install.py:   File "/usr/share/ubiquity/install.py", 
line 513, in copy_all
May 13 12:39:22 ubuntu /install.py: self.db.progress('SET', 10 + 
copy_progress)
May 13 12:39:22 ubuntu /install.py:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
May 13 12:39:22 ubuntu /install.py: lambda *args, **kw: 
self.command(command, *args, **kw))
May 13 12:39:22 ubuntu /install.py:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
May 13 12:39:22 ubuntu /install.py: status = int(status)
May 13 12:39:22 ubuntu /install.py: ValueError: invalid literal for int() with 
base 10: ''


After the update a newly started installation went just fine.


** Attachment added: "displays-dell2715q.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5138751/+files/displays-dell2715q.png

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

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]: 

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Philipp Hahn]

I'm running Debian-Stretch 9.4 and I'm observing a similar problem that
after some time my servers disappears from the network; usually first
the IPv6 address, the usually some time later the IPv4 address, but not
always.

All computers are connected to my FritzBox 7420:
- for IPv4 I'm using the fixed address 192.168.xxx.33/24, which the FritzBox 
always assigns only to that host.
- for IPv6 I get a daily changing IPv6 address from my internet provider each 
night, which gets propagated by RA. 

The affected host is using systemd 232-25+deb9u2 and I have configured
systemd-networkd to do the network configuration:

/etc/systemd/network/40-dhcp.network
 DHCP=ipv4
 IPv6AcceptRA=yes

For now I have disabled DHCP for ipv4 and switched to a static
configuration, as it sometimes happens that the network is flacky and
does not receive an address during boot at all.

I once compiled my own version of systems with this patch included:
 

It is for .

While I had that custom version running I did *not* observe those issues, but 
then Debian shipped a security update and since than the problem is back.
This might not be the same issue as there have been different comments in this 
issue mentioning ifupdown,  NetworkManager, ..., but perhaps affected users 
should clarify their environment, e.g. IPv4 and/or IPv6, static addresses or 
changing addresses/prefixes, ...

** Bug watch added: github.com/systemd/systemd/issues #5625
   https://github.com/systemd/systemd/issues/5625

-- 
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/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1726625] Re: nautilus bookmarks become unclickable and hidden

[Ads20000]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: nautilus (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  nautilus bookmarks become unclickable and hidden

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  
  EXPECTED
  

  Clicking Nautilus bookmarks is expected to always open the bookmarked
  place.

  INSTEAD
  ===

   * The last clicked user added bookmark disappears.
   * Cannot click on any sidebar item (including all bookmarks and mounted 
places).

  
  REPRODUCING
  ===

  1) Click a fixed bookmark (Documents, Videos, Pictures...)
  2) Click a user added bookmark (not a mounted one, for example a bookmark of 
a local folder)
  3) If you still able to click, go to step 1

  Note: You may have to repeat it only once or a dozen times.

  
  PATCH (?)
  =

  Nautilus have to regenerate its sidebar to recover. It can be achieved
  either by unmounting something or by editing 'bookmarks' config
  file... etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 23 23:27:40 2017
  InstallationDate: Installed on 2017-08-08 (76 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1726625/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Dedas]

@Tom

"can you elaborate a bit more what that does?
- Is it safe?
- Will it allow switching nvidia on with "sudo prime-select nvidia" ?
- Is this command needed only once?"

Yes it should be safe. It it freezes just restart your machine, the
setting will be gone.

It turns off the nvidia gpu så no.

It is needed every time you boot. So use rc.local or something similar.

-- 
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/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1770940] [NEW] Kexec reboot doesn't work on 18.04 non-EFI system

[MegaBrutal]

Public bug reported:

Unclear whether to report it against kexec-tools or systemd.

After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the 
following error message:
Cannot find the ESP partition mount point.

What's interesting is that strace shows that systemctl tries to find the
EFI partition before it emits the error message, like it was expecting
an EFI system. My laptop is not capable of EFI, and it wasn't a problem
for previous Ubuntu releases – the „systemctl kexec” command worked fine
before.

Here is my systemd version:

root@thinkpad:~# systemd --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

And my kexec-tools version is 1:2.0.16-1ubuntu1.

I attached an strace output.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kexec-tools 1:2.0.16-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 12:48:25 2018
InstallationDate: Installed on 2014-06-10 (1432 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SourcePackage: kexec-tools
UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

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

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


** Tags: amd64 apport-bug bionic

** Attachment added: "strace-kexec.log"
   
https://bugs.launchpad.net/bugs/1770940/+attachment/5138678/+files/strace-kexec.log

** Also affects: systemd (Ubuntu)
   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/1770940

Title:
  Kexec reboot doesn't work on 18.04 non-EFI system

Status in kexec-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Unclear whether to report it against kexec-tools or systemd.

  After upgrading to Ubuntu 18.04, the „systemctl kexec” command gives the 
following error message:
  Cannot find the ESP partition mount point.

  What's interesting is that strace shows that systemctl tries to find
  the EFI partition before it emits the error message, like it was
  expecting an EFI system. My laptop is not capable of EFI, and it
  wasn't a problem for previous Ubuntu releases – the „systemctl kexec”
  command worked fine before.

  Here is my systemd version:

  root@thinkpad:~# systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  And my kexec-tools version is 1:2.0.16-1ubuntu1.

  I attached an strace output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kexec-tools 1:2.0.16-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 12:48:25 2018
  InstallationDate: Installed on 2014-06-10 (1432 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: kexec-tools
  UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1770940/+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 1761659] Re: package python3-crypto 2.6.1-6ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Sebastian Ramacher]

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

** This bug has been marked a duplicate of bug 1761701
   package python3-crypto 2.6.1-7build2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration

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

Title:
  package python3-crypto 2.6.1-6ubuntu0.16.04.3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in python-crypto package in Ubuntu:
  New

Bug description:
  Error occurred during Ubuntu update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-crypto 2.6.1-6ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-93-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  Date: Fri Apr  6 11:46:17 2018
  DuplicateSignature:
   package:python3-crypto:2.6.1-6ubuntu0.16.04.3
   Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
   dpkg: error processing package python3-crypto (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-02-01 (1524 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: python-crypto
  Title: package python3-crypto 2.6.1-6ubuntu0.16.04.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1761659/+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 1761701] Re: package python3-crypto 2.6.1-7build2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

** Changed in: python-crypto (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3-crypto 2.6.1-7build2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in python-crypto package in Ubuntu:
  Confirmed

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: python3-crypto 2.6.1-7build2
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Apr  6 19:38:47 2018
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-01-20 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: python-crypto
  Title: package python3-crypto 2.6.1-7build2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1761701/+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 1762699] Re: package python-crypto 2.6.1-4ubuntu0.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Sebastian Ramacher]

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

** This bug has been marked a duplicate of bug 1740338
   package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

Title:
  package python-crypto 2.6.1-4ubuntu0.2 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-crypto package in Ubuntu:
  New

Bug description:
  It shows system problem occured and it pop ups automatically and very
  frequently.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-crypto 2.6.1-4ubuntu0.2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Tue Apr 10 12:46:41 2018
  DuplicateSignature: package:python-crypto:2.6.1-4ubuntu0.2:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-01-10 (89 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: python-crypto
  Title: package python-crypto 2.6.1-4ubuntu0.2 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/python-crypto/+bug/1762699/+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 1768991] Re: [bytchtes8316] Sound does not work

[Load Line]

i can confirm this on X99 Asrock Extreme4 board
sound became dummy

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Touch-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work

[Launchpad Bug Tracker]

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

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

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Mediacom SmartBook 130 FullHD - M-SB130
  Package: pulseaudio 1:11.1-1ubuntu7
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1cdc0f32-803e-4151-924d-d5d369d8a7ee ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 565614] Re: totem crashed when loading dvd menu

[Sebastian Ramacher]

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

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

Title:
  totem crashed when loading dvd menu

Status in libdvdnav package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: totem

  This crash happened when I tried to jump to the dvd menu via clicking
  the entry in the respective totem GO menu

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: totem 2.30.0git20100413-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  CrashCounter: 1
  Date: Sat Apr 17 23:33:09 2010
  ExecutablePath: /usr/bin/totem
  ProcCmdline: totem /media/cdrom0
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x1636c32: mov0xc(%eax),%eax
   PC (0x01636c32) ok
   source "0xc(%eax)" (0x000c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/libdvdnav.so.4
   vm_start () from /usr/lib/libdvdnav.so.4
   dvdnav_get_next_cache_block () from /usr/lib/libdvdnav.so.4
   dvdnav_get_next_block () from /usr/lib/libdvdnav.so.4
   ?? () from /usr/lib/gstreamer-0.10/libresindvd.so
  Title: totem crashed with SIGSEGV in vm_start()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1707): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-terminal:1891): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdvdnav/+bug/565614/+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 1770682] Re: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz'

[AshrafBrown]

Found this work-around

Comment #3 from
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351 had this
workaround which worked perfectly for me:

sudo rm /usr/share/doc/libperl5.22/changelog.Debian.gz
sudo apt-get install -f

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

Title:
  Scanner driver failed to install. package libperl5.26 5.26.1-6 failed
  to install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  HP 1510 PSC scanner driver failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libperl5.26 5.26.1-6
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 18:01:31 2018
  DuplicateSignature:
   package:libperl5.26:5.26.1-6
   Unpacking libperl5.26:i386 (5.26.1-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-05-02 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1770682/+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 1770919] Re: use_tempaddr is reset to 0, despite /etc/sysctl.d

[Shivaram Lingamneni]

fixed affected package

** Package changed: systemtap (Ubuntu) => systemd (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/1770919

Title:
  use_tempaddr is reset to 0, despite /etc/sysctl.d

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm on a fresh install of 18.04 Server. It ships with the following
  file in /etc/sysctl.d:

  # cat /etc/sysctl.d/10-ipv6-privacy.conf
  # IPv6 Privacy Extensions (RFC 4941)
  # ---
  # IPv6 typically uses a device's MAC address when choosing an IPv6 address
  # to use in autoconfiguration. Privacy extensions allow using a randomly
  # generated IPv6 address, which increases privacy.
  #
  # Acceptable values:
  #0 - don’t use privacy extensions.
  #1 - generate privacy addresses
  #2 - prefer privacy addresses and use them over the normal addresses.
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2

  however, on boot, my physical NIC enp0s31f6 ends up with use_tempaddr
  set to 0:

  # for i in $(ls /proc/sys/net/ipv6/conf/*/use_tempaddr); do echo $i; cat $i; 
done;
  /proc/sys/net/ipv6/conf/all/use_tempaddr
  2
  /proc/sys/net/ipv6/conf/default/use_tempaddr
  2
  /proc/sys/net/ipv6/conf/enp0s31f6/use_tempaddr
  0
  /proc/sys/net/ipv6/conf/lo/use_tempaddr
  -1

  Explicitly adding the following line to 10-ipv6-privacy.conf does not
  fix:

  net.ipv6.conf.enp0s31f6.use_tempaddr = 2

  It appears that a later stage of the boot process reapplies the 0
  value. A workaround is to add the line, then create an additional
  systemd unit that runs `systemctl restart systemd-sysctl.service` at
  the end of the boot process.

  I think the expected behavior, given the contents of
  /etc/sysctl.d/10-ipv6-privacy.conf, is that all NICs should come up
  with use_tempaddr set to 2. This does not happen; moreover, the
  workaround is counterintuitive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770919/+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 1770919] [NEW] use_tempaddr is reset to 0, despite /etc/sysctl.d

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm on a fresh install of 18.04 Server. It ships with the following file
in /etc/sysctl.d:

# cat /etc/sysctl.d/10-ipv6-privacy.conf
# IPv6 Privacy Extensions (RFC 4941)
# ---
# IPv6 typically uses a device's MAC address when choosing an IPv6 address
# to use in autoconfiguration. Privacy extensions allow using a randomly
# generated IPv6 address, which increases privacy.
#
# Acceptable values:
#0 - don’t use privacy extensions.
#1 - generate privacy addresses
#2 - prefer privacy addresses and use them over the normal addresses.
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2

however, on boot, my physical NIC enp0s31f6 ends up with use_tempaddr
set to 0:

# for i in $(ls /proc/sys/net/ipv6/conf/*/use_tempaddr); do echo $i; cat $i; 
done;
/proc/sys/net/ipv6/conf/all/use_tempaddr
2
/proc/sys/net/ipv6/conf/default/use_tempaddr
2
/proc/sys/net/ipv6/conf/enp0s31f6/use_tempaddr
0
/proc/sys/net/ipv6/conf/lo/use_tempaddr
-1

Explicitly adding the following line to 10-ipv6-privacy.conf does not
fix:

net.ipv6.conf.enp0s31f6.use_tempaddr = 2

It appears that a later stage of the boot process reapplies the 0 value.
A workaround is to add the line, then create an additional systemd unit
that runs `systemctl restart systemd-sysctl.service` at the end of the
boot process.

I think the expected behavior, given the contents of
/etc/sysctl.d/10-ipv6-privacy.conf, is that all NICs should come up with
use_tempaddr set to 2. This does not happen; moreover, the workaround is
counterintuitive.

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

-- 
use_tempaddr is reset to 0, despite /etc/sysctl.d
https://bugs.launchpad.net/bugs/1770919
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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